Set Up Data Replication Framework Using ALE (Without DRF)
The following steps are the minimal steps for a test cycle, assuming the basic customizing for ALE has been completed:
- Verify Logical Systems (SALE→Basic Settings→Logical Systems).
- Check Communication (SALE→Communication→Create RFC Connections).
- Maintain Distribution Model (BD64, choose message type MATMAS).
- Create Partner Profile (BD82, select, maintain, and generate):
Verify settings (WE20, Partner Type is LS, and message type MATMAS must appear).
- Distribute Model view to receiving system:
Run transaction SALE→Modeling and Implementing Business Processes→Maintain Distribution Model and Distribute Views.
- Create partner profile (receiving client):
- BD82, select the distributed model, enter the sender system as the "partner system", and enter the ALE-User. The remaining values are the default parameters. Execute.
- Check that the correct process code is being used in the details for the inbound parameter message types and in Inbound Options, check that the parameter Process Code is MATM.
- Repeat this procedure for the message type CLFMAS.
Replicating Data Options
In MDG 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 on ALE, see Customizing under Application Server→IDoc Interface/Application Link Enabling (ALE)→SAP Business Workflow.
For more details on the individual steps, refer to the MDG-M setup and configuration guide.
In the Configuration activity Define Technical Settings for Business Systems, SAP recommends that you select the check-box 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.
Customizing Steps for ALE

The figure, Customizing Steps for ALE, is an overview of the most important ALE customizing steps. Refer to the ALE documentation for more details.
The following steps are the minimal steps for a test cycle, assuming the basic customizing for DRF and ALE have been completed. You find more details in the generic learning map for MDG.
Set Up Data Replication Framework Using ALE (with DRF):
- Use transaction DRFIMG to check if the outbound parameter PACK_SIZE_BULK is available.
- Use transaction DRFIMG to check if the filter objects F_MAT1 - 6 are defined.
- Use transaction DRFIMG to check if the outbound implementation I_MAT has been defined.
- Define the technical settings for the business system again using DRFIMG.
- Create the replication model and assign it to the outbound implementation.
- Save and activate the replication model.
You can use ALE and DRF together. You can also use SOA and IDoc-based replication with different outbound implementations, but you can connect to any (logical) target system only using one dedicated communication channel.
In Master Data Governance for Material, the replication of material master data from the MDG Hub to connected client systems can be scheduled, triggered, and monitored using the Data Replication Framework (DRF) in concert with the ALE.
For more details on the individual steps, see the MDG-M setup and configuration guide.
For more general information on DRF, refer also to the generic MDG learning map.
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.
Replicating Material with DRF Using Engineering Change Numbers (ECN)
Material Replication with ECN Numbers
| Material and Classification without an Engineering Change Number (ECN) | Material and Classification Including an Engineering Change Number (ECN) | |
|---|---|---|
| Initialization | One MATMAS (and CLFMAS) IDoc per material of replication model (TA DRFF). Set Material CPs to processed. | Always take the latest ECN release. |
| Changes | One MATMAS (and CLFMAS) IDoc per material of replication model that was changed since the last replication. Set Material CPs to processed. | Always take the latest ECN release |
| Manual | One MATMAS (and CLFmas) IDoc per material according to manual filter criteria. Do not set Material CPs to processed. | Specify one ECN to replicate with (needs to be done in "Manual Replication Filter Criteria"). Otherwise, take the latest release. |
| Manual from Search UI | One MATMAS (and CLFmas) IDoc per material according to manual filter criteria. Do not set Material CPs to processed. Check DRF: Transfer Materials | Specify one ECN to replicate with (needs to be done in "Manual Replication Filter Criteria"). Otherwise, take the latest release. |
| Triggered by CR WF | Not applicable. Primarily for test efforts. | Not applicable. (Option: Take the latest release.) |