Configuring Replication of Language-Dependent Fields

Objective

After completing this lesson, you will be able to configure replication of language-dependent fields between Employee Central and SAP S∕4HANA.

Language-Dependent Fields

Configure the replication of texts (such as names or descriptions of organizational objects) between SAP S∕4HANA and Employee Central.

Prerequisites

The language pack for an Employee Central locale must be enabled in Provisioning so that you can transfer texts in the corresponding language.

Employee Central supports translations for position names, but not for position descriptions. Add a custom description field to the Position object definition in Employee Central if you want to replicate position descriptions for multiple languages.

Context

To enable replication of texts, you first map language-independent text fields. This mapping is used as a placeholder. Also, you map the locales you use in Employee Central to the corresponding SAP S∕4HANA languages. Based on this language mapping, the language-dependent field mappings are then automatically created and replace the placeholders when the data is extracted.

If you don't define at least a language mapping for the default locale, no language-dependent data can be transferred.

Let's say you try to replicate a new department from Employee Central to SAP S∕4HANA. This means that a new record of the Object (1000) infotype must be created in the SAP S∕4HANA system. The Object infotype needs a language. To determine the language to be used, the SAP S∕4HANA system reads the entries stored in the V_ECPAO_LOCALE. If there aren't any entries here, the system doesn't know which language to use for the infotype record. Therefore, the department can't be replicated. The corresponding replication request has the status Pending.

Results

Data transfer between Employee Central and SAP S∕4HANA automatically uses language-dependent field mappings instead of the placeholder mapping. There's no need to define a mapping for the language-dependent fields explicitly. In our example, the integration uses the following mappings.

Employee Central FieldMapping ModeSAP S∕4HANA InfotypeSAP S∕4HANA FieldSAP S∕4HANA Language
name_en_USInfotype MappingObject (1000)Object Name (STEXT)EN
name_de_DEInfotype MappingObject (1000)Object Name (STEXT)DE
name_es_ESInfotype MappingObject (1000)Object Name (STEXT)ES
name_fr_FRInfotype MappingObject (1000)Object Name (STEXT)FR
name_it_ITInfotype MappingObject (1000)Object Name (STEXT)IT
name_nl_NLInfotype MappingObject (1000)Object Name (STEXT)NL

Configure Replication of Language-Dependent Fields

Prerequisites

The language pack for an Employee Central locale must be enabled in Provisioning so that you can transfer texts in the corresponding language.

Employee Central supports translations for position names, but not for position descriptions. Add a custom description field to the Position object definition in Employee Central if you want to replicate position descriptions for multiple languages.

Context

To enable replication of texts, you first map language-independent text fields. This mapping is used as a placeholder. Also, you map the locales you use in Employee Central to the corresponding SAP S∕4HANA languages. Based on this language mapping, the language-dependent field mappings are then automatically created and replace the placeholders when the data is extracted.

If you don't define at least a language mapping for the default locale, no language-dependent data can be transferred.

Summary

  • The language pack for each Employee Central locale must be activated in Provisioning to allow text replication in the corresponding language.
  • Begin by mapping language-independent text fields as placeholders, then map Employee Central locales to SAP S/4HANA languages. This mapping enables the automatic creation of language-dependent field mappings, which replace the placeholders during data extraction.
  • Once configured, the system automatically applies language-dependent field mappings for data transfer (e.g., name_en_US → EN, name_de_DE → DE), without needing explicit mappings for each language-dependent field.