Mapping Fields and Values for Employee Data

Value mapping means that Employee Central field values are mapped to values of SAP S∕4HANA fields.

Example

Employee Central uses the value F, SAP S∕4HANA uses the value 1 for the Female gender code. The values have the same meaning, but they aren't identical. Therefore, they must be mapped so that Employee Central can read the gender code that is transferred from SAP S∕4HANA.

The data extraction programs use the value mappings when extracting data. They replace the SAP S∕4HANA keys by the corresponding Employee Central keys, if a value mapping is defined for the corresponding field mapping. Value mappings are assigned to field mappings in the Primary Mapping and Secondary Mapping views of the field mapping in the Define Field Mapping for Employee Data Customizing step (view cluster VC_ECPAO_MAP).

There are standard value mappings provided by SAP. Standard value mappings are provided for values that can't be configured in the SAP S∕4HANA system and in Employee Central and therefore always stay the same.

Example:

Language codes can't be configured. The Employee Central language code English always corresponds to the language code EN in the SAP S∕4HANA system. Therefore, a standard value mapping is provided for language codes.

However, if you want to map values that can be configured in the SAP S∕4HANA system and in Employee Central, you must define custom value mappings.

Example:

Let's say you want to map event reasons from the Job History entity in Employee Central to action types from the Actions (0000) infotype in SAP S∕4HANA. So you define, for example, a custom value mapping that maps the Hire and Termination event reasons from Employee Central to the SAP S∕4HANA action types Hiring and Leaving.

Since no country-specific standard value mappings are available, you also need to define custom value mappings if you need to map country-specific values.

Example:

Pay scale areas are country specific. If you need a pay scale area mapping, you define it using the suitable ISO code. You could, for example, map the Employee Central pay scale area BR SP BR-Sao Paulo (BRSP) to the SC pay scale area from the SAP S∕4HANA system using the BR ISO code.

Note

After copying the new value mapping entries, don’t save the entries immediately, but press the page down to see all the entries. You must choose the page down until you see the last set of entries. Once you see the last set of entries, you can save all the newly created entries.

Understand the process for replication of picklist data from Employee Central.

The process for replication of picklist data from Employee Central has steps in three systems interacting with each other: Your Employee Central system, the cloud-based middleware, and SAP SuccessFactors Employee Central.

1. The query program ECPAO_IMPORT_PICKLIST (Picklist writer report based on Generic OData Service Call) in the SAP S∕4HANA system calls the outbound Web service getGenericDataReplicationQuery_Out. It also updates the query information and administration of the picklist query table with the relevant status information.

2. The outbound Web service sends the query to the cloud integration middleware and the corresponding Web service proxy class (consumer) for the OData API is called.

3. The middleware requests the corresponding data from Employee Central using OData APIs.

4. The middleware calls the inbound Web service GenericDataReplicationRequest in the SAP S∕4HANA system to send the data it has received from Employee Central in packages to SAP S∕4HANA.

5. The cloud integration middleware sends first sends the Start Notification indicating that response packages are subsequently sent.

6. The cloud integration middleware sends the Base64 encoded messages based on the OData API response that it receives. It sends the messages to the SAP S∕4HANA system as response packages in an asynchronous way using the inbound webservice.

7. The corresponding Web service proxy class (provider) is called. The response data is written into the staging area, and it also updates the entries in the response package database table.

8. The cloud integration middleware sends a final notification message to SAP S∕4HANA system once the last package is transferred which includes the parameter TotalNumberOfResponsePackages, containing the total number of response packages. The system compares the number of entries in the response packages with this parameter and decides whether to wait further or not.

9. Once all the response packages are collected, it processes the entries in the staging area, and deserializes it. Then it triggers the processing of the picklist update logic, thereby updating the picklist-specific database tables.

10. Creates SLG1 logs once the processing logic is completed and whether the update process resulted in success or failures.

11. It clears the staging area and response package database tables if there was a successful run.

12. If there were failures, the corresponding entries get deleted in the subsequent runs.

Make more settings for the Employee Central company that you've defined before in the Define Employee Data Settings for Employee Central Company Customizing activity (view V_ECPAO_CMPNY_EE).

1. Choose your Employee Central company ID.
2. Specify how the following Employee Central fields are to be mapped to SAP S∕4HANA:
   • user_id

     You can choose from the following mapping modes:

     • Standard mapping (PERNR): The user_id field is mapped to the Personnel Number (PERNR) field in SAP S∕4HANA.
     • BAdI mapping: If you have specific requirements, you create a Business Add-In (BAdI) implementation of the Mapping of User ID, Person ID, User Name, and Object ID (EX_ECPAO_EMP_USYID_PRN_UNM_MAP) BAdI to define the mapping.
   • person_id_external

     You can choose from the following mapping modes:

     • Standard mapping (CP): The person_id_external field is mapped to the central person (CP) in SAP S∕4HANA.
     • Infotype mapping (0709): The person_id_external field is mapped to the SAP S∕4HANA infotype Person ID (0709).
     • BAdI mapping (see above)
   • username

     You can choose from the following mapping modes:

     • Standard mapping (PERNR): The username field is mapped to the Personnel Number (PERNR) field in SAP S∕4HANA.
     • Infotype mapping (0105/001): The username field is mapped to the SAP S∕4HANA infotype Communication (0105), subtype System User Name (SY-UNAME) (0001).
     • BAdI mapping (see above)
   Note

   We always ensure that an employee gets a new personnel number while undergoing any new international transfer HR process.

   An employee may have been previously migrated using the Reuse Existing Employment for International Transfer setting. If so, we ensure that it continues to work as before (data of both personnel numbers are transferred to one employment in Employee Central) during the re-migration process.

To define custom Employee Central entities, carry out the following steps described for each template that you add.

In the Define Employee Central Templates for Additional Employee Data Entities Customizing activity (view V_ECPAO_ECTMPL), you can also see the default templates defined by SAP. If the default templates suit your requirements, there's no need to define any custom templates.

Procedure

1. Define the basic settings.
   1. Enter a unique template ID and a description. The ID has to be in the customer namespace, which means that it has to start with a number (0* - 9*). You can enter any description.
   2. Enter the entity name. You must use the exact name of the corresponding entity in Employee Central.

      To find out about the name for OData entities and generic objects, go to the Admin Center and choose the OData API Data Dictionary tool. For CSV data import templates, go to the Admin Center and choose the Import Employee Data tool.

   3. If you want to be able to assign your Employee Central entity to several transformation templates, select the Multiple Use checkbox.
   4. Specify if the Employee Central entity is effective dated.
      Note

      If you define an earliest transfer date for a transformation template group in the Define Field Mapping for Employee Data Customizing step, this date influences effective-dated and noneffective dated templates in different ways.

   5. If your template refers to a generic object in Employee Central, select the Is Generic Object in EC checkbox.
   6. If your template must inherit the metadata that you upload for another Employee Central entity, specify the template that is to be used as the metadata basis.
      Note

      If you make an entry in this field for an Employee Central entity, you can't import metadata for this template. You can only import metadata for the Employee Central entity that you've entered, meaning the template from which the metadata is to be inherited.

      Example

      The Dependent Biographical Information template inherits metadata from the Biographical Information template. This means it uses the same data model comprising fields such as date-of-birth, country-of-birth, or place-of-birth. You must import the metadata for the Biographical Information template only and can then reuse it for the Dependent Biographical Information template. You can't import metadata for the Dependent Biographical Information template.

   7. If your template refers to a generic object in Employee Central, make an entry in the Object ID Field in EC field. Here, you enter the name of the field that contains the external code of the generic object in Employee Central and to which the employee ID from SAP S∕4HANA is to be transferred.

      The field must have the User data type assigned in Employee Central so that the employee ID information from SAP S∕4HANA can be transferred to this field. Which ID is transferred depends on the mapping that you have defined in the Define Employee Central Instance Customizing step. In the standard mapping, the personnel number (PERNR) is used as the employee ID.

   8. For the SAP delivered templates, the start date field is already maintained. For the templates that you want to be defined, specify the Employee Central field (such as effectiveStartDate) in which the start date is stored for the corresponding entity and which is to be mapped to the Start Date (BEGDA field in SAP S∕4HANA system.

      For standard effective dated templates if the start date is specified, then the start date would be considered as a standard field. For standard MDF templates and custom MDF templates, the start date is not considered as a standard field even if it is maintained for a template.

      CSV & WS Template	IS_MDF	Standard Field (start date)	Standard Field (end date)
      Standard EE Templates		X	X
      Standard EE MDF Templates	X
      Custom EE Templates	X
      Standard OM Templates		X	X
      Standard OM MDF Templates	X	X
      Custom OM Templates	X

   9. For the SAP delivered templates, the end date field is already maintained. For the templates that you want to be defined, specify the Employee Central field (such as endDate) in which the end date is stored for the corresponding entity and which is to be mapped to the END Date (ENDDA field in SAP S∕4HANA system.

      For standard effective dated templates if the end date is specified, then the end date would be considered as a standard field. For standard MDF templates and custom MDF templates, end date is not considered as a standard field even if it is defined for a template.

      Note

      If the start and end date fields are configured in the field mapping table, then they are considered for the template configuration. If they are not defined in field mapping, it is read from the templates table.

2. Define the settings for data replication from SAP S∕4HANA to Employee Central.
   1. Enter a unique sequence number.

      The sequence in which the Employee Central entities delivered by SAP are transferred from SAP S∕4HANA to Employee Central is defined by SAP. You can't change this sequence. If you define your own template, we recommend using a sequence number that is higher than the numbers assigned to the Employee Central entities that are delivered by SAP.

   2. If the entity has a parent entity in Employee Central, enter the ID of the parent EC entity in the ID of Dependent EC Template column. PaymentInformationV3, for example, is entered in the ID of Dependent EC Template column of PaymentInformationDetailV3.
   3. If your template refers to a country/region-specific entity in Employee Central, specify the local version. If you'd create an Employee Central entity for the PerGlobalInfoUSA template entity, for example, you would specify the 10 (USA) country version.
   4. The settings in the Deletion Supported section are only available for Employee Central templates that are defined by SAP in the SAP namespace. You can't make any entries in the following fields:

      • The Deletion Permitted flag specifies that data deletion can be replicated for the Employee Central template from SAP S∕4HANA to Employee Central.

      • The HRIS Element ID is used by the Compound Delete or SFOData.HrisCompoundDeletion template when replicating the deletion of data from SAP S∕4HANA to Employee Central. The HRIS element ID is only needed for Employee Central templates that support the replication of data deletion to Employee Central.

3. Define infotype-specific settings.
   1. Specify the SAP S∕4HANA infotype that is required for your Employee Central template to be able to use it for a proper field mapping. The infotype you specify in this field is used by the SAP S∕4HANA system to check if the necessary field mapping is defined.

      Example

      The Personal Data (0002) infotype is required for the Personal Information entity in Employee Central. You can't transfer any data from SAP S∕4HANA to this entity if you haven't defined a mapping for any of the infotype fields.

   2. Only for Employee Central entities defined by SAP: An infotype can be specified that requires a special mapping (such as the Date Specifications (0041) infotype).
   3. If you need a special processing for the Employee Central entity, specify the processing mode you need. The processing mode refers to the infotype that you enter in the next step. The following processing modes are available:

      • Repetitive Structure Mapping

      • Object Identification Mapping

      • Only for Employee Central entities defined by SAP: Time Constraint 3 Mapping

   4. Enter the SAP S∕4HANA infotype for which a special processing is needed.
   5. If you've selected the Object Identification Mapping processing mode, specify the object identification (OBJID) field for which a unique key must be generated.
   6. If you've selected the Repetitive Structure Mapping processing mode, specify a structure that contains the fields for which you want to use the repetitive mapping.

An Employee Central entity represents an entity from Employee Central, such as a CSV data import template, an OData entity, or a generic object (also known as MDF entity). You only need to define custom Employee Central entities if you want to transfer data from SAP S∕4HANA to an Employee Central entity for which SAP hasn't provided a default template.

• Employee Central and SAP S/4HANA use value mapping to align field values (such as gender codes, language codes, or event reasons) for accurate data integration, with both standard and custom mappings supported.
• Picklist data is replicated from Employee Central to SAP S/4HANA using OData APIs, middleware, and web services, with robust logging and error handling to ensure reliable updates.
• Employee data fields like user_id and person_id_external can be mapped using standard, infotype, or BAdI methods, allowing for tailored integration between SAP S/4HANA and Employee Central.
• Organizations can define custom Employee Central templates for additional data entities, specifying effective dating, infotype dependencies, inheritance of metadata, and country-specific requirements.
• Template configurations manage start/end dates, processing modes, and replication sequence, ensuring orderly and accurate transfer of employee data between SAP S/4HANA and Employee Central.