Você está na página 1de 2

ALE Scenario:

Customer has a separate SAP Warehouse Management System (WMS) in the R/3 landscape
where all R/3 Distribution data are replicated/distributed from R/3 to the WMS system via ALE.
For example, Sales Orders are created in R/3 - when they are delivered (Sales document-
>Deliver) the ALE kicks in and the same Delivery doc is distributed to the WMS system but the
Sales order is not distributed. Any subsequent functions for the Delivery like Picking, Packing,
Goods Issue, Shipment is then done from the WMS system only so that all distribution specific
transactional data are stored and processed from the WMS system.

Again, in order to successfully distribute the delivery documents to the WMS system from R/3 via
ALE, a lot of SD master data needs to be distributed prior to these subsequent distribution
business processes (like picking, packing, GI etc.). So another set of ALEs are also set up to
distribute SD master data via IDocs (within the ALE framework) to the WMS system every time
master data is created/changed in the R/3 - for example - Plant, Warehouse, Storage Type,
Storage Location, Material Master etc.

For distribution of materials from R/3 to WMS, we use Basic Type/IDoc Type MATMAS05,
Message Type MATMAS. We've set up MATMAS05 using ALE Filters on Division, Sales Org.,
Distribution Channel, Material Type, Storage Location and Plant as we want only specific org
data to distribute across WMS.

The transaction codes that are required for this method are

We81

We30

We31

We82

We21

We20

Bd64

Nace

Me22n (purchase order), va02 (sales order) etc.


Ex: purchase order.

Message type: ORDERS

Idoc type: ORDERS05

Outbound process code for purchase order: me10

Você também pode gostar