Replicating of Organizational Objects from SAP SuccessFactors Employee Central to SAP S/4HANA

If you want the middleware to filter the replication of organizational objects for active data records, enable the MDF version history in the object definitions. Creating an inactive record for the object or changing an active record to inactive only triggers the replication of the object in question if the MDF version history is enabled. If inactive data records aren't replicated, this causes Employee Central and SAP S∕4HANA to be out of sync. Enabling the MDF version history is especially important for the Position object, because MDF version history is disabled by default in the Position object definition.

If you want to replicate both departments and divisions, make sure that the association from the Department to the Division object is created in the generic object definition of the Department object. If you want to replicate both divisions and business units, make sure that the association from the Division to the Business Unit object is created in the generic object definition of the Division object.

1. Sign in to SAP SuccessFactors Employee Central.
2. Go to the Admin Center and choose the Configure Object Definitions tool.
3. Select the object definitions of all objects that you want to replicate one by one and choose Take Action.
4. Set the MDF Version History in to Delete History or Complete History.
5. Add the following association in the Department object definition:

   Association to Division

   Name	Multiplicity	Destination Object	Type
   cust_toDivision	One To Many	Division	Valid When

6. Add the following association in the Division object definition:

   Association to Business Unit

   Name	Multiplicity	Destination Object	Type
   cust_toBusinessUnit	One To Many	Business Unit	Valid When

Ensure that you don't select the object itself as the parent object when you assign:

• a parent department to a department.
• a parent division to a division.
• a parent business unit to a business unit in Employee Central.

Selecting the object itself creates a cyclic dependency and causes the replication of the object in question to fail. The SAP S∕4HANA system raises the following error message in such a case: <Object type> <object ID>: The assigned parent object will cause a cyclic dependency.

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.

Sample content provides basic field mappings (such as external code, start date, end date, name, and description) for the default organizational objects (department, division, business unit, job classification, and position) and for the organizational unit hierarchy.

Sample content provides basic field mappings (such as external code, start date, end date, name, and description) for the default organizational objects (department, division, business unit, job classification, and position) and for the organizational unit hierarchy.

This sample content also contains a conditional mapping for vacant positions. You can use it for the following scenario: If a position is vacant, position relationships are replicated from Employee Central Position Management. Once the position is staffed, the position relationships are created based on Employee Central Job Information using the organizational assignment replication process.

This sample content provides basic field mappings (such as external code, start date, end date, name, and description) for the:

• Default organizational objects (department, division, business unit, job classification, and position).
• Organizational unit hierarchy.
• Position relations.
• Position matrix relations.

Relationships of positions to jobs, cost centers, organizational units, and manager positions are replicated from Employee Central Position Management. Note that automatic propagation of the org. information from Position Management to Job Information must be enabled in EC.

Prerequisites:

• If this sample content is used, the creation of position relationships from Employee Central Job Information by the organizational assignment replication process has to be prevented ("reduced organizational assignment").
• If you use configurable replication of organizational assignments, don’t configure the position relationships in the Customizing activities Define Relationship Mapping for Position or Define Job Relationship Mapping for Position.
• If you use the non-configurable approach to replicate organizational assignments, add the respective constants (such as the constant EC to ERP: Omit Pos.-Org Unit Rel. in Non-Config. OrgAssignm) in the Maintain Constant Values for Data Replication from EC Customizing activity.

PA/PD integration synchronizes organizational data, such as position, job, organizational unit, or cost center, between the Relationships (1001) infotype in Organizational Management (OM) and the Organizational Assignment (0001) infotype in Personnel Administration (PA).

The Relationships infotype stores the relationships between the employee and the position (P – S) and all other position relationships, such as position to organizational unit (S – O), position to job (S – C), or position to cost center (S – K), for Organizational Management.

The Organizational Assignment infotype stores the assigned position, job, organizational unit, and cost center of the employee for Personnel Administration.

The Relationships infotype is updated either by the replication of employee data (which includes employee organizational assignments) or by the replication of organizational objects from Employee Central.

The Organizational Assignment infotype is updated either by PA/PD integration or–if PA/PD integration isn’t enabled–by the replication of employee master data from Employee Central.

PA/PD integration can be enabled in the SAP S/4HANA system by setting the T77S0 switch PLOGI ORGA to ‘X.’

1. Go to Customizing for the Business Integration Builder and choose Data Replication from Employee Central → Organizational Objects → Field Mapping for Organizational Object Replication from Employee Central → Define Transformation Template Group for Organizational Data.
2. Create a transformation template group and select the sample content that you want to use for it.
3. Go to the next customizing activity, Define Field Mapping for Organizational Data.
4. Create transformation templates. You have two options:

   • You create transformation templates for all object types that you want to use in your template group and assign the corresponding Employee Central entity to each template.

   • You copy the sample content to have the transformation templates for the default objects created automatically (together with the corresponding primary and secondary mapping).

     After you've copied the sample content, choose Save to make the primary and secondary mappings show up in the next steps.

5. Copy the sample primary and secondary (conditional) mapping.

   • If you've created your transformation templates manually in the previous step, copy the sample content for each template.

   • If you've already copied the sample content in the previous step, you don't need to copy anything in addition.

6. Adapt the copied sample content to suit your requirements. You can, for example, delete mappings that you don't need, change the mapped field, or add new mappings.
7. Optional: If you want to use the mapping of the Status of Vacancy (STATUS) field, define value mapping details for the VACANCY_STATUS_WS value mapping entity. The value mapping entity itself is contained in the sample content we provide for value mapping, but the details need to be defined manually.

   Use the mapping of the Status of Vacancy field only if your integration approach depends on implementing the following scenario:

   • If a position is staffed (that is, it has an incumbent in Employee Central), the position relationships are created based on Employee Central Job Information using the organizational assignment replication process.

   • If a position is vacant (that is, it has the To Be Hired status in Employee Central), you replicate position relationships from Employee Central Position Management using the organizational object replication process.

   Hint

   We recommend that you don't use this "mixed" scenario. Instead, we recommend that you replicate all position relationships from Employee Central Position Management with the replication of organizational objects.

   Hint

   Don't use this "mixed" scenario if you've enabled replication of shared positions from Employee Central. The status of shared positions can't be automatically updated in Employee Central when an employee is assigned to the position. This results in time slices being transferred by organizational object replication and organizational assignment replication, thus overwriting each other.

The sample field and value mapping are also available in the form of an editable spreadsheet containing sheets for the different sample content versions. Download this file from SAP Help Portal, at https://help.sap.com/docs/SAP_SUCCESSFACTORS_EC_S4_HCM_INTEGRATION.

We provide sample content for this activity, which you can copy and adapt to your needs. To view the sample content, choose Display Sample Value Mapping in the customizing activity.

1. Go to Customizing for the Business Integration Builder and choose Data Replication from Employee Central → Basic Settings → Define Value Mapping → Define Value Mapping Entities.
2. Select your Employee Central instance.
3. Choose Copy Sample Value Mapping if you want to use the sample content.
4. Remove entries that you don't need and adjust the copied content if necessary.
5. Choose New Entries to create value mapping entities manually, either in addition or as an alternative to copying the sample content.
6. Enter an entity name and description.

   You use the name later when you assign the value mapping entity to the field mapping in the Define Field Mapping for Organizational Data customizing activity.

7. Choose the value mapping type:
   • Choose Organizational Object Keys from Mapping Table if you want to map a relationship to another organizational object.
   • Choose Cost Center Keys from Mapping Tables if you want to map a relationship to a cost center.
   • Choose a suitable type, depending on which type of value you want to map, to map SAP S∕4HANA field values to Employee Central field values.

     Example

     Choose Picklist - External Code to map picklist values that are stored as the external code of objects in Employee Central to the corresponding field values in SAP S∕4HANA.

8. Specify the type of the related object (for example, 03 for Business Unit) in the EC Object Type field if you use the Organizational Object Keys from Mapping Table value mapping type.
9. Go to the next step in Customizing, Define Value Mapping Entities, if you use a value mapping type that's different from Organizational Object Keys from Mapping Table or Cost Center Keys from Mapping Tables.
10. Select your value mapping entity.
11. Map SAP S∕4HANA keys to Employee Central keys.

You've created value mapping entities, which you can use in primary field mapping and in secondary (conditional) mapping when defining the field mapping for organizational objects.

You've created an Employee Central instance in SAP S∕4HANA.

You can create one template group if you want to replicate all object types together, or several template groups if you want to replicate the object types separately.

The transformation template group is the entity that you specify on the selection screen of the Create and Execute Organizational Object Replication Query (RH_SFIOM_ORG_OBJ_REPL_QUERY) program. From the template group, the program determines all information it must extract data from Employee Central fields and map it to SAP S∕4HANA fields.

The transformation template is the SAP S∕4HANA counterpart of the Employee Central entity. It groups fields from SAP S∕4HANA and mappings of these fields to Employee Central fields.

1. Go to Customizing for the Business Integration Builder and choose Data Replication from Employee Central → Organizational Objects → Field Mapping for Organizational Object Replication from Employee Central → Define Field Mapping for Organizational Data.
2. Select your transformation template group and choose Transformation Template.
3. Optional: If you want to have the transformation templates for the default Employee Central entities created automatically, choose Copy Sample Content.
4. Optional: To make the sample mappings show up in the Primary Mapping and Secondary Mapping views, choose Save.
5. Choose New Entries to create a transformation template manually.
6. Enter an ID and a name.

   Transformation templates aren't self-contained objects. They only exist within a transformation template group. We recommend that you use the same name for transformation templates created within different template groups if they refer to the same entity. For example, if you create two template groups that both have a transformation template for Department, use the same template ID (such as ERP_DEP) in both template groups.

7. To enable your transformation template, select Is Active.
8. Select the Employee Central entity that corresponds to the transformation template.

   Adding the Employee Central entity enables you to choose the Employee Central fields of the corresponding object type, which you've imported as metadata from Employee Central. You can map these fields to SAP S∕4HANA fields. If you create a transformation template for one of the default object types, assign the standard Employee Central entity provided for the corresponding object type. For all other transformation templates, use the custom Employee Central entity that you've created before.

   Use the same Employee Central entity (or rather the same transformation template to which you assigned the Employee Central entity) in only one transformation template group. If you use a transformation template and Employee Central entity in multiple template groups, queries of the Last Modified Query type run into an error. The error message is: "Query for EC instance <Employee Central instance>, EC entity <Employee Central entity> already sent for templ. grp <transformation template group>"

9. To populate the Communication Channel, Entity Name in EC, and Effective Dated fields, press Enter. These fields are automatically filled in with information that comes from the Employee Central entity you've selected.
10. Save your entries.
11. Choose New Entries again and repeat the same steps to create more transformation templates.

    Create a template for each object type that you want to include in the replication.

You've created the transformation template that you want to use for replication of a specific object type.

The SAP S∕4HANA system uses the field mappings that you define when processing the replicated data in the staging area and storing it in the infotypes.

We provide sample content that contains the most common mappings of organizational object fields. For example, a mapping of the department description from Employee Central to the Line With Length 79 (TLINE) field in the General Description (0001) subtype of the Description (1002) infotype of organizational units in SAP S∕4HANA.

1. Go to Customizing for the Business Integration Builder and choose Data Replication from Employee Central → Organizational Objects → Field Mapping for Organizational Object Replication from Employee Central → Define Field Mapping for Organizational Data.
2. Select your transformation template group and choose Transformation Template.
3. Select your transformation template and go to Primary Mapping.
4. Optional: If you want to use the sample content and haven't copied it yet when you created the transformation template, choose Copy Sample Content.
   Hint

   To check which mappings are available, choose Show Sample Primary Mapping first.

5. To create a field mapping manually, choose New Entries.
6. Select the Employee Central field that you want to map.

   You can choose from the fields provided by the Employee Central entity that's assigned to the transformation template.

7. Select the mapping mode Infotype Mapping.

   The other mapping modes aren't relevant for organizational object replication from Employee Central.

8. Select the SAP S∕4HANA infotype, the subtype if applicable, and the infotype field to be mapped.
9. If you want to use conditional mapping for a field, select the Employee Central field the conditional mapping is to be based on as the linking field. If you define a linking field, choose the Infotype Mapping mapping mode, but don't select any infotype, subtype, or infotype field.
10. Optional: Select a suitable value mapping entity.

    If you want to map the Employee Central field values to field values from SAP S∕4HANA, you need a value mapping entity. You also need a value mapping entity if you want to use the information stored in the key mapping table in SAP S∕4HANA for the mapping of relationships to other organizational objects.

As the next step, you can define a conditional mapping for your transformation template or format-specific Employee Central fields using value conversion. You can also define filters for your transformation template group.

When you've defined the field mapping and replicated organizational data based on this mapping, make sure that you trigger a full load each time you change the field mapping.