Integration of a Decentralized WMS 
Integration of a Decentralized WMS
Use
You can use this function to connect an AFS ERP system to a decentralized Warehouse Management System (WMS).
Integration
This connection is based on the functions of the
Decentralized Warehouse Management System (LE-IDW). The information concerning warehouse processes is transferred to the decentralized WMS via an ALE interface.
You must use this interface to transfer AFS-specific information such as SKU and category to the decentralized WMS. See the section Features for a description of the warehouse processes for which the AFS-specific information can be transferred.
Prerequisites
If you want to use this function for AFS, you must first manually create an ALE distribution model in Customizing. In this case the system cannot automatically generate the distribution model. Make the following additional settings for the distribution model:
Features
The interface supports the transfer of the following data:
In AFS, batches are not created in the decentralized WMS, but rather in the centralized ERP system when the inbound delivery is created.
If a new batch is created in the inbound delivery in the ERP system which does not yet exist in the decentralized WMS, this batch will be replicated via the inbound delivery to the decentralized WMS. It is not possible to create and replicate batches in the transport order because in AFS new batches are created in the inbound delivery and replicated via the inbound delivery.
The ERP system replicates inbound deliveries via the BAPI AFSInboundDelivery.SaveReplica to the decentralized WMS. It transfers the SKU and category information as well.
The confirmation is sent to the ERP system via the BAPI InboundDelivery.ConfirmDecentral.
Any items with split batches will be considered accordingly.
The ERP system replicates outbound deliveries via the BAPI AFSOutboundDelivery.SaveReplica to the decentralized WMS. It transfers the SKU and category information as well.
The confirmation is sent to the ERP system via the BAPI OutboundDelivery.ConfirmDecentral. Any items with split batches will be considered accordingly.
The decentralized WMS can split the outbound delivery. The WMS then verifies the splitting results to the ERP system via the BAPI OutboundDelivery.SplitDecentral. The WMS also reports the information to the ERP concerning the SKUs and categories which are affected by the splitting.
The WMS generates inbound and outbound deliveries for stock transfers that are triggered in inventory management. The delivery items for each material are created at SKU and category level in AFS.
The decentralized WMS replicates any changes made to the data in the decentralized WMS to the ERP system via the BAPI GoodsMovement.CreateFromData.
In the following example, the inbound delivery with items and subitems is replicated in the decentralized WMS with the same structure, including the batches.
You have jeans in the colors light blue and dark blue and in the sizes S, M, L, and XL.
All sizes exist for each color in an inbound delivery. The inbound delivery therefore has a total of eight subitems for the jeans (at SKU / category level).
|
Delivery Item |
Color |
Size |
Quantity (Pieces) |
|
1 |
dark blue |
S |
10 |
|
2 |
dark blue |
M |
20 |
|
3 |
dark blue |
L |
20 |
|
4 |
dark blue |
XL |
10 |
|
5 |
light blue |
S |
5 |
|
6 |
light blue |
M |
10 |
|
7 |
light blue |
L |
10 |
|
8 |
light blue |
XL |
5 |