Settings in ALE Customizing 

You must perform the following activities in ALE Customizing to ensure that addresses are distributed together with the master objects:

  1. Maintain distribution model:
    IMG path: Basis Components – Distribution (ALE) – Modelling and Implementing Business Processes – Maintain Distribution Model and Distribute Views.
    The best way to illustrate this activity is the proposed model delivered by SAP for customer and vendor data distribution. For details, see the corresponding chapter in the Implementation Guide under Basis Components – Distribution (ALE) – Modelling and Implementing Business Processes – Predefined ALE Business Processes – Logistics – Master Data Distribution – Proposal for Distribution Model: Customer and Vendor Masters (IMG path). The associated activity runs report     RWALEACU which can also be used as a template for other objects with addresses.
  2. Activate change pointer for each message type:
    IMG path: Basis Components – Distribution (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 must separately activate the change pointers for message types     ADRMAS , ADR2MAS and ADR3MAS . This is not necessary if the data is to be sent directly.
  3. Define serialization groups:
    IMG path: Basis Components – Distribution (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:

    4. Serialization group

    Processing order of message types

    GRP_CRECOR_ADR

    ADRMAS, CRECOR

    GRP_CREMAS_ADR

    ADRMAS, CREMAS

    GRP_DEBCOR_ADR

    ADRMAS, DEBCOR

    GRP_DEBMAS_ADR

    ADRMAS, ADR3MAS, ADR2MAS, DEBMAS

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

    As a rule, you must create the serialization groups both in the sending and in the receiving system (however, you define inbound processing only in the receiving system).

    You can combine the sending and posting of IDocs that belong to a serialization group. To do this, choose Basis Components – Distribution (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 its sections Maintain Distribution Model and Serialized Distribution Using Message Types.

  4. Define inbound processing:
    IMG path: Basis Components – Distribution (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 must 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.
  5. Define partner profile:
    IMG path: Basis Components – Distribution (ALE) – Modelling and Implementing Business Processes– Partner Profiles and Time of Processing.
    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 must 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 must specify the IDoc basic type. In the case of address type 1 distribution between two systems running the current release, you must also 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 must 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.

 

Data filtering during address distribution has not been implemented.