Skip to Content
Technical Articles
Author's profile photo Vijay Vegesana


This blog post contains complete overview of Integration iFlow scenarios from Cloud for Customer to S/4 HANA On-Premise and Vice versa,

Systems Involved

SAP S/4HANA 1909  || SAP Cloud Platform Integration 1911 || SAP Cloud Connector ||

SAP Cloud for Customer 2002

Recommended Prerequisites:

S/4 HANA Version                    : S/4 HANA 1909 ||  Cloud for Customer Version     : 2002

Scope of Integration Scenarios:

  • Replicate Materials from S/4HANA to Cloud for Customer
  • Replicate Business Partners from S/4HANA to Cloud for Customer
  • Request External Pricing during from S/4HANA during creation of Quotation/Sales Order in Cloud for Customer
  • Submit for External Document from cloud for customer which in turns creates either sales quotation or sales order based on the document type received
  • Replicate Sales Orders from S/4HANA to Cloud for Customer


Let’s consider two scenarios in detailed from the above which can be followed to the other scenarios as well.

Scenario I :

  • Replicate Materials from S/4 HANA System

Scenario II:

  • Submit for External Document from cloud for customer which in turns creates either Sales quotation or sales order based on the document type received

For Scenario II, please refer the link:

Scenario I : Replicate Materials from S/4 HANA System

Source System : SAP S/4 HANA                    Target System  : SAP Cloud for Customer


Step 1: Make sure, Cloud Connector is reachable

Step 2: In Cloud Platform Integration, Identify the right iFlow to deploy

  • Login to CPI
  • Navigate to Package => SAP Cloud for Customer Integration with SAP S/4 HANA

  • Navigate to Artifact => Replicate Material from SAP Business Suite

Step 3: In S/4 HANA system, create the outbound configuration from SOAMANAGER for respective SOAP Service


Step 4: In S/4 HANA, make sure your outbound service ping is successful

Step 5: In Cloud for Customer, Create Communication Arrangement for the respective artifact

Note: If it is for the very first time, maintain communication systems as well

Step 6: In Cloud Platform Integration, deploy the iFlow by maintaining right sender and receiver details

As mentioned in Step 2, For the artifact “Replicate Material from Business Suite” we need to maintain Sender and Receiver details as shown below

Step 7: Maintain Replication Models

Transaction: DRFIMG

Refer below link

Step 8: In S/4 HANA, Execute Data Replication transaction and pass required Material Numbers that needs to be replicated in S/4 HANA system

Transaction : DRFOUT

Step 9: Once the Material is successfully replicate you will see below Success Message

Success Messages in S/4 HANA

Success message in Cloud Platform Integration ( Overview => Monitor Message Processing )

Success messages in Cloud for Customer ( Administrator => Webservice Monitoring )


Step 10: The Material has been successfully replicated in Cloud for Customer


Hope these above screenshots/steps helps to cover standard integration scenarios from S/4HANA On-Premise to C4C.

In next blog post, we will discuss the steps on Scenario II which covers integration scenarios steps from C4C to S/4HANA On-Premise.

For Part II, please refer below link:

Please feel free to add your comments for any clarifications/inputs.


Vijay Vegesana

Assigned Tags

      You must be Logged on to comment or reply to a post.
      Author's profile photo David Nguyen
      David Nguyen

      Great blog Vijay! Thank you for sharing.


      Author's profile photo Sven Kelemen
      Sven Kelemen

      Hi Vijay,

      ** UPDATE ** solved by downgrading Software Component Version C4CS4_IC 100 to SP 14
      ** Ignore unless interested 🙂

      As part of system conversion from ECC to S/4 we are implementing new web service-based integration between S/4 and C4C over on-prem PI. New message version <ns0:MaterialMassReplicationRequest xmlns:ns0=”“> has new attribute set <Material PlantPartyListCompleteTransmissionIndicator=”true” and <PlantParty> Elements.

      Those elements are creating errors in C4C processing: “XSLT exception at offset 2225 , XPath ns0:MaterialMassReplicationRequest(1)MaterialMassReplicationRequest(2)Material(2)PlantPart System expected the end of the element ‘PlantParty’ “.

      Unfortunately message mapping S4_C4C_MaterialReplicationRequest_v1 is not visible in our system with all XI CONTENT S4CORE up to 104 SP2. When opening mentioned message mapping the following error occurs “Source message Message Type: ProductMDMBulkReplicateRequestMessage does not exist in software component version S4CORE 105 Check whether software component version S4CORE 105 is in the Enterprise Services Repository. Import this or a newer version if necessary.“

      As of this moment XI CONTENT S4CORE 105 is not released for download.

      I’m searching for a way to turn off “PlantPartyListCompleteTransmissionIndicator” when sending from S/4 or how to set C4C to accept it.

      Thanks for sharing!

      Author's profile photo Former Member
      Former Member

      Hi Vijay Vegesana

      Great blog! Is it worth an update already?