Hierarchy
BBPCRM (Software Component) BBPCRM⤷
CRM (Application Component) Customer Relationship Management⤷
CRM_APPLICATION (Package) All CRM Components Without Special Structure Packages⤷
VL (Package) WS-SHP: General Processing for Shipping
IMG Activity
| ID | SIMG_XXLEIDW2009 | Generate Distribution Model |
| Transaction Code | S_ALR_87003591 | IMG Activity: SIMG_XXLEIDW2009 |
| Created on | 19981222 | |
| Customizing Attributes | SIMG_XXLEIDW2009 | Generate distribution model |
| Customizing Activity | SIMG_XXLEIDW2009 | Generate distribution model |
Document
| Document Class | SIMG | Hypertext: Object Class - Class to which a document belongs. |
| Document Name | SIMG_XXLEIDW2009 |
Generate Distribution Model
You use this activity to allow communication between a central Enterprise Resource Planning system (ERP system) and a decentralized Warehouse Management System (WMS) asynchronously using IDocs and Application Link Enabling (ALE). To achieve this, you define a distribution model.
Maintaining the distribution model requires that the necessary objects to be distributed are known. Use the option of generating the distribution automatically through the IMG. With this process, all necessary entries in the ALE distribution model are considered for the decentralized WMS.
Take note of the following when you generate the distribution model:
- Decentralized processing is activated for a specific warehouse number. This warehouse number must be entered for the distribution and must be pre-defined in the system.
- So that the generated distribution for the decentralized WMS is visible in the distribution model, you must enter a name for the model view. You can then use this name to locate the generated distribution in the distribution model.
If you generate the distribution for a specific warehouse number for the first time, enter a new name for the view to be generated. If you want to expand an existing view, you must enter the corresponding existing name.
- Enter the systems between which communication takes place as logical system names so that the partner relationship can be defined in the distribution model.
- Defining the distribution objects for the application data does not require any further specifications since in this case the distribution takes place based on the decentralized warehouse number. The warehouse number or the plant/storage location combination assigned to the warehouse number is used as the filter object for distributing these objects.
- Master data distribution is customer-specific. The standard system provides numerous options of defining the filtering process within master data distribution. This is why the generation task includes several specific selection parameters as filter objects.
You can select the following filter objects for the material master:
- Sales organisation and distribution channel
- Material type
- Plant and storage location assigned to the selected decentralized warehouse number are automatically defined as filter objects. For the customer master, you can define the sales organisation and the distribution channel as filter objects.
The material master and the customer master must always be distributed. It depends on your application whether the other master data needs to be distributed as well.
- If the vendor master is to be distributed, you must enter the corresponding message type (CREMAS by default).
- If you work with materials that are to be handled in batches, you must activate the distribution of the batches. If you use batch classification, you must also activate the distribution for batch classes.
- If you use the SAP Retail System, the necessary objects are considered in the distribution model for the distribution of the article masters. If your system is configured as a pure retail system (system setting '00' = 'SAP Retail System'), only the article masters are distributed; the distribution for the material masters is not generated. However, if you use the SAP Retail System in connection with the Manufacturing System (standard system) (system setting '99' = mixed), the distribution is generated for both the article master and the material master.
You can select the following filter objects for the article master:
- Sales organisation and distribution channel
- Plant and storage location assigned to the selected decentralized warehouse number are automatically defined as filter objects
- If you use the address file, the addresses for the customer and vendor masters must also be distributed.
The adresses are distributed separately from their master objects (customer/vendor); this means, that they are distributed as stand-alone objects. To ensure that the addresses are only sent to those systems to which their master objects are directed, dependencies between the methods of the address objects and the default message types of customer/vendor were defined. For defining the distribution of the address data in connection with the customer/vendor master, the system provides a separate generation task that you can access from within the closing screen of the WMS distribution generation.
For more information on distributing addresses in connection with the customer/vendor master, refer to the documentation Proposal for distribution model: Customer and vendor masters.
For more information on distributing the individual objects, refer to the documentation on the individual distribution objects.
Application-relevant update
Once the distribution model is generated, the individual objects for the defined warehouse number can be distributed. The distribution for decentralized processing is controlled based on the distribution model and the application. Both the model and the application must be maintained consistently since only then the distribution can be recognized and performed. In the central ERP system, you must activate the warehouse number for decentralized processing. In the decentralized WMS, you must activate the reference to the ERP system at storage location and plant level. After the distribution model is generated, all necessary settings are activated in the application irrespective of the individual maintenance. Since several updates are carried out in the partner system when the settings are activated in the application, direct communication with this system is necessary. If the distribution model is generated in the central system, synchronous communication with the decentralized WMS is required. If the distribution model is generated in the decentralized WMS, then the synchronous communication link to the ERP system is used. For more information on defining synchronous communication, refer to the documentation Distribution.
Requirements
Start this report in test mode, before you generate the distribution for the decentralized WMS. The system lists the individual methods and message types which are required for this scenario and which are defined in the distribution model when the report is run in production mode.
The warehouse number which has been defined for decentralized WMS processing, must be fully maintained both in the central and in the decentralized system.
The following data must be pre-defined in the system so that the distribution can be generated:
- The logical systems for the central ERP system and the decentralized WM system
- The RFC destination for communication between the ERP system and the WM system
- The definition of the synchronous communication between the ERP system and the WM system
For more information on the distribution requirements, refer to the dcocumentation Distribution.
Standard settings
The following relevant methods are generated for the data exchange of the WMS application:
OutboundDelivery.SaveReplicato send outbound deliveries from the ERP system to the WM systemInboundDelivery.SaveReplicato send inbound deliveries from the ERP system to the WM systemOutboundDelivery.ConfirmDecentralto send confirmations of the outbound deliveries from the WM system to the ERP systemInboundDelivery.ConfirmDecentralto send confirmations of the inbound deliveries from the WM system to the ERP systemGoodsMovement.CreateFromDatato report stock transfers/posting changes/differences from the WM system to the ERP systemInboundDelivery.Changeto change inbound deliveries subsequently in the central ERP system or the decentralized WM systemOutboundDelivery.Changeto change outbound deliveries subsequently in the central ERP system or the decentralized WM system
As far as methods 1 to 4 are concerned, the warehouse number to be distributed is defined as a filter object. For 'GoodsMovement.CreateFromData', the plant/storage location is the filter object.
For the communication direction from the central to the decentralized system, for the methods 1 through 4 and 6 through 7, the warehouse number is defined as the filter object.
For the communication direction from the decentralized to the central system, for the methods 1 through 4 and 6 through 7, the warehouse number to distribute and the logical ERP system are each defined as a filter object. In this case, after you generate the ALE model, you can decide which of the two filter objects should be used. Make the relevant setting in the following activity: SAP Web Application Server--> Application Link Enabling (ALE) --> Modelling and Implementing Business Processes --> Maintain Distribution Model and Distribute Views.
The following message types are generated for the master data distribution:
- MATMAS (or a customer-specific reduced message) for distributing the material masters from the ERP system to the WM system.
The additional selection parameters on the init
Business Attributes
| ASAP Roadmap ID | 255 | Create Interfaces |
| Mandatory / Optional | 1 | Mandatory 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 | SIMG_XXLEIDW2009 | 0 | ALR0000093 | Central Processing |
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 | OL19 | 01 | Generate distribution model |
History
| Last changed by/on | SAP | 20011207 |
| SAP Release Created in |
