Skip to Content
Author's profile photo Rishabh Dubey

Cloud Data Source – Integration

About this document:

Recently we used the Cloud Data Source to upload sales information from ERP for analytic purposes. This guide includes the key configuration required in C4C, NW PI, and ERP.  This guide assumes you know NW PI.  It provides screenshots of all the major steps


Step 1 : Design the Cloud data source for “ZTEST01”

Step 2 : Download the WSDL

  1. Administrator –>  Communication Arrangement –> Select the scenario.

Step 3. Generate Interface for the Analytics Upload :

  1. Upload the Analytic WSDL of step 2 in PI ESR.

    2. Create the Data Type, Message Type, and Service Interface for the ERP ABAP proxy.

         This is a synchronous ABAP proxy.

Data Type Request :

Data Type Response:

Message Type Request:

Message Type Response:


Service Interface : Proxy is generated over this Interface : OS_ERPInfocube_Request


  1. Operation Mapping :

XSLT mapping which will convert the xml to csv format accepted by cloud

Integration Scenario

Step 4 : Generate

ABAP Proxy


Step 5: Build ABAP report to send the data to C4C

Call to ABAP proxy in report

Test the scenario via ABAP report

Execute the report that will make a call to ABAP Proxy and response message from C4C back will be sent to the ERP system.


Request Message sent via SOAP to the C4C:

Response Message from the C4C:

SOAP UI Integration

I have used SOAP UI tool as well to test the integration to check, if I can upload the data using web service.

  1. Download Analytics WSDL from the C4C.
  2. Create project and upload the WSDL.
  3. Upload the client certificate of C4C in SOAP UI.
  4. Test the scenario

Assigned Tags

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

      Great blog, thanks!!

      Author's profile photo Former Member
      Former Member

      Hi Rishabh,

      Great Document and its really helpful......

      Many Thanks,


      Author's profile photo Rishabh Dubey
      Rishabh Dubey
      Blog Post Author

      Thanks for the appreciation !! 🙂 I think this will keep me running.

      Author's profile photo Former Member
      Former Member

      Hi Rishabh,

      nice blog. Would be useful insert also a screenshot of the request data type on PI-C4C side. I know there's a screenshot of the request message after mapping but it's very little and it's difficult to read content.

      Many Thanks,


      Author's profile photo Rishabh Dubey
      Rishabh Dubey
      Blog Post Author

      Hi Francesco,

      Thanks for the comment. Once I am back to my system, will upload the screen-shot of the AnalyticsUpload WSDL. I suppose that's what you meant ??



      Author's profile photo Tim Chang
      Tim Chang

      Great to see this blog.

      I'm still looking for a way in the webservice to change the delimiter from ":". in the <Data> payload

      Have you come across this issue ?

      Author's profile photo Rishabh Dubey
      Rishabh Dubey
      Blog Post Author

      Hi Tim,

      Thanks for the comment.

      Sorry Tim, I have not tried the delimiter ":". Anyways which character encoding are you using ??

      Author's profile photo Tim Chang
      Tim Chang

      I meant to say the webservice requires one to use the semi-colon (;).  I like to see how to change that to use another character as a better delimiter, but I don't seem to see this anywhere.

      Author's profile photo Ritesh Nasikkar
      Ritesh Nasikkar

      HI Rishabh/Tim,

      We have HCI middleware and we do not have PI middleware, please let us know how we can achieve this scenario. Our C4C is integrated to SAP ECC through HCI middleware and we have requirement to bring Sales order LIS info structure from ECC to C4C like S503 you r using in your above blog.

      Please let us know at the earliest.



      Author's profile photo Thierry Crifasi
      Thierry Crifasi

      Hey Ritesh, have you managed to apply the same principle with HCI? We have a similar requirement and architecture.