Show TOC

Background documentationSet Up Data Replication

 

For Master Data Governance for Material you have two options for replicating data from the MDG hub to the connected systems and clients:

  • Data replication using Application Link Enabling (ALE)

  • Data replication using Application Link Enabling (ALE) with the Data Replication Framework

For more information, see in Customizing under Start of the navigation path Application Server Next navigation step IDoc Interface / Application Link Enabling (ALE) Next navigation step SAP Business Workflow End of the navigation path.

Set Up Data Replication Using ALE

The following process describes briefly the minimal settings required for the two main message types MATMAS and CLFMAS.

  1. Verify logical systems

    Run transaction SALE and choose Start of the navigation path Basic Settings Next navigation step Logical Systems End of the navigation path. Both clients (source and target) need to be defined as logical systems and need to be assigned to the relevant clients.

  2. Check communication

    Run transaction SALE and choose Start of the navigation path Communication Next navigation step Created RFC Connections End of the navigation path. The target partner system has to be defined here as an ABAP connection with a connection type of 3 and with same name as the target logical system. Perform a connection test.

  3. Maintain distribution model

    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 (Maintenance of Distribution Model).

    2. In change mode, create a new model.

      Choose the Create Model View pushbutton. Enter a short text and a technical name.

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

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

    5. Repeat points 3 and 4 for message type CLFMAS

  4. 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 Profiles).

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

    3. Enter the ALE-User (the default value is ALEREMOTE) and the following values, and execute.

      Field

      Value

      Version

      3

      PackSize

      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 type MATMAS/CLFMAS should appear.

  5. 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.

  6. Create partner profile (in receiving client).

    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.

    2. Select the distributed model.

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

      Field

      Value

      Version

      3

      PackSize

      100

      Output Mode

      Transfer IDoc immediately

      Inb. Parameters: Processing

      Trigger Immediately

      Note Note

      If the protocol contains the error Port could not be created this can be ignored.

      End of the note.

    4. Check that the correct process code is being used. To do this go to the details for the inbound parameter message types and in Inbound Options check that the parameter Process Code is MATM for message type MATMS and is CLFM for message type CLFMAS.

    You can test the distribution using transaction BD10. Verify the results in the receiving client using transaction BD87.

    Note Note

    In the Configuration activity Define Technical Settings for Business Systems SAP recommends that you select the checkbox Status System Filter for the Material business object. This ensures that if an object instance was previously sent to a target system, it continues to be sent in the future, independent of filter settings.

    End of the note.

Set Up Data Replication Using ALE with DRF

In Master Data Governance for Material the replication of material master data from MDG Hub to connected client systems can be scheduled, triggered, and monitored using the Data Replication Framework (DRF) in concert with the ALE.

Note Note

If you are using ALE and DRF together to replicate materials you can improve performance by deselecting the change pointers for the MATMAS message type. You can do this in the Activate Change Pointers for Message Types configuration activity. You should only do this if all your MDG systems are integrated using ALE and DRF together. If you use ALE without DRF in one or more connected systems do not disable the change pointers.

End of the note.

The following customizing is relevant for data replication:

  • ALE (See Set Up Data Replication Using ALE above)

  • Enterprise Search (See Set Up Search above)

  • Key Mapping (See Key Mapping below)

  • ALE Audit (See Customizing for ALE Audit below)

  • Data Replication Framework (DRF)

The following process outlines the steps required to perform the customizing for the last three points above.

Customizing for Data Replication Framework (DRF)

  1. Run transaction DRFIMG and navigate to Start of the navigation path Enhance Default Settings for Outbound Implementation Next navigation step Define Parameters End of the navigation path to check if the outbound parameter PACK_SIZE_BULK is available.

    The following information should be available for this parameter:

    Outbound Parameter

    Description

    Data Type

    Value Length

    PACK_SIZE_BULK

    Package Size for Bulk Messages

    Integer

    10

  2. Use transaction DRFIMG to check if the filter objects below have been defined. Select Start of the navigation path Enhance Default Settings for Outbound Implementation Next navigation step Define Filter Objects End of the navigation path to view the filter object definitions. Check that the main filter object, MDG_BS_MAT is available.

  3. Use transaction DRFIMG to check if the outbound implementation I_MAT has been defined. Select Start of the navigation path Enhance Default Settings for Outbound Implementation Next navigation step Define Outbound Implementations End of the navigation path.

    Choose Assign Segment Filter Objects and confirm that the following settings are made.

    Type

    Technical Name

    Description

    Segment Filter Object

    F_MAT1

    Plant segment of material

    Segment Filter Object

    F_MAT2

    Sales segment of material

    Segment Filter Object

    F_MAT3

    Storage segment of Material

    Segment Filter Object

    F_MAT4

    Tax class segment of material

    Segment Filter Object

    F_MAT5

    Valuation segment of material

    Segment Filter Object

    F_MAT6

    Class segment of material

  4. Define the technical settings for the business system.

    1. Enter transaction DRFIMG and navigate to Start of the navigation path 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.

    2. In the Business System field specify the receiver system. In the Logical System field enter the Logical System used for IDoc communication. In the RFC Destination field enter the RFC destination to be used for RFC communication with the receiver system.

    3. Select the entry and click on Define Bus. Systems, BOs.

    4. In the BO Type field enter the business object type 194. In the Description field, enter a descriptive text.

    5. Select the entry and double-click on Define Bus. Systems, BOs, Communication Channel. In the Communication Channel field enter the means you want to use to transmit data to the applications. In the Key Harm. field specify if you want your keys harmonized between the hub and the client systems.

  5. Create the replication model and assign it to the outbound implementation as follows:

    1. Enter transaction DRFIMG.

    2. Navigate to Start of the navigation path Data Replication Next navigation step Define Custom Settings for Data Replication Next navigation step Define Replication Models End of the navigation path.

    3. Select Define Replication Model and then select New Entries.

    4. Enter a replication model and a description. In the Log Days field, you may enter the number of days after which you want an Application Log to expire. In the Data Model field, enter MM.

    5. Select the newly defined replication model and choose Assign Outbound Implementation.

    6. Choose New Entries.

    7. Assign the outbound implementation I_MAT.

    8. Assign a target system for the outbound implementation I_MAT.

    9. Assign the outbound parameter PACK_SIZE_BULK to the outbound implementation I_MAT with the Outbound Parameter Value 5.

  6. Save and activate the replication model.

More Information

For more information on data replication see Using the Data Replication Framework https://scn.sap.com/docs/DOC-39574Information published on SAP site.