SAP C4C

SAP C4C – Best practices for maintaining translations for dropdown values

This blog portrays the potential explanations behind interpretations characterized in the tweaking exercises of SAP C4C not reflecting in the UI when client really signs in that particular language. Consequently, I have summed up the prescribed procedures of keeping up with interpretations in SAP C4C.

We should consider the case of Lead sources to figure out this blog.

Explore to Business Configuration –> Implementation projects –> Open Activity List.

SAP C4C
  • Look for the activity Leads. Snap and open something very similar.
  • Then open the sub-activity Sources.
Search for the activity Leads
  • Keep up with interpretation for one of the sources by tapping on Translate button at the top.
 Translate button
  • In the ensuing screen, select objective language, suppose French and afterward keep up with interpretation for one of the sources. For example I kept up with the interpretation as ABC.
ABC target Language
  • I now login to C4C in French language and check for the particular dropdown esteem in Source field Ahead of the pack fast make screen. Amazingly, I consider it to be DEF, while I have characterized equivalent to ABC in the past step.
ABC in the past step
  • Justification behind this is that there is a Language Variation made with target language as French and DEF was kept up with as the interpretation for referenced source dropdown esteem in something very similar.
DEF
  • Learning here is that notwithstanding keeping up with the interpretation in Tweaking, the one characterized in the Language Transformation comes first.
  • Alter the individual Language Transformation, eliminate the interpretation kept up with for the ideal dropdown worth and save the Language Variation.
Competitor euipment
  • Re-login with French language and allude to the separate dropdown esteem in source field in the speedy make screen of lead. The normal interpretation can now be seen.
Re-logining with French language

Taking into account the above clarification, kindly note underneath best practices while keeping up with interpretations in SAP C4C.

  1. Assuming that interpretations are to be kept up with for dropdown upsides of standard fields, first inclination ought to be given to the Decipher choice in the particular Tweaking movement.
  2. Assuming that interpretations are to be kept up with for dropdown upsides of custom KUT fields, first inclination ought to be given to keeping up with interpretations by means of Alter field choice in Transformation highlight.
Interpretations in SAP C4C
  1. If Decipher choice isn’t given by standard by SAP to any of the standard fields [For for example Areas adjusting activity], Language Transformation ought to be thought of.
  2. Interpretations for custom SDK fields must be kept up with through Cloud Application Studio.

Trust this makes a difference. Cheerful counseling!!!

You may be interested in:

SAP HANA CLOUD TRAINING

Is SAP part of ERP?

Process automation Blog Series

SAP UI: Transforming User Experiences in Business