Extracting and Transferring Organizational Data from SAP S/4HANA to Employee Central

Objective

After completing this lesson, you will be able to extract organizational data from SAP S/4HANA

Sequence of Data Extraction and Import Steps for Different Object Types

Data Transfer Recommendations

When replicating data from SAP S∕4HANA to Employee Central, make sure to follow this sequence.

Make sure that the Parent field is not a required field for positions and departments in the Employee Central metadata.

Make sure that the Multiple Use checkbox is selected for the Employee Central entities that you use for organizational data. This ensures that you can assign one Employee Central entity to several transformation templates. For more information, see the Replicating Employee Data from SAP S∕4HANA to Employee Central integration guide. You can find the most current version of this guide on the SAP Help Portal at http://help.sap.com/hr_ecintegration.

Screenshot showing the location of Multiple Use checkboxes in Employee Central.

Within the transformation template group that you use for organizational data extraction, create two transformation templates for each organizational object type, one that maps the corresponding Parent field and one that doesn't. Assign the same Employee Central entity to both transformation templates.

Procedure

  1. Replicate organizational units without their relationships. To do so:
    1. In the transformation template group that you use for organizational data extraction, select the Is Active checkbox for the transformation template that you use for mapping organizational unit fields to department fields and that does not map the Parent field. Deselect this checkbox for the other transformation template that you use for mapping organizational units (the one that contains the Parent field).
    2. Extract the data for your organizational units using the Organizational Data Extraction (ECPAO_OM_OBJECT_EXTRACTION) program. On the selection screen of the program, specify the transformation template group that you use for organizational data extraction. The Organizational Data Extraction program uses the transformation template that doesn't map the Parent field since you've set the Is Active checkbox for this transformation template. The other transformation template, which maps the Parent field, isn't used since this is not active.
    3. Import the extracted data into Employee Central. Departments are created without any parent associations.
  2. Replicate jobs (which correspond to job classifications in Employee Central) without their relationships. To do so, carry out the same steps as for organizational units, but use the transformation templates that map job fields from SAP S∕4HANA to job classification fields in Employee Central.
  3. Replicate positions without their relationships. To do so, carry out the same steps as for organizational units, but use the transformation templates that map position fields from SAP S∕4HANA to position fields in Employee Central.
  4. Replicate employee data.

    There's also a recommended sequence for importing the employee data entities into Employee Central. For more information about importing the employee data entities, see the Replicating Employee Data from SAP S∕4HANA to Employee Central integration guide. You can find the most current version of this guide on the SAP Help Portal at http://help.sap.com/hr_ecintegration.

  5. To replicate the organizational unit relationships, follow these steps:
    1. In the transformation template group that you use for organizational data extraction, select the Is Active checkbox for the transformation template that you use for mapping organizational unit fields to department fields and that maps the Parent field. Clear this checkbox for the other transformation template that you use for mapping organizational units (the one that doesn't contain the Parent field).
    2. Extract the data for your organizational units using the ORGANIZATIONAL DATA EXTRACTION (ECPAO_OM_OBJECT_EXTRACTION) program. On the selection screen of the program, specify the transformation template group that you use for organizational data extraction. The Organizational Data Extraction program uses the transformation template that maps the Parent field since you've set the Is Active checkbox for this transformation template. The other transformation template, which doesn't map the Parent field, isn't used because this is not active.
    3. Import the extracted data into Employee Central. Now the parent-child associations are created for the departments you have replicated in the first step.
  6. Replicate the job relationships. To do so, carry out the same steps as for organizational unit relationships, but use the transformation templates that map job fields from SAP S∕4HANA to job classification fields in Employee Central.
  7. Replicate the position relationships. To do so, carry out the same steps as for organizational unit relationships, but use the transformation templates that map position fields from SAP S∕4HANA to position fields in Employee Central.

Extract and Transfer Organizational Data without Relationships

Organizational Data Extraction in Multiple Steps

Here is how to extract the organizational data from the SAP S∕4HANA system to transfer it to Employee Central in multiple steps without having to change and transport the template group configuration.

Prerequisites

In order to do a step wise employee data migration using a single transformation template group, you should have already created a transformation template group using the view cluster VC_ECPAO_MAP_OM.

Context

When you are using the regular extraction process, you need to transport from configuration system to production system, which is time consuming. By using this multiple step migration, you avoid the transport from the configuration system to the production system.

When you are migrating the organizational data, you can first migrate the templates without any relationship to make sure that the objects first exist in Employee Central before the relationships are migrated. This will make sure that you are not migrating templates, which have a relationship with certain templates, where you are migrating the relationships without migrating the template.

For ex: If all departments without relationships are not migrated, then departments with relationships cannot be migrated.

Once the initial migration process is successful, you can then migrate the relationships to the existing templates (ex Job relationship, Position relationship etc.). Lastly you can execute delta replication via change pointers. .

Here you can use a single transformation template group (by creating different variant ID's for a single transformation template group) to cater for different scenarios without changing any configurations in the transformation template group.

Tip

You can create a single transformation template group with all the required transformation templates and enable it for delta replication.

Procedure

  1. Create the variant ID using the customizing activity: Define the Variant IDs for Data Migration (view V_ECPAO_VARIANT).
  2. Once you create the variant ID, you will have to add the transformation template to the variant ID using the customizing activity: Define the Transformation Templates for a Variant ID (view V_ECPAO_FO_UPS).
  3. Choose the variant ID when you run the organizational extraction report.

    You can also choose the variant ID when you run the job scheduler report.

Define Background Job to Replicate Organizational Data

Replicate All OM Objects with Relationships

Log in to track your progress & complete quizzes