Customer Master

So that deliveries can be replicated in the decentralized system, customer masters must exist for the ship-to parties specified in the deliveries. The customer master must be distributed between the central ERP system and the decentralized WM system.

The leading system for the customer master is the central ERP system. In this system, the customer master is created and distributed to the WMS. In the decentralized WMS, you need the basic data and the sales view of the customer master. Which basic and sales data is required, depends on the decentralized processing functions used in the WM system.

The following basic rules apply:
Distribute only the necessary master data so that the WM system remains able to operate.

Be aware that you must manually maintain all necessary Customizing settings for the customer master in the decentralized WMS.

For general information on master data distribution, refer to the ALE documentation Master Data Distribution.

Reduction for customer master

To distribute not all customer master data, reduce the standard IDoc DEBMAS (see also: ALE documentation Create reduced message type for master data ).

The reduced IDoc must contain the following segments:

• E1KNA1M - Master customer master basic data (KNA1)

• E1KNA11 - Master customer master: additional general fields (KNA1)

• E1KNVVM - Master customer master sales data (KNVV)

Within the individual segments, you can also carry out reductions at field level. To do this, deactivate the fields that you do not need.

Customer master distributioln

The customer master distribution is carried out based on the reduced message type and controlled through the filter objects. The filters define the amount of data to be distributed. Set the filters appropriately so that only customer master data relevant for the decentralized WMS is distributed, that is, the basic data and the data of the relevant sales areas (sales organisation, distribution channel, division).

If you define a filter object (sales organisation) that does not refer to the root segment (E1KNA1M), the filtering process during distribution only starts with the specific segment that is assigned to the filter. If, for example, a sales organisation is defined as the filter, then only the segment of this sales organisation is distributed. All other segments that are independent of this sales organisation are passed on without being filtered. The master data can also be distributed using classes. In this case, only customer masters of a specific class are distributed to the decentralized WMS (see also: ALE documentation Distribution Using Classes .) To maintain the required settings, go to ALE Customizing and choose Distribution (ALE) -> Master Data Distribution -> Distribution Using Classes.

Address data distribution

The addresses are distributed through stand-alone IDos separately from the customer master. If the address distribution is defined in the distribution model, the dependent addresses are automatically distributed with the customer master. For more information on the distribution of addresses in connection with the customer/vendor master, refer to documentation Distribution model proposal: customer and vendor masters.

Example

Reduced IDoc DEBMAS:

DEBMAS03
|
---# E1KNA1M (*) Master customer master basic data (KNA1)
|
|------E1KNA11 (+) Customer master: additional general fields
|---# E1KNA1H (+) Mast. cust. master basic data: texts, header
| |
| -------E1KNA1L (+) Mast cust. master basic data: text line
|
|---# E1KNVVM (+) Master customer master sales data (KNVV)
|
----# E1KNVVH (+) Master customer master sales data: texts
|
------ E1KNVVL (+) Mast. cust. master sales: text line

All fields of the individual segments are activated.

Activities

• Reduce the standard message type DEBMAS for the distribution of the customer master. To maintain the message type, go to ALE Customizing and choose Distribution (ALE) -> Master Data Distribution -> Create reduced message type for master data.

• Perform all additional activities (such as activating the change pointer, setting the distribution using classes) for the new message type you have created. To do this, go to ALE Customizing and choose Distribution (ALE) -> Master Data Distribution.

• So that the customer master changes can be distributed, you must schedule a report that evaluates the change pointers and generates the IDocs. To schedule the report, go to ALE Customizing and choose Distribution (ALE) -> Scheduling Periodic Processing -> Scheduling IDoc Creation from Change Pointers.

• Check within ALE if further activities such as serialized distribution are still necessary.

• Maintain the distribution model for the new message type you have created. Maintain this message together with all other distribution objects when the distribution model is generated. If the address data is also to be distributed, activate distribution model generation for the address data as well.