Replicating Organizational Data from SAP S∕4HANA to Employee Central

Using this program, you can import entries and delete entries that you have imported for a specific Employee Central instance and template.

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.

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.

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.

In the Define Employee Central Entities for Additional Organizational Data Entities Customizing activity (view V_ECPAO_ECTMPL_O) 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.

To define custom Employee Central entities carry out the steps described below for each entity that you add.

1. Define the basic settings.
   1. Enter a unique entity 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 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 and Export Data tool.

   3. Specify the organizational object type from Employee Central, such as Business Unit or Job Classification.
   4. Depending on the type of Employee Central entity for which you use the template, select the communication channel (CSV File-Based Transfer or Web Service Transfer).
   5. If you want to be able to assign your Employee Central template to several transformation templates, select the Multiple Use checkbox.
   6. Specify if the Employee Central entity is effective dated.
2. Define the standard Employee Central field IDs.
   1. Specify the name of the field that contains the external code of the generic object in Employee Central and to which the organizational object I from SAP S∕4HANA is to be transferred.
   2. 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.

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

   3. 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.

      For standard effective dated templates if the end date is specified, then the end date would be considered as a standard field. For custom MDF templates and standard MDF templates, end date would not be considered as a standard field. End date is now not a mandatory field and you will be receiving a warning message when you do not mention the end date.

      Standard EC fields can be left blank while replicating the data to ERP when the dependent entity is maintained.

3. Define the Parent Child configuration.
   1. Enter the upsert sequence number. This number defines the sequence in which the data for different entities are transferred between the ERP system and SAP SuccessFactors Employee Central (EC).
   2. In the Dependent Entity field, select the Employee Central entity that corresponds to the parent object of the composite child object.

      If the parent entity is a standard delivered SAP entity, then only the upsert sequence of the child entity has to be entered which can be any number. But if the parent entity is also a custom template, then you need to ensure that the upsert sequence of parent is lower than that of the child entity.

      The EC Org. Obj.Type value should be same as the parent/dependent entity. In case the child entity is migrated to EC, the parent entity should also be included in the extraction process.

      Example: To map cost distribution, you need to create a custom composite child object with parent as position and then map the Infotype 1018 value.

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.

1. 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.

2. 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.

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.

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.

1. Go the view VC_ECPAO_MAP_OM.
2. Choose the transformation template group for which you want to map the table infotype.
3. Create a transformation template for the transformation template group corresponding to the custom OM entity.
4. 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.