Ansicht
Dokumentation

DRF_005 - Define Replication Models

In this Customizing activity, you define replication models and specify the outbound implementations that are used for each replication model. You also verify that the data replication framework can use the replication models you have created by running a report.

• You must use outbound implementations (your own or those supplied by SAP) in combination with appropriate service operations (your own or those supplied by SAP) and available filter objects (your own or those supplied by SAP).

• The outbound implementations you want to use exist.

• The outbound parameters you want to use exist.

Complete the following tasks:

1. Define a replication model and enter a description of the appropriate semantic meaning.
2. Specify the receiver systems of the replication model.
3. Assign the outbound implementations that you require for the replication model, and specify the parameters for the assigned outbound implementations.

If you have assigned outbound parameters to an outbound implementation in Customizing for Cross-Application Components under Processes and Tools for Enterprise Applications -> Master Data Governance -> General Settings -> Data Replication -> Enhance Default Settings for Outbound Implementations -> Define Outbound Implementations, you can get the system to fill the Outbound Parameters table in this activity based on the assignment in the outbound implementation definition.

To do this, choose the Get Default Settings pushbutton. For more information about the outbound parameters that SAP delivers, see the documentation in Customizing for Cross-Application Components under Processes and Tools for Enterprise Applications -> Master Data Governance -> General Settings -> Data Replication -> Enhance Default Settings for Outbound Implementations -> Define Outbound Parameters.

Only the outbound implementations assigned here are subsequently available for the replication model when you execute data replication on the SAP Easy Access screen under Cross-Application Components -> Processes and Tools for Enterprise Applications -> Master Data Governance -> Data Replication -> Execute Data Replication.

1. Optionally, define the languages that you want to take into account for language-dependent texts in the outbound implementations.

When you replicate data using a replication model, the outbound messages may contain texts or descriptions in multiple languages. If you do not want to transfer all texts in every maintained language, you can restrict the languages that are relevant for data replication to a particular replication model. If you do not assign any languages to a replication model, the system transfers texts and descriptions in all available languages. If you assign one or more languages to a replication model, the system transfers texts only in those languages.

Note that if the relevant texts are not available in all selected languages, only the available texts are transferred. If no text is available and the element in the message is mandatory, the system inserts an error message into the log and the message is not transferred for semantic reasons. The system ignores elements in optional message elements. You can alter this default behavior using a Business Add-In (BAdI). For more information, see Customizing for Cross-Application Components under Processes and Tools for Enterprise Applications -> Master Data Governance -> General Settings -> Data Replication -> Business Add-Ins (BAdIs) -> BAdI: Definition of Language-Dependent Texts.

Note that if you make settings in a test system and transfer them to a production system, you must check in the production system that the settings for the replication model (in particular the receiver system entry) are correct and if necessary adjust them.

1. Check the readiness of a replication model . Proceed as follows:
1. In the Define Replication Modelsview, select the replication models you want to check. If you select no entries, all replication models are checked.
2. Click the Check Replication Readiness button.
3. A report is run. Correct any errors.
4. After this report has been run for one or more selected entries, a status will appear in the Ready for Replication field. Only replication models with a status of Ready for Replication are available in transaction DRFOUT.





rdisp/max_wprun_time - Maximum work process run time   BAL_S_LOG - Application Log: Log header data  
This documentation is copyright by SAP AG.

Length: 5395 Date: 20240523 Time: 161252     sap01-206 ( 108 ms )