Skip to Content

ID Mapping for registered products and installation points in C4C – ERP integration


This documents provides some details about how id mapping works for

  • ERP equipments and C4C registered products
  • ERP functional locations and C4C installation points

with the standard ERP integration with C4C.

The reason to write this document was to give some guidance to a customer project. The project starts with a custom integration for S/4HANA Enterprise equipments and functional locations to C4C and with a later shift to the standard integration as soon as this integration is available for S/4HANA Enterprise as well.

To ensure a smooth migration the most essential part of the custom integration is to do the id mapping right. Otherwise you may get duplicates in C4C after migrating to the standard content. Therefore here the explanation how it currently is done for ERP and will be done for S/4HANA Enterprise in future.

ERP equipments and C4C registered products

Here you see how the ERP equipment id is passed in to Cloud for Customer with the asynchronous inbound Registered Product Service payload.


The InstallationPointIDTypeCode field has to be set to 451 to state that the id is an ERP equipment id. The InstallationPointID field then contains the ERP equipment id.

The id mapping functionality in C4C then stores the mapping between the ERP equipment id and the C4C registered product id.

You find the id mapping in the administrator workcenter.


Here you see the ID mapping entry corresponding to the above payload.


If no id mapping record is found for the incoming ERP equipment id, a new registered product is created in C4C. Otherwise the existing registerd product – 164 in this case – is updated.

ERP functional locations and C4C installation points

For ERP functional locations the situation is a little little different. This is due to the data model in ERP. The id you see in the ERP UI may not be the technical identifier but an external id that is not even stable. This is due to the special functional location feature that you can define an edit mask for the functional location id that models the functional location hierarchy.

In the C4C asynchronouns inbound service payload you see one more id.


The first is the technical identifier from ERP. This time the InstallationPointIDTypeCode is 450 to state that this is an ERP functional location id. The InstallationPointID contains the technical ERP identifier. The AlternativeLabel contains the external ERP functional location id that is shown on the ERP UI.

This is stored as a data attribute in the C4C installation point and is shown in the C4C UI.


The id mapping in C4C for this example looks like this. Here the technical ERP id is used.


You must be Logged on to comment or reply to a post.
  • Hi Hermann ,

    Thanks a lot for sharing the document.  

    We have been trying to consume the web service[C4C inbound Registered Product Service which created under communication arrangement] from SAP ECC as well as from SOAP UI, but unfortunately not able to create Registered Product and also not able to see any related log information in C4C web service monitoring.

    It would be great if you can provide the code how to consume this particular web service. Your help will be appreciated.


    Srikanth P.

    • Hi Srikanth,

      as you don't see anything in the web service monitoring in C4C looks like the communication of the message to C4C failed. This could have plenty of reasons:

      Logon issue, wrong protocol, ...

      I would assume you see some error messages in SOAP UI. Do they give any indication what the issue could be?


      • Hi Hermann,

        Thanks for response.

        I am using SOAP UI tool to test the RP web service  and below is my request and I got the result “Web service processing error; more details in the web service error log on provider side”.

        But I can’t see any log on C4C system in Web Service Message Monitoring.

        Could you please share if you have any sample request to create Register Product.


        Srikanth P.

        • Hi Srikanth,

          in your snippet I e.g. don't see a message header with sender and receiver. What I would suggest: We also have an installation point outbound. I would enable the communication arrangement for the installation point outbound and create a payload by creating/updating an installation point. Then I would use this payload as your starting point: Switch sender and receiver and change some other fields and start with this. I think you have better chances then compared to a fully hand-crafted payload.