Preparing Systems for Employee Data Migration and Replication from SAP S/4HANA to Employee Central

You're familiar with the role administration tools in the SAP S∕4HANA system.

The following template roles are available for the migration of employee master data to Employee Central:

Employee Master Data Migration from ERP to EC - Business User(SAP_HR_ECPAO_MIG_EE_PROCESSING).

This role is meant for a business user of type B (System User). It authorizes the user to carry out tasks such as the following:

• Extract employee data and migrate it to Employee Central.

• Schedule background jobs of the employee extraction report.

• Update the old key mapping table with manually migrated employee data through a CSV file.

• Determination of managers and organizational management data

• Analyze the inventory of the migrated employee data.

• Delete the inventory details from the inventory tables.

• Use the application log to analyze errors.

1. Go to the Role Maintenance (PFCG) transaction in your SAP S∕4HANA system.
2. Set up the business user.
   1. Copy the template role SAP_HR_ECPAO_MIG_EE_PROCESSING to the customer namespace.
   2. Set up permissions for the copied role to suit your specific requirements.
   3. Assign the copied roles to the user who migrates employee master data from SAP ERP to Employee Central.

This is what happens when you initially extract the data:

• Effective-dated templates:

  For effective-dated templates, if the earliest transfer date is after the hire or rehire date of an employee, the employee's data is extracted starting with the earliest transfer date. (This is also true for Non-Recurring Payments.) The following situations might occur:

  • The employee is active on the earliest transfer date: In this case, the data is extracted starting with the earliest transfer date for all effective-dated templates and Non-Recurring Payments.

  • The employee is terminated or retired on the earliest transfer date and hired or rehired later: In this case, the data is extracted starting with the hire or rehire date for all effective-dated templates and Non-Recurring Payments.

  • The employee is terminated or retired on the earliest transfer date and isn't rehired: In this case, no data is extracted for all effective-dated templates and Non-Recurring Payments.

• Non-effective dated templates

  • When an employee is hired in the past/present:

    For all other noneffective dated templates, when the employee is hired in the past or present, data is extracted starting with the later of the two dates. That is, either the current date or the earliest transfer date. If the earliest transfer date is after the date on which you run the data extraction program (the earliest transfer date is in the future), then the earliest transfer date is used for data extraction. If the earliest transfer date is before, then the date on which you run the data extraction program is used instead.

  • When an employee is hired in the future:

    For all other noneffective dated templates when the employee is hired in the future, the hire date is used for data extraction.

  • For Employment Termination, the last terminated data record for an employee is extracted. This is independent of the earliest transfer date or the date on which you run the data extraction program.

  • For Global Assignment, the last record of the employee's Details on Global Assignment(0710) infotype is extracted. This is independent of the earliest transfer date or the date on which you run the data extraction program. If the earliest transfer date is between the start and end date of the host assignment, the Job Information record is extracted for the host assignment. The PSEUDO_ADDGA event reason is used for the Add Global Assignment event.

• If the earliest transfer date is greater than the future cutoff date, then the earliest transfer date is considered during the data extraction.