This lesson focuses on the essential configuration steps in SAP S/4HANA to activate product replication. These steps are:
- Set up the Data Replication Framework
- Set up the Consumer Proxy for the Outbound Web Service
- Enable automatic replication
Objective
This lesson focuses on the essential configuration steps in SAP S/4HANA to activate product replication. These steps are:
The Data Replication Framework in SAP S/4HANA handles distributing data from SAP S/4HANA to other systems. Configuring it for product replication requires two mandatory steps:
The following video shows how to set up the business system and replication model in SAP S/4HANA. The empty stub of the Business System and the Replication Model were created as general preparation steps earlier. If you haven’t done so yet, simply choose the New Entries button at the top of the corresponding step instead of editing the existing entry.
The Data Replication Framework can be configured using transaction DRFIMG. The two relevant configuration activities involve a special user interface with a tree structure on the left and different kinds of tables on the right. To navigate to the next level in the tree, you must first select a row in the table on the right. Then, you'll see the details of that table row based on the selected tree node.
To create new table entries in the right view, select New Entries from the menu bar. Some of those settings must be transported. Therefore, a transport request dialog might appear.
Define Technical Settings for Business Systems
The following settings were applied in the demo:
This entry should already exist. Otherwise, create it and name it exactly as your SAP Sales and Service Cloud Version 2 system ID.

Define Replication Model
The following settings were applied in the demo:
This entry should already exist. If it does not, create it and give it a name of your choice.

After adding the listed entries, activate the Replication Model by choosing the Activate button in the upper right corner above the Define Replication Model table.

Unlike SAP ERP/ECC, where products were replicated as Material Master (MATMAS) IDocs, they are nowadays sent via SOAP web service messages in SAP S/4HANA. The terms Material and Product are used interchangeably in this context.
To enable the outbound web service to send products, the so-called Consumer Proxy must be configured. The consumer proxy can be compared to the Outbound Configuration of SAP Sales and Service Cloud Version 2 or the outbound part of a Communication Arrangement in version 1.
The configuration can be carried out using the SOA Manager and consists of details such as the endpoint, authentication details, protocol information, etc.
The following video demonstrates how to configure the consumer proxy.
You can set up the consumer proxy using transaction SOAMANAGER → Web Service Configuration. Look for the following object:
If the list of logical ports already has entries with one marked as default, the system is currently using this consumer proxy to send products to another system. In this case, you need to create Service Groups to enable the consumer proxy to send products to multiple endpoints. The setup of service groups is explained for business partners. In this lesson, we assume that the list of logical ports is empty.
Create a new logical port for this Consumer Proxy using a Manual Configuration with the following details.
Note
The step order and names in the wizard vary depending on whether you are creating or editing a configuration.
You can choose the name and description freely as long as the SOA manager considers the values valid. You may mark the logical port as default during the initial configuration step or after finishing the wizard.
In this step, you need to provide the authentication details. The demo uses User ID / Password along with the Client ID and Client Secret from the SAP BTP service key created earlier. If you have set up a valid client certificate in your SAP S/4HANA system using transaction STRUST, you can use it by selecting X.509 SSL Client Certificate and choosing the trust store where you uploaded it (for example, DEFAULT - SSL Client (Standard)).
Remember: Using client certificates is the recommended method!
The following graphic shows a screenshot of these two options.
HTTP Settings / Transport Settings:
In this step, you need to provide the endpoint URL of the deployed integration flow from Cloud Integration. The rest of the parameters can usually remain unchanged.


Remember to set the port as the default if you didn’t do so in the first step.
To distribute newly created or modified products, you must ensure that the Business Transaction Event (BTE) is enabled for the corresponding application.
Open transaction BF11 and verify that the application MDGM (MDG Material) is active. Changing this setting is transport-relevant.

You can verify the impact by editing a product with transaction MM02 and checking the message monitor using transaction SRT_MONI. You will learn more about monitoring messages in the troubleshooting and monitoring unit later in this course.