Maintain distribution model: IMG path:  SAP NetWeaver Application Server IDoc Interface/Application Link Enabling (ALE) Modelling and Implementing Business Processes Maintain Distribution Model and Distribute Views . This activity is best illustrated in the proposed model delivered by SAP for customer and vendor data distribution.

For more information, see the corresponding chapter in the Implementation Guide (IMG) under  SAP NetWeaver Application Server IDoc Interface/Application Link Enabling (ALE) Modelling and Implementing Business Processes Configure Predefined ALE Business Processes Logistics Master Data Distribution Proposal for Distribution Model: Customer and Vendor Masters .

The associated activity runs report RWALEACU, which can also be used as a template for other objects with addresses.

Activate change pointer for each message type: IMG path:  SAP NetWeaver Application Server IDoc Interface/Application Link Enabling (ALE) Modelling and Implementing Business Processes Master Data Distribution Replication of Modified Data In addition to activating the change pointers on a general basis in the current client, you also have to activate the change pointers separately for message types ADRMAS, ADR2MAS and ADR3MAS. This is not necessary if the data is to be sent directly.

Define serialization groups: IMG path:  SAP NetWeaver Application Server IDoc Interface/Application Link Enabling (ALE) Modelling and Implementing Business Processes Master Data Distribution Serialization for Sending and Receiving Data Serialization Using Message Types Define Serialization Groups . SAP delivers the following serialization groups as proposals:

For objects other than customer and vendor, you have to define and deliver appropriate serialization groups with regard to the message types of the application. When you create a serialization group, you have to specify a sequence number for each message type. These sequence numbers determine the order of processing.

You can combine the sending and posting of IDocs that belong to a serialization group. To do this, choose  SAP NetWeaver Application Server IDoc Interface/Application Link Enabling (ALE) Modelling and Implementing Business Processes Master Data Distribution Serialization for Sending and Receiving Data Serialization Using Message Types in the IMG to model message type SERDAT and maintain the relevant settings such as the partner profile. For more information, see the IMG chapter Serialization Using Message Types and the subsections Maintain Distribution Model and Serialized Distribution Using Message Types.

Define inbound processing: IMG path:  SAP NetWeaver Application Server IDoc Interface/Application Link Enabling (ALE) Modelling and Implementing Business Processes Master Data Distribution Serialization for Sending and Receiving Data Serialization Using Message Types Define Inbound Processing . In the receiving system, you have to make an entry for each combination of serialization group, message type, and sending system. These entries cannot be preconfigured and delivered by SAP since the sending system depends on the specific distribution model.

Maintain partner processing: IMG path:  SAP NetWeaver Application Server IDoc Interface/Application Link Enabling (ALE) Modelling and Implementing Business Processes Partner Profiles . You can either generate the partner profiles from a completely maintained distribution model, maintain the partner profiles manually, or manually edit partner profiles that have been generated. For partner type LS (= Logical system), you have to maintain message types ADRMAS, ADR2MAS and ADR3MAS as the outbound parameters in the sending system for the partner number of the receiving system. In addition to the recipient port, you also have to specify the IDoc basic type. In the case of address type 1 distribution between two systems running the current release, you also have to enter ADRMAS02. For serialization during outbound processing, select Collect IDocs and transfer as the output mode; otherwise, select Transfer IDoc immediately. In the receiving system, you have to maintain message types ADRMAS, ADR2MAS and ADR3MAS as the inbound parameters for the partner number of the sending system. Enter BAPI as the process code. For serialization during inbound processing, select Trigger by background program in the Processing group box.