Implementation Guide | PUBLIC

Document Version: 2H 2021 – 2022-04-28

Migrating Data from SAP S/4HANA On Premise

to Employee Central Using Infoporter
© 2022 SAP SE or an SAP affiliate company. All rights reserved.

THE BEST RUN

Content

1 Change History. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4

2 Overview of Data Migration from SAP S∕4HANA to Employee Central. . . . . . . . . . . . . . . . . . . . . 6

2.1 Target Group of This Document. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7
2.2 Terminology. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7
2.3 Sequence of Data Migration Steps. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10

3 Preparing the Systems for Data Migration to Employee Central. . . . . . . . . . . . . . . . . . . . . . . . 13

3.1 Defining the Migration Scope. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13
3.2 Preparing the SAP S∕4HANA System for Data Migration. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 14
3.3 Preparing Employee Central for Data Migration. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 17
Preparing Employee Central for Organizational Data Integration. . . . . . . . . . . . . . . . . . . . . . . . . 17
Preparing Employee Central for Employee Data Integration. . . . . . . . . . . . . . . . . . . . . . . . . . . . 18
Granting Permissions for Employee Data and Organizational Data Migration. . . . . . . . . . . . . . . . 19

4 Migrating Data from SAP S∕4HANA to Employee Central. . . . . . . . . . . . . . . . . . . . . . . . . . . . . .21

4.1 Sequence of Data Extraction and Import Steps for Different Object Types. . . . . . . . . . . . . . . . . . . . .21
4.2 Importing Organizational Data into Employee Central. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .24
4.3 Importing Employee Data into Employee Central. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 25
4.4 Migrating Foundation Objects to Employee Central. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 27
Migrating Work Schedules to Employee Central. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 27
Migrating Other Standard Foundation Objects to Employee Central. . . . . . . . . . . . . . . . . . . . . . 38
Migrating Custom Foundation Objects to Employee Central. . . . . . . . . . . . . . . . . . . . . . . . . . . . 42
Analyzing the Status of Migration of Foundation Object to Employee Central. . . . . . . . . . . . . . . . 43
4.5 Migrating Pay Calendar to Employee Central. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 44
Exporting Pay Calendar Information from ERP. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 45
Importing Pay Calendar Information to Employee Central. . . . . . . . . . . . . . . . . . . . . . . . . . . . . 46
4.6 Advantages of Web Service-Based Data Transfer for Migration. . . . . . . . . . . . . . . . . . . . . . . . . . . . 48
4.7 Migrating Employee Master Data from Third-Party Systems. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 49

5 HR Business Processes in Employee Data Migration. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 51

5.1 Employee Hired in SAP S∕4HANA. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 51
5.2 Employee Rehired in SAP S∕4HANA. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 53
5.3 Employee Transferred in SAP S∕4HANA. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 55
5.4 Employee in International Transfer . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .56
5.5 Employee Having Global Assignment in SAP S∕4HANA. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 58
5.6 Employee Having Concurrent Employment in SAP ERP HCM. . . . . . . . . . . . . . . . . . . . . . . . . . . . . 60
5.7 Employee Terminated in SAP S∕4HANA. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .60

Migrating Data from SAP S/4HANA On Premise to Employee Central Using Infoporter
2 PUBLIC Content
6 Starting Data Replication from Employee Central to the SAP S∕4HANA System. . . . . . . . . . . . 62

7 Validating the Migration. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 65

Migrating Data from SAP S/4HANA On Premise to Employee Central Using Infoporter
Content PUBLIC 3
1 Change History

Learn about changes to this guide in recent releases.

2H 2021/ PA_SE_IN SP32

Table 1: The following table summarizes changes to this guide for the SAP SuccessFactors 2H 2021 release.
Type of Change Description More Info

New Added information about the support of Migrating Foundation Objects to Em­
migration of Flextime Bandwidth ployee Central [page 27]
through Workschedule migration re­
port.

New Added information about the support of Migrating Custom Foundation Objects
navigational fields to send data to SAP to Employee Central [page 42]
SuccessFactors Employee Central

1H 2021/ PA_SE_IN SP31

Table 2: The following table summarizes changes to this guide for the SAP SuccessFactors 1H 2021 release.

What's New Description More Info

Updated information about the F4 help We now provide F4 help menu for all the -
menu for all the constants value in the constants value in the view
constants view V_ECPAO_CONSTANT. This help menu
will allow you to choose the allowed in­
put value for a constants value. This
makes sure that incorrect values are
not entered for a constants value.

Type of Change Description More Info

New You can now choose Logs or List View, Migrating Other Standard Foundation
which enables you to view the results Objects to Employee Central [page
via Application Logs or ALV display re­ 38]
spectively when you perform a test run.

New You can now choose the foundation ob­ Migrating Custom Foundation Objects
ject by country grouping and object id to Employee Central [page 42]
from the selection screen of the report
ECPAO_TRANSFER_FO_OBJ_TO_EC.

New You can now transfer work schedule Migrating Work Schedules to Employee
rules containing cross midnight flag. Central [page 27]

Migrating Data from SAP S/4HANA On Premise to Employee Central Using Infoporter
4 PUBLIC Change History
 Type of Change Description More Info

New A new BAdI has been added in the sys­ External Codes Generated for Work
tem to modify the external code from Schedule Objects in Employee Central
the ERP system for the work schedule [page 36]
rule.

New You now do not need to reformat the Migrating Pay Calendar to Employee
pay calander information file after the Central [page 44]
extraction process and before you im­
port the data to Employee Central.

2H 2020/ PA_SE_IN SP30

Table 3: The following table summarizes changes to this guide for the SAP SuccessFactors 2H 2020 release.

What's New Description More Info

Updated information about the F4 help We now provide F4 help menu for all the -
menu for all the constants value in the constants value in the view
constants view V_ECPAO_CONSTANT. This help menu
will allow you to choose the allowed in­
put value for a constants value. This
makes sure that incorrect values are
not entered for a constants value.

Migrating Data from SAP S/4HANA On Premise to Employee Central Using Infoporter
Change History PUBLIC 5
2 Overview of Data Migration from SAP
S∕4HANA to Employee Central

Learn how to help implement data migration from on-premise SAP S∕4HANA systems to SAP SuccessFactors
Employee Central using the Infoporter data migration tool.

The scenario we are describing here is the following: You set up a new Employee Central system and want to
migrate data from an existing SAP S∕4HANA system to Employee Central. After the migration, you switch from
using SAP S∕4HANA to using Employee Central as the system of record for the migrated data.

After executing all steps described here you will be able to migrate organizational data and employee data from
SAP S∕4HANA to Employee Central using Comma-Separated Values (CSV) files or web services. You can carry
out a one-time replication of data that refers to organizational units, jobs, and positions, including the
relationships between these objects, and of data that refers to employees from SAP S∕4HANA to Employee
Central, or you can also use the delta-enabled web service transfer mode. By using the delta-enabled web
service transfer mode, you can set up continuous migration of employee data. After the migration, you can
start replicating data from Employee Central to SAP S∕4HANA. You can work on the replicated data in Employee
Central and plan to use the SAP S∕4HANA system based on the Core Hybrid HCM or Side-by-Side HCM
deployment option.

 Note

Data migration from SAP S∕4HANA to Employee Central uses the Business Integration Builder, which is also
available for replicating data from SAP S∕4HANA to Employee Central when using the Side-by-Side HCM
deployment option. For more information about this deployment option, see the Integrating SAP ERP HCM
with Employee Central Using the Side-by-Side Deployment Option guide. Find the most current version of
this guide in SAP Help Portal at http://help.sap.com/hr_ecintegration.

 Caution

Usage of any integration software and content provided with the SAP Business Suite or SAP S∕4HANA
software and applicable to an integration between the SAP Business Suite or SAP S∕4HANA and SAP
SuccessFactors Employee Central is permitted only with SAP S∕4HANA and a valid, current contract for
SAP SuccessFactors Employee Central.

Some SAP Cloud Services are available for use with on-premise SAP S∕4HANA systems. Please contact the
SAP Cloud Support team for more information.

Target Group of This Document [page 7]

Take a look at the target groups this document is intended for.

Terminology [page 7]
Here's an overview of some terms used in this document, which might be unfamiliar to you.

Sequence of Data Migration Steps [page 10]

We recommend that you set up data migration from SAP S∕4HANA to Employee Central using this
sequence of steps.

Migrating Data from SAP S/4HANA On Premise to Employee Central Using Infoporter
6 PUBLIC Overview of Data Migration from SAP S∕4HANA to Employee Central
2.1 Target Group of This Document

Take a look at the target groups this document is intended for.

The following groups of people will benefit from reading this document:

● Implementation partners, consultants, and Product Support, for fast support of customers and
prospective customers
● Cloud operations
● SAP-certified administrators at customer site

Parent topic: Overview of Data Migration from SAP S∕4HANA to Employee Central [page 6]

Related Information

Terminology [page 7]
Sequence of Data Migration Steps [page 10]

2.2 Terminology

Here's an overview of some terms used in this document, which might be unfamiliar to you.

Table 4: Terminology Overview

Term Abbreviation Definition

Application Programming Interface API An interface technology for connecting

application systems with one another.

Business Add-In BAdI A technology used to adapt SAP soft­

ware to specific requirements. BAdIs
are used to create predefined enhance­
ment options in SAP S∕4HANA, which
can be implemented by partners and
customers.

Business Integration Builder BIB A generic framework used for the map­
ping between SAP ERP HCM and Em­
ployee Central data model which can be
used for transferring data between the
ERP and EC systems and vice versa.

Migrating Data from SAP S/4HANA On Premise to Employee Central Using Infoporter
Overview of Data Migration from SAP S∕4HANA to Employee Central PUBLIC 7
Term Abbreviation Definition

Central Person CP An object in the SAP S∕4HANA system

that links the employee to the business
partner, which means, to a party in
which a company has a business inter­
est.

Comma-Separated Values file CSV file A file that stores data, such as numbers
and text, in plain text. Each line of the
file is a data record. Each record con­
sists of one or more fields, separated by
commas.

effective dated – Effective-dated Employee Central fields

have a history associated with them
while non-effective dated fields do not
have a history. For example, compensa­
tion-specific fields are effective dated
while fields like Name and National ID
are not effective dated.

feature – An object in the SAP S∕4HANA system

that determines default values by
querying different personnel and data
structure fields.

Intermediate Document IDoc A format for electronic data inter­

change between systems.

personnel number PERNR The identifier of an employee in the SAP

S∕4HANA system.

system of record – The system in which an employee is

mastered, meaning, the system that is
the authoritative data source for the
employee's master data.

This is an overview of terminology changes we've made for the Business Integration Builder (BIB). Using BIB
you set up the SAP S∕4HANA system for organizational or employee data replication from Employee Central.

Table 5: Terminology Changes for Business Integration Builder

Old term New term

Long form Abbreviated form Long form Abbreviated form

Employee Central company EC company Employee Central instance EC instance

Employee Central company EC company ID Employee Central instance ID EC instance ID

ID

Migrating Data from SAP S/4HANA On Premise to Employee Central Using Infoporter
8 PUBLIC Overview of Data Migration from SAP S∕4HANA to Employee Central
 Old term New term

Long form Abbreviated form Long form Abbreviated form

Employee Central company EC company description Employee Central instance EC instance description
description description

Employee Central template EC template Employee Central entity EC entity

Employee Central template EC template ID Employee Central entity ID EC entity ID

ID

Employee Central template EC template description Employee Central entity de­ EC entity description
description scription

Employee Central template EC template name entity name in Employee entity name in EC
name Central

ERP picklist ID – Employee Central picklist ID EC picklist ID

Employee Central picklist ID EC picklist ID Employee Central picklist EC picklist name

name

template group – transformation template –

group

SAP ERP template ERP template transformation template –

Employee Central to SAP EC to ERP from Employee Central from EC

ERP

SAP ERP to Employee Cen­ ERP to EC to Employee Central to EC

tral

SAP ERP / SAP ERP HCM – Enterprise Resource Plan­ ERP system
ning system

Parent topic: Overview of Data Migration from SAP S∕4HANA to Employee Central [page 6]

Related Information

Target Group of This Document [page 7]

Sequence of Data Migration Steps [page 10]

Migrating Data from SAP S/4HANA On Premise to Employee Central Using Infoporter
Overview of Data Migration from SAP S∕4HANA to Employee Central PUBLIC 9
2.3 Sequence of Data Migration Steps

We recommend that you set up data migration from SAP S∕4HANA to Employee Central using this sequence of
steps.

1. Define the scope of your migration project.

For more information refer to section Defining the Migration Scope [page 13].
2. Check the technical prerequisites.
For more information, see the Replicating Employee Data from SAP S∕4HANA to Employee Central and
Replicating Organizational Data from SAP S∕4HANA to Employee Central integration guides. Find the most
current version of these guides in SAP Help Portal at http://help.sap.com/hr_ecintegration.
3. Prepare the SAP S∕4HANA system.
For more information refer to section Preparing the SAP S∕4HANA System for Data Migration [page 14].
4. Prepare the Employee Central system.
For more information see Preparing Employee Central for Organizational Data Integration [page 17] and
Preparing Employee Central for Employee Data Integration [page 18].
5. Carry out the actual data migration.
The data migration process runs as shown here:

The table below shows the process steps and the related sections in the corresponding guide.

Section in the integration

Step Substep Integration guide guide

Preparation Export data model from Replicating Employee Data Importing Metadata from
Employee Central from SAP S∕4HANA to Em­ Employee Central
ployee Central

Replicating Organizational Importing Metadata from

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

Import data model into the Replicating Employee Data Importing Metadata from
SAP S∕4HANA system from SAP S∕4HANA to Em­ Employee Central
ployee Central

Replicating Organizational Importing Metadata from

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

Migrating Data from SAP S/4HANA On Premise to Employee Central Using Infoporter
10 PUBLIC Overview of Data Migration from SAP S∕4HANA to Employee Central
 Section in the integration
Step Substep Integration guide guide

Mapping Define value mapping Replicating Employee Data Defining Value Mappings
from SAP SAP S∕4HANA to
Employee Central

Replicating Organizational Defining Value Mappings

Data from SAP S∕4HANA to
Employee Central

Define field mapping Replicating Employee Data Defining Field Mapping for
from SAP S∕4HANA to Em­ Employee Data
ployee Central

Replicating Organizational Defining Field Mapping for

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

Data extraction from SAP Use Web services or gener­ Replicating Employee Data Extracting Employee Data
S∕4HANA ate CSV files from SAP S∕4HANA to Em­
ployee Central

Replicating Organizational Extracting Organizational

Data from SAP S∕4HANA to Data
Employee Central

Update mapping table to Replicating Organizational Extracting Organizational

prepare the organizational Data from SAP S∕4HANA to Data (step 4)
data replication Employee Central

Data import into Employee Import CSV files Replicating Employee Data Importing Employee Data
Central from SAP S∕4HANA to Em­ into Employee Central
ployee Central
 Note
Not applicable if you Replicating Organizational Importing Organizational
use web service-based Data from SAP S∕4HANA to Data into Employee Central
data transfer. Employee Central

Preparation of employee Update employee key map­ Replicating Employee Data Updating the Employee Key
data replication from Em­ ping table from SAP S∕4HANA to Em­ Mapping Table
ployee Central to SAP ployee Central
S∕4HANA

6. Run the employee master data replication from Employee Central to the SAP S∕4HANA system.
For more information refer to section Starting Data Replication from Employee Central to the SAP
S∕4HANA System [page 62].
7. Validate your migration project.
For more information refer to section Validating the Migration [page 65].

Migrating Data from SAP S/4HANA On Premise to Employee Central Using Infoporter
Overview of Data Migration from SAP S∕4HANA to Employee Central PUBLIC 11
Parent topic: Overview of Data Migration from SAP S∕4HANA to Employee Central [page 6]

Related Information

Target Group of This Document [page 7]

Terminology [page 7]

Migrating Data from SAP S/4HANA On Premise to Employee Central Using Infoporter
12 PUBLIC Overview of Data Migration from SAP S∕4HANA to Employee Central
3 Preparing the Systems for Data Migration
to Employee Central

Learn more about what needs to be in place if you want to migrate data from SAP S∕4HANA to Employee
Central.

Defining the Migration Scope [page 13]

Clarify the scope of your migration project before you start the actual data migration.

Preparing the SAP S∕4HANA System for Data Migration [page 14]
Take a look at how to prepare your SAP S∕4HANA system for data migration to Employee Central.

Preparing Employee Central for Data Migration [page 17]

Here's what you need to do in Employee Central to prepare for data migration from SAP S∕4HANA.

3.1 Defining the Migration Scope

Clarify the scope of your migration project before you start the actual data migration.

To do so, ask yourself questions such as:

● Which data of which employees is to be migrated from SAP S∕4HANA to Employee Central?
● Is Organizational Management data to be migrated as well?
● Which Employee Central fields are to be mapped to which SAP S∕4HANA fields?
● Which Employee Central picklist entries are to be mapped to which SAP S∕4HANA value help entries?

Don't underestimate the effort needed for defining the scope. This task can easily take 30-40% of the time
that's planned for the complete migration project.

Parent topic: Preparing the Systems for Data Migration to Employee Central [page 13]

Related Information

Preparing the SAP S∕4HANA System for Data Migration [page 14]
Preparing Employee Central for Data Migration [page 17]

Migrating Data from SAP S/4HANA On Premise to Employee Central Using Infoporter
Preparing the Systems for Data Migration to Employee Central PUBLIC 13
3.2 Preparing the SAP S∕4HANA System for Data Migration

Take a look at how to prepare your SAP S∕4HANA system for data migration to Employee Central.

The cutover date defines when you will start using Employee Central as the system of record for the data
contained in the migration scope. Before the cutover date, SAP S∕4HANA is the system of record. You can
replicate employee master data to SAP S∕4HANA by using either of these two ways:

● Using the Business Integration Builder (BIB) framework

● Without using BIB

For the non BIB-based replication, you need to split all infotypes that are within the replication scope at cutover
date. This means that you need to split all relevant infotype records in a way that the old record ends on the day
before the cutover date and a new record starts on the cutover date.

For BIB-based replication to SAP S∕4HANA, infotype split is not a prerequisite. An employee can be filtered out
based on the employment status, and this can be done during the migration or integration of the employee
master data. This filtering would be applicable if you set the X for the ERP to EC: Filter based on
Employment status 0003 switch in the V_ECPAO_CONSTANT view. When the filtering of the employee
master data is done based on the employment status, the complete extraction of the data will be stopped
irrespective of whether the template is effective-dated or non-effective dated after the cutover date.

● If the switch ERP to EC: Filter based on Employment status is set, then the switch ERP to EC:
Additional Event Records switch should not be set. Also if you dont want to migrate a terminated or
an inactive employee and don't want to retain the original hire date in Employment Info block, then we
recommend to set the ERP to EC: Filter based on Employment status switch to X. Also note
that you cannot have both the switches set to active or both the switches as deactivated at any given point
of time. For more information on the switches, you can refer to Replicating Employee Data from SAP ERP
HCM to Employee Central Using <pname conkeyref="loiobe9c73df9e5049119f332a571e8c861e/CP-
INTEGRATION"/> as the Middleware guide.
● If the switch ERP to EC : Determine Personal Data of Global Employees is set, then:
○ You can migrate the host address of an employee during global transfer.
○ You can migrate the address and personal information of both the PERNR's linked to each other of an
employee during global transfer or international transfer.
○ You can migrate the active PERNR's and active host PERNR's email address and phone number to EC.

Table 6: Combination of switches which are recommended while migrating data to ERP

ERP to EC: Filter based on Employ­ ERP to EC : Determine Personal Data

ment status ERP to EC: Additional Event Records of Global Employees

Activated Not Activated Not Activated

Activated Not Activated Activated

Not Activated Activated Not Activated

Not Activated Activated Activated

Migrating Data from SAP S/4HANA On Premise to Employee Central Using Infoporter
14 PUBLIC Preparing the Systems for Data Migration to Employee Central
  Note

When you activate a switch, you set the value as X and if the switch is not activated, you leave the value as
blank.

Table 7: Employment Statuses Considered in Data Migration

If employment status on cutover date is (and no change is

coming up in the future until December 31, 9999)... Data is considered for integration/migration...

Active Considered

Inactive Not considered

Retired Not considered

Withdrawn Not considered

Table 8: Employment Statuses and Use Cases

If employment status on cutover date

is (and no change is coming up in the Data is considered for integration/
future until December 31, 9999)... For this use case... migration...

Active Employee was active during initial load Considered

and is still active.

Employee was inactive during initial Considered

load and changed to active state after
initial load.

Employee was retired during initial load Considered

and changed to active state after initial
load.

Inactive Employee was active during initial load Considered

but was changed to inactive state after
initial load.

Employee was inactive during initial Not considered

load and is still inactive.

Retired Employee was active during initial load Considered (default position is not
but now changed to retired state after transferred, but the last valid position
initial load. would be transferred to Employee Cen­
tral)

Employee was withdrawn during initial Not considered

load and changed to retired state after
initial load.

Migrating Data from SAP S/4HANA On Premise to Employee Central Using Infoporter
Preparing the Systems for Data Migration to Employee Central PUBLIC 15
If employment status on cutover date
is (and no change is coming up in the Data is considered for integration/
future until December 31, 9999)... For this use case... migration...

Employee was inactive during initial Not considered

load and changed to retired state after
initial load.

Withdrawn Employee was active during initial load Considered (default position is not
and changed to withdrawn state after transferred, but the last valid position
initial load. would be transferred to Employee Cen­
tral)

Employee was inactive during initial Not considered

load and changed to withdrawn state
after initial load.

Employee was moved from retired to Not considered

withdrawn state.

 Example

Let's say your cutover date is January 1, 2018. There is a record of the Personal Data (0002) infotype that
starts on November 1, 2015 and ends on December 31, 9999 (system high date). Before you switch to
Employee Central being the system of record for this employee's data, you therefore delimit this infotype
record so that it ends on December 31, 2017. Then you create a new infotype record that starts on January
1, 2018 and ends on December 31, 9999. Now you replicate employee data from SAP S∕4HANA to Employee
Central. Starting January 1, 2018 you maintain the data in Employee Central only.

 Caution

Organizational data with time constraint 3 (which means that any number of valid infotype records can
exist at any one time) is not supported by the Employee Central metadata. Therefore, you can't migrate
organizational data with time constraint 3 from SAP S∕4HANA to Employee Central.

Employee data with time constraint 3 can only be migrated to Employee Central entities that also support
overlapping data records. For more information see How Time Constraint 3 Mapping Works in the
Replicating Employee Data from SAP S/4HANA On Premise to Employee Central integration guide. Find the
most current version of this guide in SAP Help Portal at http://help.sap.com/hr_ecintegration.

Parent topic: Preparing the Systems for Data Migration to Employee Central [page 13]

Related Information

Defining the Migration Scope [page 13]

Preparing Employee Central for Data Migration [page 17]

Migrating Data from SAP S/4HANA On Premise to Employee Central Using Infoporter
16 PUBLIC Preparing the Systems for Data Migration to Employee Central
3.3 Preparing Employee Central for Data Migration

Here's what you need to do in Employee Central to prepare for data migration from SAP S∕4HANA.

Preparing Employee Central for Organizational Data Integration [page 17]

Take a look at some settings you should consider when setting up the data model for organizational
data in Employee Central.

Preparing Employee Central for Employee Data Integration [page 18]

Here are some things you should consider when setting up the data model for employee-related data in
Employee Central.

Granting Permissions for Employee Data and Organizational Data Migration [page 19]
Grant the business permissions to the users who run the migration of employee master data,
organizational object data, and foundation object data to Employee Central.

Parent topic: Preparing the Systems for Data Migration to Employee Central [page 13]

Related Information

Defining the Migration Scope [page 13]

Preparing the SAP S∕4HANA System for Data Migration [page 14]

3.3.1 Preparing Employee Central for Organizational Data

Integration

Take a look at some settings you should consider when setting up the data model for organizational data in
Employee Central.

● The field length of an Employee Central field ID that is within the integration scope must be the same as the
length of the target field in the SAP S∕4HANA system, which you want to map.
For example, if you want to map the Employee Central field ID Country to the SAP S∕4HANA field Country
Key (LAND1) and LAND1 has a length restriction of 3 characters, you must restrict the length of the Country
field in the Employee Central metadata to 3 characters.
● Picklists for Employee Central field IDs that you want to map to SAP S∕4HANA fields must be uploaded to
Employee Central before data replication starts so that picklist entries from Employee Central can be
mapped to value help entries from SAP S∕4HANA.
● If you use CSV file-based data replication, set the locale of the user who imports the CSV files containing
the data that was extracted from the SAP S∕4HANA system to English US (under Account Navigation
Options Change Language ). This is to ensure that the Employee Central metadata uses the same date
and number format as the SAP S∕4HANA system does. You can change the locale when the initial upload to
Employee Central is finished.
● The Parent field must not be a required field for positions and departments in the Employee Central
metadata during data migration. You can set it to Required when data migration is finished.

Migrating Data from SAP S/4HANA On Premise to Employee Central Using Infoporter
Preparing the Systems for Data Migration to Employee Central PUBLIC 17
  Remember

As a customer, you don't have access to Provisioning. To complete tasks in Provisioning, contact your
implementation partner. If you're no longer working with an implementation partner, contact Product
Support.

Parent topic: Preparing Employee Central for Data Migration [page 17]

Related Information

Preparing Employee Central for Employee Data Integration [page 18]

Granting Permissions for Employee Data and Organizational Data Migration [page 19]

3.3.2 Preparing Employee Central for Employee Data

Integration

Here are some things you should consider when setting up the data model for employee-related data in
Employee Central.

● The field length of an Employee Central field that is within the integration scope must be the same as the
length of the target field in the SAP S∕4HANA system, which you want to map.
For example, if you want to map the Employee Central field Country to the SAP S∕4HANA field Country Key
(LAND1) and LAND1 has a length restriction of 3 characters, you must restrict the length of the Country
field in the Employee Central data model to 3 characters.
● Picklists for Employee Central fields that you want to map to SAP S∕4HANA fields must be uploaded to
Employee Central before data replication starts so that picklist entries from Employee Central can be
mapped to value help entries from SAP S∕4HANA.
● If you use CSV file-based data replication, set the locale of the user who imports the CSV files containing
the data that was extracted from the SAP S∕4HANA system to English US (under Account Navigation
Options Change Language ). This is to ensure that the Employee Central data model uses the same
date and number format as the SAP S∕4HANA system does. You can change the locale when the initial
upload to Employee Central is finished.
● For some specific requirements Position Management must be enabled for your account using the Manage
Employee Central Settings admin tool in Employee Central.
● Some specific requirements apply to the default Employee Central entities provided for data replication.
For more information see the section that lists the entities you can use.

 Note

Infoporter is not responsible for sending the welcome emails for new users and also does not control the
password generation logic in Employee Central.

Migrating Data from SAP S/4HANA On Premise to Employee Central Using Infoporter
18 PUBLIC Preparing the Systems for Data Migration to Employee Central
  Remember

As a customer, you don't have access to Provisioning. To complete tasks in Provisioning, contact your
implementation partner. If you're no longer working with an implementation partner, contact Product
Support.

Parent topic: Preparing Employee Central for Data Migration [page 17]

Related Information

Preparing Employee Central for Organizational Data Integration [page 17]

Granting Permissions for Employee Data and Organizational Data Migration [page 19]

3.3.3 Granting Permissions for Employee Data and

Organizational Data Migration

Grant the business permissions to the users who run the migration of employee master data, organizational
object data, and foundation object data to Employee Central.

Prerequisites

You're familiar with the role administration tools in the SAP S∕4HANA system. For more information about role
administration, see User and Role Administration of Application Server ABAP in the SAP NetWeaver
documentation.

Context

The following template roles are available for the migration of employee master data, organizational object
data, and foundation object 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 via csv file
○ Determination of managers and organizational management data
○ Analyze inventory of the migrated employee data

Migrating Data from SAP S/4HANA On Premise to Employee Central Using Infoporter
Preparing the Systems for Data Migration to Employee Central PUBLIC 19
 ○ Delete the inventory details from the inventory tables
○ Use the application log to analyze errors
● Organizational and Foundation Object Data Migration from ERP to EC-Business User
(SAP_HR_ECPAO_MIG_OM_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 organizational object data and migrate it to Employee Central
○ Schedule the background jobs of the organizational data extraction
○ Analyze inventory of migrated organizational data
○ Delete the Inventory details from the inventory tables
○ Extract foundation object data from ERP and migrate it to EC
○ Analyze status of foundation object migration
○ Transfer work schedule rules from ERP to EC
(EC)
○ Use the application log to analyze errors

Procedure

1. Go to the Role Maintenance (PFCG) transaction in your SAP S∕4HANA system.

2. Set up the business user.
a. Copy the template role SAP_HR_ECPAO_MIG_EE_PROCESSING to the customer namespace.
b. Set up permissions for the copied role to suit your specific requirements.
c. Copy the template role SAP_HR_ECPAO_MIG_OM_PROCESSING to the customer namespace.
d. Set up permissions for the copied role to suit your specific requirements.
e. Assign the copied roles to the user who migrates employee master data, organizational object data,
and foundation object data from SAP ERP to Employee Central.

Task overview: Preparing Employee Central for Data Migration [page 17]

Related Information

Preparing Employee Central for Organizational Data Integration [page 17]

Preparing Employee Central for Employee Data Integration [page 18]

Migrating Data from SAP S/4HANA On Premise to Employee Central Using Infoporter
20 PUBLIC Preparing the Systems for Data Migration to Employee Central
4 Migrating Data from SAP S∕4HANA to
Employee Central

Now you're ready to actually migrate data from your SAP S∕4HANA to Employee Central.

Sequence of Data Extraction and Import Steps for Different Object Types [page 21]
When migrating data from SAP S∕4HANA to Employee Central, make sure to follow this sequence.

Importing Organizational Data into Employee Central [page 24]

Learn how to upload CSV files containing organizational data to Employee Central.

Importing Employee Data into Employee Central [page 25]

Here's how to upload CSV files containing employee master data to Employee Central.

Migrating Foundation Objects to Employee Central [page 27]

You can now migrate the foundation objects to Employee Central. SAP has delivered a standard set of
foundation objects. In addition to that, you can also create new foundation objects as per your
requirement.

Migrating Pay Calendar to Employee Central [page 44]

You can migrate the pay calendar data to Employee Central. You will have to first export the pay
calendar data information from Employee Central payroll and then import the data to Employee
Central.

Advantages of Web Service-Based Data Transfer for Migration [page 48]

Find out why web service-based data migration might be preferable to using the CSV-based approach.

Migrating Employee Master Data from Third-Party Systems [page 49]

You might want to migrate employee master data from other systems, such as non-HCM or third-party
systems, as well as from SAP S∕4HANA system to Employee Central.

4.1 Sequence of Data Extraction and Import Steps for

Different Object Types
When migrating data from SAP S∕4HANA to Employee Central, make sure to follow this sequence.

Prerequisites

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 so 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. Find the most current version of this guide in SAP Help Portal at http://help.sap.com/hr_ecintegration.

Migrating Data from SAP S/4HANA On Premise to Employee Central Using Infoporter
Migrating Data from SAP S∕4HANA to Employee Central PUBLIC 21
 Figure 1: Example: Employee Central Entities Enabled for Multiple Use

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.

 Example

Let's say, you create the transformation templates DEPARTMENT_WO_PARENT and DEPARTMENT_W_PARENT
for mapping organizational unit fields from SAP S∕4HANA to department fields in Employee Central. You
assign the Employee Central entity DEPARTMENTImportTemplate to both of the transformation templates
and map the fields as shown below.

Table 9: DEPARTMENT_WO_PARENT

Employee Central
Field Mapping Mode Infotype Subtype SAP S∕4HANA Field

Name Infotype Mapping 1000 STEXT

Code BAdI Mapping

Table 10: DEPARTMENT_W_PARENT

Employee Central
Field Mapping Mode Infotype Subtype SAP S∕4HANA Field

Name Infotype Mapping 1000 STEXT

Parent Department Infotype Mapping 1001 A002 SOBID

Code BAdI Mapping

Procedure

1. Replicate organizational units without their relationships. To do so:

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

Migrating Data from SAP S/4HANA On Premise to Employee Central Using Infoporter
22 PUBLIC Migrating Data from SAP S∕4HANA to Employee Central
  Example

In the example above, the DEPARTMENT_WO_PARENT template would be active, the

DEPARTMENT_W_PARENT template would be inactive.

b. 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.
c. 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. Find the most current version of this guide in SAP Help
Portal at http://help.sap.com/hr_ecintegration.
5. Replicate the organizational unit relationships. To do so:
a. 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. Deselect this checkbox for the other transformation
template that you use for mapping organizational units (the one that doesn't contain the Parent field).

 Example

In the example above, the DEPARTMENT_W_PARENT template would be active, the

DEPARTMENT_WO_PARENT template would be inactive.

b. 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 since this is not active.
c. 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.

Migrating Data from SAP S/4HANA On Premise to Employee Central Using Infoporter
Migrating Data from SAP S∕4HANA to Employee Central PUBLIC 23
Task overview: Migrating Data from SAP S∕4HANA to Employee Central [page 21]

Related Information

Importing Organizational Data into Employee Central [page 24]

Importing Employee Data into Employee Central [page 25]
Migrating Foundation Objects to Employee Central [page 27]
Migrating Pay Calendar to Employee Central [page 44]
Advantages of Web Service-Based Data Transfer for Migration [page 48]
Migrating Employee Master Data from Third-Party Systems [page 49]

4.2 Importing Organizational Data into Employee Central

Learn how to upload CSV files containing organizational data to Employee Central.

Prerequisites

You have extracted the data from the SAP S∕4HANA system into CSV files using the Organizational Data
Extraction (ECPAO_OM_OBJECT_EXTRACTION) program. For more information about the data extraction
program, see the Replicating Employee Data from SAP S∕4HANA to Employee Central integration guide. Find the
most current version of this guide in SAP Help Portal at http://help.sap.com/hr_ecintegration.

Context

Make sure that you follow the sequence described in section Sequence of Data Extraction and Import Steps for
Different Object Types.

Procedure

1. Go to the Admin Center.

2. Choose the Import and Export Data tool.

Migrating Data from SAP S/4HANA On Premise to Employee Central Using Infoporter
24 PUBLIC Migrating Data from SAP S∕4HANA to Employee Central
 Figure 2: Import and Export Data Tool
3. Select the Import Data action.
4. Select CSV File.
5. Choose the object type, such as Position.
6. Browse for the CSV file containing the data that was extracted from the SAP S∕4HANA system.
7. Select the Full Purge purge type.
8. Choose Import.

Task overview: Migrating Data from SAP S∕4HANA to Employee Central [page 21]

Related Information

Sequence of Data Extraction and Import Steps for Different Object Types [page 21]
Importing Employee Data into Employee Central [page 25]
Migrating Foundation Objects to Employee Central [page 27]
Migrating Pay Calendar to Employee Central [page 44]
Advantages of Web Service-Based Data Transfer for Migration [page 48]
Migrating Employee Master Data from Third-Party Systems [page 49]

4.3 Importing Employee Data into Employee Central

Here's how to upload CSV files containing employee master data to Employee Central.

Prerequisites

You have extracted the data from the SAP S∕4HANA system into CSV files using the Employee Data Extraction
(ECPAO_EMPL_EXTRACTION) program. For more information about the data extraction program, see the

Migrating Data from SAP S/4HANA On Premise to Employee Central Using Infoporter
Migrating Data from SAP S∕4HANA to Employee Central PUBLIC 25
Replicating Employee Data from SAP S/4HANA On Premise to Employee Central integration guide. Find the
most current version of this guide in SAP Help Portal at http://help.sap.com/hr_ecintegration.

Context

Make sure that you follow the sequence we recommed for data extraction and import and that you upload the
CSV files for the different employee data entities in the recommended order. For more information, see For
Which Employee Data-Related Employee Central Entities Can I Use Data Replication? in the Replicating
Employee Data from SAP S/4HANA On Premise to Employee Central integration guide, where you can find a
sequence number for each employee data entity.

Figure 3: Importing Employee Data into Employee Central

Procedure

1. Go to the Admin Center and choose the Import Employee Data tool.
2. Select the corresponding entity and the Full Purge option.
3. Choose Import.

You can also perform a bulk upload using the zip option. To import zip files, select the Composite (Zip) Data
Upload option.

Task overview: Migrating Data from SAP S∕4HANA to Employee Central [page 21]

Related Information

Sequence of Data Extraction and Import Steps for Different Object Types [page 21]

Migrating Data from SAP S/4HANA On Premise to Employee Central Using Infoporter
26 PUBLIC Migrating Data from SAP S∕4HANA to Employee Central
Importing Organizational Data into Employee Central [page 24]
Migrating Foundation Objects to Employee Central [page 27]
Migrating Pay Calendar to Employee Central [page 44]
Advantages of Web Service-Based Data Transfer for Migration [page 48]
Migrating Employee Master Data from Third-Party Systems [page 49]

4.4 Migrating Foundation Objects to Employee Central

You can now migrate the foundation objects to Employee Central. SAP has delivered a standard set of
foundation objects. In addition to that, you can also create new foundation objects as per your requirement.

Parent topic: Migrating Data from SAP S∕4HANA to Employee Central [page 21]

Related Information

Sequence of Data Extraction and Import Steps for Different Object Types [page 21]
Importing Organizational Data into Employee Central [page 24]
Importing Employee Data into Employee Central [page 25]
Migrating Pay Calendar to Employee Central [page 44]
Advantages of Web Service-Based Data Transfer for Migration [page 48]
Migrating Employee Master Data from Third-Party Systems [page 49]

4.4.1 Migrating Work Schedules to Employee Central

Here's how you can migrate work schedules from the SAP S∕4HANA system to Employee Central.

Prerequisites

You have enabled the Business Integration Builder mode in your system. To make this setting, go to
Customizing for Personnel Management and choose Integration with SuccessFactors Employee Central
Business Integration Builder Basic Settings Maintain the Constant Values . Add the Activate BIB for EC to
ERP Employee Replication constant and set the constant value to X.

You have set up work schedule rules in your SAP S∕4HANA system.

You have set up a proxy to your Employee Central instance.

Migrating Data from SAP S/4HANA On Premise to Employee Central Using Infoporter
Migrating Data from SAP S∕4HANA to Employee Central PUBLIC 27
You have set up the middleware:

● If you use SAP HANA Cloud Integration as the middleware, make sure that the Upsert Data from SAP ERP
or SAP S4HANA to SAP SuccessFactors Employee Central Using the OData API integration flow from the
SAP ERP or SAP S/4HANA Integration with SAP SuccessFactors Employee Central: Employee and
Organizational Data integration package is set up.
● If you use Dell Boomi AtomSphere as the middleware, make sure that the Packaged Integration: SAP ERP to
EC Employee Replication v1.0 process from the Packaged Integration: SAP ERP to EC Employee Replication
v1.0 integration pack is set up.

For more information about how to set up the middleware, see the corresponding version of the Replicating
Employee Data from SAP ERP HCM to Employee Central or the Replicating Employee Data from SAP S/4HANA
to Employee Central integration guide. Find the most current version of the relevant guide in SAP Help Portal at
http://help.sap.com/hr_ecintegration.

Context

To migrate work schedule rules, use the Transfer Work Schedule Rules from ERP to Employee Central
(ECTIM_TRANSFER_WSR) transaction in your SAP S∕4HANA system. This transaction calls the
ECTIM_TRANSFER_WSR_TO_EC program. You can use this program, for example, to make available work
schedules from SAP S∕4HANA in Job Information of employees whose master data is maintained in Employee
Central and replicated to SAP S∕4HANA because you use SAP S∕4HANA as the Time Management system.

 Note

What's called Work Schedule in Employee Central is the same as Work Schedule Rule in the SAP S∕4HANA
system.

The program transfers information from the following Customizing tables in the SAP S∕4HANA system to
Employee Central:

● Work Schedule Rules (T508A, T508S)

● Period Work Schedules (T551A)
● Daily Work Schedule (T550A, T550S)
● Break Schedules (T550P)

Migrating Data from SAP S/4HANA On Premise to Employee Central Using Infoporter
28 PUBLIC Migrating Data from SAP S∕4HANA to Employee Central
Here's an overview of the tables in Employee Central SAP S∕4HANA:

Figure 4: Work Schedule Rules: Tables in SAP S∕4HANA

The program uses the generic OData upsert middleware process to transfer the data to Employee Central.
Make the following settings on the selection screen of the program:

Procedure

1. Specify your Employee Central instance.

The Employee Central instance defines which language versions the program is to transfer when creating
the external names of the WorkSchedule and WorkScheduleDayModel objects in Employee Central. In the
SAP S∕4HANA system, the descriptions to be transferred are stored in the Text Table for Work Schedule
Rules (T508S) and Daily Work Schedule Texts (T550S) tables. The program transfers all languages that are
mapped for the Employee Central instance in Customizing for Personnel Management, under Integration
with SuccessFactors Employee Central Business Integration Builder Organizational Data Integration
Map Languages from Employee Central and ERP . If the Text Table for Work Schedule Rules (T508S) and
Daily Work Schedule Texts (T550S) tables don't contain any entries for the work schedule rules to be
transferred, the program transfers the external code of the work schedule rule to the External Name field –
but only for the default Employee Central language. For the other languages, no external name is
transferred in this case.
2. Select the work schedule rules to be transferred, using one of the following options:
○ Specify various selection criteria, such as the rule’s employee subgroup grouping or the public holiday
calendar assigned to the rule.

Migrating Data from SAP S/4HANA On Premise to Employee Central Using Infoporter
Migrating Data from SAP S∕4HANA to Employee Central PUBLIC 29
 ○ Select a transport request. For example, a request that you've used to transport your work schedule
rules from your test system to your productive system.
○ Select all work schedule rules that are currently stored with the status Failed in the Inventory of
Replicated Foundation Objects (ECPAO_FO_INVT) table and are assigned to the Employee Central
instance you entered above.
3. Define how the program is to deal with day work schedule variants.

Some work schedule rules use daily work schedules that have multiple day variants assigned. Employee
Central cannot handle such variants. That’s why you need to decide how the program is to handle such
work schedule rules:
○ You can transfer all work schedule rules, ignoring day variants. That is, use the default variant also for
those work schedule rules that have a specific day variant assigned (meaning, for which the Daily Work
Schedule Variant (VARIA) field in the Daily Work Schedule (T550A) table is not empty).
○ You can omit work schedule rules that use multiple daily work schedule variants.
4. Define how the program is to deal with paid work breaks.

Some work schedule rules use daily work schedules that have paid work breaks assigned. Employee
Central cannot handle paid breaks. That’s why you need to decide how the program is to handle such work
schedule rules:
○ You can transfer only unpaid work breaks when creating the WorkScheduleDayModelSegment objects
in Employee Central for the work schedule rules.
○ You can completely omit work schedule rules that use daily work schedules with breaks that have paid
periods (meaning, for which the Paid Break Period (PDBEZ) field in the Break Schedules (T550P) table
has an entry other than 0).
5. Select the time recording variant.

The time recording variant of a work schedule rule (duration or clock time) needs to be the same as for all
work schedule day models assigned to the work schedule. Following options are available for choosing the
time recording variant:
○ Use time recording variant Duration for all work schedules and work schedule day models.
○ Use time recording variant Clock Time for all work schedules and work schedule day models, but omit
work schedules that have cross-midnight shifts.
○ Use time recording variant Clock Time for all work schedules and work schedule day models, but use
Duration for work schedules that have cross-midnight shifts.
○ Use time recording variant Clock Time for all work schedules.

 Note

This option is available from the SP31 package. The Cross midnight work schedules (schedules
where the working time starts on one day and ends the next day) are now supported in SAP
SuccessFactors Employee Central. This option will then use clock time for all work schedules and
supports sending the cross-midnight work schedules to EC.

○ Use the option Transfer Day Work Schedule's Flextime as 'Flextime Bandwidth' segment so that the field
Planned working time in the Flextime are mapped to the Flextime Bandwidth category and the Normal
working time in the Flextime are mapped to the Scheduled working time.

 Note

This option is applicable only for Clock Time.

Migrating Data from SAP S/4HANA On Premise to Employee Central Using Infoporter
30 PUBLIC Migrating Data from SAP S∕4HANA to Employee Central
 Handling of day schedules with Flextime across midnight:
○ Case 1: Planned working time and Normal working time are not cross-midnight shift: Then the
report updates above segments to Flextime bandwidth and Scheduled working time segments
respectively for the Work Schedule Day Model.
○ Case 2: Planned working time and Normal working time are both across midnight: Then the report
updates to Flextime bandwidth and Scheduled working time segments respectively for the Work
Schedule Day Model.
○ Case 3: Planned working time is not cross-midnight shift but Normal working time is cross-
midnight shift: This is an invalid case as Planned working time would always be greater than
Normal Working time as per ERP configurations.
○ Case 4: Planned working time is cross-midnight shift but Normal working time is not cross-
midnight shift: EC does not allow creation of such flex time bandwidths in the day work schedule.
Hence the report skips the work schedules which have at least one such day work schedule.
6. Define whether the program is to carry out a test run first.

You can carry out a test run of the program to output the result to SAP List Viewer, without triggering the
actual transfer to Employee Central. SAP List Viewer shows the data in a tree view. You can check what
would be transferred (and what wouldn’t). If you clear the Test Mode checkbox, the program triggers the
actual upsert to Employee Central using the default logical port defined for data replication from SAP
S∕4HANA to Employee Central. The result screen shows statistical information such as how many work
schedule rules were upserted, had errors, or were skipped.

Results

If you clear the Test Mode checkbox, the program creates corresponding objects in Employee Central and
updates the following tables in SAP S∕4HANA:

● Inventory of Replicated Foundation Objects (ECPAO_FO_INVT)

● Inventory of Replicated Foundation Objects - Messages (ECPAO_FO_INVT_M)

These tables are updated for each replication run. They don't contain a replication history. Use the Analyze
Status of Foundation Object Replication (ECPAO_INVT_FO) transaction, which evaluates these tables, to check
the result of the program run.

Next Steps

If you replicate employee master data from Employee Central to the SAP S∕4HANA system and want to map
the Planned Working Time (0007) infotype, set up a conversion rule to transfer only the first eight characters of
the external key from Employee Central to the Work Schedule Rule (SCHKZ) field in SAP S∕4HANA.

Work Schedule Objects Created in Employee Central [page 33]

Based in the work schedule objects migrated from the SAP S∕4HANA system, the Transfer Work
Schedule Rules from ERP to Employee Central program creates corresponding objects in Employee
Central.

External Codes Generated for Work Schedule Objects in Employee Central [page 36]

Migrating Data from SAP S/4HANA On Premise to Employee Central Using Infoporter
Migrating Data from SAP S∕4HANA to Employee Central PUBLIC 31
 When creating work schedule objects in Employee Central, the Transfer Work Schedule Rules from ERP
to Employee Central program generates suitable external codes.

Migrating Data from SAP S/4HANA On Premise to Employee Central Using Infoporter
32 PUBLIC Migrating Data from SAP S∕4HANA to Employee Central
4.4.1.1 Work Schedule Objects Created in Employee
Central
Based in the work schedule objects migrated from the SAP S∕4HANA system, the Transfer Work Schedule Rules
from ERP to Employee Central program creates corresponding objects in Employee Central.

Here's an overview of the objects created in Employee Central:

Figure 5: Work Schedule Rules: Objects in Employee Central

 Note

If the OData upsert of the work schedule itself or of any of its child objects fails, the program sets the status
Failed for this work schedule in the Inventory of Replicated Foundation Objects (ECPAO_FO_INVT) table. It

Migrating Data from SAP S/4HANA On Premise to Employee Central Using Infoporter
Migrating Data from SAP S∕4HANA to Employee Central PUBLIC 33
 skips the work schedule and all child objects that haven't been upserted yet and continues with upserting
the next work schedule. To upsert the skipped work schedules later, correct the issue that caused the error.
Then run this program again, choosing the option Select All Previously Failed Work Schedule Rules for This
EC Instance.

WorkSchedule

If a work schedule rule is transferred which already exists in Employee Central and is used in an employee's Job
Information, the upsert fails. You will be shown the following error message in this case:
Change of work schedule not possible due to job information references

If you transfer a work schedule rule using a day model that already exists and is used in Employee Central
(because it was already replicated with another work schedule rule), you are shown the following information
message:
Change of work schedule day model not possible due to job information references

Don't worry – in this case the new work schedule rule is created correctly in Employee Central, using the day
model that was replicated before.

WorkScheduleDayModelAssignment

The program associates the WorkScheduleDayModel objects to the corresponding WorkSchedule objects using
the WorkScheduleDayModelAssignment objects.

WorkScheduleDayModel

To change an existing day model in Employee Central, a new time slice is required. That's why you need to go
through the following steps if you want to transfer a changed day model from SAP S∕4HANA to Employee
Central:

1. Edit the day model in SAP S∕4HANA, using a specific start date.
This will result in a new day model object being created in Employee Central because the time stamp is
included in the external code.
2. Create a new time slice for the work schedule rule in SAP S∕4HANA, using the same start date as for the
new day model time slice.
This will result in a new work schedule rule object being created in Employee Central because the time
stamp is included in the external code.

 Example

Let's say on October 1, 2017 you migrate a work schedule rule with a work schedule day model from SAP
S∕4HANA to Employee Central. The time slices in SAP S∕4HANA have the start date January 1, 1990. That is,
the objects created in Employee Central get the following external codes:

WorkSchedule PDAYxxxxxxxxx19900101 with WorkScheduleDayModel xxxxxxxx19900101C

Migrating Data from SAP S/4HANA On Premise to Employee Central Using Infoporter
34 PUBLIC Migrating Data from SAP S∕4HANA to Employee Central
 You assign this work schedule in an employee's Job Information.

On January 1, 2018, you change the day model in SAP S∕4HANA. If you'd now replicate this information to
Employee Central, this would result in the following objects:

WorkSchedule PDAYxxxxxxxxx19900101 with WorkScheduleDayModel xxxxxxxx120180101C

But since the PDAYxxxxxxxxx19900101 work schedule is used in Employee Central, the error message
Change of work schedule not possible due to job information references would be raised and the upsert
would fail.

That's why you also need to edit the work schedule rule in SAP S∕4HANA, using the start date January 1,
2018. Because then the following objects are created in Employee Central:

WorkSchedule PDAYxxxxxxxxx20180101 with WorkScheduleDayModel xxxxxxxx120180101C

Both are new objects, so the upsert is successful this time.

WorkScheduleDayModelSegment

For the Clock Time time recording variant, the program also creates WorkScheduleDayModelSegment objects
and links them to their parent WorkScheduleDayModel objects.

Parent topic: Migrating Work Schedules to Employee Central [page 27]

Related Information

External Codes Generated for Work Schedule Objects in Employee Central [page 36]

Migrating Data from SAP S/4HANA On Premise to Employee Central Using Infoporter
Migrating Data from SAP S∕4HANA to Employee Central PUBLIC 35
4.4.1.2 External Codes Generated for Work Schedule
Objects in Employee Central

When creating work schedule objects in Employee Central, the Transfer Work Schedule Rules from ERP to
Employee Central program generates suitable external codes.

Work Schedule

When creating the WorkSchedule object, the Transfer Work Schedule Rules from ERP to Employee Central
program populates the externalCode field with a key that is concatenated from the values of the following fields
of the Work Schedule Rules (T508A) table in the SAP S∕4HANA system:

● Work Schedule Rule (SCHKZ)

● Employee Subgroup Grouping for Work Schedules (ZEITY)
● Public Holiday Calendar (MOFID)
● Personnel Subarea Grouping for Work Schedules (MOSID)
● Start Date (BEGDA)

 Example

Let’s say, this information is stored in the Work Schedule Rules table:

● Work Schedule Rule: PDAY (= 8 Hour Day Shift)

● Employee Subgroup Grouping for Work Schedules: 1
● Public Holiday Calendar: US
● Personnel Subarea Grouping for Work Schedules: 10
● Start Date: 01/01/2018

Then the external key of the corresponding WorkSchedule object would be: PDAY 1US1020180101

The first part, which represents the actual key of the work schedule rule, needs to be eight characters long.
That's why the program adds blanks if needed. In our example, it adds four blanks because the actual key
(PDAY) is only four characters long.

 Note

Employee Central issues a warning message about the code being longer than ten characters. You can
ignore this warning.

You can use BAdI definition EX_ECTIM_WSR_DATA_MODIFY to modify the external code from the ERP system
for the work schedule rule. You use this BAdI to provide the external code in the required format during the
work schedule migration to Employee Central fields. You can access the customizing activity at Personnel
Management Integration with SuccessFactors Employee Central Business Integration Builder Business
Add-Ins (BAdIs)Business Add-Ins (BAdIs) Data Transfer to Employee Central BAdI: Mapping of External
Code during the Work Schedule Migration .

Migrating Data from SAP S/4HANA On Premise to Employee Central Using Infoporter
36 PUBLIC Migrating Data from SAP S∕4HANA to Employee Central
Work Schedule Day Model

When creating the WorkScheduleDayModel object, the program populates the externalCode field with a key
that is concatenated from the values of the following fields of the Daily Work Schedule (T550A) table in the SAP
S∕4HANA system:

● Personnel Subarea Grouping for Daily Work Schedules (MOTPR)

● Daily Work Schedule (TPROG)
● Daily Work Schedule Variant (VARIA)
● Sequential Number of Daily Work Schedule (SEQNO)

 Note

The sequential number is not considered. The program always uses 01 here.

● Start Date (BEGDA)

 Note

The start date is only added if you have implemented SAP Note 2586803 in addition to support
package 21 of the PA_SE_IN 100 software component version..

At the end of the external code, the program adds the time recording variant. Either D for Duration or C for
Clock Time.

 Example

Let’s say, this information is stored in the Daily Work Schedule table:

● Personnel Subarea Grouping for Daily Work Schedules: 01

● Daily Work Schedule: NORM
● Daily Work Schedule Variant: blank (= standard variant)
● Sequential Number of Daily Work Schedule: 1
● Start Date: 01/01/2018

The time recording variant is Clock Time

Then the external key of the corresponding WorkScheduleDayModel object would be:
01NORM0120180101C

Parent topic: Migrating Work Schedules to Employee Central [page 27]

Related Information

Work Schedule Objects Created in Employee Central [page 33]

Migrating Data from SAP S/4HANA On Premise to Employee Central Using Infoporter
Migrating Data from SAP S∕4HANA to Employee Central PUBLIC 37
4.4.2 Migrating Other Standard Foundation Objects to
Employee Central

Here's how you can migrate other standard Foundation Objects from the SAP S∕4HANA system to Employee
Central than the SAP delivered list of four standard foundation objects (Work Schedule, Pay Component, Pay
Component Group, & Company).

Context

To migrate the foundation objects: PayComponet, PayComponent Group, and Company, use the Transfer
Foundation Objects from ERP to Employee Central (ECPAO_TRANS_FO_OBJ) transaction in your SAP S∕4HANA
system. This transaction calls the ECPAO_TRANSFER_FO_OBJ_TO_EC program. You can use the BAdI: Mapping
Foundation Objects data for Data Migration to EC BAdI to read data from the ERP database tables or pass a
constant value to map with the EC fields for the foundation objects (PayComponent, PayComponentGroup, or
Company). You can access the customizing activity at Personnel Management Integration with
SuccessFactors Employee Central Business Integration Builder Business Add-Ins (BAdIs) Data Transfer to
Employee Central BAdI: Mapping Foundation Objects data for Data Migration to EC . The BAdI BADI
EX_ECPAO_MAP_FOBJ_TRANS_TO_EC is called by the ECPAO_TRANSFER_FO_OBJ_TO_EC program, based on
the foundation object that you choose. SAP has delivered default active BAdI implementations for these three
standard Foundation Objects which can be used.

Procedure

1. Specify the Employee Central instance. Once you specify the EC instance, based on that the locale
language will be picked up otherwise system log on language will be considered.
2. Choose the foundation object for which you want to migrate the data. You can choose either Pay
Component, Pay Component Group, or Company.
3. Choose the country grouping for which you want to transfer the foundation object type.
4. Choose the required Foundation Object field.
5. Choose the Transport Request in which you have made the changes or created entries for the foundation
objects. You can either choose Transport Request option or Foundation Object selection from screen option.
6. Choose the Earliest Transfer Date from which you want to migrate the Foundation Objects to EC.
7. Define whether the program is to carry out a test run first.

You can carry out a test run of the program to output the result to SAP List Viewer, without triggering the
actual transfer to Employee Central. SAP List Viewer shows the data in a tree view. You can check what
would be transferred (and what wouldn’t). If you clear the Test Mode checkbox, the program triggers the
actual upsert to Employee Central using the default logical port defined for data replication from SAP
S∕4HANA to Employee Central. The result screen shows statistical information such as how many wage
types or wage type groups or company were upserted, had errors, or were skipped.

In Test Run you can either choose Logs or List View, which enables you to view the results via Application
Logs or ALV display respectively. Additionally you can also download the results consisting of Foundation

Migrating Data from SAP S/4HANA On Premise to Employee Central Using Infoporter
38 PUBLIC Migrating Data from SAP S∕4HANA to Employee Central
 Objects and related attributes into a CSV file through List view mode. This will allow you to see the data
that is being mapped and exported. Additionally, it displays the total number of successful and erroneous
records that were processed in the current run.

 Note

The option to choose between Logs and List View is only applicable in Test Run and is disabled in
Production run.

4.4.2.1 Default Field Mapping Delivered in the Standard

Active BAdI Implementation

Here's the details of the default mappings delivered in the active BAdI implementation from SAP

Pay Component

Constant Value (No

EC Field Accepted Values in EC ERP Table ERP Field backend mapping)

externalCode T511 LGART

name T512T LGTXT/KZTXT

description T512T LGTXT/KZTXT

startDate T511 BEGDA

endDate T511 ENDDA

status ACTIVE/INACTIVE ACTIVE

payComponentType Amount/Percentage/ T511 KOMBI

Number

number If payComponentType
is Number then these
fields (fields 8, 9, 10)
are to be filled

unitOfMeasure T511 ZEINH

Rate

isEarning 0/1 T511 OPKEN

Migrating Data from SAP S/4HANA On Premise to Employee Central Using Infoporter
Migrating Data from SAP S∕4HANA to Employee Central PUBLIC 39
 Constant Value (No
EC Field Accepted Values in EC ERP Table ERP Field backend mapping)

currency WAERS

frequencyCode MON-monthly MON

Recurring 0/1 1

canOverride 0/1 T511 MOD02

isEndDatedPayment 0/1 1

Pay Component Group

Constant Value (No

EC Field Accepted Values in EC ERP Table ERP Field backend mapping)

externalCode T52D7 WGGRP

name T52D6 WGRTX

Description T52D6 WGRTX

startDate System date

endDate 31/12/9999

status ACTIVE/INACTIVE ACTIVE

showOnCompUI 0/1 1

useForComparatioCalc 0/1 0

Currency WAERS

useForRangePenetra­ 0/1 0
tion

sortOrder 0/1

payComponentFlx Example: M210|M211| Multiple Pay compo­

M212 nents can be send us­
ing the separator ‘|’

Migrating Data from SAP S/4HANA On Premise to Employee Central Using Infoporter
40 PUBLIC Migrating Data from SAP S∕4HANA to Employee Central
Legal Entity

EC Field EC Field Description Accepted Values in EC ERP Table ERP field

start-date Start Date Depending on the date

provided in the selec­
tion screen if not pro­
vided then the lowest
date 01.01.1900

externalCode Legal Entity ID T001 BUKRS

Name/name_default­ Legal Entity Name T001 BUTXT

Value

name.en_US Legal Entity Name This is a concatenation T001 BUTXT

of ‘name_’ with default
locale.

Default locale is from

Table ECPAO_COM­
PANY and field DE­
FAULT_LOCALE

Description Description T001 BUTXT

description.en_US Description This is a concatenation T001 BUTXT

of ‘description_’ with
default locale.

Default locale is from

Table ECPAO_COM­
PANY and field DE­
FAULT_LOCALE

status Status ACTIVE/INACTIVE

defaultPayGroup Default Pay Group

 Note
This is not a man­
datory field

defaultLocation Default Location

 Note
This is not a man­
datory field

Migrating Data from SAP S/4HANA On Premise to Employee Central Using Infoporter
Migrating Data from SAP S∕4HANA to Employee Central PUBLIC 41
EC Field EC Field Description Accepted Values in EC ERP Table ERP field

standardHours Standard Weekly It is a numeric for ex­

Hours ample 40
 Note
It is set 40 in
standard

Currency Currency T001 WAERS

Country Country T005 INTCA3

NameFormatGO.exter­ Name Format

nalCode

 Note
This is not a man­
datory field

In case you need a different mapping logic for any of the fields or need to include an additional field, then you
can disable the default active BAdI implementation and create your own custom BAdI implementation.

4.4.3 Migrating Custom Foundation Objects to Employee

Central

You might also want to migrate additional Foundation Objects (FO) other than the standard list delivered by
SAP.

Context

SAP delivers a list of four standard foundation objects (Work Schedule, Pay Component, Pay Component
Group, & Company). You can use the V_ECPAO_FO_UPS view to add your own foundation objects. Once you
add the new foundation object, you have to implement the EX_ECPAO_MAP_FOBJ_TRANS_TO_EC BAdI to map
the corresponding Employee Central field of the corresponding foundation object. You also need to set the filter
value as FO object name. Once you activate the BAdI, you need to run the ECPAO_TRANSFER_FO_OBJ_TO_EC
report for migrating the foundation object to EC. And for the custom foundation objects in the report selection
screen you need to also enter the transport request. You could choose the foundation objects either based on
country grouping or objects specified in the screen.

Migrating Data from SAP S/4HANA On Premise to Employee Central Using Infoporter
42 PUBLIC Migrating Data from SAP S∕4HANA to Employee Central
Procedure

1. Enter the Object type.

2. Enter the text that you want for the new foundation object that you are adding.
3. Enter the Employee Central entity name for the new foundation object.
4. Enter the table name and field name in the Validation Table Name for FO and Validation Table Field Name for
FO field. These are optional field.

When these fields are filled with valid table and field name, the selection screen of the report
ECPAO_TRANSFER_FO_OBJ_TO_EC enables the option to choose the object - foundation object by country
grouping and object id. The table name and field name in this view is used to validate the input entered in
the selection screen of the report. In case these two fields are not filled, then only the option Transport
request is enabled.

 Note

By using the navigational fields data, you can now send the data to SAP SuccessFactors Employee
Central. The report also allows you to send the navigational properties. With this you no more need to
use the text fields for entering the names of the linked objects.

4.4.4 Analyzing the Status of Migration of Foundation Object

to Employee Central

Here's how to check the migration status for Foundation Objects (FO) you transferred from the SAP S∕4HANA
system to Employee Central. You can check the status for the foundation objects like: Work Schedule Rules,
Pay Component, Pay Component Group, Company and also for any additional custom Foundation Objects.

Prerequisites

You have run the Transfer Work Schedule Rules from ERP to Employee Central (ECTIM_TRANSFER_WSR_TO_EC)
program or Transfer Foundation Objects from ERP to Employee Central) ECPAO_TRANS_FO_OBJ) program in
your SAP S∕4HANA system.

Context

To check the migration status, use the Analyze Status of Foundation Object Replication (ECPAO_INVT_FO)
transaction. This transaction calls the ECPAO_INVENTORY_FOR_FND_OBJ program. This program analyzes the
status of the last run of the Transfer Work Schedule Rules from ERP to Employee Central and Transfer

Migrating Data from SAP S/4HANA On Premise to Employee Central Using Infoporter
Migrating Data from SAP S∕4HANA to Employee Central PUBLIC 43
Foundation Objects from ERP to Employee Central program and shows the messages raised by it. While doing
so, it analyzes the content of the following tables:

● Inventory of Replicated Foundation Objects (ECPAO_FO_INVT)

● Inventory of Replicated Foundation Objects - Messages (ECPAO_FO_INVT_M)

These tables are updated for each replication run. They don't contain a replication history.

Procedure

1. Select the Employee Central foundation object type.

2. Specify the Employee Central instance for which you've transferred the foundation objects to Employee
Central.
3. Optionally, enter the external code or codes of the foundation objects whose replication status you want to
analyze.

You can also use wildcards, for example, NORM* to select specific objects. If you don't specify any external
codes, the status of all objects is analyzed that were contained in the last migration run.
4. Select the migration status you want to check.

By default, the program shows objects whose status is Failed. You can also select Successful.
5. To restrict the output to a specific time frame you're interested in, select the Select Data Based on Time
Range checkbox and enter a From and To date and time.

This is useful, for example, when you know that errors occurred on a specific day and want to analyze the
status only for this day.

Results

In the result, you'll first see some statistical information such as how many objects were upserted successfully
or had errors.

Below the statistical information is the list of objects contained in the last replication run (as specified in your
selection criteria), together with the replication status and the time stamp of when they were replicated. For
each object, all messages are listed that were raised by the last migration run. These could be messages issued
for the object itself (such as the work schedule rule or other foundation objects) as well as messages issued for
related objects (such as work schedule day models).

4.5 Migrating Pay Calendar to Employee Central

You can migrate the pay calendar data to Employee Central. You will have to first export the pay calendar data
information from Employee Central payroll and then import the data to Employee Central.

Migrating Data from SAP S/4HANA On Premise to Employee Central Using Infoporter
44 PUBLIC Migrating Data from SAP S∕4HANA to Employee Central
Parent topic: Migrating Data from SAP S∕4HANA to Employee Central [page 21]

Related Information

Sequence of Data Extraction and Import Steps for Different Object Types [page 21]
Importing Organizational Data into Employee Central [page 24]
Importing Employee Data into Employee Central [page 25]
Migrating Foundation Objects to Employee Central [page 27]
Advantages of Web Service-Based Data Transfer for Migration [page 48]
Migrating Employee Master Data from Third-Party Systems [page 49]

4.5.1 Exporting Pay Calendar Information from ERP

Before you migrate Pay Calendar to Employee Central, you need to export the payroll calendar dates to a csv
file.

Context

Procedure

1. Go to transaction SE38.
2. Enter program: PAOCF_EC_PAY_CALENDAR_INFO.
3. Enter the relevent information (Country Grouping, Pay Group Code, From Payroll Year, and To Payroll Year.)
4. Execute the report to export the Pay Calendar information into a csv file.

Results

The dates are exported to a csv file and will look similar to this.

Migrating Data from SAP S/4HANA On Premise to Employee Central Using Infoporter
Migrating Data from SAP S∕4HANA to Employee Central PUBLIC 45
  Example

4.5.2 Importing Pay Calendar Information to Employee

Central

You can import the Pay Calendar information to Employee Central.

Context

Procedure

1. Go to Admin Center. In the Tools search field, enter Import and Export Data.
2. Choose Import Data.

Migrating Data from SAP S/4HANA On Premise to Employee Central Using Infoporter
46 PUBLIC Migrating Data from SAP S∕4HANA to Employee Central
 3. Choose Pay Calendar.
4. Choose Incremental Load.
5. Click Choose File to browse for the csv file.
6. Click Import.

You can check and validate the pay calendar in Admin Center under Manage Data.

Migrating Data from SAP S/4HANA On Premise to Employee Central Using Infoporter
Migrating Data from SAP S∕4HANA to Employee Central PUBLIC 47
4.6 Advantages of Web Service-Based Data Transfer for
Migration

Find out why web service-based data migration might be preferable to using the CSV-based approach.

● In the web service-based data replication mode, less manual effort is required while replicating the data
into Employee Central. In contrast, the CSV-based data replication mode is a two-step process, where the
files have to be first downloaded and then imported manually into the Employee Central.
● In the web service-based data replication mode, the employee key mapping table is populated
automatically during the replication process. In contrast, in the CSV-based data replication mode, you need
to execute the key mapping update program ECPAO_EEREPCSV_EEKEYMAP_UPDATE separately after
you've imported the employee data to populate the employee key mapping table.

 Note

This is applicable only for non-BIB mode.

● Change pointers or delta transfer is possible in web service-based data transfer.

● You can set up a continuous migration of employee data. During the initial data migration from SAP
S∕4HANA system to Employee Central, you can simulate the replication from Employee Central to SAP
S∕4HANA. During the simulation, you can check for any errors and resolve the errors before you replicate

Migrating Data from SAP S/4HANA On Premise to Employee Central Using Infoporter
48 PUBLIC Migrating Data from SAP S∕4HANA to Employee Central
 the actual data to Employee Central. Further migration will happen only for the delta when the initial
migration was completed. Only for the delta, you can run the replication from Employee Central to SAP
S∕4HANA, during which you can check for any errors and resolve the errors before the actual replication.
● In the web service-based data replication you can schedule the job in background for mass replication of
employees, which requires less manual effort. This makes the scheduling of the replication job easier. In
contrast, in the CSV-based data replication mode, to schedule the background job, you need to choose the
Application Server option, where all the CSV files will be downloaded to a pre-defined location in the
Application Server.
● The complete metadata of all the web service entities can be imported together from Employee Central to
SAP S∕4HANA in a single execution of the metadata import program. The ODate Metadata XML file in
Employee Central contains the complete metadata details including all attributes, such as is mandatory,
data type, and so on. In contrast, in the CSV-based data replication mode, you need to import the metadata
of all the entities individually. The Employee Central field level attributes are not available in the CSV
metadata files.

Parent topic: Migrating Data from SAP S∕4HANA to Employee Central [page 21]

Related Information

Sequence of Data Extraction and Import Steps for Different Object Types [page 21]
Importing Organizational Data into Employee Central [page 24]
Importing Employee Data into Employee Central [page 25]
Migrating Foundation Objects to Employee Central [page 27]
Migrating Pay Calendar to Employee Central [page 44]
Migrating Employee Master Data from Third-Party Systems [page 49]

4.7 Migrating Employee Master Data from Third-Party

Systems
You might want to migrate employee master data from other systems, such as non-HCM or third-party
systems, as well as from SAP S∕4HANA system to Employee Central.

During migration, you want to consider using employee master data from third-party systems to migrate the
data to Employee Central. You can do either of the following:

● You can either consider migrating some entities from the third-party system and the remaining entities
from the SAP S∕4HANA system. You can migrate the relevant Employee Central entity data from third-party
system using CSV files. And you can run the migration for the remaining entities using the data migration
tool. The employee identifier fields in Employee Central, user-id and person-id-external, have to be same in
both the data migration tool and in the CSV file-based migration from the third-party system. Meaning, the
third-party CSV files should be imported to Employee Central with the same user-id and person-id-external.

 Note

The time segments of related entities that appear in the same portlet in Employee Central, such as
compensation and recurring pay components, personal info and global info, payment info details and

Migrating Data from SAP S/4HANA On Premise to Employee Central Using Infoporter
Migrating Data from SAP S∕4HANA to Employee Central PUBLIC 49
 county specific payment info details, need to be in sync to enable successful imports into Employee
Central. That's why we recommend that you use the third-party migration via CSV file-based imports
either for all related entities belonging to the same portlets in Employee Central or for none of them.

 Example

The compensation entity has this time slice: January 1, 2012 to December 31, 9999. The recurring pay
components entity has this time slice: January 1, 2014 to December 31, 9999. If you import
compensation information using the data migration tool and recurring information from a third-party
system, you need to manually synchronize the time segments accordingly.

● You can populate some fields of an Employee Central entity from a third-party system and the remaining
fields of the same entity from SAP S∕4HANA system. In this scenario, you can store the data of the fields
from the third-party system using a custom table in the SAP S∕4HANA system. Then you can use the field
mapping BAdI ( EX_ECPAO_EMP_DATA_EXTRACT_OUT) to read the custom table and populate in the
relevant fields of the Employee Central entities.

Parent topic: Migrating Data from SAP S∕4HANA to Employee Central [page 21]

Related Information

Sequence of Data Extraction and Import Steps for Different Object Types [page 21]
Importing Organizational Data into Employee Central [page 24]
Importing Employee Data into Employee Central [page 25]
Migrating Foundation Objects to Employee Central [page 27]
Migrating Pay Calendar to Employee Central [page 44]
Advantages of Web Service-Based Data Transfer for Migration [page 48]

Migrating Data from SAP S/4HANA On Premise to Employee Central Using Infoporter
50 PUBLIC Migrating Data from SAP S∕4HANA to Employee Central
5 HR Business Processes in Employee Data
Migration

Find out how the HR business processes work when you use the employee data migration.

The following topics describes the behavior when you have not activated the switch ERP to EC: Additional
Events Records in the view V_ECPAO_CONSTANT.

Employee Hired in SAP S∕4HANA [page 51]

You can migrate an employee hired in SAP S∕4HANA to Employee Central.

Employee Rehired in SAP S∕4HANA [page 53]

You rehire an employee in SAP S∕4HANA system and migrate the employee's master data to Employee
Central.

Employee Transferred in SAP S∕4HANA [page 55]

You can migrate an employee which has been transferred in SAP S∕4HANA system.

Employee in International Transfer [page 56]

You can migrate an employee which has an international transfer in SAP S∕4HANA system from one
country to another country.

Employee Having Global Assignment in SAP S∕4HANA [page 58]

You can migrate an employee having global assignment in SAP S∕4HANA system.

Employee Having Concurrent Employment in SAP ERP HCM [page 60]

You can migrate an employee who has several personnel assignments.

Employee Terminated in SAP S∕4HANA [page 60]

You can migrate an employee who has been terminated in SAP S∕4HANA system.

5.1 Employee Hired in SAP S∕4HANA

You can migrate an employee hired in SAP S∕4HANA to Employee Central.

In Employee Central, the personnel number (PERNR) is mapped to the user_id field and the central person (CP)
is mapped to the person_id_external field. The employee's data is stored in Employee Central according to the
field mapping that you have defined in Customizing. For more information about the Customizing settings, see
the Replicating Employee Data from SAP ERP HCM to Employee Central integration guide. Find the most
current version of this guide at http://help.sap.com/hr_ecintegration.

 Note

In SAP S∕4HANA, you can define how the hire date is determined using the Rule for Determining Entry Date
(ENTRY) feature. The employee's hire date provided by this feature is replicated to Employee Central.

If you have stored your employees' data in SAP S∕4HANA for several years already and want to start the
employee master data replication from SAP S∕4HANA to Employee Central at a certain point in time, you can

Migrating Data from SAP S/4HANA On Premise to Employee Central Using Infoporter
HR Business Processes in Employee Data Migration PUBLIC 51
define a cutoff date. If you use the cutoff date, the Hire Date and Original Start Date fields in Employee Central
are filled in different ways, depending on whether the employee’s hire date is before or after the cutoff date:

● If the cutoff date is before the hire date in SAP S∕4HANA, the Hire Date and Original Start Date fields in
Employee Central are both filled with the SAP S∕4HANA hire date.

Figure 6: Cutoff Date is Before Hire Date

The employee's data is extracted starting with the hire date for all effective-dated entities, including Job
Info (Job History) and also for Non-Recurring Pay Components.
● If the cutoff date is after the hire date in SAP S∕4HANA, the SAP S∕4HANA hire date is mapped to the
Original Start Date field and the cutoff date is mapped to the Hire Date field in Employee Central.
Since this is not a usual hire in Employee Central (because the employee was already hired before the
cutoff date in SAP S∕4HANA), a Hire event with the PSEUDO_HIRE event reason is carried out.

Figure 7: Cutoff Date is After Hire Date

The employee's data is extracted starting with the cutoff date for all effective-dated entities, including Job
Info (Job History) and also for Non-Recurring Pay Components.
● If the hire date is before the cutoff date and data is changed in SAP S∕4HANA before the cutoff date, the
SAP S∕4HANA hire date is mapped to the Original Start Date field and the cutoff date is mapped to the Hire

Migrating Data from SAP S/4HANA On Premise to Employee Central Using Infoporter
52 PUBLIC HR Business Processes in Employee Data Migration
 Date field in Employee Central. The employee has only one Job Information record in Employee Central
representing the data valid at the cutoff date.
Also in this case a Hire event with the PSEUDO_HIRE event reason is carried out in Employee Central.

Figure 8: Cutoff Date is After Hire Date

The employee's data is extracted starting with the cutoff date for all effective-dated entities, including Job
Info (Job History) and also for Non-Recurring Pay Components.

Parent topic: HR Business Processes in Employee Data Migration [page 51]

Related Information

Employee Rehired in SAP S∕4HANA [page 53]

Employee Transferred in SAP S∕4HANA [page 55]
Employee in International Transfer [page 56]
Employee Having Global Assignment in SAP S∕4HANA [page 58]
Employee Having Concurrent Employment in SAP ERP HCM [page 60]
Employee Terminated in SAP S∕4HANA [page 60]

5.2 Employee Rehired in SAP S∕4HANA

You rehire an employee in SAP S∕4HANA system and migrate the employee's master data to Employee Central.

When you try to hire a person in SAP S∕4HANA, a duplicate check is carried out. If an employee with the same
name and birth date already existed before, you have to carry out a rehire action instead of the hire action.
When you rehire an employee, he or she gets the same personnel number (PERNR) as before, which is assigned
to the same central person (CP). Once the employee is rehired, you can migrate the employee's master data to
Employee Central.

Migrating Data from SAP S/4HANA On Premise to Employee Central Using Infoporter
HR Business Processes in Employee Data Migration PUBLIC 53
If you use the cutoff date, the following situations can occur:

● If the cutoff date is after the rehire date, meaning, the employee was hired, terminated, and then rehired in
SAP S∕4HANA before the cutoff date, the first hire date (first entry into the company) is mapped to the
Original Start Date field in Employee Central. The cutoff date is mapped to the Hire Date field in Employee
Central. You can still use the date of the employee's first entry into the company to calculate, for example,
the employee's seniority, since this date is stored in the Original Start Date field.
Since this is not a usual hire in Employee Central (because the employee was already hired before), a Hire
event with the PSEUDO_REHIRE event reason is carried out. For more information about the event reasons,
see the Replicating Employee Data from SAP ERP HCM to Employee Central integration guide. Find the
most current version of this guide at http://help.sap.com/hr_ecintegration.

Figure 9: Cutoff Date is After Rehire Date

The employee's data is extracted starting with the cutoff date for all effective-dated entities, including Job
Info (Job History) and also for Non-Recurring Pay Components.
● When an employee is rehired after the termination date and the cutoff date is between termination date
and rehire date, then job information records will be extracted from the rehire date with PSEUDO_REHIRE
event reason.
The first hire date (first entry into the company) is mapped to the Original Start Date field and the rehire
date is mapped to the Hire Date field of Employment Info template in Employee Central.

Migrating Data from SAP S/4HANA On Premise to Employee Central Using Infoporter
54 PUBLIC HR Business Processes in Employee Data Migration
 Figure 10: Cutoff Date is Before Rehire Date

The employee's data is extracted starting with the rehire date for all effective-dated entities, including Job
Info (Job History) and also for Non-Recurring Pay Components.
● If the cutoff date is after the termination date and the employee is not rehired, no data is extracted for all
effective-dated templates and the Non-Recurring Pay Components template.

Parent topic: HR Business Processes in Employee Data Migration [page 51]

Related Information

Employee Hired in SAP S∕4HANA [page 51]

Employee Transferred in SAP S∕4HANA [page 55]
Employee in International Transfer [page 56]
Employee Having Global Assignment in SAP S∕4HANA [page 58]
Employee Having Concurrent Employment in SAP ERP HCM [page 60]
Employee Terminated in SAP S∕4HANA [page 60]

5.3 Employee Transferred in SAP S∕4HANA

You can migrate an employee which has been transferred in SAP S∕4HANA system.

When you carry out an organizational reassignment for an employee whose data is mastered in SAP ERP HCM,
the Organizational Reassignment (0001) infotype is changed. An organizational reassignment means that:

● The employee’s country assignment and personnel number (PERNR) stay the same
● Only one personnel number exists for the employee

Migrating Data from SAP S/4HANA On Premise to Employee Central Using Infoporter
HR Business Processes in Employee Data Migration PUBLIC 55
You can migrate the changes regarding the organizational assignment to Employee Central. In Employee
Central, a Data Change event with the DATAREORG event reason is carried out and a new Job Information record
is created. The date of the organizational reassignment in SAP ERP HCM is used as the effective start date of
this Job Information record.

Parent topic: HR Business Processes in Employee Data Migration [page 51]

Related Information

Employee Hired in SAP S∕4HANA [page 51]

Employee Rehired in SAP S∕4HANA [page 53]
Employee in International Transfer [page 56]
Employee Having Global Assignment in SAP S∕4HANA [page 58]
Employee Having Concurrent Employment in SAP ERP HCM [page 60]
Employee Terminated in SAP S∕4HANA [page 60]

5.4 Employee in International Transfer

You can migrate an employee which has an international transfer in SAP S∕4HANA system from one country to
another country.

When you transfer an employee in SAP ERP HCM from one country to another, you usually carry out a Leaving
action in the original country and a Hiring action in the new country. This means that the employee gets a new
personnel number (PERNR) which is assigned to the same central person (CP).

When extracting data, the Employee Data Extraction (ECPAO_EMPL_EXTRACTION) program analyzes the
personnel numbers assigned to one central person. The personnel numbers are handled together and the data
of both is transferred to the same Job Information record in Employee Central if the following conditions are
fulfilled for both personnel numbers:

● They are assigned to different countries.

● Only one of them is active.
● The Leaving and Hiring actions were carried out for them.

In Employee Central, a Transfer event is carried out with an international transfer event reason.

You can create new employment for the international transfer. For more details, refer the Defining Employee
Data-Related Settings for Your Employee Central Company topic in the Replicating Employee Data from SAP
ERP HCM to Employee Central guides. You should always create new employment for international transfer in
order to streamline the end-to-end replication process of a person having multipe contracts.

After the migration process from SAP S∕4HANA if you will also be replicating the employees back from
Employee Central to SAP S∕4HANA, then we recommend you to always create a new employment for
international transfer during migration.

When the centralized services switch in Employee Central is enabled, the isRehire field is set as true or false for
the international transfer scenario. The isRehire field is considered as a standard field and the value is set as

Migrating Data from SAP S/4HANA On Premise to Employee Central Using Infoporter
56 PUBLIC HR Business Processes in Employee Data Migration
false for the first employment and true for the second employment (rehire) record. In case this field is not sent,
then the secondary assignments are created in EC, which is not intended for international transfer. And this
works only with option Create New Employment in the company settings. For more information on the IsRehire
field, refer the Non-Configurable (Standard) Mapping of SAP ERP HCM Fields to Employee Central Fields topic in
the Related Information section.

 Note

The original country and the new country can be mastered in one SAP S∕4HANA system or in different SAP
S∕4HANA systems. The assignment in the new country can start immediately after the assignment in the
original country has ended, or there can be a gap between them. You only need to make sure that the
employee's personnel numbers are always assigned to one and the same central person.

 Note

If there are more than two multiple contracts for an employee (starting after the earliest transfer date)
involving two PERNRs, then this scenario is not supported. This can include scenarios involving
international transfer. For example:

● There is a global assignment from PERNR 1 to PERNR 2 (host PERNR is terminated when global
assignment starts) followed by international transfer from PERNR 2 to PERNR 1 (which is rehired). In
this case if the first HR process happens before the earliest transfer date, then it would be ignored and
only the international transfer from country 2 to country 1 will be considered. The earliest transfer date
must be after the termination date of PERNR 1 in these cases.
● Multiple contracts involving different types of HR processes like Global Assignment, International
Transfer and Concurrent employment for the same employee is not supported.

When you enable the ERP to EC: Determine Personal Data of Global Employees switch in the
V_ECPAO_CONSTANT view, the following options are applicable:

● When there is a global transfer from PERNR 1 to PERNR 2, the personal information (infotype 0002) and
address details (infotype 0006) from both the PERNR's are replicated based on the earliest transfer date.
● Email address and phone number of an employee would be extracted from the employee who is active. If
there is no data available for the active assignment, then the system will get the information from the first
assignment before International Transfer mapped with the same person.
● Biographical information of an employee would be extracted based on which assignment is active.
● For National ID information block, system will extract both the assignment data.

Parent topic: HR Business Processes in Employee Data Migration [page 51]

Related Information

Employee Hired in SAP S∕4HANA [page 51]

Employee Rehired in SAP S∕4HANA [page 53]
Employee Transferred in SAP S∕4HANA [page 55]
Employee Having Global Assignment in SAP S∕4HANA [page 58]
Employee Having Concurrent Employment in SAP ERP HCM [page 60]
Employee Terminated in SAP S∕4HANA [page 60]

Migrating Data from SAP S/4HANA On Premise to Employee Central Using Infoporter
HR Business Processes in Employee Data Migration PUBLIC 57
Non-Configurable (Standard) Mapping of SAP ERP HCM Fields to Employee Central Fields

5.5 Employee Having Global Assignment in SAP S∕4HANA

You can migrate an employee having global assignment in SAP S∕4HANA system.

In SAP S∕4HANA, you can store information about an employee's global assignment in the following infotypes:

● To determine which is the host and which is the home assignment, you can use the Details on Global
Assignment (0710) infotype.
● To determine which personnel number is used to send biographical and personal information to Employee
Central, you can use the Main Personnel Assignment (0712) infotype with the SuccessFactors (SFSF)
subtype.

 Note

If the planned end date in the 0710 Infotype is greater than the actual termination date, then the
system will consider the termination date of an employee from the Infotype 0000 – Actions. But if the
planned end date in the 0710 Infotype is less than the actual termination date, then the system will
consider only the Infotype 0710 – Planned End Date, as this is a data issue. Hence you will have to
extend the end date of the employee in Infotype 0710.

The data from both the host and the home assignments is migrated to Employee Central. The second
assignment is sent using a separate API. In Employee Central, the employee's biographical and personal
information is taken from the personnel number that you have marked as the main personnel assignment in
SAP S∕4HANA.

If you've defined a cutoff date for data replication, this can affect the start date of the global assignment: If the
cutoff date is later than the actual start date of the global assignment, the cutoff date is used. If the cutoff date
is between the start date and the end date of the host assignment, the Job Information record for the host
assignment is transferred to Employee Central using the PSEUDO_ADDGA event reason for the Add Global
Assignment event.

 Note

If there are more than two multiple contracts for an employee (starting after the earliest transfer date)
involving two PERNR's, then this scenario is not supported. This can include the scenario involving global
assignment. For example: There is a global assignment from PERNR 1 to PERNR 2 (which is terminated
when the assignment period ends) then there is an international transfer to the second country from
PERNR 1 to PERNR 2 (which is rehired). In this case if the global assignment happens before the earliest
transfer date, then this would be ignored and only the international transfer from country 1 to country 2 will
be considered.

When you enable the ERP to EC : Determine Personal Data of Global Employees switch in the
V_ECPAO_CONSTANT view, the following options are applicable:

● When there is a global assignment from PERNR 1 to PERNR 2, the personal information (infotype 0002)
and address details (infotype 0006) from both the PERNR's are replicated based on the earliest transfer
date. In this case, you have to maintain infotype 0712 (main personnel assignment) for the 2nd PERNR and
maintain the home PERNR as the leading PERNR during the global assignment period. Based on this, the

Migrating Data from SAP S/4HANA On Premise to Employee Central Using Infoporter
58 PUBLIC HR Business Processes in Employee Data Migration
 host address will be created in EC with address type host for the host PERNR along with the home address,
which is mapped with the home PERNR.

 Note

From EC, you will have to make sure that the host address type is available in the EC picklist.

● For global assignment user, if the permanent residence address is maintained for both the assignments
(home & host), then the home PERNR would hold the home address type and host PERNR would hold the
host address type in the EC system.

 Note

Emp_users_sys_id field should be added into perAddress enitity with the configurations: Enabled =
True, Visibility = view & allow import = Yes in the Employee Central system. This field has to be included
in the view cluster (VC_ECPAO_MAP) field mapping for address entity.

● Email address and phone number of an employee would be extracted from the employee who is active. If
both the PERNR's are active then system will migrate the host PERNR's email address and phone number.
If there is no data available for the host PERNR, then the system will get the information from the other
PERNR mapped with the same person. For global assignment, system will try to send the host PERNR's
email address and phone number based on the infotype 0712.
● Biographical information of an employee would be extracted based on which assignment is active. If both
home and host assignment is active, then the home PERNR data would be considered for biographical
information during the extraction process.
● For National ID information portlet, system will extract both the assignment data.

 Note

If you have not maintained the infotype 0712 (main personnel assignment), then the host address type for
the host PERNR would not be created. Instead home sub-type is created for both home and host PERNR.
Similarly for biographical, email address, and phone number of an employee will be extracted only from the
home PERNR even though the host is active.

 Note

When global assignment configuration object is enabled in Employee Central to create global assignment
events like Away on Global Assignment and Back from Global Assignment, following points to be considered:

● Equivalent custom actions for the above events have to be explicitly created for the pernrs in the ERP
system.
● Additional value mapping for the events have to be done : Eg: custom Action for Away on Global
Assignment has to be mapped to event AGA(Away on global Assignment) on EC.

If the above actions are not performed, then whenever there is a change from ERP sent to home
assignment or when the replication from ERP is triggered again, the automatic events created in EC will be
deleted as the upsert is a full purge.

Parent topic: HR Business Processes in Employee Data Migration [page 51]

Migrating Data from SAP S/4HANA On Premise to Employee Central Using Infoporter
HR Business Processes in Employee Data Migration PUBLIC 59
Related Information

Employee Hired in SAP S∕4HANA [page 51]

Employee Rehired in SAP S∕4HANA [page 53]
Employee Transferred in SAP S∕4HANA [page 55]
Employee in International Transfer [page 56]
Employee Having Concurrent Employment in SAP ERP HCM [page 60]
Employee Terminated in SAP S∕4HANA [page 60]

5.6 Employee Having Concurrent Employment in SAP ERP

HCM

You can migrate an employee who has several personnel assignments.

In SAP ERP HCM, an employee who has several personnel assignments (personnel numbers) with the
employment status Active within the same country is considered as concurrently employed. You can migrate
his or her data to Employee Central.

In Employee Central, an employment is created for each of the employee's personnel assignments.

Parent topic: HR Business Processes in Employee Data Migration [page 51]

Related Information

Employee Hired in SAP S∕4HANA [page 51]

Employee Rehired in SAP S∕4HANA [page 53]
Employee Transferred in SAP S∕4HANA [page 55]
Employee in International Transfer [page 56]
Employee Having Global Assignment in SAP S∕4HANA [page 58]
Employee Terminated in SAP S∕4HANA [page 60]

5.7 Employee Terminated in SAP S∕4HANA

You can migrate an employee who has been terminated in SAP S∕4HANA system.

When you terminate an employee in SAP S∕4HANA, the information about the termination is migrated to
Employee Central if the earliest transfer date is before the termination date. This ensures that the employee is
also terminated in Employee Central and becomes inactive there. When you carry out the Leaving action in SAP
S∕4HANA, the employee's employment status is changed to Withdrawn. When the termination is replicated to

Migrating Data from SAP S/4HANA On Premise to Employee Central Using Infoporter
60 PUBLIC HR Business Processes in Employee Data Migration
Employee Central, a Termination event with the Termination event reason is carried out and a new Job
Information record is created.

 Note

When an employee is terminated, his or her assigned position, job code, division, department, business
unit, and cost-center information remains in Job Information in Employee Central. In the SAP S∕4HANA
system, however, a terminated employee has a default position assigned, and job, organizational unit, and
cost-center assignments are removed from the Organizational Assignment (0001) infotype. If this
information was replicated to Employee Central, the assignments are also removed from the employee's
Job Information. This is the reason why the SAP S∕4HANA system migrates the corresponding assignments
from the employee's last active Organizational Assignment record instead of from the terminated one.

Parent topic: HR Business Processes in Employee Data Migration [page 51]

Related Information

Employee Hired in SAP S∕4HANA [page 51]

Employee Rehired in SAP S∕4HANA [page 53]
Employee Transferred in SAP S∕4HANA [page 55]
Employee in International Transfer [page 56]
Employee Having Global Assignment in SAP S∕4HANA [page 58]
Employee Having Concurrent Employment in SAP ERP HCM [page 60]

Migrating Data from SAP S/4HANA On Premise to Employee Central Using Infoporter
HR Business Processes in Employee Data Migration PUBLIC 61
6 Starting Data Replication from Employee
Central to the SAP S∕4HANA System

Once you've finished data migration from the SAP S∕4HANA system to Employee Central, you can start
replicating employee master data from Employee Central to SAP S∕4HANA.

Some things to remember:

● The employee key mapping table should be filled before you start replicating data from Employee Central
to SAP S∕4HANA.
For more information, see the Replicating Employee Data from SAP S∕4HANA to Employee Central
integration guide. Find the most current version of this guide in SAP Help Portal at http://help.sap.com/
hr_ecintegration.
● Set an appropriate full transmission start date (FTSD), in the properties of the process that replicates
employee master data from Employee Central to SAP S∕4HANA. For more information refer to section
Setting up the Middleware in the Replicating Employee Master Data from Employee Central to SAP S∕4HANA
integration guide. Find the most current version of this guide in SAP Help Portal at http://help.sap.com/
hr_ecintegration.
The FTSD is the earliest extraction date. Data in Employee Central that has a last modified date that is
before FTSD isn't replicated to the SAP S∕4HANA system. This way, the FTSD helps you to control the
volume of data that is to be transferred from Employee Central to SAP S∕4HANA.
You must not choose a FTSD that is before the cutover date for your migration project. You can set any
FTSD that is after the cutover date and suits your specific business requirements.
● After the cutover date for data migration, Employee Central creates a new employee using an event reason
with the Hire event. If you replicate this employee's data back to SAP S∕4HANA, the SAP S∕4HANA system
tries to initiate a new Hiring personnel action since the Hire event from Employee Central is mapped to the
Hiring action in SAP S∕4HANA. But the employee already exists in SAP S∕4HANA, so a Hiring action was
already carried out for him or her. A second Hiring action cannot be triggered, therefore the employee data
replication from Employee Central to SAP S∕4HANA shows an error for this employee.
To prevent this kind of error, you can create a new event reason such as Cutover. Assign the Hire event to
this event reason. Also specify the SAP S∕4HANA action to be carried out in the Payroll Event field of the
event reason.

Migrating Data from SAP S/4HANA On Premise to Employee Central Using Infoporter
62 PUBLIC Starting Data Replication from Employee Central to the SAP S∕4HANA System
 Figure 11: Event Reason in Employee Central

Figure 12: Action Type in the SAP S∕4HANA System

At cutover date, you can add this event reason to the employees who were earlier hired in the SAP
S∕4HANA system. This has the following effects:
○ The Job History record of the employee can be created without issues since the Hire event is set for the
event reason.
○ The employee can be replicated without issues to the SAP S∕4HANA system since you've specified a
specific action in the Payroll Event field, which is then used in SAP S∕4HANA instead of the Hiring
action.

 Example

Employee 12345 was hired in SAP S∕4HANA on January 10, 2012. The cutover date for data migration
from SAP S∕4HANA to Employee Central is July 1, 2015. So employee 12345 has a first Job History
record in Employee Central starting with July 1, 2015. This Job History record is created using a specific
Cutover event reason. Now you replicate this employee's data from Employee Central to SAP S∕4HANA.

Migrating Data from SAP S/4HANA On Premise to Employee Central Using Infoporter
Starting Data Replication from Employee Central to the SAP S∕4HANA System PUBLIC 63
 The data replication will set the action to be carried out in SAP S∕4HANA automatically since you’ve
mapped the desired action to the Payroll Event field of the Cutover event reason in Employee Central.

Note that if you don't specify the SAP S∕4HANA action in the Payroll Event field of the Cutover event
reason in Employee Central, employee data replication from Employee Central to SAP S∕4HANA shows
an error because then the SAP S∕4HANA system tries to carry out the Hiring action. But the Hiring
action was already carried out on January 10, 2012 for employee 12345 and can't be carried out again.

Migrating Data from SAP S/4HANA On Premise to Employee Central Using Infoporter
64 PUBLIC Starting Data Replication from Employee Central to the SAP S∕4HANA System
7 Validating the Migration

Make some checks to validate whether data migration from the SAP S∕4HANA system to Employee Central was
successful.

Checking data migration from SAP S∕4HANA to Employee Central

In your SAP S∕4HANA system, go to the Analyze Application Log (SLG1) transaction or you can run the (SLGD)
transaction to display the data in text format and export the data into an excel file or in other formats. After
executing the transaction you can choose the required format in which you want to export the log file check the
following application logs:

● For employee data: ECPAO object and subobject

● For organizational data: ECPAO object and ECPAO_OM subobject

Checking employee master data replication from Employee Central to SAP

S∕4HANA

In your SAP S∕4HANA system, check the following:

● Go to the Analyze Application Log (SLG1) transaction and check the error log for the PAOC_SFI_PA object.
The new Analyze Inventory of Replicated Employee Data (ECPAO_EMPL_INVENTORY_ALV) program and
Replicated Organizational Data (ECPAO_OM_INVENTORY_ALV) is available to check the inventory tables.
The new inventory tables are updated with the replication information per Employee Central entity. The
Analyze Application Log (SLG1) transaction now shows the messages per employee/personnel number.
● Go to the Web Service Utilities (SRTUTIL) transaction.
○ In the error log, check the messages for the II_PAOCF_EC_EMPLOYEE_MASTER_DA interface.
○ In the message monitor, check the messages for the EmployeeMasterDataReplicationRequest_In
interface.
For more information about checking data replication results refer to the Replicating Employee Master Data
from Employee Central to SAP S∕4HANA integration guide. Find the most current version of this guide in
SAP Help Portal at http://help.sap.com/hr_ecintegration.

 Note

Depending on your system configuration, the SRTUTIL transaction might not be available. If it's not,
use the Integration Engine: Monitoring (SXMB_MONI) transaction instead.

Migrating Data from SAP S/4HANA On Premise to Employee Central Using Infoporter
Validating the Migration PUBLIC 65
Important Disclaimers and Legal Information

Hyperlinks
Some links are classified by an icon and/or a mouseover text. These links provide additional information.
About the icons:

● Links with the icon : You are entering a Web site that is not hosted by SAP. By using such links, you agree (unless expressly stated otherwise in your
agreements with SAP) to this:

● The content of the linked-to site is not SAP documentation. You may not infer any product claims against SAP based on this information.
● SAP does not agree or disagree with the content on the linked-to site, nor does SAP warrant the availability and correctness. SAP shall not be liable for any
damages caused by the use of such content unless damages have been caused by SAP's gross negligence or willful misconduct.

● Links with the icon : You are leaving the documentation for that particular SAP product or service and are entering a SAP-hosted Web site. By using such
links, you agree that (unless expressly stated otherwise in your agreements with SAP) you may not infer any product claims against SAP based on this
information.

Videos Hosted on External Platforms

Some videos may point to third-party video hosting platforms. SAP cannot guarantee the future availability of videos stored on these platforms. Furthermore, any
advertisements or other content hosted on these platforms (for example, suggested videos or by navigating to other videos hosted on the same site), are not within
the control or responsibility of SAP.

Beta and Other Experimental Features

Experimental features are not part of the officially delivered scope that SAP guarantees for future releases. This means that experimental features may be changed by
SAP at any time for any reason without notice. Experimental features are not for productive use. You may not demonstrate, test, examine, evaluate or otherwise use
the experimental features in a live operating environment or with data that has not been sufficiently backed up.
The purpose of experimental features is to get feedback early on, allowing customers and partners to influence the future product accordingly. By providing your
feedback (e.g. in the SAP Community), you accept that intellectual property rights of the contributions or derivative works shall remain the exclusive property of SAP.

Example Code
Any software coding and/or code snippets are examples. They are not for productive use. The example code is only intended to better explain and visualize the syntax
and phrasing rules. SAP does not warrant the correctness and completeness of the example code. SAP shall not be liable for errors or damages caused by the use of
example code unless damages have been caused by SAP's gross negligence or willful misconduct.

Bias-Free Language
SAP supports a culture of diversity and inclusion. Whenever possible, we use unbiased language in our documentation to refer to people of all cultures, ethnicities,
genders, and abilities.

Migrating Data from SAP S/4HANA On Premise to Employee Central Using Infoporter
66 PUBLIC Important Disclaimers and Legal Information
Migrating Data from SAP S/4HANA On Premise to Employee Central Using Infoporter
Important Disclaimers and Legal Information PUBLIC 67
www.sap.com/contactsap

© 2022 SAP SE or an SAP affiliate company. All rights reserved.

No part of this publication may be reproduced or transmitted in any form

or for any purpose without the express permission of SAP SE or an SAP
affiliate company. The information contained herein may be changed
without prior notice.

Some software products marketed by SAP SE and its distributors

contain proprietary software components of other software vendors.
National product specifications may vary.

These materials are provided by SAP SE or an SAP affiliate company for

informational purposes only, without representation or warranty of any
kind, and SAP or its affiliated companies shall not be liable for errors or
omissions with respect to the materials. The only warranties for SAP or
SAP affiliate company products and services are those that are set forth
in the express warranty statements accompanying such products and
services, if any. Nothing herein should be construed as constituting an
additional warranty.

SAP and other SAP products and services mentioned herein as well as
their respective logos are trademarks or registered trademarks of SAP
SE (or an SAP affiliate company) in Germany and other countries. All
other product and service names mentioned are the trademarks of their
respective companies.

Please see https://www.sap.com/about/legal/trademark.html for

additional trademark information and notices.

THE BEST RUN