Symptom
- The integrated landscape setup within the environment is multi system for example SAP S/4HANA Cloud, System A and System C.
- The flow of data in this landscape is intended to be as follows: System A <-> SAP S/4HANA Cloud <-> System C.
- Data is replicated to SAP S/4HANA Cloud from the leading system (System A), and following the successful inbound replication into SAP S/4HANA Cloud there is no automatically triggered follow on outbound message to System C.
- No outbound message is triggered to System C following the successful replication to SAP S/4HANA Cloud from System A.
- Alternately, after migrating business partners, that is "Customer" or "Supplier" master data using the following migration objects and the communication arrangements for business partner integration" (SAP_COM_0008) is not triggered from SAP S/4HANA Cloud to system A or C.
- Customer (SIF_CUSTOMER_2)
- Supplier (SIF_VENDOR_2)
- Customer - extend existing record by new org levels (SIF_CUST_EXT_2)
- Supplier - extend existing record by new org levels (SIF_VEND_EXT_2).
Environment
SAP S/4HANA Cloud
Reproducing the Issue
Scenario 1 - Integration Service for example BP SOAP
- Bidirectional business partner integration between System A and S/4HANA Cloud has been configured with SAP_COM_0008.
- Bidirectional business partner integration has been configured with SAP_COM_0008 between SAP S/4HANA Cloud and System C.
- Direct outbound has been set in SAP_COM_0008 for the integration between SAP S/4HANA Cloud and System C, this means that when data is created or changed, it will be immediately replicated into the target system.
- When replicating data between System A and SAP S/4HANA Cloud the data flow is successful, however no outbound message is triggered to System C.
Scenario 2 - Migration Cockpit
- Migrate business partner master data into the system using the SAP S/4HANA Cloud Migration Cockpit
- The communication arrangement "Business Partner, Customer and Supplier Integration SAP_COM_0008" is not triggered automatically to send out the new BP master data records.
Cause
- For the integration scenario, the business partner SOAP service (SAP_COM_0008) inbound doesn't trigger further replication of Master data to the connected system to prevent an infinite loop of data replication.
- The replication or communication arrangement trigger is disabled during migration since it would cause performance issues and might lead to a heavy load.
Resolution
- The recommended way to configure such a scenario are as follows:
System A <-> SAP S/4HANA Cloud
System A <-> System C - If you still wish the data flow to be from System A -> SAP S/4HANA Cloud-> System C, you may use the following SAP S/4HANA Cloud apps
- These apps can also be used to send out the data after they are created via the SAP S/4HANA Cloud migration cockpit.
See Also
Keywords
SAP S/4HANA Cloud, S4_PC, S4_1C, X4BC, S4HC, S/4HC, Data Replication Framework, DRF, Migration Cockpit, Migrate your data, Communication Arrangement, SAP_COM_0008
, KBA , LO-MD-BP , Business Partners , LO-MD-BP-ODT , OData Service for Business Partner , LO-MD-BP-WS , Web Service for Business Partner , LO-MD-BP-MIG , Business Partner Migration , LO-MD-BP-ID , IDocs for Customer/Supplier (DEBMAS/CREMAS) , How To
Product
SAP S/4HANA Cloud Public Edition all versions ; SAP S/4HANA Cloud all versions