Hierarchy
SAP_APPL (Software Component) Logistics and Accounting⤷
CA-BFA-ABL (Application Component) ALE Business Process Library⤷
DALE (Package) ALE Application
IMG Activity
| ID | OALE_DSTSCN_SDMM | Stock Transfer Between Distributed Systems |
| Transaction Code | S_ALR_87008557 | IMG Activity: OALE_DSTSCN_SDMM |
| Created on | 19990115 | |
| Customizing Attributes | OALE_DSTSCN_SDMM | Stock Transfer Between Distributed Systems |
| Customizing Activity | OALE_DSTSCN_SDMM | Stock Transfer Between Distributed Systems |
Document
| Document Class | SIMG | Hypertext: Object Class - Class to which a document belongs. |
| Document Name | OALE_DSTSCN_SDMM |
In this section of the IMG, the settings necessary for the scenario Transfer between distributed systems are outlined.
The Customizing and the processing of master data are discussed.
Consistency checking
The function in this chapter checks the consistency of your settings. We recommend that you make use of this consistency checking when you make the relevant settings.
Execute the function in the purchasing system. This allows you to check whether the settings between the systems are correctly maintained for the message types that are required. Check the application consistency for the sending system and the 'ORDERS' message.
To perform the consistency check, you have to create a variant of the RBDMMSD1 report.
The check tests the settings for the 'Stock transfer between distributed systems' scenario and the 'Separate sales' scenario. For that reason, you can ignore the warning message that no variant for report RBDSDMM1 exists. This variant only tests the settings for the 'Separate sales' scenario.
If you double-click on one of the lines of the consistency check log, you will enter the corresponding Customizing transaction and you can make the necessary settings there.
Before you can do this, it is necesssary that you have maintained the partner profiles in all the relevant systems.
Partner profiles
The partner profile settings can be generated from the customer distribution model. Please see the section entitled Communication in this IMG.
The message types are as follows:
Message type Meaning Input & output parameters
ORDERS purchase order output purchasing system and
input shipping system
ORDCHG purchase order change output purchasing system and
input shipping system
ORDRSP order acknowledgement output shipping system and
input purchasing system
DESADV shipping notification output shipping system and
input purchasing system
INVOIC invoice output shipping system and
input purchasing system
The intermediate document type ORDERS01 or ORDERS02 must be set in both cases when setting the output parameters.
Example
- In this scenario, the purchasing system in system A should procure goods via purchase orders in system B. The purchasing system sees the shipping system as a vendor; the shipping system sees the purchasing system as a customer.
- The messages which go from system A to system B are: purchase order and purchase order change;
- The messages which come back are: order confirmation, shipping notification and billing document. It is not strictly necessary for the
- shipping notification to be returned.
Maintaining the customer distribution model
You should use customer or vendor as the filter object
when maintaining the customer distribution model with the PC Tool. For
numeric values, specify the number with leading zeroes.
Settings in the purchasing system
Message control
MM Customizing
- The message control has to be set up for the outgoing messages
(purchase order, purchase order change).
- The standard uses the NEU output type.
- Proceed as follows to set up the message control:
- The NEU output type is defined in client 000. Copy the NEU output type
- to other clients if necessary.
- The RMBEF1 message determination schema must be assigned for purchase orders.
- The NEU message must be allocated to the RMBEF1 schema.
You can find more information on setting up message control in this IMG in the section called Messages -> Output control in the Purchasing book.
Shipping notification input
To ensure that the shipping notification can be posted via ALE, you must use a confirmation control key in purchasing.
For more detailed information on this, please refer to the Purchasing Implementation Guide, chapter Shipping notification -> Set up confirmation control.
Invoice verification
For incoming invoices, the following must be set up:
- which company code and
- which document type and default control key (program parameters)
are to be used in the document. Please refer to the Implementation Guide, section Invoice verification -> EDI in the chapter on materials management.
Error processing
To ensure that work items are generated for error processing should an error arise, the standard tasks listed below must be assigned to positions or workflow organizational units.
Standard task: ID code Description
ORDRSP_Error ORDRSP inbound error
DESADV Error DESADV inbound error
INVOIC_MM_Err INVOIC inbound error MM
You can find more information on this in the menu: Error handling
Settings in the shipping system
Message control
SD Customizing
Message control must be set up correspondingly for the outbound messages (order response, shipping notification and billing document). You can find information on this subject in the Implementation Guide: Sales and Distribution -> Basic functions -> Messages -> Message determination -> Message default via condition technique.
Assignment to sales area
The sales area must be determined for incoming sales orders (purchase orders). A description of how to set this up is given in the Sales and Distribution Implementation Guide Electronic Data Interchange -> EDI messages. Choose Configuration EDI (transaction VOED) in the popup and then choose the menu function Partner -> Application -> Customer/vendor.
The reassignment of partner numbers is not necessary in 3.0, since you can store your own number with the partner in the customer master or in the vendor master. You can find more information on this in the section called Master data for purchasing and shipping.
Processing of warnings
When an order arrives you can make settings which determine the system's response to certain errors. In the Sales and Distribution chapter of the Implementation Guide, Electronic Data Interchange -> EDI messages, choose Define exception processing (transaction SMME).
Error processing
To ensure that work items are generated for error processing should an error arise, the standard tasks listed below must be assigned to positions or workflow organizational units.
Standard task: ID code Description
ORDERS_Error ORDRSP inbound error
ORDCHG_Error ORDCHG inbound error
Master data for purchasing and shipping
Business partners
- Create the customer "purchasing" and the vendor "shipping". The customer must exist in the shipping system, and the vendor in the purchasing system
- For the customer "purchasing", specify "shipping" as the "separate number for partner". (View: 'purchasing', field: 'Account w. customer').
- For the vendor "shipping", specify "purchasing" as the "separate number for partner". (View: 'correspondence', field: 'Account w. vendor').
Purchasing information record
- The material number of the partner must be maintained in the purchasing system, even if the material numbers in the two systems are identical.
- You make sure of this by creating a purchasing information record in the purchasing system.
- Alternatively this can be maintained in the sales information record.
Messages conditions record
- Purchasing system
You must create a messages conditions record for the purchase order for the NEU output type. You use the following key combination to do this: 'document type / purchasing organization / vendor'.
Specify the following parameters for the messages conditions record:
- Document type: 'NB'
- Transmission medium for message: 'A' (ALE)
- Other settings: as required
The messages conditions record is created in the menu: Logistics -> Materials management -> Purchasing -> Master data -> Messages -> Purchase order -> Create.
- Shipping system
You must create messages conditions records for the following document types:
- 1. Sales
Business Attributes
| ASAP Roadmap ID | 204 | Establish Functions and Processes |
| Mandatory / Optional | 2 | Optional activity |
| Critical / Non-Critical | 1 | Critical |
| Country-Dependency | A | Valid for all countries |
Assigned Application Components
| Documentation Object Class | Documentation Object Name | Current line number | Application Component | Application Component Name |
|---|---|---|---|---|
| SIMG | OALE_DSTSCN_SDMM | 0 | HLA0009512 | Purchasing |
Maintenance Objects
| Maintenance object type | C | Customizing Object |
| Assigned objects | ||||||
|---|---|---|---|---|---|---|
| Customizing Object | Object Type | Transaction Code | Sub-object | Do not Summarize | Skip Subset Dialog Box | Description for multiple selections |
| IMGDUMMY | D - Dummy object | BDD5 | 305 |
History
| Last changed by/on | SAP | 19990119 |
| SAP Release Created in |
