Mapping Organizational Data Fields and Values

Objective

After completing this lesson, you will be able to map organizational data fields and values to support data replication between SAP S/4HANA and Employee Central.

Transformation Template Group and Templates for Organizational Data

To enable the data extraction programs to extract the correct SAP S∕4HANA information for the correct Employee Central fields, you must map SAP S∕4HANA fields to Employee Central fields.

To map fields, go to the Define Field Mapping for Organizational Data Customizing step, which has the VC_ECPAO_MAP_OM view cluster assigned. The configuration in this view cluster is carried out in the following steps:

Create at least one transformation template group. A template group bundles all field mappings that you want to use when running the data extraction program. This is the entity that you specify on the program selection screen. From the transformation template group, the data extraction program determines all information that it must extract data from SAP S∕4HANA fields and map it to Employee Central field IDs.
Create at least one transformation template for your transformation template group. A transformation template groups information from the SAP S∕4HANA system that belongs together logically. It is the SAP S∕4HANA counterpart of the Employee Central entity.
Define a primary mapping for each of your transformation templates. This means you choose Employee Central field IDs from the Employee Central entity assigned to the transformation template, and you map suitable SAP S∕4HANA fields to these Employee Central field IDs.

The Employee Central Instance ID and the Transformation Template Group are the main configuration elements of the Business Integration Builder.

Employee Central Instance ID

The Employee Central Instance ID represents in SAP S/4HANA the connected SAP SuccessFactors Employee Central Instance.

All BIB configurations are linked to one specified Employee Central instance, which includes the following:

EC Entities, that is imported EC meta data, to be mapped and replicated.
Value Mapping Entities (EC Picklists) which represent EC values to be mapped and replicated.

Transformation Template Group

The Transformation Template Group specifies the scope of data and configured mapping scenarios considered during the replication run. A Transformation Template Group is assigned to an EC Instance and consist of the following:

Field and value mapping specified in Transformation Templates. Transformation templates are based on metadata from EC represented by EC entities and imported EC picklist information represented by value mapping entities.
EC entities represent an entity of EC, such as a CSV data import template, an OData entity, or a generic object, also known as MDF entity.

If you want to map organizational units, consider that business units, divisions, and departments from Employee Central all map to organizational units in the SAP S∕4HANA system. Therefore, you must decide how to handle the organizational unit templates:

Either you decide which of these object types you want to use. For example, if you decide to always replicate organizational units to departments, only add a transformation template to your transformation template group if the template has the Department Employee Central entity assigned.
If you want to use all three templates in your transformation template group, implement the Validity Periods for Data Replication to EC(EX_ECPAO_EMP_VALIDITY_TAB) Business Add-In (BAdI). This add-in defines to which object in Employee Central each organizational unit is mapped.

The following sample transformation template groups are defined for the Employee Central company SBS_MODEL in the delivered sample Customizing:

SBS_OM_MODEL_CSV
This is an example of the replication of organizational data using the CSV File-Based Transfer communication channel.
SBS_OM_MODEL_WS
This is an example of the replication of organizational data using the Web Service Transfer communication channel.

You can copy the transformation template group to your Employee Central company and change the field mapping of the transformation templates to suit your requirements.

Create a Transformation Template Group and Templates

A template group bundles all field mappings that you want to use when transferring data from SAP S∕4HANA to Employee Central.

Screenshot of the Transformation Template Group. Details are explained in the following text.

The transformation template is the counterpart of the Employee Central entity. You can map fields from the transformation template to fields from the assigned Employee Central entity.

Screenshot of the Transformation Template. Details are explained in the following text.

ExerciseStart Exercise

Primary Field Mapping for Organizational Data

You can choose Employee Central fields from the Employee Central data model that you've uploaded to the SAP S∕4HANA system, and you map suitable SAP S∕4HANA fields to these Employee Central field IDs.

Context

To define a field mapping for each transformation template, go to the Primary Mapping view of the VC_ECPAO_MAP_OM view cluster.

There are predefined standard mappings, which are automatically added to the templates you use and aren't available for configuration in this Customizing activity.

How to Map Fields

Choose an Employee Central field from the assigned Employee Central template.
Make sure that you have imported the data model for this Employee Central template to the SAP S∕4HANA system using the metadata import program. Otherwise, no fields are available here.
Map each Employee Central field to an SAP S∕4HANA field using a suitable mapping mode:

When you select the mapping mode Infotype Mapping, you assign an infotype or subtype field in the primary mapping. You can use fields from Organizational Management infotypes for field mapping. For the mappings of text fields such as Object Name (STEXT), you define a language-independent mapping. The Use Language Mapping checkbox is selected for this kind of field mapping.
To make the language-dependent mapping work, you must also map Employee Central locales to SAP S∕4HANA languages.
When you select the mapping mode BAdI Mapping, you can use an implementation of the Mapping of EC and ERP Data for Data Replication to EC (EX_ECPAO_EMP_DATA_EXTRACT_OUT) BAdI to define the field mapping.
When you select the mapping mode Evaluation Path Mapping, you can map an Employee Central field ID to an evaluation path from SAP S∕4HANA.

Results

If the value from the SAP S∕4HANA field must be converted to an Employee Central value, enter the value mapping entity that you defined in the Define Value Mapping Entities customizing step. You can define the value mappings for this entity directly from here by choosing Define Value Mapping Entries.

You are now ready to use your field mapping when running the data extraction program.

Don't define a secondary field mapping for organizational data. The Organizational Data Extraction program doesn't replicate organizational data fields that have a secondary mapping.

Value Mapping Entities and Details for Organizational Data

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

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 view cluster. Field mappings are grouped together in a transformation template group. You enter the transformation template group on the selection screen to tell the extraction program which field mappings and which value mappings it must use.

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.

Note

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

Sample Value Mapping for Organizational Data

Use the sample value mapping entities SAP provides for organizational objects to easily create the value mappings you need, for example, for the relationships to other objects.

We provide sample value mapping entities for the default organizational objects (departments, divisions, business units, job classifications, and positions) and for the Status of Vacancy (STATUS) field of the Vacancy infotype (1007).

Note

If you choose Copy Sample Value Mapping, all entities that are available in the V_ECPAO_VALENT_S (S table) view are copied to the V_ECPAO_VALUENTY (C table) view in the Define Value Mapping Entities Customizing activity. This includes the value mapping entities for organizational data and employee data, and for both directions (replication from SAP S∕4HANA to Employee Central and replication from Employee Central to SAP S∕4HANA). If you only need some of the sample value mapping entities, choose Copy Sample Value Mapping and then remove all entities that you don't need from the V_ECPAO_VALUENTY view.

Once you've made entries in the V_ECPAO_VALUENTY view (either by copying or by entering them manually), you can no longer copy the sample value mapping entities. Either remove all entries from the V_ECPAO_VALUENTY view and copy again, or show the sample value mapping entities and use them as an example for making the entries manually.

If you want to replicate other organizational objects (including custom objects), you must define custom value mapping entities for them.

Map Organizational Data to Table Infotype

You want to map the table infotype in the view cluster to support the migration process.

Prerequisites

You must create a custom OM Entity in the V_ECAPO_ECTMPL_O view similar to the one, which is created in the EC instance.

Context

Table infotypes allow you to store the data in a tabular structure in one infotype record. All the OM infotypes, which have HRT table in addition to the HRP tables are table infotypes. You can map any table infotype in the configuration since this is common for both Organizational data migration and Organizational data replication. But in Organizational data migration, only table infotypes 1002 and 1018 are supported.

Go the view VC_ECPAO_MAP_OM.
Choose the transformation template group for which you want to map the table infotype.
Create a transformation template for the transformation template group corresponding to the custom OM entity.
In the Primary Mapping screen, choose the fields from the F4 help menu and then perform the mapping. All the fields from HRP and HRT table will be available for mapping.
You can migrate multiple cost distributions stored in the corresponding 1018 table infotype records for the parent object, as shown in the following example.

Screenshot of the position entries in the 1018 table.

Summary

Field mappings are organized into transformation template groups and templates in the VC_ECPAO_MAP_OM view cluster, which define how SAP S/4HANA fields correspond to Employee Central fields for data extraction and replication.
For each transformation template, you establish primary mappings by linking Employee Central field IDs to appropriate SAP S/4HANA fields using mapping modes like Infotype Mapping, BAdI Mapping, or Evaluation Path Mapping, ensuring correct data flow between systems.
Where field values differ between SAP S/4HANA and Employee Central, value mapping entities are defined to convert values accurately. SAP provides standard value mappings for non-configurable fields (e.g., language codes), while custom mappings must be created for configurable values or custom objects.
You must determine how business units, divisions, and departments from Employee Central are mapped to organizational units in SAP S/4HANA, either by selecting specific templates or using a BAdI for more complex scenarios.
Table infotypes allow storage of tabular data in one record, and you can map custom OM entities and table infotypes (supported for certain infotypes like 1002 and 1018) to facilitate both organizational data migration and replication processes.

Go to Course