Hierarchy
⤷ 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_XXLEIDW2016 | Batches |
Transaction Code | S_ALR_87003601 | IMG Activity: SIMG_XXLEIDW2016 |
Created on | 19981222 | |
Customizing Attributes | SIMG_XXLEIDW2016 | Batches |
Customizing Activity |
Document
Document Class | SIMG | Hypertext: Object Class - Class to which a document belongs. |
Document Name | SIMG_XXLEIDW2016 |
When a transfer order is created for an inbound delivery in the WM system, goods that are delivered from an external or internal source are recorded in the system. For materials to be handled in batches, new batch stock can be added to existing batch stock. If no batch is specified when the transfer order is created or if a batch is specified by an external system for which no master record exists, the system automatically creates a batch master record in the WM system. At the same time, the system recognizes that the central ERP system must be informed. The batch master record is transferred to the ERP system and created there.
Batch distribution
For the distribution of batches, the individual batches are replicated. The entire process is controlled through the filter objects. The filters define the amount of data to be distributed. Set the filters appropriately so that batches created in the WM system are distributed to the ERP system. The filter object to be used is the plant. When the distribution model is generated in advance, the plant assigned to the decentralized WMS is used as the filter object.
Example
Requirements
Standard settings
Distribution is carried out using BAPI Batch.SaveReplica. (Method SaveReplica for object type BUS1001002 = Batch). Communication is asynchronous and takes place via the IDoc of message type BATMAS generated from the BAPI.
Recommendation
Activities
- You must maintain the distribution model for method Batch.SaveReplica.
If the central system (ERP system) is an SAP system, the distribution model is maintained in the central system and distributed to the decentralized WMS. In this case, you are not required to maintain the model for this method.
If the central system (ERP system) is a non-SAP system, you must maintain this method together with all other distribution objects when the distribution model is generated.
Further notes
Business Attributes
ASAP Roadmap ID | 255 | Create Interfaces |
Mandatory / Optional | 2 | Optional activity |
Critical / Non-Critical | 2 | Non-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_XXLEIDW2016 | 0 | ALR0000094 | Local Operations |
Maintenance Objects
Maintenance object type |
History
Last changed by/on | SAP | 19981222 |
SAP Release Created in |