Show TOC

Background documentationData Replication of Business Partner Master Data Using ALE

 

Replication of business partner master data from the MDG hub to the connected systems and clients can be done using Application Link Enabling (ALE).

  1. Set up RFC connections (in both directions: hub to client and client to hub

    1. Set up the RFC connection: Run transaction SM59 (configuration of RFC connections) and provide the required RFC destination details.

    2. To define a logical system in Customizing for SAP Netweaver run transaction SALE and then choose Start of the navigation path Basic Settings Next navigation step Logical Systems Next navigation step Define Logical System End of the navigation path. Enter all target systems/clients as logical systems.

  2. Maintain distribution model in SAP ERP (Outbound) for the distribution of Business Partner Master

    1. Run transaction SALE (Display ALE Customizing) and choose Start of the navigation path Modeling and Implementing Business Processes Next navigation step Maintain Distribution Model and Distribute Views End of the navigation path. Alternatively, run transaction BD64 (Display Distribution Model).

    2. In change mode, create a new model. Choose the Create Model View. Enter a short text and a technical name.

    3. Choose Add Message Type for the newly created model.

    4. Enter names for the logical source and destination systems and choose message type BUPA_INBOUND_MAIN_SAVE_M and BUPA_INBOUND_REL_SAVE_M.

    Note Note

    For the maintenance of the distribution model in an SRM or a CRM system (Inbound), repeat steps 1 to 4 in the corresponding system.

    End of the note.

    Note Note

    To distribute business partner data and business partner relationship data, configure your target system as described:

    1. Run transaction SALE and choose Start of the navigation path Modelling and Implementing Business Processes Next navigation step Master Data Distribution Next navigation step Serialization for Sending and Receiving Data Next navigation step Serialization Using Message Types Next navigation step Define Serialization Groups End of the navigation path.

      1. Define a serialization group.

      2. Assign the message types listed below to the serialization group and enter the corresponding sequence numbers:

        Message Type

        Seq. number

        BUPA_INBOUND_MAIN_SAVE_M

        1

        BUPA_INBOUND_REL_SAVE_M

        2

    2. Run transaction SALE and choose Start of the navigation path Modelling and Implementing Business Processes Next navigation step Master Data Distribution Next navigation step Serialization for Sending and Receiving Data Next navigation step Serialization Using Message Types Next navigation step Define Inbound Processing End of the navigation path and enter the following data:

      Group

      Message Type

      Sending system

      Obj/Proc

      [Serialization group]

      BUPA_INBOUND_MAIN_SAVE_M

      [Sending system]

      [value, e.g. 100]

      [Serialization group]

      BUPA_INBOUND_REL_SAVE_M

      [Sending system]

      [value, e.g. 100]

    3. Make sure that incoming IDocs are not processed immediately. Run transaction WE20 and choose Start of the navigation path Partner Next navigation step Partner Type LS Next navigation step [Sending system] End of the navigation path. For both inbound parameters proceed as described:

      1. Select the inbound parameter.

      2. Choose DetailScreenInboundParameter.

      3. On the Inbound options tab, select Trigger by background program.

    4. Run transaction SE38 and create a variant for the Report RBDSER04. AsSerialization Group enter the serialization group created above.

    End of the note.

  3. Create partner profile

    1. Run transaction SALE and choose Start of the navigation path Modeling and Implementing Business Processes Next navigation step Partner Profiles Next navigation step Generate Partner Profiles End of the navigation path. Alternatively, run transaction BD82 (Generate Partner Profile).

    2. Select the newly created model and in the Partner System field, enter the logical destination system.

    3. Enter the ALE-User and the following values in the corresponding fields, and execute.

      Field

      Value

      Version

      3

      Pack Size

      100

      Output Mode

      Transfer IDoc immediately

      Inb. Parameters: Processing

      Trigger immediately

    4. To verify your settings, run transaction WE20 and from the Partner Profiles menu, choose Partner type LS. Verify that Partner type LS is the logical destination system.

    5. In the detail screen, the chosen message types BUPA_INBOUND_MAIN_SAVE_M and BUPA_INBOUND_REL_SAVE_M must appear as outbound parameters.

  4. Distribute model view to receiving system.

    1. Run transaction SALE and choose Start of the navigation path Modeling and Implementing Business Processes Next navigation step Maintain Distribution Model and Distribute Views End of the navigation path. Alternatively, run transaction BD64.

    2. Select the new model and choose Start of the navigation path Edit Next navigation step Model view Next navigation step Distribute End of the navigation path.

    3. Verify that the correct receiving system is marked and choose Enter.

    4. Verify within the receiving system that the model view was created.

      1. Run transaction SALE and choose Start of the navigation path Modelling and Implementing Business Processes Next navigation step Partner Profiles Next navigation step Generate Partner Profiles End of the navigation path. Alternatively, run transaction BD82.

      2. Select the distributed model and the partner system.

      3. Enter the ALE-User and the following values in the corresponding fields, and execute.

        Field

        Value

        Version

        3

        Pack Size

        100

        Output Mode

        Transfer IDoc immediately

        Inb. Parameters: Processing

        Trigger immediately

      4. To verify your settings, run transaction WE 20 and from the partner profiles menu, choose partner type LS. Verify that partner type LS is the logical destination system.

      5. In the detail screen, the chosen message types BUPA_INBOUND_MAIN_SAVE_M and BUPA_INBOUND_REL_SAVE_M must appear as inbound parameters.

  5. Replication ALE Using the Data Replication Framework (DRF)

    Prerequisite: Receiving systems/clients are defined in the SLD (system landscape directory). For more information, see Customizing for Master Data Governance under Start of the navigation path General Settings Next navigation step Data Replication Next navigation step Overall Information End of the navigation path.

    1. Define technical settings for business system under Start of the navigation path General Settings Next navigation step Data Replication Next navigation step Define Custom Settings for Data Replication Next navigation step Define Technical Settings Next navigation step Define Technical Settings for Business Systems End of the navigation path.

      1. To define a new business system and to maintain the logical system for the receiving systems, choose New Entries.

      2. Enter a business system, for example ABC_123 and a logical system, for example ABCCLNT123, select the Define Bus. Systems, BOs view, and enter the BO Type 147 (Business Partner) and 1405 (Business Partner Relationship).

      3. Make sure that under Start of the navigation path General Settings Next navigation step Data Replication Next navigation step Enhance Default Settings for Outbound Implementations Next navigation step Define Outbound Implementations End of the navigation path in the line 986_1 (Outbound Impl. for MDG BP via ALE) the Sup. Key H (Support Key Harmonization) flag is set.

      4. Mark the BO Type 147 (Business Partner) and 1405 (Business Partner Relationship), select the Define Bus. Systems, BOs, Communication Channel view, enter the C. Channel Replication via IDoc, and select the value Key Mapping for the Key Harm. field.

        Note Note

        If you select Harmonized IDs (no key mapping) for Key Harm. you have to use ALE inbound. It is not possible to import data using MDG DIF (Data Import Framework).

        End of the note.

    2. Define replication model (replication of business partners) under Start of the navigation path General Settings Next navigation step Data Replication Next navigation step Define Custom Settings for Data Replication Next navigation step Define Replication Models End of the navigation path

      1. Using New Entries, define a new replication model and enter a description.

      2. Mark the line and choose Assign Outbound Implementation. Create a new entry and enter the following values:

        • Outb. Impl.: 986_1 (Outbound Impl. for MDG BP via ALE)

        • Communication Channel: Replication via IDoc

        • Filter time: 2 (filter after change analysis)

      3. Mark the line and choose Assign Target System for Repl. Model/Outb.Impl. Create a new entry and enter the business system name for the receiving system created in the step before.

      4. Choose Assign Outbound Parameter. Create a new entry, enter the following values, and save.

        • Outb. Parameter: PACK_SIZE_BULK

        • Outb. Parameter value: 100 (example value)

      5. Return to the Define Replication Model view. Optionally, you can also add an expiration time for the log.

      6. Choose Save to save your entries.

      7. Mark the newly created replication model, and choose Activate.

        For more information, see Master Data Governance under Start of the navigation path General Settings Next navigation step Data Replication Next navigation step Define Custom Settings for Data Replication Next navigation step Define Replication Models End of the navigation path.

      8. Define filter criteria.

        In case different business partners are sent to receiver systems do the following:

        1. Select your replication model and choose Create.

        2. Enter filter values to determine which business partners shall be distributed, or which won’t, for example, due to number range settings for business partner creation.

          Run transaction DRFF or in SAP NetWeaver Portal or SAP NetWeaver Business Client, choose Start of the navigation path Data Exchange Next navigation step Data Replication Next navigation step Define Filter Criteria End of the navigation path.

  6. Enable monitoring of IDoc posting (ALE Audit)

    1. In the hub system: Run transaction BD64 to maintain a distribution model and define the direction MDG client to MDG hub.

      For more information about distribution models, see Distribution Model.

    2. Open transaction WE20 and navigate to the partner profile for the client system.

    3. Enter the following inbound parameters without changing further data:

      • Message type: ALEAUD

      • Process code: AUD2

    4. Replicate the distribution model to the target system using transaction BD64.

    5. In the client system: To generate a partner profile open transaction SALE and choose Start of the navigation path System Monitoring Next navigation step IDoc Confirmation in Receiving System (ALE Audit) Next navigation step Distribution Model for ALE Audit End of the navigation path. Then select Start of the navigation path Environment Next navigation step Generate Partner Profiles End of the navigation path.

    6. Open transaction WE20, navigate to the partner profile and enter the outbound parameter ALEAUD.

    7. To configure the replication of audit documents open the transaction SALE and choose Start of the navigation path System Monitoring Next navigation step IDoc Confirmation in Receiving System (ALE Audit) Next navigation step Confirmation of Audit Data Next navigation step Define Variant End of the navigation path.

      You can schedule the report RBDSTATE as a background job to run on a regular base.