Defining Organizational Data Settings

Objective

After completing this lesson, you will be able to define organizational data-related settings for your Employee Central company.

Custom Definition of Employee Central Entities for Organizational Data Entities

An Employee Central entity represents an entity from Employee Central, such as a CSV data import template 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.

Context

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.

The graphic displays a screenshot of the details of and Employee Central Entity for Org. Data

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

Procedure

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

Summary

Custom Employee Central entities need to be defined only if you want to transfer data from SAP S/4HANA to Employee Central entities that do not have SAP-provided default templates.
Effective dating fields (start and end dates) have specific mapping rules; end date is not mandatory and missing it will trigger a warning message.
Set up parent-child configurations by assigning upsert sequence numbers and mapping dependent entities, ensuring the parent’s sequence number is lower than the child’s for custom templates, and maintaining consistent object types between parent and child entities.

Go to Course