CRM and CX Blogs by SAP
Stay up-to-date on the latest developments and product news about intelligent customer experience and CRM technologies through blog posts from SAP experts.
Showing results for 
Search instead for 
Did you mean: 
Product and Topic Expert
Product and Topic Expert
In this blog we will touch upon how Text Collections are replicated between C4C and external systems(ERP,CRM,S/4 etc.).

In Cloud for Customer Text collections or Notes can be maintained in multiple objects for e.g. Sales Quote, Orders, Materials etc.

However, there are slight differences between the way notes are saved in C4C and on-premise systems.

In C4C, the notes are language independent, meaning user can save only one note per text collection field for any given document, however in On-Premise systems, you could have N number of notes per field based upon different languages. This would also mean that irrespective of which language users are logged in C4C, the notes are same.

And for integration scenarios, TextCollectionTextTypeCode is the one which determines where or which field the notes would be saved.

Considering all of these details, lets get into the details on how texts are actually replication between C4C and other systems.


1. Inbound Scenario(On-Premise to C4C)

  • In this scenario, as on-premise systems are capable of having notes in multiple languages, the inbound message would have multiple text notes.

  • There could be multiple text contents with same Textcollectiontypecode but different language code.

    • <TextCollection textListCompleteTransmissionIndicator="true">
      <ContentText languageCode="EN">Test Note</ContentText>
      <ContentText languageCode="DE">Test Hinweis</ContentText>
      <ContentText languageCode="FR">Note de test</ContentText>

  • As C4C is capable of having single language independent note, so only one of the incoming notes is saved.

  • To determine which one, we make use of Business Configuration activities, namely "Communication Language for Data Replication" and "Code List Mapping for Integration with External Applications and Solutions".

  • Maintain code list mappings for the typecode, 0001 as in our example for the datatype TextCollectionTextTypeCode.

  • Code list mappings for all Text type codes are maintained with local context 10296.

  • Now Communication Language maintained should match any of the incoming language codes.

  • Now when we have code list mappings and communication language maintained, C4C will decide which note to be saved.

  • Please do note, this particular note is still saved in C4C without any language associated.

  • These configurations are required only for integration purpose, the actual notes are still language independent in C4C.


2. Outbound Scenario(C4C to On-Premise)

  • Since C4C maintains single note per field, there would be only one text content in the payload.

  • And this text content would have Text Type based upon the code list mappings.

  • More importantly, here the language code would be picked from Fine Tuning activity "Communication Language for Data Replication".

  • This way, only a particular note is created/updated in On-Premise systems, other language notes would be untouched.


Additional Points to consider:

  • Inbound replications do not consider issues with respect to Text notes as hard errors and message would be processed.

  • If there are any issues/missing code list mappings or language codes, the message would still be processed, and text notes will be skipped from the document.

  • However in case of outbound replication, if there are any missing code list mapping or any issue with code list mappings for text type code, the outbound replication will be stopped with corresponding error.

  • This is so designed to prevent incorrect data flowing from C4C to ERP/CRM etc.

  • If your issue is still not resolved, then please raise an incident for SAP Support. Also, please send the following information in the incident:

    • Problem description

    • Steps to reproduce

    • Cloud for Customer Message ID

    • IDoc number from ERP/CRM.