9/3/2020

Set Up Data Replication

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 Application Server IDoc Interface / Application Link Enabling (ALE) SAP
Business Work ow .

Set Up Data Replication Using ALE

The following process describes the minimal settings required for the message types MATMAS, CLFMAS, DOLMAS, ECMREV, and
MATQM.

If you want to replicate change states or revsion levels using IDoc ECMREV, you must also activate the ALE change pointers using
transaction SALE. In transaction SALE navigate to IDoc Interface/Application Link Enabling (ALE) Modeling and Implementing
Business Processes Master Data Distribution Activate Change Pointers for Message Types or use transaction BD50.

. Verify logical systems

Run transaction SALE and choose Basic Settings Logical Systems . Both clients (source and target) need to be de ned
as logical systems and need to be assigned to the relevant clients.

. Check communication

Run transaction SALE and choose Communication Created RFC Connections . The target partner system has to be
de ned here as an ABAP connection with a connection type of 3 and with same name as the target logical system. Perform
a connection test.

. Use bgRFC

Run transaction SBGRFCCONF and on the tab De ne Inbound Destination choose Create New Inbound Destination.
Maintain the destination name and go to Add Queue Pre x. Enter MDG_ and choose Add. This pre x is mandatory. Choose
Save. Go to the Scheduler: Destination tab. Choose Create and Create Scheduler Settings for Inbound Destination.
Select the new destination and check the default setting. Choose Save.

. Maintain distribution model

a. Run transaction SALE (Display ALE Customizing) and choose Modeling and Implementing Business
Processes Maintain Distribution Model and Distribute Views . Alternatively, run transaction BD64 (Maintenance
of Distribution Model).

b. In change mode, create a new model.

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

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

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

e. Repeat points 3 and 4 for message type CLFMAS, DOLMAS, and ECMREV.

1/5
9/3/2020

f. For MATQM, choose the Add BAPI. Enter names for the logical source and destination systems and choose object
name MatInspectionControl and method SaveReplica.

g. Optional: Use the message type SERDAT to prevent errors during inbound processing such as posting MATQM before
MATMAS. With serialized message distribution, IDocs are created, sent, and posted in a speci c order. Set up
sending and receiving systems using transaction SALE in sender and target systems and choose Modeling and
Implementing Business Processes Master Data Distribution Serialization for Sending and Receiving Data . See
the customizing documentation for setup process.

. Create partner pro le.

a. Run transaction SALE and choose Modeling and Implementing Business Processes Partner Pro les Generate
Partner Pro les . Alternatively, run transaction BD82 (Generate Partner Pro les).

b. Select the newly created model and in the Partner System eld, enter the logical destination system.

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

d. To verify your settings, run transaction WE20 and from the Partner Pro les menu, choose Partner Type LS. Verify
that Partner type LS is the logical destination system.

e. In the detail screen, the chosen message types should appear.

f. Check and change the outbound parameters:

Message Type Receiver Port Package Size Basic Type

CLFMAS A000000021 100 CLFMAS02

DOLMAS A000000021 1 DOLMAS01

ECMREV A000000021 100 ECMREV01

MATMAS A000000021 100 MATMAS05

MATQM A000000021 1 MATQM01

SERDAT A000000021 100 SERDAT01

. Distribute model view to receiving system.

a. Run transaction SALE and choose Modeling and Implementing Business Processes Maintain Distribution Model
and Distribute Views . Alternatively, run transaction BD64.

b. Select the new model and choose Edit Model view Distribute .

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

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

. Create partner pro le (in receiving client).

2/5
9/3/2020

a. Run transaction SALE and choose Modeling and Implementing Business Processes Partner Pro les Generate
Partner Pro les . Alternatively, run transaction BD82.

b. Select the distributed model.

c. 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
If the protocol contains the error Port could not be created this can be ignored.

d. 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 as follows:

Message Type Process Type Processing by Function Module

CLFMAS CLFM Trigger by background program

DOLMAS DOLMAS Trigger by background program

ECMREV ECMR Trigger by background program

MATMAS MATM Trigger by background program

MATQM BAPI Trigger by background program

SERDAT SERD Trigger Immediately

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

 Note
In the Con guration activity De ne 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 lter settings.

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
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 con guration
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.

3/5
9/3/2020

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 (Optional) below)

Data Replication Framework (DRF)

The following process outlines the steps required to perform the customizing for the point above.

Customizing for Data Replication Framework (DRF)

. Run transaction DRFIMG and navigate to Enhance Default Settings for Outbound Implementation De ne Parameters 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

. Select the parameter and open the Outbound Parameter Value view. Check that the parameter value is 1000.

. Use transaction DRFIMG to check if the lter objects below have been de ned. Select Enhance Default Settings for
Outbound Implementation De ne Filter Objects to view the lter object de nitions. Check that the main lter object,
MDG_BS_MAT is available.

. Use transaction DRFIMG to check if the outbound implementations I_MAT and I_MAT_V2 have been de ned. Select
Enhance Default Settings for Outbound Implementation De ne Outbound Implementations .

Choose Assign Segment Filter Objects and con rm 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

. De ne the technical settings for the business system.

a. Enter transaction DRFIMG and navigate to De ne Custom Settings for Data Replication De ne Technical
Settings De ne Technical Settings for Business Systems .

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

4/5
9/3/2020

c. Select the entry and open the De ne Bus. Systems, BOs view.

d. In the BO Type eld enter the business object type 194. In the Output Mode eld Object-Dependent Default is the
default entry. You can optionally use, Direct Output, where changes are directly transferred to a target system.

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

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

a. Enter transaction DRFIMG.

b. Navigate to Data Replication De ne Custom Settings for Data Replication De ne Replication Models .

c. Select De ne Replication Model and then select New Entries.

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

e. Select the newly de ned replication model and choose Assign Outbound Implementation.

f. Choose New Entries.

g. Assign the outbound implementation I_MAT or I_MAT_V2 . I_MAT sends only MATMAS and CLFMAS messages;
I_MAT_V2 sends MATMAS, CLFMAS, DOLMAS, ECMREV, and MATQM messages.

h. Assign a target system for the outbound implementation.

i. Assign the outbound parameter PACK_SIZE_BULK to the outbound implementation with the Outbound Parameter
Value 1000.

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

5/5