PUBLIC

Document Version: 1H 2024 – 2024-08-14

Implementing Data Migration and Replication to

Employee Central
© 2024 SAP SE or an SAP afliate company. All rights reserved.

THE BEST RUN

Content

1 Introduction to Data Migration and Replication from SAP S∕4HANA to Employee Central. . . . . . . . 4
1.1 Before Starting: Am I reading the right documentation?. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5
1.2 Target Group of This Document. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6
1.3 Your Integration Team. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6

2 Data Migration and Replication to Employee Central. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8

2.1 Prerequisites and Basic Steps for Implementing Data Migration and Replication to Employee Central
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .8
Basic Steps in SAP SuccessFactors. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .8
Basic Steps in SAP Cloud Integration. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 15
Basic Steps in SAP S∕4HANA. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 47
2.2 Employee Data. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 59
Preparing the Systems for Employee Data Replication. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .59
Replicating Employee Data from SAP S∕4HANA to Employee Central. . . . . . . . . . . . . . . . . . . . . . . . 68
2.3 Organizational Data. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 270
Replicating Organizational Data from SAP S∕4HANA to Employee Central. . . . . . . . . . . . . . . . . . . . 270
2.4 Foundation Objects. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .349
Replicating Foundation Object Data from SAP S∕4HANA to Employee Central. . . . . . . . . . . . . . . . . 349

3 Migrating Data to Employee Central. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .380

3.1 Employee Data. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 380
Preparing the SAP S∕4HANA System for Data Migration. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 380
Sequence of Data Extraction and Import Steps for Dierent Object Types. . . . . . . . . . . . . . . . . . . . 382
Importing Organizational Data into Employee Central. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 384
Importing Employee Data into Employee Central. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 385
Migrating Work Schedules to Employee Central. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 386
Employee Having Global Assignment in SAP ERP HCM. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 390
Advantages of Web Service-Based Data Transfer for Migration. . . . . . . . . . . . . . . . . . . . . . . . . . . . 392
Migrating Pay Calendar to Employee Central. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 392
Migrating Foundation Objects to Employee Central. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 397
Migrating Employee Master Data from Third-Party Systems. . . . . . . . . . . . . . . . . . . . . . . . . . . . . 406
Starting Data Replication from Employee Central to the SAP S∕4HANA System. . . . . . . . . . . . . . . . 407
Validating the Migration. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 409

4 Side-by-Side Deployment Option. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .411

4.1 Introduction to the Side-By-Side Deployment Option. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 411
Business Scenario: Side-by-Side Deployment Option. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .412
4.2 How to Migrate from Talent Hybrid Integration to Integration with Employee Central. . . . . . . . . . . . . . . 413

Implementing Data Migration and Replication to Employee Central

2 PUBLIC Content
 Migrating from Talent Hybrid Integration to ERP Integration when Assignment ID Field is Enabled
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 414
Determining the User ID. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 420
Determining the Person ID. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 421
Handling the Dierent Integration Scenarios. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 422
Switching from One Replication to the Other. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 423
Making Additional Customizing Settings. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 424
Changing the Employment Status to Inactive Before and to Active Again After Switching from One
Replication to the Other. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 424
Handling Concurrent Employment and Global Assignment Situations. . . . . . . . . . . . . . . . . . . . . . . 425
4.3 HR Business Processes for the Side-by-Side Deployment Option in Employee Data Migration. . . . . . . . 426
Prerequisites and Restrictions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 427
Hire. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 428
Rehire. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .432
Transfer. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 435
International Transfer. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 437
Global Assignment. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 441
Concurrent Employment. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 446
Termination. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 451
4.4 Special Use Cases in Data Replication to Employee Central. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .452
How to Use Country Filtering for the Side-by-Side Deployment Option. . . . . . . . . . . . . . . . . . . . . . 453
How to Use SAP SuccessFactors Compensation Together with the Side-by-Side Deployment
Option. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 453
How to Use Employee Central Advanced Reporting in the Side-by-Side Deployment Option. . . . . . . 455
Supporting the Migration of Long Term Absence Records. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 458

5 Change History. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 460

Implementing Data Migration and Replication to Employee Central

Content PUBLIC 3
1 Introduction to Data Migration and
Replication from SAP S∕4HANA to
Employee Central

Implement SAP SuccessFactors Employee Central integration with SAP Human Capital Management for SAP S/
4HANA to migrate employee and organizational data from SAP S∕4HANA to SAP SuccessFactors Employee Central
once, for example, if you want to switch from SAP S∕4HANA to Employee Central to manage your employees. In
addition, you can also replicate the data regaulary to use Employee Central as the cloud-based core HR system for
a subset of employees and retain SAP S∕4HANA as the core HR system for another subset of employees.

Use this integration guide to set up a regular or one-time replication of employee-related data from the SAP
S∕4HANA system to Employee Central.

 Remember

The SFSF EC S4 HCM INTEGRATION (ECS4HCM) add-on is intended for integration with SAP S/4HANA
(on-premise edition) or SAP S/4HANA Cloud Private Edition but not for integration with SAP S/4HANA
Cloud Public Edition. Use SAP Master Data Integration instead for SAP SuccessFactors integration with SAP S/
4HANA Cloud Public Edition. For more information, refer to Integrating SAP SuccessFactors Employee Central
with SAP Master Data Integration.

You can also use SAP Master Data Integration for integration with SAP S/4HANA Cloud Private Edition.
However, this requires that no HR processes run in SAP S/4HANA Cloud Private Edition. With SAP Master
Data Integration, only the workforce person is replicated to the SAP S/4HANA system. This is not sufcient to
support HR processes such as payroll.

What Does Data Migration Mean?

You can use the data replication described in this guide to set up a delta-enabled migration to initially move your
employee data from the SAP S∕4HANA system to Employee Central if you want to transition to the core hybrid
deployment option and plan to use Employee Central as the master system for employee-related data in the future.

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.

For Which Deployment Option Is this Integration Intended?

The core hybrid deployment option means that Employee Central is used as the system of record holding the
employee data and reporting lines of all employees, but existing processes such as payroll, time management, or
custom HR processes still run in an SAP S∕4HANA system landscape.
Implementing Data Migration and Replication to Employee Central
Introduction to Data Migration and Replication from SAP S∕4HANA to Employee
4 PUBLIC Central
  Restriction

Data replication from SAP S∕4HANA systems to Employee Central is generally available for:

• Existing SAP SuccessFactors customers leveraging SAP SuccessFactors Performance & Goals, SAP
SuccessFactors Succession & Development, Employee Prole and Organization Chart as part of the
Foundational Capabilities, and the related Reporting capabilities.
• Net new SAP SuccessFactors customers who don't use any of the SAP SuccessFactors solutions yet,
but have implemented or plan to implement SAP SuccessFactors Employee Central for parts of their
organization.

1.1 Before Starting: Am I reading the right documentation?

Before you start looking for information in this document, you need to be sure you're looking in the right place.

This document describes how to set up integration between SAP S∕4HANA and SAP SuccessFactors Employee
Central. It assumes that you have a team of experts in place who know their ways in the systems involved in the
integration.

What this document does not describe:

• How to set up and use Employee Central. For example:

• How to congure object types in Employee Central. We tell you which prerequisites object types must
ulll so that they can be replicated between SAP S∕4HANA and Employee Central. For example, whether a
length restriction applies to a specic eld. For basics such as how to restrict the length of a eld, refer to
the Employee Central documentation.
• Why and how to enable Position Management in Employee Central. We tell you what happens in the
integration if Position Management is or is not enabled. For basics such as when and how to enable it, refer
to the Employee Central documentation.
• How to set up and use the SAP S∕4HANA system or the SAP Human Capital Management solution for SAP
S∕4HANA. For example:
• How to use the Customizing Implementation Guide (IMG) in your system. We tell you which customizing
activities and settings are relevant for integration. For basics such as how to make entries in customizing
views or how to implement a Business Add-In, refer to the SAP S∕4HANA documentation.
• How to create a variant for a program or schedule it to be run in the background. We tell you which
programs you need to execute or schedule. For basics such as how to dene variants or background jobs,
refer to the SAP S∕4HANA documentation.
• How to set up and use the middleware. For example:
• How to get started, congure a tenant, or connect a system in SAP Cloud Integration.
• How dierent adapter types work. We tell you which adapters you need when conguring integration ows.
For information about what the dierences between adapter types are, refer to the SAP Cloud Integration
documentation.

Read the following information to learn how to set up and use the products or modules involved in the integration.

Implementing Data Migration and Replication to Employee Central

Introduction to Data Migration and Replication from SAP S∕4HANA to Employee
Central PUBLIC 5
Product / Module Where to Find Information

Employee Central https://help.sap.com/docs/SAP_SUCCESSFACTORS_EM-

PLOYEE_CENTRAL > Implement

SAP S∕4HANA For platform information: https://help.sap.com/docs/

SAP_NETWEAVER > ABAP Platform

For information about SAP S/4HANA: https://help.sap.com/

docs/SAP_S4HANA_ON-PREMISE and SAP Human Capital
Management for SAP S/4HANA

Middleware SAP Cloud Integration

 Note

For information about data purge, refer to the following sections in the SAP SuccessFactors guide Implementing
and Managing Data Protection and Privacy:

• Purge of Employee Central Data Replicated to the Enterprise Resource Planning (ERP) System
• Purge of Data Related to Data Replication to Employee Central in the Enterprise Resource Planning (ERP)
System

1.2 Target Group of This Document

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

The following groups of people will benet from reading this document:

• Implementation partners, consultants, and Product Support, for fast support of customers and prospective
customers
• Cloud operations
• SAP-certied administrators at customer site

1.3 Your Integration Team

The implementation and integration process of SAP SuccessFactors Employee Central with SAP S∕4HANA is a
collaborative eort that leverages the skills of various experts.

You need to pull together a team of experts for your implementation project when integrating SAP SuccessFactors
Employee Central with SAP S∕4HANA.

Implementing Data Migration and Replication to Employee Central

Introduction to Data Migration and Replication from SAP S∕4HANA to Employee
6 PUBLIC Central
The following experts are typically involved in the process:

Expert What the Expert Does

SAP SuccessFactors consultant • Is the main point of contact for the entire implementation
and integration process.
• Ensures that all required system settings for Employee
Central are done.
• Works closely with the SAP S∕4HANA team, to ensure
successful data replication.

SAP Cloud Integration consultant Provides support on setting up the middleware.

SAP HCM for SAP S∕4HANA consultant • Is the main point of contact for the conguration of SAP
HCM for SAP S∕4HANA according to the needs of the
customer.
• Works closely with the SAP SuccessFactors consultant to
ensure successful data replication.

Implementing Data Migration and Replication to Employee Central

Introduction to Data Migration and Replication from SAP S∕4HANA to Employee
Central PUBLIC 7
2 Data Migration and Replication to
Employee Central

2.1 Prerequisites and Basic Steps for Implementing Data

Migration and Replication to Employee Central

Check the prerequisites and complete the basic steps in SAP SuccessFactors, SAP Cloud Integration, and SAP
S∕4HANA to implement data migration and replication to Employee Central.

Basic Steps in SAP SuccessFactors [page 8]

Complete the basic steps in SAP SuccessFactors to implement data migration and replication to Employee
Central.

Basic Steps in SAP Cloud Integration [page 15]

Complete the basic steps in SAP Cloud Integration to implement data migration and replication to
Employee Central.

Basic Steps in SAP S∕4HANA [page 47]

Complete the basic steps in SAP S∕4HANA to implement data migration and replication to Employee
Central.

2.1.1 Basic Steps in SAP SuccessFactors

Complete the basic steps in SAP SuccessFactors to implement data migration and replication to Employee Central.

Making Provisioning Settings in SAP SuccessFactors [page 9]

Enable the features required for integrating SAP SuccessFactors Employee Central with SAP S∕4HANA in
SAP SuccessFactors Provisioning.

Creating the SAP SuccessFactors API User [page 10]

Create the SAP SuccessFactors API user (for example, a user, which is called SFAPI). This user is used in
SAP Cloud Integration and in SAP S∕4HANA.

Creating Permission Group and Permission Role for the SAP SuccessFactors API User [page 11]
Create a permission group and a permission role for the API user so that the permissions required for data
replication from SAP SuccessFactors Employee Central can be granted to this user.

Permissions Required for SAP SuccessFactors API Access [page 12]

Data replication between SAP SuccessFactors Employee Central and the SAP S∕4HANA system requires
administrator and user permissions for SAP SuccessFactors APIs.

Setting SAP SuccessFactors API User Login Exceptions [page 14]

Ensure that the password for your SAP SuccessFactors user doesn’t expire. You can also restrict the user's
access to specic IP addresses.

Implementing Data Migration and Replication to Employee Central

8 PUBLIC Data Migration and Replication to Employee Central
2.1.1.1 Making Provisioning Settings in SAP SuccessFactors

Enable the features required for integrating SAP SuccessFactors Employee Central with SAP S∕4HANA in SAP
SuccessFactors Provisioning.

Procedure

1. Sign in to SAP SuccessFactors Provisioning.

 Remember

As a customer, you don't have access to Provisioning. To complete tasks in Provisioning, contact
your implementation partner or Account Executive. For any non-implementation tasks, contact Product
Support.

2. Select the relevant company name in the List of Companies.

3. Choose Company Settings.
4. Enable the following features by selecting the checkboxes:
• Enable the Attachment Manager
• Employee Prole data audit
• Employee Central Foundation Objects and Enable Translation of Employee Central Foundation Objects
• In the Employee Central section:
• Eective Dated Data Platform and Enable Eective Dated elds in Basic Import
• Employee Central V2
• Enable Global Assignment Management
• Enable Dependents Management
• Enable Position Management
• Enable Business Conguration
• Role-Based Permission
• Enable Generic Objects
• Enable Concurrent Employment Management
• People Prole
• Enable SAP ERP Integration
• Enable Intelligent Services Center (ISC)
• Picklist Management
5. Scroll up and choose Save Feature.
6. In the Conrm Changes dialog box, enter the Company ID and choose Conrm.
7. Scroll down to the Web Services section and enable the SAP SuccessFactors API services required for data
replication by selecting the checkboxes:
• SFAPI (Warning: SFAPI is legacy API technology. Please use OData API instead. Only use SFAPI if you are
using the Compound Employee API.)
• Employee Central SOAP API (Warning: SFAPI is legacy API technology. Please use OData API instead. Only
use SFAPI if you are using the Compound Employee API.)

Implementing Data Migration and Replication to Employee Central

Data Migration and Replication to Employee Central PUBLIC 9
8. Make sure the checkbox for Disable OData API is not selected.
9. Choose Save within the Web Services section.
10. In the Conrm Changes dialog box, enter the company ID and choose Conrm.

Results

The required SAP SuccessFactors services are enabled.

2.1.1.2 Creating the SAP SuccessFactors API User

Create the SAP SuccessFactors API user (for example, a user, which is called SFAPI). This user is used in SAP Cloud
Integration and in SAP S∕4HANA.

Procedure

1. Sign in to SAP SuccessFactors Employee Central.

2. Go to the Admin Center and choose the Import Employee Data admin tool.
3. In Select the action you want to perform, choose Download Template.
4. In Select an Entity, choose Basic Import.
5. Keep the File Encoding as Unicode (UTF-8).
6. Choose Generate Template and save the le on a share.
7. Enter the following information in the le and leave all other elds empty:

Field Name Value

STATUS active

USERID SFAPI

USERNAME SFAPI

ASSIGNMENT_ID_EXTERNAL SFAPI

MANAGER NO_MANAGER

HR NO_HR

 Note

The rst two rows in the le must be header rows. If you want, you can also remove empty columns in order
to make the le easier to read.

8. Save the le.

9. Go back to the Import Employee Data admin tool.

Implementing Data Migration and Replication to Employee Central

10 PUBLIC Data Migration and Replication to Employee Central
 10. In Select the action you want to perform, choose Import Data.
11. In Select an Entity, choose Basic Import.
12. In Choose File, browse for your le.
13. Keep the File Encoding as Unicode (UTF-8).
14. Select the File Locale.
15. Choose Import.

Results

You’ve created a user with the status Active and the user ID, user name, and assignment ID SFAPI.

2.1.1.3 Creating Permission Group and Permission Role for

the SAP SuccessFactors API User

Create a permission group and a permission role for the API user so that the permissions required for data
replication from SAP SuccessFactors Employee Central can be granted to this user.

Procedure

1. Sign in to SAP SuccessFactors Employee Central.

2. Go to the Admin Center and choose the Manage Permission Groups admin tool.
3. Choose Create New and enter the following values:

Field Name User Action and Values

Group Name For example: SFAPI

4. In the Choose Group Members section, assign the SAP SuccessFactors API user you created. To do so, select
the Username category and search for SFAPI.
5. Choose Done.
6. Go back to the Admin Center and choose the Manage Permission Roles admin tool.
7. Choose Create New and enter the following values:

Field Name User Action and Values

Role Name For example: SFAPI

Description For example: API Login Permission

8. Grant this role to the permission group you created (such as SFAPI).
9. Choose Save Changes.

Implementing Data Migration and Replication to Employee Central

Data Migration and Replication to Employee Central PUBLIC 11
10. Go back to the Admin Center and choose the Reset User Passwords admin tool.
11. Search for your SAP SuccessFactors API user by entering the name (such as SFAPI) in Username.
12. Select the user and enter a new password.
13. Choose Reset User Password.
14. Perform a check of your new SAP SuccessFactors API user and password:

a. Log on to SAP SuccessFactors using your new SAP SuccessFactors API user and password.

Use the logon URL of the structure https://<server>.successfactors.com/login you used before.
b. Check whether the logon is successful.

In case you’re asked to reset the initial password during the logon, provide a new password and note it
down.

Results

You now have a group and role for the SAP SuccessFactors API user.

Next Steps

Grant all permissions that are required for integration with SAP S∕4HANA to the permission role and set API login
exceptions for the user (for example, to ensure that their password doesn't expire).

2.1.1.4 Permissions Required for SAP SuccessFactors API

Access

Data replication between SAP SuccessFactors Employee Central and the SAP S∕4HANA system requires
administrator and user permissions for SAP SuccessFactors APIs.

The permissions listed here grant users and administrators access to the SAP SuccessFactors OData API and
SFAPI. SFAPI access includes access to CompoundEmployee API.

Who's This Permission For? Permission Location Permission Name

User General User Permission SFAPI User Login

Administrator Employee Central API Employee Central Foundation SOAP API

Implementing Data Migration and Replication to Employee Central

12 PUBLIC Data Migration and Replication to Employee Central
 Who's This Permission For? Permission Location Permission Name

Administrator Employee Central API Employee Central HRIS SOAP API or

Employee Central Compound Employee
API (restricted access)

 Note
Either grant the Employee Central
HRIS SOAP API permission, to give
the administrator unrestricted ac-
cess to the CompoundEmployee
API. Or grant the Employee Central
Compound Employee API (restricted
access) permission, to restrict the
access to the data of specic em-
ployees. Don't select both permis-
sions for the same permission role.
For more information, refer to Grant-
ing Permissions for Full Access to the
CompoundEmployee API and Grant-
ing Permissions for Restricted Ac-
cess to the CompoundEmployee API
in the Employee Central Compound
Employee API guide.

Administrator Employee Central API Employee Central Compound Employee

API (restricted segment access)

 Note
With this permission, you can fur-
ther restrict either the Employee
Central HRIS SOAP API permission
or the Employee Central Compound
Employee API (restricted access)
permission. The Employee Central
Compound Employee API (restricted
segment access) permission allows
the user with this role to access
CompoundEmployee segments
according to the conguration setup
only. For more information, refer to
Granting Permissions for Segment
Access to the CompoundEmployee
API in the Employee Central Com-
pound Employee API guide.

Administrator Employee Central API Employee Central Foundation OData API

(read-only)

Administrator Employee Central API Employee Central HRIS OData API (read-
only)

Implementing Data Migration and Replication to Employee Central

Data Migration and Replication to Employee Central PUBLIC 13
Who's This Permission For? Permission Location Permission Name

Administrator Employee Central API Employee Central Foundation OData API

(editable)

Administrator Employee Central API Employee Central HRIS OData API

(editable)

Administrator Metadata Framework Admin access to MDF OData API

 Note
This permission is required for snap-
shot pagination. Snapshot pagina-
tion is used in all integration ows
that perform an OData query. This
applies to the following integration
ow:

• Replicate Organizational Objects

from SAP SuccessFactors
Employee Central to SAP ERP or
SAP S4HANA

Related Information

What Are Role-Based Permissions?

2.1.1.5 Setting SAP SuccessFactors API User Login

Exceptions

Ensure that the password for your SAP SuccessFactors user doesn’t expire. You can also restrict the user's access
to specic IP addresses.

Procedure

1. Sign in to SAP SuccessFactors Employee Central.

2. Go to the Admin Center and choose the Password & Login Policy Settings admin tool.
3. Choose Set API login exceptions....
4. Choose Add.
5. Make the following settings:

Implementing Data Migration and Replication to Employee Central

14 PUBLIC Data Migration and Replication to Employee Central
 Field Name User Action and Values

Username Enter the SAP SuccessFactors API user you created

Maximum password age (days) Enter -1

IP address restrictions Enter one or more designated IP addresses or address

ranges from which the API user accesses the API. You can
use this to ensure that the API is only called from designated
sources. If you don’t want to apply any restrictions, enter
0.0.0.0-255.255.255.255.

 Restriction
We don't support domain names in this tool at present.

Results

You’ve congured your SAP SuccessFactors API user in a way that their password won't expire.

2.1.2 Basic Steps in SAP Cloud Integration

Complete the basic steps in SAP Cloud Integration to implement data migration and replication to Employee
Central.

Middleware Content for Data Replication to Employee Central [page 17]

Get an overview of the integration content that's available in SAP Cloud Integration for replicating employee
and organizational data from SAP S∕4HANA to Employee Central and for replication of generic data such as
picklists from Employee Central.

Performing Basic Steps for Using SAP Cloud Integration [page 19]
Ensure that the basic setup is completed before you start conguring SAP Cloud Integration for data
replication from Employee Central to SAP S∕4HANA.

Creating User Credentials in SAP Cloud Integration [page 21]

Add the user credentials in your SAP Cloud Integration account that are required for communication with
SAP S∕4HANA and SAP SuccessFactors Employee Central.

Downloading Certicate from SAP Cloud Integration [page 22]

Download the certicate from your SAP Cloud Integration account so that the SAP S∕4HANA administrator
can upload it to the SAP S∕4HANA system.

Uploading SAP S∕4HANA Certicate to SAP Cloud Integration [page 23]

Upload the SAP S∕4HANA to your SAP Cloud Integration account to secure the data exchange between
both systems.

Adding Your User to the Members List in SAP BTP Cockpit [page 24]
Ensure that your user is available in the members list in the SAP BTP cockpit so that you can determine the
technical name of your subaccount.

Determining Subaccount Name for the Cloud Connector in SAP BTP Cockpit [page 24]

Implementing Data Migration and Replication to Employee Central

Data Migration and Replication to Employee Central PUBLIC 15
 Determine the technical name of your subaccount in the SAP BTP cockpit. The Cloud Connector
administrator enters this name when connecting the Cloud Connector to your SAP Cloud Integration
account.

Connecting the Cloud Connector to Your SAP Cloud Integration Account [page 25]
Add a SAP Cloud Integration subaccount to the Cloud Connector so that you can connect it.

Creating an Access Control System Mapping for the Cloud Connector [page 26]
Add a system mapping for access control in the Cloud Connector to specify the backend systems that can
be accessed by your cloud applications.

Creating an Access Control Resource Mapping for the Cloud Connector [page 27]
Add a resource mapping for access control in the Cloud Connector to specify the resources that can be
accessed by your cloud applications.

Checking Whether the Cloud Connector Is Registered in Your Subaccount [page 27]
Check whether your Cloud Connector has been successfully created.

Copying the Integration Packages in SAP Cloud Integration [page 28]

Copy the integration packages for data replication to SAP SuccessFactors Employee Central that you want
to use from the catalog to your customer workspace in SAP Cloud Integration.

Conguring the Integration Flow for Data Replication to Employee Central [page 29]
Congure the integration ow for replication of employee and organizational data to SAP SuccessFactors
Employee Central in your customer workspace in SAP Cloud Integration.

Conguring the Integration Flow for Replication of Generic Data from Employee Central to SAP S∕4HANA Using
the OData API [page 34]
Congure the integration ow for replication of data such as MDF objects or picklists from SAP
SuccessFactors Employee Central in your customer workspace in SAP Cloud Integration.

Conguring the Value Mapping for Connecting Multiple Employee Central Instances to SAP S∕4HANA [page
40]
Congure the mapping of Employee Central instance IDs from SAP S∕4HANA to the address and
credentials dened in the corresponding integration ows if you want to connect multiple Employee Central
instances to the same client of your SAP S∕4HANA system.

Deploying the Artifacts in SAP Cloud Integration [page 44]

Deploy the artifacts that you've congured before in your customer workspace in SAP Cloud Integration.

Determining the Endpoint URLs Required for Outbound Communication from SAP S∕4HANA [page 45]
Determine the endpoint URLs of the integration ows in SAP Cloud Integration. The SAP S∕4HANA
administrator enters these URLs when activating the SAP S∕4HANA outbound web services, so that SAP
S∕4HANA is able to address the middleware.

Reporting Middleware Issues [page 46]

Report a case if you have issues that you can't solve using the monitoring in SAP Cloud Integration,
providing information about the process run.

Implementing Data Migration and Replication to Employee Central

16 PUBLIC Data Migration and Replication to Employee Central
2.1.2.1 Middleware Content for Data Replication to Employee
Central

Get an overview of the integration content that's available in SAP Cloud Integration for replicating employee and
organizational data from SAP S∕4HANA to Employee Central and for replication of generic data such as picklists
from Employee Central.

Data replication to Employee Central uses the following integration packages and integration ows in SAP Cloud
Integration.

Integration Package Contained Integration Flow

SAP ERP or SAP S/4HANA Integration with Upsert Data from SAP ERP or SAP S4HANA to SAP
SAP SuccessFactors Employee Central: Employee and
SuccessFactors Employee Central Using the OData API
Organizational Data

 Note
The integration package also contains another integration
ow, Query Employee Key Data from SAP SuccessFactors
Employee Central. This integration ow isn't used in the
SFSF EC S4 HCM INTEGRATION (ECS4HCM) add-on.
Therefore, don't congure and deploy this integration ow.

SAP SuccessFactors Employee Central Integration with SAP Replicate Generic Data from SAP SuccessFactors Employee
ERP or SAP S/4HANA: Generic Data Central to SAP ERP or SAP S/4HANA Using the OData API

SAP SuccessFactors Employee Central Integration with SAP Mapping of Employee Central Instance ID to Enable Connection
ERP or SAP S/4HANA: System Mapping of Multiple Employee Central Instances

 Note
You only need this integration package if you want to con-
nect multiple Employee Central instances to the same cli-
ent of your SAP S∕4HANA system.

Here are graphical overviews of how the integration ows work and how the systems interact with each other.

Implementing Data Migration and Replication to Employee Central

Data Migration and Replication to Employee Central PUBLIC 17
 Replication of Employee and Organizational Data to Employee Central

Implementing Data Migration and Replication to Employee Central

18 PUBLIC Data Migration and Replication to Employee Central
 Replication of Generic Data from Employee Central

2.1.2.2 Performing Basic Steps for Using SAP Cloud

Integration

Ensure that the basic setup is completed before you start conguring SAP Cloud Integration for data replication
from Employee Central to SAP S∕4HANA.

Procedure

1. Check whether you have the required SAP Cloud Integration account.

For more information, refer to Initial Setup.

Implementing Data Migration and Replication to Employee Central

Data Migration and Replication to Employee Central PUBLIC 19
2. Check whether you have access to the web-based SAP Cloud Integration tools.

For more information, refer to Tool Access.

3. Check whether you have access to the runtime node.

For more information, refer to Runtime in Detail.

4. Make sure that you have an SAP Cloud Integration user, which enables the customer system for authentication
based on user credentials.

You can use your S-user for this purpose. For more information, refer to Creating a User for Cloud Integration,
Neo Environment.
5. Make sure that the SAP Cloud Integration user has the necessary permission for sending messages.

For more information, refer to Dening Permissions for Senders to Process Messages on a Runtime Node,
Persona for the Cloud Foundry Environment, or Persona for the Neo Environment.

Results

SAP Cloud Integration is ready for the conguration steps.

Next Steps

 Note

For more information about which versions of the middleware content provided for this integration are
supported, refer to SAP Note 3400216 .

 Caution

You are only allowed to congure the content as described in this guide. If you make modications not
described in this guide, SAP will not provide support for the modied content.

The middleware content described in this guide is meant for use in SAP Cloud Integration. You are not
allowed to deploy it in an on-premise SAP Process Orchestration system. For more information, see SAP Note
2428801 .

Implementing Data Migration and Replication to Employee Central

20 PUBLIC Data Migration and Replication to Employee Central
2.1.2.3 Creating User Credentials in SAP Cloud Integration

Add the user credentials in your SAP Cloud Integration account that are required for communication with SAP
S∕4HANA and SAP SuccessFactors Employee Central.

Procedure

1. Sign in to the SAP Cloud Integration web UI.

2. Choose Monitor (Operate and monitor integration scenarios) from the top-level menu on the left.
3. Choose Security Material in the Manage Security section.
4. To create a credentials artifact for the communication between SAP Cloud Integration and Employee Central,
choose Create and select a credentials type.
• If you want to use the Basic authentication type for Employee Central receivers, select User Credentials and
deploy a credentials artifact with the following attributes:

Field Name User Action and Values

Name Enter any name.

Type Select User Credentials.

User Enter the name of the SAP SuccessFactors API user.

Password Enter the password of the SAP SuccessFactors API user.

Company ID Enter the name of your SAP SuccessFactors Employee

Central instance.

• If you want to use the OAuth2 SAML Bearer Assertion authentication type for Employee Central receivers,
select OAuth2 SAML Bearer Assertion and deploy a corresponding credentials artifact.
For more information, refer to Deploying an OAuth2 SAML Bearer Assertion.

5. To create a credentials artifact for the communication between SAP Cloud Integration and SAP S∕4HANA,
select User Credentials again.
6. Deploy a credentials artifact with the following attributes:

Field Name User Action and Values

Name Enter any name.

Type Select User Credentials.

User Enter the name of the SAP S∕4HANA integration user.

Password Enter the password of the SAP S∕4HANA integration user.

Implementing Data Migration and Replication to Employee Central

Data Migration and Replication to Employee Central PUBLIC 21
Results

You've added the user credentials of your SAP S∕4HANA system and SAP SuccessFactors instance in SAP Cloud
Integration.

2.1.2.4 Downloading Certicate from SAP Cloud Integration

Download the certicate from your SAP Cloud Integration account so that the SAP S∕4HANA administrator can
upload it to the SAP S∕4HANA system.

Context

How you download a certicate depends on the browser you're using. We explain it here using the Edge browser as
an example.

Procedure

1. In your browser window, choose the Settings and more symbol in the upper right corner.

2. Choose Settings Privacy, search, and services .

3. Scroll down to the Security section.
4. Choose Manage certicates.
5. Go to the Trusted Root Certication Authorities tab.
6. Select the root certicate and choose Export.

The Certicate Export Wizard opens.

7. Choose Next.
8. Select the format DER encoded binary X.508 (.CER) and choose Next.
9. Specify a le name and select a location, then save the certicate.

Results

You’ve downloaded the certicate from SAP Cloud Integration and can now hand it over to the SAP S∕4HANA
administrator.

Implementing Data Migration and Replication to Employee Central

22 PUBLIC Data Migration and Replication to Employee Central
Related Information

Uploading SAP Cloud Integration Certicate to SAP S∕4HANA [page 53]

2.1.2.5 Uploading SAP S∕4HANA Certicate to SAP Cloud

Integration

Upload the SAP S∕4HANA to your SAP Cloud Integration account to secure the data exchange between both
systems.

Prerequisites

The SAP S∕4HANA administrator has downloaded the certicate from your SAP S∕4HANA system.

Procedure

1. Log on to the SAP Cloud Integration web UI.

2. Add the certicate in the Keystore.

For more information, refer to Importing a Certicate.

Results

You've enabled certicate-based communication from SAP Cloud Integration to your SAP S∕4HANA system.

Related Information

Downloading Certicate from SAP S∕4HANA [page 52]

Implementing Data Migration and Replication to Employee Central

Data Migration and Replication to Employee Central PUBLIC 23
2.1.2.6 Adding Your User to the Members List in SAP BTP
Cockpit

Ensure that your user is available in the members list in the SAP BTP cockpit so that you can determine the
technical name of your subaccount.

Context

The subaccount is required for conguring the Cloud Connector. The Cloud Connector acts as a reverse invoke
proxy between the SAP S∕4HANA system and SAP Cloud Integration.

Procedure

1. Log on to the SAP BTP cockpit.

2. Choose Members on the left side.
3. Check if your user is in the list. If not, add it to the list.

Results

Your user is now visible in Members.

2.1.2.7 Determining Subaccount Name for the Cloud

Connector in SAP BTP Cockpit

Determine the technical name of your subaccount in the SAP BTP cockpit. The Cloud Connector administrator
enters this name when connecting the Cloud Connector to your SAP Cloud Integration account.

Prerequisites

Your user has been added to the members list in SAP BTP Cockpit

Implementing Data Migration and Replication to Employee Central

24 PUBLIC Data Migration and Replication to Employee Central
Procedure

1. Log on to the SAP BTP cockpit.

2. Go to the Overview page of your SAP Cloud Integration tenant.
3. Locate the technical name in the Subaccount Information section at the bottom.

Results

You’ve determined the subaccount name and can provide it to the Cloud Connector administrator. They'll use the
name when setting up the connection to the subaccount.

2.1.2.8 Connecting the Cloud Connector to Your SAP Cloud

Integration Account

Add a SAP Cloud Integration subaccount to the Cloud Connector so that you can connect it.

Prerequisites

The SAP BTP cockpit administrator has determined the subaccount name.

Procedure

1. Log on to the Cloud Connector.

2. Choose Add Subaccount.
3. Enter the following information:

Field Name User Action and Values

Region Choose your region.

Subaccount Enter the technical name of the SAP Cloud Integration sub-
account that has been provided by the SAP BTP cockpit
administrator.

Subaccount User Enter the name of the subaccount user, which you obtained
when you registered your account on SAP BTP. Alternatively,
you can add a new subaccount user in the SAP BTP cockpit.

Password Enter the password of the subaccount user.

Implementing Data Migration and Replication to Employee Central

Data Migration and Replication to Employee Central PUBLIC 25
 Field Name User Action and Values

Location ID Enter SFSFintegration.

Results

You've created a subaccount in the Cloud Connector.

2.1.2.9 Creating an Access Control System Mapping for the

Cloud Connector

Add a system mapping for access control in the Cloud Connector to specify the backend systems that can be
accessed by your cloud applications.

Procedure

1. Log on to the Cloud Connector.

2. In the menu on the left side, navigate to Cloud To On-Premise.
3. Choose the Plus symbol under ACCESS CONTROL on the right side to add a mapping.
4. In the Add System Mapping dialog, set Back-End Type to ABAP System, then choose Next.
5. Set Protocol to HTTPS, then choose Next.
6. Set Internal Host to <backend host name>.<backend domain name> of your SAP S∕4HANA system.
7. Set Internal Port to the SSL port of your SAP S∕4HANA system, then choose Next.
8. Specify Virtual Host and Virtual Port, then choose Next.
9. Set Principal Type to None, then choose Next.
10. Enter a description, then choose Next.
11. Review your entries on the Summary screen, then choose Finish.

Results

Your system mapping is now available in the Cloud Connector.

Implementing Data Migration and Replication to Employee Central

26 PUBLIC Data Migration and Replication to Employee Central
2.1.2.10 Creating an Access Control Resource Mapping for the
Cloud Connector

Add a resource mapping for access control in the Cloud Connector to specify the resources that can be accessed
by your cloud applications.

Procedure

1. Log on to the Cloud Connector.

2. In the menu on the left side, navigate to Cloud To On-Premise.
3. In the ACCESS CONTROL section, select Resources Of <virtual host> and choose Add.
4. In the Add Resource dialog, make the following settings:

Field Name User Action and Values

URL Path Enter /sap/bc/srt/.

Enable Set to Enabled.

Access Policy Select Path and all sub-paths.

5. Save your settings.

Results

Your resource mapping is now available in the Cloud Connector.

2.1.2.11 Checking Whether the Cloud Connector Is Registered

in Your Subaccount

Check whether your Cloud Connector has been successfully created.

Procedure

1. Log on to the SAP BTP cockpit.

2. Choose Cloud Connectors on the left side.
3. Select the subaccount for which you created the connection in the Cloud Connector.

Implementing Data Migration and Replication to Employee Central

Data Migration and Replication to Employee Central PUBLIC 27
Results

The Cloud Connector you created with the location ID you specied should be shown as Connected.

2.1.2.12 Copying the Integration Packages in SAP Cloud

Integration

Copy the integration packages for data replication to SAP SuccessFactors Employee Central that you want to use
from the catalog to your customer workspace in SAP Cloud Integration.

Procedure

1. Log on to the SAP Cloud Integration web UI.

2. Choose Discover from the top-level menu on the left.
3. Search for the SAP ERP or SAP S/4HANA Integration with SAP SuccessFactors Employee Central: Employee
and Organizational Data integration package and choose Copy.
4. Optional: Proceed in the same way with the other integration packages if you use them:
• SAP SuccessFactors Employee Central Integration with SAP ERP or SAP S/4HANA: Generic Data
• SAP SuccessFactors Employee Central Integration with SAP ERP or SAP S/4HANA: System Mapping

If you receive a warning that a package already exists in your workspace, choose either Overwrite or Create
copy, depending on what ts better in your situation.

Results

You've copied the required integration packages to your workspace and can now start conguring the integration
ows contained in the package.

Implementing Data Migration and Replication to Employee Central

28 PUBLIC Data Migration and Replication to Employee Central
2.1.2.13 Conguring the Integration Flow for Data Replication
to Employee Central

Congure the integration ow for replication of employee and organizational data to SAP SuccessFactors Employee
Central in your customer workspace in SAP Cloud Integration.

Prerequisites

You've copied the SAP ERP or SAP S/4HANA Integration with SAP SuccessFactors Employee Central: Employee and
Organizational Data and SAP SuccessFactors Employee Central Integration with SAP ERP or SAP S/4HANA: Generic
Data integration package to your customer workspace.

Procedure

1. Log on to the SAP Cloud Integration web UI.

2. Choose Design Integration and Artifacts from the top-level menu on the left.
3. Select the SAP ERP or SAP S/4HANA Integration with SAP SuccessFactors Employee Central: Employee and
Organizational Data integration package from the list of packages in your customer workspace.

The package content is shown.

4. Choose Artifacts.

5. Choose Actions Congure for the Upsert Data from SAP ERP or SAP S4HANA to SAP SuccessFactors
Employee Central Using the OData API integration ow.
6. On the Sender tab, select SAP_ERP for Sender and ll in the following elds:

Field Name Default Value or Value to Be Entered Comment

Adapter Type SOAP Retain the default value.

For more information, refer to SOAP

(SAP RM) Adapter.

Implementing Data Migration and Replication to Employee Central

Data Migration and Replication to Employee Central PUBLIC 29
 Field Name Default Value or Value to Be Entered Comment

Address For example: / This value must match the outbound

ERP_to_EC_GenericODataUpsert service path that the SAP S∕4HANA ad-
ministrator enters when activating the
SAP S∕4HANA outbound web services.
For example, if you enter /
ERP_to_EC_GenericODataUpse
rt here, the outbound service path
must be: /cxf/
ERP_to_EC_GenericODataUpse
rt. Since this sufx is part of the de-
rived endpoint URL, it must be unique
for each instance of this integration
ow deployed within the same SAP
Cloud Integration tenant.

Authorization User Role or Client Certicate If you choose User Role, the SAP
S∕4HANA administrator must select
the User ID / Password authentica-
tion option when enabling the SAP
S∕4HANA outbound web services. If
you choose Client Certicate here, the
SAP S∕4HANA administrator must se-
lect the X.509 SSL Client Certicate
authentication option when you enable
the outbound web services.

User Role (only in case User Role is se- The pre-entered role, Create a custom role if you want to
lected for Authorization) ESBmessaging.send, or the name of a use a dedicated role to control author-
custom role that you created for this ization to process the integration ow.
purpose
For more information, refer to Connec-
tion Setup for Inbound Communication
- Integration Flow Endpoints.

Certicate (only in case Client Name of the certicate that you cong- For more information, refer to Client
Certicate is selected for Authorization) ured for this purpose Certicate Authentication (Inbound).

7. Go to the Receiver tab, select SFSF_EC for Receiver and ll in the following elds:

Field Name Default Value or Value to Be Entered Comment

Adapter Type HTTP Retain the default value.

For more information, refer to HTTP Re-

ceiver Adapter.

Authentication Basic or OAuth2 SAML Bearer Assertion

Implementing Data Migration and Replication to Employee Central

30 PUBLIC Data Migration and Replication to Employee Central
 Field Name Default Value or Value to Be Entered Comment

Credential Name Name of the credentials artifact of type If you've selected Basic for
User Credentials or type OAuth2 SAML Authentication: Enter the name of the
Bearer Assertion type that you created credentials artifact with the type User
before
Credentials.

If you've selected OAuth2 SAML Bearer

Assertion for Authentication: Enter the
name of the credentials artifact of type
OAuth2 SAML Bearer Assertion.

 Note
If you connect multiple Employee
Central instances to the same cli-
ent of your SAP S∕4HANA system,
remove the credential name and re-
place it with the following string: $
{property.CREDENTIALS_H
TTP}. Enter the credential name
that you removed from here in the
value mapping Mapping of
Employee Central Instance ID to
Enable Connection of Multiple
Employee Central Instances and
map it to an Employee Central in-
stance ID there. Then this integra-
tion ow derives the credentials for
this specic Employee Central in-
stance from the value mapping.

Timeout (in ms) 1 Use the default value. Only change this
value if you’re facing issues. In that
case, try a higher number.

8. Go to the More tab, select All Parameters for Type, and ll in the following elds:

Implementing Data Migration and Replication to Employee Central

Data Migration and Replication to Employee Central PUBLIC 31
 Field Name Default Value or Value to Be Entered Comment

SFSF_EC_Base_URL Base URL of your SAP SuccessFactors  Restriction

instance, using the https:// syntax
We don’t support IP addresses in
URLs as part of our reference ar-
chitecture. Use domain names in-
stead. If you think you have a spe-
cial case that requires IP addresses
instead of domain names, contact
Product Support.

 Note
If you connect multiple Employee
Central instances to the same cli-
ent of your SAP S∕4HANA sys-
tem, remove the URL and re-
place it with the following string: $
{property.ADDRESS_HTTP}.
Enter the URL that you removed
from here in the value mapping
Mapping of Employee Central
Instance ID to Enable Connection
of Multiple Employee Central
Instances and map it to an Em-
ployee Central instance ID there.
Then this integration ow derives
the URL for this specic Employee
Central instance from the value
mapping.

Implementing Data Migration and Replication to Employee Central

32 PUBLIC Data Migration and Replication to Employee Central
 Field Name Default Value or Value to Be Entered Comment

ENABLE_PAYLOAD_LOGGING No default Enter TRUE to transfer extended infor-

mation to the process log in the mid-
dleware to be able to analyze issues
more easily. Reset the parameter to
FALSE again if you no longer need the
extended log.

 Caution
For data protection reasons, enable
the extended log for troubleshoot-
ing purposes only. Make sure that
you disable the parameter again af-
terwards.

If you enable the extended log,

the complete message payload
containing all data that is to be
transferred is stored in the log.
Make sure that you congure per-
missions in a way that only au-
thorized persons can view the pay-
load in the log. Also ensure that
you're compliant with the data pro-
tection and privacy regulations so
that your data gets the highest level
of protection.

For more information, refer to:

• Data Protection and Privacy

• Identity and Access Manage-
ment and Persona for the
Cloud Foundry Environment
• Managing Users and Role As-
signments and Persona for the
Neo Environment

9. Choose Save in the lower right corner.

The Messages screen is shown, which informs you about errors and warnings issued for this integration ow.
10. To ignore the messages, choose Close.

Results

You’ve congured the integration ow for replication of employee and organizational data to SAP SuccessFactors
Employee Central in SAP Cloud Integration and generic data replication can now deploy it.

Implementing Data Migration and Replication to Employee Central

Data Migration and Replication to Employee Central PUBLIC 33
Related Information

Enabling and Testing the SAP S∕4HANA Outbound Web Service [page 55]
Creating User Credentials in SAP Cloud Integration [page 21]
Conguring the Value Mapping for Connecting Multiple Employee Central Instances to SAP S∕4HANA [page 40]

2.1.2.14 Conguring the Integration Flow for Replication of

Generic Data from Employee Central to SAP S∕4HANA
Using the OData API

Congure the integration ow for replication of data such as MDF objects or picklists from SAP SuccessFactors
Employee Central in your customer workspace in SAP Cloud Integration.

Prerequisites

You've copied the SAP SuccessFactors Employee Central Integration with SAP ERP or SAP S/4HANA: Generic Data
integration package to your customer workspace.

Context

You can use the Replicate Generic Data from SAP SuccessFactors Employee Central to SAP ERP or SAP S/4HANA
Using the OData API integration ow to replicate entities from Employee Central that are exposed to the OData API.
In the standard, the integration ow is currently available for importing picklists from Employee Central into the
SAP S∕4HANA system.

Procedure

1. Log on to the SAP Cloud Integration web UI.

2. Choose Design Integration and Artifacts from the top-level menu on the left.
3. Select the SAP SuccessFactors Employee Central Integration with SAP ERP or SAP S/4HANA: Generic Data
integration package from the list of packages in your customer workspace.

The package content is shown.

4. Choose Artifacts.

5. Choose Actions Congure for the Replicate Generic Data from SAP SuccessFactors Employee Central to
SAP ERP or SAP S/4HANA Using the OData API integration ow.

Implementing Data Migration and Replication to Employee Central

34 PUBLIC Data Migration and Replication to Employee Central
 6. On the Sender tab, select ERP_Query for Sender and ll in the following elds:

Field Name Default Value or Value to Be Entered Comment

Adapter Type SOAP Retain the default value.

For more information, refer to SOAP

(SOAP 1.x) Adapter.

Address For example: / This value must match the outbound

EC_to_ERP_Generic_Odata_Query service path that the SAP S∕4HANA ad-
ministrator enters when activating the
SAP S∕4HANA outbound web services.
For example, if you enter /
EC_to_ERP_Generic_Odata_Qu
ery here, the outbound service path
must be: /cxf/
EC_to_ERP_Generic_Odata_Qu
ery. Since this sufx is part of the de-
rived endpoint URL, it must be unique
for each instance of this integration
ow deployed within the same SAP
Cloud Integration tenant.

Authorization User Role or Client Certicate If you choose User Role, the SAP
S∕4HANA administrator must select
the User ID / Password authentica-
tion option when enabling the SAP
S∕4HANA outbound web services. If
you choose Client Certicate here, the
SAP S∕4HANA administrator must se-
lect the X.509 SSL Client Certicate
authentication option when you enable
the outbound web services.

User Role (only in case User Role is se- The pre-entered role, Create a custom role if you want to
lected for Authorization) ESBmessaging.send, or the name of a use a dedicated role to control author-
custom role that you created for this ization to process the integration ow.
purpose
For more information, refer to Connec-
tion Setup for Inbound Communication
- Integration Flow Endpoints.

Certicate (only in case Client Name of the certicate that you cong- For more information, refer to Client
Certicate is selected for Authorization) ured for this purpose Certicate Authentication (Inbound),
Neo Environment.

7. Go to the Receiver tab, select Employee_Central for Receiver and ll in the following elds:

Field Name Default Value or Value to Be Entered Comment

Adapter Type SuccessFactors Retain the default value.

For more information, refer to Success-

Factors SOAP Adapter.

Implementing Data Migration and Replication to Employee Central

Data Migration and Replication to Employee Central PUBLIC 35
 Field Name Default Value or Value to Be Entered Comment

Address Base URL of your SAP SuccessFactors Choose Select to add the base URL of
instance, using the https:// syntax your SAP SuccessFactors system, de-
pending on your data center.

 Restriction
We don’t support IP addresses in
URLs as part of our reference ar-
chitecture. Use domain names in-
stead. If you think you have a spe-
cial case that requires IP addresses
instead of domain names, contact
Product Support.

 Note
If you connect multiple Employee
Central instances to the same cli-
ent of your SAP S∕4HANA sys-
tem, remove the URL and re-
place it with the following string: $
{property.ADDRESS_SFSF}.
Enter the URL that you removed
from here in the value mapping
Mapping of Employee Central
Instance ID to Enable Connection
of Multiple Employee Central
Instances and map it to an Em-
ployee Central instance ID there.
Then this integration ow derives
the URL for this specic Employee
Central instance from the value
mapping.

Authentication Basic or OAuth2 SAML Bearer Assertion

Implementing Data Migration and Replication to Employee Central

36 PUBLIC Data Migration and Replication to Employee Central
 Field Name Default Value or Value to Be Entered Comment

Credential Name Name of the credentials artifact of type If you've selected Basic for
SuccessFactors or type OAuth2 SAML Authentication: Enter the name of
Bearer Assertion type that you created the credentials artifact with the
before
type SuccessFactors. For example:
ba_BPTestS40

If you've selected OAuth2 SAML Bearer

Assertion for Authentication: Enter the
name of the credentials artifact of type
OAuth2 SAML Bearer Assertion.

 Note
If you connect multiple Employee
Central instances to the same cli-
ent of your SAP S∕4HANA system,
remove the credential name and re-
place it with the following string: $
{property.CREDENTIALS_S
FSF}. Enter the credential name
that you removed from here in the
value mapping Mapping of
Employee Central Instance ID to
Enable Connection of Multiple
Employee Central Instances and
map it to an Employee Central in-
stance ID there. Then this integra-
tion ow derives the credentials for
this specic Employee Central in-
stance from the value mapping.

Page Size 400 Retain the default value. Only change

this value if you’re facing issues.

 Note
If this integration ow keeps termi-
nating with a timeout error, you
can reduce the page size and in-
crease the timeout value so that
the middleware processes less data
in more time.

Timeout (in min) 1 Use the default value. Only change this
value if you’re facing issues. In that
case, try a higher number.

8. Select ERP for Receiver and ll in the following elds:

Implementing Data Migration and Replication to Employee Central

Data Migration and Replication to Employee Central PUBLIC 37
 Field Name Default Value or Value to Be Entered Comment

Adapter Type SOAP Retain the default value.

For more information, refer to SOAP

(SAP RM) Adapter.

Address SAP S∕4HANA web service address Enter the endpoint URL that the SAP
S∕4HANA administrator determined
from the SOA Management transaction
in your SAP S∕4HANA system. For ex-
ample: http://
mys4system12345/sap/bc/srt
/scs/sap/
genericdatareplicationrequ
est

If you don't use the Cloud Connector,

the URL must start with https://.

If you use the Cloud Connector, the

URL must start with http://. For
more information about using the
Cloud Connector, refer to Outbound:
SAP Cloud Connector.

Proxy Type Internet or On-Premise If you don't use the Cloud Connector,
choose Internet.

If you use the Cloud Connector, choose

On-Premise.

Location ID (only in case On-Premise is Location ID that you dened for the You can also enter $
selected for Proxy Type) Cloud Connector instance associated {header.headername} to dynami-
with your account in the destination
cally read the value from a header.
conguration on the cloud side
The location ID identies the location
of this Cloud Connector for a specic
account. It is used as routing informa-
tion. Thus it’s possible to connect multi-
ple Cloud Connector instances to a sin-
gle account. The location ID must be
unique per account and must be some
identier that can be used in a URI.

Implementing Data Migration and Replication to Employee Central

38 PUBLIC Data Migration and Replication to Employee Central
 Field Name Default Value or Value to Be Entered Comment

Authentication Basic, Client Certicate, or Principal In case Internet is selected for Proxy
Propagation Type: Choose either Basic or Client
Certicate. Don't use the other options.

In case On-Premise is selected for Proxy

Type: Choose either Basic or Principal
Propagation. Don't use the other op-
tions.

For more information about principal

propagation, refer to Setting Up Princi-
pal Propagation (Example Scenario).

Credential Name (only in case Basic is Name of the credentials artifact of type For more information, refer to Basic Au-
selected for Authentication) User Credentials that you created be- thentication.
fore

Private Key Alias (only in case Name of the certicate that you cong- For more information, refer to Client
Client Certicate is selected for ured for this purpose Certicate Authentication (Outbound).
Authentication)

Timeout (in ms) 60000 Use the default value. Only change this
value if you’re facing issues. In that
case, try a higher number.

Allow Chunking Selected By default, this checkbox is selected.

This setting is supported by all HTTP 1.1
servers. If you use an HTTP server that
doesn't support chunking and therefore
face connection issues, deselect this
checkbox.

9. Choose Save in the lower right corner.

The Messages screen is shown, which informs you about errors and warnings issued for this integration ow.
10. To ignore the messages, choose Close.

Results

You’ve congured the integration ow for replication integration ow for replication of generic data from Employee
Central using the OData API in SAP Cloud Integration and can now deploy it.

 Note

This integration ow isn’t scheduled in the middleware. Instead, the replication of picklists is
initiated by the SAP S∕4HANA system using the Report to Import Picklists Using the Generic OData
Service Call (ECPAO_IMPORT_PICKLIST) program. This program calls the outbound web service
getGenericDataReplicationQuery_Out. The web service queries the picklists from SAP SuccessFactors
Employee Central, using the Replicate Generic Data from SAP SuccessFactors Employee Central to SAP ERP
or SAP S/4HANA Using the OData API integration ow.

Implementing Data Migration and Replication to Employee Central

Data Migration and Replication to Employee Central PUBLIC 39
Related Information

Enabling and Testing the SAP S∕4HANA Outbound Web Service [page 55]
Determining the Endpoint URLs Required for the SAP S∕4HANA Receivers of the Integration Flows [page 58]
Conguring the Value Mapping for Connecting Multiple Employee Central Instances to SAP S∕4HANA [page 40]

2.1.2.15 Conguring the Value Mapping for Connecting Multiple

Employee Central Instances to SAP S∕4HANA

Congure the mapping of Employee Central instance IDs from SAP S∕4HANA to the address and credentials
dened in the corresponding integration ows if you want to connect multiple Employee Central instances to the
same client of your SAP S∕4HANA system.

Prerequisites

The constant ERP to EC/EC to ERP: Connect Multiple EC Instances must be enabled in SAP S∕4HANA.

You've copied the SAP SuccessFactors Employee Central Integration with SAP ERP or SAP S/4HANA: System
Mapping integration package to your customer workspace.

Context

You only need to congure this value mapping if you want to connect multiple Employee Central instances to the
same client of your SAP S∕4HANA system.

Procedure

1. Log on to the SAP Cloud Integration web UI.

2. Choose Design Integration and Artifacts from the top-level menu on the left.
3. Select the SAP SuccessFactors Employee Central Integration with SAP ERP or SAP S/4HANA: System Mapping
integration package from the list of packages in your customer workspace.

The package content is shown.

4. Choose Artifacts.

5. Choose Actions Congure for the Mapping of Employee Central Instance ID to Enable Connection of
Multiple Employee Central Instances value mapping.
6. Make the following entries in the mapping table.

Implementing Data Migration and Replication to Employee Central

40 PUBLIC Data Migration and Replication to Employee Central
 Column Name Value to Be Entered Comment

ERP, ECCompany Enter the Employee Central instance ID Employee Central instance IDs are
as dened in the SAP S∕4HANA system. dened in Customizing of the
Business Integration Builder in
the SAP S∕4HANA system, under
Prerequisites Specify Employee
Central Instance ID .

Implementing Data Migration and Replication to Employee Central

Data Migration and Replication to Employee Central PUBLIC 41
 Column Name Value to Be Entered Comment

EC, URL; SFSF Credentials; HTTP Enter the following values separated by Map the URL and the SFSF Credentials
Credentials semicolons: elds for the following integration ows
if you use them:
• URL: Enter the address as dened
in the Employee Central receiver • Replicate Employee Master Data
of the integration ow. If one and Org. Assignments from SAP
SuccessFactors Employee Central
Employee Central instance is con-
to SAP ERP or SAP S4HANA
nected to your SAP S∕4HANA sys-
• Send Conrmations from SAP
tem, the Address eld contains the
ERP or SAP S4HANA to SAP
base URL of your SAP SuccessFac- SuccessFactors Employee Central
tors instance. If you connect mul-
• Replicate Generic Data from SAP
tiple Employee Central instances, SuccessFactors Employee Central
remove the URL from the integra- to SAP ERP or SAP S/4HANA
tion ow and enter it here. In the Using the OData API
integration ow, you enter a string
Map the URL and the HTTP Credentials
instead so that the integration ow
elds for the Upsert Data from SAP ERP
reads this value mapping.
or SAP S4HANA to SAP SuccessFactors
Employee Central Using the OData API
 Note integration ow. If you don't use this in-
For the Upsert Data from tegration ow, make only two entries in
SAP ERP or SAP S4HANA to this column and omit the third value.
SAP SuccessFactors Employee
Central Using the OData API in- For more information about the strings
tegration ow, the URL is not to be entered in these integration ows,
stored in the receiver. It is de- refer to the pages about conguring the
ned on the More tab, in the integration ows listed in Related Infor-
eld SFSF_EC_Base_URL.
mation.

• SFSF Credentials: Enter the name

of the credentials artifact of type
SuccessFactors as dened in the
Employee Central receiver of the
integration ow. If one Employee
Central instance is connected
to your SAP S∕4HANA system,
the Credential Name eld con-
tains a credentials artifact of the
SuccessFactors or OAuth2 SAML
Bearer Assertion type that you
created for your SAP SuccessFac-
tors instance. If you connect multi-
ple Employee Central instances, re-
move the credential name from the
integration ow and enter it here.
In the integration ow, you enter
a string instead so that the integra-
tion ow reads this value mapping.
• HTTP Credentials: Enter the name
of the credentials artifact of type

Implementing Data Migration and Replication to Employee Central

42 PUBLIC Data Migration and Replication to Employee Central
 Column Name Value to Be Entered Comment

HTTP as dened in the Upsert Data

from SAP ERP or SAP S4HANA
to SAP SuccessFactors Employee
Central Using the OData API in-
tegration ow. If one Employee
Central instance is connected
to your SAP S∕4HANA system,
the Credential Name eld con-
tains a credentials artifact of the
User Credentials or OAuth2 SAML
Bearer Assertion type that you
created for your SAP SuccessFac-
tors instance. If you connect multi-
ple Employee Central instances, re-
move the credential name from the
integration ow and enter it here.
In the integration ow, you enter
a string instead so that the integra-
tion ow reads this value mapping.

7. Choose Save in the lower right corner.

The Messages screen is shown, which informs you about errors and warnings issued for this value mapping.
8. To ignore the messages, choose Close.

Results

You’ve congured the mapping of Employee Central instance IDs from SAP S∕4HANA to the integration ow
address and credentials and can now deploy it.

Related Information

Conguring the Integration Flow for Employee Master Data and Organizational Assignment Replication
Conguring the Integration Flow for Conrmation
Conguring the Integration Flow for Replication of Generic Data from Employee Central to SAP S∕4HANA Using the
OData API [page 34]
Conguring the Integration Flow for Data Replication to Employee Central [page 29]

Implementing Data Migration and Replication to Employee Central

Data Migration and Replication to Employee Central PUBLIC 43
2.1.2.16 Deploying the Artifacts in SAP Cloud Integration

Deploy the artifacts that you've congured before in your customer workspace in SAP Cloud Integration.

Procedure

1. Log on to the SAP Cloud Integration web UI.

2. Choose Design Integration and Artifacts from the top-level menu on the left.
3. Select the SAP ERP or SAP S/4HANA Integration with SAP SuccessFactors Employee Central: Employee and
Organizational Data integration package from the list of packages in your customer workspace.

The package content is shown.

4. Choose Artifacts.

5. Choose Actions Deploy for the integration ow Upsert Data from SAP ERP or SAP S4HANA to SAP
SuccessFactors Employee Central Using the OData API.
6. Proceed in the same way with the other integration packages and artifacts if you use them:

Integration Package Artifact to Be Deployed

SAP SuccessFactors Employee Central Integration with SAP Replicate Generic Data from SAP SuccessFactors Employee
ERP or SAP S/4HANA: Generic Data Central to SAP ERP or SAP S/4HANA Using the OData API

SAP SuccessFactors Employee Central Integration with SAP Mapping of Employee Central Instance ID to Enable
ERP or SAP S/4HANA: System Mapping Connection of Multiple Employee Central Instances

Results

You have successfully deployed the integration ows and, if required, the value mapping so that your SAP Cloud
Integration account is ready for replication of data to Employee Central.

Implementing Data Migration and Replication to Employee Central

44 PUBLIC Data Migration and Replication to Employee Central
2.1.2.17 Determining the Endpoint URLs Required for Outbound
Communication from SAP S∕4HANA

Determine the endpoint URLs of the integration ows in SAP Cloud Integration. The SAP S∕4HANA administrator
enters these URLs when activating the SAP S∕4HANA outbound web services, so that SAP S∕4HANA is able to
address the middleware.

Procedure

1. Log on to the SAP Cloud Integration web UI.

2. Choose Operations View from the top-level menu on the left.

3. Choose Manage Integration Content All .

4. Select the following integration ows one by one and mark down the URL shown on the Endpoints tab:
• Replicate Generic Data from SAP SuccessFactors Employee Central to SAP ERP or SAP S/4HANA Using the
OData API
• Upsert Data from SAP ERP or SAP S4HANA to SAP SuccessFactors Employee Central Using the OData API

The SAP S∕4HANA uses this URL when setting up the outbound web service in SAP S∕4HANA.

 Note

The URL looks like this: https://<runtime URL of your SAP Cloud Integration
environment>/cxf/<sender address>

The sender address part is the sufx you enter in the Address eld of the sender in SAP Cloud Integration
when setting up the integration ow. For example: ERP_to_EC_GenericODataUpsert

To get the complete endpoint URL, congure and deploy the integration ow rst, then copy the URL from
Manage Integration Content.

Results

You’ve successfully copied the endpoint URLs the SAP S∕4HANA administrator needs when activating the SAP
S∕4HANA outbound web services.

Related Information

Enabling and Testing the SAP S∕4HANA Outbound Web Service [page 55]

Implementing Data Migration and Replication to Employee Central

Data Migration and Replication to Employee Central PUBLIC 45
2.1.2.18 Reporting Middleware Issues

Report a case if you have issues that you can't solve using the monitoring in SAP Cloud Integration, providing
information about the process run.

Context

If you face an issue with your SAP Cloud Integration-based integration scenario and want to report a case, enable
the extended log to ensure that the data that's needed for analyzing the issue is written to the log.

 Caution

For data protection reasons, enable the extended log for troubleshooting purposes only. Make sure that you
disable the parameter again afterwards.

If you enable the extended log, the complete message payload containing all data that is to be transferred is
stored in the log. Make sure that you congure permissions in a way that only authorized persons can view the
payload in the log. Also ensure that you're compliant with the data protection and privacy regulations so that
your data gets the highest level of protection.

For more information, refer to:

• Data Protection and Privacy

• Identity and Access Management and Persona for the Cloud Foundry Environment
• Managing Users and Role Assignments and Persona for the Neo Environment

Procedure

1. Enable the extended logging option for the integration that caused errors.

Replication Type Where to Enable How to Enable

Replication of employee and organiza- Conguration of the Upsert Data from Set the
tional data to Employee Central SAP ERP or SAP S4HANA to SAP ENABLE_PAYLOAD_LOGGING pa-
SuccessFactors Employee Central Using rameter to TRUE
the OData API integration ow

Replication of generic data such as Selection screen of the Report Select the Enable Payload Logging
MDF objects or picklists from Employee to Import Picklists Using the checkbox
Central Generic OData Service Call
(ECPAO_IMPORT_PICKLIST) program
in the SAP S∕4HANA system

2. Run the integration.

3. Go to Create a Support Case and report a case for the LOD-SF-INT-CPI component.
4. Add the log ID from the payload to the case so that the support team can nd the log easily.

Implementing Data Migration and Replication to Employee Central

46 PUBLIC Data Migration and Replication to Employee Central
Next Steps

For the required information that you should add in your case, refer to the SAP Knowledge Base Article (KBA)
2763716 .

2.1.3 Basic Steps in SAP S∕4HANA

Complete the basic steps in SAP S∕4HANA to implement data migration and replication to Employee Central.

Installing the Required Software Component Versions and Support Packages in SAP S∕4HANA [page 48]
Ensure that the required software component versions and support packages are installed in your SAP
S∕4HANA system.

Implementing the Required SAP Notes in SAP S∕4HANA [page 49]

Check for SAP Notes that provide bug xes, which are relevant for data replication from SAP
SuccessFactors Employee Central to SAP S∕4HANA.

How to Keep Your Systems in Sync [page 50]

Find out why we recommend that you always install the latest support package of the integration add-on in
the SAP S∕4HANA system.

Granting Permissions for Picklist Data Replication [page 51]

Grant the technical and the business permissions to the users who runs the replication of picklist data from
Employee Central.

Downloading Certicate from SAP S∕4HANA [page 52]

Download the certicate from your SAP S∕4HANA system so that the SAP Cloud Integration administrator
can upload it to your SAP Cloud Integration account.

Uploading SAP Cloud Integration Certicate to SAP S∕4HANA [page 53]

Upload the SAP Cloud Integration to your SAP S∕4HANA system to secure the data exchange between both
systems.

Enabling the SAP S∕4HANA Inbound Web Services [page 54]

Enable the SAP S∕4HANA inbound web services used during the replication of picklists into SAP S∕4HANA.

Enabling and Testing the SAP S∕4HANA Outbound Web Service [page 55]
Enable the SAP S∕4HANA outbound web service and perform a basic test to check whether it works.

Determining the Endpoint URLs Required for the SAP S∕4HANA Receivers of the Integration Flows [page 58]
Locate the endpoint URLs of the service denitions in your SAP S∕4HANA system. The SAP Cloud
Integration administrator enters these URLs for the SAP S∕4HANA receivers of the integration ows in
SAP Cloud Integration.

Creating an Employee Central Instance ID [page 58]

Dene an ID that represents your SAP SuccessFactors Employee Central instance in the SAP S∕4HANA
system.

Implementing Data Migration and Replication to Employee Central

Data Migration and Replication to Employee Central PUBLIC 47
2.1.3.1 Installing the Required Software Component Versions
and Support Packages in SAP S∕4HANA

Ensure that the required software component versions and support packages are installed in your SAP S∕4HANA
system.

Procedure

1. Make sure that your SAP S∕4HANA system has at least release level SAP S/4HANA 2022 installed.
a. Sign in to your SAP S∕4HANA system.
b. Choose System Status... .
c. In the SAP System Data section, choose Details for Product Version.
d. Make sure component S4HCM with release 100 (or a higher release) is listed on the Installed Software
Component Versions tab.

If your system doesn't have the minimum release level yet, upgrade it using the Software Update Manager
(SUM). For more information, refer to Software Update Manager 2.0.

For more information about the HCM approach within SAP S∕4HANA, refer to the SAP Note 2273108 .

 Note

If you want to connect multiple Employee Central instances to the same client of your SAP S∕4HANA
system, the following minimum stack level is required:
• SAP S/4HANA 2022: Support Package Stack 4 or higher
• SAP S/4HANA 2023: Feature Package Stack 2 or higher

2. Implement the SFSF EC S4 HCM INTEGRATION (ECS4HCM) add-on in your SAP S∕4HANA system.
a. Go to the Maintenance Planner and choose Explore Systems.
b. Select your SAP S∕4HANA system by clicking the system ID.
c. Choose Plan.
d. Select Install or Maintain an Add-On.
e. Select SFSF EC S4 HCM INTEGRATION.
f. Select at least one instance, for example, PA Inbound Service Enabling, and the highest support package
stack.

 Note

Only the newest support package ensures that all features provided for this integration are available in
your system.

g. Follow the process to download the software packages and the target.xml le to your download
directory.
h. Go to the Add-On Installation Tool (SAINT) transaction in your SAP S∕4HANA system and install the
add-on.

The add-on comprises the ECS4HCM 100 software component version. For more information about the add-
on, such as maintenance period, language support, or available support package stacks, go to the Product

Implementing Data Migration and Replication to Employee Central

48 PUBLIC Data Migration and Replication to Employee Central
 Availability Matrix and search for SFSF EC S4 HCM INTEGRATION. For more information about the
installation of the add-on, refer to the SAP Note 1841471 .

Results

You’ve ensured that the required software component versions and support package stacks are installed in SAP
S∕4HANA. You can now check for additional SAP Notes that may be required.

Related Information

How to Keep Your Systems in Sync [page 50]

Connecting Multiple Employee Central Instances to the Same SAP S∕4HANA Client
Implementing the Required SAP Notes in SAP S∕4HANA [page 49]

2.1.3.2 Implementing the Required SAP Notes in SAP

S∕4HANA

Check for SAP Notes that provide bug xes, which are relevant for data replication from SAP SuccessFactors
Employee Central to SAP S∕4HANA.

Procedure

1. Sign in to your SAP S∕4HANA system.

2. To nd SAP Notes you need to implement in your SAP S∕4HANA system, go to My SAP Notes & KBAs in SAP for
Me .
3. Choose Expert Search, enter LOD-EC-INT-TLS in Components (Exact), and choose Go.
4. Download and implement all applicable SAP Notes.

Only consider SAP Notes provided for the ECS4HCM 100 software component version. Most SAP Notes are
included in the latest support package provided for this software component version. If the latest support
package is installed in your system, you don't need to implement the SAP Notes contained in the support
package again.

Results

You’ve ensured that required SAP Notes are applied to your SAP S∕4HANA system.

Implementing Data Migration and Replication to Employee Central

Data Migration and Replication to Employee Central PUBLIC 49
Next Steps

If you face issues with the technical conguration of the web service runtime environment in your SAP S∕4HANA
system, refer to SAP Note 2347013 (Conguration of the ABAP Web Service Runtime with transaction
SRT_ADMIN).

Related Information

How to Keep Your Systems in Sync [page 50]

Installing the Required Software Component Versions and Support Packages in SAP S∕4HANA [page 48]

2.1.3.3 How to Keep Your Systems in Sync

Find out why we recommend that you always install the latest support package of the integration add-on in the SAP
S∕4HANA system.

The main use case of the SFSF EC S4 HCM INTEGRATION add-on, which comprises the ECS4HCM 100 software
component version, is to synchronize data between the cloud solution SAP SuccessFactors Employee Central and
SAP S/4HANA (on-premise edition) or SAP S/4HANA Cloud Private Edition.

Cloud solutions are regularly upgraded by SAP. Upgrades of on-premise systems are customer-managed.

New features in Employee Central often require enhancements of the ECS4HCM software component. New
integration features are also made available in the latest version of the ECS4HCM software component only. You
can use these new features only if your SAP S∕4HANA system is up to date. Furthermore, the data synchronization
between Employee Central and the SAP S∕4HANA system can only run smoothly if regular upgrades are performed
on both sides. Therefore, the add-on must also be upgraded regularly.

Ideally, you install the latest support package of the SFSF EC S4 HCM INTEGRATION add-on together with each
new Employee Central release.

If this isn’t possible due to upgrade restrictions concerning your SAP S∕4HANA system, we recommend installing
the latest support package of the add-on at least once a year. Only then we can ensure that the integration runs
smoothly.

Implementing Data Migration and Replication to Employee Central

50 PUBLIC Data Migration and Replication to Employee Central
2.1.3.4 Granting Permissions for Picklist Data Replication

Grant the technical and the business permissions to the users who runs the replication of picklist data from
Employee Central.

Prerequisites

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

Context

You can divide the triggering of the replication of picklist data from Employee Central and the actual replication and
processing of the picklist data in SAP S∕4HANA between dierent users:

• A processing user more as a business user, who initiates the report (ECPAO_IMPORT_PICKLIST) to query the
picklist data from Employee Central.
• A technical user for recieving the queried data and processing it in the SAP S∕4HANA system.

The following template role is available for the replication of picklist data from Employee Central:

• Generic Data Replication from EC - Technical User (SAP_HR_ECPAO_GEN_WEBSERVICES)

This role is meant for a technical user. It authorizes the user to carry out tasks such as the following:
• Execute the inbound web services GenericDataReplicationRequest_In
• Access the picklist query administration tables (ECPAO_PKL_QRY, ECPAO_PKL_RPRQ,
ECPAO_PKL_RQ_PKG, and ECPAO_QRY_INFO)
• Employee Master Data Migration from ERP to EC - Business User (SAP_HR_ECPAO_MIG_EE_PROCESSING)
This role is meant for a business user. It authorizes the user to carry out the following tasks:
• Delete picklist data queries from the picklist query administration 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 also meant for the business user. It contains the permissions the user needs to process
organizational assignments in SAP S∕4HANA. The role authorizes the user to carry out the following tasks
• Delete picklist data queries from the picklist query administration tables
• Use the application log to analyze the errors

Procedure

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

2. Set up the technical user.

Implementing Data Migration and Replication to Employee Central

Data Migration and Replication to Employee Central PUBLIC 51
 1. Copy the template role SAP_HR_ECPAO_GEN_WEBSERVICES to the customer namespace.
2. Adjust the permissions for the copied role, if necessary, to suit your specic requirements.
3. Assign the copied role to the user who executes the web service and replicate the picklist data in the SAP
S∕4HANA system.
3. Set up the business user.

1. Copy the template role SAP_HR_ECPAO_MIG_OM_PROCESSING or

SAP_HR_ECPAO_MIG_EE_PROCESSING to the customer namespace.
2. Set up permissions for the copied role to suit your specic requirements.
3. Assign the roles to the user who queries picklist data from Employee Central, monitors the integration in
the SAP S∕4HANA system and delete the picklist query administration tables.

2.1.3.5 Downloading Certicate from SAP S∕4HANA

Download the certicate from your SAP S∕4HANA system so that the SAP Cloud Integration administrator can
upload it to your SAP Cloud Integration account.

Procedure

1. Sign in to your SAP S∕4HANA system.

2. Go to the Trust Manager (STRUST) transaction.

For more information about this transaction, refer to Trust Manager.

3. Download the public key certicate.

For more information, refer to Exporting the AS ABAP’s Public-Key Certicate.

Results

You’ve downloaded the certicate from your SAP S∕4HANA system and can now hand it over to the SAP Cloud
Integration administrator.

Related Information

Uploading SAP S∕4HANA Certicate to SAP Cloud Integration [page 23]

Implementing Data Migration and Replication to Employee Central

52 PUBLIC Data Migration and Replication to Employee Central
2.1.3.6 Uploading SAP Cloud Integration Certicate to SAP
S∕4HANA

Upload the SAP Cloud Integration to your SAP S∕4HANA system to secure the data exchange between both
systems.

Prerequisites

The SAP Cloud Integration administrator has downloaded the certicate from your SAP Cloud Integration tenant.

Procedure

1. Sign in to your SAP S∕4HANA system.

2. Go to the Trust Manager (STRUST) transaction.

For information about this transaction, refer to Trust Manager.

3. Double-click the SSL client SSL Client (Anonymous) node.
4. Choose Display <-> Change to switch to the edit mode.
5. In the Certicate section, choose the Import Certicate pushbutton.
6. In File Path, browse for the certicate that was exported by the SAP Cloud Integration administrator and
choose Continue.
7. Choose Add to Certicate List.
8. Save your changes.

Results

You've enabled certicate-based communication from your SAP S∕4HANA system to SAP Cloud Integration.

Related Information

Downloading Certicate from SAP Cloud Integration [page 22]

Implementing Data Migration and Replication to Employee Central

Data Migration and Replication to Employee Central PUBLIC 53
2.1.3.7 Enabling the SAP S∕4HANA Inbound Web Services

Enable the SAP S∕4HANA inbound web services used during the replication of picklists into SAP S∕4HANA.

Context

By activating the inbound web services, you enable the SAP S∕4HANA system to request data from Employee
Central, using the integration ows in the middleware. Picklist import from Employee Central uses the following
SAP S∕4HANA inbound web service:

Web Service Internal Name Purpose

GenericDataReplicationRequest_In GENERICDATAREPLICATIONREQUEST Returns the Picklist data from Employee

Central.

Procedure

1. Sign in to your SAP S∕4HANA system.

2. Go to the SOA Management (SOAMANAGER) transaction.
3. Choose Simplied Web Service Conguration.
4. Search for the following service denitions one after the other:
• GENERICDATAREPLICATIONREQUEST
5. Select User Name / Password (Basic) or X.509 Client Certicate for each web service depending on which
authentication option you're using for SAP S∕4HANA inbound communication.
6. Save your settings.

Implementing Data Migration and Replication to Employee Central

54 PUBLIC Data Migration and Replication to Employee Central
2.1.3.8 Enabling and Testing the SAP S∕4HANA Outbound
Web Service

Enable the SAP S∕4HANA outbound web service and perform a basic test to check whether it works.

Context

By activating the outbound web service, you enable the SAP S∕4HANA system to request for generic data like
picklists from Employee Central using the integration ow in the middleware. Data replication is triggered by the
SAP S∕4HANA system, which uses the following SAP S∕4HANA outbound web service:

Web Service Internal Name Purpose

getGenericODataUpsert_Out CO_ECPAO_GET_GENERIC_ODATA_UPS Replicates employee and organizational

data to Employee Central.

getGenericDataReplicationQuery_Out CO_ECPAOX_GENERIC_DATA_QRY Replication Query for Generic Data from

SuccessFactors OData API.

Procedure

1. Sign in to your SAP S∕4HANA system.

2. Go to the SOA Management (SOAMANAGER) transaction.
3. Choose Web Service Conguration.
4. Search for the CO_ECPAOX_GENERIC_DATA_QRY and CO_ECPAO_GET_GENERIC_ODATA_UPS service
denition.

5. Choose Create Manual Conguration and create a new logical port.

6. Select either the User ID / Password or the X.509 SSL Client Certicate authentication option.

 Note

If you select the User ID / Password authentication option, the SAP Cloud Integration administrator must
choose User Role when conguring authorizations for the ERP sender in the corresponding integration
ow.

If you select the X.509 SSL Client Certicate authentication option, there are dierent options depending
on whether you use SAP Cloud Integration in the Cloud Foundry or the Neo environment:
• In the Cloud Foundry environment, the SAP Cloud Integration administrator must choose Client
Certicate when conguring authorizations for the ERP sender in the integration ow.
• In the Neo environment, the SAP Cloud Integration administrator can choose Client Certicate or User
Role when conguring authorizations for the ERP sender in the integration ow. If the administrator
selects the User Role authorization, a certicate-to-user mapping is required in addition. For more
information, refer to Setting Up Inbound HTTP Connections (with Certicate-to-User Mapping), Neo
Environment.

Implementing Data Migration and Replication to Employee Central

Data Migration and Replication to Employee Central PUBLIC 55
7. If you've selected User ID / Password, enter the user ID and password of your SAP Cloud Integration
communication user. If you've selected X.509 SSL Client Certicate, select an SSL Client Personal Security
Environment (PSE).

For more information, refer to Creating PSEs and Maintaining the PSE Infrastructure in the SAP NetWeaver
documentation.
8. Congure the transport settings.

Setting What to Enter

URL access path settings

URL components Select this radio button.

Protocol Select HTTPS.

Host Enter the <runtime URL of your SAP Cloud

Integration environment> part of the URL that the
SAP Cloud Integration administrator has provided.

Port Enter the port number of your SAP Cloud Integration envi-
ronment. If you haven't set up a specic port, enter 443 (the
default port for HTTPS).

Path Enter the /cxf/<sender address> part

of the URL that the SAP Cloud Integration
administrator has provided. For example: /
ERP_to_EC_GenericODataUpsert. And enter
the /cxf/EC_to_ERP_Generic_Odata_Query for
querying generic data such as MDF objects or picklist.

Logon language Select Language of User Context.

Proxy settings

Name of proxy host If you use a proxy, enter proxy. If not, leave this eld empty.

Port number of proxy host If you use a proxy, enter the port number, such as 8080. If
not, leave this eld empty.

User name for proxy access If applicable, enter your proxy user

Password of proxy user If applicable, enter the password of your proxy user

Transport binding settings

Make local call Select No Call in Local System.

Transport binding type Select SOAP 1.1.

Maximum wait for WS consumer Select 0.

Implementing Data Migration and Replication to Employee Central

56 PUBLIC Data Migration and Replication to Employee Central
 Setting What to Enter

Optimized XML transfer Select None.

Compress HTTP message Select Inactive.

Compress response Select True.

9. Congure the SOAP protocol.

Setting What to Enter

Reliable messaging protocol Select SAP RM

Message ID protocol Select Suppress ID Transfer

Data transfer scope Select Enhanced Data Transfer

Transfer protocol Select Transfer via SOAP Header

10. Leave the other elds empty. You don't need to make any entries in the Identiable Business Context and
Operation Settings steps.
11. Choose Finish to save your new logical port.
12. Select the entry end choose Set Log. Port Default.
13. Choose Ping Web Service to test outbound connectivity from SAP S∕4HANA to SAP Cloud Integration.

You're shown the message Web service ping successful for LP '<name of logical port>', proxy '<web service
name>'

Results

You've set up and tested the outbound web service in your SAP S∕4HANA system.

Related Information

Determining the Endpoint URLs Required for Outbound Communication from SAP S∕4HANA [page 45]

Implementing Data Migration and Replication to Employee Central

Data Migration and Replication to Employee Central PUBLIC 57
2.1.3.9 Determining the Endpoint URLs Required for the SAP
S∕4HANA Receivers of the Integration Flows

Locate the endpoint URLs of the service denitions in your SAP S∕4HANA system. The SAP Cloud Integration
administrator enters these URLs for the SAP S∕4HANA receivers of the integration ows in SAP Cloud Integration.

Procedure

1. Sign in to your SAP S∕4HANA system.

2. Go to the SOA Management (SOAMANAGER) transaction.
3. Choose Simplied Web Service Conguration.
4. Search for the following service denition:
• GENERICDATAREPLICATIONREQUEST
5. For the service denition, select the corresponding entry in the search result and choose Show Details.
6. Mark down the URL shown in Access URL.

Results

You’ve successfully copied the URLs the SAP Cloud Integration administrator needs when setting up the
integration ows in SAP Cloud Integration.

2.1.3.10 Creating an Employee Central Instance ID

Dene an ID that represents your SAP SuccessFactors Employee Central instance in the SAP S∕4HANA system.

Context

The Employee Central ID serves as a bracket for the metadata that you use in Employee Central and transfer to
the SAP S∕4HANA system. It bundles the settings that you make for data replication between Employee Central
and SAP S∕4HANA. The ID you dene doesn't necessarily have to match the name of your SAP SuccessFactors
instance. However, if the constant ERP to EC/EC to ERP: Connect Multiple EC Instances is enabled, the Employee
Central instance ID identies the corresponding physical SAP SuccessFactors instance that is connected to the
SAP S∕4HANA system. In this case, it can be helpful to use the name of the SAP SuccessFactors instance as the
Employee Central instance ID so that you can identify the corresponding Employee Central instance more easily.

If you replicate data in both directions (fromSAP S∕4HANA to Employee Central and from Employee Central to SAP
S∕4HANA), the ID is used for both replication directions.

Implementing Data Migration and Replication to Employee Central

58 PUBLIC Data Migration and Replication to Employee Central
Procedure

1. Go to Customizing for the Business Integration Builder and choose Prerequisites Specify Employee Central
Instance ID .
2. Enter an ID and a description for your Employee Central instance.

Next Steps

Make additional settings for your Employee Central instance, such as mapping PersonIdExternal from Employee
Central or dening a default language. To do so, go to the following activities in Customizing for the Business
Integration Builder:

• Data Migration and Replication to Employee Central Employee Data Dene Employee Data Settings for
Employee Central Instance
• Data Migration and Replication to Employee Central Organizational Data Dene Organizational Data
Settings for Employee Central Instance

Related Information

Connecting Multiple Employee Central Instances to the Same SAP S∕4HANA Client [page 242]
Dening Employee Data-Related Settings for Your Employee Central Company [page 118]
Dening Organizational Data-Related Settings for Your Employee Central Company [page 294]

2.2 Employee Data

2.2.1 Preparing the Systems for Employee Data Replication

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

Before proceeding, we should determine the full transmission start date that should be used in your
implementation. The full transmission start date denes when you will start using Employee Central as the system
of record for the data contained in the replication scope. Before the full transmission start date, SAP S∕4HANA is
the system of record. For more details you can refer the eect of this date on the replication behaviour here How
the Earliest Transfer Date Inuences Eective-Dated and Non-Eective Dated Templates.

You can replicate the employee master data to SAP S∕4HANA by using Business Integration Builder framework
(BIB) framework.

Implementing Data Migration and Replication to Employee Central

Data Migration and Replication to Employee Central PUBLIC 59
  Caution

Employee data with time constraint 3 can only be migrated to Employee Central entities that also support
overlapping data records.

2.2.1.1 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 eld length of an Employee Central eld that is within the integration scope must be the same as the
length of the target eld in the SAP S∕4HANA system, which you want to map.
For example, if you want to map the Employee Central eld Country to the SAP S∕4HANA eld Country Key
(LAND1) and LAND1 has a length restriction of 3 characters, you must restrict the length of the Country eld in
the Employee Central data model to 3 characters.
• Picklists for Employee Central elds that you want to map to SAP S∕4HANA elds 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 le-based data replication, set the locale of the user who imports the CSV les 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 nished.
• For some specic requirements Position Management must be enabled for your account using the Manage
Employee Central Settings admin tool in Employee Central.
• Some specic 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.

 Remember

As a customer, you don't have access to Provisioning. To complete tasks in Provisioning, contact your
implementation partner or Account Executive. For any non-implementation tasks, contact Product Support.

Implementing Data Migration and Replication to Employee Central

60 PUBLIC Data Migration and Replication to Employee Central
2.2.1.1.1 Creating Event Reasons in Employee Central

The HR processes related to the replication of employee master data from SAP S∕4HANA to Employee Central
require some new event reasons for handling specic cases.

Context

Here's what you need to do:

Procedure

1. Create a PSEUDO_HIRE event reason for the Hire event using the Active employee status as shown here:

PSEUDO_HIRE Event Reason

This event reason is used when the cuto date is after the hire date of an employee. Here the date of record
in Employee Central is not the actual hire date. The event reason of the starting record in Job Info will be
PSEUDO_HIRE even though the action type on cuto date is rehire.
2. Create a PSEUDO_REHIRE event reason for the hire event using the Active employee status as shown here:
This event reason is applicable when an employee is rehired after termination and when the earliest transfer
date is between the termination date and rehire date. Job information records will be extracted from the rehire
date with PSEUDO_REHIRE event reason.

 Note

The PSEUDO_REHIRE event reason should be dened as type hire in EC.

3. Create a PSEUDO_ADDGA event reason for the Add Global Assignment event using the Active employee status
as shown here:

Implementing Data Migration and Replication to Employee Central

Data Migration and Replication to Employee Central PUBLIC 61
 PSEUDO_ADDGA Event Reason

This event reason is used when the earliest transfer date you've dened for data replication is later than the
start date of a global assignment. The PSEUDO_ADDGA event reason implies that the start date of the Job
Information record isn't the actual start date of the global assignment. Instead, the earliest transfer date
(which is after the start of the host assignment) is used.
4. Create a DATAVAL event reason for the Data Change event using the Active employee status as shown here:

DATAVAL Event Reason

This event reason is used when the employee master data being extracted is valid for the replication
to Employee Central, based on the implementation of the Validity Periods for Data Replication to EC
(EX_ECPAO_EMP_VALIDITY_TAB) BAdI.
5. Create a DATAINVAL event reason for the Data Change event using the Furlough employee status as shown
here:

Implementing Data Migration and Replication to Employee Central

62 PUBLIC Data Migration and Replication to Employee Central
 DATAINVAL Event Reason

This event reason is used when the employee master data being extracted is not valid for the replication
to Employee Central, based on the implementation of the Validity Periods for Data Replication to EC
(EX_ECPAO_EMP_VALIDITY_TAB) BAdI.
6. Create a DATACHG event reason for the Data Change event using the Active employee status as shown here:

Implementing Data Migration and Replication to Employee Central

Data Migration and Replication to Employee Central PUBLIC 63
 DATACHG Event Reason

This event reason is used when there is a change in the value of a EC eld but no change in actions between two
consecutive records in the Job Info template.
7. Create a REHINT event reason for the Rehire event using the Active employee status as shown here:

Implementing Data Migration and Replication to Employee Central

64 PUBLIC Data Migration and Replication to Employee Central
 DATAREHINT Event Reason

This event reason is used when there is a gap between the termination date in PERNR belonging to one country
and hire date of the PERNR in next country, during international transfer. (There is a date gap of the PERNR
belonging to the rst country when terminated and the PERNR of the second country when hired.)
8. Create an INT_TRANSFER event reason for the International Transfer event using the Active employee status as
shown here:

Implementing Data Migration and Replication to Employee Central

Data Migration and Replication to Employee Central PUBLIC 65
 DATAINT_TRANSFER Event Reason

This event reason is used when there is no gap between the termination date in PERNR belonging to one
country and hire date of the PERNR in next country during international transfer.

2.2.1.2 Granting Permissions for Employee Master Data

Migration

Grant the business permissions to the users who run the migration of employee master 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.

Implementing Data Migration and Replication to Employee Central

66 PUBLIC Data Migration and Replication to Employee Central
Context

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

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

This role is meant for a business user of type B (System User). It authorizes the user to carry out tasks such as
the following:
• Extract employee data and migrate it to Employee Central
• Schedule background jobs of the employee extraction report
• Update the old key mapping table with manually migrated employee data via csv le
• Determination of managers and organizational management data
• Analyze inventory of the migrated employee data
• Delete the inventory details from the inventory tables
• 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 specic requirements.
a. Assign the copied roles to the user who migrates employee master data from SAP ERP to Employee
Central.

2.2.1.3 Setting of Frequency Field for Pay Components in EC

For the migration of recurring and non-recurring payment, you need to enable few rules in Employee Central for
automatic calculation of the frequency eld.

Context

Due to the change in the auto calculation funtionality in Employee Central, you will now have to manually enable few
rules for the automatic calculation of frequency eld.

Procedure

1. Go to Admin Center and choose Manage Permission Role.

Implementing Data Migration and Replication to Employee Central

Data Migration and Replication to Employee Central PUBLIC 67
2. Choose the Permission Role for which, you want to change the permissions.
3. Choose Permission under Permission settings.
4. Choose Employee Central Import Settings.
5. Under Employe Central Import Settings, either select Select All or Enable Business Rules for selected areas.
6. Click Finised to save the settings.

2.2.2 Replicating Employee Data from SAP S∕4HANA to

Employee Central

This section describes in detail which steps need to be carried out when you want to replicate data from SAP
S∕4HANA to Employee Central to Employee Central to use Employee Central as your system of record.

 Caution

Make sure that data that is mastered in SAP S∕4HANA and replicated to Employee Central can't be edited
in Employee Central. Use role-based permissions to disable the edit mode in Employee Central based, for
example, on country and not based on the legal entity of the employee. Filtering by Legal entity is not allowed.

 Note

Employee data with time constraint 3 (which means that any number of valid infotype records can exist at any
one time) can only be replicated to Employee Central entities that also support overlapping data records.

2.2.2.1 For Which Employee Data-Related Employee Central

Entities Can I Use Data Replication?

By default, you can use the Employee Central entities that are listed below.

You can also replicate data to custom generic objects.

The number in the rst column shown below denes the sequence in which employee data should be imported
into Employee Central. If you import the data manually using CSV les, make sure that you follow this sequence.
For more information refer to section Working with Data Imports in the Implementing Employee Central Core
implementation guide. Find the most current version of this guide at http://help.sap.com/hr_ec.

Employee Data Entities Supported by Data Replication

Template Used for CSV- Template Used for Web

Employee Central Based Data Extraction in Service-Based Data Extrac- Type of Entity in
Sequence No. Entity SAP S∕4HANA tion in SAP S∕4HANA Employee Central

20 Biographical informa- PersonInfoImportTemplate PerPerson (WS_2) Person object

tion (CSV_2)

Implementing Data Migration and Replication to Employee Central

68 PUBLIC Data Migration and Replication to Employee Central
 Template Used for CSV- Template Used for Web
Employee Central Based Data Extraction in Service-Based Data Extrac- Type of Entity in
Sequence No. Entity SAP S∕4HANA tion in SAP S∕4HANA Employee Central

21 Biographical informa- PersonInfoImportTemplate PerPerson (WS_2_DEP) Person object

tion (for employee's (CSV_2_DEP)
dependents)

25 Localized Biographi- Localized Biographical See Country-Specic table Person object

cal Information Information (CSV_2_LOC) below

30 Personal information PersonalInfoImportTemplate PerPersonal (WS_5) Person object

(CSV_5)

31 Personal information PersonalInfoImportTemplate PerPersonal (WS_5_DEP) Person object

(for employee's de- (CSV_5_DEP)
pendents)

35 Global information GlobalInfoImportTemplate See Country-Specic table Person object

(for employee) (CSV_18) below

36 Global information GlobalInfoImportTemplate See Country-Specic table Person object

(for employee's de- (CSV_18_DEP) below
pendents)

40 Employment details EmploymentInfoImportTempl EmpEmployment (WS_3) Employment object

ate (CSV_3)

50 Global assignments GlobalAssignmentInfoImport EmpGlobalAssignment Employment object

Template (CSV_6) (WS_6)

60 Job history JobInfoImportTemplate EmpJob (WS_4) Employment object

(CSV_4)

70 Email information EmailInfoImportTemplate PerEmail (WS_7) Person object

(CSV_7)

80 Phone information PhoneInfoImportTemplate PerPhone (WS_8) Person object

(CSV_8)

90 Job relationships JobRelationsInfoImportTempl EmpJobRelationships (WS_9) Employment object

ate (CSV_9)

95 Person relationship PersonRelationshipInfoImport PerPersonRelationship Person object

Template (CSV_19) (WS_19)

100 Addresses AddressImportTemplate PerAdressDEFLT (WS_10) Person object

(CSV_10)

101 Addresses (for em- AddressImportTemplate PerAdressDEFLT Person object

ployee's dependents) (CSV_10_DEP) (WS_10_DEP)

Implementing Data Migration and Replication to Employee Central

Data Migration and Replication to Employee Central PUBLIC 69
 Template Used for CSV- Template Used for Web
Employee Central Based Data Extraction in Service-Based Data Extrac- Type of Entity in
Sequence No. Entity SAP S∕4HANA tion in SAP S∕4HANA Employee Central

110 Compensation infor- CompInfoImportTemplate EmpCompensation (WS_11) Employment object

mation (CSV_11)

120 Recurring pay com- PayComponentRecurringImp EmpPayCompRecurring Employment object

ponents ortTemplate (CSV_12) (WS_12)

130 Non-recurring pay PayComponentNonRecurringI EmpPayCompNonRecurring Employment object

components mportTemplate (CSV_13) (WS_13)

130 Non-recurring pay PayComponentNonRecurringI EmpPayCompNonRecurring Employment object

components for o- mportTemplate (CSV_13_OC) (WS_13_OC)
cycle payments

140 Payment information PaymentInformation PaymentInformationV3 Generic object (pay-re-

(CSV_16) (WS_16 ) lated object)

150 Employment termina- EmploymentTerminationInfoI EmpEmploymentTermination Employment object

tion details mportTemplate (CSV_15) (WS_15)

160 Payment information Payment Information-Details PaymentInformationDetailV3 Generic object (pay-re-

details (CSV_14) (WS_14) lated object)

170 National ID informa- NationalIdCardImportTemplat PerNationalId (WS_17) Person object

tion e (CSV_17)

171 National ID informa- NationalIdCardImportTemplat PerNationalId (WS_17_DEP) Person object

tion (for employee's e (CSV_17_DEP)
dependents)

200 Alternative cost dis- Alternative Cost Distribution EmpCostDistribution (WS_20) Employment object
tribution (CSV_20)

210 Alternative cost dis- Alternative Cost Distribution EmpCostDistributionItem Employment object
tribution items Items (CSV_21) (WS_21)

 Note

• In all Employee Central entities listed above there are standard mappings which are predened by the
SAP S∕4HANA system. You can't congure them while dening primary mappings in the transformation
template group conguration.
• Employee Central entities WS_EE_REPL and WS_EE_WOR have been delivered for the employee replication
of data to ERP. These entities are not relevant when you replicate the data to Employee Central. For
migration scenarios, these entities should not be congured.
• For migrating the payment information details, you will have to now congure the payment information
template CSV_16/WS_16.

Implementing Data Migration and Replication to Employee Central

70 PUBLIC Data Migration and Replication to Employee Central
Country Specic Entities Supported by Data Replication

Template Used
Template Used for for Web Service-
CSV-Based Data Based Data Ex- Type of Entity
Employee Cen- Extraction in SAP traction in SAP in Employee Cen-
Sequence No. Country tral Entity ERP HCM ERP HCM tral

25 Brazil Localized Biograph- CSV_2_LOC* PerBiographicalInfo Person Object

ical Information LocBRA
(WS_2_BRA)

25 Chile Localized Biograph- CSV_2_LOC* PerBiographicalInfo Person Object

ical Information LocCHL
(WS_2_CHL)

25 France Localized Biograph- CSV_2_LOC* PerBiographicalInfo Person Object

ical Information LocFRA
(WS_2_FRA)

25 Italy Localized Biograph- CSV_2_LOC* PerBiographicalInfo Person Object

ical Information LocITA (WS_2_ITA)

25 Venezuela Localized Biograph- CSV_2_LOC* PerBiographicalInfo Person Object

ical Information LocVEN
(WS_2_VEN)

35 India Global Information CSV_18* PerGlobalInfoIND Person Object

(WS_18_IND)

161 USA Payment informa- PaymentInformatio PaymentInformatio Generic object

tion details for USA nDetail- nDetailV3USA (pay-related ob-
PaymentInformatio (WS_14_USA) ject)
nDetailUSA
(CSV_14_USA)

181 India Global Information CSV_18_DEP* PerGlobalInfoIND Person Object

(for employee's de- (WS_18D_IND)
pendent)

 Note

* - Non-Country specic templates that must be used for all countries.

Here is more information about some of these entities:

Basic import / User

Basic Import / User information is generated by the data extraction program. All elds of this entity use a standard
mapping, which you can't change.

Implementing Data Migration and Replication to Employee Central

Data Migration and Replication to Employee Central PUBLIC 71
Job history

If Global Assignment Management is enabled for your account and the corresponding role-based permissions are
enabled, standard events are validated for global assignments. Therefore you might get a validation error when
you transfer Job History data from SAP S∕4HANA to Employee Central. We recommend that you set up the
conguration of the missing events using a picklist entry and setting the active status for it.

If you don't use these feature, you can disable the Global Assignment Management option using the Manage
Employee Central Settings admin tool in Employee Central to avoid validation errors during data replication.

Addresses

In the SAP S∕4HANA system, the Addresses (0006) infotype has time constraint 2, which means that there can
be gaps between address records. The Employee Central addresses entities are able to handle these gaps, but
the user doesn't see them on the UI. If you maintain any subtype with time constraint 1, the gap would not be
supported in the SAP S∕4HANA system.

Recurring and non-recurring pay components

Each wage type is itself a subtype of the Recurring Payments/Deductions (0014) infotype or Additional Payments
(0015) infotype or One time Payment o-cycle (0267) infotype. The wage types include directly- and indirectly-
evaluated wage types. Use the cloning feature to dene a eld mapping for the Recurring Payments/Deductions
infotype.

Wage types with time constraint 3 (which means that any number of valid records can exist at any one time) are
not supported by Employee Central for Pay Component Recurring entity. Therefore, you can neither dene a eld
mapping for wage types with time constraint 3 in the SAP S∕4HANA system nor replicate them from SAP S∕4HANA
to Employee Central. In Employee Central, you can have multiple records in Non recurring payment Info for the
same pay component. So wage types with time constraint 3 are supported for Pay Component Non Recurring
template.

Non-recurring pay components can have a future date.

 Note

When you maintain negative values for the Amount eld for a wage type instead of deduction wage types
(which is the recommended approach), the same negative value is transferred to Employee Central. If any
calculations/rules are applied on Employee Central side against this eld, then you need to check the
calculations and the Employee Central congurations applied on it for correctness.

Payment information

If you use CSV-based data replication, you only need the child entity Payment Information Details, since the parent
payment information entity associated with this child entity is created automatically during CSV imports.

Implementing Data Migration and Replication to Employee Central

72 PUBLIC Data Migration and Replication to Employee Central
If you use web service-based data replication, you need the parent entity PaymentInformationV3 as well as
the associated child entity PaymentInformationDetailV3. In the Dene Custom Employee Central Templates
Customizing activity, the ID of the parent Employee Central template is specied in the ID of Dependent EC
Template eld of the child template.

 Note

Data replication can't handle the parent and the child entity together in one upsert. The
validateMainPaymentMethod_PaymentInfo business rule in Employee Central, however, checks for the child
entity that also the parent entity is contained in the same upsert. Therefore, we recommend that you deactivate
this rule for the legal entity of the employees whose data you replicate from SAP S∕4HANA to Employee
Central.

Let's say the employees whose data is mastered in SAP S∕4HANA and replicated to Employee
Central are all assigned to the legal entity SBM. Then you would add this statement to the
validateMainPaymentMethod_PaymentInfo rule as shown below:

Worker.Job Information.Company.Legal Entity ID is not equal to Text SBM

The new MDF-based Payment Information in Employee Central has to be enabled in Provisioning. For more
information refer to section Setting up MDF-based Payment Information in the Implementing Employee Central
Core implementation guide.

 Remember

As a customer, you don't have access to Provisioning. To complete tasks in Provisioning, contact your
implementation partner or Account Executive. For any non-implementation tasks, contact Product Support.

Implementing Data Migration and Replication to Employee Central

Data Migration and Replication to Employee Central PUBLIC 73
National ID

A precongured mapping entity is available for mapping the country-specic Employee Central card types to
country codes from the Countries (T005) table in the SAP S∕4HANA system.

Global information

Since global information data is country-specic, not all global information templates delivered as standard
templates are provided for the Web Service Transfer communication channel. For the le based transfer CSV_18
can be used. If you want to replicate global information data from SAP S∕4HANA to Employee Central using web
service transfer, create an Employee Central template in the customer namespace for each country version you
support and select the corresponding country in the Country column. The Employee Central template name you
enter must match the name of the country-specic global information OData entity as you can nd it in the OData
API Data Dictionary in Employee Central. Also the upsert sequence must be 35 and the dependent entity should be
personal information (WS_5).

 Note

WS_18_IND has been delivered as a standard entity for web service transfer communication channel for
country India as mentioned in the above table.

Global information for employee's dependents

Similar to global information of employee, global information for employee's dependents is country-specic.
Hence, not all global information templates delivered as standard templates are provided for the Web Service
Transfer communication channel. For the le based transfer CSV_18_DEP can be used. If you want to replicate
global information data for employee's dependents from SAP S∕4HANA to Employee Central using web service
transfer, then create an Employee Central template in the customer namespace for each country version you
support and select the corresponding country in the Country column. The Employee Central template name you
enter must match the name of the country-specic global information OData entity as you can nd it in the OData
API Data Dictionary in Employee Central. Also the dependent entity should be dependent's personal information
(WS_5_DEP).

 Note

WS_18D_IND has been delivered as a standard entity for web service transfer communication channel for
country India as mentioned in the above table.

Payment information details for USA

Payment Information details for country USA has been delivered. You can create custom template for any other
countries for which you want to replicate the data.

Implementing Data Migration and Replication to Employee Central

74 PUBLIC Data Migration and Replication to Employee Central
Alternative cost distribution

If you use CSV-based data replication, you only need the child entity Alternative Cost Distribution Items, since
the parent alternative cost distribution entity associated with this child entity is created automatically during CSV
imports.

If you use web service-based data replication, you need the parent entity EmpCostDistribution as well as the
associated child entity EmpCostDistributionItem. In the Dene Custom Employee Central Templates Customizing
activity, the ID of the parent Employee Central template is specied in the ID of Dependent EC Template eld of the
child template.

Some restrictions apply if you want to transfer alternative cost distribution data using repetitive structure mapping.

2.2.2.2 Communication Channels for Employee Data

Replication

You can transfer data from SAP S∕4HANA to Employee Central using dierent communication channels.

• Using CSV-based template les and the manual import framework in Employee Central
To use the manual import framework, go to the Admin Center and choose the following tools:

Data Upload Tools in Employee Central

For this type of entity in Employee Central ... You use this admin tool ...

Person and employment objects Import Employee Data

Generic objects Import and Export Data

• Using a synchronous Web service call and the middleware that is available for the data replication from SAP
S∕4HANA to Employee Central

 Example

This is an example of communication channels which you can use for employee data replication:

Implementing Data Migration and Replication to Employee Central

Data Migration and Replication to Employee Central PUBLIC 75
CSV File-Based Employee Data Extraction

To extract employee data from SAP S∕4HANA into CSV-based templates, make these settings for the Employee
Data Extraction (ECPAO_EMPL_EXTRACTION) program:

• Choose a template group that uses the CSV File-Based Transfer communication channel.
• Choose the communication channel File Transfer Use Server Path or File Transfer Use Local Drive
Path .

 Note

When you schedule the program as a background job (using the job scheduler report
ECPAO_EMPL_DMT_JOB_SCHEDULER) to carry out a mass data extraction, always choose the File
Transfer Use Server Path option.

It is recommended to use server path for downloading the payload les and as a result the default option to
download the les are server path.

The download log le shows all the success, error, and warning messages. It will also include the number of les
that were downloaded and from where the le is downloaded from. An additional authorization is performed to
check if the user has the rights to download the CSV le.

Implementing Data Migration and Replication to Employee Central

76 PUBLIC Data Migration and Replication to Employee Central
 Selection Settings for CSV File-Based Employee Data Extraction

Web Service-Based Employee Data Extraction

To transfer employee data using a synchronous web service call, make these settings for the Employee Data
Extraction (ECPAO_EMPL_EXTRACTION) program:

• Choose a template group that uses the Web Service Transfer communication channel.
• Choose the communication channel Web Service Transfer.

It is recommended to use server path for downloading the payload les and as a result the default option to
download the les are server path.

Implementing Data Migration and Replication to Employee Central

Data Migration and Replication to Employee Central PUBLIC 77
 Selection Settings for Web Service-Based Employee Data Extraction

2.2.2.3 How the Earliest Transfer Date Infuences Eective-

Dated and Non-Eective Dated Templates

If you dene an earliest transfer date for a transformation template group that you use for employee data
extraction, this date inuences eective-dated as well as non-eective dated templates.

What happens for initial data extraction

This is what happens when you initially extract the data:

• Eective-dated templates:
For eective-dated templates, if the earliest transfer date is after the hire or rehire date of an employee,
the employee's data is extracted starting with the earliest transfer date. (This is also true for Non-Recurring
Payments.) The following situations might occur:
• The employee is active on the earliest transfer date: In this case, the data is extracted starting with the
earliest transfer date for all eective-dated templates and Non-Recurring Payments.

Implementing Data Migration and Replication to Employee Central

78 PUBLIC Data Migration and Replication to Employee Central
 • The employee is terminated or retired on the earliest transfer date and hired or rehired later: In this
case, the data is extracted starting with the hire or rehire date for all eective-dated templates and
Non-Recurring Payments.
• The employee is terminated or retired on the earliest transfer date and isn't rehired: In this case, no data
will be extracted for all eective-dated templates and Non-Recurring Payments.
• Non-eective dated templates:
• When an employee is hired in past/present:
For all other non-eective dated templates when the employee is hired in the past or present, data is
extracted starting with the later of the two dates – current date or the earliest transfer date. If the earliest
transfer date is after the date on which you run the data extraction program (the earliest transfer date is in
future), then the earliest transfer date is used for data extraction. If the earliest transfer date is before, then
the date on which you run the data extraction program is used instead.
• When an employee is hired in future:
For all other non-eective dated templates when the employee is hired in future, the hire date is used for
data extraction.
• For Employment Termination, the last terminated data record for an employee is extracted. This is
independent of the earliest transfer date or the date on which you run the data extraction program.
• For Global Assignment, the last record of the employee's Details on Global Assignment (0710) infotype is
extracted. This is independent of the earliest transfer date or the date on which you run the data extraction
program. If the earliest transfer date is after the start date of the global assignment, the earliest transfer
date is used. If the earliest transfer date is between the start and end date of the host assignment, the Job
Information record is extracted for the host assignment using the PSEUDO_ADDGA event reason for the Add
Global Assignment event.
• If the earliest transfer date is greater than the future cuto date, then the earliest transfer date is considered
during the data extraction.

What happens for delta extraction

This is what happens for delta extraction:

• For eective-dated templates, if the earliest transfer date is after the hire or rehire date of an employee,
the employee's data is extracted starting with the earliest transfer date. (This is also true for Non-Recurring
Payments.) The following situations might occur:
• The employee active on the earliest transfer date: In this case, the data is extracted starting with the
earliest transfer date for all eective-dated templates and Non-Recurring Payments.
• The employee is terminated or retired on the earliest transfer date and hired or rehired later: In this
case, the data is extracted starting with the hire or rehire date for all eective-dated templates and
Non-Recurring Payments.
• The employee is terminated or retired on the earliest transfer date and isn't rehired: In this case, no data
will be extracted for all eective-dated templates and Non-Recurring Payments.
• For non-eective dated templates, if the earliest transfer date is after the date on which you run the data
extraction program, no data is extracted. If the earliest transfer date is before the date on which you run the
data extraction program or if no earliest transfer date is dened, the data record valid on the date on which you
run the data extraction program is extracted.

Implementing Data Migration and Replication to Employee Central

Data Migration and Replication to Employee Central PUBLIC 79
  Note

When an employee is terminated, his or her assigned position, job code, division, department, business
unit, and cost-center are persisted in Job Information in Employee Central. In the SAP S∕4HANA system,
however, a terminated employee is a default position assigned, and the 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 there from the employee's Job Information.
That's why the SAP S∕4HANA system replicates the corresponding assignments from the employee's last
active Organizational Assignment record instead of from the terminated one.

2.2.2.4 Steps in the SAP S∕4HANA System

In the next sections we'll go step by step through all activities you need to carry out in the SAP S∕4HANA system to
make data replication work.

 Note

All employee infotypes (both standard PA infotype and non-standard PA infotype) are allowed to be congured
in the Business Integration Builder framework. These infotypes are indicated by the PAPD eld value "X" in the
table T777D. In the employee migration/integration only the standard PA infotypes which has prex "PA" in the
database table names are supported. Any elds mapped to the non-standard PA infotypes will be not extracted
and hence will be ltered out in the migration/integration scenario.

2.2.2.4.1 Accessing the Customizing Structure in the SAP

S∕4HANA System

To dene customer-specic settings, you use the Customizing activities and Business Add-Ins (BAdIs) in the
integration add-on for SAP S∕4HANA and SAP SuccessFactors Employee Central (EC H4HCM) .

In your SAP S∕4HANA system, go to the Customizing: Execute Project (SPRO) transaction and choose SAP
Reference IMG. In the SAP Customizing Implementation Guide structure, open Personnel Management
Integration with SuccessFactors Employee Central Business Integration Builder :
Overview of Customizing Structure

In the Customizing structure, you can nd detailed information for each Customizing activity and BAdI:

Details of Customizing Structure

Implementing Data Migration and Replication to Employee Central

80 PUBLIC Data Migration and Replication to Employee Central
The next sections describe the steps you need to carry out in the SAP S∕4HANA system.

2.2.2.4.2 Switching O Talent Hybrid Integration for

Employee Data

If you've used the so called Talent Hybrid integration before, you need to specify that you now use employee data
replication from SAP S∕4HANA to SAP SuccessFactors Employee Central instead.

Context

You make this setting in the Switch O Talent Hybrid Integration for Employee Data Customizing activity (view
V_ECPAO_T77S0_SFSFI_SBSER). You need to set the switch in this Customizing activity if you want to start using
the SFSF EC INTEGRATION (PA_SE_IN) add-on to replicate employee master data from SAP S∕4HANA to SAP
SuccessFactors Employee Central , where you have previously used the integration add-on for SAP S∕4HANA and
SAP SuccessFactors HCM Suite to replicate employee data from SAP S∕4HANA to the Employee Prole in the SAP
SuccessFactors Talent Suite (which is also known as Talent Hybrid integration).

Setting the switch tells your SAP S∕4HANA system that employee data is replicated to Employee Central using the
Employee Data Extraction (ECPAO_EMPL_EXTRACTION) program. This has the following eects on the integration
add-on for SAP S∕4HANA and SAP SuccessFactors HCM Suite:

• You can no longer use the following programs:

• Sync Employee Data with SuccessFactors in Pre-Hire Period (RH_SFI_PREHIRE_EMPL_DATA)
• Sync Employee Data with SuccessFactors (with Delta and Inactive Logic)
(RH_SFI_SYNCHRONIZE_EMPL_DATA)
• Extraction of Employee Data for SuccessFactors (RH_SFI_TRIGGER_EMPL_DATA_REPL)
This is because the same data must only be transferred from one source to the SAP SuccessFactors system.
Otherwise, data from dierent sources in SAP S∕4HANA could be transferred to the same eld in the SAP
SuccessFactors system, which would lead to data inconsistencies.
• In the Replication of Employee's Compensation Data (RH_SFI_SYNCH_COMP_DATA) program, you can no
longer select an option for transferring the user ID to SAP SuccessFactors. The User ID Determination eld
is removed from the selection screen.
This is because when you replicate data toEmployee Central, the user ID is determined by the
Employee Data Extraction (ECPAO_EMPL_EXTRACTION) program and stored in the Employee Key Mapping
(PAOCFEC_EEKEYMAP) table.

Procedure

Set the value of the SFSFI SBSER switch to X or leave it empty.

Implementing Data Migration and Replication to Employee Central

Data Migration and Replication to Employee Central PUBLIC 81
2.2.2.4.3 Importing Metadata from Employee Central

You import the metadata from SAP SuccessFactors Employee Central to make Employee Central elds available in
the SAP S∕4HANA system so that you can use them for eld mappings.

To import metadata, use one of the following programs:

• Import of Metadata from Employee Central Using XML File (ECPAO_ECTMPL_METADATA_WRITER)

This program is available in the Import Metadata for Web Service-Based Data Transfer from Employee Central
Customizing activity.

 Note

You can only use this program to import metadata for web service entities. If you want to import metadata
for CSV le-based entities, use the Import of Metadata from Employee Central program instead.

• Import of Metadata from Employee Central (ECPAO_ECFLD_METADATA_WRITER)

This program is available in the Import Metadata for File-Based Data Transfer from Employee Central
Customizing activity.

 Note

You can only use this program to import metadata for CSV le-based entities. If you want to import
metadata for web service entities, use the Import of Metadata from Employee Central Using XML File
program instead.

2.2.2.4.3.1 Importing Metadata for Web Service-Based Data

Transfer

Use the Import of Metadata from Employee Central Using XML File (ECPAO_ECTMPL_METADATA_WRITER) program
to import metadata for web service-based data transfer.

Context

Using this program, you can import entries as well as delete entries you have imported for a specic Employee
Central instance and template.

 Caution

You can't delete metadata in the SAP S∕4HANA system that you have already used for eld mappings.
Otherwise your mappings become invalid. You are shown an error message if you try to delete metadata that is
used for eld mappings.

Implementing Data Migration and Replication to Employee Central

82 PUBLIC Data Migration and Replication to Employee Central
Procedure

1. Download the metadata that you want to import from Employee Central.
1. Go to the Admin Center and choose the OData API Metadata Refresh and Export tool.

OData API Metadata Refresh and Export Tool

2. To make sure that the metadata is up to date choose Refresh.
3. Choose Export for the Export Metadata to File option.
4. Store the metadata le in the XML format on a server or on your local disk.

 Note

API tools need to be enabled in Provisioning.

 Remember

As a customer, you don't have access to Provisioning. To complete tasks in Provisioning, contact
your implementation partner or Account Executive. For any non-implementation tasks, contact Product
Support.

 Note

When a new eld is added in Employee Central, you will have to re-import the metadata report and re-run
the report once again.

2. On the selection screen of the program, specify which metadata you want to import to SAP S∕4HANA and from
which le you want to upload it:

Implementing Data Migration and Replication to Employee Central

Data Migration and Replication to Employee Central PUBLIC 83
 Selection Screen of the ECPAO_ECTMPL_METADATA_WRITER Program

 Note

If you don't specify a specic Employee Central entity, the metadata is imported for all Employee Central
entities that are available and use the Web Service Transfer communication channel.

3. Optional: Carry out a test run of the program to check the data that will be uploaded to SAP S∕4HANA.
4. Clear the Test Run checkbox and execute the program to upload the data from the Employee Central metadata
le into the EC Entity Field Mapping (ECPAO_FLD) table.

If you run the program in a test system or client with the Test Run checkbox deselected, the program asks for
a transport request, to which the imported metadata will be assigned. Using this request you can transport the
entries to the productive system or client.

 Note

The standard elds are also uploaded into the EC Entity Field Mapping table. In this table, the Is Standard
Field (IS_FLD_STANDARD) ag is set for these elds. Since a standard mapping is dened for them, they
are not available in the Customizing of the transformation template groups.

5. Optional: To delete the entries you have imported for the Employee Central instance and template that you
have specied on the selection screen, select the Delete Metadata checkbox and execute the program. This will
make sure that the WS based and File based transfer will be consistent.
6. Check the metadata that you have imported in the Transport Imported Metadata and Check Metadata for
File-Based Data Transfer Customizing activity.

 Tip

For details about which information about the Employee Central elds exactly is imported by the
program, see the program documentation in your SAP S∕4HANA system. You'll nd a link to the program
documentation in the documentation of the Import Metadata for Web Service-Based Data Transfer from
Employee Central Customizing step.

Implementing Data Migration and Replication to Employee Central

84 PUBLIC Data Migration and Replication to Employee Central
 Transport Imported Metadata and Check Metadata for File-Based Data Transfer

 Note

Don't make any changes to the metadata in this Customizing view. Use the metadata import program to
update the entries in this view.

 Caution

If the Employee Central eld has Picklist ag is set for an imported Employee Central eld, you might need
to assign a value mapping entity when you dene a eld mapping for this Employee Central eld. Otherwise
the data extraction program might fail.

7. You can also store entries from this view on a transport request, for example, to transport them from your SAP
S∕4HANA test system to your productive system. To do so, choose Table View Transport .

2.2.2.4.3.2 Importing Metadata for File-Based Data Transfer

Use the Import of Metadata from Employee Central (ECPAO_ECFLD_METADATA_WRITER) program, to import
metadata for CSV le-based data transfer.

Context

Using this program, you can import entries as well as delete entries you have imported for a specic Employee
Central instance and template.

 Caution

You can't delete metadata in the SAP S∕4HANA system that you have already used for eld mappings.
Otherwise your mappings become invalid. You are shown an error message if you try to delete metadata that is
used for eld mappings.

Implementing Data Migration and Replication to Employee Central

Data Migration and Replication to Employee Central PUBLIC 85
Procedure

1. To download the metadata that you want to import from Employee Central, go to the Admin Center and choose
the following tools:

Metadata Download from Employee Central

For this type of entity in Employee Central ... You use this admin tool ...

Person and employment objects Choose the Import Employee Data tool, then choose
Download a blank CSV template

Foundation objects Choose the Import Foundation Data tool, then choose
Download a blank CSV template

Generic objects Choose the Import and Export Data tool, then select the
Export Data action

 Note

When a new eld is added in Employee Central, you will have to re-import the metadata report and re-run
the report once again.

2. On the selection screen of the program, specify which metadata you want to import to SAP S∕4HANA and from
which le you want to upload it:

Selection Screen of ECPAO_ECFLD_METADATA_WRITER Program

3. Select the Update Metadata checkbox to import the metadata.
4. Optional: Carry out a test run of the program to check the data that will be uploaded to SAP S∕4HANA.
5. Clear the Test Run checkbox and execute the program to upload the data from the Employee Central metadata
le into the EC Entity Field Mapping (ECPAO_FLD) table or delete data from this table.

If you run the program in a test system or client with the Test Run checkbox deselected, the program asks for
a transport request, to which the imported metadata will be assigned. Using this request you can transport the
entries to the productive system or client.

Implementing Data Migration and Replication to Employee Central

86 PUBLIC Data Migration and Replication to Employee Central
 6. Optional: To delete the entries you have imported for the Employee Central instance and template that you
have specied on the selection screen, select the Delete Metadata checkbox and execute the program.
7. Check the metadata that you have imported or deleted in the Transport Imported Metadata and Check
Metadata for File-Based Data Transfer Customizing activity.

 Tip

For details about which information about the Employee Central elds exactly is imported by the
program, see the program documentation in your SAP S∕4HANA system. You'll nd a link to the program
documentation in the documentation of the Import Metadata for Web Service-Based Data Transfer from
Employee Central Customizing step.

Transport Imported Metadata and Check Metadata for File-Based Data Transfer

 Note

You might need to make some changes to the uploaded metadata in this view. For example:

• If a eld is a required eld in your Employee Central data model and you want the SAP S∕4HANA
system to validate the settings for this eld, select the Is Required checkbox.
• You might need to specify the data type for elds. For elds that contain a date, for example, choose
the datetime data type so that the content can be identied correctly.

 Caution

If you upload the metadata again, the changes you've made manually will be overwritten.

Don't select the Standard Field and Deleted checkboxes. These ags are set by the metadata import
program:

• The Standard Field ag is set for all elds that are considered to be standard elds. This means that a
standard mapping is dened and that the elds are not available in Customizing for eld mapping.

Implementing Data Migration and Replication to Employee Central

Data Migration and Replication to Employee Central PUBLIC 87
 • Deleted eld means that the eld has become invalid since the last run of the program. This happens,
for example, if you've imported an Employee Central eld and dened a mapping for it. Now you delete
this eld in Employee Central and run the metadata import program again. The program recognizes
that the eld is missing in the new metadata import run and therefore sets this ag for it. Since the eld
no longer exists, your mapping becomes invalid.

If you select the EC Field Has Picklist checkbox for an imported Employee Central eld, you might need to
assign a value mapping entity when you dene a eld mapping for this Employee Central eld. Otherwise
the data extraction program might fail.

8. You can also store entries from this view on a transport request, for example, to transport them from your SAP
S∕4HANA test system to your productive system. To do so, choose Table View Transport .

2.2.2.4.4 Dening Value Mappings

Value mapping means that Employee Central eld values are mapped to values of SAP S∕4HANA elds.

 Example

Employee Central uses the value F, SAP S∕4HANA uses the value 1 for the Female gender code. The values have
the same meaning, but they aren't identical. Therefore they need to be mapped so that Employee Central can
read the gender code that is transferred from SAP S∕4HANA.

The data extraction programs use the value mappings when extracting data. They replace the SAP S∕4HANA keys
by the corresponding Employee Central keys if a value mapping is dened for the corresponding eld mapping.
Value mappings are assigned to eld mappings in the Primary Mapping and Secondary Mapping views of the eld
mapping in the Dene Field Mapping for Employee Data Customizing step (view cluster VC_ECPAO_MAP).

There are standard value mappings provided by SAP. Standard value mappings are provided for values that can't be
congured in the SAP S∕4HANA system and in Employee Central and therefore always stay the same.

 Example

Language codes can't be congured. The Employee Central language code English always corresponds to the
language code EN in the SAP S∕4HANA system. Therefore, a standard value mapping is provided for language
codes.

However, if you want to map values that can be congured in the SAP S∕4HANA system and in Employee Central,
you need to dene custom value mappings.

 Example

Let's say you want to map event reasons from the Job History entity in Employee Central to action types from
the Actions (0000) infotype in SAP S∕4HANA. So you dene, for example, a custom value mapping that maps
the Hire and Termination event reasons from Employee Central to the SAP S∕4HANA action types Hiring and
Leaving.

Since no country-specic standard value mappings are available, you also need to dene custom value mappings if
you need to map country-specic values.

Implementing Data Migration and Replication to Employee Central

88 PUBLIC Data Migration and Replication to Employee Central
  Example

Pay scale areas are country specic. If you need a pay scale area mapping, you dene it using the suitable ISO
code. You could, for example, map the Employee Central pay scale area BR SP BR-Sao Paulo (BRSP) to the SC
pay scale area from the SAP S∕4HANA system using the BR ISO code.

 Note

After copying the new value mapping entries, don’t save the entries immediately, but press the page down
button to see all the entries. You must click the page down button until you see the last set of entries. Once you
see the last set of entries, you can save all the newly created entries.

2.2.2.4.4.1 Import Picklists and Picklist Values from Employee

Central

Learn how you can import picklist data using web service and le upload method.

2.2.2.4.4.1.1 Import Picklists from Employee Central using Web

Service

Learn about how you can process and import picklists and picklist values from Employee Central to the SAP
S∕4HANA system by using OData query and analyze the application logs.

2.2.2.4.4.1.1.1 Import Picklists from Employee Central using

Web Service

You can import picklists and picklist values from Employee Central to the SAP S∕4HANA system system by using
OData query

Context

To import picklist you can use the program Report to Import Picklist using the Generic OData Service Call
(ECPAO_IMPORT_PICKLIST) or ECPAO_IMPORT_PICKLST transaction. You can use the imported picklists and
picklist values when dening value mappings in Customizing to map Employee Central eld values to values of ERP
elds.

Implementing Data Migration and Replication to Employee Central

Data Migration and Replication to Employee Central PUBLIC 89
Procedure

1. Access the Customizing activity Business Integration Builder Data Migration and Replication to Employee
Central Basic Seettings Dene Value Mapping Import Picklists and Picklist Values from Employee Central
Import Picklists from Employee Central Using Web Service
2. Select your Employee Central instance ID.
3. Specify the locale of the picklist labels that you want to import to the ERP system. The picklists are queried
only for this locale and imported. You can only choose one locale. As a practice, use the locale of the user who
logs on to SuccessFactors Employee Central and carries out data replication.
4. Choose the customizing task that should be used for locking the picklist entries.
5. Select the Reference Picklist Tables checkbox if you are importing the picklists from your productive Employee
Central instance to your ERP productive system or client. Don't select this checkbox if you import picklists
from your test Employee Central instance to your ERP test system or client.
6. Select the Enable Payload Logging checkbox, if you want to enable logging to the middleware.
7. Select the Update Picklist option to import picklists or the Delete Picklist option to delete imported picklists
from the ERP system.

Results

You can check the SLG1 to see the completion status of the report. Once the process is successful, you are ready to
use the picklists and picklist values in the next Customizing steps when you dene value mappings.

During the replication of picklist data process, application logs are written which can be accessed using the Analyze
Application Log (SLG1) transaction. The log object and sub object used are ECPAO and PICKLIST_IMPORT. With
each run of the program ECPAO_IMPORT_PICKLIST (Picklist Writer report based on Generic OData Service Call),
the system writes error and information messages to the application log. SLG1 logs are created once the update
process is completed (Success/Failures).

2.2.2.4.4.1.1.2 Replication Process for Picklist Data

Understand the process for replication of picklist data from Employee Central.

The process for replication of picklist data from Employee Central has steps in three systems interacting with each
other: Your SAP S∕4HANA system, the cloud-based middleware, and SAP SuccessFactors Employee Central.

1. The query program ECPAO_IMPORT_PICKLIST (Picklist writer report based on Generic OData Service Call) in
the SAP S∕4HANA system calls the outbound web service getGenericDataReplicationQuery_Out. It also
updates the query information and administration of picklist query table with the relevant status information.
2. The outbound web service sends the query to the cloud integration middleware and the corresponding web
service consumer proxy for the OData API is called.
3. The middleware requests the corresponding data from Employee Central using OData APIs.
4. The middleware calls the inbound web service GenericDataReplicationRequest in the SAP S∕4HANA
system to send the data it has received from Employee Central in packages to SAP S∕4HANA.

Implementing Data Migration and Replication to Employee Central

90 PUBLIC Data Migration and Replication to Employee Central
 5. The cloud integration middleware sends rst sends the Start Notication indicating that response packages
would be subsequently sent.
6. The cloud integration middleware sends the Base64 encoded messages based on the OData API response it
receives and sends it to the SAP S∕4HANA system as response packages in an asynchronous way using the
inbound web service.
7. The corresponding web service provider proxy is called. The response data is written into staging area, and it
also updates the entries in the response package database table.
8. The cloud integration middleware sends a nal notication message to SAP S∕4HANA system once the
last package is transferred which includes parameter TotalNumberOfResponsePackages containing the total
number of response packages. The system compares the number of entries in the response packages with this
parameter and decides whether to wait further or not.
9. Once all the response packages are collected, it processes the entries in the staging area, and deserializes
it. Then it triggers the processing of the picklist update logic thereby updating the picklist specic database
tables.
10. Creates SLG1 logs once the processing logic is completed and whether the update process resulted in success
or failures.
11. It clears the staging area and response package database tables in case of a successful run.
12. In case of failures the corresponding entries gets deleted in the subsequent runs.

2.2.2.4.4.1.1.3 Analyzing the Application Log for Picklist Data

Replication

Using the application log you can analyze the picklist writer report progress.

Context

During the replication of picklist data process, the application logs are written which can be accessed using the
Analyze Application Log (SLG1) transaction. The log object and sub object used are ECPAO and PICKLIST_IMPORT.
With each run of the program ECPAO_IMPORT_PICKLIST (Picklist Writer report based on Generic OData Service
Call), the system writes error and information messages to the application log.

On triggering the replication of picklist data from Employee Central using the report ECPAO_IMPORT_PICKLIST
(Picklist Writer report based on Generic OData Service Call) a log Query for instance nnnn and query type
PickListValueV2 with uuid (query ID) nnnn (the instance for which you are running the replication) is created
and sent.

Once the middleware sends the start notication to SAP S∕4HANA system, the following log ECPAO_PKL_QRY
updated with status In Process for query nnnn, resp. mess. nnnn is written.

Once all the response packages have reached the SAP S∕4HANA system from the middleware and the processing
of picklist update logic is completed, the following logs are displayed:

• Successful processing of picklist data:

• Picklists and picklist values successfully updated.
• ECPAO_PKL_QRY updated with status Successful for query nnnn, resp. mess. nnnn.

Implementing Data Migration and Replication to Employee Central

Data Migration and Replication to Employee Central PUBLIC 91
• Failures during the processing of picklist data:
• Error specic message.
• ECPAO_PKL_QRY updated with status Failed for query nnnn, resp. mess. nnnn.

Procedure

1. Go to the Analyze Application Log (SLG1) transaction.

2. Enter the ECPAO object and sub-object PICKLIST_IMPORT.
3. Make additional selections as suits your requirements and choose Execute.

2.2.2.4.4.1.2 Import Picklists and Picklist Values from

Employee Central Using File Upload

You can import picklists and picklist values from Employee Central to the SAP S∕4HANA system to use them in
Customizing when mapping Employee Central eld values to values of SAP S∕4HANA elds.

Context

To import picklists, you use the Import of Picklists from Employee Central (ECPAO_PICKLIST_WRITER) program.
This program is available in the Import Picklists from Employee Central Customizing step. You can use a transport
request to import the picklists from Employee Central. If you run the picklist import programs in an SAP S∕4HANA
test system or client system, the programs now automatically ask for a transport request, to which the imported
picklist report will be assigned.

Procedure

1. Import the picklist le from Employee Central through one of the below approaches. Download the picklists and
store the picklist le in the comma-separated values (CSV) format on a server or on your local disk.
• If the Employee Central picklist data is maintained via Picklist Center then you need to download via
import/export data tool in Employee Central.
1. Go to the Admin Center and choose the Import and Export Data tool.
2. Select the action to perform as Export data.
3. Choose Picklist-Values as the generic object.
4. Choose No for Include dependencies option.
5. Choose External Code for key preference.
6. Click Export.
• If you are using the legacy picklist, then you will have to download from the Picklist Management.

Implementing Data Migration and Replication to Employee Central

92 PUBLIC Data Migration and Replication to Employee Central
 2. On the selection screen of the ECPAO_PICKLIST_WRITER program, select your Employee Central instance and
the picklist le that you want to upload.

Selection Screen of Picklist Import Program

3. Enter the locale of the picklist labels that you want to import.

Only the labels of the locale you enter here are imported. The labels listed for other locales are ignored. You can
only choose one locale.

 Example

If you enter en_US, the labels Female and Male are imported for the gender picklist. All other labels of this
picklist, such as Femenino and Masculino for locale es_ES or Femme and Homme for locale fr_FR, are not
imported.

We recommend that you use the locale of the user who logs on to Employee Central and replicates the data
from SAP S∕4HANA.
4. Select the Update Picklist checkbox to import picklists and picklist values.
5. Optional: Carry out a test run of the program to check the data that will be uploaded to SAP S∕4HANA.
6. Clear the Test Run checkbox and execute the program to upload the data from the Employee Central picklist
le into the following tables:
• Picklists Imported from Employee Central (ECPAO_PIKLST_ENT)
• Picklist Values Imported from Employee Central (ECPAO_PIKLST_VAL)

The program generates an SAP S∕4HANA ID for each picklist. This ID is used as the unique key to identify each
picklist without ambiguity in the SAP S∕4HANA system.

 Example

248 could be the SAP S∕4HANA picklist ID that is generated for the addressType picklist.

7. Optional: To delete picklists and picklist values that you have imported to the SAP S∕4HANA system, select the
Delete Picklist checkbox and execute the program.

Implementing Data Migration and Replication to Employee Central

Data Migration and Replication to Employee Central PUBLIC 93
  Note

You can't delete picklist values in the SAP S∕4HANA system that you have already used for value mappings
because your value mappings might become invalid. You are shown an error message if you try to delete
picklist values that are used for value mappings.

Results

You are now ready to use the picklists and picklist values in the next Customizing steps when you dene value
mappings.

 Note

Infoporter tool will decide to send either the optional ID or the external code for a eld based on the object
types (MDF/Non-MDF) in Employee Central.

2.2.2.4.4.2 Dening Value Mapping Entities

A value mapping entity combines a set of value mappings for a specic purpose (for example, gender code value
mappings).

Context

You dene value mapping entities in the Dene Value Mapping Entities Customizing step (view
V_ECPAO_VALUENTY). The easiest way to create value mapping entities is to copy the sample entities by choosing
the Copy Sample Value Mapping pushbutton. You can also create country specic value mapping entries and create
a new value mapping entity using the Create Value Mapping Entity and Dene Ctry. Spec. Value Mapping Entries
pushbuttons from the primary mapping details screen.

Copy Sample Value Mapping

Implementing Data Migration and Replication to Employee Central

94 PUBLIC Data Migration and Replication to Employee Central
  Tip

If you want to check rst which sample value mapping entities are available, choose the Show Sample Value
Mapping pushbutton.

Create Value Mapping Entity/Dene Country Specic Value Mapping Entries

You'll get a list of all standard entities provided for the integration, which you can adjust to your needs.

Copied Standard Value Mapping Entities

During the employee replication from Employee Central, the value mapping type Organizational Object Keys
from Mapping Table is considered for mapping of organizational objects like Position, Departments, Divisons
etc. When these types are maintained in the value mapping entity, the data replication uses the mapping from
SFIOM_KMAP_OSI key mapping table. This table maps the keys of organizational objects (such as divisions or job
classications) from Employee Central to organizational object IDs (such as organizational unit IDs or job IDs) from

Implementing Data Migration and Replication to Employee Central

Data Migration and Replication to Employee Central PUBLIC 95
ERP. For value mapping entities with this mapping type, you need not enter the Employee Central and ERP values
that are to be mapped in the Dene Value Mapping Details Customizing activity. Instead, the replication uses the
mapping that is dened in the key mapping table. When this value mapping type is assigned, the type of the related
object (for example, Business Unit) also needs to be specied (column 'EC Org. Object Type' in the maintenance
view).

Procedure

1. To create a value mapping entity from scratch, enter a name and description. If you want to use a standard
entity, you need to keep its name, but you can adjust the description.
2. Specify how the values are to be mapped. If you want to use a standard entity, we recommend that you use the
suggested mapping types.
• Picklist mapping using the Organization eld from the picklist
Use this type if the picklist value you want to map is an external code. This is the case, for example, for
Employee Central elds such as Department and Division.
• Picklist mapping using the External Code eld from the picklist
Use this type if the picklist value you want to map is an External Code. This is the case for most of the
picklists.
• Picklist mapping using the Option ID.
Use this type if the picklist value you want to map works only with Option ID.

 Tip

Use this method only if you have been already using this is in the past. The infoporter report now
automatically derives the option id even if external code mapping is maintained and so you need not
congure the option id explicitly in the value mapping details.

• Picklist mapping using the Label eld from the picklist

Use this type if the picklist value you want to map is the picklist label.
• Foundation Object Key mapping
Use this type to map, for example, Employee Central event reasons to personnel actions from SAP
S∕4HANA.

 Example

You want to map the Employee Central event reason DATAREORG to the personnel action 02
(Organizational Reassignment).

• Generic Object Key mapping

Use this type to map keys of generic objects from Employee Central to the corresponding SAP S∕4HANA
keys.
• Standard mapping
Use this type for a standard mapping of Employee Central and SAP S∕4HANA values, for which no picklist
ID is required. Standard mappings are predened in the SAP S∕4HANA system and can't be changed.
3. To make available picklist values you've imported to the SAP S∕4HANA system from Employee Central in the
value mapping details, assign a picklist to the value mapping entity.

Implementing Data Migration and Replication to Employee Central

96 PUBLIC Data Migration and Replication to Employee Central
 Choose Picklist for Value Mapping Entity

Picklist Assigned to Value Mapping Entity

This enables you to choose the imported picklist values in the Employee Central Key eld when you actually
map the values. If you don't assign a picklist, you can still enter keys in the Employee Central Key eld, but you
can't choose from the imported picklist values.
4. To make available input help values from an infotype eld in the value mapping details, specify the SAP
S∕4HANA value help.

This is a combination of the technical name of the infotype table (such as PA0002) and the technical name of
the infotype eld (such as GESCH), connected with a hyphen (as in PA0002-GESCH). This means that you can
choose the input help values from the Gender Key (GESCH) eld of the Personal Data (0002) infotype in the
ERP Key eld when you actually map the values. It does not mean that you can only use the value mapping
entity for the GESCH eld. If you want to use a sample entity, we recommend that you use the suggested SAP
S∕4HANA value helps.

SAP S∕4HANA Value Help Assigned to Value Mapping Entity

Results

You are now ready to map the actual Employee Central and SAP S∕4HANA values in the next Customizing steps,
where you dene the value mapping details.

Implementing Data Migration and Replication to Employee Central

Data Migration and Replication to Employee Central PUBLIC 97
2.2.2.4.4.3 Updating the Reference Picklist Tables to
Reuse Value Mappings in the Productive System
Environment

You can store picklist entries in reference tables to reuse value mappings you've dened in your test SAP S∕4HANA
system in the productive system landscape.

Context

Some of the picklist elds in Employee Central accept only Option Id as input in the Odata API. Hence the
infoporter tool would send the option ids of the corresponding values of the picklist. Also you might have
congured and dened the option ids in the value mapping. When picklists used for web service transfer are
transported from the test to the productive SAP S∕4HANA system or client, the option IDs can change. This means
that the value mappings you've dened in the test SAP S∕4HANA system or client and transported from there don't
work for data transfer from the productive SAP S∕4HANA system to the productive Employee Central instance.

 Example

Let's say, in your test system and instance the Marital Status picklist uses the option ID 16696 for Single
(which has the external code S), and 16697 for Married (which has the external code M). But in the productive
system and instance, Single (S) uses the option ID 5673 and Married (M) uses the option ID 5674. After you've
transported value mappings from your test to your productive system, data transfer to the Employee Central
productive instance shows an error because the option IDs 16696 and 16697 don't exist there. 16696 needs to
be converted to 5673 and 16697 needs to be converted to 5674 to make data transfer work.

To avoid this kind of error, you can store the picklist entries in the following reference tables:

• Reference Picklists Imported from Employee Central (ECPAO_REFPIK_ENT)

• Reference Picklist Values Imported from Employee Central (ECPAO_REFPIK_VAL)

Here's what you need to do in detail:

Procedure

1. Import picklists from your test Employee Central instance to your SAP S∕4HANA test system or client. To do
this, run the Import of Picklists from Employee Central (ECPAO_PICKLIST_WRITER) program or the Report to
Import Picklist using the Generic OData Service Call (ECPAO_IMPORT_PICKLIST) with the Reference Picklist
Tables checkbox not selected.
2. Dene your value mappings in the test system or client.
3. Transport the value mappings from the test to the productive SAP S∕4HANA system or client.

If you now run the data extraction program, errors will be shown because now other option IDs are used.
4. Update the reference picklist tables in the productive SAP S∕4HANA system or client. To do this, run the Import
of Picklists from Employee Central or Report to Import Picklist using the Generic OData Service Call program
with the Reference Picklist Tables checkbox selected.

Implementing Data Migration and Replication to Employee Central

98 PUBLIC Data Migration and Replication to Employee Central
Results

Now the data extraction program can compare the entries in the picklist tables with the entries in the reference
picklist tables (based on the picklist ID and the external code) and replace the option IDs accordingly.

2.2.2.4.4.4 Converting External Code to Option ID Due

to Dierent Option ID's in Dierent Employee
Central Systems

Option ID usually varies from one Employee Central system to another system. Since the Option ID is dierent, you
need to dene the value mapping details again when you congure the data for a new system as per the Option ID’s
for the new system.

Context

Value mapping entities are dened based on the type of the communication channel that you use (Web service or
csv mode). If you use Web service-based replication, the suitable mapping type is usually the Option ID. Since the
Option ID varies from one EC instance to another EC instance, you can use the following approach:

• Value mapping entities of type External Code would be converted to Option ID for web service mode
of replication. So you can dene the value mapping entity of type Picklist-external code in the view
V_ECPAO_VALUENTY and then dene the external code in the EC keys for the corresponding SAP S∕4HANA
values in the view V_ECPAO_VALENTY which can be used across dierent Employee Central systems. If the
value mapping entity mapped EC entity is non MDF entity, then internally we are converting the EC key value
from external code to option ID. If the value mapping entity mapped EC entity is MDF entity. then we are not
converting the EC key value and sending the same external code. Converting the external code to option id is
based on the EC Entity. If value mapping entity mapped EC entity is Non MDF entity, then internally we are
converting EC key value from external code to option id. If value mapping entity mapped EC entity is MDF entity
then we are not converting the EC key value and sending the same external code.
• If the external code is same on SAP S∕4HANA and Employee Central systems then you can just dene the
value mapping entity of type Picklist external code in view V_ECPAO_VALUENTY leaving the value mapping
details view V_ECPAO_VALENTY empty. Internally Option ID would be fetched based on the external code of the
picklist and sent to Employee Central.

Procedure

1. Execute the picklist writer report ECPAO_PICKLIST_WRITER with the option “ Update picklist” on the test
system
2. Congure the value mapping entity table V_ECPAO_VALUENTY as per your requirement. You can congure
the entity with the mapping mode Picklist -external code where the original mapping mode expected is
Picklist-option ID. Enter the EC picklist ID using the search help.

Implementing Data Migration and Replication to Employee Central

Data Migration and Replication to Employee Central PUBLIC 99
3. Enter the values in the value mapping details view V_ECPAO_VALENTY. You can skip this step if the external
code is same on SAP S∕4HANA and Employee Central systems for the value mapping entities with the mapping
mode picklist-external code.
4. Transport all these changes to production system.
5. Execute the picklist writer report ECPAO_PICKLIST_WRITER by selecting the Reference Picklist table check
box with the option Update picklist on the production system.

2.2.2.4.4.5 Dening Value Mapping Details

The value mapping details actually map SAP S∕4HANA values to the corresponding Employee Central values.

Procedure

1. Go to the Dene Value Mapping Details Customizing activity (view V_ECPAO_VALENTY).

2. Map SAP S∕4HANA keys and the corresponding Employee Central keys.

If the value mapping entity has a picklist ID and a SAP S∕4HANA value help assigned, you can select suitable
picklist values in the EC Key eld and corresponding input help values in the ERP Key eld.

Choose SAP S∕4HANA Key for Value Mapping

Implementing Data Migration and Replication to Employee Central

100 PUBLIC Data Migration and Replication to Employee Central
 Choose Employee Central Key for Value Mapping

You can also enter the wildcard * in the ERP Key eld. If only the wildcard is dened in the value mapping
details, any SAP S∕4HANA value will be mapped to the Employee Central key for the eld that uses this value
mapping entity. If the wildcard is dened in addition to specic SAP S∕4HANA keys, the system rst checks for
the specic keys. If an Employee Central key is mapped to a specic SAP S∕4HANA key, this mapping is used.
For all other SAP S∕4HANA values, the Employee Central key mapped to the wildcard is used.

Results

The data extraction programs can now use the value mappings. When extracting data, they will replace the SAP
S∕4HANA keys by the assigned Employee Central keys if a value mapping is dened for the corresponding eld
mapping. If no value mapping is available, they won't map any values for the specic eld and use the values from
SAP S∕4HANA as they are.

2.2.2.4.4.6 Dening Value Mapping Details

The value mapping details actually map SAP S∕4HANA values to the corresponding Employee Central values.

Procedure

1. Go to the Dene Value Mapping Details Customizing activity (view V_ECPAO_VALENTY).

2. Map SAP S∕4HANA keys and the corresponding Employee Central keys.

If the value mapping entity has a picklist with external code (as an example) and a SAP S∕4HANA value help
assigned, you can select suitable picklist values in the EC Key eld and corresponding input help values in the
key elds dened in the SAP S∕4HANA system.

Implementing Data Migration and Replication to Employee Central

Data Migration and Replication to Employee Central PUBLIC 101
 Choose SAP S∕4HANA Key for Value Mapping

Choose Employee Central Key for Value Mapping

You can also enter the wildcard * in the ERP Key eld. If only the wildcard is dened in the value mapping
details, any SAP S∕4HANA value will be mapped to the Employee Central key for the eld that uses this value
mapping entity. If the wildcard is dened in addition to specic SAP S∕4HANA keys, the system rst checks for
the specic keys. If an Employee Central key is mapped to a specic SAP S∕4HANA key, this mapping is used.
For all other SAP S∕4HANA values, the Employee Central key mapped to the wildcard is used.

Results

The data extraction programs can now use the value mappings. When extracting data, they will replace the SAP
S∕4HANA keys by the assigned Employee Central keys if a value mapping is dened for the corresponding eld
mapping. If no value mapping is available, they won't map any values for the specic eld and use the values from
SAP S∕4HANA as they are.

Implementing Data Migration and Replication to Employee Central

102 PUBLIC Data Migration and Replication to Employee Central
2.2.2.4.4.7 How to Use the Sample Value Mapping for Employee
Data Integration

We provide sample value mapping entities for employee data and also value mapping details for some of the
sample value mapping entities. Here's how to use them.

Value mapping entities are assigned to eld mappings in the Dene Field Mapping for Employee Data Customizing
step (view cluster VC_ECPAO_MAP). The sample content provided there contains some sample value mapping
entities. Some of these sample value mapping entities, such as GENDER_CODE_CSV, are provided together with
sample value mapping details. But most of the sample value mapping entities, such as ADDRESS_TYPE_CSV, don't
have any details assigned. In the second case, you need to dene the value mapping details. Otherwise the value
mapping entity isn't usable. Here are more details about how to handle these situations:

Use case 1: A sample value mapping entity is available together with value
mapping details

Let's say the value mapping entity GENDER_CODE_CSV is assigned to the eld mapping of the gender Employee
Central eld in the VC_ECPAO_MAP view cluster. A sample value mapping entity with this name is provided,
as you can see in the V_ECPAO_VALENT_S view. (To display this view, go to the Dene Value Mapping Entities
Customizing activity and choose Show Sample Value Mapping). Sample value mapping details are assigned to the
GENDER_CODE_CSV value mapping entity in the V_ECPAO_VALMAP_S view. For example, for the Female gender
code, the Employee Central key F and the SAP S∕4HANA key 1 are mapped here.

Since you want to use this sample value mapping entity and the assigned sample value mapping details, you
go to the Dene Value Mapping Entities Customizing activity and copy the sample value mapping. This copies
the entity to the V_ECPAO_VALUENTY view – but the details are not copied to the V_ECPAO_VALENTY view
(which is contained in the Dene Value Mapping Details Customizing activity). To check the details, you can go
to the V_ECPAO_VALMAP_S view using the Edit Table Views (SM30) transaction and display the details for the
GENDER_CODE_CSV value mapping entity from there. If you want to use them, make the same entries in the
V_ECPAO_VALENTY view.

When extracting data for the gender eld, the data extraction program rst checks if a suitable GENDER_CODE_CSV
custom value mapping entity exists in the V_ECPAO_VALENTY view. Since this is the case, it uses this entity and
the assigned value mapping details. If no custom value mapping entity exists, the program can still use the sample
value mapping entity from the V_ECPAO_VALMAP_S view together with the assigned sample value mapping details
as a fallback.

Use case 2: Sample value mapping entity is available without sample value
mapping entries

Let's say the value mapping entity ADDRESS_TYPE_CSV is assigned to the eld mapping of the address-type
Employee Central eld in the VC_ECPAO_MAP view cluster. A sample value mapping entity with this name is
provided, as you can see in the V_ECPAO_VALENT_S view. But no sample value mapping entries are assigned
to the ADDRESS_TYPE_CSV value mapping entity in the V_ECPAO_VALMAP_S view. Since you want to use this
value mapping entity, you go to the Dene Value Mapping Entities Customizing activity and copy the sample value

Implementing Data Migration and Replication to Employee Central

Data Migration and Replication to Employee Central PUBLIC 103
mapping. In addition, you need to go to the Dene Value Mapping Details Customizing activity and map Employee
Central keys and SAP S∕4HANA keys. For example, for the address type Home Address, you map the Employee
Central key Home and the SAP S∕4HANA key 3. If you forget to dene the details, you are shown a warning message
in the VC_ECPAO_MAP view cluster for the eld mapping of the address-type Employee Central eld.

When extracting data for the address-type eld, the data extraction program rst checks if a suitable
ADDRESS_TYPE_CSV custom value mapping entity exists in the V_ECPAO_VALENTY view. Since this is the case,
it uses this entity and the assigned value mapping details. If no custom value mapping entity exists, the program
cannot use the sample value mapping entity from the V_ECPAO_VALMAP_S as a fallback, because this entity
doesn't have any value mapping details assigned.

Note

If you choose Copy Sample Value Mapping, all entities that are available in the V_ECPAO_VALENT_S (S table) view
are copied to the V_ECPAO_VALUENTY (C table) view. This includes the value mapping entities for organizational
data as well as employee data. If you only need some of the sample value mapping entities, choose Copy Sample
Value Mapping and then remove all entities that you don't need from the V_ECPAO_VALUENTY view.

Once you've made entries in the V_ECPAO_VALUENTY view (either by copying or by entering them manually), you
can no longer copy the sample value mapping entities. Either remove all entries from the V_ECPAO_VALUENTY view
and copy again, or show the sample value mapping entities and use them as an example for making the entries
manually.

2.2.2.4.4.8 Dening Value Mapping Based on Constants

You can use an SAP S∕4HANA eld that always holds the same value to transfer a constant value to a specic
Employee Central eld.

Context

 Example

An infotype eld from SAP S∕4HANA always returns an empty value. You use this to always set the mapped
eld to true in Employee Central.

It doesn't matter which SAP S∕4HANA eld you use – the important point is to know that the eld will always hold
the same value.

Procedure

1. Dene a suitable eld mapping in the Primary Mapping view of the Dene Field Mapping for Employee Data
Customizing step.

Implementing Data Migration and Replication to Employee Central

104 PUBLIC Data Migration and Replication to Employee Central
  Example

You know that the Object Identication (OBJPS) eld of the Communication (0105) infotype (subtype
Private Phone (CELL)) will always be empty. You map this eld to the isPrimary Employee Central eld
because you want the isPrimary elds to always hold the value true.

Primary Mapping for Constant

2. Dene a value mapping entity in the Dene Value Mapping Entities Customizing step.
3. Dene the value mapping details for this entity in the Dene Value Mapping Details Customizing step.

 Example

You dene an IS_PRMARY value mapping entity and map the SAP S∕4HANA key blank to the Employee
Central key true.

Implementing Data Migration and Replication to Employee Central

Data Migration and Replication to Employee Central PUBLIC 105
 Value Mapping Details for Constant

Results

Since the mapped SAP S∕4HANA eld has a constant value, data replication will always transfer the same value to
the Employee Central eld.

 Example

The Object Identication (OBJPS) eld is always blank in SAP S∕4HANA, so the mapped isPrimary eld will
always be set to true in Employee Central.

2.2.2.4.4.9 Dening Value Mapping Details Depending on

Employee's Country Grouping

Country-specic value mapping details actually map SAP S∕4HANA values to the corresponding Employee Central
values, depending on the country version.

Procedure

1. Go to the Dene Value Mapping Details Depending on Employee's Country Grouping Customizing activity (view
V_ECPAO_VALENTYC).
2. Map SAP S∕4HANA keys and the corresponding Employee Central keys as described in the previous section,
and additionally assign ISO codes.

Implementing Data Migration and Replication to Employee Central

106 PUBLIC Data Migration and Replication to Employee Central
 Value Mapping Depending on Employee's Country Grouping

Results

The data extraction programs can now use the value mappings. When extracting data, they will replace the SAP
S∕4HANA keys by the assigned Employee Central keys if a value mapping is dened for the corresponding eld
mapping. If a suitable country-specic value mapping is dened for the ISO code that corresponds the employee's
country grouping (MOLGA), they will use this mapping. If no country-specic value mapping is available, they'll
use the country-independent value mapping. If no value mapping is available, they won't map any values for the
specic eld and use the values from SAP S∕4HANA as they are.

2.2.2.4.5 Formatting the Employee Central Fields by Value

Conversion during the Migration of Data to
Employee Central

You can now format the Employee Central elds by using value conversion when migrating or replicating the data to
Employee Central system.

Before you migrate the data to Employee Central, you might have to format the ERP eld for the transformation
template group to convert this value to a valid Employee Central value. Value conversion enables you to format the
value of the Employee Central elds by maintaining a sequence of supported operations. This value conversion is
performed for the Employee Central elds after the eld mapping and the value mapping is done for the Employee
Central elds based on the congurations. The conversion supports a set of arithmetic and string operations which
can be used in a sequence. You can dene the sequence at which the dierent value conversion operations that
needs to be executed. There are two customizing views available, one will be generic value conversion view and the
other view is based on country or linking eld. The customizing view can be maintained at each Employee Central
eld level for a particular transformation template.

 Note

There are standard value conversion rules provided by SAP. Currently only country-specic value conversion
content is provided by SAP.

The value conversion for a eld is congured in the view cluster under Generic Value Conversion and Country
Specic Value Conversion. You can now see if a generic conversion rule or country specic conversion rule is

Implementing Data Migration and Replication to Employee Central

Data Migration and Replication to Employee Central PUBLIC 107
already congured for any EC eld from the primary mapping screen. If the generic conversion rule or country
specic conversion rule is already applied for any EC eld, then the Gen. Value Conv. and Country Spec. Value Conv.
checkboxes would be selected.Following elds to be maintained while using the conversion logic:

Field Description

HCM Localization Value of Employee Central linking eld (required only in case of
country-specic value conversion)

Seq No Sequence number for multiple actions, order of actions is

based on this number

CONV_RULE Supported value conversion rules

PARAMETER_1 Parameter 1 for rule (function of parameter depends on rule

selected)

PARAMETER_2 Parameter 2 for rule (function of parameter depends on rule

selected)

PARAMETER_EC_FLD Parameter for Employee Central eld ID

The Employee Central eld after the formatting based on the value conversion would be migrated to the
corresponding EC eld.

 Note

If you want to enter a single-space character in the view cluster, you must use <nbsp>.

Operations supported for value conversion:

Arithmetic operations - Multiplication with a number

Parameter for Employee

Parameter 1 Parameter 2 Central feld Description

Value to be multiplied with. Nil Nil Multiply with a constant value.

Replace using patterns with string/Employee Central eld

Parameter for Employee

Parameter 1 Parameter 2 Central feld Description

Pattern (any standard Regular Constant string Employee Central eld Id Replace the characters in
expression) Employee Central eld value
matching the pattern entered
in Parameter 1 with the con-
stant string or the value of an-
other Employee Central eld

Implementing Data Migration and Replication to Employee Central

108 PUBLIC Data Migration and Replication to Employee Central
  Example

EC feld value Sequence number Operation Parameter1 Parameter2 Result

First_Middle-Sur- 1 Replace using _ / First/Middle-Sur-

name patterns with name
string/EC eld

2 Replace using - \ First/Middle\Sur-

patterns with name
string/EC eld

3 Replace using Middle <nbsp> First/ \Surname

patterns with
string/EC eld

 Tip

For more information on Regular Expression, see ABAP - By Theme Process Internal Data Byte String
and Character String Regular Expressions in the ABAP keyword documentation. For testing the regular
expression, you can use the report program DEMO_REGEX_TOY.

Append with string/EC eld

Parameter for Employee

Parameter 1 Parameter 2 Central feld Description

String/Character to be used Constant String Employee Central eld Id Concatenate the Employee
as separator Central eld value with the
constant string/ EC eld in
parameter 2 by sufxing the
Employee Central eld sepa-
rated by the characters in Pa-
rameter 1

 Example

Sequence Parameter for

EC feld value number Operation Parameter1 Parameter2 EC Field Result

ABCD 1 Append with 1234 ABCD1234

string/EC eld

2 Append with - Test ABCD1234-Test

string/EC eld

Implementing Data Migration and Replication to Employee Central

Data Migration and Replication to Employee Central PUBLIC 109
 Sequence Parameter for
EC feld value number Operation Parameter1 Parameter2 EC Field Result

3 Append with / 10 ABCD1234-

string/EC eld Test/string1

 Note
Assuming
that the
value for
the EC eld
is string1.

Adjust string to length

Parameter 1 Parameter 2 Parameter for EC feld Description

Length to be adjusted to Filler characters to be used in Nil Adjust the Employee Central
case the EC value length is eld value to a xed length,
less than the parameter1 which can be either shorter
or greater than the original
length and ll with characters
in-case the length of the value
is less that the xed length.

 Example

EC feld value Sequence number Operation Parameter1 Parameter2 Result

ABCD 1 Adjust string to 10 X ABCDXXXXXX

length

Prepend with string/Employee Central eld

Parameter 1 Parameter 2 Parameter for EC feld Description

String/Character to be used Constant String EC eld Id Concatenate the Employee

as separator Central eld value with the
constant string/ Employee
Central eld in parameter 2
by prexing the Employee
Central eld separated by the
characters in Parameter 1.

Implementing Data Migration and Replication to Employee Central

110 PUBLIC Data Migration and Replication to Employee Central
  Example

EC feld value Sequence number Operation Parameter1 Parameter2 Result

ABCD 1 Prepend with - Test Test-ABCD

string/EC eld

Replace with string/EC eld

Parameter 1 Parameter 2 Parameter for EC feld Description

Nil Constant string EC eld Id Replace the Employee Central

eld string value irrespective
of the content with the con-
stant string or the value of an-
other EC eld.

 Example

EC feld value Sequence number Operation Parameter1 Parameter2 Result

ABCD 1 Replace with con- Test Test

stant/EC eld

Split before string/character

Parameter for Employee

Parameter 1 Parameter 2 Central feld Description

String/character to be used Nil Nil Split at the rst occurrence of

for splitting the string/character in param-
eter 1 and return the substring
before parameter 1.

 Example

EC feld value Sequence number Operation Parameter1 Parameter2 Result

ABCD-Test 1 Split before string/ - ABCD

character

Implementing Data Migration and Replication to Employee Central

Data Migration and Replication to Employee Central PUBLIC 111
Split after string/character

Parameter for Employee

Parameter 1 Parameter 2 Central feld Description

String/character to be used Nil Nil Split at the rst occurrence of

for splitting the string/character in param-
eter 1 and return the substring
after parameter 1.

 Example

EC feld value Sequence number Operation Parameter1 Parameter2 Result

ABCD-Test 1 Split after string/ - Test

character

Edit using pattern

Parameter for Employee

Parameter 1 Parameter 2 Central feld Description

Mask Nil Nil Simple insertion of charac-

ters/strings at specic posi-
tions of Employee Central eld
string Eg:- AAABBBCCC, to
convert this into a string like
– AAA-BBB/CCC, mask can
be given as : ___-___/___ Each
underscore represents a char-
acter of the incoming string
and nal output string will
have the additional characters
given in mask .

 Example

EC feld value Sequence number Operation Parameter1 Parameter2 Result

AABBCCDD 1 Edit using pattern __:__/__+__ AA:BB/CC+DD

Implementing Data Migration and Replication to Employee Central

112 PUBLIC Data Migration and Replication to Employee Central
Check and Replace

Parameter for Employee

Parameter 1 Parameter 2 Central feld Description

String to be compared with String to be used for replace- ID of the Employee Central Replace the value of the
ment eld to be used for compari- Employee Central eld with
son the string in Parameter 2,
only if the value of EC elds
mentioned in Parameter for
EC eld (another eld from
the same Employee Central
entity) is same as string men-
tioned in Parameter 1.

 Example

Sequence Parameter for

EC feld value number Operation Parameter1 Parameter2 EC Field Result

ABCD 1 Check and re- true TEST 10 TEST

place
 Note
Assuming
that the
Employee
Central
eld 10 is a
boolean
number.

 Note

Check and Remove and Check and Remove when doesn’t match rules are not supported in the ERP to EC
direction.

Implementing Data Migration and Replication to Employee Central

Data Migration and Replication to Employee Central PUBLIC 113
Sample scenario with multiple operations

 Example

Parameter for
Sequence Employee
EC feld value number Operation Parameter1 Parameter2 Central feld Result

AA-BB/CC 1 Split before <nbsp> AA-BB/CC

Test_string string/charac-
ter

2 Replace using /CC$ AA-BB

patterns with
string/EC eld

3 Append with + 10 AA-BB+string1

string/EC eld
 Note
Assuming
that the
value for
the EC eld
is
string1.

4 Prepend with / Constant Constant/AA-

string/EC eld BB+string1

2.2.2.4.6 Using Assignment ID in SAP S∕4HANA Integration

with Employee Central

What use of assignment ID (assignment_id_external) in SAP S∕4HANA means for integration with an Employee
Central system.

Using assignment ID is helpful if you have a heterogeneous system landscape with multiple cross-system business
processes. For example, if you integrate Employee Central with an ERP system for Payroll and also integrate SAP
Concur with Employee Central and an ERP system for Financials. All integrated systems run business processes
around employees and therefore generate system-specic employee IDs. But you want to use one unique identier
to be able to easily identify employee data that belongs to the same business context. Such as determine which
accruals in the ERP Payroll system belong to which Financials vendor and which employment in Employee Central.

For more information, see Assignment ID in Managing User Information.

Implementing Data Migration and Replication to Employee Central

114 PUBLIC Data Migration and Replication to Employee Central
2.2.2.4.6.1 Important Notes About Assignment ID in Employee
Central Integration with an ERP System

If you plan to integrate Employee Central with SAP S/4HANA (on-premise edition or SAP S/4HANA Cloud Private
Edition) or SAP ERP, consider the following before you enable use of assignment ID in Employee Central.

Data Migration to Employee Central

Before you migrate employees from your SAP S/4HANA or SAP ERP system to Employee Central, make sure that
the following prerequisites are ullled:

• To include the assignment ID during the migration process, you need to enable the switch ERP to EC/EC to
ERP (BIB): Activate Assignment ID External in the view V_ECPAO_CONSTANT using the Maintain the Constant
Values Customizing activity.
• If the ERP to EC/EC to ERP (BIB): Activate Assignment ID External eld is switched on, the Assignment ID
External eld is included in the User, Employment, and Global Assignment entities during the migration of the
employee data.
• Assignment ID must be enabled in the following entities:
• User
• Employment Details
• Global Assignment Details
Use the Manage Business Conguration admin tool to do so.

Data Replication from Employee Central

Before you replicate employee data from Employee Central to your SAP S/4HANA or SAP ERP system, make sure
that the following prerequisites are ullled:

• You can only use assignment ID if you set up a new integration project for the Core Hybrid HCM deployment
option. You can’t switch a running integration to using assignment ID.
• You must set up a business rule to generate assignment IDs in Employee Central. Assignment IDs generated by
this business rule must comply with the format used for personnel numbers in the SAP S/4HANA or SAP ERP
system. The business rule must also be able to handle error situations.
• In the Employment Settings Conguration object you create in Employee Central, Activate "Generate
Assignment ID External" by Using a Business Rule must be set to Yes.
For more information, refer to Creating the Employment Settings Conguration Object.
• The Assignment ID eld must be set up in your Employee Central data model in a way that complies with
the format used for personnel numbers in the SAP S/4HANA or SAP ERP system. That is, it must be eight
characters long and can only contain numeric values, no letters.
• You must ensure that the behavior for creating new employments in Employee Central is the same as for
creating new personnel numbers in the SAP S/4HANA or SAP ERP system. For example, you must have a
new employment created when transferring an employee to a new country/region in Employee Central. If you
perform an international transfer using the same employment, the SAP S/4HANA or SAP ERP system raises
an error message and aborts replication of employee data from Employee Central.

Implementing Data Migration and Replication to Employee Central

Data Migration and Replication to Employee Central PUBLIC 115
• Once you’ve enabled the use of assignment ID in Employee Central integration with an SAP S/4HANA or SAP
ERP system, ensure that no function import changes the assignment IDs in Employee Central.
• Once you’ve enabled the use of assignment ID in Employee Central and replicated employee data to the SAP
S/4HANA or SAP ERP system, we recommend that you don't disable assignment ID again. Otherwise, you
must also disable use of assignment ID in your SAP S/4HANA or SAP ERP system and adjust the number
ranges you use for creating personnel numbers there. That is, reverting to the previous behavior causes major
administration eort.

2.2.2.4.6.2 Conguring Assignment ID for Employee Central

Integration with SAP S∕4HANA and Migrating to
Employee Central

Set up assignment ID for integration of Employee Central with an SAP S∕4HANA system. Once assignment ID is set
up, migrate your employees to Employee Central, using personnel numbers from SAP S∕4HANA as assignment IDs
in Employee Central.

Prerequisites

You enabled use of assignment ID in Employee Central. And you made sure that the requirements listed in the
important notes section for assignment ID in Employee Central integration with SAP S∕4HANA are met.

Implementing Data Migration and Replication to Employee Central

116 PUBLIC Data Migration and Replication to Employee Central
Context

Here's an overview of the setup and migration process:

Setting Up and Migrating Assignment ID for Employee Central Integration With SAP S∕4HANA

Procedure

1. Analyze the number ranges you dened in the SAP S∕4HANA system from which you plan to migrate employee
master data to Employee Central.

When doing so, consider that the SAP S∕4HANA number range logic will be replaced by business rules in
Employee Central. Most probably you’re currently using an internal number range so that personnel numbers
are assigned by the SAP S∕4HANA system automatically. Once assignment ID is turned on, you can no longer
use this internal number range. You must use an external number range because only then personnel numbers
can be assigned by an external system (that is, by Employee Central).

Implementing Data Migration and Replication to Employee Central

Data Migration and Replication to Employee Central PUBLIC 117
2. Dene a business rule in Employee Central for generating assignment IDs, to replace the number range logic
you currently use in your SAP S∕4HANA system for generating personnel numbers.
3. Enable use of assignment ID in Employee Central. Make sure that the Assignment ID eld is an 8-digit eld in
your Employee Central data model.
4. Enable use of assignment ID in SAP S∕4HANA.

To do so, go to Customizing of Business Integration Builder and choose Basic Settings Maintain the
Constant Values . Add the constant ERP to EC/EC to ERP (BIB): Activate Assignment ID External and set the
constant value to X.
5. Migrate employee data from your SAP S∕4HANA system to Employee Central.

The migrated employees are allocated the personnel number from the SAP S∕4HANA system as assignment
ID.

Results

You successfully set up assignment ID and migrated your personnel numbers from SAP S∕4HANA to Employee
Central, to use them as assignment IDs.

Next Steps

You can now run an initial load and then start the regular replication of assignment IDs either from SAP S∕4HANA to
Employee Central or from Employee Central to SAP S∕4HANA.

2.2.2.4.7 Dening Employee Data-Related Settings for Your

Employee Central Company

Make additional settings for the Employee Central company you've dened before in the Dene Employee Data
Settings for Employee Central Company Customizing activity (view V_ECPAO_CMPNY_EE).

Procedure

1. Choose your Employee Central company ID.

2. Specify how the following Employee Central elds are to be mapped to SAP S∕4HANA:
• user_id
You can choose from the following mapping modes:
• Standard mapping (PERNR): The user_id eld is mapped to the Personnel Number (PERNR) eld in
SAP S∕4HANA.

Implementing Data Migration and Replication to Employee Central

118 PUBLIC Data Migration and Replication to Employee Central
 • BAdI mapping: If you have specic requirements, you create a Business Add-In (BAdI)
implementation of the Mapping of User ID, Person ID, User Name, and Object ID
(EX_ECPAO_EMP_USYID_PRN_UNM_MAP) BAdI to dene the mapping.
• person_id_external
You can choose from the following mapping modes:
• Standard mapping (CP): The person_id_external eld is mapped to the central person (CP) in SAP
S∕4HANA.
• Infotype mapping (0709): The person_id_external eld is mapped to the SAP S∕4HANA infotype
Person ID (0709).
• BAdI mapping (see above)
• username
You can choose from the following mapping modes:
• Standard mapping (PERNR): The username eld is mapped to the Personnel Number (PERNR) eld in
SAP S∕4HANA.
• Infotype mapping (0105/001): The username eld is mapped to the SAP S∕4HANA infotype
Communication (0105), subtype System User Name (SY-UNAME) (0001).
• BAdI mapping (see above)

 Note

We always ensure that employee gets a new personnel number while undergoing any new international
transfer HR process. Incase if an employee was earlier migrated using Reuse Existing Employment for
International Transfer setting, then we ensure that it will continue to work as before (data of both personnel
numbers are transferred to one employment in Employee Central) during re-migration process.

2.2.2.4.8 Dening Custom Employee Central Entities for

Employee Data Entities

An Employee Central entity represents an entity from Employee Central, such as a CSV data import template, an
OData entity, or a generic object (also known as MDF entity). You only need to dene custom Employee Central
entities if you want to transfer data from SAP S∕4HANA to an Employee Central entity for which SAP hasn't
provided a default template.

Context

In the Dene Employee Central Templates for Additional Employee Data Entities Customizing activity (view
V_ECPAO_ECTMPL) you can also see the default templates dened by SAP. If the default templates suit your
requirements, there's no need to dene any custom templates.

Implementing Data Migration and Replication to Employee Central

Data Migration and Replication to Employee Central PUBLIC 119
 Details of an Employee Central Entities

To dene custom Employee Central entities carry out the steps described below for each template that you add.

Procedure

1. Dene the basic settings.

a. Enter a unique template ID and a description. The ID has to be in the customer namespace, which means
that it has to start with a number (0* - 9*). You can enter any description.

Implementing Data Migration and Replication to Employee Central

120 PUBLIC Data Migration and Replication to Employee Central
 b. Enter the entity name. You must use the exact name of the corresponding entity in Employee Central.

To nd out about the name for OData entities and generic objects, go to the Admin Center and choose the
OData API Data Dictionary tool. For CSV data import templates, go to the Admin Center and choose the
Import Employee Data tool.
c. If you want to be able to assign your Employee Central entity to several transformation templates, select
the Multiple Use checkbox.
d. Specify if the Employee Central entity is eective dated.

 Note

If you dene a earliest transfer date for a transformation template group in the Dene Field Mapping
for Employee Data Customizing step, this date inuences eective-dated and non-eective dated
templates in dierent ways.

e. If your template refers to a generic object in Employee Central, select the Is Generic Object in EC checkbox.
f. If your template should inherit the metadata that you upload for another Employee Central entity, specify
the template that is to be used as the metadata basis.

 Note

If you make an entry in this eld for an Employee Central entity, you can't import metadata for this
template. You can only import metadata for the Employee Central entity that you've entered, meaning
the template from which the metadata is to be inherited.

 Example

The Dependent Biographical Information template inherits metadata from the Biographical Information
template. This means it uses the same data model comprising elds such as date-of-birth, country-of-
birth, or place-of-birth. You need to import the metadata for the Biographical Information template only
and can then reuse it for the Dependent Biographical Information template. You can't import metadata
for the Dependent Biographical Information template.

g. If your template refers to a generic object in Employee Central, make an entry in the Object ID Field in EC
eld. Here you enter the name of the eld that contains the external code of the generic object in Employee
Central and to which the employee ID from SAP S∕4HANA is to be transferred.

The eld must have the User data type assigned in Employee Central so that the employee ID information
from SAP S∕4HANA can be transferred to this eld. Which ID is transferred depends on the mapping that
you have dened in the Dene Employee Central Instance Customizing step. In the standard mapping, the
personnel number (PERNR) is used as the employee ID.
h. For the SAP delivered templates start date eld is already maintained. For the templates that you want to
be dened, specify the Employee Central eld (such as eectiveStartDate) in which the start date is stored
for the corresponding entity and which is to be mapped to the Start Date (BEGDA eld in SAP S∕4HANA
system.

For standard eective dated templates if the start date is specied, then the start date would be
considered as a standard eld. For standard MDF templates and custom MDF templates, start date would
not be considered as a standard eld even if it is maintained for a template.

Implementing Data Migration and Replication to Employee Central

Data Migration and Replication to Employee Central PUBLIC 121
 CSV & WS Template IS_MDF Standard Field (start-date) Standard Field (end-date)

Standard EE Templates X X

Standard EE MDF Tem- X

plates

Custom EE Templates X

Standard OM Templates X X

Standard OM MDF Tem- X X

plates

Custom OM Templates X

i. For the SAP delivered templates end date eld is already maintained. For the templates that you want to
be dened, specify the Employee Central eld (such as endDate) in which the end date is stored for the
corresponding entity and which is to be mapped to the END Date (ENDDA eld in SAP S∕4HANA system.

For standard eective dated templates if the end date is specied, then the end date would be considered
as a standard eld. For standard MDF templates and custom MDF templates, end date would not be
considered as a standard eld even if it is dened for a template.

 Note

If the start and end date elds are congured in the eld mapping table then they will be considered
for the template conguration. If they are not dened in eld mapping, then it will be read from the
templates table.

2. Dene the settings for data replication from SAP S∕4HANA to Employee Central.
a. Enter a unique sequence number.

The sequence in which the Employee Central entities delivered by SAP are transferred from SAP S∕4HANA
to Employee Central is dened by SAP. You can't change this sequence. If you dene your own template, we
recommend to use a sequence number that is higher than the numbers assigned to the Employee Central
entities that are delivered by SAP.
b. If the entity has a parent entity in Employee Central, enter the ID of the parent EC entity in the ID of
Dependent EC Template column. PaymentInformationV3, for example, is entered in the ID of Dependent EC
Template column of PaymentInformationDetailV3
c. If your template refers to a country-specic entity in Employee Central, specify the country version. If you'd
create an Employee Central entity for the PerGlobalInfoUSA template entity, for example, you would specify
the 10 (USA) country version.
d. The settings in the Deletion Supported section are only available for Employee Central templates that are
dened by SAP in the SAP namespace. You can't make any entries in the following elds:
• The Deletion Permitted ag species that data deletion can be replicated for the Employee Central
template from SAP S∕4HANA to Employee Central.
• The HRIS Element ID is used by the Compound Delete or SFOData.HrisCompoundDeletion template
when replicating the deletion of data from SAP S∕4HANA to Employee Central. The HRIS element ID is
only needed for Employee Central templates that support the replication of data deletion to Employee
Central.

Implementing Data Migration and Replication to Employee Central

122 PUBLIC Data Migration and Replication to Employee Central
 3. Dene inotype-specic settings.
a. Specify the SAP S∕4HANA infotype that is required for your Employee Central template to be able to use
it for a proper eld mapping. The infotype you specify in this eld is used by the SAP S∕4HANA system to
check if the necessary eld mapping is dened.

 Example

The Personal Data (0002) infotype is required for the Personal Information entity in Employee Central.
You can't transfer any data from SAP S∕4HANA to this entity if you haven't dened a mapping for any of
the infotype elds.

b. Only for Employee Central entities dened by SAP: An infotype can be specied that requires a special
mapping (such as the Date Specications (0041) infotype).
c. If you need a special processing for the Employee Central entity, specify the processing mode you need.
The processing mode refers to the infotype you enter in the next step. The following processing modes are
available:
• Repetitive Structure Mapping
• Object Identication Mapping
• Only for Employee Central entities dened by SAP: Time Constraint 3 Mapping
d. Enter the SAP S∕4HANA infotype for which a special processing is needed.
e. If you've selected the Object Identication Mapping processing mode, specify the object identication
(OBJID) eld for which a unique key needs to be generated.
f. If you've selected the Repetitive Structure Mapping processing mode, specify a structure that contains the
elds for which you want to use the repetitive mapping.

2.2.2.4.8.1 Supporting Country Specic Payment Information

Details

For any specic country, you can create country specic templates (ex: USA) and for other countries, you can
dene the custom templates. When you want to replicate country specic payment information details for a
non-USA country, you will have to create a custom transformation template in the view V_ECPAO_ECTMPL. While
creating the new custom transformation template, you should enter WS_16 as the dependent entity and 161 in the
upsert sequence eld. After creating the new transformation template, you will have to do the eld mapping in the
conguration.

Implementing Data Migration and Replication to Employee Central

Data Migration and Replication to Employee Central PUBLIC 123
In the eld mapping you will have to perform the ltering of the country specic records based on the BANK country
key (BANKS eld of Infotype 0009) as a linking eld. If an employee has bank details for a certain country in a
particular time segment, then the country specic payment details will be replicated only for that BANK country in
that period.

 Example

If an employee has a bank account from 1-1-2012 to 31-12-2013 in USA and another bank account from
1-1-2014 to 31-12-2015 in Mexico, then USA specic payment information details will be replicated only for the
period (1-1-2012 - 31-12-2013). For this period 1-1-2014 to 31-12-2015, only the Mexico specic details would be
replicated.

While running the country specic payment information details, you will have to include the generic payment
information details mandatorly in the same session.

Implementing Data Migration and Replication to Employee Central

124 PUBLIC Data Migration and Replication to Employee Central
2.2.2.4.9 Conguring Field Mapping for Employee Data

To enable the data extraction programs to extract the right SAP S∕4HANA information for the right Employee
Central elds, you need to map SAP S∕4HANA elds to Employee Central elds.

To map elds, you can go to the Dene Field Mapping for Employee Data Customizing step, which include the below
steps:

1. You create at least one transformation template group. A transformation template group bundles all eld
mappings that you want to use when running the data extraction program. This is the entity that you specify
on the program selection screen. From the transformation template group the data extraction program
determines all information it needs to extract data from SAP S∕4HANA elds and map it to Employee Central
eld IDs.
2. You create at least one transformation template for your transformation template group. The transformation
template groups information from the SAP S∕4HANA system that belongs together logically. It is the SAP
S∕4HANA counterpart of the Employee Central entity.
3. You dene a primary mapping for each of your transformation templates. This means you choose Employee
Central elds from the Employee Central template assigned to the transformation template, and you map
suitable SAP S∕4HANA elds to these Employee Central eld IDs.
4. If you need an additional eld mapping, for example for country-specic elds, you could also dene a
secondary eld mapping.

 Note

We also provide sample content, which contains congurable standard eld mappings, in Primary Mapping of
the Dene Field Mapping for Employee Data Customizing step. When you dene a eld mapping there, you
can easily copy these standard eld mappings using a pushbutton and then adapt them if necessary. This is
a dierent kind of sample content than the transformation template groups, templates, and eld mappings
contained in the delivered sample Customizing.

2.2.2.4.9.1 Creating a Transformation Template Group for

Employee Data

A template group bundles all eld mappings that you want to use when transferring data from SAP S∕4HANA to
Employee Central.

Context

To dene template groups, you need to initially go to the Dene Transformation Template Group for Employee Data
Customizing step, which has the V_ECPAO_TTG_EE view assigned and then go to the Dene Field Mapping for
Employee Data Customizing step (view cluster VC_ECPAO_MAP) to congure the communication channel, sample
content, and the earliest transfer date.

Implementing Data Migration and Replication to Employee Central

Data Migration and Replication to Employee Central PUBLIC 125
Procedure

1. Go to Dene Transformation Template Group for Employee Data Customizing step (V_ECPAO_TTG_EE view)
and enter the preliminary details for the transformation template group that you are creating:

1. Click New Entries

2. Enter a name and description for the transformation template group.
3. Assign it to the Employee Central instance dened in the Specify Employee Central Instance ID
Customizing activity.

 Note

You will be able to modify or choose the EC instance only when you are creating a new transformation
template group.

4. Choose the replication direction ERP to EC/EC to ERP from the drop-down list box depending upto the
scenario you are running.
2. Go to Dene Field Mapping for Employee Data Customizing step (VC_ECPAO_MAP view) and enter the
communication channel, sample content, and the earliest transfer date.
1. In the transformation template group window, double click the transformation template group that you
have created.
2. Choose one of these communication channels for the transformation template group:
• CSV File-Based Transfer
Choose this communication channel if you want to use the transformation template group for the CSV
le-based data extraction.
• Web Service Transfer
Choose this communication channel if you want to use the transformation template group to transfer
data using a Web service call.
3. Select the sample content that you want to use for your transformation template group. We provide
sample content for dierent use cases.
4. Optional: Dene an Earliest Transfer date.
You can specify this date to start employee data replication at a specic point in time. This prevents the
complete history of data records being replicated from SAP S∕4HANA to Employee Central. If you dene
an earliest transfer date for a transformation template group, this date inuences eective-dated and
non-eective dated templates in dierent ways.
5. Dene if the transformation template group is available for delta replication.

 Note

You can only use transformation template groups with the Web Service Transfer communication
channel for delta replication. To make sure that the delta replication works, use a transformation
template group with the Web Service Transfer communication channel and for which the Enable for
Delta Replication checkbox is selected. There can only be one transformation template group for which
the Enable for Delta Replication checkbox is selected.

Implementing Data Migration and Replication to Employee Central

126 PUBLIC Data Migration and Replication to Employee Central
2.2.2.4.9.2 Dening Transformation Templates to Map
Employee Data Fields
The transformation template is the counterpart of the Employee Central entity. You can map elds from the
transformation template to elds from the assigned Employee Central entity.

Context

To dene a set of transformation templates for each transformation template group, you go to the Dene Field
Mapping for Employee Data Customizing step, which has the VC_ECPAO_MAP view cluster assigned.

Transformation Templates Assigned to a Transformation Template Group

Details of an Transformation Template

 Note

If you want to map managers from SAP S∕4HANA to the Job Relationship template in Employee
Central, you need a separate transformation template for each type of manager. You could, for example,
dene the transformation templates ERP_JOBREL_CUSTOM (Job Relationship - Custom Manager) and
ERP_JOBREL_MATRIX (Job Relationship - Matrix Manager).

Implementing Data Migration and Replication to Employee Central

Data Migration and Replication to Employee Central PUBLIC 127
These are the settings that you need to make for each transformation template you dene:

Procedure

1. Enter a name and description for the template.

2. Select the Is Active checkbox to dene that the template is to be used for data extraction.
3. Select the Based on Hire Date checkbox if you want to specify if the template data to be extracted is from the
hire date of the employee.
If you select this checkbox, the employee data to be extracted based on the transformation template is
retrieved using the hire date of the employee as the start date for the data records. Hire date will take
precedence of the cutover date.

 Note

Based on Hire Date option is disabled and made invisible for non-eective dated type of records. For non-
eective dated template, see How the Earliest Transfer Date Inuences Eective-Dated and Non-Eective
Dated Templates.

4. Select the Don't Merge Records checkbox to avoid the default behaviour and send the records as is from the
ERP system for the specic entity for which you have choosen this checkbox. By default when there are records
with same data but with dierent timesplits, infoporter merges these records into a single record.

If you have included global information template in your transformation template group, then you need to
ensure:
• The start date and the end date labels of the entity is maintained in the view V_ECPAO_ECTMPL.
• The country version is included in the view V_ECPAO_ECTMPL.
• The Don't Merge Records option is selected for personal information entity and all country specic global
information entities in the Transformation Template Details screen of the View Cluster.
• The entity order sequence of all the country specic global information templates dened in the view
V_ECPAO_ECTMPL should be the same value 35.
• The dependent entity for country specic global information should be maintained as personal information
entity.

 Example

Let's say the following records of the Recurring Payments/Deductions (0014) infotype exist for an
employee:

Recurring Payments/Deductions Records – Without Data Merge

Start Date End Date Wage Type Amount Currency

January 1, 2015 June 31, 2015 MW00 500 USD

July 1, 2015 December 31, 2015 MW00 500 USD

Implementing Data Migration and Replication to Employee Central

128 PUBLIC Data Migration and Replication to Employee Central
 If you select this checkbox, these infotype records are transferred separately. If you don't select this
checkbox, these infotype records are merged and the following record is transferred:

Recurring Payments/Deductions Records – With Data Merge

Start Date End Date Wage Type Amount Currency

January 1, 2015 December 31, 2015 MW00 1000 USD

5. Assign one of the default standard Employee Central entities or a custom Employee Central entity that you've
created before.

Results

You have now created a transformation template, which will be equivalent to the Employee Central entity. You can
now perform the eld mapping for the transformation template that you have created.

2.2.2.4.9.3 Dening the Primary Field Mapping for Employee

Data

You can choose Employee Central elds from the Employee Central metadata that you've uploaded to the
SAP S∕4HANA system, and you map suitable SAP S∕4HANA elds to these Employee Central elds and dene
additional transformations if needed.

Context

To dene a eld mapping for each transformation template, you go to the Primary Mapping view of the
VC_ECPAO_MAP view cluster. An easy way to dene your eld mapping is to copy the sample content we provide
and adapt it to your requirements. You can use the sample content that you've selected for your transformation
template group.

Sample Content Options in Primary Mapping View

Choose Show Sample Primary Mapping to check which sample content is available.

Implementing Data Migration and Replication to Employee Central

Data Migration and Replication to Employee Central PUBLIC 129
 Sample Content for Addresses Template

 Note

In addition to the sample content shown here, there are also predened standard mappings, which are
automatically added to the templates you use and aren't available for conguration in this Customizing activity.

Choose Copy Sample Content to copy the sample eld mappings. This includes primary mappings as well as
secondary mappings (if available).

If you want to dene your own eld mapping, here's how to do this:

Procedure

1. Choose an Employee Central eld from the assigned If you don't have any specic requirements, such as
mapping country-specic elds, you are now ready to use your eld mapping when running the data extraction
report. Otherwise, dene a secondary eld mapping in addition.Employee Central entity.

 Note

Make sure that you have imported the metadata for this. If you don't have any specic requirements,
such as mapping country-specic elds, Employee Central entity to the SAP S∕4HANA system using the
metadata import program. Otherwise no elds are available here.

2. Map each Employee Central eld to an SAP S∕4HANA eld using a suitable mapping mode:
• When you select the mapping mode Infotype Mapping, you assign an infotype or subtype eld in the
primary mapping. You can use elds from the Personnel Administration infotypes for eld mapping.
Some infotypes require a special processing such as:
• Repetitive mapping: If you enter an infotype such as Basic Pay (0008), to denote the repetitive
mapping setting in the V_ECPAO_ECTMPL view (entity creation). Eg 0008 in WS_12, you can't make
entries in the Infotype Field eld. Instead, the Repetitive Field eld is displayed. Here you can select the
infotype eld for which you want to use a repetitive mapping.
• Date type mapping: If you enter the Date Specications (0041) infotype, you can't make entries in the
Infotype Field eld either. Instead, the Date Type eld is displayed. Here you can select the date type
that you want to map.
• When you select the mapping mode Precongured Mapping, you can use mappings that were dened by
SAP in the Precongured Mapping tables (ECPAO_PREMAPPING, ECPAO_PREMAP_TT).

Implementing Data Migration and Replication to Employee Central

130 PUBLIC Data Migration and Replication to Employee Central
 • When you select the mapping mode BAdI Mapping, you can use an implementation of the Mapping of EC
and ERP Data for Data Replication to EC (EX_ECPAO_EMP_DATA_EXTRACT_OUT) BAdI to dene the eld
mapping.

 Note

User ID eld of the Employment Information (WS_3) and Person ID External of Biographical Information
(WS_2) are congurable for Business Integration Builder based SAP S∕4HANA replication from Employee
Central. This eld should not be mapped for replicating the date to Employee Central.

3. To map managers from SAP S∕4HANA to Employee Central, carry out the following steps for each
transformation template that denes a type of manager:
1. In the Infotype eld, select MNGR.
2. In the Subtype eld, select the suitable type of manager relationship that you have dened in the
V_ECPAO_MNGRTYPE Customizing view as described in section Dene Types of Manager Relationships.

3. Select one of the following elds from the Manager Assignments for Employee Replication
(ECPAO_EE_MGNR) table as the infotype eld to be mapped:
• RELATION_CODE
You can map the relation-type eld in the Job Relationships template to the RELATION_CODE eld.
You also need to dene a value mapping entity for the relation-type eld using the type of manager
relationship that you have dened in the V_ECPAO_MNGRTYPE Customizing view as the SAP S∕4HANA
key.

Implementing Data Migration and Replication to Employee Central

Data Migration and Replication to Employee Central PUBLIC 131
 • EC_MGNR_USER
If the manager's data is mastered in Employee Central, you can map the manager-id eld in the Job
Information template or the rel-user-id eld in the Job Relationships template to the EC_MNGR_USER
eld.
• MNGR_USER_ID
If the manager's data is mastered in SAP S∕4HANA, you can map the manager-id eld in the Job
Information template or the rel-user-id eld in the Job Relationships template to the MNGR_USER_ID
eld.
• ENDDA
If an employee has assignments to dierent types of managers in SAP S∕4HANA in overlapping time
slices, you need to map the end date eld of the Job Relationships template to the ENDDA eld.

 Example

You want to map the Employee Central eld Supervisor in the Job Information template with a suitable
manager from SAP S∕4HANA. Therefore, you select the MNGR infotype, the 0001 subtype (which is dened
in the V_ECPAO_MNGRTYPE Customizing view with an evaluation path that determines the supervisor of
an employee), and the MNGR_USER_ID infotype eld. The content from the MNGR_USER_ID eld is then
read from the ECPAO_EE_MGNR table during employee extraction and transferred to Job Information in
Employee Central.

4. To map additional Organizational Management elds (such as the functional area or job family) for employees
from SAP S∕4HANA to custom-string# elds in Employee Central, carry out the steps described in section Map
Organizational Management Fields from SAP ERP HCM to Employee Central.
5. Specify if the Employee Central eld is a required eld based on the Succession Data Model congured in your
Employee Central instance.

Implementing Data Migration and Replication to Employee Central

132 PUBLIC Data Migration and Replication to Employee Central
 All the required elds as per Succession Data Model of Employee Central needs to have a mapping and a
corresponding value. If no data is available for these elds the program returns error for that particular entity.

 Note

The metadata report already updates the required elds as per the input metadata le. You can see the
eld is required or not with the Required Field in EC checkbox in primary mapping overview screen.

6. If the value from the SAP S∕4HANA eld needs to be converted into an Employee Central value, enter the value
mapping entity that you have dened in the Dene Value Mapping Entities Customizing step.

 Example

You might want to map the SAP S∕4HANA address type Home Address to the Employee Central address
type Home.

 Caution

If the EC Field Has Picklist ag is set for the Employee Central eld that you have imported to SAP S∕4HANA
in the Import Metadata from Employee Central Customizing step, you need to assign a value mapping
entity. Otherwise the data extraction program might fail.

 Note

You can dene the value mappings for this entity directly from here by choosing Dene Value Mapping
Entries.

Dene Value Mapping Entries Pushbutton

Implementing Data Migration and Replication to Employee Central

Data Migration and Replication to Employee Central PUBLIC 133
Results

Primary Mapping Example: Address Type Field

2.2.2.4.9.4 If Needed, Dene a Secondary Field Mapping

If you need an additional eld mapping, for example for country/region-specic elds, dene a secondary mapping.

Context

 Caution

When a secondary mapping is dened for an SAP transformation template, you cannot clone this template.

To dene an additional eld mapping for an SAP transformation template, you go to the Secondary Mapping view
of the VC_ECPAO_MAP view cluster. An easy way to dene a custom secondary mapping is to copy the sample
secondary mappings that are provided by SAP and adapt them to your requirements. Sample secondary mappings
are available for the following country/regions:

• Argentina
• Australia
• Austria
• Brazil
• Canada

Implementing Data Migration and Replication to Employee Central

134 PUBLIC Data Migration and Replication to Employee Central
 • Chile
• China
• Colombia
• Finland
• France
• Germany
• Hong Kong
• India
• Ireland
• Italy
• Japan
• Malaysia
• Mexico
• Netherlands
• New Zealand
• Russia
• Saudi Arabia
• Singapore
• South Korea
• Spain
• Sweden
• Switzerland
• United Kingdom
• United States of America
• Venezuela

If you need to dene eld mappings for other countries, you can also copy and adapt the sample content provided
for one of these countries.

Sample Content Options in Primary Mapping View

Choose Show Sample Secondary Mapping in the Primary Mapping view to check which sample content is available.

Implementing Data Migration and Replication to Employee Central

Data Migration and Replication to Employee Central PUBLIC 135
 Sample Secondary Mapping for Address Field

Choose Copy Sample Content to copy the sample eld mappings. This includes primary mappings as well as
secondary mappings.

If you want to dene your own eld mapping, here's how to do this. You have two options:

Procedure

1. You can use a linking eld.

This is one of the elds from the infotype or subtype that you have dened in the primary mapping. You can
choose the linking eld from the value help in the Secondary Mapping view. The linking eld is dynamically
populated based on the infotype or subtype you have specied in the Primary Mapping view.

Implementing Data Migration and Replication to Employee Central

136 PUBLIC Data Migration and Replication to Employee Central
 Linking Field Country Key

Dening Secondary Mapping for Linking Field Country Key

2. You can use the Country Grouping (MOLGA) eld.

Dening Secondary Mapping for Country Grouping Field

2.2.2.4.9.5 How to Use the Sample Content for Employee Data

We provide sample content for dierent use cases in the Dene Field Mapping for Employee Data Customizing step,
which you can copy and adapt to your needs.

Use Cases

Sample content is available for all employee-related templates apart from: Job Relationships, Payment Information
Details USA, Dependent Address, Dependent National ID, and Dependent Global Information.

Implementing Data Migration and Replication to Employee Central

Data Migration and Replication to Employee Central PUBLIC 137
Sample content is available for these use cases:

Employee Data ERP to EC: Mini Master Scope (EE_WS_1)

Provides eld mappings for the employee mini master records to be replicated from the SAP S∕4HANA system to
SAP SuccessFactors. The mini master is a subset of infotypes containing data that is needed for the Employee
Prole in SAP SuccessFactors.

Use this sample content to set up a regular web service-based replication of employee mini master data for the
Employee Prole when using the side-by-side deployment option.

 Note

This sample content includes eld mappings only for the entities and elds that are needed for the Employee
Prole.

Employee Data ERP to EC: Integration or Migration (EE_WS_2)

Provides eld mappings for employee master data to be regularly replicated or to be migrated from the SAP
S∕4HANA system to Employee Central. You can use this sample content in two scenarios:

• Either to set up a regular web service-based replication of employee data from the SAP S∕4HANA system to
Employee Central when using the side-by-side deployment option.
• Or to set up a delta-enabled migration to initially move your employee data from the SAP S∕4HANA system to
Employee Central if you want to transition to the side-by-side or the core hybrid deployment option.

 Note

This sample content includes eld mappings for all entities supported by the standard delivery.

Employee Data ERP to EC: CSV File-Based Migration (EE_CSV_1)

Provides eld mappings for employee master data to be migrated from the SAP S∕4HANA system to Employee
Central. Use this sample content to set up a CSV le-based migration to initially move your employee data from the
SAP S∕4HANA system to Employee Central if you want to transition to the core hybrid deployment option.

 Note

This sample content includes eld mappings for all entities supported by the standard delivery.

 Note

The sample content for the Pay Component Recurring and Pay Component Non Recurring entities does not
contain any entries in the Subtype column since each subtype corresponds to a wage type. Wage types
are customer specic, therefore no sample mapping can be provided for them. The sample content for the
Dependent ... templates contains entries for the Family Member/Dependents (0021) infotype, but the Subtype
column is also empty here. If you want to use the sample content for these entities, copy it and ll in the
subtypes.

You can use the cloning feature to dene a eld mapping for these entities. But make sure that you don't add a
secondary mapping in this case, since templates for which a secondary mapping is dened cannot be cloned.

Implementing Data Migration and Replication to Employee Central

138 PUBLIC Data Migration and Replication to Employee Central
How to Proceed

Here is how to use the sample content provided in the Dene Field Mapping for Employee Data Customizing activity:

1. Create a transformation template group and select the sample content that you want to use for it.
2. Create transformation templates for all entities you want to use and assign the corresponding Employee
Central entities. You can create the transformation templates using two methods:
• Using the Copy Sample Content button at the transformation template group level.

You can use the Copy Sample Content button to save all the congurations like: Primary Mapping,
Secondary Mapping, Generic Value Conversion, and Country Specic Value Conversion conguration
details for the relevant EC entities based on the chosen sample content version at each transformation
template group level. You need to click on the save button after you click the Copy Sample Content button
to save all the congurations

 Note

In case when the primary mapping is not maintained in the S table (ECPAO_FLDMAP_S) for a template,
that template will not be available in the Transformation Template view of the View Cluster. You
should manually add the template in the View Cluster. For example for Employment Info and Payment
Information template, you need to manually add the template after copying the sample content.

• Using the Copy Sample Content button at the transformation template level.

 Note

Use this function only if you have not copied the sample content at the transformation template group
level.

Which eld mappings are copied depends on the sample content you have selected for the transformation
template group. After you copy the sample content for each transformation template, all the details of the
primary mapping, secondary mapping, generic value conversion, and country specic value conversion will

Implementing Data Migration and Replication to Employee Central

Data Migration and Replication to Employee Central PUBLIC 139
 get copied. You need to click on the save button after you click the Copy Sample Content button to save all
the congurations.
3. If needed, adapt the copied sample content to suit your requirements. You can, for example, delete mappings
you don't need, change the mapped eld, or add new mappings.
4. Make the following additional settings:
1. If sample value mapping entities are assigned to the sample content you use, but no value mapping details
are provided, you need to create corresponding custom value mapping entities and dene a suitable value
mapping for them.

 Example

You use the sample content provided for the Address template. The ADDRESS_TYPE_CSV value
mapping entity is assigned to the mapping of the address-type eld. A sample value mapping entity
with this name is provided. But no value mapping details are assigned to the ADDRESS_TYPE_CSV
value mapping entity. Therefore you go to the Dene Value Mapping Entities Customizing activity and
create an ADDRESS_TYPE_CSV custom value mapping entity. Then you go to the Dene Value Mapping
Details Customizing activity and dene the values to be mapped for this value mapping entity.

2. The sample content provided for the Job History template contains a mapping for the Supervisor
(manager-id) eld from Employee Central that uses the LMNG relationship type.
• If you want to use this mapping, copy the sample content for the Job History template. Then go to the
Dene Relationship Types for Managers and Employee-Related Org. Mgmt Data Customizing activity,
create the LMNG relationship type, and make the appropriate settings for it. Run the Determination
of Managers and Organizational Management Data (ECPAO_MNGR_TYPES_EXTRACTION) program
to extract the manager information. Otherwise, the NO_MANAGER entry will be replicated to the
Supervisor eld in the employee's Job History.
• If you want to use this mapping, but don't want to use the LMNG relationship type, copy the sample
content for the Job History template and change the mapping mode for the manager-id Employee
Central eld to BAdI Mapping. Then implement the Mapping of EC and ERP Data for Data Replication to
EC (EX_ECPAO_EMP_DATA_EXTRACT_OUT) Business Add-In (BAdI).
• If you don't want to use this mapping, copy the sample content for the Job History template and
remove the entry for the manager-id Employee Central eld ID.

 Note

Once you have made custom entries in the Primary Mapping view (either by copying and adapting the sample
content or by making your custom entries from scratch), you can no longer copy the sample content. If you
have dened custom mappings and decide that you want to use the mappings provided by the sample content
instead, delete the transformation template and create a new template.

If you have already dened eld mappings in the previous releases, you can continue to use them without
any changes. However, if you want to replace your custom mappings with mappings provided with the sample
content, create new transformation templates for all entities for which you want to use the sample mapping.
Then continue as described above. Remove your existing transformation templates for the same entities from
the transformation template group or clear the Is Active checkbox for them so that the new transformation
templates are used instead.

Implementing Data Migration and Replication to Employee Central

140 PUBLIC Data Migration and Replication to Employee Central
2.2.2.4.9.6 Cloning Transformation Templates

Cloning a transformation template means that you reuse the eld mapping you dene for an infotype and
subtype in the Primary Mapping view of the VC_ECPAO_MAP view cluster (Dene Field Mapping for Employee
Data customizing activity) for some or all subtypes of this infotype.

Prerequisites

Dene the eld mapping for the transformation template using VC_ECPAO_MAP view cluster.

Context

You can dene the infotypes to be cloned and their subtypes in the Clone SAP Transformation Templates
Customizing section.

 Example

This is useful for the Recurring Payments/Deductions (0014) and Additional Payments (0015) infotypes since
each wage type is itself a subtype of these infotypes. Using the cloning feature, you can use the same eld
mapping for all or some of these wage types. The cloning feature is also useful for infotypes such as Addresses
(0006), which has, for example, subtypes for the home or mailing address, or Communication (0105), which
has, for example, subtypes for the business phone number or private phone number.

Procedure

1. Dene which infotypes are relevant for cloning transformation templates and for which subtypes of these
infotypes you want to clone the corresponding templates in the Dene Infotypes and Subtypes for Cloning
Transformation Templates Customizing activity (V_ECPAO_CLN_INTY view).
a. Select the transformation template group and transformation template.
b. Enter the infotype and subtype. Repeat this for all subtypes for which you want to clone the corresponding
transformation template.
2. Dene which infotypes (primary or secondary) are relevant for cloning transformation templates and for which
country-specic subtypes of these infotypes (primary or secondary) you want to clone the corresponding
transformation templates in the Dene Country-Specic Infotypes and Subtypes for Cloning Transformation
Templates Customizing activity (V_ECPAO_CLN_CINT view).
a. Select the transformation template group and transformation template.
b. Enter the country grouping, the infotype, and the subtype. Repeat this for all subtypes for which you want
to clone the corresponding transformation template.

 Note

While performing cloning for the dependent template, make sure that the number of clone subtypes
dened for Person Relationship (WS_19) should be the same as the number of clone subtypes for

Implementing Data Migration and Replication to Employee Central

Data Migration and Replication to Employee Central PUBLIC 141
 Biographical Info for dependents (WS_2_DEP). For more information on dependent template, see How
Object Identication Mapping Works. Cloning will not be successful for all dependents if all the subtypes
of infotype 21 are not cloned for all the dependent related EC entities.

 Example

In the view cluster you can now congure a transformation template using both primary infotype and
the corresponding secondary infotype. Consider the primary infotype 0021 and secondary infotype
0106 (secondary infotype of 0021 for US). You can now clone this in the V_ECPAO_CLN_CINT view for
the required subtypes using the primary infotype 0021, which would clone the transformation template
for all the elds (elds using both 0021 and 0106 would be cloned).

Results

Once a transformation template group has been congured for a subtype cloning using the views
ECPAO_CLON_INTY and ECPAO_CLON_CINTY, then the Clone Infty and Ctry Clone Infty will be enabled at the
transformation template level. This will help you to identify which type of clone infotype was congured for that
transformation template without going into the primary mapping details screen.

Next Steps

If you want to dene a dierent eld mapping for a specic subtype of an infotype, don't enter it in the Customizing
activities listed above. Instead, dene a separate transformation template for this combination of infotype and
subtype in the VC_ECPAO_MAP view cluster.

2.2.2.4.10 Copy Conguration from one EC Instance to another

EC Instance

You can copy the congurations like transformation template group, metadata, picklists etc from one Employee
Central instance to another EC instance based on a template group.

Context

When you are setting up the basic conguration activities in your ERP system for the replication of employee
master data and organization data, you can run this report to speed-up the process. After choosing the source
EC instance and transformation template group and entering the target EC instance and transformation template
group, the target EC instance and transformation template group is rst created and then the congurations are
copied into them when you execute the report.

Implementing Data Migration and Replication to Employee Central

142 PUBLIC Data Migration and Replication to Employee Central
Procedure

1. Run the Copy conguration from one EC instance to another EC instance (ECPAO_COPY_CONFIGURATION)
program. You can also use the ECPAO_COPY_CONFIG transaction to run the program.

The program copies the conguration (Transformation Template Group, Metadata, Picklists etc) from one EC
instance to another EC instance based on your selection criteria.
2. On the selection screen, choose the source EC instance and transformation template group.
3. Choose the target EC instance and transformation template group.
4. Choose Copy Replication Direction if you want to create a copy for the same replication direction as the source
(ERP to EC or EC to ERP). If this eld is unchecked, the new copied transformation template group is created
without setting the replication direction. You could go to V_ECPAO_TTG_EE or V_ECPAO_TT_OM views to set
the required replication direction again.
5. In the action type, choose Test Run to carry out a test run of the program to check the data that will be copied.

If you run the program in a test system or client with the Test Run checkbox deselected, the program asks for a
transport request.

2.2.2.4.11 Comparison Tool to Compare Conguration Details

You can now compare the transformation template group data and check if there is any dierence between the
congurations before even you run the data extraction tool.

Context

You can run the comparison tool to check the metadata elds, settings at the instance level between two Employee
Central instances. In addition, the primary eld mapping, secondary eld mapping, and the value mappings
between two transformation template groups can be compared. The report displays the information at both the
instance level and could also be used to check if there is any dierence between the two data.

In the result screen, a hierarchical tree structure is displayed, showing the data of the source and targets in the
left and right side panes respectively. The results are shown at the entity level, showing how the congurations are
congured in both the source and target elements. You can expand each node to see the details within it. Using the
above view, you can identify the dierence between the source and target transformation templates and make the
necessary corrections if needed using the corresponding IMG activity.

Procedure

1. Go to the comparing the conguration (ECPAO_COMPARE_CONFIG) transaction to run the Report for
Comparing the conguration (ECPAO_COMPARE_CONFIGURATION) program.

The program compares the conguration (Transformation Template Group, Field Mappings, Primary and
Secondary Mappings and Conversion rules, etc.) from one Employee Central instance to another Employee
Central instance based on your selection criteria.

Implementing Data Migration and Replication to Employee Central

Data Migration and Replication to Employee Central PUBLIC 143
2. On the selection for comparison, choose the option which you want to compare.
3. Enter the details based on the selected option.

• Metadata - Choose the source Employee Central instance, target instance, and the Employee Central
entity.
• Transformation Template Group - Choose if you are going to compare the transformation template groups
of employee data or organizational data type. After you choose the relevant option (employee data or
organizational data), choose the Employee Central instance, source and target transformation template
group, and the Employee Central entity.
• Employee Central Instance/Company - Choose the source Employee Central instance and target Employee
Central instance.
4. In Other Selection Criteria, choose Show Only Differences if you want to display only the dierence in the
result.

2.2.2.4.12 Filtering of Employees During Migration based on

Employment Status

An employee can be ltered out based on the employment status and this can be done during the migration of the
employee master data.

When the ltering of the employee master data is done based on the employment status, then the complete
extraction of the data will be stopped irrespective of whether the template is eective-dated or non-eective dated
after the earliest transfer date. For more information on how the earliest transfer works in the BIB replication
mode, refer to the Replicating Employee Master Data and Organizational Assignments from Employee Central to
SAP S∕4HANA guide.

Employment Status on earliest transfer date is... (and no

change in the future until 31.12.9999) ...Is considered for integration/migration

Active Yes

Inactive No

Retired No

Withdrawn No

Employment Status on earliest transfer

date is...(and no change in the future ...Is considered for integration/migra-
until 31.12.9999) Use cases tion

Active Employee was active during initial load Yes

and is still active.

Employee was inactive during initial load Yes

and changed to active state after initial
load.

Employee was retired during initial load Yes

and changed to active state after initial
load.

Implementing Data Migration and Replication to Employee Central

144 PUBLIC Data Migration and Replication to Employee Central
 Employment Status on earliest transfer
date is...(and no change in the future ...Is considered for integration/migra-
until 31.12.9999) Use cases tion

Inactive Employee was active during initial load Yes

but was changed to inactive state after
initial load.

Employee was inactive during initial load No

and is still inactive.

Retired Employee was active during initial load Yes (Default position is not transferred,
but now changed to retired state after but the last valid position would be trans-
initial load. ferred to Employee Central.)

Employee was withdrawn during initial No

load and changed to retired state after
initial load.

Employee was inactive during initial load No

and changed to retired state after initial
load.

Withdrawn Employee was active during initial load Yes (Default position is not transferred,
and changed to withdrawn state after ini- but the last valid position would be trans-
tial load. ferred to Employee Central.)

Employee was inactive during initial load No

and changed to withdrawn state after ini-
tial load.

Employee was moved from retired to No

withdrawn state.

The above logic for ltering the PERNR's based on the employment status and the earliest transfer date is also
applicable for an employee having multiple PERNR's as part of the International Transfer, Global Assignment, and
Concurrent employment. In this case, individual PERNR's will be ltered out completely if it satises the above
ltering criteria's. For example, in international transfer if the earliest transfer date is after the termination date of
the PERNR 1, then the PERNR 1 will be completely ltered out and PERNR 2 will be migrated to Employee Central
with single employment.

2.2.2.4.13 User Status in Employee Central

The user status in employee prole can be set to Active or Inactive based on the current employment status in ERP.

For terminated employee the user status was previously set to inactive in Employee Central by the HRIS
synchronization process, which was executed after the upsert of the job info entity. Now you can directly set
the user status to Active or Inactive based on the current employment status on the current date with upsert of
user entity (WS_1) or import of basic info template (CSV_1).

2.2.2.4.14 Data Replication and Mapping Information

Implementing Data Migration and Replication to Employee Central

Data Migration and Replication to Employee Central PUBLIC 145
2.2.2.4.14.1 Non-Congurable (Standard) Employee Central
Fields

Standard elds aren't available for conguration in Customizing, independent of which communication channel you
use.

A default mapping is dened for these elds, which you can't change.

Standard Fields for CSV File-Based Entities

Entity Standard Fields

Basic Im- STATUS USERID FIRST- LAST- MI HR Onboard- USER- Assign-

ment ID
port NAME NAME ing_ID NAME
External

 No
te
Appli-
cable
only
when
the
switch
ERP to
ER/EC
to ERP
(BIB):
Activat
e
Assign
mentI
D
Extern
al in
the
view
V_EC-
PAO_C
ONST-
ANT is
ena-
bled.

Biographi- user-id person-id-

cal Infor- external
mation

Implementing Data Migration and Replication to Employee Central

146 PUBLIC Data Migration and Replication to Employee Central
 Entity Standard Fields

Personal person- start-date end-date

Informa- Info.per-
tion son-id-ex-
ternal

Employ- user-id start-date person-id- original- Assign- isRehire

ment De- external StartDate ment ID
Set to True
tails External
for the
consecu-
 No
tive em-
te
ployments
Appli- (except the
cable rst em-
only ployment)
when in an inter-
the national
switch transfer
ERP to scenario
ER/EC when the
to Centralized
ERP: Services
Activat switch is
e activated
Assign in
mentI SuccessFa
D ctors
Extern Employee
al in Central.
the
False for all
view
other
V_EC-
cases.
PAO_C
ONST-
ANT is
ena-
bled.

Implementing Data Migration and Replication to Employee Central

Data Migration and Replication to Employee Central PUBLIC 147
Entity Standard Fields

Global As- user-id person-id- start-date planned- Assign-

signment external end-date ment ID
External

 No
te
Appli-
cable
only
when
the
switch
ERP to
ER/EC
to
ERP:
Activat
e
Assign
mentI
D
Extern
al in
the
view
V_EC-
PAO_C
ONST-
ANT is
ena-
bled.

Implementing Data Migration and Replication to Employee Central

148 PUBLIC Data Migration and Replication to Employee Central
 Entity Standard Fields

Job His- user-id start-date end-date seq-num-

ber
tory

 No
te
The
stand-
ard
eld
Se-
quenc
e
num-
ber is
popu-
lated
by de-
fault. If
multi-
ple re-
cords
of job
infor-
mat-
ion en-
tity for
an
user
on a
same
day
exist
then
se-
quenc
e
num-
ber
will be
incre-
mente
d for
each
re-
cord.

Implementing Data Migration and Replication to Employee Central

Data Migration and Replication to Employee Central PUBLIC 149
Entity Standard Fields

Email Info person-

Info.per-
son-id-ex-
ternal

Phone person-
Info Info.per-
son-id-ex-
ternal

Job Rela- user-id start-date end-date

tionships

Addresses person-id- start-date end-date

external

Implementing Data Migration and Replication to Employee Central

150 PUBLIC Data Migration and Replication to Employee Central
 Entity Standard Fields

Compen- user-id start-date end-date seq-num-

ber
sation Info

 No
te
The
stand-
ard
eld
Se-
quenc
e
num-
ber is
popu-
lated
by de-
fault. If
multi-
ple re-
cords
of
com-
pensa-
tion in-
forma-
tion
entity
for an
user
on a
same
day
exist
then
se-
quenc
e
num-
ber
will be
incre-
mente
d for
each
re-
cord.

Implementing Data Migration and Replication to Employee Central

Data Migration and Replication to Employee Central PUBLIC 151
Entity Standard Fields

This
eld is
availa-
ble
only in
the
parent
entity.
This
eld is
not
sup-
ported
for the
corre-
spondi
ng
child
entites
(Pay
Com-
po-
nent
Recur-
ring).

Pay Com- user-id start-date end-date

ponent
Recurring

Pay Com- user-id

ponent
Non Re-
curring

Pay Com- user-id

ponent
Non Re-
curring
O Cycle

Payment Payment toPaymen-

Informa- Informa- tInforma-
tion De- tion.Worke tionDe-
tails r tailV3.ex-
ternalCode

Implementing Data Migration and Replication to Employee Central

152 PUBLIC Data Migration and Replication to Employee Central
 Entity Standard Fields

Payment worker Paymen-

Informa- tInforma-
tion Detail tionDe-
USA tail.exter-
nalCode

Nationa- person-id-
lIdCardIm- external
portTem-
plate

GlobalIn- person-id- Start Date End Date

foImport- external
Template

Alterna- usersSysId
tive Cost
Distribu-
tion

Alterna- usersSysId
tive Cost
Distribu-
tion Items

Termina- user-id person-id- Termina-

tion external tion Date

Depend- user-id person-id-

ent Bio- external
graphical

Depend- person-id- start-date end-date

ent Per- external
sonal

Depend- person-id- start-date end-date

ent Ad- external
dress

Depend- person-id-
ent Na- external
tional id

Depend- person-id- start-date end-date

ent Global
external
Info

Implementing Data Migration and Replication to Employee Central

Data Migration and Replication to Employee Central PUBLIC 153
Entity Standard Fields

Person Re- person- related- start-date end-date

lationship Info.per- person-id-
son-id-ex- external
ternal

Standard Fields for Web Service-Based Entities

Employee Cen-
tral Entity Standard Fields

User status userId rstName lastName username Assignment ID

External

 Note
Applicable
only when
the switch
ERP to
ER/EC to
ERP (BIB):
Activate
AssignmentI
D External in
the view
V_EC-
PAO_CON-
STANT is
enabled.

PerPerson userId personIdExter-

nal

PerPersonal startDate personIdExter- endDate

nal

Implementing Data Migration and Replication to Employee Central

154 PUBLIC Data Migration and Replication to Employee Central
 Employee Cen-
tral Entity Standard Fields

EmpEmploy- userId startDate personIdExter- originalStart- Assignment ID isRehire

ment nal Date External
Set to True for
the consecutive
 Note
employments
Applicable (except the rst
only when employment) in
the switch an international
ERP to transfer sce-
ER/EC to nario when the
ERP: Centralized
Activate Services switch
AssignmentI is activated in
D External in SuccessFactors
the view Employee
V_EC- Central.
PAO_CON-
False for all
STANT is
other cases.
enabled.

EmpGlobalAs- userId personIdExter- startDate plannedEndDate Assignment ID

signment nal External

 Note
Applicable
only when
the switch
ERP to
ER/EC to
ERP:
Activate
AssignmentI
D External in
the view
V_EC-
PAO_CON-
STANT is
enabled.

Implementing Data Migration and Replication to Employee Central

Data Migration and Replication to Employee Central PUBLIC 155
Employee Cen-
tral Entity Standard Fields

EmpJob userId startDate seq-number endDate

 Note
The stand-
ard eld Se-
quence
number is
populated
by default. If
multiple re-
cords of job
information
entity for an
user on a
same day
exist then
sequence
number will
be incre-
mented for
each record.

PerEmail personIdExter-
nal

PerPhone personIdExter-
nal

EmpJobRela- userId startDate endDate

tionships

PerAddress- personIdExter- startDate endDate

DEFLT nal

Implementing Data Migration and Replication to Employee Central

156 PUBLIC Data Migration and Replication to Employee Central
 Employee Cen-
tral Entity Standard Fields

EmpCompensa- userId startDate endDate seq-number

tion
 Note
The stand-
ard eld Se-
quence
number is
populated
by default. If
multiple re-
cords of
compensa-
tion infor-
mation en-
tity for an
user on a
same day
exist then
sequence
number will
be incre-
mented for
each record.

EmpPayCom- userId startDate endDate

pRecurring

EmpPayComp- userId
NonRecurring

PaymentInfor- PaymentInfor- externalCode

mationDetailV3 mat-
ionV3_worker

PaymentInfor- PaymentInfor- PaymentInfor-

mationDe- mationDe- mat-
tailV3USA tailV3_external- ionV3_worker
Code

PerNationalId personIdExter-
nal

EmpCostDistri- usersSysId
bution

Implementing Data Migration and Replication to Employee Central

Data Migration and Replication to Employee Central PUBLIC 157
Employee Cen-
tral Entity Standard Fields

EmpCostDistri- EmpCostDistri-
butionItem bution_usersSy-
sId

Job Relation- userId startDate endDate

ship

Non Recurring userId payDate

Ocycle

Payment Infor- worker

mation

Termination userId personIdExter- Termination

nal Date

Dependent Bio- userId personIdExter-

graphical nal

Dependent Per- personIdExter- startDate endDate

sonal nal

Dependent Ad- personIdExter- startDate endDate

dress nal

Dependent Na- personIdExter-

tional id nal

Person Rela- personIdExter- relatedPersonI- startDate endDate

tionship nal dExternal

Global Info In- personIdExter- startDate endDate

dia nal

 Note

If any new or existing elds in Employee Central are declared as standard elds in Business Integration Builder,
then you need to update the metadata by running the metadata reports.

Implementing Data Migration and Replication to Employee Central

158 PUBLIC Data Migration and Replication to Employee Central
2.2.2.4.14.2 Non-Congurable (Standard) Mapping of SAP
S∕4HANA Fields to Employee Central Fields

Standard mappings aren't available for conguration in Customizing, independent of which communication
channel you use. They are automatically added to the mappings you dene.

Mappings Dened for Employee Central Instance

Employee Central Field SAP S∕4HANA Field

user-id Personnel number (PERNR) of the employee

username Personnel number (PERNR) of the employee

person-id-external Central person (CP) of the employee

The mappings listed above are used if you select Standard Mapping in the User ID Mapping, User Name Mapping,
and Person ID Mapping columns in the Dene Employee Data Settings for Employee Central Instance Customizing
activity.

Mappings Dened for Basic Import / User Entity

Employee Central Field SAP S∕4HANA Field

status SAP S∕4HANA always sends the value as Active. Status is sent
as Active/Inactive based on the current employment status.
(Later on the HRIS synchronization process in Employee Cen-
tral sets the status from the event reason of the relevant Job
Info record.)

user-id See Mappings Dened for Employee Central Instance above

rstName First Name (VORNA) eld in the Personal Data (0002) infotype

lastName Last Name (NACHN) eld in the Personal Data (0002) infotype

middle-name Middle Name (MIDNM) eld in the Personal Data (0002) info-
type

manager-id Taken from the Supervisor eld in Job History, which is map-
ped using the Dene Relationship Types for Managers and
Employee-Related Org. Mgmt Data Customizing activity (view
V_ECPAO_MNGRTYPE)

Implementing Data Migration and Replication to Employee Central

Data Migration and Replication to Employee Central PUBLIC 159
Employee Central Field SAP S∕4HANA Field

username See Mappings Dened for Employee Central Instance above

 Note

You can't congure the Basic Import / User entity in the SAP S∕4HANA system. All elds of this entity use a
standard mapping, which you can't change.

Mappings Dened for Biographical Information Entity

Employee Central Field SAP S∕4HANA Field

user-id See Mappings Dened for Employee Central Instance above

person-id-external See Mappings Dened for Employee Central Instance above

Mappings Dened for Personal Information Entity

Employee Central Field SAP S∕4HANA Field

start-date Start Date (BEGDA) eld of the Personal Data (0002) infotype

personInfo.person-id-external See Mappings Dened for Employee Central Instance above

Mappings Dened for Employment Details Entity

Employee Central Field SAP S∕4HANA Field

user-id See Mappings Dened for Employee Central Instance above

Implementing Data Migration and Replication to Employee Central

160 PUBLIC Data Migration and Replication to Employee Central
 Employee Central Field SAP S∕4HANA Field

start-date Max (Cut-o Date, First Hire Date)

 Note
• Start date eld is a standard eld and is a congura-
ble eld for WS_3 and CSV_3 entity. But from the SAP
S∕4HANA to Employee Central direction, start date
eld does not consider eld mapping. By default, data
extraction process logic is triggered.
• The start date eld is automatically derived from the
rst record of the job information entity and the eld
does not carry the value sent from ERP. Therefore,
whatever value the Infoporter tool sends will be over-
written in Employee Central.

person-id-external See Mappings Dened for Employee Central Instance above

originalStartDate First hire date of the employee

 Note
In SAP S∕4HANA, you can dene how the hire date is
determined using the Rule for Determining Entry Date (EN-
TRY) feature. The employee's hire date provided by this
feature is replicated to Employee Central.

assignmentExternalId Personnel number (PERNR) of the employee

 Note
Assignment ID external eld will be extracted based on
the constant ERP to EC/EC to ERP: Activate AssigmentID
External. You can enable or disable the switch using
the Maintain Constant Values for Data Migration and
Replication to EC customizing activity. If the switch is ac-
tivated then the assignment ID external eld will be ex-
tracted as PERNR.

isRehire Set to True for the consecutive employments (except the rst
employment) in an international transfer scenario when the
Centralized Services switch is activated in SAP SuccessFactors
Employee Central.

False for all other cases.

 Note

Original start date is now available for mapping in the view cluster (VC_ECPAO_MAP). If these elds are
mapped at the view cluster level, then the mapping would be considered from the view cluster level. If you

Implementing Data Migration and Replication to Employee Central

Data Migration and Replication to Employee Central PUBLIC 161
 have not dened at the view cluster level then the standard mapping would be considered. Derived Dates in
Employee Central, even if it is mapped and extracted through BIB mapping, would be overwritten in Employee
Central when the Centralized Service Layer switch in enabled. For more information refer to Job Information
topic from the Data Object Tables in Employee Central guide.

Mappings Dened for Global Assignment Entity

Employee Central Field SAP S∕4HANA Field

user-id See Mappings Dened for Employee Central Instance above

person-id-external See Mappings Dened for Employee Central Instance above

start-date Hire date of the employee

planned-end-date End Date of Assignment (TERMINATION_DATE) eld of the

Details on Global Assignment (0710) infotype

Mappings Dened for Job History Entity

Employee Central Field SAP S∕4HANA Field

start-date Start Date (BEGDA) eld of the Actions (0000) infotype

user-id See Mappings Dened for Employee Central Instance above

seq-number Filled with numbers 1..n for subsequent records with same
start date (multiple changes per day). For single records on
a day the sequence number remains as 1.

Mappings Dened for Email Information and Phone Information Entities

Employee Central Field SAP S∕4HANA Field

personInfo.person-id-external See Mappings Dened for Employee Central Instance above

Implementing Data Migration and Replication to Employee Central

162 PUBLIC Data Migration and Replication to Employee Central
Mappings Dened for Job Relationships Entity

Employee Central Field SAP S∕4HANA Field

user-id See Mappings Dened for Employee Central Instance above

start-date Start Date (BEGDA) eld of the Actions (0000) infotype

Mappings Dened for Addresses Entity

Employee Central Field SAP S∕4HANA Field

person-id-external See Mappings Dened for Employee Central Instance above

Mappings Dened for Compensation Entity

Employee Central Field SAP S∕4HANA Field

user-id See Mappings Dened for Employee Central Instance above

seq-number Filled with numbers 1..n for subsequent records with same
start date (multiple changes per day). For single records on
a day the sequence number remains as 1.

 Note
This eld is available only in the parent entity. This eld
is not supported for the corresponding child entities (Pay
Component Recurring, Pay Component Non Recurring,
Pay Component Non Recurring O Cycle).

Mappings Dened for Pay Component Recurring and Pay Component Non
Recurring Entities

Employee Central Field SAP S∕4HANA Field

user-id See Mappings Dened for Employee Central Instance above.

Implementing Data Migration and Replication to Employee Central

Data Migration and Replication to Employee Central PUBLIC 163
Mappings dened for Payment Information-Details entity

Employee Central Field SAP S∕4HANA Field

Payment Information.worker See Mappings Dened for Employee Central Instance above
(Payment Information.worker corresponds to user-id)

If the payment currency and standard currency are dierent in terms of decimal values, then the amount is
converted as per the decimal places of the payment currency. If the payment currency is not maintained, then
the amount is converted as per the decimal place value of the standard currency. For example: When EUR4 is
the payment currency having 4 decimals and EUR is the standard currency having 2 decimals, then during the
migration the amount value is converted to have 4 decimals and transferred to Employee Central.

Mappings Dened for National ID Card Entity

Employee Central Field CM Field

person-id-external See Mappings Dened for Employee Central Instance above

You can now replicate the temporary national ID via value mapping entities. You can create new country specic
value mapping entities for the temporary national ID with value mapping type as Standard Mapping.

Mappings Dened for Global Information Entity

Employee Central Field SAP S∕4HANA Field

person-id-external See Mappings Dened for Employee Central Instance above

Event Date Start Date (BEGDA) eld of the Personal Data (0002) infotype

End Date End Date (ENDDA) eld of the Personal Data (0002) infotype

Mappings Dened for Termination Entity

Employee Central Field SAP S∕4HANA Field

user-id See Mappings Dened for Employee Central Instance above

person-id-external See Mappings Dened for Employee Central Instance above

Implementing Data Migration and Replication to Employee Central

164 PUBLIC Data Migration and Replication to Employee Central
 Employee Central Field SAP S∕4HANA Field

Termination Date Termination date of the employee

Mappings Dened for Dependent Biographical, Dependent Personal, Dependent

Address, Dependent National ID, and Dependent Global Info

Employee Central Field SAP S∕4HANA Field

user-id See Mappings Dened for Employee Central Instance above

person-id-external See Mappings Dened for Employee Central Instance above

start date Start Date (BEGDA) eld of the Personal Data (0002) infotype

end date End Date (ENDDA) eld of the Personal Data (0002) infotype

2.2.2.4.14.3 Precongured Mapping of SAP S∕4HANA Fields to

Employee Central Fields

The following mappings of SAP S∕4HANA entities and Employee Central entities are precongured. This
means that the mapping is dened by SAP in the Precongured Mapping tables (ECPAO_PREMAPPING,
ECPAO_PREMAP_TT).

Precongured Mapping

Employee Central Entity SAP S∕4HANA Entity

Cost Center in Job Information Concatenation of Controlling Area (KOKRS) and Cost Center
(KOSTL) elds from Organizational Assignment (0001) infotype

Source of Record* in Employment Information Logical System (LOGSYS) eld in Clients (T000) table

Country Code**, for example, in National ID entity Country codes from Countries (T005) table

* You use the Source of Record eld to dene which is the leading system for the employee's data. If an employee's
data is mastered in SAP S∕4HANA, the Source of Record eld should indicate the corresponding SAP S∕4HANA
system. Also make sure that you have created the picklist for the Source of Record eld in the Employee Central
system.

Source of Record eld is now used for license auditing. For more information see User Types in Employee Central/
Classifying Users in Employee Central for License Compliance topics in the Related Information section. With this
eld, you will be able to classify your users which are still mastered in an ERP HCM system, as functional vs. full
user.

Implementing Data Migration and Replication to Employee Central

Data Migration and Replication to Employee Central PUBLIC 165
If a country that used to be mastered in SAP S∕4HANA is now mastered in Employee Central, you need to change
the Source of Record eld for all employments assigned to this country.

 Example

Let's say, the data of all your employees in France is mastered in SAP S∕4HANA and replicated to Employee
Central. So the Source of Record eld of all employments assigned to France contains the logical system
ID of the corresponding SAP S∕4HANA system, indicating that this data is mastered in SAP S∕4HANA. Now
you switch the system of record for employees in France so that their data is mastered in Employee Central.
Therefore, the entry in the Source of Record eld of all employments assigned to France needs to be changed so
that it now indicates Employee Central as the master system. For employees who have employments in several
countries, only the employment assigned to France needs to be changed. The other employments should stay
as they are. After having changed the Source of Record eld, you stop replicating the data of your employees in
France from SAP S∕4HANA to Employee Central.

To do so, download the Employment Information data for all aected employments from SAP S∕4HANA as a CSV
le and upload it to Employee Central. Make sure that you have lled the Source of Record eld with the entry EC
from the external code of the SourceOfRecord picklist and the user_id eld with the correct user IDs of the aected
employees. If you want to leave the other elds empty, use the NO_OVERWRITE notation. For more information, see
the FAQs: Importing Data section in the Implementing Employee Central Core implementation guide. Find the most
current version of this guide in SAP Help Portal at http://help.sap.com/hr_ec.

** This is used, for example, for mapping the mandatory Card Type eld from the National ID entity in Employee
Central to the Personnel ID Number (PERID) eld from the Personal Data (0002) infotype in SAP S∕4HANA. Since
there is no card type information provided by the SAP S∕4HANA system, the TM_USMIGRATION value mapping
entity is used for the PERID eld, which maps the country-specic Employee Central card types to country codes
from the Countries (T005) table in the SAP S∕4HANA system.

Implementing Data Migration and Replication to Employee Central

166 PUBLIC Data Migration and Replication to Employee Central
 TM_USMIGRATION Value Mapping Entity

You can also use this precongured mapping for other entities where it suits your requirements.

2.2.2.4.15 Repetitive Structure Mapping of Cost Distribution

Data

Repetitive structure mapping is used for the Cost Distribution (0027) infotype, which has a repetitive structure.

In principle, repetitive structure mapping for this infotype works the same way as for the Basic Pay (0008) infotype,
but it uses some other objects:

• The Employee Central template provided for cost distribution is the Alternative Cost Distribution Items
template.
• The repetitive structure ECPAO_REPETITIVE_ST_IT0027 is entered in the Repetitive Structure eld of this
template is. This structure contains the following elds:
• Company Code (KBU01)
• Business Area (KGB01)
• Cost Center (KST01)
• Cost center percentage (KPR01)

Implementing Data Migration and Replication to Employee Central

Data Migration and Replication to Employee Central PUBLIC 167
In the Dene Field Mapping for Employee Data Customizing step, in your transformation template for the mapping
of cost distribution items, you can map these elds as shown in this example:

 Example

Primary Mapping of Alternative Cost Distribution Fields

Employee Central SAP S∕4HANA Info- Repetitive Structure

Field ID Mapping Mode type Subtype Field

items.costCenter.ex- Infotype Mapping 0027 01 KST01

ternalCode

items.percentage Infotype Mapping 0027 01 KPR01

Mapping External Code Field of Cost Distribution Item

 Note

You can only transfer cost distribution to cost centers. Other cost distribution items are currently not
supported. Employee Central doesn't accept more than 12 cost distribution items per employee. If an
employee's Cost Distribution infotype contains more than 12 entries, the data extraction program shows an
error message. No data is extracted for this employee.

2.2.2.5 Particular Mapping Types

Implementing Data Migration and Replication to Employee Central

168 PUBLIC Data Migration and Replication to Employee Central
 How Repetitive Structure Mapping Works [page 169]
Repetitive structure mapping is used for infotypes such as Basic Pay (0008) or Cost Distribution (0027)
that use a repetitive structure.

How Object Identication Mapping Works [page 175]

Object identication mapping is used for infotypes such as Family Member/Dependents (0021) that use
the Object Identication (OBJPS) eld to make a distinction between data records with the same infotype,
subtype, lock indicator, start date, and end date.

How Time Constraint 3 Mapping Works [page 177]

Time constraint 3 mapping is used for the infotypes Bank Details (0009), Additional Payments (0015),
Additional O-Cycle Payments (0267), and Additional Actions (0302), which can have overlapping records.

How Date Type Mapping Works [page 181]

The Date Specications (0041) infotype can't use a straightforward eld mapping, but has special
requirements.

How to Map Event Reasons for Data Migration [page 183]

Learn how to map event reasons for data migration.

How to Map Additional Actions [page 187]

The Additional Actions (0302) infotype allows you to execute several personnel action types for an
employee on one day.

2.2.2.5.1 How Repetitive Structure Mapping Works

Repetitive structure mapping is used for infotypes such as Basic Pay (0008) or Cost Distribution (0027) that use a
repetitive structure.

In this kind of infotype, data is entered in table form. The user can enter the data such as wage types or cost
distribution items several times. The input line for the data is available several times on the input screen. The
structure of the input line is stored in the infotype structure, and the individual elds are numbered.

Without repetitive structure mapping you would have to create a separate SAP transformation template for each
repetitive eld (for example, for each wage type or cost distribution item that can be entered) to map the elds
separately to the corresponding Employee Central eld ID's.

If you use repetitive structure mapping, you only need a single SAP transformation template, which maps the
repetitive elds once. There's no need to create several SAP transformation templates. The data extraction
program extracts the wage types or cost distibution items that are stored in an employee's infotype using the
eld mapping you have dened once.

Parent topic: Particular Mapping Types [page 168]

Related Information

How Object Identication Mapping Works [page 175]

How Time Constraint 3 Mapping Works [page 177]
How Date Type Mapping Works [page 181]

Implementing Data Migration and Replication to Employee Central

Data Migration and Replication to Employee Central PUBLIC 169
How to Map Event Reasons for Data Migration [page 183]
How to Map Additional Actions [page 187]

2.2.2.5.1.1 Repetitive Structure Mapping of Basic Pay Data

Repetitive structure mapping is used for the Basic Pay (0008) infotype, which has a repetitive structure.

In this infotype, you can enter up to forty dierent wage types and their amounts. The structure of the wage type
line is stored in the infotype structure (P0008), and the individual elds are numbered from one to forty.

Without repetitive structure mapping you would have to create a transformation template for each wage type to
map the infotype elds such as LGA01 separately to the corresponding Employee Central elds.

 Example

You'd create an ERP_RECURRING_1 template to map the LGA01 and BET01 elds. You'd create an
ERP_RECURRING2 template to map the LGA02 and BET02 elds. And so on – up to forty templates.

If you use repetitive structure mapping, you only need a single transformation template, which maps the
repetitive elds once. A repetitive structure is needed for this, which comprises the infotype elds to be
mapped. This structure needs to be entered in the Repetitive Structure eld in the Dene Employee Central
Templates for Additional Employee Data Entities Customizing step. We provide the default repetitive structure
ECPAO_REPETITIVE_ST_IT0008. This structure contains the following elds:

• Wage Type (LGA01)

• Wage Type Amount for Payments (BET01)
• Number (ANZ01)
• Time/Measurement Unit (EIN01)
• Operation Indicator for Wage Types (OPK01)

Implementing Data Migration and Replication to Employee Central

170 PUBLIC Data Migration and Replication to Employee Central
 Repetitive Structure

The ECPAO_REPETITIVE_ST_IT0008 structure is assigned to the Pay Component Recurring Employee Central
entity in the Dene Additional Employee Central Entities for Employee Data Customizing step.

Implementing Data Migration and Replication to Employee Central

Data Migration and Replication to Employee Central PUBLIC 171
 Recurring Pay Components Template

In the Dene Field Mapping for Employee Data Customizing step, you can now create a transformation template for
the mapping of recurring pay components. If you assign the Pay Component Recurring Employee Central entity to

Implementing Data Migration and Replication to Employee Central

172 PUBLIC Data Migration and Replication to Employee Central
this transformation template, the Repetitive Field entry eld is added to the Primary Mapping view. Here you can
select a eld from the repetitive structure such as Wage Type (LGA01) and map it to the Employee Central eld
such as pay-component.

Primary Mapping of Recurring Pay Components Fields

There's no need to create multiple transformation templates. The data extraction program extracts all wage types
that are stored in an employee's Basic Pay infotype using the eld mapping you have dened once.

2.2.2.5.1.2 Repetitive Structure Mapping of Cost Distribution

Data

Repetitive structure mapping is used for the Cost Distribution (0027) infotype, which has a repetitive structure.

In principle, repetitive structure mapping for this infotype works the same way as for the Basic Pay (0008) infotype,
but it uses some other objects:

• The Employee Central template provided for cost distribution is the Alternative Cost Distribution Items
template.
• The repetitive structure ECPAO_REPETITIVE_ST_IT0027 is entered in the Repetitive Structure eld of this
template is. This structure contains the following elds:
• Company Code (KBU01)
• Business Area (KGB01)

Implementing Data Migration and Replication to Employee Central

Data Migration and Replication to Employee Central PUBLIC 173
 • Cost Center (KST01)
• Cost center percentage (KPR01)

In the Dene Field Mapping for Employee Data Customizing step, in your transformation template for the mapping
of cost distribution items, you can map these elds as shown in this example:

 Example

Primary Mapping of Alternative Cost Distribution Fields

Employee Central SAP S∕4HANA Info- Repetitive Structure

Field ID Mapping Mode type Subtype Field

items.costCenter.ex- Infotype Mapping 0027 01 KST01

ternalCode

items.percentage Infotype Mapping 0027 01 KPR01

Mapping External Code Field of Cost Distribution Item

 Note

You can only transfer cost distribution to cost centers. Other cost distribution items are currently not
supported. Employee Central doesn't accept more than 12 cost distribution items per employee. If an
employee's Cost Distribution infotype contains more than 12 entries, the data extraction program shows an
error message. No data is extracted for this employee.

Implementing Data Migration and Replication to Employee Central

174 PUBLIC Data Migration and Replication to Employee Central
2.2.2.5.2 How Object Identication Mapping Works

Object identication mapping is used for infotypes such as Family Member/Dependents (0021) that use the Object
Identication (OBJPS) eld to make a distinction between data records with the same infotype, subtype, lock
indicator, start date, and end date.

With object identication mapping, you have two options to dene a eld mapping for this kind of infotype:

• Option 1: You map the necessary elds once for each type of relationship. The mapping includes country-
independent as well as country-specic elds The relationships are represented by subtypes such as Spouse
(subtype 1), Child (subtype 2), or Mother (subtype 12). You can create one transformation template per type of
relationship, such as ERP_PERSONAL_SPOUSE, ERP_PERSONAL_CHILD, ERP_PERSONAL_MOTHER. You specify
the subtype in the Primary Mapping view of the Dene Field Mapping for Employee Data Customizing step.
You only need one ERP_PERSONAL_CHILD transformation template group for the Child subtype, even if an
employee has several children.
The SAP S∕4HANA system creates the additional transformation templates that are needed for the data
records that are identied by the OBJPS eld.

 Example

Let's say an employee has three children. This means that three records of the Family Member/Dependents
infotype with the Child subtype exist for this employee, each with a dierent OBJPS entry (01, 02, and 03).
You have created a transformation template to map the elds of the Child subtype. This transformation
template is used for the data record with the OBJPS entry 01. The SAP S∕4HANA system creates two
additional transformation templates for the data record with the OBJPS entries 02 and 03.

• Option 2: If no country-specic eld mapping is needed, you can also create one single transformation
template, such as ERP_PERSONAL_DEPEND, for all dependents (meaning for all subtypes). In this case you
don't enter the subtypes in the Primary Mapping view.
Instead you use the Clone Transformation Templates Customizing steps to reuse the eld mapping you dene
for the Family Member/Dependents infotype for the subtypes of this infotype. So you enter, for example, the
Family Member/Dependents infotype and the subtypes 01 and 02 in the Dene Country-Specic Infotypes and
Subtypes for Cloning Transformation Templates Customizing step.

 Note

You can't use the cloning feature for transformation templates that use the secondary eld mapping. The
Addresses, National ID, and Global Information templates for an employee's dependents, for example,
comprise country-specic elds and therefore need a secondary mapping. Use option 1 for these
templates. This means you create, for example, an ERP_ADDR_CHILD transformation template. For this
template, you can use primary as well as secondary eld mapping.

For both options an additional logic is needed to generate a unique key for the entities dened by the OBJPS entry.
This logic is applied to the Employee Central eld that is entered in the Object Identication Field eld in the Dene
Employee Central Templates for Additional Employee Data Entities Customizing step.

 Note

The number of clone subtypes dened for Person Relationship should be the same as the number of clone
subtypes for Biographical Info for dependents.

Implementing Data Migration and Replication to Employee Central

Data Migration and Replication to Employee Central PUBLIC 175
  Example

Object identication mapping is used for the Biographical Information Employee Central template. Therefore,
person-id-external is specied in the Object Identication Field for this template. This means, a unique key is
generated that can be transferred to the person-id-external eld in Employee Central to identify the employee's
dependents.

We provide a standard logic that concatenates the employee's personnel number (PERNR) with the subtype of the
Family Member/Dependents infotype, and, where applicable, with the OBJPS entry.

 Example

Let's say the employee with the personnel number 00000250 has a spouse and two children. Then the
following keys are generated for the employee's dependents: 250_1 (Spouse), 250_2_01 (Child 1), 250_2_02
(Child 2).

To store the key mapping information for OBJPS-relevant infotype replication we use the ECPAO_OBJPS_KMAP
table. This table is relevant for all templates having GENERATOR_MODE as O in the ECPAO_ECTMPL table. The
external and the internal value of the generator eld are part of the table. In case of infotype 21 replication, the
internal generator eld signies the person ID of the dependents (this is an Employee Central-internal value) and
the external generator le value will store the person ID external of the dependent. This key mapping table is
populated only for those subtypes that are OBJPS-relevant subtypes.

ECPAO_OBJPS_KMAP table

Fields Description

PERNR Personnel Number

INFTY Infotype

SUBTY Subtype

OBJPS Object Identication

EXT_GEN_FLD_VAL External value for generator eld for OBJPS replication

INT_GEN_FLD_VAL Internal value for generator eld for OBJPS replication

During replication of data to Employee Central, personnel number, infotype, subtype, and object identication
elds would be populated.

Parent topic: Particular Mapping Types [page 168]

Related Information

How Repetitive Structure Mapping Works [page 169]

How Time Constraint 3 Mapping Works [page 177]
How Date Type Mapping Works [page 181]
How to Map Event Reasons for Data Migration [page 183]

Implementing Data Migration and Replication to Employee Central

176 PUBLIC Data Migration and Replication to Employee Central
How to Map Additional Actions [page 187]

2.2.2.5.3 How Time Constraint 3 Mapping Works

Time constraint 3 mapping is used for the infotypes Bank Details (0009), Additional Payments (0015), Additional
O-Cycle Payments (0267), and Additional Actions (0302), which can have overlapping records.

Time constraint 3 means that any number of valid records of an infotype can exist at any one time. If several
infotype records with the same start date and end date exist, they are assigned dierent sequence numbers in the
Number of Infotype Record With Same Key (SEQNR) eld.

Fields from infotypes that have time constraint 3 can be mapped to elds from Employee Central entities that also
support overlapping data records. The infotypes listed above, for example, can be mapped to these entities:

Entities Supporting Time Constraint 3

SAP S∕4HANA Infotype Employee Central Entity

Bank Details (0009) Payment Information Details

Additional Payments (0015) Non-Recurring Pay Component

Additional O-Cycle Payments (0267) Non-Recurring Pay Component

Additional Actions (0302) Job History

The Time Constraint 3 Mapping processing mode and the corresponding infotype are assigned to the Employee
Central templates that can have overlapping data. This enables the employee data extraction program to extract
the overlapping data records.

 Example

Let's say, these records of the Bank Details (0009) infotype exist for an employee:

An Employee's Bank Details in SAP S∕4HANA

Type of Bank
Payment Standard Details Re-
Start Date End Date Seq.No. Method Amount Currency Percentage cord

January 1, December 31, 0 Check 0,00 USD 0,00 Main Bank

2016 9999

January 1, December 31, 0 Check 0,00 USD 0,00 Main Bank

2015 2015

January 1, December 31, 1 Check 0,00 USD 10,00 Other Bank

2016 9999

January 1, December 31, 0 Bank Transfer 1.500,00 USD 0,00 Other Bank
2016 9999

Implementing Data Migration and Replication to Employee Central

Data Migration and Replication to Employee Central PUBLIC 177
 Type of Bank
Payment Standard Details Re-
Start Date End Date Seq.No. Method Amount Currency Percentage cord

January 1, December 31, 1 Check 0,00 USD 10,00 Other Bank

2015 2015

January 1, December 31, 0 Bank Transfer 1.500,00 USD 0,00 Other Bank
2015 2015

January 1, December 31, 0 Check 0,00 USD 25,25 Other Bank

2016 9999 Details for
O-Cycle

January 1, December 31, 0 Check 0,00 USD 25,25 Other Bank

2015 2015 Details for
O-Cycle

Example: Employee's Bank Details in SAP S∕4HANA

Implementing Data Migration and Replication to Employee Central

178 PUBLIC Data Migration and Replication to Employee Central
 Using the Time Constraint 3 Mapping processing mode, this Bank Details information can be transferred to
Employee Central:

Example: Employee's Payment Information Details in Employee Central

And here's another example showing the records of the Additional Payments (0015) infotype:

Example: Employee's Additional Payments in SAP S∕4HANA

Start Date End Date Seq.No. Wage Type Amount Currency

July 31, 2015 July 31, 2015 0 M114 1.250,00 USD

July 31, 2015 July 31, 2015 0 M116 250,00 USD

January 15, 2015 January 15, 2015 0 M114 1.000,00 USD

January 15, 2015 January 15, 2015 1 M114 250,00 USD

January 15, 2015 January 15, 2015 2 M114 1.000,00 USD

Implementing Data Migration and Replication to Employee Central

Data Migration and Replication to Employee Central PUBLIC 179
 Example: Employee's Additional Payments in SAP S∕4HANA

This information is transferred to as shown here:

Employee Central

Example: Employee's Spot Bonuses in Employee Central

Parent topic: Particular Mapping Types [page 168]

Related Information

How Repetitive Structure Mapping Works [page 169]

How Object Identication Mapping Works [page 175]
How Date Type Mapping Works [page 181]
How to Map Event Reasons for Data Migration [page 183]
How to Map Additional Actions [page 187]

Implementing Data Migration and Replication to Employee Central

180 PUBLIC Data Migration and Replication to Employee Central
2.2.2.5.4 How Date Type Mapping Works

The Date Specications (0041) infotype can't use a straightforward eld mapping, but has special requirements.

This infotype allows you to enter a user-dened combination of data. It uses a combination of Date Type elds
(DAR01, DAR02, and so on) and Date for Date Type elds (DAT01, DAT02, and so on). You can select any date type,
such as First Working Day, in any DARnn eld and store the corresponding date in the corresponding DATnn eld.
For another employee, you can use the same combination of DARnn and DATnn elds to store a dierent type of
date. Or you can store the same type of date in a dierent combination of DARnn and DATnn elds.

This means that you can't map the actual Date Type infotype eld, such as DAR01, to an Employee Central eld,
such as initial-entry-date, because the infotype eld can have dierent meanings. Instead, you need to be able to
map the actual date types, such as First Working Day, to the Employee Central eld. To support this, a special
mapping makes available an additional Date Type eld in the Primary Mapping view of the Dene Field Mapping for
Employee Data Customizing step.

Primary Mapping for Employment Details Template – Overview Screen

Implementing Data Migration and Replication to Employee Central

Data Migration and Replication to Employee Central PUBLIC 181
 Primary Mapping for Employment Details Template – Details Screen

This eld provides the input help entries dened for the Date Type infotype eld so that you can use them for eld
mapping. The input help is populated from the Date Types (T548Y) table that contains standard date types as well
as date types dened in Customizing (for example, in Customizing for Personnel Management under Personnel
Administration Evaluation Basis Date Specications Dene Date Type ).

Date type mapping can also be used for country-specic elds. Meaning, for SAP S∕4HANA templates that use the
secondary eld mapping.

 Example

Let's say you want to map the professionalServiceDate eld from Employee Central to dierent country-specic
date types, such as:

• The Adjust service date (U2) date type for the US

• The Probation Expire - NZ (32) date type for New Zealand

Implementing Data Migration and Replication to Employee Central

182 PUBLIC Data Migration and Replication to Employee Central
 Secondary Mapping for Employment Details Template

The mapping of date types is currently used for the Employment Details and Job History Employee Central entities.

You can specify a mapping between the employment details date elds and Job information date elds in Employee
Central to infotype date specication (IT0041) date types. If dates are relevant for payroll, we recommend that you
use corresponding job information date elds in Employee Central. In particular, we recommend using event-based
job information date elds. For example, if event-based date job information elds are used, these are lled
automatically by the Employee Central events. In Employee Central, this also saves a history of the data and hence
ensures data consistency with historical IT0041 data in SAP S∕4HANA system.

Parent topic: Particular Mapping Types [page 168]

Related Information

How Repetitive Structure Mapping Works [page 169]

How Object Identication Mapping Works [page 175]
How Time Constraint 3 Mapping Works [page 177]
How to Map Event Reasons for Data Migration [page 183]
How to Map Additional Actions [page 187]

2.2.2.5.5 How to Map Event Reasons for Data Migration

Learn how to map event reasons for data migration.

Context

In Employee Central any change of data of an employee happens based on an event. The event can be a salary
hike, promotion or a change in the department information etc. The information about each event is stored in the
Event reason eld of Job information entity. In ERP, event reason can be mapped to either Action Type (MASSN) or
Reason of Action (MASSG) in infotype 0000.

Implementing Data Migration and Replication to Employee Central

Data Migration and Replication to Employee Central PUBLIC 183
Procedure

In the Dene Field Mapping for Employee Data Customizing step, when dening the primary mapping for the
SAP transformation template that has the Job History Employee Central entity assigned, map the eventReason
Employee Central eld to the Action Type (MASSN) eld of the Actions (0000) infotype.

Event reason data can be migrated based on the Action Type or Reason of Actions.
• Method 1: Event reason data is migrated based on the Action Type (MASSN)

 Example

IT0000 is maintained - Actions based on the Action Type (MASSN) and Reason of Action is not mandatory
(MASSG).

Field mapping for Event Reason eld: Based on the primary mapping congurations, event reason eld
extracted data with respective action type.

Implementing Data Migration and Replication to Employee Central

184 PUBLIC Data Migration and Replication to Employee Central
  Note

In this case, Value Mapping entries are updated with the respective action types MASSN (for ex: ERP
Key 01 (Hiring) – EC Key HIRENEW). If you have enabled additional actions (IT0302), then change only
the infotype eld mapping as “0302” instead of “0000”.

• Method 2: Event reason data is migrated based on the Reason of Actions (MASSG) with reference of linked eld
MASSN.

 Example

IT0000 is maintained - Actions based on the Action Type (MASSN) and Reason of Action (MASSG) as
mandatory elds.

Implementing Data Migration and Replication to Employee Central

Data Migration and Replication to Employee Central PUBLIC 185
 Field mapping for Event Reason eld:

Based on the linked eld MASSN congurations, secondary mapping eld will be dynamically listing the
values (for ex: Linked eld is used as MASSN and secondary mapping screen rst column will display the
Action type). With this system conguration, event reason eld extracts the data based on the Reason of
Action condition instead of Action Type.

Implementing Data Migration and Replication to Employee Central

186 PUBLIC Data Migration and Replication to Employee Central
 With the above system conguration, event reason eld extracted the data based on the Reason of Action
condition instead of Action type.

 Note

In this case, value mapping entries are updated with the respective reason of actions MASSG (for ex:
ERP Key 01 (Expansion) – EC Key : HIRENEW). If you have enabled additional actions (IT0302), then
change only the infotype eld mapping as “0302” instead of “0000”.

Task overview: Particular Mapping Types [page 168]

Related Information

How Repetitive Structure Mapping Works [page 169]

How Object Identication Mapping Works [page 175]
How Time Constraint 3 Mapping Works [page 177]
How Date Type Mapping Works [page 181]
How to Map Additional Actions [page 187]

2.2.2.5.6 How to Map Additional Actions

The Additional Actions (0302) infotype allows you to execute several personnel action types for an employee on
one day.

Prerequisites

To enable the use of the Additional Actions (0302) infotype, run the Activation of Additional Actions (RPUEVSUP)
program in your SAP S∕4HANA system for the required employees. This program carries out the following steps:

• It activates the Additional Actions infotype by setting the value of the ADMIN EVSUP switch in the T77S0 table
to 1.

Implementing Data Migration and Replication to Employee Central

Data Migration and Replication to Employee Central PUBLIC 187
• It sets the Update Infotype 0302 When Executing an Action (P0302) indicator for all personnel action types in
the T529A table. This means that the system logs all personnel action types that are executed for an employee
and their related reasons in the Additional Actions infotype.
• It creates an Additional Actions (0302) record for each Actions (0000) infotype record on the specied key
date.

Context

The Additional Actions (0302) infotype enables automatic logging of all personnel action types performed for an
employee for a specied key date. You can display and edit the records stored in the Additional Actions infotype
(0302) on the Actions (0000) infotype list screen.

 Note

You can't display or edit Additional Actions records directly.

Here's how you dene the mappings the mappings needed to enable replication of additional actions to Employee
Central:

Procedure

1. Since the Additional Actions (0302) infotype can have overlapping records, the Time Constraint 3 Mapping
processing mode needs to be assigned to the Employee Central template. This step was already carried out for
the Job History (Job Info) default template:

Implementing Data Migration and Replication to Employee Central

188 PUBLIC Data Migration and Replication to Employee Central
 Job History Employee Central Template Uses Time Constraint 3 Mapping
2. In the Dene Field Mapping for Employee Data Customizing step, when dening the primary mapping for the
SAP transformation template that has the Job History Employee Central entity assigned, map the eventReason
Employee Central eld to the Action Type (MASSN) eld of the Additional Actions (0302) infotype. (Previously,
the eld was mapped to the Action Type (MASSN) eld of the Actions (0000) infotype.)

Implementing Data Migration and Replication to Employee Central

Data Migration and Replication to Employee Central PUBLIC 189
 eventReason Employee Central Field Mapped to Additional Actions Infotype Field

Results

If you now run the employee data extraction program, the content of the Action Type eld from the Additional
Actions (0302) infotype is extracted for the eventReason Employee Central eld. If for an employee there is no
Additional Actions entry, the corresponding entry from the Actions (0000) infotype is extracted as a fallback.

Task overview: Particular Mapping Types [page 168]

Related Information

How Repetitive Structure Mapping Works [page 169]

How Object Identication Mapping Works [page 175]

Implementing Data Migration and Replication to Employee Central

190 PUBLIC Data Migration and Replication to Employee Central
How Time Constraint 3 Mapping Works [page 177]
How Date Type Mapping Works [page 181]
How to Map Event Reasons for Data Migration [page 183]

2.2.2.6 Handling Manager Relationships

Dene Types of Manager Relationships [page 191]

You dene dierent types of employee-manager relationships (such as a line manager or a matrix manager
relationship) and the corresponding evaluation paths in the Dene Relationship Types for Managers and
Employee-Related Org. Mgmt Data Customizing activity (view V_ECPAO_MNGRTYPE).

Determine the Employees' Managers [page 193]

How the Manager's User ID Is Updated [page 195]

The User ID eld assigned to a manager's personnel number in the Managers and Org. Mgmt Fields for
Employee Replication table is updated from the corresponding User ID eld in the employee key mapping
table. Here's how this update happens.

Manager Extraction Logic for Dierent Types of Managers [page 196]

See where SAP S∕4HANA and Employee Central dier regarding manager assignments.

Handle Managers in the SAP S∕4HANA System Whose Data Is Mastered in Employee Central [page 197]
Managers whose data is mastered in Employee Central don't have a personnel number in the SAP
S∕4HANA system, that's why they need special handling.

Use Position Relationships from SAP S∕4HANA to Create Supervisor Relationships in Employee Central [page
199]
You can create supervisor relationships for the Job History entity in Employee Central by replicating
position relationships from SAP S∕4HANA, without replicating the manager from SAP S∕4HANA explicitly to
the Supervisor eld of the employee's Job History.

2.2.2.6.1 Dene Types of Manager Relationships

You dene dierent types of employee-manager relationships (such as a line manager or a matrix manager
relationship) and the corresponding evaluation paths in the Dene Relationship Types for Managers and Employee-
Related Org. Mgmt Data Customizing activity (view V_ECPAO_MNGRTYPE).

Context

The Determination of Managers and Organizational Management Data (ECPAO_MNGR_TYPES_EXTRACTION)

program (transaction ECPAO_MNGR_EXTR) uses the types of manager relationships you dene here to determine
the dierent types of managers for a given selection of employees.

In the VC_ECPAO_MAP view cluster, you can use the types of manager relationships you dene here to map
managers from SAP S∕4HANA to Employee Central, for example, to use them in the Job Relationship template.

Implementing Data Migration and Replication to Employee Central

Data Migration and Replication to Employee Central PUBLIC 191
For each type of manager relationship you want to use, carry out the steps described below.

Procedure

1. Enter a unique ID and a description of the relationship type.

You can enter any description. The ID you enter here is used in the VC_ECPAO_MAP view cluster, in the Primary
Mapping view. In this view cluster, you enter the ID in the Subtype eld.

2. Select the evaluation path that is to be used to determine the managers for this type of relationship.
The evaluation path describes a chain of relationships between objects in a hierarchical structure, such as
organizational unit position person . The SAP S∕4HANA system evaluates the structure along this
evaluation path and takes into account the objects that it nds using this path. You can use evaluation paths
that start with the object types * (any), O (organizational unit), S (position), or P (person).
3. Enter the structure depth.
This is a number of one to six digits. The number corresponds with the dierent levels of an organizational
structure, with 1 being the highest level in a structure, and all subsequent numbers representing lower levels.
The level number determines how much of a structure is processed. For example, if the structure depth is 3,
the SAP S∕4HANA system processes down three levels of the structure, beginning from the object that you
select as the root object. If you don't want to limit processing, leave the structure depth blank.
4. To dene whether the type of manager relationship is currently active and used by the manager extraction
report or not, select or clear the Is Active checkbox.

Results

Implementing Data Migration and Replication to Employee Central

192 PUBLIC Data Migration and Replication to Employee Central
Task overview: Handling Manager Relationships [page 191]

Related Information

Determine the Employees' Managers [page 193]

How the Manager's User ID Is Updated [page 195]
Manager Extraction Logic for Dierent Types of Managers [page 196]
Handle Managers in the SAP S∕4HANA System Whose Data Is Mastered in Employee Central [page 197]
Use Position Relationships from SAP S∕4HANA to Create Supervisor Relationships in Employee Central [page 199]

2.2.2.6.2 Determine the Employees' Managers

Context

You can determine dierent types of managers for a given selection of employees, based on the types of
manager relationships you have dened in the Relationship Types for Managers and Organizational Mgmt Data
(V_ECPAO_MNGRTYPE) view (see section Dene Types of Manager Relationships [page 191]). The managers are
stored in the Managers and Org. Mgmt Fields for Employee Replication (ECPAO_EE_MGNR) table so that manager
relationships can be transferred to Employee Central. Employee Central uses the manager relationships, for
example, in the Job Relationships and the Job Information templates to identify dierent types of managers, such
as matrix managers, second managers, custom managers, or HR managers.

Procedure

1. Go to the Dene Background Job (SM36) transaction.

2. Schedule the Determination of Managers and Organizational Management Data
(ECPAO_MNGR_TYPES_EXTRACTION) program as a regular background job.

Implementing Data Migration and Replication to Employee Central

Data Migration and Replication to Employee Central PUBLIC 193
3. On the selection screen, specify the personnel numbers for which you want to determine the managers.
4. The program reads the active types of manager relationships from the V_ECPAO_MNGRTYPE view and uses the
evaluation paths stored there to determine the managers for the given selection of employees.
5. To check the messages issued by the program, go to the Analyze Application Log (SLG1) transaction.
6. Enter the ECPAO object and ECPAO_MANAGER subobject, optionally specify additional selection criteria, and
click Execute.

Next Steps

The Employee Data Extraction program reads the information about the managers from the ECPAO_EE_MGNR table.
If it nds the manager for an employee, it transfers this information to Employee Central. Otherwise, the entry
NO_MANAGER is transferred.

Task overview: Handling Manager Relationships [page 191]

Related Information

Dene Types of Manager Relationships [page 191]

How the Manager's User ID Is Updated [page 195]
Manager Extraction Logic for Dierent Types of Managers [page 196]
Handle Managers in the SAP S∕4HANA System Whose Data Is Mastered in Employee Central [page 197]
Use Position Relationships from SAP S∕4HANA to Create Supervisor Relationships in Employee Central [page 199]

Implementing Data Migration and Replication to Employee Central

194 PUBLIC Data Migration and Replication to Employee Central
2.2.2.6.3 How the Manager's User ID Is Updated

The User ID eld assigned to a manager's personnel number in the Managers and Org. Mgmt Fields for Employee
Replication table is updated from the corresponding User ID eld in the employee key mapping table. Here's how
this update happens.

Let's assume the following:

An MMNG (Matrix Manager) relationship type is dened in the Dene Relationship Types for Managers and Employee-
Related Org. Mgmt Data Customizing activity.

The following mapping is dened in primary mapping of the Dene Field Mapping for Employee Data Customizing
activity for the manager-id eld:

• Infotype: MNGR (Manager Table)

• Subtype: MMNG (Matrix Manager)
• Infotype Field: MNGR_USER_ID (from table ECPAO_EE_MGNR)

And this mapping is dened in primary mapping for the user-id eld:

• Infotype: 0105 (Communication)

• Subtype: SY-UNAME (0001)
• Infotype Field: USRID (Communication ID/Number)

Then this is how the manager's user ID is updated:

1. The Determination of Managers and Organizational Management Data (ECPAO_MNGR_TYPES_EXTRACTION)

program determines an employee's manager from the organizational structure in SAP S∕4HANA and stores his
or her personnel number in the Personnel Number of Related Manager (RELATED_PERNR) eld of the Managers
and Org. Mgmt Fields for Employee Replication (ECPAO_EE_MGNR) table.
2. Based on the mapping dened for the manager-id eld, the Employee Data Extraction
(ECPAO_EMPL_EXTRACTION) program reads the content from the MNGR_USER_ID eld in the ECPAO_EE_MGNR
table during employee extraction and transfers it to Job Information in Employee Central. Based on the
mapping dened for the user-id eld, it also determines the manager's user ID and transfers this to Employee
Central.
3. The Employee Key Mapping (PAOCFEC_EEKEYMAP) table is updated. The User ID (USER_ID) eld of this table is
lled with the ID that was determined from the Communication (0105) infotype and transferred to the user-id
eld Employee Central.
4. The user ID stored for a personnel number in the USER_ID eld of the employee key mapping table is written to
the MNGR_USER_ID eld assigned to this same personnel number in the ECPAO_EE_MGNR table.

Parent topic: Handling Manager Relationships [page 191]

Related Information

Dene Types of Manager Relationships [page 191]

Determine the Employees' Managers [page 193]
Manager Extraction Logic for Dierent Types of Managers [page 196]
Handle Managers in the SAP S∕4HANA System Whose Data Is Mastered in Employee Central [page 197]

Implementing Data Migration and Replication to Employee Central

Data Migration and Replication to Employee Central PUBLIC 195
Use Position Relationships from SAP S∕4HANA to Create Supervisor Relationships in Employee Central [page 199]

2.2.2.6.4 Manager Extraction Logic for Dierent Types of

Managers

See where SAP S∕4HANA and Employee Central dier regarding manager assignments.

In the SAP S∕4HANA system, an employee can be assigned to dierent types of managers as well as to multiple
managers of the same type in overlapping periods. In Employee Central, an employee can only be assigned to
one manager of the same type (for example, to one matrix manager) at a specic point in time. If the employee
is assigned to multiple types of managers, the assignment periods must match. The extraction logic adapts the
manager assignments in the two cases described below.

Employee is assigned to multiple types of managers in overlapping periods in

SAP S∕4HANA

In this case, the extraction logic modies the time slices so that the assignment periods of the same employee to
dierent types of managers match.

 Note

To make this work, you need to map the end date eld of the Job Relationships Employee Central entity to the
SAP S∕4HANA eld ENDDA.

 Example

An employee has the following manager assignments in SAP S∕4HANA:

• 01/01/2010 to 12/31/2014: Custom manager C

• 01/01/2013 to 12/31/2015: Matrix manager M

The manager assignments are replicated to Employee Central as follows:

• 01/01/2010 to 12/31/2012: Custom manager C

• 01/01/2013 to 12/31/2014: Custom manager C and matrix manager M
• 01/01/2015 to 12/31/2015: Matrix manager M

Employee is assigned to multiple managers of the same type in overlapping

periods in SAP S∕4HANA

In this case, the extraction logic delimits the records accordingly.

Implementing Data Migration and Replication to Employee Central

196 PUBLIC Data Migration and Replication to Employee Central
  Example

An employee has the following manager assignments in SAP S∕4HANA:

• 01/01/2010 to 12/31/2014: Supervisor M1

• 01/01/2012 to 12/31/9999: Supervisor M2

The manager assignments are replicated to Employee Central as follows:

• 01/01/2010 to 12/31/2014: Supervisor M1

• 01/01/2015 to 12/31/9999: Supervisor M2

The second manager assignment starts after the rst assignment has ended.

Parent topic: Handling Manager Relationships [page 191]

Related Information

Dene Types of Manager Relationships [page 191]

Determine the Employees' Managers [page 193]
How the Manager's User ID Is Updated [page 195]
Handle Managers in the SAP S∕4HANA System Whose Data Is Mastered in Employee Central [page 197]
Use Position Relationships from SAP S∕4HANA to Create Supervisor Relationships in Employee Central [page 199]

2.2.2.6.5 Handle Managers in the SAP S∕4HANA System

Whose Data Is Mastered in Employee Central

Managers whose data is mastered in Employee Central don't have a personnel number in the SAP S∕4HANA
system, that's why they need special handling.

Context

To be able to transfer the manager relationships of employees who are assigned to these managers from SAP
S∕4HANA to Employee Central, you must create users for these managers in SAP S∕4HANA. The Determination of
Managers and Organizational Management Data (ECPAO_MNGR_TYPES_EXTRACTION) program then stores these
managers' users instead of the personnel numbers in the Managers and Org. Mgmt Fields for Employee Replication
(ECPAO_EE_MGNR) table.

Implementing Data Migration and Replication to Employee Central

Data Migration and Replication to Employee Central PUBLIC 197
Procedure

1. Go to the User Maintenance (SU01) transaction.

2. Create a user for each manager whose data is mastered in Employee Central and who has employees assigned
whose data is mastered in SAP S∕4HANA.
3. Maintain an alias for each user that corresponds to the unique identier of this employee in Employee Central.

 Restriction

The managers' users have to be absolutely identical in SAP S∕4HANA and in Employee Central. In the
SAP S∕4HANA system, user names can only have 40 characters and have to be in uppercase. Therefore,
this approach only works for new Employee Central customers who make sure that their user names in
Employee Central comply with the SAP S∕4HANA user denition.

4. Go to the Organization and Stafng (PPOME) transaction and assign the user to the corresponding
organizational structure.
5. Go to the Dene Relationship Types for Managers and Employee-Related Org. Mgmt Data Customizing activity
and select an appropriate evaluation path for the User (US) object type.

Task overview: Handling Manager Relationships [page 191]

Related Information

Dene Types of Manager Relationships [page 191]

Determine the Employees' Managers [page 193]
How the Manager's User ID Is Updated [page 195]
Manager Extraction Logic for Dierent Types of Managers [page 196]
Use Position Relationships from SAP S∕4HANA to Create Supervisor Relationships in Employee Central [page 199]

Implementing Data Migration and Replication to Employee Central

198 PUBLIC Data Migration and Replication to Employee Central
2.2.2.6.6 Use Position Relationships from SAP S∕4HANA
to Create Supervisor Relationships in Employee
Central

You can create supervisor relationships for the Job History entity in Employee Central by replicating position
relationships from SAP S∕4HANA, without replicating the manager from SAP S∕4HANA explicitly to the Supervisor
eld of the employee's Job History.

Prerequisites

Position Management must be enabled for your account using the Manage Employee Central Settings admin tool in
Employee Central.

The Parent Position eld must not be a required eld in the Employee Central data model during data replication.

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 multiple transformation templates.

Within the transformation template group that you use for organizational data extraction, create two
transformation templates for positions, one that maps the Parent eld and one that doesn't. Assign the same
Employee Central template to both transformation templates.

 Example

Let's say, you create the transformation templates POSITION_WO_PARENT and POSITION_W_PARENT for
mapping SAP S∕4HANA elds to Employee Central elds. You assign the Employee Central entity Position
to both of the transformation templates and map the elds as shown below.

POSITION_WO_PARENT

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

defaultValue Infotype Mapping 1000 STEXT

Position Title Infotype Mapping 1000 STEXT

POSITION_W_PARENT

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

defaultValue Infotype Mapping 1000 STEXT

Implementing Data Migration and Replication to Employee Central

Data Migration and Replication to Employee Central PUBLIC 199
 Employee Central
Field Mapping Mode Infotype Subtype SAP S∕4HANA Field

Position Title Infotype Mapping 1000 STEXT

Position.Higher-Level Infotype Mapping 1001 A002 SOBID

Posit

Procedure

1. Replicate the child position P1 and its parent position P2 - but without the relationships between them - from
SAP S∕4HANA to Employee Central. 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 position elds and that does not map
the Parent eld. Deselect this checkbox for the other transformation template that you use for mapping
positions (the one that contains the Parent eld).

 Example

In the example above, the POSITION_WO_PARENT template would be active, the POSITION_W_PARENT
template would be inactive.

b. Replicate the positions 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 eld since you've set the Is Active checkbox for this transformation
template. The other transformation template, which maps the Parent eld, isn't used since this is not
active.
2. Replicate the employee-position assignments from SAP S∕4HANA to Employee Central. To do so:
a. Create the employees E1 and E2 in the SAP S∕4HANA system. Assign employee E1 to position P1 and
employee E2 to position P2.
b. Don't extract the employee's managers - make sure that you don't run the Determination of Managers and
Organizational Management Data (ECPAO_MNGR_TYPES_EXTRACTION) program for these employees.
c. Replicate the employees' data using the Employee Data Extraction (ECPAO_EMPL_EXTRACTION) program.
d. In Employee Central, the Supervisor eld of employee E2 remains empty since no supervisor information
was replicated from SAP S∕4HANA.
3. Replicate the position relationships from SAP S∕4HANA to Employee Central. 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 position elds and that maps the
Parent eld. Deselect this checkbox for the other transformation template that you use for mapping
positions (the one that doesn't contain the Parent eld).

 Example

In the example above, the POSITION_W_PARENT template would be active, the POSITION_WO_PARENT
template would be inactive.

Implementing Data Migration and Replication to Employee Central

200 PUBLIC Data Migration and Replication to Employee Central
 b. Replicate the positions 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 eld since you've set the Is Active checkbox for this transformation
template. The other transformation template, which doesn't map the Parent eld, isn't used since this
is not active. For more information position replication, see Replicating Organizational Data from SAP
S∕4HANA to Employee Central integration guide.
c. The parent-child associations are created for the positions in Employee Central.
4. Check employee E2's Job History in Employee Central. The Supervisor eld should now show an entry for
employee E1.

Task overview: Handling Manager Relationships [page 191]

Related Information

Dene Types of Manager Relationships [page 191]

Determine the Employees' Managers [page 193]
How the Manager's User ID Is Updated [page 195]
Manager Extraction Logic for Dierent Types of Managers [page 196]
Handle Managers in the SAP S∕4HANA System Whose Data Is Mastered in Employee Central [page 197]

2.2.2.7 Data Extraction and Transfer

Extracting Employee Data [page 202]

Here is how to extract employee data from the SAP S∕4HANA system to transfer it to Employee Central.

Extracting Employee Data in Multiple Steps [page 210]

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

Extracting Employees Manager Information [page 212]

Learn how to migrate the Manager ID eld value in the employee job information entity.

Downloading CSV Files from the Application Server [page 217]

If you've stored the data extracted to CSV les on the application server, here's how to transfer the data
from the application server location to a local drive.

Extracting Changed Employee Data Using Delta Replication [page 219]

After the initial run of the employee data extraction program, changed data is replicated using delta
replication. Here's how you need to set this up.

Replicating Employee Data to Custom Entities in Employee Central [page 221]

Here's an overview of the steps involved when you want to transfer data from SAP S∕4HANA to a custom
entity in Employee Central.

Transferring Data Deletion to Employee Central [page 222]

Implementing Data Migration and Replication to Employee Central

Data Migration and Replication to Employee Central PUBLIC 201
 For some Employee Central templates, a deletion of data can be transferred from SAP S∕4HANA to
Employee Central.

Extracting Employee Data with Additional Events Before Earliest Transfer Date [page 224]
Learn how to extract the employee data with additional events before the earliest transfer date.

How the Extraction Report behave for dierent Employment Statuses [page 236]
When the additional events are not congured, the employments that are inactive as of earliest transfer
date and changes beyond the earliest transfer date is ignored from transferring to Employee Central.

Parallelization of Employee Data Extraction with the Job Scheduler Report [page 238]
For migrating a large number of employee data to Employee Central you can use the Job Scheduler report.
This report will automatically divide the load into smaller batches and schedule multiple background jobs,
which can be executed in parallel.

2.2.2.7.1 Extracting Employee Data

Here is how to extract employee data from the SAP S∕4HANA system to transfer it to Employee Central.

Procedure

1. Go to the Employee Data Extraction (ECPAO_EE_EXTR) transaction to run the Employee Data Extraction
(ECPAO_EMPL_EXTRACTION) program (Infoporter tool).

The program extracts employee data from the SAP S∕4HANA system based on your selection criteria.

Implementing Data Migration and Replication to Employee Central

202 PUBLIC Data Migration and Replication to Employee Central
 Selection Screen of the ECPAO_EMPL_EXTRACTION Program
2. Select the transformation template group to be used for the data extraction.

If the constant ERP to EC/EC to ERP: Connect Multiple EC Instances is enabled, the SAP S∕4HANA system
checks whether the specied transformation template group is correct. For more information, refer to Setting
Up the Connection of Multiple Employee Central Instances to the Same SAP S∕4HANA System Client [page
244].
3. Select the variant ID that you have created before in the Dene the Variant IDs for Data Migration customizing
activity (view V_ECPAO_VARIANT).

Once you have created the variant ID, you should have also assigned the required transformation templates
to the variant ID using the Dene the Transformation Templates for a Variant ID customizing activity (view
V_ECPAO_TEMP_VAR).

 Note

This is not a mandatory eld. You can choose the Variant ID if you want to perform the extraction in multiple
steps. For more information, see: Extracting Employees in Multiple Steps .

Implementing Data Migration and Replication to Employee Central

Data Migration and Replication to Employee Central PUBLIC 203
 For example, a transformation template group consists of the 5 transformation templates (ERP1, ERP2, ERP3,
ERP4, and ERP5). In these templates if you want to choose only ERP1, ERP3, and ERP5, you can create a
variant ID for these transformation templates. And when you choose this variant ID for migration process, only
these transformation templates (ERP1, ERP3, and ERP5) would be considered.

 Note

You can congure the Employee Central templates that should be ltered out for a given country using
the customizing activity Filter EC Entities for Migrating Employee Data to EC based on Country (view
V_ECPAO_ECTM_FIL).

4. Specify how you would like to transfer the data.

• By Web services, using the middleware that is available for the data replication from SAP S∕4HANA to
Employee Central. You can only use this option if the transformation template group you specify uses the
Web Service Transfer communication channel. On selecting the test run option in the web service mode,
you can download a le with all the employee data information and mapping details. Thus before the actual
upload of the data, you can see the data mappings and congurations done in SAP S∕4HANA and make the
necessary data corrections in the system if required.
• You can download the payload le in the CSV format to see all the data based on the congurations and
mapping details before you actually run the report. By this you can verify if the employee data information
and mapping details are correct and avoid any errors while executing the extraction report.
The download log le shows all the success, error, and warning messages. It will also include the number of
les that were downloaded and from where the le is downloaded from. In addition it will also show which
EC Instance has been used for the migration, and if any employments are ltered out while sending data to
certain EC Instance.
Please note that the les might contain personal and sensitive data. Additional authorization is performed
to check if the user has the right to download the CSV le. Only specic authorized users should be allowed
for this operation. The downloads that are triggered by a user to the application server or local server in
Production mode and in Test Run (Download Payload) are logged via table ECPAO_OBJ_DWNLD along with
the timestamp and transformation template details.
The below authorizations are required to be able to download the CSV les:

Authorizations
Authorization Object Authorization Field Authorization Value

S_DATASET(for application server) ACTVT 34

S_DATASET(for application server) FILENAME /usr/*

S_DATASET(for application server) PROGRAM CL_ECPAO_FILE_ON_SERVER*

ECPAO_EMPL_EXTRACTION

S_TABU_NAM ACTVT 02

S_TABU_NAM TABLE ECPAO_OBJ_DWNLD

Further, it is your responsibility for the retention and deletion of these les from the application server or
local machine.

• Using comma-separated values (CSV) les.

If you select the File Transfer and Use Server Path options, you can later transfer the data from the
application server location to a local drive.

Implementing Data Migration and Replication to Employee Central

204 PUBLIC Data Migration and Replication to Employee Central
  Note

Default option for the le transfer is server path.

If you select the File Transfer and Use Local Drive Path options, you must specify where the CSV le is to be
stored.

 Note

When you schedule the program as a background job to carry out a mass data extraction, always
choose the File Transfer Use Server Path option.

For both options you can specify an addition to the le name to prevent existing les from being
overwritten by new les. If you don't enter a le identier, the same le name is used for each download so
that existing les are overwritten.
If you want to combine several CSV les into a .zip le, select the Combine into ZIP le checkbox. Please
note that CSV les that you create for generic objects can't be zipped. They are stored separately, even if
you select the Combine into ZIP le option.

 Caution

While using local drive to save the CSV le, make sure that you are storing the les in a secure folder,
which will have access only the users having HR administrator role.

5. Select the Detailed Message Log checkbox if you want to get a detailed log containing all warning and error
messages for each employee.
6. Select the Failed Employee Replication checkbox if you want to re-run the replication for only those employees
for which the replication status is failed.

 Note

File transfer mode is not supported for this selection.

7. You can carry out a test run of the program rst to check if the data can be extracted from SAP S∕4HANA
without errors.
8. If you carry out a productive run, the program extracts the data.
9. The program updates the following tables:
• Inventory of Data Replicated for Employees and Org. Objects (ECPAO_EE_INVT)

Implementing Data Migration and Replication to Employee Central

Data Migration and Replication to Employee Central PUBLIC 205
 This table holds information about when the data of which employee was replicated to Employee Central,
such as:

Sample Entry in the ECPAO_EE_INVT Table

Employee's Person- Data Successfully Time Stamp (Uni-

Employee Central In- SAP S∕4HANA Ob- nel Number in SAP Replicated to Em- versal Coordinated
stance ject Type S∕4HANA ployee Central Time)

SBS_MODEL P (= Person) 00000561 X 20.150.325.063.810,4

298650 = 2015 March
25, 6:38 (plus sec-
onds, milliseconds,
microseconds, and
the rst decimal of
the nanoseconds)

• Inventory of Data Replicated for Employee Central Templates (ECPAO_INVT)

This table holds information about when the data of which Employee Central template was replicated to
Employee Central, such as:

Sample Entry in the ECPAO_INVT Table

Employee's Data Suc-

Personnel cessfully Re- Data Repli- Time Stamp
Employee SAP Number in Employee plicated to cated in Data Dele- (Universal
Central In- S∕4HANA SAP Central Employee Last Repli- tion Repli- Coordinated
stance Object Type S∕4HANA Template Central cation Run cated Time)

SBS_MODEL P (= Person) 55261454 WS_6 X X 20.160.704.0

82.354,7129
620 = 2016
July 04, 8:23
(plus sec-
onds, milli-
seconds, mi-
croseconds,
and the rst
decimal of
the nanosec-
onds)

Implementing Data Migration and Replication to Employee Central

206 PUBLIC Data Migration and Replication to Employee Central
 Employee's Data Suc-
Personnel cessfully Re- Data Repli- Time Stamp
Employee SAP Number in Employee plicated to cated in Data Dele- (Universal
Central In- S∕4HANA SAP Central Employee Last Repli- tion Repli- Coordinated
stance Object Type S∕4HANA Template Central cation Run cated Time)

SBS_MODEL P (= Person) 55261454 WS_7 X X 20.160.704.0

82.354,7129
620 = 2016
July 04, 8:23
(plus sec-
onds, milli-
seconds, mi-
croseconds,
and the rst
decimal of
the nanosec-
onds)

• Inventory of Replicated Data: Error Messages (ECPAO_INVT_MSG)

This table holds the error messages issued for the replication by Employee Central or by SAP S∕4HANA,
per Employee Central template, such as:

Sample Entry in the ECPAO_INVT_MSG Table

Employee's Per-
Employee Cen- SAP S∕4HANA sonnel Number Employee Cen- Sequence Num-
tral Instance Object Type in SAP S∕4HANA tral Template ber Message Text

SBS_MODEL P (= Person) 55261454 WS_6 1 02157601 is an

invalid Person Id
External [...]

SBS_MODEL P (= Person) 55261454 WS_6 2 user-id is

invalid.,#Employe
e 55261454 does
not have valid Job
Information data
[...]

 Tip

Use the Analyze Inventory of Replicated Employee Data (ECPAO_EMPL_INVENTORY_ALV) program to check
these tables.

10. When delta enabled transformation template group is selected in the selection screen, for the successfully
migrated personnel numbers, the extraction process updates the corresponding ECPAO message type change
pointers (if available), and marks them as processed.

Implementing Data Migration and Replication to Employee Central

Data Migration and Replication to Employee Central PUBLIC 207
  Note

This applies when you do not choose any variant selection on the selection screen.

11. The program writes messages to the application log.

The application log would contain the warning, error, or success messages. Here you can see for how many
employees the data has been successfully extracted or replicated and for how many employees the extraction
or the replication process has failed. In addition it will also show which EC Instance has been used for the
migration, and if any employments are ltered out while sending data to certain EC Instance. Even when the
Employee Central entity is successfully replicated from ERP, there could be some warning messages from
Employee Central. You can see these messages here. If you have chosen to get a detailed log, the personnel
numbers and transformation templates in question are listed with the relevant error or warning messages from
Employee Central. All messages are also stored in the application log.
12. To check the messages, go to the Analyze Application Log (SLG1) transaction.

 Tip

You can also run SLGD transaction to display data in text format and export the data into an excel le or
in other formats. After executing the transaction go to List Save/Send Local File... and choose the
required format in which you want to export the log le.

13. Enter the ECPAO object and subobject. To check for a specic employee, enter the employee's personnel
number in the External ID eld. Optionally specify additional selection criteria, then choose Execute.

Implementing Data Migration and Replication to Employee Central

208 PUBLIC Data Migration and Replication to Employee Central
 Selection Screen of the SLG1 Transaction

 Note

You can use the V_ECPAO_PACKSIZE view to set the packet size for an Employee Central instance
template. This view can be maintained directly in the production system and thus a transport is not
required for this conguration in the production system. Packet size denes the maximum number of
records for an Employee Central entity that gets replicated in a single session. The congured data is
stored in the table ECPAO_PACKSIZE. The Employee Extraction Report (ECPAO_EMPL_EXTRACTION) use
this table data while creating the packets on the extracted data from the SAP S∕4HANA system. By
setting the packet size, you can now avoid the time out errors while using complex APIs such as payment
information, Position, EmpCostDistribution etc. If you are not setting the packet size, then the default
packet size of 100 is considered during the replication process. The packet size should be in-between 20
and 100. You can set the packet size only when you are using web service mode while replicating the
employee data or organizational objects to Employee Central.

Implementing Data Migration and Replication to Employee Central

Data Migration and Replication to Employee Central PUBLIC 209
  Note

Suppress Identical Records option that was previously present in the selection screen is not available from
SP 03 as Employee Central by default does suppression for the identical records always.

Next Steps

Make sure that the data of employees who are mastered in SAP S∕4HANA can't be edited in Employee Central. Use
role-based permissions to disable the edit mode in Employee Central based, for example, on the country of the
employee.

After the initial run of the program, changed data is replicated using delta replication. For more information, refer to
section Extracting Changed Employee Data Using Delta Replication. You can still run the Employee Data Extraction
program to extract data for selected employees.

Task overview: Data Extraction and Transfer [page 201]

Related Information

Extracting Employee Data in Multiple Steps [page 210]

Extracting Employees Manager Information [page 212]
Downloading CSV Files from the Application Server [page 217]
Extracting Changed Employee Data Using Delta Replication [page 219]
Replicating Employee Data to Custom Entities in Employee Central [page 221]
Transferring Data Deletion to Employee Central [page 222]
Extracting Employee Data with Additional Events Before Earliest Transfer Date [page 224]
How the Extraction Report behave for dierent Employment Statuses [page 236]
Parallelization of Employee Data Extraction with the Job Scheduler Report [page 238]

2.2.2.7.2 Extracting Employee Data in Multiple Steps

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

Prerequisites

In order to do a step wise employee data migration using a single transformation template group, you should have
already created a transformation template group using the view cluster VC_ECPAO_MAP. For more information see:
Creating a Transformation Template Group for Employee Data.

Implementing Data Migration and Replication to Employee Central

210 PUBLIC Data Migration and Replication to Employee Central
Context

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

When you are migrating data in steps, you don't need to perform the time-consuming process of changing the
template group conguration for each step in the test system and then transporting the same to the production
system. And for delta replication via change pointers, all the templates in the same template group can be used.
This can be done using the same template group by grouping the relevant templates of a step in a variant ID. The
relevant variant ID for a step must be selected in the selection screen of the Extraction report or the Job Scheduler
report.

When you are migrating the employee data, you can rst migrate only the minimum set of templates like
Biographical Info, Personal Info, Employment Info, and Job Info etc. This will make sure that you are not migrating
other templates, which are dependent on a template, where if the migration of that template fails, the subsequent
templates need not be migrated.

For ex: If Job Info template migration fails, then you really don't need to migrate Compensation, Recurring, Spot
bonus, Payment Information etc.

Once the initial migration process is successful, you can then migrate the remaining templates (ex Compensation,
Recurring, Spot bonus, Payment Information). Lastly you can execute the migration process only for the changed
data. For more information on migrating only the changed data, see: Extracting Changed Employee Data Using
Delta Replication.

Here you can use a single transformation template group (by creating dierent variant ID's for a single
transformation template group) to cater dierent scenarios without changing any congurations in the
transformation template group.

 Tip

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

Procedure

1. Create the variant ID using the customizing activity: Dene the Variant IDs for Data Migration (view
V_ECPAO_VARIANT).
2. Once you create the variant ID, you will have to add the transformation template to the variant ID using the
customizing activity: Dene the Transformation Templates for a Variant ID (view V_ECPAO_TEMP_VAR).
3. Choose the variant ID when you run the employee extraction report. For more information see:Extracting
Employee Data.

 Note

You can also choose the variant ID when you run the job scheduler report. For more information on job
scheduler report, see: Parallelization of Employee Data Extraction with the Job Scheduler Report.

Implementing Data Migration and Replication to Employee Central

Data Migration and Replication to Employee Central PUBLIC 211
  Note

Also make sure that all entities having dependencies should be included in the same variant. For ex:
Compensation with Recurring and Payment Information with Payment Information details and country
specic Payment Information details.

Task overview: Data Extraction and Transfer [page 201]

Related Information

Extracting Employee Data [page 202]

Extracting Employees Manager Information [page 212]
Downloading CSV Files from the Application Server [page 217]
Extracting Changed Employee Data Using Delta Replication [page 219]
Replicating Employee Data to Custom Entities in Employee Central [page 221]
Transferring Data Deletion to Employee Central [page 222]
Extracting Employee Data with Additional Events Before Earliest Transfer Date [page 224]
How the Extraction Report behave for dierent Employment Statuses [page 236]
Parallelization of Employee Data Extraction with the Job Scheduler Report [page 238]

2.2.2.7.3 Extracting Employees Manager Information

Learn how to migrate the Manager ID eld value in the employee job information entity.

ManagerID eld is part of the job information entity, and it is the key eld based on the Employee Central system
conguration. In Employee Central system, ManagerID eld is congured as associate object of employee user ID.

There are dierent ways by which you can migrate the Manager ID eld and this should be done in two steps.
Where, in the rst step you will have to rst migrate the Manager ID without manager assignments so that all
employments are migrated successfully. In the second step, you will have to migrate the manager assignments.
Below are the options to enable the migration of manager information. If the eld is mandatory in Employee
Central, then NO_MANAGER constant should be sent in the initial run and the the original manager could be
transferred in the subsequent run.

Option 1: Migrating the employee data with manager by choosing the dierent transformation template
groups in each step. You can migrate the employee data by running the employee extraction report by
choosing a transformation template group where all the employee data is extracted without manager
(NO_MANAGER) and then choose a second transformation template group where all the employee data is
extracted with manager.

1. Create a transformation template group having job information entity with ManagerID eld mapping as BAdI
Mapping for Integration/Migration to EC. Make sure that job info supervisor eld mapping dened as BAdI
Mapping for Integration/Migration to EC and data extracted as NO_MANAGER.

Implementing Data Migration and Replication to Employee Central

212 PUBLIC Data Migration and Replication to Employee Central
 Transformation template group having job information entity with ManagerID eld mapping as BAdI Mapping for Integration/
Migration to EC

In this case, by default all the employees manager will extract as NO_MANAGER as a initial run.

2. Create the second transformation template group having job information entity with ManagerID eld mapping
as Infotype Mapping. Make sure that job info supervisor eld mapping dened as Infotype Mapping with MNGR
infotype. You might have to run the extraction report for this transformation template group once again.

Implementing Data Migration and Replication to Employee Central

Data Migration and Replication to Employee Central PUBLIC 213
 Transformation template group having job information entity with manager id eld mapping as Infotype Mapping
3. Run the employee extraction report by choosing the rst transformation template group where all the
employee data is extracted without manager (NO_MANAGER)
4. Re-run the employee extraction report by choosing the second transformation template group where all the
employee data is extracted with manager.

Option 2: Migrating the employee data using the variant concept.

1. Create the transformation template group by supporting all the transformation templates and enable the delta
process.
2. Create transformation template job information for the transformation template group that you have created
now without manager and maintain the supervisor eld as BAdI mapping and as transformation template
status as inactive.

Implementing Data Migration and Replication to Employee Central

214 PUBLIC Data Migration and Replication to Employee Central
 Primary mapping conguration for job information without manager

3. Create another transformation template for job information for the same transformation template group with
manager and eld mapping for supervisor eld is MNGR.

Implementing Data Migration and Replication to Employee Central

Data Migration and Replication to Employee Central PUBLIC 215
 Primary mapping conguration for job information with manager
4. Activate the inactive transformation templates that you have created.
5. Create two variants, one with manager and one without manager. You can use the Dene the Variant IDs for
Data Migration Customizing activity (view V_ECPAO_VARIANT) to create the variant.
6. Link the variant with the transformation template. You can use the Dene the Transformation Templates for
a Variant ID Customizing activity (ECPAO_TEMP_VAR) to select which transformation templates should be
categorized under a variant ID congured for the corresponding transformation template group.
• Without manager variant: Link all necessary transformation templates with job info without manager
template.
• With manager variant: Link all necessary transformation templates with job info with manager template.
7. Run the employee extraction report to migrate the employee data by choosing the variant 1, where all the
employee data is extracted without manager details (NO_MANAGER).
8. Re-run the employee extraction report by choosing the variant 2, where all the employee data is extracted with
manager details.

Parent topic: Data Extraction and Transfer [page 201]

Related Information

Extracting Employee Data [page 202]

Extracting Employee Data in Multiple Steps [page 210]
Downloading CSV Files from the Application Server [page 217]
Extracting Changed Employee Data Using Delta Replication [page 219]
Replicating Employee Data to Custom Entities in Employee Central [page 221]

Implementing Data Migration and Replication to Employee Central

216 PUBLIC Data Migration and Replication to Employee Central
Transferring Data Deletion to Employee Central [page 222]
Extracting Employee Data with Additional Events Before Earliest Transfer Date [page 224]
How the Extraction Report behave for dierent Employment Statuses [page 236]
Parallelization of Employee Data Extraction with the Job Scheduler Report [page 238]

2.2.2.7.4 Downloading CSV Files from the Application Server

If you've stored the data extracted to CSV les on the application server, here's how to transfer the data from the
application server location to a local drive.

Prerequisites

• Dene the logical le path ECPAO_TMPL_DIR in the Logical File Path Denition (FILE) transaction.
• Dene Assignment of physical paths to logical path for the logical le path ECPAO_TMPL_DIR.

 Note

• Maintain the syntax group as UNIX.

• Maintain the source le path as /usr/sap/<SYSID>/SYS/global/<FILENAME> in the physical path.
• In the logical le name denition, double click on the logical le of ECPAO_TMPL_DIR dened similar to
as mentioned below: Parameters of this conguration should have the below values
• Physical le: <PARAM_1>
• Data format: ASC
• Applicat.area: HR
• Logical path: ECPAO_TMPL_DIR

Context

Procedure

1. Go to the SAP Directories (AL11) transaction.

2. Double-click DIR_GLOBAL to see the les in this directory and note the name of the le that you want to
download, such as 0001_BasicUSerInfoImportTemplate_Company.CSV.
3. Run the ECPAO_APPSRVR_FILE_DWNLD report using the transaction ECPAO_SRVR_FILE_DWNL.
1. Enter the server le path along with the lename from where you want to download the data. A value help
is also available which provides a list of all les existing in the application server le path maintained in FILE
conguration. Select any le from F4 help to proceed.

Implementing Data Migration and Replication to Employee Central

Data Migration and Replication to Employee Central PUBLIC 217
 2. Enter the local le path along with the le name where you want to save the data. A value help is also
available which enables you to select the folder. Once the folder is selected, the le name is auto-populated
using a reference of the lename provided in the server le path.

 Note

• Make sure that both the path’s extension matches to avoid any error.
• Only one le can be downloaded at one time.
• This report is not added as a part of the standard sample roles delivered with the add-on.

The below authorizations are required to run the report:

• S_DATASET ACTVT 33
• S_DATASET FILENAME
• S_DATASET PROGRAM ECPAO_APPSRVR_FILE_DWNLD
• S_TABU_NAM ACTVT 02
• S_TABU_NAM TABLE ECPAO_ASDNLD_INV
You can nd the downloaded le at the path provided on the selection screen. Once the le is successfully
downloaded, a log le is created in an inventory table (ECPAO_ASDNLD_INV) to track the download activities
performed by a user.

Task overview: Data Extraction and Transfer [page 201]

Related Information

Extracting Employee Data [page 202]

Extracting Employee Data in Multiple Steps [page 210]
Extracting Employees Manager Information [page 212]
Extracting Changed Employee Data Using Delta Replication [page 219]
Replicating Employee Data to Custom Entities in Employee Central [page 221]
Transferring Data Deletion to Employee Central [page 222]
Extracting Employee Data with Additional Events Before Earliest Transfer Date [page 224]
How the Extraction Report behave for dierent Employment Statuses [page 236]
Parallelization of Employee Data Extraction with the Job Scheduler Report [page 238]

Implementing Data Migration and Replication to Employee Central

218 PUBLIC Data Migration and Replication to Employee Central
2.2.2.7.5 Extracting Changed Employee Data Using Delta
Replication

After the initial run of the employee data extraction program, changed data is replicated using delta replication.
Here's how you need to set this up.

Prerequisites

You can only use template groups with the Web Service Transfer communication channel for delta replication.

Context

When HR administrator change employee data in the SAP S∕4HANA system, change pointers are created. You can
use the Job Scheduler report (ECPAO_EMPL_DMT_JOB_SCHEDULER) to extract the data for the changed employees.
In addition you can now replicate the employees who will be hired in future using the change pointers. By using the
job scheduler report, you can run the extraction process for a larger load and also schedule the extraction process
in batches. SAP recommends to use the Job Scheduler report as it is more efcient. For more information see:
Parallelization of Employee Data Extraction Via Job Scheduler Report topic.

Data extraction program choose the transformation template group from the VC_ECPAO_MAP view cluster. You
need to choose Enable for Delta Replication option to enable the delta replication. For more information see:
Creating a Transformation Template Group for Employee Data topic. Additionally, you can choose a subset of
transformation templates from the group for delta replication by enabling the Enable for Delta Replication option in
the V_ECPAO_VARIANT view.

The Creating IDoc Type from Change Pointers (RBDMIDOC) program (or BD21 transaction) reads the change
pointers with the ECPAO and ECPAO_OM message type, collects the object list to be processed, and determines
the delta enabled transformation template group and submits these details to the employee extraction report at
once. If you enable the ERP to EC/EC to ERP: Connect Multiple EC Instances switch in the constants table, then
the objects that are to be processed are split based on the Employee Central instance that is associated with their
company code and grouped them together with the associated delta enabled transformation template group. The
related objects belonging to the same Employee Central instance are processed together using the corresponding
delta enabled transformation template group.

 Note

The data replication does not use Application Link Enabling (ALE) or IDocs. The RBDMIDOC program uses
the ECPAO message type to trigger the replication of changed employee data to Employee Central using a
synchronous Web service call.

In SAP S∕4HANA, all infotype data is eective dated. In Employee Central, some data, such as email or phone
information, isn't eective dated. If you change data in SAP S∕4HANA for the future that isn't eective dated in
Employee Central, the corresponding change pointers will only be executed at this future date.

To ensure that the change pointers are not captured in PA_SE_IN integration when the message type ECPAO
and ECPAO_OM are not active in BD50 transaction, you must install the SAP Note: 2552346 .

Implementing Data Migration and Replication to Employee Central

Data Migration and Replication to Employee Central PUBLIC 219
  Tip

For larger loads of data, we recommend you to run the delta replication using the job scheduler report instead
of RBDMIDOC program or BD21 transaction.

To run the RBDMIDOC program, follow the below mentioned steps. To run the Job Scheduler report see:
Parallelization of Employee Data Extraction Via Job Scheduler Report topic.

Procedure

1. Go to the Dene Background Job (SM36) transaction.

2. Schedule the Creating IDoc Type from Change Pointers (RBDMIDOC) program as a regular background job using
the ECPAO message type.

Change Pointers for the ECPAO Message Type

Task overview: Data Extraction and Transfer [page 201]

Related Information

Extracting Employee Data [page 202]

Extracting Employee Data in Multiple Steps [page 210]
Extracting Employees Manager Information [page 212]
Downloading CSV Files from the Application Server [page 217]
Replicating Employee Data to Custom Entities in Employee Central [page 221]
Transferring Data Deletion to Employee Central [page 222]
Extracting Employee Data with Additional Events Before Earliest Transfer Date [page 224]
How the Extraction Report behave for dierent Employment Statuses [page 236]
Parallelization of Employee Data Extraction with the Job Scheduler Report [page 238]

Implementing Data Migration and Replication to Employee Central

220 PUBLIC Data Migration and Replication to Employee Central
2.2.2.7.6 Replicating Employee Data to Custom Entities in
Employee Central

Here's an overview of the steps involved when you want to transfer data from SAP S∕4HANA to a custom entity in
Employee Central.

Prerequisites

You have created a custom generic object in Employee Central. You can do this in the Admin Center by choosing the
Congure Object Denitions tool. When you create your entity, make sure to set the API Visibility option to Editable.

Procedure

1. Import the data model for your custom entity from Employee Central into the SAP S∕4HANA system.

a. Download the metadata from your custom entity in Employee Central.

• To download metadata of the CSV File-Based Transfer type:
1. Go to the Admin Center and choose the Import and Export Data tool.
2. In the Select the action to perform eld choose Download Template.
3. Select your object denition in the Select Generic Object eld and choose Download.
• To download metadata of the Web Service Transfer type:
1. Go to the Admin Center and choose the OData API Data Dictionary tool.
2. A list of entities is displayed.
If your custom entity isn't shown here, go back and choose the OData API Metadata Refresh and
Export tool, then choose Refresh.

OData API Metadata Refresh and Export Tool

3. Expand your custom entity and copy the complete content of the table displayed below Fields,
including the table header.
4. Paste the content to a spreadsheet and save the spreadsheet using the .csv le extension.
b. Import the metadata into the SAP S∕4HANA system using one of the metadata import programs.
2. Dene an Employee Central entity for your custom entity.
3. Map the elds of your Employee Central entity to a transformation template.

Implementing Data Migration and Replication to Employee Central

Data Migration and Replication to Employee Central PUBLIC 221
Task overview: Data Extraction and Transfer [page 201]

Related Information

Extracting Employee Data [page 202]

Extracting Employee Data in Multiple Steps [page 210]
Extracting Employees Manager Information [page 212]
Downloading CSV Files from the Application Server [page 217]
Extracting Changed Employee Data Using Delta Replication [page 219]
Transferring Data Deletion to Employee Central [page 222]
Extracting Employee Data with Additional Events Before Earliest Transfer Date [page 224]
How the Extraction Report behave for dierent Employment Statuses [page 236]
Parallelization of Employee Data Extraction with the Job Scheduler Report [page 238]

2.2.2.7.7 Transferring Data Deletion to Employee Central

For some Employee Central templates, a deletion of data can be transferred from SAP S∕4HANA to Employee
Central.

This means if you delete infotype data (such as an employee's phone number) in the SAP S∕4HANA system, this
data deletion can be transferred to Employee Central. To transfer the deletion, the compound delete Employee
Central entities are used. For CSV le-based data transfer, this is the Compound Delete CSV data import entity. For
Web service-based data transfer, this is the SFOData.HrisCompoundDeletion OData entity.

 Note

Use of the Compound Delete or SFOData.HrisCompoundDeletion entities needs to be enabled in Provisioning

using the Enable Compound Delete option.

 Remember

As a customer, you don't have access to Provisioning. To complete tasks in Provisioning, contact your
implementation partner or Account Executive. For any non-implementation tasks, contact Product Support.

The appropriate entity is lled with the employee's user ID and the HRIS element ID from the Employee Central
data model that corresponds to the Employee Central entity (such as phoneInfo). When the compound delete
entity is transferred to Employee Central, the corresponding data is deleted there for the specic employee.

To determine if data deletion is to be triggered, the employee data extraction program checks if the key eld of
the corresponding Employee Central template is empty. If this is the case, it issues a warning message. If you then
transfer the deletion to Employee Central, the data is actually deleted there.

Implementing Data Migration and Replication to Employee Central

222 PUBLIC Data Migration and Replication to Employee Central
The following Employee Central entities support transfer of data deletion:

CSV Data Import Entity Web Service Entity HRIS Element ID Key Field

Email Info PerEmail emailInfo email-address

Phone Info PerPhone phoneInfo phone-number

Job Relationships EmpJobRelationships jobRelationsInfo rel-user-id

Addresses PerAdressDEFLT homeAddress address-type

Pay Component Non Recurring EmpPayCompNonRecurring payComponentNonRecurring pay-component-code

NationalIdCardImportTemplat PerNationalId nationalIdCard national-id

e

 Note

Data deletion is currently supported only by Employee Central entities dened by SAP. You can't use it for
custom Employee Central entities.

 Example

Let's say you use the PhoneInfoImportTemplate Employee Central entity for CSV le-based data replication.
The employee data extraction program extracts phone info data using the eld mapping that is dened for the
transformation template to which the PhoneInfoImportTemplate Employee Central entity is assigned. Since the
corresponding infotype record was deleted, the data extracted for employee 12345 doesn't contain an entry in
the phone-number eld. Therefore, the extraction program issues the message that deletion of the phone info
data is triggered for this employee. It lls the employee ID 12345 and the HRIS element ID phoneInfo into the
Compound Delete template. Once you upload this information to Employee Central, the phone information for
employee 12345 is deleted there.

Parent topic: Data Extraction and Transfer [page 201]

Related Information

Extracting Employee Data [page 202]

Extracting Employee Data in Multiple Steps [page 210]
Extracting Employees Manager Information [page 212]
Downloading CSV Files from the Application Server [page 217]
Extracting Changed Employee Data Using Delta Replication [page 219]
Replicating Employee Data to Custom Entities in Employee Central [page 221]
Extracting Employee Data with Additional Events Before Earliest Transfer Date [page 224]
How the Extraction Report behave for dierent Employment Statuses [page 236]
Parallelization of Employee Data Extraction with the Job Scheduler Report [page 238]

Implementing Data Migration and Replication to Employee Central

Data Migration and Replication to Employee Central PUBLIC 223
2.2.2.7.8 Extracting Employee Data with Additional Events
Before Earliest Transfer Date

Learn how to extract the employee data with additional events before the earliest transfer date.

Context

The employee extraction report extracts the employee data from or after the earliest transfer date that you have
dened at the transformation template group. Hence the records are extracted with the earliest transfer date or
after the earliest transfer date with pseudo hire date as the rst event reason. During this process:

• Employee records before the earliest transfer date are not extracted which might lead to dierent hire date
in Employee Central (Employment information). Hire date in Employee Central is derived from the rst job
information record. Hence the start date of the pseudo hire event reason might be considered as the actual hire
date in the Employee Central (Employment Information) system.
• Terminated employees and the employees on long-term absences are not migrated.

To overcome these problems, as a best practice, it is recommended to use the additional events feature. By
conguring the additional events, employee extraction report migrate the records (Job Information and Personnel
Information) before the earliest transfer date with an additional data along with the records after the earliest
transfer date. For such additional records of job information created before the cut-o date you have an option to
migrate a constant or an actual database value based on the validity period.

 Note

Migration of additional events is not supported for the global information template.

If the additional events are not congured, the employee data migrates the data as shown here:

Employee Data Migration Without Conguring Additional Event Records

During the employee extraction report, the employee records are extracted based upon the earliest transfer date
that you have dened in the transformation template group. Hence the records are extracted with the earliest
transfer date or after the earliest transfer date with pseudo hire date as the rst event reason.

Implementing Data Migration and Replication to Employee Central

224 PUBLIC Data Migration and Replication to Employee Central
Procedure

1. Congure additional event types.

Disable Cut O Termination Start

Country Grouping Action Type Reason for Action Event Reason Split Date

01 PSEUDO_HIRE

02 DATAREORG

10 TEROTH

12 REHREH

16 DATACHG

01 01 PSEUDO_HIRE

01 02 DATAREORG

01 10 01 TEROTH

01 10 02 TEROTH X

01 10 03 TEROTH 01.01.2014

01 12 REHREH

01 16 DATACHG

01 82 ADDGA

01 - ENDGA

 Note
Action Type
depends on
Event Reason.

a. Go to the Dene Additional Event Types Conguration Customizing activity (view V_ECPAO_PLHD_ACT)
and maintain the action type with event reasons to create the additional event types before the earliest
transfer date and if there is a record with the start date as same as the earliest transfer date.
b. Choose the Transformation Template Group, for which you want to maintain the additional event types.
c. Choose the country for which you want to maintain the action types and the reason for action.
• In this view, you can maintain the set of action types with or without the country grouping. If you do not
provide any country grouping, then the action types would be applicable for all the available countries
for which the conguration is not maintained in this view

Implementing Data Migration and Replication to Employee Central

Data Migration and Replication to Employee Central PUBLIC 225
  Example

• Personnel Number: 1 – Belongs to US

• Personnel Number: 2 – Belongs to DE
• Personnel Number: 3 – Belongs to IN

Country Group- Reason for Ac- Disable Cut O Termination

ing Action Type tion Event Reason Split Start Date

01 PSEUDO_HIRE

10 TEROTH

12 REHREH

01 01 PSEUDO_HIRE

01 10 TEROTH

01 12 REHREH

If the above mentioned conguration is available, then for Personnel number 1 & 3 system
will consider the below conguration for the processing. Because there is no country specic
congurations available for these country groupings.

Country Group- Reason for Ac- Disable Cut O Termination

ing Action Type tion Event Reason Split Start Date

01 PSEUDO_HIRE

10 TEROTH

12 REHREH

For Personnel number 2 system will consider the below conguration for processing. Because
there is Germany specic congurations available for this country grouping.

Country Group- Reason for Ac- Disable Cut O Termination

ing Action Type tion Event Reason Split Start Date

01 01 PSEUDO_HIRE

01 10 TEROTH

01 12 REHREH

• Combination of dierent country grouping action types for a single PERNR is not allowed.

Implementing Data Migration and Replication to Employee Central

226 PUBLIC Data Migration and Replication to Employee Central
  Example

As per the conguration mentioned in the above table, for the country Germany a set of action
types are created with their country grouping as same as the action types with blank country
grouping. So in this case, German employee will only consider the set of action types, which is
congured for their corresponding country grouping. It won't consider the set of action types
with blank country grouping. Same rule is applicable for the other countries where as per
the conguration mentioned in the above table, blank country groupings action types will be
considered ignoring the set of action types with Germany country grouping.

d. Choose the action type.

In general maintain the action type like Hire, Termination, and Re-Hire in the view for that particular
template group. If the termination action type is not maintained, then a warning message would be
displayed for the terminated employees. In this case, this employee would be ignored during the employee
migration. If no action type is maintained in this view, then an error would be displayed during the
employee extraction process.

 Note

All the status-changing actions have to be dened to ensure correct status changes are extracted.

e. Choose the reason for the action type.

If the reason for action is left blank, then all the combination of that particular action type would be
considered for additional event migration.

 Example

Country Group- Reason for Ac- Disable Cut O Termination

ing Action Type tion Event Reason Split Start Date

01 PSEUDO_HIRE

10 TEROTH

12 REHREH

In this case the above mentioned action types will consider all the combination of reason for action for
migration.

Country Group- Reason for Ac- Disable Cut O Termination

ing Action Type tion Event Reason Split Start Date

01 01 PSEUDO_HIRE

10 01 TEROTH

12 S1 REHREH

Implementing Data Migration and Replication to Employee Central

Data Migration and Replication to Employee Central PUBLIC 227
 In this case the above mentioned action types will consider only the combination of reason for action
maintained in the conguration view for the migration.

f. Enter the event reason.

You need to maintain the corresponding Employee Central event reason based upon the combination of
Action Type and Reason for Action.
g. Disable Cut O Split option is applicable for the Action Type whose employment status is not active. If the
option is not enabled, an additional record is created as o the earliest transfer date. If the option Disable
Cut O Split is enabled, an additional record as o earliest transfer date won't be created. Instead earlier
record will be extended to the actual end date.
h. Maintain the Termination Start Date if the terminated employees are to be considered from the termination
start date. This is valid only if the Termination Action is the last action performed for an employee.

 Note

Termination start date should be always less than the earliest transfer date. Be default Create New
Employment for International Transfer is created when an employee in transferred internationally. Only
for those employess that were previously migrated using REUSE Employment we will continue to
support this on re-migration.

2. Congure additional event data

Transformation EC Field ID De-

Country Grouping Template EC Field ID scription Value Type Constant

ERP_JOBINFO_WS 86 Supervisor Constant Value NO_MANAGER

ERP_JOBINFO_WS 39 Department ERP Database

Value

01 ERP_JOBINFO_WS 86 Supervisor Constant Value NO_MANAGER

01 ERP_JOBINFO_WS 41 Division ERP Database

Value

a. Go to the Dene Additional Event Data Conguration Customizing activity (view V_ECPAO_PLHD_ CON)
and maintain the additional event infotype data. Here you can set the constant value or database value for
an Employee Central eld available in the Job information or the Personal information.
b. Choose the Transformation Template Group, for which you want to maintain the additional event infotype
data.
c. Choose the country for which you want to maintain the additional event infotype data.
• As default Employee Central eld data conguration with blank country grouping would be considered
if country- specic Employee Central eld conguration is not maintained for additional events.

 Example

• Personnel Number: 1 – Belongs to US

• Personnel Number: 2 – Belongs to DE

Implementing Data Migration and Replication to Employee Central

228 PUBLIC Data Migration and Replication to Employee Central
 • Personnel Number: 3 – Belongs to IN

Country Group- Transformation EC Field ID

ing Template EC Field ID Desc Value Type Constant

ERP_JO- 86 Supervisor Constant Value NO_MANAGER

BINFO_WS

ERP_JO- 39 Department ERP Database

BINFO_WS Value

01 ERP_JO- 86 Supervisor Constant Value NO_MANAGER

BINFO_WS

01 ERP_JO- 41 Division ERP Database

BINFO_WS Value

If the above mentioned conguration is available, then for Personnel number 1 & 3 system
will consider the below conguration for the processing. Because there is no country specic
congurations available for these country groupings.

Country Group- Transformation EC Field ID

ing Template EC Field ID Desc Value Type Constant

ERP_JO- 86 Supervisor Constant Value NO_MANAGER

BINFO_WS

ERP_JO- 39 Department ERP Database

BINFO_WS Value

For Personnel number 2 system will consider the below conguration for processing. Because
there is Germany specic congurations available for this country grouping.

Country Group- Transformation EC Field ID

ing Template EC Field ID Desc Value Type Constant

01 ERP_JO- 86 Supervisor Constant Value NO_MANAGER

BINFO_WS

01 ERP_JO- 41 Division ERP Database

BINFO_WS Value

• Combination of dierent country grouping Employee Central eld conguration for a single employee
is not allowed.

d. Choose the Transformation Template (Job information & Personal information). Here you need to select
the transformation template for which the data should be set as Constant Value or ERP Database Value.

Implementing Data Migration and Replication to Employee Central

Data Migration and Replication to Employee Central PUBLIC 229
  Note

Only active transformation template would be displayed in the search help.

e. Choose the Employee Central eld ID from the above mentioned transformation template. Once the
Employee Central eld ID is selected, corresponding description is populated in the Employee Central eld
description eld.
f. Choose the Value Type from the drop down box. From the value type, you can maintain whether the
selected Employee Central eld should hold a constant value or a database value.

Constant Constant value type can be used for precongured mapping and infotype mapping
Value Employee Central elds available in the Job information and Personnel information
template. For constant value type, Constant column should be maintained. Even a blank
value can be considered as a Constant value.

ERP Database Database value type can be used only for infotype mapping Employee Central elds,
Value which is part of a valid Personal Administration infotype. Constant column should not be
maintained for this infotype This database value cannot be used for the infotype mapping
elds whose value depend on the another eld.

 Note

BAdi mapping elds are not supported for both value types.

Congured Employee Central eld values which are migrated through the above mentioned value types
should be available in Employee Central. If the values are not maintained in Employee Central, then
during the migration process, an error message would be generated during the data transfer process
(CSV upload or middleware).

g. Enter a value if the value type is set as Constant Value. Even a blank value can be considered as a Constant
value.

 Note

This eld is not supported for the value type ERP Database Value.

If there is no conguration data maintained in this view, then the additional event records will have
the same data as the rst record after the earliest transfer date. To migrate an empty data for a
particular Employee Central eld, congure the Employee Central eld as constant value type with a
blank constant value.

 Note

• When an employee is having multiple assignments like Global Transfer, Global Assignments,
Concurrent Employment and based on the additional event termination start date condition
(V_ECPAO_PLHD_ACT), employment 1 is ltered. All the employee data is not extracted but only
User, Biographical and Personnel info entity data based on the employment 1 are extracted.
• Termination start date limit is not applicable for the users whose home assignment is not
considered. If this is considered, then the replication process will fail. This is because we would
not be able to migrate the data to Employee Central without home assignment employment
information details. This is applicable only for Global Assignment scenario.
• Additional event records via conversion rules are not supported.

Implementing Data Migration and Replication to Employee Central

230 PUBLIC Data Migration and Replication to Employee Central
 • On the earliest transfer date if the employee is not active, then the system will try to extract
the data of Position ID, Department, Division, Business Unit, Job Code, and Cost Center elds as
available in the ERP system during the inactive status of that earliest transfer period. Hence to get
the active record data, you need to modify the earlier transfer date through a BAdi process. You
can also maintain the default position ID in Employee Central.
• During an international transfer once a PERNR is terminated from the rst country a new second
PERNR is created in the second country. Now if the employee is transferred back to the old country
a new third PERNR should be created. In case the rst PERNR is re-hired in the rst country due
to the second international transfer, then this use case is not supported currently. We are also not
supporting the following scenarios:
• Two dierent combinations of contracts for an employee through Re-hire concept.

 Example

• There is a global assignment from PERNR 1 to PERNR 2 (host PERNR is terminated

when global assignment starts) followed by an international transfer from PERNR 2 to
PERNR 1.
• There is an international transfer from PERNR 1 to PERNR 2 followed by an
international transfer back from PERNR 2 to PERNR 1.

Example

Scenario 1: Additional Event on Hire

Additional Event on Hire

Scenario 2: Additional Event on Termination

Implementing Data Migration and Replication to Employee Central

Data Migration and Replication to Employee Central PUBLIC 231
 Additional Event on Termination

 Note

If you are performing the migration from SAP S∕4HANA to Employee Central and replication from Employee
Central to SAP S∕4HANA in a full cycle, then SAP would recommend you to use the Option 2. If only migration
of data from SAP S∕4HANA to Employee Central is performed, then you can use Option 1 or 2.

Scenario 3: Additional Event on Re-Hire

Implementing Data Migration and Replication to Employee Central

232 PUBLIC Data Migration and Replication to Employee Central
 Additional Event on Re-Hire

Scenario 4: Additional Event on Leave of Absence

Additional Event on Leave of Absence

Implementing Data Migration and Replication to Employee Central

Data Migration and Replication to Employee Central PUBLIC 233
  Note

If you are performing the migration from SAP S∕4HANA to Employee Central and replication from Employee
Central to SAP S∕4HANA in a full cycle, then SAP would recommend you to use the Option 2. If only migration
of data from SAP S∕4HANA to Employee Central is performed, then you can use Option 1 or 2.

Scenario 5: Additional Event on Concurrent Employment

Additional Event on Concurrent Employment

Scenario 6: Additional Event on Global Assignment

Additional Event on Global Assignment

Implementing Data Migration and Replication to Employee Central

234 PUBLIC Data Migration and Replication to Employee Central
Scenario 7: Additional Event on International Transfer

Additional Event on International Transfer - When the same employment was re-used in EC

Task overview: Data Extraction and Transfer [page 201]

Related Information

Extracting Employee Data [page 202]

Extracting Employee Data in Multiple Steps [page 210]
Extracting Employees Manager Information [page 212]
Downloading CSV Files from the Application Server [page 217]
Extracting Changed Employee Data Using Delta Replication [page 219]
Replicating Employee Data to Custom Entities in Employee Central [page 221]
Transferring Data Deletion to Employee Central [page 222]
How the Extraction Report behave for dierent Employment Statuses [page 236]
Parallelization of Employee Data Extraction with the Job Scheduler Report [page 238]

2.2.2.7.8.1 Recommended Congurations while Using Additional

Events

Here you can read about the recommended congurations that you can use to use the additional events feature.

• If you are performing the migration from SAP S∕4HANA to Employee Central and replication from Employee
Central to SAP S∕4HANA in a full cycle, then we would recommend you to disable (Option 2) the Disable Cut O
Split option in the view V_ECPAO_PLHD_ACT. If only migration of data from SAP S∕4HANA to Employee Central
is performed, then you can either enable (Option 1) or disable (Option 2) the Disable Cut O Split option in the
view V_ECPAO_PLHD_ACT.
• Action types mentioned in the view V_ECPAO_PHLD_ACT will be considered only for the records, which are
migrated before the earliest transfer date and if there is a record in SAP S∕4HANA with the start date as same

Implementing Data Migration and Replication to Employee Central

Data Migration and Replication to Employee Central PUBLIC 235
 as the earliest transfer date, then the action types mentioned in the same view would be considered for that
record.
• SAP S∕4HANA database value type in the view V_ECPAO_PLHD_CON can be used only for the Employee Central
elds, which are part of the Personnel Administration infotypes.
• SAP S∕4HANA database value type can be used only for the direct eld mapping eld value.
• Transformation template group cutover date should be same as the middleware full transformation start date.

2.2.2.7.9 How the Extraction Report behave for dierent

Employment Statuses

When the additional events are not congured, the employments that are inactive as of earliest transfer date and
changes beyond the earliest transfer date is ignored from transferring to Employee Central.

If an employee has an employment status as inactive, then the complete extraction of the data will be stopped
irrespective of whether the template is eective-dated or non-eective dated after the earliest transfer date. The
user status that is part of User Entity (WS_1 or CSV_1) is set to Active or Inactive based on the current employment
status on the current date.

Behaviour during the initial load

Employment Status on earliest transfer date is... (and no
change in the future until 31.12.9999) ...Is considered for migration

Active Yes

Inactive No

Retired No

Withdrawn No

Behaviour during delta

Employment Status on earliest transfer
date is...(and no change in the future
until 31.12.9999) Use cases ...Is considered for migration

Active Employee was active during initial load Yes

and is still active.

Employee was inactive during initial load Yes

and changed to active state after initial
load.

Employee was retired during initial load Yes

and changed to active state after initial
load.

Inactive Employee was active during initial load Yes

but was changed to inactive state after
initial load.

Employee was inactive during initial load No

and is still inactive.

Implementing Data Migration and Replication to Employee Central

236 PUBLIC Data Migration and Replication to Employee Central
 Employment Status on earliest transfer
date is...(and no change in the future
until 31.12.9999) Use cases ...Is considered for migration

Retired Employee was active during initial load Yes (Default position is not transferred,
but now changed to retired state after but the last valid position would be trans-
initial load. ferred to Employee Central.)

Employee was withdrawn during initial No

load and changed to retired state after
initial load.

Employee was inactive during initial load No

and changed to retired state after initial
load.

Withdrawn Employee was active during initial load Yes (Default position is not transferred,
and changed to withdrawn state after ini- but the last valid position would be trans-
tial load. ferred to Employee Central.)

Employee was inactive during initial load No

and changed to withdrawn state after ini-
tial load.

Employee was moved from retired to No

withdrawn state.

The above logic for ltering the PERNR's based on the employment status and the earliest transfer date is also
applicable for an employee having multiple PERNR's as part of the International Transfer, Global Assignment, and
Concurrent employment. In this case, individual PERNR's will be ltered out completely if it satises the above
ltering criteria's. For example, in international transfer if the earliest transfer date is after the termination date of
the PERNR 1, then the PERNR 1 will be completely ltered out and PERNR 2 will be migrated to Employee Central
with single employment.

Parent topic: Data Extraction and Transfer [page 201]

Related Information

Extracting Employee Data [page 202]

Extracting Employee Data in Multiple Steps [page 210]
Extracting Employees Manager Information [page 212]
Downloading CSV Files from the Application Server [page 217]
Extracting Changed Employee Data Using Delta Replication [page 219]
Replicating Employee Data to Custom Entities in Employee Central [page 221]
Transferring Data Deletion to Employee Central [page 222]
Extracting Employee Data with Additional Events Before Earliest Transfer Date [page 224]
Parallelization of Employee Data Extraction with the Job Scheduler Report [page 238]

Implementing Data Migration and Replication to Employee Central

Data Migration and Replication to Employee Central PUBLIC 237
2.2.2.7.10 Parallelization of Employee Data Extraction with the
Job Scheduler Report

For migrating a large number of employee data to Employee Central you can use the Job Scheduler report. This
report will automatically divide the load into smaller batches and schedule multiple background jobs, which can be
executed in parallel.

Prerequisites

You should have already congured the settings for running the employee extraction report.

Context

When you execute the report, it will automatically divide the load into smaller batches and schedule multiple
background jobs for each batch. The program extracts all employee data for the selected employees that you
have dened using the transformation template group specied on the selection screen of the program. At any
point of time there will be a set of parallel jobs running. Once a particular job is completed, the next job would
start immediately. This will ensure that the total processing time to complete the employee migration for all the
employees is shorter.

Procedure

1. Go to the Job Scheduler for Employee Data Migration (ECPAO_JOB_SCHED_EE) transaction to run the Job
Scheduler for Employee Data Migration (ECPAO_EMPL_DMT_JOB_SCHEDULER) program.

The program extracts employee data from the SAP S∕4HANA system based on your selection criteria.
2. Specify for which employees the data is to be extracted. To do so, either specify the personnel numbers of the
employees or use organizational assignment criteria to select a group of employees.

For the list of PERNR's that you have chosen, the delta enabled transformation template group is determined
for the chosen Employee Central instance and it's submitted via the background jobs for processing. The
remaining PERNR's would be ltered out for processing as they don't belong to the chosen Employee Central
instance.
3. Select the Modied Employees Only checkbox if you want to extract the data only for the modied employees
and then schedule the extraction process in the background. When you choose this option, you can only use
the Job Selection Criteria elds to execute the report. This option should be chosen when you want to perform
delta replication via change pointers. For more information see: Extracting Changed Employee Data Using
Delta Replication topic. If the ERP to EC/EC to ERP: Connect Multiple EC Instances switch is enabled in the
constants table, then you need to choose the Employee Central instance. Only those objects that are related to
the chosen Employee Central instance are considered for processing by the job scheduler for employee data
migration program.

Implementing Data Migration and Replication to Employee Central

238 PUBLIC Data Migration and Replication to Employee Central
 4. Specify the number of employees that need to be replicated per job and the number of jobs that has to be
performed in parallel.

 Note

The maximum number of Employees Per Job is 100 and the Max No. of Jobs is 50. The default Max No. of
Jobs is 10. If the number of employees per job and the maximum number of jobs exceeds the limit, you
would receive a warning message.

5. Select the transformation template group to be used for the data extraction. Transformation template groups
are dened in the VC_ECPAO_MAP view cluster.
6. Select the variant ID that you have created before in the Dene the Variant IDs for Data Migration customizing
activity (view V_ECPAO_VARIANT). Once you have created the variant ID, you should have assigned the
required transformation templates to the variant ID using the Dene the Transformation Templates for a Variant
ID customizing activity (view V_ECPAO_TEMP_VAR).

 Note

This is not a mandatory eld. You can choose the Variant ID if you want to perform the extraction in multiple
steps. For more information, see: Extracting Employee Data in Multiple Steps.

For example, a transformation template group consists of the 5 transformation templates (ERP1, ERP2, ERP3,
ERP4, and ERP5). In these templates if you want to choose only ERP1, ERP3, and ERP5, you can create a
variant ID for these transformation templates. And when you choose this variant ID for migration process, only
these transformation templates (ERP1, ERP3, and ERP5) would be considered.

 Note

You can congure the EC templates, which should be ltered out for a given country using the customizing
activity Filter EC Entities for Migrating Employee Data to EC based on Country (view V_ECPAO_ECTM_FIL).

7. Specify how you would like to transfer the data:

• By Web Services, using the middleware that is available for the Employee data migration from SAP
S∕4HANA to Employee Central .
• Using an application server.
If you select the File Transfer and Use Server Path options, you can later transfer the data from the
application server location to a local drive.

 Note

When you schedule the program as a background job to carry out a mass data extraction where the
data would be imported to Employee Central, choose the File Transfer Use Server Path option.

If you want to combine several CSV les into a .zip le, select the Combine into ZIP le checkbox. Please
note that CSV les that you create for generic objects can't be zipped. They are stored separately, even if
you select the Combine into ZIP le option.
8. Select the Detailed Message Log checkbox if you want to get a detailed log containing all messages.

The download log le shows all the success, error, and warning messages. It will also include the number of les
that were downloaded and from where the le is downloaded from.

Please note that the les might contain personal and sensitive data. Additional authorization is performed to
check if the user has the right to download the CSV le. Only specic authorized users should be allowed

Implementing Data Migration and Replication to Employee Central

Data Migration and Replication to Employee Central PUBLIC 239
 for this operation. The downloads that are triggered by a user to the application server or local server in
Production mode and in Test Run (Download Payload) are logged via table ECPAO_OBJ_DWNLD along with the
timestamp and transformation template details.

The below authorizations are required to be able to download the CSV les:

Authorizations
Authorization Object Authorization Field Authorization Value

S_DATASET(for application server) ACTVT 34

S_DATASET(for application server) FILENAME /usr/*

S_DATASET(for application server) PROGRAM CL_ECPAO_FILE_ON_SERVER*

ECPAO_EMPL_EXTRACTION

S_TABU_NAM ACTVT 02

S_TABU_NAM TABLE ECPAO_OBJ_DWNLD

9. You can also choose other selection criteria based on for which employees the data is to be extracted:
• Select the Failed Employees Only checkbox if you want to re-run the replication for only those employees
for which the replication status is failed. The number of jobs created will be based on the number of failed
employees.

 Note

Failed Employees Only is supported only for Web Service Transfer mode.

Supress Identical Records option that was previously present in the selection screen is not available from SP 03
as Employee Central by default does suppression for the identical records always.

Results

After all the jobs are completed in the background, all the Employee data will be migrated to Employee Central via
web service transfer or downloaded via csv les in the application server.

 Note

If multiple PERNRs are linked to one Central Person (CP), then the PERNR's belonging to the same Central
Person will be processed in the same job. If the employees per job is 100, then there might be a chances of
having more than 100 PERNR's being executed in a single job due to the PERNR' been linked to the same CP.

The extraction process updates the change pointers (if available) of the successfully migrated PERNR's, and marks
the change pointers as processed. In case the ERP to EC/EC to ERP: Connect Multiple EC Instances switch is
enabled in the constants table then the change pointers are used to determine the list of PERNRs that are relevant
to the chosen Employee Central instance and only these PERNRs are processed by the program.

Task overview: Data Extraction and Transfer [page 201]

Implementing Data Migration and Replication to Employee Central

240 PUBLIC Data Migration and Replication to Employee Central
Related Information

Extracting Employee Data [page 202]

Extracting Employee Data in Multiple Steps [page 210]
Extracting Employees Manager Information [page 212]
Downloading CSV Files from the Application Server [page 217]
Extracting Changed Employee Data Using Delta Replication [page 219]
Replicating Employee Data to Custom Entities in Employee Central [page 221]
Transferring Data Deletion to Employee Central [page 222]
Extracting Employee Data with Additional Events Before Earliest Transfer Date [page 224]
How the Extraction Report behave for dierent Employment Statuses [page 236]

2.2.2.7.10.1 Monitoring Employee Migration Status using Job

Scheduler Report

You can monitor the Employee migration status using the Job Scheduler Report.

You can check the intermediate status of the current set of completed and running jobs using the SM37
transaction. You can check the output using the SM37 transaction by entering “*” in the job name and user name
eld. You can enter the user name who will be executing the operation.

Since employee migration has been executed in multiple batches, the ongoing migration status analysis is possible
based on the already completed jobs. Once a single job is completed, the migration status information for those
PERNR's and the relevant templates will be stored in the inventory tables (ECPAO_INVT & ECPAO_INVT_MSG).
And you can execute the ALV report (ECPAO_EMPL_INVENTORY_ALV) to get the status of all the employees for
which extraction has already happened. Here you can see status messages, which shows the success, success with
detailed warning messages from Employee Central or the failed process with a detailed error message.

When you now run the employee inventory report, you can now choose the "Filtered Employee List" option to list
only the ltered employees during the replication process. The SLG log le will display the information of personnel
number, reason message and the last execution date

 Note

When you choose Filtered Employee List option, other selection criteria’s would be disabled.

Implementing Data Migration and Replication to Employee Central

Data Migration and Replication to Employee Central PUBLIC 241
The naming convention of the jobs would be like: DM_RUN_SB_JOB_1, DM_RUN_SB_JOB_2, DM_RUN_SB_JOB_3
etc, where "SB" is the File Identier that you have mentioned in the report screen.

 Note

After executing the report when you view the jobs using the SM37 transaction, do not cancel the jobs, which are
in process. This denotes the migration of the employees belonging to that job is still in process.

2.2.2.8 Special Use Cases in Data Replication to Employee

Central

Take a look at special use cases that can occur during data replication to Employee Central.

2.2.2.8.1 Connecting Multiple Employee Central Instances to

the Same SAP S∕4HANA Client

Connect multiple Employee Central instances to the same client of your SAP S∕4HANA system. For example, if your
company has dierent legal entities that require separate management of employee data and therefore separate
instances of SAP SuccessFactors Employee Central, but you want to ensure that common processes, such as
payroll that you run in SAP S∕4HANA, run consistently for all your employees.

What Does this Feature Look Like?

The following graphic shows an example of how multiple Employee Central instances could be connected to one
client of the SAP S∕4HANA system, as well as some of the conguration settings that you make for the connection.

Implementing Data Migration and Replication to Employee Central

242 PUBLIC Data Migration and Replication to Employee Central
The following graphic shows an example of how multiple Employee Central instances can be connected to one
client of the SAP S∕4HANA system. We recommend that you use one SAP Cloud Integration tenant and set up a
default logical port to connect to that tenant.

For Whom Is this Feature?

This feature can be useful for you if you are in the following situation:

• You are a service provider that provides specic processes such as payroll in an SAP S∕4HANA system and
operates other HR functions in SAP SuccessFactors Employee Central. You need separate Employee Central
instances for dierent legal entities, but you want to use a common payroll system to run payroll consistently
across all Employee Central instances.
• Your company is a conglomerate with dierent legal entities. For certain business processes, you need separate
Employee Central instances to be able to separate the management of employee and organizational data for
the legal entities. However, general processes such as benets, taxes, and payroll should be run consistently in
one SAP S∕4HANA system.
• Your company goes through a company event, such as a merger or split, during which you must use separate
Employee Central instances for a transition period. You want to run processes such as payroll consistently in an
SAP S∕4HANA system and gradually adapt your company to the changed situation until all internal processes
are unied.

 Restriction

Migration follows the paradigm One CP. That is, all related employments can be sent to one Employee Central
instance only. For example, if an employee has one employment associated with company code DE01 and
another employment associated with company code DE02, this employee cannot be migrated if these two
employments are associated with dierent Employee Central instance IDs.

Implementing Data Migration and Replication to Employee Central

Data Migration and Replication to Employee Central PUBLIC 243
Prerequisites for Using this Feature

You need to decide prior to the migration process whether you have the need for multiple Employee Central, single
ERP landscape and then set the ERP to EC/EC to ERP: Connect Multiple EC Instances constant accordingly in the
constants table. This feature should not be enabled in the middle of the migration process.

If you use the external assignment ID, you must congure your business rules in Employee Central in a way that the
external assignment ID is unique across Employee Central instances.

Your SAP S∕4HANA system must have the following minimum stack level:

• SAP S/4HANA 2022: Support Package Stack 4 or higher

• SAP S/4HANA 2023: Feature Package Stack 2 or higher

2.2.2.8.1.1 Setting Up the Connection of Multiple Employee

Central Instances to the Same SAP S∕4HANA
System Client

Perform the required steps in the correct order if you had previously connected your SAP S∕4HANA system to one
Employee Central instance and now want to connect multiple Employee Central instances to the same client.

Procedure

Step
Number Step Description Step Details More Info

1 Migrate the employee key mapping You may already have run the
from the non-BIB version to the BIB- Convert Employee Key Mapping from
based version. Non-BIB to BIB-Based Version
(ECPAO_CONV_EEKEYMAP_TO_EE_K
MAP) program. If not, it's important
to do this before you enable the con-
stant ERP to EC/EC to ERP: Connect
Multiple EC Instances.

2 Enable the constant ERP to EC/EC to Go to Customizing for the Busi- Enabling Connection of Multiple Em-
ERP: Connect Multiple EC Instances. ness Integration Builder and choose ployee Central Instances to SAP
Data Replication from Employee S∕4HANA [page 248]

Central Basic Settings Maintain

Constant Values for Data Replication
from EC . Add the constant ERP to
EC/EC to ERP: Connect Multiple EC
Instances and set the constant value
to X.

Implementing Data Migration and Replication to Employee Central

244 PUBLIC Data Migration and Replication to Employee Central
 Step
Number Step Description Step Details More Info

3 Map your Employee Central instance Go to Customizing for the Busi-

IDs to your company codes. ness Integration Builder, choose
Prerequisites Connect Multiple
Employee Central Instances Assign
Employee Central Instance to
Company Code , and assign your
Employee Central instances to com-
pany codes. The extraction report
used this information to check if the
PERNR is run with the transforma-
tion template group corresponding
to the Employee Central instance as-
sociated with the PERNR's company
code.

4 Run the Prepare Employee Data Go to the Prepare Multiple EC

Replication for Connecting Multiple Instances (ECPAO_PREPARE_MULT)
EC Instances transaction to run the program. This
(ECPAO_PREPARE_MULT_EC_COMPA ensures that theEmployee Central in-
NY) program. stance ID is updated in the employee
key mapping table for the existing
employee records that were already
migrated.

Implementing Data Migration and Replication to Employee Central

Data Migration and Replication to Employee Central PUBLIC 245
Step
Number Step Description Step Details More Info

5a Congure SAP Cloud Integration Perform either this step or the next Copying the Integration Packages in
for the connection of multiple Em-
step. SAP Cloud Integration [page 28]
ployee Central instances if you use
the same SAP Cloud Integration in- If you use one SAP Cloud Integration Conguring the Value Mapping for
stance for all Employee Central in- instance, you can use the default log- Connecting Multiple Employee Cen-
stances that you connect.
ical port that you've created in the tral Instances to SAP S∕4HANA
SOA Management (SOAMANAGER) [page 40]
transaction for all Employee Central
Conguring the Integration Flow for
instances that you connect.
Data Replication to Employee Cen-
1. Go to your SAP Cloud tral [page 29]
Integration instance and
copy the SAP SuccessFactors Conguring the Integration Flow for
Employee Central Integration Replication of Generic Data from
with SAP ERP or SAP S/4HANA: Employee Central to SAP S∕4HANA
System Mapping integration Using the OData API [page 34]
package.
2. Congure and deploy the Conguring the Integration Flow for
SAP SuccessFactors Employee Replication of Generic Data from
Central Integration with SAP Employee Central to SAP S∕4HANA
ERP or SAP S/4HANA: System Using the OData API [page 34]
Mapping value mapping.
3. Replace the conguration of the
Employee Central address and
credentials for the following in-
tegration ows with a string that
reads the value mapping if you
use them:
• Replicate Generic Data
from SAP SuccessFactors
Employee Central to SAP
ERP or SAP S/4HANA
Using the OData API
• Upsert Data from SAP ERP
or SAP S4HANA to SAP
SuccessFactors Employee
Central Using the OData
API

Implementing Data Migration and Replication to Employee Central

246 PUBLIC Data Migration and Replication to Employee Central
 Step
Number Step Description Step Details More Info

5b Congure SAP Cloud Integration for Perform either this step or the previ- Conguring Consumer Proxies and
the connection of multiple Employee
ous step. Logical Ports for Connecting Multiple
Central instances if you use separate
Employee Central Instances [page
SAP Cloud Integration instances for If you use several SAP Cloud
the Employee Central instances that 250]
Integration instances, you need spe-
you connect.
cic logical ports for the Employee Copying the Integration Packages in
Central instances that you connect. SAP Cloud Integration [page 28]

1. Go to the SOA Management Conguring the Value Mapping for

(SOAMANAGER) transaction and Connecting Multiple Employee Cen-
create a logical port for each
tral Instances to SAP S∕4HANA
Employee Central instance that
[page 40]
you connect.
2. Go to the Assign Logical Conguring the Integration Flow for
Port to EC Instance Data Replication to Employee Cen-
(ECPAO_INSTANCE_LP) trans-
tral [page 29]
action and assign the logical
port and consumer proxy to Conguring the Integration Flow for
the specic Employee Central Replication of Generic Data from
instance ID for which you want
Employee Central to SAP S∕4HANA
to use the logical port.
Using the OData API [page 34]
3. Go to one of your SAP
Cloud Integration instances and Conguring the Integration Flow for
copy the SAP SuccessFactors Replication of Generic Data from
Employee Central Integration
Employee Central to SAP S∕4HANA
with SAP ERP or SAP S/4HANA:
Using the OData API [page 34]
System Mapping integration
package. Conguring the Integration Flow for
4. Congure and deploy the Data Replication to Employee Cen-
SAP SuccessFactors Employee
tral [page 29]
Central Integration with SAP
ERP or SAP S/4HANA: System
Mapping value mapping.
5. Replace the conguration of the
Employee Central address and
credentials for the following in-
tegration ows with a string that
reads the value mapping if you
use them:
• Replicate Generic Data
from SAP SuccessFactors
Employee Central to SAP
ERP or SAP S/4HANA
Using the OData API
• Upsert Data from SAP ERP
or SAP S4HANA to SAP
SuccessFactors Employee
Central Using the OData
API
6. Congure all other SAP Cloud
Integration instances that you
use in the same way.

Implementing Data Migration and Replication to Employee Central

Data Migration and Replication to Employee Central PUBLIC 247
2.2.2.8.1.2 Enabling Connection of Multiple Employee Central
Instances to SAP S∕4HANA

Set a constant to enable the connection of multiple Employee Central instances to the same client of your SAP
S∕4HANA system.

Prerequisites

If you use the external assignment ID, you must congure your business rules in Employee Central in a way that the
external assignment ID is unique across Employee Central instances.

Context

Enabling the constant is only one step in a setup process. Refer to Related Information and ensure that you perform
all required steps in the correct order.

Procedure

1. Go to Customizing for the Business Integration Builder and choose Data Replication from Employee Central
Basic Settings Maintain Constant Values for Data Replication from EC .
2. Choose New Entries and select the ERP to EC/EC to ERP: Connect Multiple EC Instances constant.
3. Enter X in the Constant Value eld.

Results

Enabling the constant results in the following changes in your SAP S∕4HANA system:

• The SAP S∕4HANA systems adds the Employee Central instance during migration in the employee key
mapping table. We provide the Prepare Multiple EC Instances (ECPAO_PREPARE_MULT) transaction for you
to add your Employee Central instance to the records in these tables that already existed before you enabled
the constant.
• The conguration Assign Employee Central Instance to Company Code is checked during employee migration
to ensure that the employment (PERNR) is migrated to the intended Employee Central instance.
• Application logs are enhanced to display the Employee Central instance that was used for extraction.

Implementing Data Migration and Replication to Employee Central

248 PUBLIC Data Migration and Replication to Employee Central
2.2.2.8.1.3 Connecting New Employee Central Instances to SAP
S∕4HANA

Connect additional Employee Central instances to the same client of your SAP S∕4HANA system.

Prerequisites

You need to decide whether you have the need for multiple Employee Central, single ERP landscape and then set
the ERP to EC/EC to ERP: Connect Multiple EC Instances constant accordingly in the constants table. This feature
should not be enabled in the middle of the migration process.

Run the Prepare Multiple EC Instances (ECPAO_PREPARE_MULT) transaction to add the ID of your existing
Employee Central instance in the employee key mapping table.

Procedure

1. Create a new Employee Central instance ID in Customizing for the Business Integration Builder under
Prerequisites Specify Employee Central Instance ID .
2. Set up the migration for this Employee Central instance.
To do so, perform at least the following steps:
a. Import the metadata from Employee Central.
b. Create a new transformation template group and transformation templates.
c. Dene the eld mapping.
d. Dene a new logical port if you don't want to use the default logical port to address the outbound web
services for your new Employee Central instance.
e. Ensure that the customizing activity Assign Employee Central Instance to Company Code is complete by
assigning the Employee Central instance with the company code.
3. Trigger the extraction process for the employee by ensuring that the right transformation template group ID
(based on the associated Employee Central instance) is used.

Results

Extraction process updates the employee key mapping table with the Employee Central instance details. The
extraction process uses the Assign Employee Central instance to company code congurations to ensure that
the employment (PERNR) is migrated to the intended Employee Central instance. Based on this conguration, a
validation is introduced to identify if the transformation template group used for this extraction is relevant for the
PERNR which is extracted or not.

For the additional employments of existing employees, the Employee Central instance is determined also from
this conguration and migration is allowed only when the Employee Central instance matches with the Employee
Central instance used for the previous contracts.

Implementing Data Migration and Replication to Employee Central

Data Migration and Replication to Employee Central PUBLIC 249
Next Steps

Repeat the same steps for all Employee Central instances that you want to add.

2.2.2.8.1.4 Conguring Consumer Proxies and Logical Ports for

Connecting Multiple Employee Central Instances

Assign specic logical ports and consumer proxies to your Employee Central instance IDs if you want the SAP
S∕4HANA outbound web services to address dierent SAP Cloud Integration tenants for dierent Employee Central
instance IDs.

Context

The logical port enables multiple web services to be addressed logically. It is a conguration for a consumer proxy.
The consumer proxy acts as a local representation of a web service. The web service, in turn, provides an access
URL that is stored in the SAP S∕4HANA receiver of the corresponding integration ow in SAP Cloud Integration.

If you dene a logical port as default in the SOA Management (SOAMANAGER) transaction, it always addresses all
web services. This means that regardless of the Employee Central instance that you connect to SAP S∕4HANA, the
same integration ow with the same settings is always called in the middleware.

If you want to use separate SAP Cloud Integration instances with a specic conguration of the integration ows
for dierent Employee Central instances that you connect to the SAP S∕4HANA system, you can't use the default
logical port. Instead, you need to create specic logical ports for the dierent Employee Central instances and
assign the respective logical port to the corresponding Employee Central instance ID. You have the following
options:

• You use the default logical port for all connected Employee Central instances.
If all Employee Central instances and your SAP Cloud Integration tenant are running on the same data center,
we recommend that you use a default logical port. In this case, you don't need to make the settings described
here.
• You use the default logical port for one or more connected Employee Central instances and additionally create
one or more specic logical ports for other connected Employee Central instances.
• You don't use a default logical port and create one or more specic logical ports for all connected Employee
Central instances instead.

Procedure

1. Go to the Assign Logical Port to EC Instance (ECPAO_INSTANCE_LP) transaction in your SAP S∕4HANA system.
2. Choose New Entries.
3. Select your Employee Central instance.
4. Select the consumer proxy of the outbound web service that you want to use for this Employee Central
instance.

Implementing Data Migration and Replication to Employee Central

250 PUBLIC Data Migration and Replication to Employee Central
 5. Enter the logical port that you've created for this consumer proxy in the SOAMANAGER transaction.

Results

The SAP S∕4HANA system uses the default logical port for all combinations of Employee Central instance and
consumer proxy that you have not entered in the Assign Logical Port to EC Instance transaction. For all Employee
Central instances that you've entered in the transaction, it uses the logical port you specied to address the web
service dened by the consumer proxy.

Example

The following graphic shows an example where you use two SAP Cloud Integration tenants in two dierent data
centers. You set up a default logical port to connect to the rst SAP Cloud Integration tenant and a specic logical
port to connect to the second SAP Cloud Integration tenant.

Implementing Data Migration and Replication to Employee Central

Data Migration and Replication to Employee Central PUBLIC 251
Next Steps

The entries you make in the Assign Logical Port to EC Instance transaction are client-specic. You can't transport
these entries. Make the entries separately in all test and production clients in which you need them.

2.2.2.8.1.5 How Multiple Employee Central Instance behave in

Single and Multiple Employments

Understand how multiple Employee Central instances behave during a single or multiple employment of an
employee.

Consider the following scenario:

Company Code EC Instance ID

DE01 ECInstance1

DE02 ECInstance2

US01 ECInstance3

* ECInstance4

Assuming that the above conguration is maintained in the Dene Employee Data Settings for Employee Central
Company Customizing activity (view V_ECPAO_CMPNY_EE), then following scenarios works as described:

Scenario 1: Single employment: PERNR 1 (DE01)

When you trigger the extraction process for an employee having a single employment associated with company
code DE01, infoporter tool validates whether the transformation template group ID being used is associated with
the Employee Central instance that is same as the one based on the company code assignment. The employee
migration is allowed in case the transformation template group associated with ECInstance1 is used. In case a
dierent transformation template group associated with a dierent Employee Central instance is used for E.g.
ECInstance2, then the validation prevents this employee from getting migrated.

Scenario 2: Single employment with Organizational reassignment: PERNR 1 (DE02 -> DE03)

When an employee is having a single employment associated with multiple company code DE02 and DE03, then
the infoporter tool checks the latest company code assignment to determine the associated Employee Central
instance ID. Then the logic traverses back to the previous time periods in infotype 0001, and derives the company
code assignment and checks whether the company code is also associated with the same Employee Central
instance ID. If both are not matching as in this instance, then the employee data is extracted from starting from
the latest active time split from infotype 0001. Additionally assignment-specic full transmission start date is also
updated with this new cut over date. However, if dierent company code assignments are associated with the same
Employee Central instance ID then we do not shift the cut over date.

Scenario 3: Multiple employments - Global Assignment: PERNR 1 (DE01) / PERNR 2 (US01)

When an employee has multiple employments associated with dierent company codes and each associated
with dierent Employee Central instance ID, then in such case employee migration is not supported. Employee
migration is supported only if all the company code assignments across multiple employments are associated with
the same Employee Central instance ID. It follows the paradigm one CP (all employments) can be sent to only one
Employee Central instance.

Implementing Data Migration and Replication to Employee Central

252 PUBLIC Data Migration and Replication to Employee Central
Scenario 4: Multiple employments - Concurrent Employment: PERNR 1 (US01) / PERNR 2 (US01)

When an employee has multiple employments associated with the same company codes and in turn the same
Employee Central instance ID, then in such cases employee migration is supported.

Scenario 5: Handling of Single PERNR with multiple company code and future dated changes

When an employee has a company code assignment related changes for future time periods, in such cases if the
associated Employee Central instance ID for the future dated record is dierent than that of the valid as of today,
then the employee cannot be migrated.

2.2.2.8.2 Supporting the Migration of Long Term Absence

Records

Learn how to congure the migration of the long term absence leave record.

Prerequisites

You will have to create two new event reasons of event type DATACHG and status paid or un-paid leave in Employee
Central.

 Example

• PSEUDO_DATACHG_LOA_START
• PSEUDO_DATACHG_LOA_END

Context

Irrespective of the switch (When Time O or Time O for Leave of Absence Only) status the job info records with
event reason corresponding to leave of absence (LOA) cannot be imported to Employee Central. You need to
use the MDF object EmployeeTime and create the leave of absence dates and time period for a particular user
through the Import and Export data tool. This will inturn create the LOA events (LOA start and LOA end) in the
job information as per congurations. These events will be appearing in the job info as part of sync jobs from
EmployeeTime Object (parent object).

For more information, refer to3228287 .

Procedure

1. In your SAP S∕4HANA system, go to the (SPRO) transaction and choose SAP Reference IMG. In
the SAP Customizing Implementation Guide structure, open Personnel Management Integration with

Implementing Data Migration and Replication to Employee Central

Data Migration and Replication to Employee Central PUBLIC 253
 SuccessFactors Employee Central Business Integration Builder Data Migration and Replication to Employee
Central Employee Data Dene Field Mapping for Employee Data .
2. Choose the transformation template group that you are using.
3. Choose transformation template corresponding to Job Info (WS_4).
4. In the Primary mapping screen, double click the Event reason eld.
5. In the value mapping section, click the Dene value mapping entries button.
6. In the Value Mapping Details view, for the ERP value corresponding to Leave of Absence and Return to work,
maintain the new event reasons (Eg: PSEUDO_DATACHG_LOA_START and PSEUDO_DATACHG_LOA_END)
created in Employee Central.
7. Save the changes.
8. Run the migration report for the employee. Run the migration as often as needed until the nal run before the
Go-live. After all the migration is done, you can use the Import and Export Data tool to create the Employee
Time Object containing the leave of absence information. After the import, as per congurations in your
system, the job info shall show the PSEUDO_DATACHG_LOA_START and the actual LOA START events.

 Note

• If you run the migration again after importing the absent data, there is a problem. Infoporter always
runs in the full purge, hence it would be overwritten and the generated LOA events will be erased.
Hence you should always complete the migration runs and import the absences post migration only.
• In case you are running a replication from EC to ERP again, you need to follow the below steps when
doing the replication to ERP:
1. The value mapping details for MASSN congured for EC to ERP replication has to be changed. For
this direction of replication, the actual event reason LOA_START has to be mapped to the action
with semantic Start of LOA and the event reason LOA_END has to be mapped to the action with the
semantic End of LOA. With this there should be no change in IT 0000.
2. The two pseudo event reason that was created PSEUDO_LOA_DATACHG_START and
PSEUDO_LOA_DATACHG_END should not be mapped (delete them from value mapping details).
This will skip these records in replication. This will ensure that both IT 0000/IT 0302 are not
changed when replicating the data back to ERP. If you donot skip and still do a mapping for this as
well, then an additional record would be created in IT0302.

2.2.2.8.3 Supporting the Replication of an Employee Who Had

a Prehire Record in SAP S∕4HANA

Learn how to migrate employees who have prehire record in ERP.

Prerequisites

• You will have to create a new event reason PSEUDO_HIRE_AFTER_PREHIRE of event type HIRE with the status
Active.
• Prehire action type in ERP should have employment status as 1.

Implementing Data Migration and Replication to Employee Central

254 PUBLIC Data Migration and Replication to Employee Central
Context

In ERP, you can use a prehire record before the actual hiring happens. This is to ensure that the newly hired
employees are only considered in the payroll run if they complete the hiring or joining process. In Employee
Central, hiring is always considered as the rst event. The extraction report has a specic logic to identify and
lter the prehire record of the employee and migrate rest of the employee information using special event reasons.
Additionally, the extraction report also updates the personal full transmission start date (FTSD) for the PERNR with
the actual hire date for end-to-end process to work without any issues.

Procedure

1. In your SAP S∕4HANA system, go to the (SPRO) transaction and choose SAP Reference IMG. In
the SAP Customizing Implementation Guide structure, open Personnel Management Integration with
SuccessFactors Employee Central Business Integration Builder Data Migration and Replication to Employee
Central Employee Data Dene Field Mapping for Employee Data .
2. Choose the transformation template group that you are using.
3. Choose transformation template corresponding to Job Info (WS_4).
4. In the Primary mapping screen, double click the Event reason eld.
5. In the value mapping section, click the Dene value mapping entries button.
6. In the Value Mapping Details view, for the ERP value corresponding to the action type denoting the HIRE after
the prehire action type, maintain any new custom event reasons of type HIRE.

 Note

This event reason should be dierent from the regular HIRE event reason to distinguish between the two
types of hire event reasons when replicating the data back to ERP.

 Example

If UR is your action for the hire and you have a event reason for this case
as HIRE_AFTER_PREHIRE, then maintain the value mapping details as below example:

7. Save the changes.

8. Run the migration report for the employee.

Behaviour of Infoporter for an employee who has prehire and the hire action types before earlier transfer date,
during the migration without using the concept of additional events:

Implementing Data Migration and Replication to Employee Central

Data Migration and Replication to Employee Central PUBLIC 255
 • On the cuto date, the new event reason PSEUDO_HIRE_AFTER_PREHIRE to be sent to Employee Central.
• The personal FTSD date is updated with the original hire date.

Behaviour of Infoporter for an employee who has prehire and the hire action types after earlier transfer date,
during the migration without using the concept of additional events:
• The event reason for the hire records are fetched as per the conguration maintained in step 6.
• The personal FTSD date is updated with the original hire date.

Behaviour of Infoporter for an employee who has prehire and the hire action types before the earlier transfer
date, during the migration using the concept of additional events:
• The event reason for the hire records are fetched as per the conguration maintained in additional events
conguration table V_ECPAO_PLHD_ACT.
• The personal FTSD date is updated with the original hire date.

As seen in the above cases, the extraction report updates the table PAOCFEC_PN_FTSD with the actual hire
date as the personal FTSD date. This is done so that while replicating back to ERP, the replication process
should not fail because of the existing prehire records in Action Infotype(PA0000). Updating the personal
FTSD ensures that the replication back to ERP happens only beyond this date.

 Note

• During replication the constant switch EC to ERP (BIB): Ignore Action If T529A Feature Raises Error
should be enabled to avoid replication error thrown by PA framework based on the settings of T529A.
• For replication the event PSEUDO_HIRE_AFTER_PREHIRE should be mapped to the action type
corresponding to the hire action that is allowed to take place after the prehire action type. As per
our example in point 6, the PSEUDO_HIRE_AFTER_PREHIRE should also be mapped to action type UR.

Implementing Data Migration and Replication to Employee Central

256 PUBLIC Data Migration and Replication to Employee Central
2.2.2.8.4 Supporting Migration of Work Permit Entity

Read about the congurations that are done to migrate the work permit entity.

Work permit entity is not a standard entity that is supported with Infoporter tool. However you could congure this
and use the work permit entity. With service layer, work permit has Country, Document Type, Document Number,
User ID, and Issue date eld as business key.

Following ERP congurations are valid when the below settings are enabled in Employee Central.

Conguration changes:

• Employee Central settings:

1. Go to Admin Center Company System and Logo Settings .
2. Disable Exclude Issue Date from Work Permit Business Keys in OData API EmpWorkPermit.
3. Enable Enable Centralized Services for Work Permit to save changes on Editing UI.
4. Enable Enable validations on the Work Permit Editing UI.
• ERP congurations:
Workpermit in general is non-eective dated. However with issue date coming as part of business key, it is
possible to have date specic information.
As per standard integration code when eective date checkbox is unchecked at the entity conguration
(V_ECPAO_ECTMPL), it is treated as non eective dated and always fetches only one record that is active as of
the system date.
Inorder to x the work-permit with multiple issue dates, we had to congure as Eective dated. Only then all
the date records (past) will be fetched.

Implementing Data Migration and Replication to Employee Central

Data Migration and Replication to Employee Central PUBLIC 257
Once you do the above mentioned congurations in the eld mapping, the migration of the work permit could be
done successfully.

2.2.2.8.5 Extracting Third Gender

Learn how third gender is supported when migrating the data to EC using infoporter tool .

Context

Employee Central now supports a new country-specic gender eld for employees and dependents based on legal
requirement of specic countries. Hence you will have to congure the metadata, picklists, and the BIB mapping to
send the gender eld IT0002-GESCH to the gender eld of global information entity.

If the gender value in Infotype 0002 is Male or Female, then this value should be populated to both the gender eld
in Personal Info and country specic gender eld in the Global Info entity for the corresponding country.

For example: If the gender value in Info type 2 is a country-specic gender value like Transgender for India, then this
value should be sent to the new gender eld in the Global Info and in Personal Info it will be shown as Others.

You can check on view V_T77PAD_GENDER for the support of third gender in ERP for the countries in scope of
migration. Based on this information, you could congure to use this setup.

Employee Central supports third gender for the following countries.

No Supported Countries

1 Argentina

2 Austria

3 Brazil

4 Canada

5 Chile

6 France

7 Germany

Implementing Data Migration and Replication to Employee Central

258 PUBLIC Data Migration and Replication to Employee Central
 No Supported Countries

8 India

9 Italy

10 New Zealand

11 USA

12 Venezuela

Procedure

1. Import the metadata of the global info entity of the required country.

Update metadata of global info entity (PerGlobalInfoIND entity).

 Note

WS_18_IND is provided as a standard entity for country India. You can create custom EC entities for the
required countries.

2. Import the picklist corresponding to the countryspecicgender eld into ERP.

3. Congure the value mapping entities in the Dene Value Mapping Entities Customizing step (view
V_ECPAO_VALUENTY).

Primary mapping details - WS5. In the below example for country India, for the Personal Info Entity, the
mapping of the gender shall be either Male or Female and for all other values it could be marked as Others.

Implementing Data Migration and Replication to Employee Central

Data Migration and Replication to Employee Central PUBLIC 259
 Value mapping details - WS5

Implementing Data Migration and Replication to Employee Central

260 PUBLIC Data Migration and Replication to Employee Central
 Primary mapping details - WS18. For the global information entity, the country-specic gender could provide
the actual value of third gender as in the below screenshots. The same infotype eld IT0002-GESCH is mapped
and a dierent value mapping entity is used to dierentiate the gender mapping of Personal Info Entity and
Global Info Entity.

Implementing Data Migration and Replication to Employee Central

Data Migration and Replication to Employee Central PUBLIC 261
 Value mapping details - WS18

Implementing Data Migration and Replication to Employee Central

262 PUBLIC Data Migration and Replication to Employee Central
2.2.2.8.6 How to update the Time Prole elds in Job
information

In this section, you will nd the steps to be followed if you would want to update the time prole elds of job
information when you migrate the employee data.

Some prerequisites need to be ullled if you want to use replication of absence data from Employee Central to SAP
S∕4HANA together with Employee Central Time O. For more information refer the Replicating Employee Time Data
from Employee Central to SAP S∕4HANA integration guide.

Creating a Business Rule [page 264]

Learn how to create a business rule.

Assigning the Business Rules [page 265]

The Business Conguration UI (BCUI) allows you to assign rules to HRIS elements and elds to trigger
events.

Checking the Company Code Mapping [page 266]

Cross check if the rule is congured with the company code that you are dealing in migration.

Conguring the Transformation Template Group for Adding Time Prole Fields [page 269]
Learn how to congure the transformation template group to add the time prole elds sent from ERP.

Related Information

Implementing Point-to-Point Time Data Replication

Implementing Data Migration and Replication to Employee Central

Data Migration and Replication to Employee Central PUBLIC 263
2.2.2.8.6.1 Creating a Business Rule

Learn how to create a business rule.

Context

You create a business rule in Employee Central to ll the following elds of the Job Information entity with default
values when the rule is successfully executed for an employee:

• Holiday Calendar
• Work Schedule
• Time Prole
• Time Recording Variant
• Time Recording Prole
• Time Recording Admissibility
• Default Overtime Compensation Variant

Procedure

1. Go to the Admin Center and choose the Congure Business Rules tool.
2. Create a business rule based on your requirements.

Implementing Data Migration and Replication to Employee Central

264 PUBLIC Data Migration and Replication to Employee Central
 Ex:

Task overview: How to update the Time Prole elds in Job information [page 263]

Related Information

Assigning the Business Rules [page 265]

Checking the Company Code Mapping [page 266]
Conguring the Transformation Template Group for Adding Time Prole Fields [page 269]

2.2.2.8.6.2 Assigning the Business Rules

The Business Conguration UI (BCUI) allows you to assign rules to HRIS elements and elds to trigger events.

Context

In order to trigger the rule, you will have to assign the previously created business rule.

Implementing Data Migration and Replication to Employee Central

Data Migration and Replication to Employee Central PUBLIC 265
Procedure

1. Go to Admin Center Manage Business Conguration .

2. Go to Employee Central HRIS Elements and choose the HRIS element jobInfo for Job Information to
assign the rule as a OnSave rule.

3. Save our changes.

Task overview: How to update the Time Prole elds in Job information [page 263]

Related Information

Creating a Business Rule [page 264]

Checking the Company Code Mapping [page 266]
Conguring the Transformation Template Group for Adding Time Prole Fields [page 269]

2.2.2.8.6.3 Checking the Company Code Mapping

Cross check if the rule is congured with the company code that you are dealing in migration.

Procedure

1. In your SAP S∕4HANA system, go to the Maintain HR Master Data (PA30) transaction.
2. Search for the employee whose data you want to replicate to Employee Central.

Implementing Data Migration and Replication to Employee Central

266 PUBLIC Data Migration and Replication to Employee Central
 Maintain HR Master Data Transaction
3. Display the Organizational Assignment (0001) infotype and check the value stored in the Company Code eld.

Implementing Data Migration and Replication to Employee Central

Data Migration and Replication to Employee Central PUBLIC 267
 Company Code in the Organizational Assignment Infotype
4. Go to the Dene Value Mapping Details Customizing activity and check if this company code (stored in the ERP
Key eld) is mapped to the company (stored in the EC Key eld) that is congured in your business rule.

For more information about value mapping, 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.

Company Codes Mapping

Implementing Data Migration and Replication to Employee Central

268 PUBLIC Data Migration and Replication to Employee Central
  Caution

In Employee Central, the company is represented by an instance of the Legal Entity foundation object. Make
sure that both the legal entity code in Employee Central and the Employee Central key that you specify in
the value mapping Customizing are in upper case.

Task overview: How to update the Time Prole elds in Job information [page 263]

Related Information

Creating a Business Rule [page 264]

Assigning the Business Rules [page 265]
Conguring the Transformation Template Group for Adding Time Prole Fields [page 269]

2.2.2.8.6.4 Conguring the Transformation Template Group for

Adding Time Prole Fields

Learn how to congure the transformation template group to add the time prole elds sent from ERP.

Context

Procedure

1. Go to the Dene Field Mapping for Employee Data Customizing activity.

For more information about the Customizing settings, refer the Replicating Employee Data from SAP ERP HCM
to Employee Central integration guide.
2. Go to the Primary Mapping view of your transformation template corresponding to WS_4 (Job information) and
add the time prole elds sent from ERP.

 Note

• You don't have to ll other elds with content from SAP S∕4HANA since the business rule you have
created in Employee Central provides the values for these elds.
• You can map the Work Schedule to IT0007 - SCHKZ to map from ERP or else you can consider this
eld as well in your business rule and assign as like other elds.
• We recommend you not to activate the business rules during the initial load. Delta migration shall be
carried out to enable the business rules to be run.

Implementing Data Migration and Replication to Employee Central

Data Migration and Replication to Employee Central PUBLIC 269
Task overview: How to update the Time Prole elds in Job information [page 263]

Related Information

Creating a Business Rule [page 264]

Assigning the Business Rules [page 265]
Checking the Company Code Mapping [page 266]

2.3 Organizational Data

2.3.1 Replicating Organizational Data from SAP S∕4HANA to

Employee Central

This section describes in detail which steps need to be carried out when you want to replicate data from SAP
S∕4HANA to Employee Central to use Employee Central as your system of record.

 Caution

Make sure that data that is mastered in SAP S∕4HANA and replicated to Employee Central can't be edited
in Employee Central. Use role-based permissions to disable the edit mode in Employee Central based, for
example, on the legal entity of the employee.

 Note

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 data model. Therefore, you can't replicate
organizational data with time constraint 3 from SAP S∕4HANA to Employee Central.

For Which Organizational Data-Related Employee Central Entities Can I Use Data Replication? [page 271]
By default, you can use the Employee Central entities that are listed below.

Communication Channels for Organizational Data Replication [page 272]

You can transfer data from SAP S∕4HANA to Employee Central using dierent communication channels.

Steps in the SAP S∕4HANA System [page 275]

In the next sections we'll go step by step through all activities you need to carry out in the SAP S∕4HANA
system to make data replication work.

Extensibility of the Integration [page 341]

Data Replication and Mapping Information [page 346]

Implementing Data Migration and Replication to Employee Central

270 PUBLIC Data Migration and Replication to Employee Central
2.3.1.1 For Which Organizational Data-Related Employee
Central Entities Can I Use Data Replication?

By default, you can use the Employee Central entities that are listed below.

You can also replicate data to custom generic objects.

Organizational Data Entities Supported by Data Replication

Template Used for Template Used for

CSV-Based Data Ex- Web Service-Based
Employee Central En- traction in SAP Data Extraction in SAP Type of Data in Em- Type of Entity in Em-
tity S∕4HANA S∕4HANA ployee Central ployee Central

Position Position (CSV_OM_POS) Position (WS_OM_POS) Foundation data Generic object

New template name

that has been added for
position matrix relation-
ship is CSV_OM_PMR &
WS_OM_PMR.

Job classication JOB_CLASSIFICATIONI FOJobCode Foundation data Generic object (job-re-

mportTemplate (WS_OM_JOB) lated object)
(CSV_OM_JOB)

Department DEPARTMENTImportTe FODepartment Foundation data Generic object (organi-

mplate (CSV_OM_DEP) (WS_OM_DEP) zation object)

Division DIVISIONImportTempla FODivision Foundation data Generic object (organi-

te (CSV_OM_DIV) (CSV_OM_DIV) zation object)

Business unit BUSINESS_UNITImport FOBusinessUnit Foundation data Generic object (organi-

Template (WS_OM_BUS) zation object)
(CSV_OM_BUS)

 Note

In all Employee Central entities listed above there are standard mappings which are predened by the SAP
S∕4HANA system. You can't congure them while dening primary mappings in the transformation template
group conguration.

Since business units, divisions, and departments all map to organizational units in the SAP S∕4HANA system,
you need to make additional settings if you want to use all three templates referring to these object types in one
transformation template group.

Parent topic: Replicating Organizational Data from SAP S∕4HANA to Employee Central [page 270]

Implementing Data Migration and Replication to Employee Central

Data Migration and Replication to Employee Central PUBLIC 271
Related Information

Communication Channels for Organizational Data Replication [page 272]

Steps in the SAP S∕4HANA System [page 275]
Extensibility of the Integration [page 341]
Data Replication and Mapping Information [page 346]

2.3.1.2 Communication Channels for Organizational Data

Replication

You can transfer data from SAP S∕4HANA to Employee Central using dierent communication channels.

• Using CSV-based template les and the manual import framework in Employee Central
To use the manual import framework, go to the Admin Center and choose the Import and Export Data tool.
• Using a synchronous Web service call and the middleware that is available for data transfer from SAP S∕4HANA
to Employee Central

CSV File-Based Organizational Data Extraction

To extract organizational data from SAP S∕4HANA into CSV-based templates, make these settings for the
Organizational Data Extraction (ECPAO_OM_OBJECT_EXTRACTION) program:

• Choose a transformation template group that uses the CSV File-Based Transfer communication channel.
• Choose the communication channel File Transfer Use Server Path or File Transfer Use Local Drive
Path .

 Note

When you schedule the program as a background job to carry out a mass data extraction, always choose
the File Transfer Use Server Path option.

The download log le shows all the success, error, and warning messages. It will also include the number of les
that were downloaded and from where the le is downloaded from. An additional authorization is performed to
check if the user has the rights to download the CSV le.

Implementing Data Migration and Replication to Employee Central

272 PUBLIC Data Migration and Replication to Employee Central
 Selection Settings for CSV File-Based Organizational Data Extraction

Web Service-Based Organizational Data Extraction

To transfer organizational data using a synchronous web service call, make these settings for the Organizational
Data Extraction (ECPAO_OM_OBJECT_EXTRACTION) program:

• Choose a transformation template group that uses the Web Service Transfer communication channel.
• Choose the communication channel Web Service Transfer.

Implementing Data Migration and Replication to Employee Central

Data Migration and Replication to Employee Central PUBLIC 273
 Selection Settings for Web Service-Based Organizational Data Extraction

Parent topic: Replicating Organizational Data from SAP S∕4HANA to Employee Central [page 270]

Related Information

For Which Organizational Data-Related Employee Central Entities Can I Use Data Replication? [page 271]
Steps in the SAP S∕4HANA System [page 275]
Extensibility of the Integration [page 341]
Data Replication and Mapping Information [page 346]

Implementing Data Migration and Replication to Employee Central

274 PUBLIC Data Migration and Replication to Employee Central
2.3.1.3 Steps in the SAP S∕4HANA System

In the next sections we'll go step by step through all activities you need to carry out in the SAP S∕4HANA system to
make data replication work.

 Note

All employee infotypes (both standard PA infotype and non-standard PA infotype) are allowed to be congured
in the Business Integration Builder framework. These infotypes are indicated by the PAPD eld value "X" in the
table T777D. In the employee migration/integration only the standard PA infotypes which has prex "PA" in the
database table names are supported. Any elds mapped to the non-standard PA infotypes will be not extracted
and hence will be ltered out in the migration/integration scenario.

Preparatory Steps [page 275]

Dening Value Mappings [page 302]

Value mapping means that Employee Central eld values are mapped to values of SAP S∕4HANA elds.

Mapping Organizational Data to Table Infotype [page 312]

You want to map the table infotype in the view cluster to support the migration process.

Particular Mapping Types [page 314]

Data Extraction and Transfer [page 320]

Parent topic: Replicating Organizational Data from SAP S∕4HANA to Employee Central [page 270]

Related Information

For Which Organizational Data-Related Employee Central Entities Can I Use Data Replication? [page 271]
Communication Channels for Organizational Data Replication [page 272]
Extensibility of the Integration [page 341]
Data Replication and Mapping Information [page 346]

2.3.1.3.1 Preparatory Steps

Accessing the Customizing Structure in the SAP S∕4HANA System [page 277]
To dene customer-specic settings, you use the Customizing activities and Business Add-Ins (BAdIs) in
the integration of SAP S∕4HANA and SAP SuccessFactors Employee Central (ECS4HCM) add-on.

Importing Metadata from Employee Central [page 278]

You import the metadata from SAP SuccessFactors Employee Central to make Employee Central elds
available in the SAP S∕4HANA system so that you can use them for eld mappings.

Conguring Replication of Language-Dependent Fields Between Employee Central and SAP S∕4HANA [page
285]

Implementing Data Migration and Replication to Employee Central

Data Migration and Replication to Employee Central PUBLIC 275
 Congure the replication of texts (such as names or descriptions of organizational objects) between SAP
S∕4HANA and Employee Central.

Transferring Language-Dependent Fields [page 288]

Make the settings required to enable transfer of texts (such as names or descriptions of business units)
between SAP S∕4HANA and Employee Central.

Dening Organizational Data-Related Settings for Your Employee Central Company [page 294]
Make additional settings for the Employee Central instance you've dened before in the
Dene Organizational Data Settings for Employee Central Company Customizing activity (view
V_ECPAO_CMPNY_OM).

Dening Custom Employee Central Entities for Organizational Data Entities [page 294]
An Employee Central entity represents an entity from Employee Central, such as a CSV data import
template or a generic object (also known as MDF entity). You only need to dene custom Employee Central
entities if you want to transfer data from SAP S∕4HANA to an Employee Central entity for which SAP hasn't
provided a default template.

Dening Field Mapping for Organizational Data [page 297]

To enable the data extraction programs to extract the right SAP S∕4HANA information for the right
Employee Central elds, you need to map SAP S∕4HANA elds to Employee Central elds.

Parent topic: Steps in the SAP S∕4HANA System [page 275]

Related Information

Dening Value Mappings [page 302]

Mapping Organizational Data to Table Infotype [page 312]
Particular Mapping Types [page 314]
Data Extraction and Transfer [page 320]

Implementing Data Migration and Replication to Employee Central

276 PUBLIC Data Migration and Replication to Employee Central
2.3.1.3.1.1 Accessing the Customizing Structure in the SAP
S∕4HANA System

To dene customer-specic settings, you use the Customizing activities and Business Add-Ins (BAdIs) in the
integration of SAP S∕4HANA and SAP SuccessFactors Employee Central (ECS4HCM) add-on.

In your SAP S∕4HANA system, go to the Customizing: Execute Project (SPRO) transaction and choose SAP
Reference IMG. In the SAP Customizing Implementation Guide structure, open Personnel Management
Integration with SuccessFactors Employee Central Business Integration Builder :

Overview of Customizing Structure

In the Customizing structure, you can nd detailed information for each Customizing activity and BAdI:

Details of Customizing Structure

The next sections describe the steps you need to carry out in the SAP S∕4HANA system.

Parent topic: Preparatory Steps [page 275]

Implementing Data Migration and Replication to Employee Central

Data Migration and Replication to Employee Central PUBLIC 277
Related Information

Importing Metadata from Employee Central [page 278]

Conguring Replication of Language-Dependent Fields Between Employee Central and SAP S∕4HANA [page 285]
Transferring Language-Dependent Fields [page 288]
Dening Organizational Data-Related Settings for Your Employee Central Company [page 294]
Dening Custom Employee Central Entities for Organizational Data Entities [page 294]
Dening Field Mapping for Organizational Data [page 297]

2.3.1.3.1.2 Importing Metadata from Employee Central

You import the metadata from SAP SuccessFactors Employee Central to make Employee Central elds available in
the SAP S∕4HANA system so that you can use them for eld mappings.

To import metadata, use one of the following programs:

• Import of Metadata from Employee Central Using XML File (ECPAO_ECTMPL_METADATA_WRITER)

This program is available in the Import Metadata for Web Service-Based Data Transfer from Employee Central
Customizing activity.

 Note

You can only use this program to import metadata for web service entities. If you want to import metadata
for CSV le-based entities, use the Import of Metadata from Employee Central program instead.

• Import of Metadata from Employee Central (ECPAO_ECFLD_METADATA_WRITER)

This program is available in the Import Metadata for File-Based Data Transfer from Employee Central
Customizing activity.

 Note

You can only use this program to import metadata for CSV le-based entities. If you want to import
metadata for web service entities, use the Import of Metadata from Employee Central Using XML File
program instead.

Parent topic: Preparatory Steps [page 275]

Related Information

Accessing the Customizing Structure in the SAP S∕4HANA System [page 277]
Conguring Replication of Language-Dependent Fields Between Employee Central and SAP S∕4HANA [page 285]
Transferring Language-Dependent Fields [page 288]
Dening Organizational Data-Related Settings for Your Employee Central Company [page 294]
Dening Custom Employee Central Entities for Organizational Data Entities [page 294]

Implementing Data Migration and Replication to Employee Central

278 PUBLIC Data Migration and Replication to Employee Central
Dening Field Mapping for Organizational Data [page 297]

2.3.1.3.1.2.1 Importing Metadata for Web Service-Based Data

Transfer

Use the Import of Metadata from Employee Central Using XML File (ECPAO_ECTMPL_METADATA_WRITER) program
to import metadata for web service-based data transfer.

Context

Using this program, you can import entries as well as delete entries you have imported for a specic Employee
Central instance and template.

 Caution

You can't delete metadata in the SAP S∕4HANA system that you have already used for eld mappings.
Otherwise your mappings become invalid. You are shown an error message if you try to delete metadata that is
used for eld mappings.

Procedure

1. Download the metadata that you want to import from Employee Central.
1. Go to the Admin Center and choose the OData API Metadata Refresh and Export tool.

OData API Metadata Refresh and Export Tool

2. To make sure that the metadata is up to date choose Refresh.
3. Choose Export for the Export Metadata to File option.
4. Store the metadata le in the XML format on a server or on your local disk.

 Note

API tools need to be enabled in Provisioning.

Implementing Data Migration and Replication to Employee Central

Data Migration and Replication to Employee Central PUBLIC 279
  Remember

As a customer, you don't have access to Provisioning. To complete tasks in Provisioning, contact
your implementation partner or Account Executive. For any non-implementation tasks, contact Product
Support.

 Note

When a new eld is added in Employee Central, you will have to re-import the metadata report and re-run
the report once again.

2. On the selection screen of the program, specify which metadata you want to import to SAP S∕4HANA and from
which le you want to upload it:

Selection Screen of the ECPAO_ECTMPL_METADATA_WRITER Program

 Note

If you don't specify a specic Employee Central entity, the metadata is imported for all Employee Central
entities that are available and use the Web Service Transfer communication channel.

3. Optional: Carry out a test run of the program to check the data that will be uploaded to SAP S∕4HANA.
4. Clear the Test Run checkbox and execute the program to upload the data from the Employee Central metadata
le into the EC Entity Field Mapping (ECPAO_FLD) table.

If you run the program in a test system or client with the Test Run checkbox deselected, the program asks for
a transport request, to which the imported metadata will be assigned. Using this request you can transport the
entries to the productive system or client.

 Note

The standard elds are also uploaded into the EC Entity Field Mapping table. In this table, the Is Standard
Field (IS_FLD_STANDARD) ag is set for these elds. Since a standard mapping is dened for them, they
are not available in the Customizing of the transformation template groups.

Implementing Data Migration and Replication to Employee Central

280 PUBLIC Data Migration and Replication to Employee Central
 5. Optional: To delete the entries you have imported for the Employee Central instance and template that you
have specied on the selection screen, select the Delete Metadata checkbox and execute the program. This will
make sure that the WS based and File based transfer will be consistent.
6. Check the metadata that you have imported in the Transport Imported Metadata and Check Metadata for
File-Based Data Transfer Customizing activity.

 Tip

For details about which information about the Employee Central elds exactly is imported by the
program, see the program documentation in your SAP S∕4HANA system. You'll nd a link to the program
documentation in the documentation of the Import Metadata for Web Service-Based Data Transfer from
Employee Central Customizing step.

Transport Imported Metadata and Check Metadata for File-Based Data Transfer

 Note

Don't make any changes to the metadata in this Customizing view. Use the metadata import program to
update the entries in this view.

 Caution

If the Employee Central eld has Picklist ag is set for an imported Employee Central eld, you might need
to assign a value mapping entity when you dene a eld mapping for this Employee Central eld. Otherwise
the data extraction program might fail.

7. You can also store entries from this view on a transport request, for example, to transport them from your SAP
S∕4HANA test system to your productive system. To do so, choose Table View Transport .

Implementing Data Migration and Replication to Employee Central

Data Migration and Replication to Employee Central PUBLIC 281
2.3.1.3.1.2.2 Importing Metadata for File-Based Data Transfer

Use the Import of Metadata from Employee Central (ECPAO_ECFLD_METADATA_WRITER) program, to import
metadata for CSV le-based data transfer.

Context

Using this program, you can import entries as well as delete entries you have imported for a specic Employee
Central instance and template.

 Caution

You can't delete metadata in the SAP S∕4HANA system that you have already used for eld mappings.
Otherwise your mappings become invalid. You are shown an error message if you try to delete metadata that is
used for eld mappings.

Procedure

1. To download the metadata that you want to import from Employee Central, go to the Admin Center and choose
the following tools:

Metadata Download from Employee Central

For this type of entity in Employee Central ... You use this admin tool ...

Person and employment objects Choose the Import Employee Data tool, then choose
Download a blank CSV template

Foundation objects Choose the Import Foundation Data tool, then choose
Download a blank CSV template

Generic objects Choose the Import and Export Data tool, then select the
Export Data action

 Note

When a new eld is added in Employee Central, you will have to re-import the metadata report and re-run
the report once again.

2. On the selection screen of the program, specify which metadata you want to import to SAP S∕4HANA and from
which le you want to upload it:

Implementing Data Migration and Replication to Employee Central

282 PUBLIC Data Migration and Replication to Employee Central
 Selection Screen of ECPAO_ECFLD_METADATA_WRITER Program
3. Select the Update Metadata checkbox to import the metadata.
4. Optional: Carry out a test run of the program to check the data that will be uploaded to SAP S∕4HANA.
5. Clear the Test Run checkbox and execute the program to upload the data from the Employee Central metadata
le into the EC Entity Field Mapping (ECPAO_FLD) table or delete data from this table.

If you run the program in a test system or client with the Test Run checkbox deselected, the program asks for
a transport request, to which the imported metadata will be assigned. Using this request you can transport the
entries to the productive system or client.
6. Optional: To delete the entries you have imported for the Employee Central instance and template that you
have specied on the selection screen, select the Delete Metadata checkbox and execute the program.
7. Check the metadata that you have imported or deleted in the Transport Imported Metadata and Check
Metadata for File-Based Data Transfer Customizing activity.

 Tip

For details about which information about the Employee Central elds exactly is imported by the
program, see the program documentation in your SAP S∕4HANA system. You'll nd a link to the program
documentation in the documentation of the Import Metadata for Web Service-Based Data Transfer from
Employee Central Customizing step.

Implementing Data Migration and Replication to Employee Central

Data Migration and Replication to Employee Central PUBLIC 283
 Transport Imported Metadata and Check Metadata for File-Based Data Transfer

 Note

You might need to make some changes to the uploaded metadata in this view. For example:

• If a eld is a required eld in your Employee Central data model and you want the SAP S∕4HANA
system to validate the settings for this eld, select the Is Required checkbox.
• You might need to specify the data type for elds. For elds that contain a date, for example, choose
the datetime data type so that the content can be identied correctly.

 Caution

If you upload the metadata again, the changes you've made manually will be overwritten.

Don't select the Standard Field and Deleted checkboxes. These ags are set by the metadata import
program:

• The Standard Field ag is set for all elds that are considered to be standard elds. This means that a
standard mapping is dened and that the elds are not available in Customizing for eld mapping.
• Deleted eld means that the eld has become invalid since the last run of the program. This happens,
for example, if you've imported an Employee Central eld and dened a mapping for it. Now you delete
this eld in Employee Central and run the metadata import program again. The program recognizes
that the eld is missing in the new metadata import run and therefore sets this ag for it. Since the eld
no longer exists, your mapping becomes invalid.

If you select the EC Field Has Picklist checkbox for an imported Employee Central eld, you might need to
assign a value mapping entity when you dene a eld mapping for this Employee Central eld. Otherwise
the data extraction program might fail.

8. You can also store entries from this view on a transport request, for example, to transport them from your SAP
S∕4HANA test system to your productive system. To do so, choose Table View Transport .

Implementing Data Migration and Replication to Employee Central

284 PUBLIC Data Migration and Replication to Employee Central
2.3.1.3.1.3 Conguring Replication of Language-Dependent
Fields Between Employee Central and SAP
S∕4HANA

Congure the replication of texts (such as names or descriptions of organizational objects) between SAP S∕4HANA
and Employee Central.

Prerequisites

The language pack for an Employee Central locale must be enabled in Provisioning so that you can transfer texts in
the corresponding language.

 Remember

As a customer, you don't have access to Provisioning. To complete tasks in Provisioning, contact your
implementation partner or Account Executive. For any non-implementation tasks, contact Product Support.

Employee Central supports translations for position names, but not for position descriptions. Add a custom
description eld to the Position object denition in Employee Central if you want to replicate position descriptions
for multiple languages.

Context

To enable replication of texts, you rst map language-independent text elds. This mapping is used as a
placeholder. Additionally, you map the locales you use in Employee Central to the corresponding SAP S∕4HANA
languages. Based on this language mapping, the language-dependent eld mappings are then automatically
created and replace the placeholders when the data is extracted.

If you don't dene at least a language mapping for the default locale, no language-dependent data can be
transferred.

 Example

Let's say you try to replicate a new department from Employee Central to SAP S∕4HANA. This means that a
new record of the Object (1000) infotype needs to be created in the SAP S∕4HANA system. The Object infotype
needs a language. To determine the language to be used, the SAP S∕4HANA system reads the entries stored in
the V_ECPAO_LOCALE. If there aren't any entries here, the system doesn't know which language to use for the
infotype record. Therefore, the department can't be replicated. The corresponding replication request has the
status Pending.

Implementing Data Migration and Replication to Employee Central

Data Migration and Replication to Employee Central PUBLIC 285
Procedure

1. Go to Customizing for the Business Integration Builder and choose Data Migration and Replication to
Employee Central Organizational Data Map Languages from Employee Central and ERP or Data
Replication from Employee Central Organizational Objects Map Languages from Employee Central and
ERP .
2. Create a mapping for the default locale that you use in Employee Central.

Make sure that you use the correct format:

• The locale identier from Employee Central must consist of a language identier in lowercase and a
location or country/region identier in uppercase, linked by an underscore. For example: en_US (English,
USA), en_GB (English, UK), fr_FR (French, France), fr_CA (French, Canada).
• The language identier from SAP S∕4HANA must be a two-character country/region ISO code. For
example: EN, FR.

Let's say that your default locale is en_US. Therefore, you create the following mapping.

Employee Central Locale SAP S∕4HANA Language

en_US EN

3. Create mappings for all additional locales that your Employee Central instance supports for translation of texts.

Let's say your Employee Central instance also supports German (for Germany), Spanish (for Spain), French,
Italian, and Dutch. Therefore, you create the following entries.

Employee Central Locale SAP S∕4HANA Language

de_DE DE

es_ES ES

fr_FR FR

it_IT IT

nl_NL NL

 Note

If you use two locales for the same language in Employee Central (such as en_US and en_GB), you need
to decide which of these locales you want to map to SAP S∕4HANA. In SAP S∕4HANA, there's only one
language key you can map (in our example: EN).

4. Go to the Dene Organizational Data Settings for Employee Central Instance activity in the same customizing
structure.
5. Specify the default locale that you use in Employee Central.

The SAP S∕4HANA system uses the default locale, for example, when writing language-independent content,
such as IDs, to a language-dependent infotype, such as the Object (1000) infotype.

Implementing Data Migration and Replication to Employee Central

286 PUBLIC Data Migration and Replication to Employee Central
 The eld help in the Employee Central instance view shows the locales you've mapped in the rst step:
• en_US
• de_DE
• es_ES
• fr_FR
• it_IT
• nl_NL

You select en_US.

 Note

You can also carry out Dene Organizational Data Settings for Employee Central Instance as the rst step.
In this case, the eld help doesn't show any languages yet. You’re redirected to the Map Languages from
Employee Central and ERP customizing activity.

6. Go to the Dene Field Mapping for Organizational Data activity in the same customizing structure.
7. Create language-independent eld mappings for text elds.

The Use Language Mapping checkbox is automatically selected for these eld mappings. This means that the
SAP S∕4HANA system uses them as placeholders.

Let's say you dene the following placeholder mapping for department names.

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

name_defaultValue Infotype Mapping Object (1000) Object Name (STEXT)

 Note

Most organizational objects use name_defaultValue, but not positions. That's why the mapping looks
dierent for position names:

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

externalName_defaultValue Infotype Mapping Object (1000) Object Name (STEXT)

Results

Data transfer between Employee Central and SAP S∕4HANA automatically uses language-dependent eld
mappings instead of the placeholder mapping. There's no need to dene a mapping for the language-dependent
elds explicitly. In our example, the integration uses the following mappings.

Implementing Data Migration and Replication to Employee Central

Data Migration and Replication to Employee Central PUBLIC 287
 SAP S∕4HANA Info- SAP S∕4HANA Lan-
Employee Central Field Mapping Mode type SAP S∕4HANA Field guage

name_en_US Infotype Mapping Object (1000) Object Name (STEXT) EN

name_de_DE Infotype Mapping Object (1000) Object Name (STEXT) DE

name_es_ES Infotype Mapping Object (1000) Object Name (STEXT) ES

name_fr_FR Infotype Mapping Object (1000) Object Name (STEXT) FR

name_it_IT Infotype Mapping Object (1000) Object Name (STEXT) IT

name_nl_NL Infotype Mapping Object (1000) Object Name (STEXT) NL

Task overview: Preparatory Steps [page 275]

Related Information

Accessing the Customizing Structure in the SAP S∕4HANA System [page 277]
Importing Metadata from Employee Central [page 278]
Transferring Language-Dependent Fields [page 288]
Dening Organizational Data-Related Settings for Your Employee Central Company [page 294]
Dening Custom Employee Central Entities for Organizational Data Entities [page 294]
Dening Field Mapping for Organizational Data [page 297]

2.3.1.3.1.4 Transferring Language-Dependent Fields

Make the settings required to enable transfer of texts (such as names or descriptions of business units) between
SAP S∕4HANA and Employee Central.

Prerequisites

You can only transfer texts for an Employee Central locale if the corresponding language pack was enabled in
Provisioning for Employee Central.

 Remember

As a customer, you don't have access to Provisioning. To complete tasks in Provisioning, contact your
implementation partner or Account Executive. For any non-implementation tasks, contact Product Support.

Implementing Data Migration and Replication to Employee Central

288 PUBLIC Data Migration and Replication to Employee Central
Employee Central supports translations for position names, but not for position descriptions. That's why you
need to dene a custom description eld for positions if you want to replicate position descriptions for multiple
languages.

Context

To enable replication of texts in at least one language, you rst map language-independent text elds. This mapping
is used as a placeholder. Additionally, you map the locales you use in Employee Central to the corresponding
SAP S∕4HANA languages. Based on this language mapping, the language-dependent eld mappings are then
automatically created and replace the placeholders when the data is extracted.

Procedure

1. In Customizing for Personnel Management, choose Integration with SuccessFactors Employee Central
Business Integration Builder Data Migration and Replication to Employee Central Organizational Data Map
Languages from Employee Central and ERP to map Employee Central locales to SAP S∕4HANA languages.
Here's what you need to do there:
a. Dene a mapping for the default locale you use in Employee Central.

 Example

If your default locale is en_US, enter:

Mapping the Default Employee Central Locale

Employee Central Locale SAP S∕4HANA Language

en_US EN

 Note

Make sure that you use the correct format:

• The locale identier from Employee Central must consist of a language identier in lowercase and
a location or country/region identier in uppercase, linked by an underscore. For example: en_US
(English, USA), en_GB (English, UK), fr_FR (French, France), fr_CA (French, Canada).
• The language identier from SAP S∕4HANA must be a two-character country/region ISO code. For
example: EN, FR.

If you don't dene at least a language mapping for the default locale, no language-dependent data can
be transferred.

 Example

Let's say you try to replicate a new department from Employee Central to SAP S∕4HANA. This means
that a new record of the Object (1000) infotype needs to be created in the SAP S∕4HANA system. The

Implementing Data Migration and Replication to Employee Central

Data Migration and Replication to Employee Central PUBLIC 289
 Object infotype needs a language. To determine the language to be used, the SAP S∕4HANA system
reads the entries stored in the V_ECPAO_LOCALE. If there aren't any entries here, the system doesn't
know which language to use for the infotype record. Therefore, the department can't be replicated. The
corresponding replication request has the status Pending.

b. Dene mappings for all additional locales your Employee Central instance supports for translation of texts.

 Example

If your Employee Central instance also supports German (for Germany), Spanish (for Spain), French,
Italian, and Dutch, add these entries:

Mapping Additional Employee Central Locales

Employee Central Locale SAP S∕4HANA Language

de_DE DE

es_ES ES

fr_FR FR

it_IT IT

nl_NL NL

Example: Mapping Languages from Employee Central and SAP S∕4HANA

 Caution

If you use two locales for the same language in Employee Central (such as en_US and en_GB), you
need to decide which of these locales you want to map to SAP S∕4HANA. In SAP S∕4HANA, there's only
one language key you can map (in our example: EN).

Implementing Data Migration and Replication to Employee Central

290 PUBLIC Data Migration and Replication to Employee Central
 2. Go to Dene Organizational Data Settings for Employee Central Instance in the same Customizing structure to
specify which of the mapped locales is your default Employee Central locale.

 Example

The eld help in the Employee Central instance view shows the locales you've mapped in the rst step:
• en_US
• de_DE
• es_ES
• fr_FR
• it_IT
• nl_NL

You select en_US.

Example: Dening the Default Locale for Your Employee Central Instance

 Example

The SAP S∕4HANA system uses the default locale, for example, when writing language-independent
content, such as IDs, to a language-dependent infotype, such as the Object (1000) infotype.

 Note

If Dene Organizational Data Settings for Employee Central Instance is your rst step, the eld help doesn't
show any languages yet. In this case, you’re redirected from here to the language mapping Customizing
view and can make the settings described in step 1.

3. Go to Dene Field Mapping for Organizational Data in the same Customizing structure and dene language-
independent eld mappings for text elds, which are used as placeholders.

Implementing Data Migration and Replication to Employee Central

Data Migration and Replication to Employee Central PUBLIC 291
  Example

You dene this placeholder mapping for department names:

Placeholder Field Mapping of Department Name

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

name_defaultValue Infotype Mapping Object (1000) Object Name (STEXT)

 Note

Most organizational objects use name_defaultValue, but not positions. That's why the mapping looks
dierent for position names:

Placeholder Field Mapping of Position Name

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

externalName_defaultValue Infotype Mapping Object (1002) Subtype Object Name (STEXT)

0001

The Use Language Mapping checkbox is automatically selected for this eld mapping.

Use Language Mapping Checkbox in Field Mapping

Implementing Data Migration and Replication to Employee Central

292 PUBLIC Data Migration and Replication to Employee Central
Results

Data transfer between Employee Central and SAP S∕4HANA automatically uses language-dependent eld
mappings instead of the placeholder mapping. There's no need to dene these four mappings explicitly.

 Example

In the example we've used above, these mappings would be used:

Language-Dependent Mappings of Department Name

Employee Central SAP S∕4HANA Info- SAP S∕4HANA Lan-

Field Mapping Mode type SAP S∕4HANA Field guage

name_en_US Infotype Mapping Object (1000) Object Name (STEXT) EN

name_de_DE Infotype Mapping Object (1000) Object Name (STEXT) DE

name_es_ES Infotype Mapping Object (1000) Object Name (STEXT) ES

name_fr_FR Infotype Mapping Object (1000) Object Name (STEXT) FR

name_it_IT Infotype Mapping Object (1000) Object Name (STEXT) IT

name_nl_NL Infotype Mapping Object (1000) Object Name (STEXT) NL

Task overview: Preparatory Steps [page 275]

Related Information

Accessing the Customizing Structure in the SAP S∕4HANA System [page 277]
Importing Metadata from Employee Central [page 278]
Conguring Replication of Language-Dependent Fields Between Employee Central and SAP S∕4HANA [page 285]
Dening Organizational Data-Related Settings for Your Employee Central Company [page 294]
Dening Custom Employee Central Entities for Organizational Data Entities [page 294]
Dening Field Mapping for Organizational Data [page 297]

Implementing Data Migration and Replication to Employee Central

Data Migration and Replication to Employee Central PUBLIC 293
2.3.1.3.1.5 Dening Organizational Data-Related Settings for
Your Employee Central Company

Make additional settings for the Employee Central instance you've dened before in the Dene Organizational Data
Settings for Employee Central Company Customizing activity (view V_ECPAO_CMPNY_OM).

Procedure

1. Choose your Employee Central instance ID.

2. Specify the company's default locale as you've dened it in Employee Central (for example, en_US).

To enable transfer of text elds (such as names or descriptions) between SAP S∕4HANA and Employee Central,
you need to map this default locale to an SAP S∕4HANA language such as EN.

Task overview: Preparatory Steps [page 275]

Related Information

Accessing the Customizing Structure in the SAP S∕4HANA System [page 277]
Importing Metadata from Employee Central [page 278]
Conguring Replication of Language-Dependent Fields Between Employee Central and SAP S∕4HANA [page 285]
Transferring Language-Dependent Fields [page 288]
Dening Custom Employee Central Entities for Organizational Data Entities [page 294]
Dening Field Mapping for Organizational Data [page 297]

2.3.1.3.1.6 Dening Custom Employee Central Entities for

Organizational Data Entities

An Employee Central entity represents an entity from Employee Central, such as a CSV data import template or a
generic object (also known as MDF entity). You only need to dene custom Employee Central entities if you want to
transfer data from SAP S∕4HANA to an Employee Central entity for which SAP hasn't provided a default template.

Context

In the Dene Employee Central Entities for Additional Organizational Data Entities Customizing activity (view
V_ECPAO_ECTMPL_O) you can also see the default templates dened by SAP. If the default templates suit your
requirements, there's no need to dene any custom templates.

Implementing Data Migration and Replication to Employee Central

294 PUBLIC Data Migration and Replication to Employee Central
 Details of an Employee Central Template

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

Procedure

1. Dene the basic settings.

a. Enter a unique entity ID and a description. The ID has to be in the customer namespace, which means that
it has to start with a number (0* - 9*). You can enter any description.
b. Enter the entity name. You must use the exact name of the corresponding entity in Employee Central.

To nd out about the name for generic objects, go to the Admin Center and choose the OData API Data
Dictionary tool. For CSV data import templates, go to the Admin Center and choose the Import and Export
Data tool.
c. Specify the organizational object type from Employee Central, such as Business Unit or Job Classication.
d. Depending on the type of Employee Central entity for which you use the template, select the
communication channel (CSV File-Based Transfer or Web Service Transfer).
e. If you want to be able to assign your Employee Central template to several transformation templates,
select the Multiple Use checkbox.
f. Specify if the Employee Central entity is eective dated.
2. Dene the standard Employee Central eld IDs.
a. Specify the name of the eld that contains the external code of the generic object in Employee Central and
to which the organizational object I from SAP S∕4HANA is to be transferred.

Implementing Data Migration and Replication to Employee Central

Data Migration and Replication to Employee Central PUBLIC 295
 b. Specify the Employee Central eld (such as eectiveStartDate) in which the start date is stored for the
corresponding entity and which is to be mapped to the Start Date (BEGDA) eld in SAP S∕4HANA.

For standard eective dated templates and standard eective dated MDF templates if the start date is
specied, then the start date would be considered as a standard eld. For custom MDF templates, start
date would not be considered as a standard eld.
c. Specify the Employee Central eld (such as endDate) in which the end date is stored for the corresponding
entity and which is to be mapped to the End Date (ENDDA) eld in SAP S∕4HANA.

For standard eective dated templates if the end date is specied, then the end date would be considered
as a standard eld. For custom MDF templates and standard MDF templates, end date would not be
considered as a standard eld. End date is now not a mandatory eld and you will be receiving a warning
message when you do not mention the end date.

 Note

Standard EC elds can be left blank while replicating the data to ERP when the dependent entity is
maintained.

3. Dene the Parent Child conguration.

a. Enter the upsert sequence number. This number denes the sequence in which the data for dierent
entities are transferred between the ERP system and SAP SuccessFactors Employee Central (EC).
b. In the Dependent Entity eld, select the Employee Central entity that corresponds to the parent object of
the composite child object.

If the parent entity is a standard delivered SAP entity, then only the upsert sequence of the child entity has
to be entered which can be any number. But if the parent entity is also a custom template, then you need to
ensure that the upsert sequence of parent is lower than that of the child entity.

 Note

The EC Org. Obj.Type value should be same as the parent/dependent entity. In case the child entity is
migrated to EC, the parent entity should also be included in the extraction process.

 Example

To map cost distribution, you need to create a custom composite child object with parent as position
and then map the Infotype 1018 value.

Task overview: Preparatory Steps [page 275]

Related Information

Accessing the Customizing Structure in the SAP S∕4HANA System [page 277]
Importing Metadata from Employee Central [page 278]
Conguring Replication of Language-Dependent Fields Between Employee Central and SAP S∕4HANA [page 285]
Transferring Language-Dependent Fields [page 288]
Dening Organizational Data-Related Settings for Your Employee Central Company [page 294]
Dening Field Mapping for Organizational Data [page 297]

Implementing Data Migration and Replication to Employee Central

296 PUBLIC Data Migration and Replication to Employee Central
2.3.1.3.1.7 Dening Field Mapping for Organizational Data

To enable the data extraction programs to extract the right SAP S∕4HANA information for the right Employee
Central elds, you need to map SAP S∕4HANA elds to Employee Central elds.

To map elds, you go to the Dene Field Mapping for Organizational Data Customizing step, which has the
VC_ECPAO_MAP_OM view cluster assigned. The conguration in this view cluster is done in several steps:

1. You create at least one transformation template group. A template group bundles all eld mappings that
you want to use when running the data extraction program. This is the entity that you specify on the
program selection screen. From the transformation template group the data extraction program determines all
information it needs to extract data from SAP S∕4HANA elds and map it to Employee Central eld IDs.
2. You create at least one transformation template for your transformation template group. A transformation
template groups information from the SAP S∕4HANA system that belongs together logically. It is the SAP
S∕4HANA counterpart of the Employee Central entity.
3. You dene a primary mapping for each of your transformation templates. This means you choose Employee
Central eld IDs from the Employee Central entity assigned to the transformation template, and you map
suitable SAP S∕4HANA elds to these Employee Central eld IDs.

 Example

The following sample transformation template groups are dened for the Employee Central company
SBS_MODEL in the delivered sample Customizing:

• SBS_OM_MODEL_CSV
This is an example for the replication of organizational data using the CSV File-Based Transfer
communication channel.
• SBS_OM_MODEL_WS
This is an example for the replication of organizational data using the Web Service Transfer communication
channel.

You can copy the transformation template group to your Employee Central company and change the eld
mapping of the transformation templates to suit your requirements.

Parent topic: Preparatory Steps [page 275]

Related Information

Accessing the Customizing Structure in the SAP S∕4HANA System [page 277]
Importing Metadata from Employee Central [page 278]
Conguring Replication of Language-Dependent Fields Between Employee Central and SAP S∕4HANA [page 285]
Transferring Language-Dependent Fields [page 288]
Dening Organizational Data-Related Settings for Your Employee Central Company [page 294]
Dening Custom Employee Central Entities for Organizational Data Entities [page 294]

Implementing Data Migration and Replication to Employee Central

Data Migration and Replication to Employee Central PUBLIC 297
2.3.1.3.1.7.1 Creating a Transformation Template Group for
Organizational Data

A template group bundles all eld mappings that you want to use when transferring data from SAP S∕4HANA to
Employee Central.

Context

To dene template groups, you go to the Dene Transformation Template Group for Organizational Data
Customizing step, which has the V_ECPAO_TTG_OM view cluster assigned.

Procedure

1. Click New Entries

2. Enter a name and description for the transformation template group.
3. Assign it to the Employee Central instance dened in the Specify Employee Central Instance ID Customizing
activity.

 Note

EC Instance is a read only eld when you are editing or copying the transformation template group. You will
be able to modify or choose the EC instance only when you are creating a new transformation template
group.

4. Choose the replication direction from the drop-down list box.

2.3.1.3.1.7.2 Dening Templates to Map Organizational Data

Fields

The transformation template is the counterpart of the Employee Central entity. You can map elds from the
transformation template to elds from the assigned Employee Central entity.

Context

To dene a set of transformation templates for each transformation template group, you go to the Transformation
Templates view of the VC_ECPAO_MAP_OM view cluster.

Implementing Data Migration and Replication to Employee Central

298 PUBLIC Data Migration and Replication to Employee Central
 Transformation Templates Assigned to a Transformation Template Group

Details of a Transformation Template

 Note

If you want to map organizational units, take into account that business units, divisions, and departments from
Employee Central all map to organizational units in the SAP S∕4HANA system. Therefore you need to decide
how to handle the organizational unit templates:

• Either you decide which of these object types you want to use. For example, if you decide to
always replicate organizational units to departments, you only add an transformation template to your
transformation template group that has the Department Employee Central entity assigned.
• If you want to use all three templates in your transformation template group, implement the Validity Periods
for Data Replication to EC (EX_ECPAO_EMP_VALIDITY_TAB) Business Add-In (BAdI) to dene for each
organizational unit to which object in Employee Central it is to be mapped.

These are the settings that you need to make for each transformation template you dene:

Procedure

1. Enter a name and description for the template.

2. Select the Is Active checkbox to dene that the template is to be used for data extraction.

Implementing Data Migration and Replication to Employee Central

Data Migration and Replication to Employee Central PUBLIC 299
3. Specify for eective-dated entities, if infotype records that contain the same data for the same object but refer
to dierent time periods are to be merged for data transfer between SAP S∕4HANA and Employee Central.

 Example

Let's say the following records of the Object (1000) infotype exist for an organizational unit:

Organizational Unit Infotype Records – Without Data Merge

Object Abbre-
Object Type Object ID Start Date End Date Language Key viation Object Name

O 50000955 January 1, December 31, E BU_3498 Business Unit

2015 2015 3498

O 50000955 January 1, December 31, E BU_3498 Business Unit

2016 2016 3498

If you select this checkbox, these infotype records are transferred separately. If you don't select this
checkbox, these infotype records are merged and the following record is transferred:

Organizational Unit Infotype Records – With Data Merge

Object Abbre-
Object Type Object ID Start Date End Date Language Key viation Object Name

O 50000955 January 1, December 31, E BU_3498 Business Unit

2015 2016 3498

4. Assign one of the default Employee Central entity or a custom Employee Central entity that you've created
before.

2.3.1.3.1.7.3 Dening the Primary Field Mapping for

Organizational Data

You can choose Employee Central elds from the Employee Central data model that you've uploaded to the SAP
S∕4HANA system, and you map suitable SAP S∕4HANA elds to these Employee Central eld IDs.

Context

To dene a eld mapping for each transformation template, you go to the Primary Mapping view of the
VC_ECPAO_MAP_OM view cluster.

 Note

There are predened standard mappings, which are automatically added to the templates you use and aren't
available for conguration in this Customizing activity.

Implementing Data Migration and Replication to Employee Central

300 PUBLIC Data Migration and Replication to Employee Central
Here's how to map elds:

Procedure

1. Choose an Employee Central eld from the assigned Employee Central template.

 Note

Make sure that you have imported the data model for this Employee Central template to the SAP S∕4HANA
system using the metadata import program. Otherwise no elds are available here.

2. Map each Employee Central eld to an SAP S∕4HANA eld using a suitable mapping mode:
• When you select the mapping mode Infotype Mapping, you assign an infotype or subtype eld in the
primary mapping. You can use elds from Organizational Management infotypes for eld mapping. For the
mappings of text elds such as Object Name (STEXT), you dene a language-independent mapping. The
Use Language Mapping checkbox is selected for this kind of eld mapping.

Use Language Mapping Checkbox

To make the language-dependent mapping work, you also need to map Employee Central locales to SAP
S∕4HANA languages.
• When you select the mapping mode BAdI Mapping, you can use an implementation of the Mapping of EC
and ERP Data for Data Replication to EC (EX_ECPAO_EMP_DATA_EXTRACT_OUT) BAdI to dene the eld
mapping.
• When you select the mapping mode Evaluation Path Mapping, you can map an Employee Central eld ID to
an evaluation path from SAP S∕4HANA.
3. If the value from the SAP S∕4HANA eld needs to be converted into an Employee Central value, enter the value
mapping entity that you have dened in the Dene Value Mapping Entities Customizing step.

Implementing Data Migration and Replication to Employee Central

Data Migration and Replication to Employee Central PUBLIC 301
  Note

You can dene the value mappings for this entity directly from here by choosing Dene Value Mapping
Entries.

Results

You are now ready to use your eld mapping when running the data extraction program.

 Note

Don't dene a secondary eld mapping for organizational data. Organizational data elds that have a secondary
mapping aren't replicated by the Organizational Data Extraction program.

2.3.1.3.2 Dening Value Mappings

Value mapping means that Employee Central eld values are mapped to values of SAP S∕4HANA elds.

The data extraction programs use the value mappings when extracting data. They replace the SAP S∕4HANA keys
by the corresponding Employee Central keys if a value mapping is dened for the corresponding eld mapping.
Value mappings are assigned to eld mappings in the Primary Mapping and Secondary Mapping views of the eld
mapping view cluster. Field mappings are grouped together in a transformation template group. You enter the
transformation template group on the selection screen to tell the extraction program which eld mappings and
which value mappings it is to use.

There are standard value mappings provided by SAP. Standard value mappings are provided for values that can't be
congured in the SAP S∕4HANA system and in Employee Central and therefore always stay the same.

 Example

Language codes can't be congured. The Employee Central language code English always corresponds to the
language code EN in the SAP S∕4HANA system. Therefore, a standard value mapping is provided for language
codes.

However, if you want to map values that can be congured in the SAP S∕4HANA system and in Employee Central,
you need to dene custom value mappings.

 Note

After copying the new value mapping entries, don’t save the entries immediately, but press the page down
button to see all the entries. You must click the page down button until you see the last set of entries. Once you
see the last set of entries, you can save all the newly created entries.

Dening Value Mapping Entities [page 303]

A value mapping entity combines a set of value mappings for a specic purpose (for example, gender code
value mappings).

Dening Value Mapping Details [page 306]

Implementing Data Migration and Replication to Employee Central

302 PUBLIC Data Migration and Replication to Employee Central
 The value mapping details actually map SAP S∕4HANA values to the corresponding Employee Central
values.

How to Use the Sample Value Mapping for Organizational Data [page 308]
Use the sample value mapping entities we provide for organizational objects to easily create the value
mappings you need, for example, for the relationships to other objects.

How to Use the Sample Content for Organizational Data [page 309]
We provide sample content for dierent use cases in the Dene Field Mapping for Organizational Data
Customizing step, which you can copy and adapt to your needs.

Parent topic: Steps in the SAP S∕4HANA System [page 275]

Related Information

Preparatory Steps [page 275]

Mapping Organizational Data to Table Infotype [page 312]
Particular Mapping Types [page 314]
Data Extraction and Transfer [page 320]

2.3.1.3.2.1 Dening Value Mapping Entities

A value mapping entity combines a set of value mappings for a specic purpose (for example, gender code value
mappings).

Context

You dene value mapping entities in the Dene Value Mapping Entities Customizing step (view
V_ECPAO_VALUENTY). The easiest way to create value mapping entities is to copy the sample entities by choosing
the Copy Sample Value Mapping pushbutton.

Copy Sample Value Mapping in V_ECPAO_VALUENTY

Implementing Data Migration and Replication to Employee Central

Data Migration and Replication to Employee Central PUBLIC 303
  Tip

If you want to check rst which sample value mapping entities are available, choose the Show Sample Value
Mapping pushbutton.

You can also create country-specic value mapping entries and create a new value mapping entity in the Dene
Field Mapping for Employee Data Customizing activity (view cluster VC_ECPAO_MAP). In this Customizing activity,
go to Primary Mapping Details and choose Create Value Mapping Entity or Dene Ctry. Spec. Value Mapping
Entries.

Create Value Mapping Entity/Dene Country-Specic Value Mapping Entries from Primary Mapping in VC_ECPAO_MAP

You'll get a list of all standard entities provided for the integration, which you can adjust to your needs.

Copied Standard Value Mapping Entities

Implementing Data Migration and Replication to Employee Central

304 PUBLIC Data Migration and Replication to Employee Central
During the employee replication from Employee Central, the value mapping type Organizational Object Keys
from Mapping Table is considered for mapping of organizational objects like Position, Departments, Divisons
etc. When these types are maintained in the value mapping entity, the data replication uses the mapping from
SFIOM_KMAP_OSI key mapping table. This table maps the keys of organizational objects (such as divisions or job
classications) from Employee Central to organizational object IDs (such as organizational unit IDs or job IDs) from
ERP. For value mapping entities with this mapping type, you need not enter the Employee Central and ERP values
that are to be mapped in the Dene Value Mapping Details Customizing activity. Instead, the replication uses the
mapping that is dened in the key mapping table. When this value mapping type is assigned, the type of the related
object (for example, Business Unit) also needs to be specied (column 'EC Org. Object Type' in the maintenance
view).

Procedure

1. To create a value mapping entity from scratch, enter a name and description. If you want to use a standard
entity, you need to keep its name, but you can adjust the description.
2. Specify how the values are to be mapped. If you want to use a standard entity, we recommend that you use the
suggested mapping types.
• Picklist mapping using the External Code eld from the picklist
Use this type if the picklist value you want to map is an External Code. This is the case for most of the
picklists.
3. To make available picklist values you've imported to the SAP S∕4HANA system from Employee Central in the
value mapping details, assign a picklist to the value mapping entity.

Choose Picklist for Value Mapping Entity

Picklist Assigned to Value Mapping Entity

Implementing Data Migration and Replication to Employee Central

Data Migration and Replication to Employee Central PUBLIC 305
 This enables you to choose the imported picklist values in the Employee Central Key eld when you actually
map the values. If you don't assign a picklist, you can still enter keys in the Employee Central Key eld, but you
can't choose from the imported picklist values.
4. To make available input help values from an infotype eld in the value mapping details, specify the SAP
S∕4HANA value help.

This is a combination of the technical name of the infotype table (such as PA0002) and the technical name of
the infotype eld (such as GESCH), connected with a hyphen (as in PA0002-GESCH). This means that you can
choose the input help values from the Gender Key (GESCH) eld of the Personal Data (0002) infotype in the
ERP Key eld when you actually map the values. It does not mean that you can only use the value mapping
entity for the GESCH eld. If you want to use a sample entity, we recommend that you use the suggested SAP
S∕4HANA value helps.

SAP S∕4HANA Value Help Assigned to Value Mapping Entity

Results

You are now ready to map the actual Employee Central and SAP S∕4HANA values in the next Customizing steps,
where you dene the value mapping details.

Task overview: Dening Value Mappings [page 302]

Related Information

Dening Value Mapping Details [page 306]

How to Use the Sample Value Mapping for Organizational Data [page 308]
How to Use the Sample Content for Organizational Data [page 309]

2.3.1.3.2.2 Dening Value Mapping Details

The value mapping details actually map SAP S∕4HANA values to the corresponding Employee Central values.

Procedure

1. Go to the Dene Value Mapping Details Customizing activity (view V_ECPAO_VALENTY).

2. Map SAP S∕4HANA keys and the corresponding Employee Central keys.

Implementing Data Migration and Replication to Employee Central

306 PUBLIC Data Migration and Replication to Employee Central
 If the value mapping entity has a picklist ID and a SAP S∕4HANA value help assigned, you can select suitable
picklist values in the EC Key eld and corresponding input help values in the ERP Key eld.

Choose SAP S∕4HANA Key for Value Mapping

Choose Employee Central Key for Value Mapping

You can also enter the wildcard * in the ERP Key eld. If only the wildcard is dened in the value mapping
details, any SAP S∕4HANA value will be mapped to the Employee Central key for the eld that uses this value
mapping entity. If the wildcard is dened in addition to specic SAP S∕4HANA keys, the system rst checks for
the specic keys. If an Employee Central key is mapped to a specic SAP S∕4HANA key, this mapping is used.
For all other SAP S∕4HANA values, the Employee Central key mapped to the wildcard is used.

Results

The data extraction programs can now use the value mappings. When extracting data, they will replace the SAP
S∕4HANA keys by the assigned Employee Central keys if a value mapping is dened for the corresponding eld
mapping. If no value mapping is available, they won't map any values for the specic eld and use the values from
SAP S∕4HANA as they are.

Implementing Data Migration and Replication to Employee Central

Data Migration and Replication to Employee Central PUBLIC 307
Task overview: Dening Value Mappings [page 302]

Related Information

Dening Value Mapping Entities [page 303]

How to Use the Sample Value Mapping for Organizational Data [page 308]
How to Use the Sample Content for Organizational Data [page 309]

2.3.1.3.2.3 How to Use the Sample Value Mapping for

Organizational Data

Use the sample value mapping entities we provide for organizational objects to easily create the value mappings
you need, for example, for the relationships to other objects.

We provide sample value mapping entities for the default organizational objects (departments, divisions, business
units, job classications, and positions) and for the Status of Vacancy (STATUS) eld of the Vacancy infotype
(1007).

 Note

If you choose Copy Sample Value Mapping, all entities that are available in the V_ECPAO_VALENT_S (S table)
view are copied to the V_ECPAO_VALUENTY (C table) view in the Dene Value Mapping Entities Customizing
activity. This includes the value mapping entities for organizational data as well as employee data, and for both
directions (replication from SAP S∕4HANA to Employee Central and replication from Employee Central to SAP
S∕4HANA). If you only need some of the sample value mapping entities, choose Copy Sample Value Mapping
and then remove all entities that you don't need from the V_ECPAO_VALUENTY view.

Once you've made entries in the V_ECPAO_VALUENTY view (either by copying or by entering them
manually), you can no longer copy the sample value mapping entities. Either remove all entries from the
V_ECPAO_VALUENTY view and copy again, or show the sample value mapping entities and use them as an
example for making the entries manually.

If you want to replicate other organizational objects (including custom objects), you need to dene custom value
mapping entities for them.

Use Case 1: You Replicate Only the Default Objects

1. Copy the sample value mapping entities.

2. The only value mapping entity that uses value mapping details is VACANCY_STATUS_WS. If you want to use it,
also make entries in the Dene Value Mapping Details Customizing step (V_ECPAO_VALENTY view).
The other value mapping entities used for organizational data replication don't use any value mapping details,
that's why you don't need to make any additional settings.

Implementing Data Migration and Replication to Employee Central

308 PUBLIC Data Migration and Replication to Employee Central
Use Case 2: You Replicate the Default Plus Additional Objects

1. Copy the sample value mapping entities.

2. If necessary, create additional value mapping entities for the additional objects.

Parent topic: Dening Value Mappings [page 302]

Related Information

Dening Value Mapping Entities [page 303]

Dening Value Mapping Details [page 306]
How to Use the Sample Content for Organizational Data [page 309]

2.3.1.3.2.4 How to Use the Sample Content for Organizational

Data

We provide sample content for dierent use cases in the Dene Field Mapping for Organizational Data Customizing
step, which you can copy and adapt to your needs.

Use Cases

Sample content is available for all organizational-related templates and are available for the following use cases.

Organizational Data SAP S∕4HANA to EC: CSV File-Based Objects (OM_CSV_1)

Provides eld mappings for the default organizational objects (organizational units, jobs, positions). Use this
sample content to set up a CSV le-based migration to initially move your organizational objects from the SAP
S∕4HANA system to Employee Central if you transition to using Employee Central as the system of record for
Organizational Management.

 Note

This sample content includes eld mappings only for the default organizational objects. It does not include
relationships between the objects (such as position to organizational unit relationships) or parent relationships
(such as organizational unit to parent organizational unit relationships). Use the OM_CSV_2 sample content in
addition to migrate the relationships in a second step.

Organizational Data SAP S∕4HANA to EC: CSV File-Based Objects and Relationships
(OM_CSV_2)
Provides eld mappings for the relationships between the default organizational objects (organizational units, jobs,
positions, position matrix relationship), including parent relationships. Use this sample content to set up a CSV

Implementing Data Migration and Replication to Employee Central

Data Migration and Replication to Employee Central PUBLIC 309
le-based migration to initially move the relationships between the objects and the parent relationships from the
SAP S∕4HANA system to Employee Central if you transition to using Employee Central as the system of record for
Organizational Management.

If you use this sample content, make sure that you have migrated the default organizational objects before with the
OM_CSV_1 sample content.

If you want to include cost center relationships, make sure that you've set up cost center replication from the SAP
S∕4HANA system to Employee Central before.

Organizational Data SAP S∕4HANA to EC: Objects (OM_WS_4)

Provides eld mappings for the default organizational objects (organizational units, jobs, positions). You can use
this sample content in two scenarios:

• Either to set up a regular web service-based replication of organizational data from the SAP S∕4HANA system
to Employee Central when using the side-by-side deployment option.
• Or to set up a delta-enabled migration to initially move your organizational data from the SAP S∕4HANA system
to Employee Central if you transition to the side-by-side or the core hybrid deployment option and plan to use
Employee Central as the system of record for Organizational Management in the future.

 Note

This sample content includes eld mappings only for the default organizational objects. It does not include
relationships between the objects (such as position to organizational unit relationships) or parent relationships
(such as organizational unit to parent organizational unit relationships). Use the OM_WS_5 sample content in
addition to migrate the relationships in a second step.

Organizational Data SAP S∕4HANA to EC: Objects and Relationships (OM_WS_5)

Provides eld mappings for the relationships between the default organizational objects (organizational units, jobs,
positions, position matrix relationship), including parent relationships. You can use this sample content in two
scenarios:

• Either to set up a regular web service-based replication of relationships from the SAP S∕4HANA system to
Employee Central when using the side-by-side deployment option.
• Or to set up a delta-enabled migration to initially move the relationships from the SAP S∕4HANA system to
Employee Central if you transition to the side-by-side or the core hybrid deployment option and plan to use
Employee Central as the system of record for Organizational Management in the future.

If you use this sample content, make sure that you have migrated the default organizational objects before using
the OM_WS_4 sample content.

How to Proceed

Here is how to use the sample content provided in the Dene Field Mapping for Organizational Data Customizing
activity:

1. Create a transformation template group and select the sample content that you want to use for it.
2. In your transformation template group, create transformation templates for all entities you want to use and
assign the corresponding Employee Central entities. You can create the transformation templates using two
methods:

Implementing Data Migration and Replication to Employee Central

310 PUBLIC Data Migration and Replication to Employee Central
 • Using the Copy Sample Content button at the transformation template group level.

You can use the Copy Sample Content button to copy the transformation templates and the corresponding
Primary Mapping and Secondary Mapping congurations for the relevant Employee Central entities. To see
the entries copied to the Primary and Secondary Mapping views, you need to click the Save button to save
and view all the congurations. Which eld mappings are copied depends on the sample content you have
selected for the transformation template group.
• Using the Copy Sample Content button at the each transformation template level.

Which eld mappings are copied depends on the sample content you have selected for the transformation
template group.
3. If needed, adapt the copied sample content to suit your requirements. You can, for example, delete mappings
you don't need, change the mapped eld, or add new mappings.
4. Replicate the organizational unit relationships. To do so:
1. In the 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 elds to department elds and
that maps the Parent eld. Deselect this checkbox for the other transformation template that you use for
mapping organizational units (the one that doesn't contain the Parent eld).
2. Extract the data for your organizational units using the Organizational Data Extraction
(ECPAO_OM_OBJECT_EXTRACTION) program. On the selection screen of the program, specify the
template group that you use for organizational data extraction. The Organizational Data Extraction program
uses the transformation template that maps the Parent eld since you've set the Is Active checkbox for
this transformation template. The other transformation template, which doesn't map the Parent eld, isn't
used since this is not active.
3. Import the extracted data into Employee Central. Now the parent-child associations are created for the
departments you have replicated in the rst step.

 Note

Once you have made custom entries in the Primary Mapping view (either by copying and adapting the sample
content or by making your custom entries from scratch), you can no longer copy the sample content. If you
have dened custom mappings and decide that you want to use the mappings provided by the sample content
instead, delete the transformation template and create a new template.

If you have already dened eld mappings in the previous releases, you can continue to use them without
any changes. However, if you want to replace your custom mappings with mappings provided with the sample

Implementing Data Migration and Replication to Employee Central

Data Migration and Replication to Employee Central PUBLIC 311
 content, create new transformation templates for all entities for which you want to use the sample mapping.
Then continue as described above. Remove your existing transformation templates for the same entities from
the transformation template group or clear the Is Active checkbox for them so that the new transformation
templates are used instead.

Parent topic: Dening Value Mappings [page 302]

Related Information

Dening Value Mapping Entities [page 303]

Dening Value Mapping Details [page 306]
How to Use the Sample Value Mapping for Organizational Data [page 308]

2.3.1.3.3 Mapping Organizational Data to Table Infotype

You want to map the table infotype in the view cluster to support the migration process.

Prerequisites

You need to create a custom OM Entity in the V_ECAPO_ECTMPL_O view similar to the one, which is created in the
EC instance.

Context

Table infotypes allows you to store the data in a tabular structure in one infotype record. All the OM infotypes,
which have HRT table in addition to the HRP tables are table infotypes. You can map any table infotype in the
conguration since this is common for both Organizational data migration and Organizational data replication. But
in Organizational data migration, only table infotype 1002 and 1018 are supported.

Procedure

1. Go the view VC_ECPAO_MAP_OM.

2. Choose the transformation template group, for which you want to map the table infotype.
3. Create a transformation template for the transformation template group corresponding to the custom OM
entity.

Implementing Data Migration and Replication to Employee Central

312 PUBLIC Data Migration and Replication to Employee Central
 4. In the Primary Mapping screen, choose the elds from the F4 help menu and then perform the mapping. All the
elds from HRP and HRT table will be available for mapping.

You can migrate multiple cost distributions stored in the corresponding 1018 table infotype records for the
parent object, as shown in the below example.

 Example

Position entries for Cost Distrubution in ERP system:

After the migration process, the position entries in EC system:

Task overview: Steps in the SAP S∕4HANA System [page 275]

Related Information

Preparatory Steps [page 275]

Dening Value Mappings [page 302]
Particular Mapping Types [page 314]
Data Extraction and Transfer [page 320]

Implementing Data Migration and Replication to Employee Central

Data Migration and Replication to Employee Central PUBLIC 313
2.3.1.3.4 Particular Mapping Types

How Evaluation Path Mapping Works [page 314]

You can use evaluation path mapping, for example, to extract chief positions even if they aren't assigned to
the employee's organizational unit directly, but to a higher-level organizational unit.

Replicating Navigation Fields for Organizational Data [page 318]

Carry out the steps we describe here to replicate navigation eld of organizational objects, such as the
division associated to a position.

Parent topic: Steps in the SAP S∕4HANA System [page 275]

Related Information

Preparatory Steps [page 275]

Dening Value Mappings [page 302]
Mapping Organizational Data to Table Infotype [page 312]
Data Extraction and Transfer [page 320]

2.3.1.3.4.1 How Evaluation Path Mapping Works

You can use evaluation path mapping, for example, to extract chief positions even if they aren't assigned to the
employee's organizational unit directly, but to a higher-level organizational unit.

With evaluation path mapping, you don't map an Employee Central eld directly to an SAP S∕4HANA eld. Instead,
you map it to an evaluation path from SAP S∕4HANA. The SAP S∕4HANA system then uses this evaluation path to
determine the mapped object, such as the chief position of an organizational unit.

If you choose this mapping mode, you need to select the evaluation path to be used. This is a chain of relationships
between objects in a hierarchical structure. The SAP S∕4HANA system evaluates the organizational structure along
the evaluation path you specify. The evaluation paths from which you can choose are dened in Customizing
for Personnel Management under Organizational Management Basic Settings Maintain Evaluation Paths
(transaction OOAW).

Here's an example of an evaluation path that uses the following relations to determine parent positions from the
organizational structure:

• Position belongs to organizational unit

• Position manages organizational unit
• Organizational unit reports to organizational unit

Implementing Data Migration and Replication to Employee Central

314 PUBLIC Data Migration and Replication to Employee Central
 Evaluation Path for Parent Position

 Example

Let's say you select the Evaluation Path Mapping mapping mode for the Job code eld of the Position entity
and choose an evaluation path that retrieves the job code of the chief position evaluating the organizational
structure.

In the following example, you select the Evaluation Path Mapping mapping mode for the jobCode eld of the
Position entity and choose an evaluation path that uses the Is described by relationship between all kinds of
organizational objects:

Evaluation Path Mapping of jobCode Field

Primary mapping conguration : Position Object -- Job code eld mapping in primary mapping screen:

Implementing Data Migration and Replication to Employee Central

Data Migration and Replication to Employee Central PUBLIC 315
 The assigned value mapping entity species that data replication is to use the mapping from the
SFIOM_KMAP_OSI key mapping table to map the key of the related job from the SAP S∕4HANA system to
determine the object type (04 = job classication) and to map the job classication key from Employee Central.

In the value mapping eld, a value mapping entity for the object type must be entered. The value mapping type
must be of type Organization Object Keys From Mapping Table.

Job Code Value Mapping Entity

This means, the SAP S∕4HANA system determines the jobs that are related to the extracted positions from the
organizational structure in your SAP S∕4HANA system.

For the extraction of the below Position object: 50862581, the behaviour will be as follows:

Organizational Structure of Position Object but not assigned Job code

Implementing Data Migration and Replication to Employee Central

316 PUBLIC Data Migration and Replication to Employee Central
 In the Position organizational structure, selected Position is not assigned any job code then required to retrieve
the job code for the chief position of the same org unit.

Organizational Structure chief position (B012 relationship) with assigned Job code

Organizational Data Extraction

Organizational Data Extraction Result

Parent topic: Particular Mapping Types [page 314]

Related Information

Replicating Navigation Fields for Organizational Data [page 318]

Implementing Data Migration and Replication to Employee Central

Data Migration and Replication to Employee Central PUBLIC 317
2.3.1.3.4.2 Replicating Navigation Fields for Organizational
Data

Carry out the steps we describe here to replicate navigation eld of organizational objects, such as the division
associated to a position.

Procedure

1. Download the latest OData metadata XML le from your Employee Central instance using the OData API
Metadata Refresh and Export admin tool.
2. Make sure that an Employee Central template exists for the associated object in the Dene Employee Central
Templates for Additional Org. Data Entities Customizing step. If a default template is provided here, you can use
this. If not, create a custom template.

 Example

A position can have a divisionNav/externalCode eld, meaning, an associated division. We provide a default
Employee Central template, WS_OM_DIV, for the FODivision entity. That's why you don't need to create any
additional template.

Implementing Data Migration and Replication to Employee Central

318 PUBLIC Data Migration and Replication to Employee Central
 Here's an example of a position that has a division associated in Employee Central (and also a higher-level
position):

Position Associations in Employee Central

Or, let's say, a job classication has a cust_toJobFunction/externalCode eld, which refers to an associated
Job Function entity. We don't provide a default Employee Central template for Job Function. This means,
you need to dene a custom Employee Central template for this entity in the Dene Employee Central
Templates for Additional Org. Data Entities Customizing step using the customer name space. For example:
0_JOB_FUNC. In this template, you specify the name of the associated object (FOJobFunction) as the
Employee Central template name. In the Object ID in EC eld ID, you enter the FOJobFunction eld that
contains the ID of this entity, such as externalCode. And in the Start Date in EC eld ID, you enter the
FOJobFunction eld that contains the start date, such as eectiveStartDate or startDate.

3. Run the Import of Metadata from Employee Central Using XML File (ECPAO_ECTMPL_METADATA_WRITER)
program using the le you've downloaded in the rst step.

This will update the attributes of all the existing elds and add new elds if there are any.

 Example

In the rst example, you would import the metadata for the WS_OM_POS because a mapping of the
divisionNav/externalCode and divisionNav/eectiveStartDate elds is dened for this template.

Implementing Data Migration and Replication to Employee Central

Data Migration and Replication to Employee Central PUBLIC 319
 In the second example, you would import the metadata for the WS_OM_JOB Employee Central template.

4. The metadata import lls the Navigation Target Field (EC_NAV_TARGET) eld in he EC Entity Field Mapping
(ECPAO_FLD) table with the name of the associated object.

 Example

In the rst example, the content of the Navigation Target Field eld would be FODivision.

In the second example, it would be FOJobFunction.

5. Run the Organizational Data Extraction (ECPAO_OM_OBJECT_EXTRACTION) program.

Results

The navigation elds will be created in Employee Central for the replicated objects.

Task overview: Particular Mapping Types [page 314]

Related Information

How Evaluation Path Mapping Works [page 314]

2.3.1.3.5 Data Extraction and Transfer

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

Extracting Organizational Data [page 324]

Here is how to extract organizational data from the SAP S∕4HANA system to transfer it to Employee
Central.

Extracting Organizational Data in Multiple Steps [page 331]

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

Downloading CSV Files from the Application Server [page 332]

If you've stored the data extracted to CSV les on the application server, here's how to transfer the data
from the application server location to a local drive.

Extracting Changed Organizational Data Using Delta Replication [page 334]

After the initial run of the organizational data extraction program, changed data is replicated using delta
replication. Here's how you need to set this up.

Replicating Organizational Data to Custom Entities in Employee Central [page 336]

Here's an overview of the steps involved when you want to transfer data from SAP S∕4HANA to a custom
entity in Employee Central.

Implementing Data Migration and Replication to Employee Central

320 PUBLIC Data Migration and Replication to Employee Central
 Parallelization of Organizational Data Extraction Via Job Scheduler Report [page 337]
For migrating a large number of organizational data to Employee Central you can use the Job Scheduler
report. This report will automatically divide the load into smaller batches and schedule multiple background
jobs, which can be executed in parallel.

Extraction of Inactive Organizational Objects [page 340]

ERP system might have delimited organization objects which does not exist until the end of time
(31.12.9999). In this case when you replicate the data to Employee Central system has to send an inactive
record since the last active date to 31.12.9999.

Parent topic: Steps in the SAP S∕4HANA System [page 275]

Related Information

Preparatory Steps [page 275]

Dening Value Mappings [page 302]
Mapping Organizational Data to Table Infotype [page 312]
Particular Mapping Types [page 314]

2.3.1.3.5.1 Sequence of Data Extraction and Import Steps for

Dierent Object Types

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

Prerequisites

Make sure that the Parent eld is not a required eld 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.

Example: Employee Central Entities Enabled for Multiple Use

Implementing Data Migration and Replication to Employee Central

Data Migration and Replication to Employee Central PUBLIC 321
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 eld 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 elds from SAP S∕4HANA to department elds in Employee Central. You assign the
Employee Central entity DEPARTMENTImportTemplate to both of the transformation templates and map the
elds as shown below.

DEPARTMENT_WO_PARENT

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

Name Infotype Mapping 1000 STEXT

Code BAdI Mapping

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 elds
to department elds and that does not map the Parent eld. Deselect this checkbox for the other
transformation template that you use for mapping organizational units (the one that contains the Parent
eld).

 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 eld since you've set the
Is Active checkbox for this transformation template. The other transformation template, which maps the
Parent eld, isn't used since this is not active.

Implementing Data Migration and Replication to Employee Central

322 PUBLIC Data Migration and Replication to Employee Central
 c. Import the extracted data into Employee Central. Departments are created without any parent
associations.
2. Replicate jobs (which correspond to job classications 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
elds from SAP S∕4HANA to job classication elds 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 elds from SAP S∕4HANA to position elds 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 elds to
department elds and that maps the Parent eld. Deselect this checkbox for the other transformation
template that you use for mapping organizational units (the one that doesn't contain the Parent eld).

 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 eld since you've set the Is
Active checkbox for this transformation template. The other transformation template, which doesn't map
the Parent eld, 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 rst 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 elds from SAP S∕4HANA to job classication elds 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 elds from SAP S∕4HANA to position elds in
Employee Central.

Task overview: Data Extraction and Transfer [page 320]

Related Information

Extracting Organizational Data [page 324]

Extracting Organizational Data in Multiple Steps [page 331]
Downloading CSV Files from the Application Server [page 332]

Implementing Data Migration and Replication to Employee Central

Data Migration and Replication to Employee Central PUBLIC 323
Extracting Changed Organizational Data Using Delta Replication [page 334]
Replicating Organizational Data to Custom Entities in Employee Central [page 336]
Parallelization of Organizational Data Extraction Via Job Scheduler Report [page 337]
Extraction of Inactive Organizational Objects [page 340]

2.3.1.3.5.2 Extracting Organizational Data

Here is how to extract organizational data from the SAP S∕4HANA system to transfer it to Employee Central.

Procedure

1. Go to the Organizational Data Extraction (ECPAO_OM_EXTR) transaction to run the Organizational Data
Extraction (ECPAO_OM_OBJECT_EXTRACTION) program.

The program extracts organizational data from the SAP S∕4HANA system based on your selection criteria.

Selection Screen of the ECPAO_OM_OBJECT_EXTRACTION Program

Implementing Data Migration and Replication to Employee Central

324 PUBLIC Data Migration and Replication to Employee Central
 On the selection screen:

• Select the template group to be used for the data extraction.

• Select the variant ID that you have created before in the Dene the Variant IDs for Data Migration
customizing activity (view V_ECPAO_VARIANT). Once you have created the variant ID, you should have
assigned the required transformation templates to the variant ID using the Dene the Transformation
Templates for a Variant ID customizing activity (view V_ECPAO_TEMP_VAR).

 Note

This is not a mandatory eld. You can choose the Variant ID if you want to perform the extraction in
multiple steps. For more information, see: Extracting Organizational Data in Multiple Steps [page 331]

For example, a transformation template group consists of the 5 transformation templates (ERP1, ERP2,
ERP3, ERP4, and ERP5). In these templates if you want to choose only ERP1, ERP3, and ERP5, you can
create a variant ID for these transformation templates. And when you choose this variant ID for migration
process, only these transformation templates (ERP1, ERP3, and ERP5) would be considered.
• Specify how you would like to transfer the data:
• By web services, using the middleware that is available for the data replication from SAP S∕4HANA to
Employee Central.
• Using comma-separated values (CSV) les.
If you choose the File Transfer Using Server Path option, you can later transfer the data from the
application server location to a local drive.

 Note

Default option for the le transfer is server path.

If you choose the File Transfer Using Local Drive Path option, you must specify where the CSV le is to
be stored.

 Note

When you schedule the program as a background job to carry out a mass data extraction, always
choose the File Transfer Use Server Path option.

For both options, you can specify an addition to the le name to prevent existing les from being
overwritten by new les. If you don't enter a le identier, the same le name is used for each
download so that existing les are overwritten.

 Note

You can carry out a test run of the program rst to check if the data can be extracted from SAP
S∕4HANA without errors.

• Select the Detailed Message Log checkbox if you want to get a detailed log containing all warning and error
messages.
• Select the Failed Objects Only checkbox if you want to re-run the replication for only those objects for
which the replication status has failed.
2. If you carry out a productive run, the program extracts the data.

Implementing Data Migration and Replication to Employee Central

Data Migration and Replication to Employee Central PUBLIC 325
  Note

If the template group you have entered on the selection screen contains multiple transformation templates
for organizational units, which map organizational units to dierent object types in Employee Central, your
are shown an error message. Since business units, divisions, and departments from Employee Central
all map to organizational units in the SAP S∕4HANA system, you need to decide how to handle the
organizational unit templates:
• Either you decide which of these object types you want to use. For example, if you decide to
always replicate organizational units to departments, you only add a transformation template to your
transformation template group that has the Department Employee Central entity assigned.
• If you want to use all three templates in your transformation template group, you must implement the
Validity Periods for Data Replication to EC (EX_ECPAO_EMP_VALIDITY_TAB) Business Add-In (BAdI) to
dene for each organizational unit to which object in Employee Central it is to be mapped.

3. The program updates the following tables:

• Inventory of Data Replicated for Employees and Org. Objects (ECPAO_EE_INVT)
This table shows when the data of which organizational object was extracted, such as:

Sample Entry in the ECPAO_EE_INVT Table

Time Stamp (Universal Co-

Employee Central Instance SAP S∕4HANA Object Type SAP S∕4HANA Object ID ordinated Time)

SBS_MODEL S (= Position) 50080944 20.150.325.063.810,429865

0 = 2015 March 25, 6:38
(plus seconds, milliseconds,
microseconds, and the rst
decimal of the nanosec-
onds)

• Inventory of Data Replicated for Employee Central Entities (ECPAO_INVT)

Implementing Data Migration and Replication to Employee Central

326 PUBLIC Data Migration and Replication to Employee Central
 This table holds information about when the data of which Employee Central entity was replicated to
Employee Central, such as:

Sample Entry in the ECPAO_INVT Table

Employee's Data Suc-

Personnel cessfully Re- Data Repli- Time Stamp
Employee SAP Number in Employee plicated to cated in Data Dele- (Universal
Central In- S∕4HANA SAP Central En- Employee Last Repli- tion Repli- Coordinated
stance Object Type S∕4HANA tity Central cation Run cated Time)

SBS_MODEL S (= Posi- 50080944 WS_OM_PO X X 20.160.704.0

tion) S 82.354,7129
620 = 2016
July 04, 8:23
(plus sec-
onds, milli-
seconds, mi-
croseconds,
and the rst
decimal of
the nanosec-
onds)

• Inventory of Replicated Data: Error Messages (ECPAO_INVT_MSG)

This table holds the error messages issued for the replication by Employee Central or by SAP S∕4HANA,
per Employee Central entity, such as:

Sample Entry in the ECPAO_INVT_MSG Table

Employee SAP S∕4HANA SAP S∕4HANA Employee Sequence Num-

Central Instance Object Type Object ID Central Entity ber Message Text

SBS_MODEL S (= Position) 50080944 WS_OM_POS 1 Save batch

with same
externalCode
failed! Cannot
nd GO by
externalCode : [...]

SBS_MODEL S (= Position) 50080944 WS_OM_POS 2 Data of Position

50080944 was
not completely
replicated to EC

• Organizational Structure Item Key Mapping (SFIOM_KMAP_OSI)

Implementing Data Migration and Replication to Employee Central

Data Migration and Replication to Employee Central PUBLIC 327
 This table maps the Employee Central object types and codes to the corresponding object IDs and names
in SAP S∕4HANA, such as:

Sample Entry in the SFIOM_KMAP_OSI Table

Employee Central Object SAP S∕4HANA Object

Type Employee Central Code SAP S∕4HANA Object ID Name

05 (= Position) POSITION_01 50002326 Position 01

Employee Central codes are mapped to SAP S∕4HANA IDs either using the standard mapping
or based on an implementation of the Mapping of User ID, Person ID, Username, and Object ID
(EX_ECPAO_EMP_USYID_PRN_UNM_MAP) Business Add-In (BAdI).
To view the table, go to the View Org. Structure Item Key Mapping (SFIOM_KMAP_OSI) transaction.

 Tip

Use the Analyze Inventory of Replicated Organizational Data (ECPAO_OM_INVENTORY_ALV) program to

check the inventory tables.

4. When delta enabled transformation template group is selected in the selection screen, for the successfully
migrated PERNR's, the extraction process updates the corresponding ECPAO message type change pointers (if
available), and marks them as processed.

 Note

This applies when you do not choose any variant selection on the selection screen.

5. Before the extraction report runs, you need to replicate the cost centers from your SAP S∕4HANA Finance
system to Employee Central and then the organizational data migration takes place. The cost center eld value
in the organizational objects which are being migrated should be formatted or converted to the external codes
of the corresponding Employee Central cost centers. This formatting or conversion logic is required since the
value of the related cost center object ID stored in Infotype 1001 is dierent than that of the cost center ID,
which is created in Employee Central system.

The value mapping entity type for this cost center should be Cost Center Keys from Mapping Table, otherwise
the data will not be extracted from the cost center. The default cost center external code that is created in
EC via the cost center replication report ODTP_REPL_CC will have the cost center formatted like 4 characters
controlling area (KOKRS) + 10 characters controlling area (KOSTL). Whereas in SAP ERP, the cost center ID
stored in infotype 1001 is 10 characters and KOSTL concatenated with the 4 characters KOKRS. If the cost
center ID in EC is not as per the expected format of concatenation of KOKRS and KOSTL, then you will get
an error during the migration of the organizational object having cost center relationships. In that case, you
will either have to use the BAdI EX_ECPAO_ERP_EMP_DATA_MODIFY or map the value explicitly using a value
mapping entity (type standard).
6. The program writes messages to the application log. To check the messages, go to the Analyze Application Log
(SLG1) transaction.

The download log le shows all the success, error, and warning messages. It will also include the number of les
that were downloaded and from where the le is downloaded from.

Please note that the les might contain personal and sensitive data. Additional authorization is performed to
check if the user has the right to download the CSV le. Only specic authorized users should be allowed

Implementing Data Migration and Replication to Employee Central

328 PUBLIC Data Migration and Replication to Employee Central
 for this operation. The downloads that are triggered by a user to the application server or local server in
Production mode and in Test Run (Download Payload) are logged via table ECPAO_OBJ_DWNLD along with the
timestamp and transformation template details.

The below authorizations are required to be able to download the CSV les:

Authorizations
Authorization Object Authorization Field Authorization Value

S_DATASET(for application server) ACTVT 34

S_DATASET(for application server) FILENAME /usr/*

S_DATASET(for application server) PROGRAM CL_ECPAO_FILE_ON_SERVER*

ECPAO_OM_OBJECT_EXTRACTION

S_TABU_NAM ACTVT 02

S_TABU_NAM TABLE ECPAO_OBJ_DWNLD

7. Enter the ECPAO object and the ECPAO_OM subobject. To check for a specic object, enter the object ID in the
External ID eld. Optionally specify additional selection criteria, then choose Execute.

Implementing Data Migration and Replication to Employee Central

Data Migration and Replication to Employee Central PUBLIC 329
 Selection Screen of the SLG1 Transaction

Task overview: Data Extraction and Transfer [page 320]

Related Information

Sequence of Data Extraction and Import Steps for Dierent Object Types [page 321]
Extracting Organizational Data in Multiple Steps [page 331]
Downloading CSV Files from the Application Server [page 332]
Extracting Changed Organizational Data Using Delta Replication [page 334]
Replicating Organizational Data to Custom Entities in Employee Central [page 336]
Parallelization of Organizational Data Extraction Via Job Scheduler Report [page 337]

Implementing Data Migration and Replication to Employee Central

330 PUBLIC Data Migration and Replication to Employee Central
Extraction of Inactive Organizational Objects [page 340]

2.3.1.3.5.3 Extracting Organizational Data in Multiple Steps

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

Prerequisites

In order to do a step wise employee data migration using a single transformation template group, you should have
already created a transformation template group using the view cluster VC_ECPAO_MAP_OM. For more information
see: Creating a Transformation Template Group for Organizational Data.

Context

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

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

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

Once the initial migration process is successful, you can then migrate the relationships to the existing templates (ex
Job relationship, Position relationship etc.). Lastly you can execute delta replication via change pointers. For more
information on delta replication, see: Extracting Changed Organizational Data Using Delta Replication [page 334].

Here you can use a single transformation template group (by creating dierent variant ID's for a single
transformation template group) to cater for dierent scenarios without changing any congurations in the
transformation template group.

 Tip

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

Implementing Data Migration and Replication to Employee Central

Data Migration and Replication to Employee Central PUBLIC 331
Procedure

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

 Note

You can also choose the variant ID when you run the job scheduler report. For more information on job
scheduler report, see: Parallelization of Organizational Data Extraction Via Job Scheduler Report

Task overview: Data Extraction and Transfer [page 320]

Related Information

Sequence of Data Extraction and Import Steps for Dierent Object Types [page 321]
Extracting Organizational Data [page 324]
Downloading CSV Files from the Application Server [page 332]
Extracting Changed Organizational Data Using Delta Replication [page 334]
Replicating Organizational Data to Custom Entities in Employee Central [page 336]
Parallelization of Organizational Data Extraction Via Job Scheduler Report [page 337]
Extraction of Inactive Organizational Objects [page 340]

2.3.1.3.5.4 Downloading CSV Files from the Application Server

If you've stored the data extracted to CSV les on the application server, here's how to transfer the data from the
application server location to a local drive.

Prerequisites

• Dene the logical le path ECPAO_TMPL_DIR in the Logical File Path Denition (FILE) transaction.
• Dene Assignment of physical paths to logical path for the logical le path ECPAO_TMPL_DIR.

 Note

• Maintain the syntax group as UNIX.

Implementing Data Migration and Replication to Employee Central

332 PUBLIC Data Migration and Replication to Employee Central
 • Maintain the source le path as /usr/sap/<SYSID>/SYS/global/<FILENAME> in the physical path.
• In the logical le name denition, double click on the logical le of ECPAO_TMPL_DIR dened similar to
as mentioned below: Parameters of this conguration should have the below values
• Physical le: <PARAM_1>
• Data format: ASC
• Applicat.area: HR
• Logical path: ECPAO_TMPL_DIR

Context

Procedure

1. Go to the SAP Directories (AL11) transaction.

2. Double-click DIR_GLOBAL to see the les in this directory and note the name of the le that you want to
download, such as 0001_BasicUSerInfoImportTemplate_Company.CSV.
3. Run the ECPAO_APPSRVR_FILE_DWNLD report using the transaction ECPAO_SRVR_FILE_DWNL.
1. Enter the server le path along with the lename from where you want to download the data. A value help
is also available which provides a list of all les existing in the application server le path maintained in FILE
conguration. Select any le from F4 help to proceed.
2. Enter the local le path along with the le name where you want to save the data. A value help is also
available which enables you to select the folder. Once the folder is selected, the le name is auto-populated
using a reference of the lename provided in the server le path.

 Note

• Make sure that both the path’s extension matches to avoid any error.
• Only one le can be downloaded at one time.
• This report is not added as a part of the standard sample roles delivered with the add-on.

The below authorizations are required to run the report:

• S_DATASET ACTVT 33
• S_DATASET FILENAME
• S_DATASET PROGRAM ECPAO_APPSRVR_FILE_DWNLD
• S_TABU_NAM ACTVT 02
• S_TABU_NAM TABLE ECPAO_ASDNLD_INV
You can nd the downloaded le at the path provided on the selection screen. Once the le is successfully
downloaded, a log le is created in an inventory table (ECPAO_ASDNLD_INV) to track the download activities
performed by a user.

Task overview: Data Extraction and Transfer [page 320]

Implementing Data Migration and Replication to Employee Central

Data Migration and Replication to Employee Central PUBLIC 333
Related Information

Sequence of Data Extraction and Import Steps for Dierent Object Types [page 321]
Extracting Organizational Data [page 324]
Extracting Organizational Data in Multiple Steps [page 331]
Extracting Changed Organizational Data Using Delta Replication [page 334]
Replicating Organizational Data to Custom Entities in Employee Central [page 336]
Parallelization of Organizational Data Extraction Via Job Scheduler Report [page 337]
Extraction of Inactive Organizational Objects [page 340]

2.3.1.3.5.5 Extracting Changed Organizational Data Using Delta

Replication

After the initial run of the organizational data extraction program, changed data is replicated using delta replication.
Here's how you need to set this up.

Prerequisites

You can only use the transformation template groups with the Web Service Transfer communication channel for
delta replication.

Context

When administrator change organizational data in the SAP S∕4HANA system, change pointers are created. The
Creating IDoc Type from Change Pointers (RBDMIDOC) program (or BD21 transaction) reads the change pointers
with the ECPAO_OM message type, replicates the changed data using the data extraction program, and marks the
change pointers as processed.

Data extraction program choose the transformation template group from the VC_ECPAO_MAP view cluster. In
the view cluster, while creating the transformation template group or after creating, the transformation template
group can be enabled for delta replication. You need to choose Enable for Delta Replication option to enable the
delta replication. For more information see: Creating a Transformation Template Group for Employee Data topic.
Additionally, you can choose a subset of transformation templates from the group for delta replication by enabling
the Enable for Delta Replication option in the V_ECPAO_VARIANT view.

This replication only identies the changes which are maintained directly on an object. By implementing the
HRALE00CHANGE_PTRS BAdi, you can now capture the changed inherited objects and which can be stored in the
change pointers table BDCP2. Any changes in the position, organizational units, cost center, and jobs (For ex: cost
center assigned to an organization unit is changed.) can be stored in the changed pointers table. When you run
the data extraction report you can see these changes as well. For example coding, you can refer to the SAP note:
2399459.

Implementing Data Migration and Replication to Employee Central

334 PUBLIC Data Migration and Replication to Employee Central
  Note

The data replication does not use Application Link Enabling (ALE) or IDocs. The RBDMIDOC program uses the
ECPAO_OM message type to trigger the replication of changed organizational data to Employee Central using a
synchronous Web service call.

In SAP S∕4HANA, all infotype data is eective dated. In Employee Central, some data, such as email or phone
information, isn't eective dated. If you change data in SAP S∕4HANA for the future that isn't eective dated
in Employee Central, the corresponding change pointers will only be executed at this future date. For any text
changes, you can use the delta enablement option.

Procedure

1. Go to the Dene Background Job (SM36) transaction.

2. Schedule the Creating IDoc Type from Change Pointers (RBDMIDOC) program as a regular background job using
the ECPAO_OM message type.

Change Pointers for the ECPAO_OM Message Type

Task overview: Data Extraction and Transfer [page 320]

Related Information

Sequence of Data Extraction and Import Steps for Dierent Object Types [page 321]
Extracting Organizational Data [page 324]
Extracting Organizational Data in Multiple Steps [page 331]
Downloading CSV Files from the Application Server [page 332]
Replicating Organizational Data to Custom Entities in Employee Central [page 336]
Parallelization of Organizational Data Extraction Via Job Scheduler Report [page 337]
Extraction of Inactive Organizational Objects [page 340]

Implementing Data Migration and Replication to Employee Central

Data Migration and Replication to Employee Central PUBLIC 335
2.3.1.3.5.6 Replicating Organizational Data to Custom Entities
in Employee Central

Here's an overview of the steps involved when you want to transfer data from SAP S∕4HANA to a custom entity in
Employee Central.

Prerequisites

You have created a custom generic object in Employee Central. You can do this in the Admin Center by choosing the
Congure Object Denitions tool. When you create your entity, make sure to set the API Visibility option to Editable.

Procedure

1. Import the metadata for your custom entity from Employee Central into the SAP S∕4HANA system.

a. Download the metadata from your custom entity in Employee Central.

• To download metadata of the CSV File-Based Transfer type::
1. Go to the Admin Center and choose the Import and Export Data tool.
2. In the Select the action to perform eld choose Download Template.
3. Select your object denition in the Select Generic Object eld and choose Download.
• To download metadata of the Web Service Transfer type:
1. Go to the Admin Center and choose the OData API Data Dictionary tool.
2. A list of entities is displayed.
If your custom entity isn't shown here, go back and choose the OData API Metadata Refresh and
Export tool, then choose Refresh.

OData API Metadata Refresh and Export Tool

3. Expand your custom entity and copy the complete content of the table displayed below Fields,
including the table header.
4. Paste the content to a spreadsheet and save the spreadsheet using the .csv le extension.
b. Import the metadata into the SAP S∕4HANA system using one of the metadata import programs.
2. Dene an Employee Central template for your custom entity.
3. Map the elds of your Employee Central entity to the transformation template.

Implementing Data Migration and Replication to Employee Central

336 PUBLIC Data Migration and Replication to Employee Central
Task overview: Data Extraction and Transfer [page 320]

Related Information

Sequence of Data Extraction and Import Steps for Dierent Object Types [page 321]
Extracting Organizational Data [page 324]
Extracting Organizational Data in Multiple Steps [page 331]
Downloading CSV Files from the Application Server [page 332]
Extracting Changed Organizational Data Using Delta Replication [page 334]
Parallelization of Organizational Data Extraction Via Job Scheduler Report [page 337]
Extraction of Inactive Organizational Objects [page 340]

2.3.1.3.5.7 Parallelization of Organizational Data Extraction Via

Job Scheduler Report

For migrating a large number of organizational data to Employee Central you can use the Job Scheduler report.
This report will automatically divide the load into smaller batches and schedule multiple background jobs, which
can be executed in parallel.

Prerequisites

You should have already congured the settings for running the organizational data extraction report.

Context

When you execute the report, it will automatically divide the load into smaller batches and schedule multiple
background jobs for each batch. The scheduler report performs the jobs in batches. When you run it initially, the
program extracts all organizational data for the selected objects that you have dened using the transformation
template group specied on the selection screen of the program. This report reduces the execution time of the
complete migration process for a large number of organizational data.

The extraction process updates the change pointers (if available) of the successfully migrated PERNR's, and marks
the change pointers as processed.

Implementing Data Migration and Replication to Employee Central

Data Migration and Replication to Employee Central PUBLIC 337
Procedure

1. Go to the Organizational Objects Data Migration (ECPAO_JOB_SCHED_OM) transaction to run the Organizational
Objects Data Migration (ECPAO_OM_OBJ_DMT_JOB_SCHEDULER) program.

The program extracts organizational data from the SAP S∕4HANA system based on your selection criteria.
2. Specify for which objects the data is to be extracted. To do so, either specify the object type or the object IDs.
3. Specify the number of objects that need to be replicated per job and the number of jobs that has to be
performed in parallel. At any given time, the scheduler job will perform the number of jobs mentioned in the
Max no. of jobs eld in parallel when a single or multiple jobs are completed.

 Note

The maximum number of Objects Per Job is 100 and the Max No. of Jobs is 50. The default Max No. of
Jobs is 10. If the number of objects per job and the maximum number of jobs exceeds the limit, you would
receive a warning message

4. Select the transformation template group to be used for the data extraction. Transformation template groups
are dened in the VC_ECPAO_MAP_OM view cluster.
5. Select the variant ID that you have created before in the Dene the Variant IDs for Data Migration customizing
activity (view V_ECPAO_VARIANT). Once you have created the variant ID, you should have assigned the
required transformation templates to the variant ID using the Dene the Transformation Templates for a Variant
ID customizing activity (view V_ECPAO_TEMP_VAR).

 Note

This is not a mandatory eld. You can choose the Variant ID if you want to perform the extraction in multiple
steps. For more information, see: Extracting Organizational Data in Multiple Steps [page 331].

For example, a transformation template group consists of the 5 transformation templates (ERP1, ERP2, ERP3,
ERP4, and ERP5). In these templates if you want to choose only ERP1, ERP3, and ERP5, you can create a
variant ID for these transformation templates. And when you choose this variant ID for migration process, only
these transformation templates (ERP1, ERP3, and ERP5) would be considered.
6. Specify how you would like to transfer the data:
• By Web Services, using the middleware that is available for the Employee data migration from SAP
S∕4HANA to Employee Central. You can only use this option if the transformation template group you
specify uses the Web Service Transfer communication channel.
• Using an application server.

 Note

You can specify an addition to the le name to prevent existing les from being overwritten by new
les by entering a le identier. If you don't enter a le identier, the same le name is used for each
download so that existing les are overwritten.

7. Select the Detailed Message Log checkbox if you want to get a detailed log containing all messages.

The download log le shows all the success, error, and warning messages. It will also include the number of les
that were downloaded and from where the le is downloaded from.

Please note that the les might contain personal and sensitive data. Additional authorization is performed to
check if the user has the right to download the CSV le. Only specic authorized users should be allowed

Implementing Data Migration and Replication to Employee Central

338 PUBLIC Data Migration and Replication to Employee Central
 for this operation. The downloads that are triggered by a user to the application server or local server in
Production mode and in Test Run (Download Payload) are logged via table ECPAO_OBJ_DWNLD along with the
timestamp and transformation template details.

The below authorizations are required to be able to download the CSV les:

Authorizations
Authorization Object Authorization Field Authorization Value

S_DATASET(for application server) ACTVT 34

S_DATASET(for application server) FILENAME /usr/*

S_DATASET(for application server) PROGRAM CL_ECPAO_FILE_ON_SERVER*

ECPAO_OM_OBJECT_EXTRACTION

S_TABU_NAM ACTVT 02

S_TABU_NAM TABLE ECPAO_OBJ_DWNLD

8. Select the Failed Objects Only checkbox if you want to re run the replication for only those objects for which the
replication status has failed. The number of jobs created will be based on the number of failed organizational
objects.

Task overview: Data Extraction and Transfer [page 320]

Related Information

Sequence of Data Extraction and Import Steps for Dierent Object Types [page 321]
Extracting Organizational Data [page 324]
Extracting Organizational Data in Multiple Steps [page 331]
Downloading CSV Files from the Application Server [page 332]
Extracting Changed Organizational Data Using Delta Replication [page 334]
Replicating Organizational Data to Custom Entities in Employee Central [page 336]
Extraction of Inactive Organizational Objects [page 340]

2.3.1.3.5.7.1 Monitoring Organizational Migration Status using

Job Scheduler Report

You can monitor the Organizational migration status using the Job Scheduler Report.

You can check the intermediate status of the current set of completed and running jobs using the SM37
transaction. You can check the output using the SM37 transaction by entering “*” in the job name and user name
eld. You can enter the user name who will be executing the operation.

Since organizational migration has been executed in multiple batches, the ongoing migration status analysis
is possible based on the already completed jobs. Once a single job is completed, the migration status

Implementing Data Migration and Replication to Employee Central

Data Migration and Replication to Employee Central PUBLIC 339
information for those PERNR's and the relevant templates will be stored in the inventory tables (ECPAO_INVT
& ECPAO_INVT_MSG). And you can execute the ALV report (ECPAO_OM_INVENTORY_ALV) to get the status of all
the objects for which extraction has already happened.

The naming convention of the jobs would be like: DMOM_RUN_S_JOB_1, DMOM_RUN_S_JOB_2,

DMOM_RUN_S_JOB_3 etc, where "S" is the File Identier that you have mentioned in the report screen.

 Note

After executing the report when you view the jobs using the SM37 transaction, do not cancel the jobs, which are
in process. This denotes the migration of the employees belonging to that job is still in process.

2.3.1.3.5.8 Extraction of Inactive Organizational Objects

ERP system might have delimited organization objects which does not exist until the end of time (31.12.9999). In
this case when you replicate the data to Employee Central system has to send an inactive record since the last
active date to 31.12.9999.

For example you have a position in ERP system which is present from 01.01.2010 to 31.12.2015. Then the replication
process generates an additional job code record from 01.01.2016 to 31.12.9999 with status as “I” indicating inactive
status. This is done in order to ensure that in EC, the organization object is inactive in that duration. To generate the
additional inactive record at the end, the values of all elds from the last active period are copied over.

However based on the congurations in EC, some eld values will no longer be valid during the inactive period.

For example the parent position does not exist in EC during the inactive period of the child position.
In this case, you need to clear the value of parent position eld in the inactive period using the BAdI
EX_ECPAO_ERP_EMP_DATA_MODIFY. To clear or modify the values of such elds, you can implement the
EX_ECPAO_ERP_EMP_DATA_MODIFY BAdI. In the IMG structure open SAP Customizing Implementation Guide
Personnel Management Integration with SuccessFactors Employee Central Business Integration Builder

Implementing Data Migration and Replication to Employee Central

340 PUBLIC Data Migration and Replication to Employee Central
 Business Add-Ins (BAdIs) Data Transfer to Employee Central BAdI: Change of Mapping Result for Data
Replication to EC .

Parent topic: Data Extraction and Transfer [page 320]

Related Information

Sequence of Data Extraction and Import Steps for Dierent Object Types [page 321]
Extracting Organizational Data [page 324]
Extracting Organizational Data in Multiple Steps [page 331]
Downloading CSV Files from the Application Server [page 332]
Extracting Changed Organizational Data Using Delta Replication [page 334]
Replicating Organizational Data to Custom Entities in Employee Central [page 336]
Parallelization of Organizational Data Extraction Via Job Scheduler Report [page 337]

2.3.1.4 Extensibility of the Integration

Parent topic: Replicating Organizational Data from SAP S∕4HANA to Employee Central [page 270]

Related Information

For Which Organizational Data-Related Employee Central Entities Can I Use Data Replication? [page 271]
Communication Channels for Organizational Data Replication [page 272]
Steps in the SAP S∕4HANA System [page 275]
Data Replication and Mapping Information [page 346]

Implementing Data Migration and Replication to Employee Central

Data Migration and Replication to Employee Central PUBLIC 341
2.3.1.4.1 Implementing Business Add-Ins to Enhance the
Replication

You can use Business Add-Ins (BAdIs) to adapt the data replication from SAP S∕4HANA to Employee Central to
your specic requirements.

Procedure

1. Optional: Implement Validity Periods for Data Replication to EC (EX_ECPAO_EMP_VALIDITY_TAB) BAdI to

exclude the employee/organizational object data that is extracted from the ERP system, based on a specic
criteria. This BAdI can be used only for excluding data after cut-o date. For details, refer to the BAdI
documentation at Business Integration Builder Business Add-Ins (BAdIs) BAdI: Validity Periods for Data
Replication to EC .

 Caution

Filtering of the employee data for extraction should be done only for country.

2. If you have selected the BAdI Mapping mapping mode Customizing activity, you must implement the Mapping
of EC and ERP Data for Data Replication to EC (EX_ECPAO_EMP_DATA_EXTRACT_OUT) BAdI.

Your BAdI implementation must provide the mapping for all elds for which you have selected this mapping
mode. Using this BAdI, you read the relevant SAP S∕4HANA data based on any condition or calculation you
dene and map it to an Employee Central eld ID.
3. Optional: If you want to overwrite the data that is extracted from the SAP S∕4HANA system, implement the
Change of Mapping Result for Data Replication to EC (EX_ECPAO_ERP_EMP_DATA_MODIFY) BAdI.

2.3.1.4.2 Chief Positions in Organizational Data Integration

Between Employee Central and SAP S∕4HANA

How to support the SAP S∕4HANA concept of chief positions when integrating Employee Central and SAP
S∕4HANA.

The chief position relationship used by SAP S∕4HANA is the Manages... / Is managed by... (012) relationship
between the manager position (object type S) and the organizational unit (object type O). All employees assigned
to the organizational unit are assigned the holder of this position as manager. This chief position concept, however,
isn’t used in Employee Central. The concept used by Employee Central corresponds to the Reports (line) to / Is line
supervisor of (002) relationship between the manager and the employee position in SAP S∕4HANA. That's why you
need to make some adjustments if you want to use the chief position concept in Employee Central integration.

 Note

The Reports (line) to / Is line supervisor of (002) relationship is transferred with the replication of employee
organizational assignments to the SAP S∕4HANA system. Disable the replication of this relationship if you want
to use the Manages... / Is managed by... (012) relationship instead. There are dierent ways to do this:

Implementing Data Migration and Replication to Employee Central

342 PUBLIC Data Migration and Replication to Employee Central
 • If you use congurable replication of organizational assignments, simply don't congure the relationship
between the employee position and the manager position in the customizing activity Dene Relationship
Mapping for Position.
• If you use the non-congurable approach to replicate organizational assignments, add the EC to ERP:
Omit Pos.-Manager Rel. in Non-Cong. Org Assignm constant in the customizing activity Maintain Constant
Values for Data Replication from EC.

Adding and Downloading Chief Position Custom Field in Employee Central [page 343]
Add a chief position custom eld to the object denition in Employee Central and download the metadata
of the changed object denition.

Conguring Chief Position for Data Migration from SAP S∕4HANA to Employee Central [page 344]
Congure the use of chief positions when migrating data from SAP S∕4HANA to Employee Central.

2.3.1.4.2.1 Adding and Downloading Chief Position Custom

Field in Employee Central

Add a chief position custom eld to the object denition in Employee Central and download the metadata of the
changed object denition.

Context

We use the Department object denition as an example.

Procedure

1. In SAP SuccessFactors, log on to your Employee Central company.

2. Go to the Admin Center and choose the Congure Object Denitions tool.
3. In the rst Search eld, choose Object Denition.
4. In the second Search eld, choose Department.

5. Choose Take Action Make Correction .

6. Scroll down to add a custom chief position eld.
7. In the Data TypeGeneric Object, then choose Details.
8. In the Valid Values Source eld, select Position.
9. Choose Done and save the changed object denition.
10. Download the metadata of the changed object denition using the OData API Metadata Refresh and Export
admin tool.

Implementing Data Migration and Replication to Employee Central

Data Migration and Replication to Employee Central PUBLIC 343
Results

Your custom eld is available for upload to the SAP S∕4HANA.

Next Steps

Congure chief position in SAP S∕4HANA for data replication from Employee Central.

2.3.1.4.2.2 Conguring Chief Position for Data Migration from

SAP S∕4HANA to Employee Central

Congure the use of chief positions when migrating data from SAP S∕4HANA to Employee Central.

Prerequisites

You've added a custom eld for chief position in Employee Central and downloaded the corresponding object
denition.

Context

We use Department as an example, which is represented by an organizational unit in SAP S∕4HANA.

Procedure

1. Map the elds you need for data migration to Employee Central in SAP S∕4HANA.

a. Go to Customizing for the Business Integration Builder and choose Data Migration and Replication to
Employee Central Organizational Data Field Mapping for Organizational Data Replication to Employee
Central Dene Transformation Template Group for Organizational Data .
b. Create a transformation template group for the Employee Central instance that you use and select the Web
Service Transfer communication channel for it. Don't ll in the other elds.

You can choose any name and description for your template group. Let's call it CHIEF_POS_TO_EC in this
example.
c. Go to Dene Field Mapping for Organizational Data.
d. Create a transformation template within your template group.

Implementing Data Migration and Replication to Employee Central

344 PUBLIC Data Migration and Replication to Employee Central
 e. Select the Is Active checkbox and the Employee Central entity WS_OM_DEP.
f. Don't select the Merge Records checkbox.

You can choose any name and description for your transformation template. Let's call it ERP_DEPARTMENT
in this example.
g. Select Primary Mapping and map the chief position custom eld and the department name.

Employee SAP S∕4HANA Value Mapping

Central Field Mapping Mode Evaluation Path Infotype Infotype Field Entity

cust_chief_posi- Evaluation Path B012 – – WS_POSITION

tion Mapping

name_default- Infotype Mapping – 1000 STEXT –

Value

2. Create a department that has a chief position assigned in SAP S∕4HANA.

a. Go to the Maintain Object (PP01) transaction.
b. Select Current Plan in Plan Version.
c. Select Organizational Unit in Object Type.
d. Select the Object infotype and choose Create.
e. Enter the dates as applicable for your department should in Validity.
f. Enter any abbreviation in Object Abbrevation.
g. Enter any name in Object Name.
h. Save your new department and make a note of its ID.
i. Choose the Allowed Relationships pushbutton to select the chief position relationship for your department.
j. Enter B and 012 in Relationship Type.
k. Select Position in Type of Related Object.
l. Enter the ID of a position that exists in Employee Central (meaning, which you replicated from Employee
Central before) in ID of Related Object.
m. Save the relationship.
3. Replicate the new department together with its chief position relation to Employee Central.
a. Go to the Organizational Data Extraction (ECPAO_OM_EXTR) transaction.
b. Select O (Organizational Unit) in Object Type.
c. Enter the ID of the department that you created earlier in Object ID.
d. Select the transformation template that you created earlier.

In our example, it was the ERP_DEPARTMENT template.

e. Clear the Test Run checkbox.
f. Select the Web Service Transfer communication channel.
g. Execute the program.

You're shown a success message.

Implementing Data Migration and Replication to Employee Central

Data Migration and Replication to Employee Central PUBLIC 345
Results

The Department object that you created in SAP S∕4HANA is now available in Employee Central and has a Chief
Position eld.

Next Steps

Check the replication result in Employee Central. Go to Admin Center and choose the Manage Data tool. In the rst
Search eld, choose Department, in the second Search eld, choose the department you created in SAP S∕4HANA
and transferred to Employee Central. Your department is shown. Check whether the Chief Position eld is lled with
the position you assigned to your department in SAP S∕4HANA, using the B012 relationship

2.3.1.5 Data Replication and Mapping Information

Parent topic: Replicating Organizational Data from SAP S∕4HANA to Employee Central [page 270]

Related Information

For Which Organizational Data-Related Employee Central Entities Can I Use Data Replication? [page 271]
Communication Channels for Organizational Data Replication [page 272]
Steps in the SAP S∕4HANA System [page 275]
Extensibility of the Integration [page 341]

2.3.1.5.1 Non-Congurable (Standard) Employee Central

Fields

Standard elds aren't available for conguration in Customizing, independent of which communication channel you
use.

A default mapping is dened for these elds, which you can't change.

Implementing Data Migration and Replication to Employee Central

346 PUBLIC Data Migration and Replication to Employee Central
Standard Fields for CSV File-Based Entities
Employee Central En-
tity Standard Fields

BUSINESS_UNITIm- externalCode status start-date

portTemplate

DIVISIONImportTem- externalCode status start-date

plate

DEPARTMENTImport- externalCode status start-date end-date

Template

JOB_CLASSIFICATIO- Job Code status start-date end-date

NImportTemplate

Position Code eectiveStatus start-date

Standard Fields for Web Service-Based Entities

Employee Central En-
tity Standard Fields

FOBusinessUnit externalCode status startDate

FODivision externalCode status startDate

FODepartment externalCode status startDate endDate

FOJobCode Job Code Status startDate endDate

Position Code eectiveStatus Start Date

2.3.1.5.2 Non-Congurable (Standard) Mapping of SAP

S∕4HANA Fields to Employee Central Field IDs

Standard mappings aren't available for conguration in Customizing, independent of which communication
channel you use. They are automatically added to the mappings you dene.

Mappings dened for Business Unit entity

Employee Central Field ID SAP S∕4HANA system Field or Entry

Code Object ID (OBJID) eld of the Object (1000) infotype

Status Value A for Active

Implementing Data Migration and Replication to Employee Central

Data Migration and Replication to Employee Central PUBLIC 347
Employee Central Field ID SAP S∕4HANA system Field or Entry

Start Date Start Date (BEGDA) eld of the Object (1000) infotype

Mappings dened for Division entity

Employee Central Field ID SAP S∕4HANA system Entry

Code Object ID (OBJID) eld of the Object (1000) infotype

Status Value A for Active

Start Date Start Date (BEGDA) eld of the Object (1000) infotype

Mappings dened for Department entity

Employee Central Field ID SAP S∕4HANA system Field or Entry

Code Object ID (OBJID) eld of the Object (1000) infotype

Status Value A for Active

Start Date Start Date (BEGDA) eld of the Object (1000) infotype

End Date End Date (ENDDA) eld of the Object (1000) infotype

Mappings dened for Job Classication entity

Employee Central Field ID SAP S∕4HANA system Field or Entry

Job Code Object ID (OBJID) eld of the Object (1000) infotype

Status Value A for Active

Start Date Start Date (BEGDA) eld of the Object (1000) infotype

End Date End Date (ENDDA) eld of the Object (1000) infotype

Implementing Data Migration and Replication to Employee Central

348 PUBLIC Data Migration and Replication to Employee Central
Mappings dened for Position entity

Employee Central Field ID SAP S∕4HANA system Field or Entry

Code Object ID (OBJID) eld of the Object (1000) infotype

Status Value A for Active

Start Date Start Date (BEGDA) eld of the Object (1000) infotype

2.3.1.5.3 Sample Mapping of SAP S∕4HANA Fields to

Employee Central Fields

Some sample transformation template groups are dened for the Employee Central company SBS_MODEL in the
delivered sample Customizing. These transformation template groups provide some mappings of SAP S∕4HANA
elds and Employee Central eld IDs.

• SBS_OM_MODEL_CSV
This is an example for organizational data replication using the CSV File-Based Transfer communication
channel.
• SBS_OM_MODEL_WS
This is an example for the replication of organizational data using the Web Service Transfer communication
channel.

You can copy the delivered sample Customizing and use it as an example for your own eld mappings.

 Note

We also provide sample content, which contains congurable standard eld mappings, in the Dene Field
Mapping for Organizational Data Customizing step. When you dene a eld mapping there, you can easily copy
these standard eld mappings using a pushbutton and then adapt them if necessary.

2.4 Foundation Objects

2.4.1 Replicating Foundation Object Data from SAP S∕4HANA

to Employee Central

This section describes in detail which steps need to be carried out when you want to replicate foundation objects
data from SAP S∕4HANA to Employee Central.

There are two types be which you can replicate the foundation obects: BIB based and BAdI implementation based.

Implementing Data Migration and Replication to Employee Central

Data Migration and Replication to Employee Central PUBLIC 349
2.4.1.1 Congurable Data Replication

You can migrate foundation objects as per your requirement by conguring the transformation template group,
transformation template, and developing the BAdI implementations.

This process involves extracting data of foundation objects from S/4 HANA system and migrating it to
SAPSAP SuccessFactors Employee Central (EC) using the program ECPAO_FO_OBJ_EXTRACTION. It replicates
the foundation objects data by making use of transformation template group congurations dened using the view
cluster VC_ECPAO_MAP_FO.

SAP has delivered a standard set of foundation objects (Pay Component, Pay Component Group, & Company)
together with Sample Content and Example BAdI Implementation. In addition to that, you can also migrate
additional foundation objects as per your requirement by conguring the transformation template group and
transformation template and developing the BAdI implementations.

Please ensure that below preparatory steps are completed before proceeding with the replication of foundation
data:

• Dene Additional Employee Central Entities for Foundation Objects

• Import Metadata for Web Service-Based Data Transfer from Employee Central
• Dene Transformation Template Group for Foundation Objects
• Dene Field Mapping for Foundation Objects

This program is developed to select the foundation objects and trigger the upsert to Employee Central system
based on the objects selected in the selection screen. It replicates the foundation objects data by making use of the
Primary Mappings that are dened for an EC Entity. It supports the following mapping modes:

• Table Mapping – This could be chosen when we have conguration T-table eld that acts as a direct data
source for the mapped eld. This currently supports the whitelisted set of T-tables that are listed in the
database table ECPAO_TABLE_LIST. Other conguration tables that are not part of this table are currently not
supported and are not allowed to be chosen for table mapping.
• BAdI Mapping for Integration/Migration to EC - This could be chosen when we do not have a direct data source
that could be used for mapping and instead must rely on the BAdI implementation to fetch the details for
the mapped eld. You must implement the BAdI EX_ECPAO_FO_MAP_DATA for mapping the corresponding
Employee Central eld of the corresponding foundation object.

You could also specify Value Mapping Entity to map SAP SAP SuccessFactors Employee Central eld values to
values of ERP elds.

This program can be either executed in test run or production run mode and it displays the results via Application
Logs with statistics for each run, listing how many objects were processed successfully and how many with failures.
You can use the Analyse Inventory of migrated Foundation Object Data (ECPAO_FO_INVENTORY_ALV) program to
check the replication status per foundation object.

2.4.1.1.1 Supported Standard Foundation Data Related

Employee Central Entities

Read about the standard set of foundation objects that is delivered by SAP.

SAP has delivered a standard set of foundation objects: Pay Component, Pay Component Group, and Legal Entity.

Implementing Data Migration and Replication to Employee Central

350 PUBLIC Data Migration and Replication to Employee Central
Below are the EC Entity details that are packaged along with the service pack together with sample content and a
sample BAdI implementation. The replication currently works only with web service transfer mode.

EC Entity Entity Name in EC EC Entity Description

WS_FO_LEG FOCompany EC Entity for FO Legal Entity

WS_FO_PC FOPayComponent EC Entity for Pay Component

WS_FO_PCG FOPayComponentGroup EC Entity for Pay Component Group

Here's the details of the sample content delivered from SAP:

Legal Entity
EC Field EC Field Description ERP Table ERP Field BAdI Mapping

country Country T001 LAND1 -

currency Currency T001 WAERS -

externalCode Legal Entity ID T001 BUKRS -

name_defaultValue Legal Entity Name T001 BUTXT -

standardHours Standard Weekly Hours - - Yes

startDate Start Date - - Yes

status Status - - Yes

Pay Component
EC Field EC Field Description ERP Table ERP Field BAdI Mapping

externalCode Pay Component ID - - Yes

canOverride Can Override - - Yes

currency Currency - - Yes

description Description T512T LGTXT -

endDate End Date T511 ENDDA -

description Description T512T LGTXT -

status Status - - Yes

payComponentType Pay Component Type - - Yes

startDate Start Date T511 BEGDA -

isEarning Is Earning - - Yes

frequencyCode Frequency - - Yes

recurring Recurring - - Yes

isEndDatedPayment isEndDatedPayment - - Yes

maxFractionDigits Maximum Decimal Pla- - - Yes

ces

name Name T512T LGTXT -

Implementing Data Migration and Replication to Employee Central

Data Migration and Replication to Employee Central PUBLIC 351
Pay Component Group
EC Field EC Field Description ERP Table ERP Field BAdI Mapping

externalCode Pay Component Group - - Yes

ID

name Name T52D6 WGRTX -

description Description T52D6 WGRTX -

startDate Start Date - - Yes

endDate End Date - - Yes

status Status - - Yes

showOnCompUI Display on Comp UI - - Yes

useForComparatioCalc Use for Comparatio Cal- - - Yes

culation

currency Currency - - Yes

useForRangePenetra- Use for Range Penetra- - - Yes

tion tion

payComponentFlx Pay Component ID - - Yes

In addition to the above sample content, sample implementation has been provided as part of the implementation
example class CL_ECPAO_MAP_FO_DATA_VIA_BADI to support the standard foundation objects replication.

2.4.1.1.2 Steps in the SAP S∕4HANA System

In the next sections we'll go step by step through all activities you need to carry out in the SAP S∕4HANA system to
make data replication work.

Implementing Data Migration and Replication to Employee Central

352 PUBLIC Data Migration and Replication to Employee Central
2.4.1.1.2.1 Accessing the Customizing Structure in the SAP
S∕4HANA System

To dene customer-specic settings, you use the Customizing activities and Business Add-Ins (BAdIs) in the
integration of SAP S∕4HANA and SAP SuccessFactors Employee Central (ECS4HCM) add-on.

In your SAP S∕4HANA system, go to the Customizing: Execute Project (SPRO) transaction and choose SAP
Reference IMG. In the SAP Customizing Implementation Guide structure, open Personnel Management
Integration with SuccessFactors Employee Central Business Integration Builder :

Overview of Customizing Structure

In the Customizing structure, you can nd detailed information for each Customizing activity and BAdI:

Details of Customizing Structure

The next sections describe the steps you need to carry out in the SAP S∕4HANA system.

Implementing Data Migration and Replication to Employee Central

Data Migration and Replication to Employee Central PUBLIC 353
2.4.1.1.2.2 Importing Metadata from Employee Central

You import the metadata from SAP SuccessFactors Employee Central to make Employee Central elds available in
the SAP S∕4HANA system so that you can use them for eld mappings.

Context

To import metadata, use Import of Metadata from Employee Central Using XML File
(ECPAO_ECTMPL_METADATA_WRITER).

This program is available in the Import Metadata for Web Service-Based Data Transfer from Employee Central
Customizing activity.

Using this program, you can import entries as well as delete entries you have imported for a specic SAP
SuccessFactors instance and template.

 Note

You can't delete metadata in the SAP S∕4HANA system that you have already used for eld mappings.
Otherwise your mappings become invalid. You are shown an error message if you try to delete metadata that is
used for eld mappings.

Procedure

1. Download the metadata that you want import from Employee Central.

a. Go to the Admin Center and choose the OData API Data Dictionary tool.

OData API Metadata Refresh and Export Tool

b. Click Refresh to make sure that the metadata is upto date.
c. Click Export to export the Export Metadata to File and store the metadata le in the XML format on a
server or on your local disk.

 Note

API tools need to be enabled in Provisioning.

Implementing Data Migration and Replication to Employee Central

354 PUBLIC Data Migration and Replication to Employee Central
  Remember

As a customer, you don't have access to Provisioning. To complete tasks in Provisioning, contact
your implementation partner or Account Executive. For any non-implementation tasks, contact Product
Support.

 Note

When a new eld is added in Employee Central, you will have to re-import the metadata report and re-run
the report once again.

2. On the selection screen of the program, specify which metadata you want to import to SAP S∕4HANA and from
which le you want to upload it:

Selection Screen of the ECPAO_ECTMPL_METADATA_WRITER Program

 Note

If you don't specify a specic Employee Central entity, the metadata is imported for all Employee Central
entities that are available and use the Web Service Transfer communication channel.

3. Optional: Carry out a test run of the program to check the data that will be uploaded to SAP S∕4HANA.
4. Clear the Test Run checkbox and execute the program to upload the data from the Employee Central metadata
le into the EC Entity Field Mapping (ECPAO_FLD) table.

If you run the program in a test system or client with the Test Run checkbox deselected, the program asks for
a transport request, to which the imported metadata will be assigned. Using this request you can transport the
entries to the productive system or client.

 Note

The standard elds are also uploaded into the EC Entity Field Mapping table. In this table, the Is Standard
Field (IS_FLD_STANDARD) ag is set for these elds. Since a standard mapping is dened for them, they
are not available in the Customizing of the transformation template groups.

Implementing Data Migration and Replication to Employee Central

Data Migration and Replication to Employee Central PUBLIC 355
5. Optional: To delete the entries you have imported for the Employee Central instance and template that you
have specied on the selection screen, select the Delete Metadata checkbox and execute the program. This will
make sure that the WS based and File based transfer will be consistent.
6. Check the metadata that you have imported in the Transport Imported Metadata and Check Metadata for
File-Based Data Transfer Customizing activity.

 Tip

For details about which information about the Employee Central elds exactly is imported by the
program, see the program documentation in your SAP S∕4HANA system. You'll nd a link to the program
documentation in the documentation of the Import Metadata for Web Service-Based Data Transfer from
Employee Central Customizing step.

Transport Imported Metadata and Check Metadata for File-Based Data Transfer

 Note

Don't make any changes to the metadata in this Customizing view. Use the metadata import program to
update the entries in this view.

 Caution

If the Employee Central eld has Picklist ag is set for an imported Employee Central eld, you might need
to assign a value mapping entity when you dene a eld mapping for this Employee Central eld. Otherwise
the data extraction program might fail.

7. You can also store entries from this view on a transport request, for example, to transport them from your SAP
S∕4HANA test system to your productive system. To do so, choose Table View Transport .

Implementing Data Migration and Replication to Employee Central

356 PUBLIC Data Migration and Replication to Employee Central
2.4.1.1.2.3 Conguring Replication of Language-Dependent
Fields

Congure the replication of texts (such as names or descriptions of organizational objects) between SAP S∕4HANA
and Employee Central.

To enable replication of texts (name, descriptions etc) related elds, you need to select the Lang. Mapping indicator
and map the eld to the corresponding text table in the Primary Mapping view of the VC_ECPAO_MAP_FO view
cluster. The Lang. Mapping Indicator is enabled only for language dependent text elds. These could be Name and
Description related text elds. The SAP S∕4HANA Language that is maintained for the default locale mapped to
Employee Central is used for fetching the values.

2.4.1.1.2.4 Transferring Language-Dependent Fields

Make the settings required to enable transfer of texts (such as names or descriptions of foundation objects)
between SAP S∕4HANA and Employee Central.

Prerequisites

You can only transfer texts for an Employee Central locale if the corresponding language pack was enabled in
Provisioning for Employee Central.

 Remember

As a customer, you don't have access to Provisioning. To complete tasks in Provisioning, contact your
implementation partner or Account Executive. For any non-implementation tasks, contact Product Support.

Implementing Data Migration and Replication to Employee Central

Data Migration and Replication to Employee Central PUBLIC 357
Context

To enable replication of texts in language maintained againt the default Employee Central, you rst map language-
independent text elds in the primary mapping with Lang. Mapping indicator.

Procedure

1. In Customizing for Personnel Management, choose Integration with SuccessFactors Employee Central
Business Integration Builder Data Migration and Replication to Employee Central Foundation Object Data
Map Languages from Employee Central and ERP to map Employee Central locales to SAP S∕4HANA
languages. Here's what you need to do there:
a. Dene a mapping for the default locale you use in Employee Central.

 Example

If your default locale is en_US, enter:

Mapping the Default Employee Central Locale

Employee Central Locale SAP S∕4HANA Language

en_US EN

 Note

Make sure that you use the correct format:

• The language dependent text is extracted only for the default locale.
• The default locale identier from Employee Central must consist of a language identier in
lowercase and a location or country/region identier in uppercase, linked by an underscore.
For example: en_US (English, USA), en_GB (English, UK), fr_FR (French, France), fr_CA (French,
Canada).
• The language identier from SAP S∕4HANA must be a two-character country/region ISO code. For
example: EN, FR.
• Currently no additional locales are supported for translation of texts.

If you don't dene at a language mapping for the default locale, user’s logon language is used, and
language-dependent data can be transferred.

2. Go to Dene Locale Settings for Employee Central Instance in the same Customizing structure to specify which
of the mapped locales is your default Employee Central locale.

 Example

The eld help in the Employee Central instance view shows the locales you've mapped in the rst step:
• en_US

You select en_US.

Implementing Data Migration and Replication to Employee Central

358 PUBLIC Data Migration and Replication to Employee Central
 Example: Dening the Default Locale for Your Employee Central Instance

Results

Data transfer between Employee Central and SAP S∕4HANA uses the language mapped against default EC Locale
for getting the values. If not maintained, then user’s logon language is used to fetch the value.

2.4.1.1.2.5 Dening Organizational Data-Related Settings for

Your Employee Central Company

Make additional settings for the Employee Central instance you've dened before in the Dene Organizational Data
Settings for Employee Central Company Customizing activity (view V_ECPAO_CMPNY_OM).

Procedure

1. Choose your Employee Central instance ID.

2. Specify the company's default locale as you've dened it in Employee Central (for example, en_US).

To enable transfer of text elds (such as names or descriptions) between SAP S∕4HANA and Employee Central,
you need to map this default locale to an SAP S∕4HANA language such as EN.

2.4.1.1.2.6 Dening Custom Employee Central Entities for

Foundation Object Data Entities

An Employee Central entity represents an entity from Employee Central, such as a CSV data import template or a
generic object (also known as MDF entity). You only need to dene custom Employee Central entities if you want to
transfer data from SAP S∕4HANA to an Employee Central entity for which SAP hasn't provided a default template.

Implementing Data Migration and Replication to Employee Central

Data Migration and Replication to Employee Central PUBLIC 359
Context

In the Dene Additional Employee Central Entities for Foundation Objects Customizing activity (view
V_ECPAO_ECTMPL_F) you can also see the default templates dened by SAP. If the default templates suit your
requirements, there's no need to dene any custom templates.

Details of an Employee Central Template

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

Procedure

1. Dene the basic settings.

a. Enter a unique entity ID and a description. The ID has to be in the customer namespace, which means that
it has to start with a number (0* - 9*). You can enter any description.
b. Enter the entity name. You must use the exact name of the corresponding entity in Employee Central.

To nd out about the name for generic objects, go to the Admin Center and choose the OData API Data
Dictionary tool.
c. Select the communication channel Web Service Transfer).
d. Enter the key eld.
2. Dene the Validation Table details.
a. Enter the validation table details and click Maintain Table and Fields.

Implementing Data Migration and Replication to Employee Central

360 PUBLIC Data Migration and Replication to Employee Central
 b. Choose the validation eld from the list.
c. Click New Entries if you want to add a new table eld. Or select elds you want, and make one of the elds
as Key eld.

2.4.1.1.2.7 Dening Field Mapping for Foundation Objects

To enable the data extraction programs to extract the right SAP S∕4HANA information for the right Employee
Central elds, you need to map SAP S∕4HANA elds to Employee Central elds.

To map elds, you go to the Dene Field Mapping for Foundation Objects Customizing step, which has the
VC_ECPAO_MAP_FO view cluster assigned. The conguration in this view cluster is done in several steps:

1. You create at least one transformation template group. A template group bundles all eld mappings that
you want to use when running the data extraction program. This is the entity that you specify on the
program selection screen. From the transformation template group the data extraction program determines all
information it needs to extract data from SAP S∕4HANA elds and map it to Employee Central eld IDs.
2. You create at least one transformation template for your transformation template group. A transformation
template groups information from the SAP S∕4HANA system that belongs together logically. It is the SAP
S∕4HANA counterpart of the Employee Central entity.
3. You dene a primary mapping for each of your transformation templates. This means you choose Employee
Central eld IDs from the Employee Central entity assigned to the transformation template, and you map
suitable SAP S∕4HANA elds to these Employee Central eld IDs.

2.4.1.1.2.7.1 Creating a Transformation Template Group for

Foundation Objects

A template group bundles all eld mappings that you want to use when transferring data from SAP S∕4HANA to
Employee Central.

Context

To dene template groups, you go to the Dene Transformation Template Group for Foundation Objects Customizing
step, which has the V_ECPAO_TTG_FO view cluster assigned.

Procedure

1. Click New Entries

2. Enter a name and description for the transformation template group.
3. Assign it to the Employee Central instance dened in the Specify Employee Central Instance ID Customizing
activity view (V_ECPAO_COMPANY).

Implementing Data Migration and Replication to Employee Central

Data Migration and Replication to Employee Central PUBLIC 361
  Note

EC Instance is a read only eld when you are editing or copying the transformation template group. You will
be able to modify or choose the EC Instance only when you are creating a new transformation template
group.

2.4.1.1.2.7.2 Dening Templates to Map Foundation Objects

Fields

The transformation template is the counterpart of the Employee Central entity. You can map elds from the
transformation template to elds from the assigned Employee Central entity.

Context

To dene a set of transformation templates for each transformation template group, you go to the Transformation
Templates view of the VC_ECPAO_MAP_FO view cluster.

Transformation Templates Assigned to a Transformation Template Group

Details of a Transformation Template

Implementing Data Migration and Replication to Employee Central

362 PUBLIC Data Migration and Replication to Employee Central
These are the settings that you need to make for each transformation template you dene:

Procedure

1. Enter a name and description for the template.

2. Select the Is Active checkbox to dene that the template is to be used for data extraction.
3. Assign one of the default Employee Central entity or a custom Employee Central entity that you've created
before.

2.4.1.1.2.7.3 Dening the Primary Field Mapping for Foundation

Objects

You can choose Employee Central elds from the Employee Central data model that you've uploaded to the SAP
S∕4HANA system, and you map suitable SAP S∕4HANA elds to these Employee Central eld IDs.

Context

To dene a eld mapping for each transformation template, you go to the Primary Mapping view of the
VC_ECPAO_MAP_FO view cluster.

 Note

There are predened standard mappings, which are automatically added to the templates you use and aren't
available for conguration in this Customizing activity.

Here's how to map elds:

Procedure

1. Choose an Employee Central eld from the assigned Employee Central template.

 Note

• For Mapping mode as Table Mapping, the system allows to choose only a set of whitelisted tables.

 Tip

The system table ECPAO_TABLE_LIST contains the currently supported conguration tables.

• While creating a foundation object entity, a primary table is assigned along with one key eld which
identies the foundation object.

Implementing Data Migration and Replication to Employee Central

Data Migration and Replication to Employee Central PUBLIC 363
 • When conguring the table mapping for the above FO entity, only those whitelisted tables which has
the same key as dened above should be used. Whitelisted tables with dierent keys are restricted to
be used.

2. Map each Employee Central eld to an SAP S∕4HANA eld using a suitable mapping mode:
• When you select the mapping mode Table Mapping, you can map an Employee Central xxxxx.
• When you select the mapping mode BAdI Mapping for Integration/Migration to EC, you can
use an implementation of the Mapping of EC and ERP Data for Data Replication to EC
(EX_ECPAO_EMP_DATA_EXTRACT_OUT) BAdI to dene the eld mapping.
3. If the value from the SAP S∕4HANA eld needs to be converted into an Employee Central value, enter the value
mapping entity that you have dened in the Dene Value Mapping Entities Customizing step.

 Note

You can dene the value mappings for this entity directly from here by choosing Dene Value Mapping
Entries.

2.4.1.1.2.7.4 How to Use the Sample Content for Foundation

Objects

We provide sample content for dierent use cases in the Dene Field Mapping for Foundation Objects Customizing
step, which you can copy and adapt to your needs.

Context

You can copy the sample content for the required foundation objects according to your need.

Procedure

1. Create a transformation template group and select the sample content that you want to use for it.
2. In your transformation template group, create transformation templates for all entities you want to use and
assign the corresponding Employee Central entities. You can create the transformation templates by using the
Copy Sample Content button at the each transformation template level.

You can use the Copy Sample Content button to copy the transformation templates and the corresponding
Primary Mapping congurations for the relevant Employee Central entities. To see the entries copied to the
Primary Mapping view, you need to click the Save button to save and view all the congurations. Which eld
mappings are copied depends on the sample content you have selected for the transformation template group.

Which eld mappings are copied depends on the sample content you have selected for the transformation
template group.
3. If needed, adapt the copied sample content to suit your requirements. You can, for example, delete mappings
you don't need, change the mapped eld, or add new mappings.

Implementing Data Migration and Replication to Employee Central

364 PUBLIC Data Migration and Replication to Employee Central
  Note

Once you have made custom entries in the Primary Mapping view (either by copying and adapting the
sample content or by making your custom entries from scratch), you can no longer copy the sample
content. If you have dened custom mappings and decide that you want to use the mappings provided by
the sample content instead, delete the transformation template and create a new template.

If you have already dened eld mappings in the previous releases, you can continue to use them without
any changes. However, if you want to replace your custom mappings with mappings provided with the
sample content, create new transformation templates for all entities for which you want to use the sample
mapping. Then continue as described above. Remove your existing transformation templates for the same
entities from the transformation template group or clear the Is Active checkbox for them so that the new
transformation templates are used instead.

2.4.1.1.2.8 Dening Value Mappings

Value mapping means that Employee Central eld values are mapped to values of SAP S∕4HANA elds.

The data extraction programs use the value mappings when extracting data. They replace the SAP S∕4HANA keys
by the corresponding Employee Central keys if a value mapping is dened for the corresponding eld mapping.
Value mappings are assigned to eld mappings in the Primary Mapping view of the eld mapping view cluster. Field
mappings are grouped together in a transformation template group. You enter the transformation template group
on the selection screen to tell the extraction program which eld mappings and which value mappings it is to use.

There are standard value mappings provided by SAP. Standard value mappings are provided for values that can't be
congured in the SAP S∕4HANA system and in Employee Central and therefore always stay the same.

 Example

Language codes can't be congured. The Employee Central language code English always corresponds to the
language code EN in the SAP S∕4HANA system. Therefore, a standard value mapping is provided for language
codes.

However, if you want to map values that can be congured in the SAP S∕4HANA system and in Employee Central,
you need to dene custom value mappings.

 Note

After copying the new value mapping entries, don’t save the entries immediately, but press the page down
button to see all the entries. You must click the page down button until you see the last set of entries. Once you
see the last set of entries, you can save all the newly created entries.

Implementing Data Migration and Replication to Employee Central

Data Migration and Replication to Employee Central PUBLIC 365
2.4.1.1.2.8.1 Dening Value Mapping Entities

A value mapping entity combines a set of value mappings for a specic purpose.

Context

You dene value mapping entities in the Dene Value Mapping Entities Customizing step (view
V_ECPAO_VALUENTY). The easiest way to create value mapping entities is to copy the sample entities by choosing
the Copy Sample Value Mapping pushbutton. You can also create country specic value mapping entries and create
a new value mapping entity using the Create Value Mapping Entity and Dene Ctry. Spec. Value Mapping Entries
pushbuttons from the primary mapping details screen.

Copy Sample Value Mapping

 Tip

If you want to check rst which sample value mapping entities are available, choose the Show Sample Value
Mapping pushbutton.

Create Value Mapping Entity/Dene Country Specic Value Mapping Entries

You'll get a list of all standard entities provided for the integration, which you can adjust to your needs.

Implementing Data Migration and Replication to Employee Central

366 PUBLIC Data Migration and Replication to Employee Central
Procedure

1. To create a value mapping entity from scratch, enter a name and description. If you want to use a standard
entity, you need to keep its name, but you can adjust the description.
2. Specify how the values are to be mapped. If you want to use a standard entity, we recommend that you use the
suggested mapping types.
• Picklist mapping using the Picklist - External Code eld from the picklist
Use this type if the picklist value you want to map is an External Code. This is the case for most of the
picklists.
3. To make available picklist values you've imported to the SAP S∕4HANA system from Employee Central in the
value mapping details, assign a picklist to the value mapping entity.

This enables you to choose the imported picklist values in the Employee Central Key eld when you actually
map the values. If you don't assign a picklist, you can still enter keys in the Employee Central Key eld, but you
can't choose from the imported picklist values.
4. To make available input help values from an infotype eld in the value mapping details, specify the SAP
S∕4HANA value help.

This is a combination of the technical name of the infotype table (such as PA0002) and the technical name of
the infotype eld (such as GESCH), connected with a hyphen (as in PA0002-GESCH). This means that you can
choose the input help values from the Gender Key (GESCH) eld of the Personal Data (0002) infotype in the
ERP Key eld when you actually map the values. It does not mean that you can only use the value mapping
entity for the GESCH eld. If you want to use a sample entity, we recommend that you use the suggested SAP
S∕4HANA value helps.
SAP S∕4HANA Value Help Assigned to Value Mapping Entity

2.4.1.1.2.8.2 Dening Value Mapping Details

The value mapping details actually map SAP S∕4HANA values to the corresponding Employee Central values.

Procedure

1. Go to the Dene Value Mapping Details Customizing activity (view V_ECPAO_VALENTY).

2. Map SAP S∕4HANA keys and the corresponding Employee Central keys.

If the value mapping entity has a picklist ID and a SAP S∕4HANA value help assigned, you can select suitable
picklist values in the EC Key eld and corresponding input help values in the ERP Key eld.

Implementing Data Migration and Replication to Employee Central

Data Migration and Replication to Employee Central PUBLIC 367
 Choose SAP S∕4HANA Key for Value Mapping

Choose Employee Central Key for Value Mapping

You can also enter the wildcard * in the ERP Key eld. If only the wildcard is dened in the value mapping
details, any SAP S∕4HANA value will be mapped to the Employee Central key for the eld that uses this value
mapping entity. If the wildcard is dened in addition to specic SAP S∕4HANA keys, the system rst checks for
the specic keys. If an Employee Central key is mapped to a specic SAP S∕4HANA key, this mapping is used.
For all other SAP S∕4HANA values, the Employee Central key mapped to the wildcard is used.

Results

The data extraction programs can now use the value mappings. When extracting data, they will replace the SAP
S∕4HANA keys by the assigned Employee Central keys if a value mapping is dened for the corresponding eld
mapping. If no value mapping is available, they won't map any values for the specic eld and use the values from
SAP S∕4HANA as they are.

Implementing Data Migration and Replication to Employee Central

368 PUBLIC Data Migration and Replication to Employee Central
2.4.1.1.2.9 Data Replication and Mapping Information

2.4.1.1.2.9.1 Non-Congurable (Standard) Employee Central

Fields

Standard elds aren't available for conguration in Customizing, independent of which communication channel you
use.

A default mapping is dened for these elds, which you can't change.

Standard Fields for FO EC Entity

Employee Central Entity Standard Fields

FOCompany startDate

FOPayComponent startDate

FOPayComponentGroup startDate

2.4.1.1.3 Data Extraction and Transfer

This section describes in detail which steps need to be carried out when you want to replicate foundation objects
from the SAP S∕4HANA system to Employee Central.

Context

You can now replicate the foundation objects to Employee Central. SAP has delivered a standard set of foundation
objects (Pay Component, Pay Component Group, & Company). In addition to that, you can also migrate additional
Foundation Objects as per your requirement. You need to run the ECPAO_FO_OBJ_EXTRACTION report for
replicating the foundation object to Employee Central. You could choose the foundation objects either based on
country grouping or objects specied in the screen.

Procedure

1. Go to the Foundation Object Data Extraction (ECPAO_FO_EXTR) transaction to run the Foundation Object Data
Extraction (ECPAO_FO_OBJECT_EXTRACTION) program.

The program extracts foundation object data from the SAP S∕4HANA system based on your selection criteria.

Implementing Data Migration and Replication to Employee Central

Data Migration and Replication to Employee Central PUBLIC 369
 Selection Screen of the ECPAO_FO_OBJECT_EXTRACTION Program

On the selection screen:

• Select the transformation template group to be used for the data extraction.
• Select the transformation template to be used for the data extraction based on the foundation object.
Based on the selected transformation template group and transformation template, the specic
Foundation Object’s Input Key eld with value help will be displayed.
• Choose the country grouping for which you want to transfer the Foundation Object type.
• Choose the country grouping for which you want to transfer the Foundation Object type.
• Choose Test Run checkbox if you want to run the report in test or production run mode.

 Note

• You can carry out a test run of the program rst to check if the data can be extracted from SAP
S∕4HANA without errors.
• If you carry out a productive run, the program extracts the data.

2. The program updates the following tables:

• Inventory of Replicated Foundation Objects-BIB (ECPAO_FO_B_INVT)

Implementing Data Migration and Replication to Employee Central

370 PUBLIC Data Migration and Replication to Employee Central
 This table holds information about when the data of which employee was replicated to Employee Central,
such as:

Sample Entry in the ECPAO_FO_B_INVT Table

Time Stamp (Uni-

Employee Central In- External Code of versal Coordinated
stance EC Entity Foundation Object Time) Replication Status

ECINT WS_FO_LEG 0001 20.220.625.063.810,4 S

298650 = 2015 March
25, 6:38 (plus sec-
onds, milliseconds,
microseconds, and
the rst decimal of
the nanoseconds)

• Inventory of Replicated Foundation Objects - Messages- BIB (ECPAO_FO_B_INVTM)

This table holds the error messages issued for the replication by Employee Central or by SAP S∕4HANA,
per Employee Central template, such as:

Sample Entry in the ECPAO_FO_B_INVTM Table

Type of Message
External Code Returned by Up-
Employee Employee of Foundation Sequence Num- sert of Founda-
Central Instance Central Entity Object ber tion Object Message Text

ECINT WS_FO_LEG 001 1 E Invalid ENUM

value: 'ACTIVE1'

 Tip

Use the Status of foundation object with EC entity BIB (ECPAO_FO_INVENTORY_ALV) program to check
these tables.

3. The program displays the results as Application Logs.

Implementing Data Migration and Replication to Employee Central

Data Migration and Replication to Employee Central PUBLIC 371
 The application log le shows all the success and error messages. It will also include the number of foundation
objects that were successfully extracted or replicated and for how many foundation objects the extraction or
the replication process has failed.

2.4.1.2 Non-Congurable Data Replication

You can extract foundation objects data from S/4 HANA system and migrating it to SAP SuccessFactors Employee
Central (EC) using the program ECPAO_TRANSFER_FO_OBJ_TO_EC.

This program is developed to select the foundation objects and trigger the Upsert to Employee Central system
based on the objects selected in the selection screen. It migrates the foundation data by making use of
enhancement spot ES_ECPAO_EMP_DATA_EXTRACT_OUT and the BAdI implementations created based on the
business requirements.

You can use this BAdI to read the data from the S/4 HANA database tables and map it with the Employee Central
elds for the foundation objects. SAP has delivered active BAdI implementations for the following foundation
objects delivered in the standard set - Pay Component, Pay Component Group, & Company. You can nd
the list of standard foundation objects delivered by SAP for migrating data to Employee Central in the view
V_ECPAO_FO_UPS. However, any changes to the elds of these standard foundation objects which are to be
considered for extraction would mean changes to these BAdI implementations.

You can dene any additional foundation objects for migrating data to Employee Central that are not delivered
as part of the standard set using the view V_ECPAO_FO_UPS. After dening the new foundation object, you must
implement the BAdI EX_ECPAO_MAP_FOBJ_TRANS_TO_EC for mapping the corresponding Employee Central eld
of the corresponding foundation object. Once you activate the BAdI implementation, you need to run this program
for migrating that foundation object to Employee Central.

You can specify if you want to carry out a test run or production run. If you run this program in a test system or
client and haven't selected the Test Run checkbox, the program asks for a transport request.

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 objects and
related attributes into a CSV le 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.

You can use the Analyse Status of Foundation Object Replication (ECPAO_INVENTORY_FOR_FND_OBJ) program to
check the replication status per Foundation Object.

Implementing Data Migration and Replication to Employee Central

372 PUBLIC Data Migration and Replication to Employee Central
2.4.1.2.1 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 elds 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 Data Migration and Replication to Employee
Central Business Add-Ins 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 eld.
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 Employee Central.
7. Dene whether the program is to carry out a test run rst.

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 dened 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 Objects

Implementing Data Migration and Replication to Employee Central

Data Migration and Replication to Employee Central PUBLIC 373
 and related attributes into a CSV le 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.

2.4.1.2.1.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/Percent- T511 KOMBI

age/Number

number If payComponentType
is Number then these
elds (elds 8, 9, 10)
are to be lled

unitOfMeasure T511 ZEINH

Rate

isEarning 0/1 T511 OPKEN

Implementing Data Migration and Replication to Employee Central

374 PUBLIC Data Migration and Replication to Employee Central
 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 using
the separator ‘|’

Implementing Data Migration and Replication to Employee Central

Data Migration and Replication to Employee Central PUBLIC 375
Legal Entity

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

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 eld 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 eld DE-
FAULT_LOCALE

status Status ACTIVE/INACTIVE

defaultPayGroup Default Pay Group

 Note
This is not a man-
datory eld

defaultLocation Default Location

 Note
This is not a man-
datory eld

Implementing Data Migration and Replication to Employee Central

376 PUBLIC Data Migration and Replication to Employee Central
 EC Field EC Field Description Accepted Values in EC ERP Table ERP feld

standardHours Standard Weekly Hours It is a numeric for exam-

ple 40
 Note
It is set 40 in stand-
ard

Currency Currency T001 WAERS

Country Country T005 INTCA3

NameFormatGO.exter- Name Format

nalCode

 Note
This is not a man-
datory eld

In case you need a dierent mapping logic for any of the elds or need to include an additional eld, then you can
disable the default active BAdI implementation and create your own custom BAdI implementation.

2.4.1.2.2 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 eld of the corresponding foundation object. You also need to set the lter 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 specied in the screen.

Implementing Data Migration and Replication to Employee Central

Data Migration and Replication to Employee Central PUBLIC 377
Procedure

1. Go to the V_ECPAO_FO_UPS view to add your own foundation objects and click New Entries.
2. Enter the Object type.
3. Enter the text that you want for the new foundation object that you are adding.
4. Enter the Employee Central entity name for the new foundation object.
5. Enter the table name and eld name in the Validation Table Name for FO and Validation Table Field Name for FO
eld. These are optional eld.

When these elds are lled with valid table and eld 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 eld name in this view is used to validate the input entered in the
selection screen of the report. In case these two elds are not lled, then only the option Transport request is
enabled.

 Note

By using the navigational elds 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
elds for entering the names of the linked objects.

2.4.1.2.3 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 Foundation

Implementing Data Migration and Replication to Employee Central

378 PUBLIC Data Migration and Replication to Employee Central
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 specic 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 specic time frame you're interested in, select the Select Data Based on Time Range
checkbox and enter a From and To date and time. The date and time provided correspond to the system time
zone.

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

Results

In the result, you'll rst 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 specied in your
selection criteria), together with the replication status and the time stamp of when they were replicated. The
timestamp displayed correspond to the system time zone. 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).

Implementing Data Migration and Replication to Employee Central

Data Migration and Replication to Employee Central PUBLIC 379
3 Migrating Data to Employee Central

3.1 Employee Data

3.1.1 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 denes 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. By default,
active employment details are used when you migrate the data to SAP S∕4HANA system.

For replicating data to SAP S∕4HANA, infotype split is not a prerequisite. An employee is ltered out based on the
employment status during the migration of the employee master data.

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

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/mi-
future until December 31, 9999)... For this use case... gration...

Active Employee was active during initial load Considered

and is still active.

Employee was inactive during initial load Considered

and changed to active state after initial
load.

Employee was retired during initial load Considered

and changed to active state after initial
load.

Implementing Data Migration and Replication to Employee Central

380 PUBLIC Migrating Data to Employee Central
 If employment status on cutover date
is (and no change is coming up in the Data is considered for integration/mi-
future until December 31, 9999)... For this use case... gration...

Inactive Employee was active during initial load Considered

but was changed to inactive state after
initial load.

Employee was inactive during initial load Not considered

and is still inactive.

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

Employee was withdrawn during initial Not considered

load and changed to retired state after
initial load.

Employee was inactive during initial load Not considered

and changed to retired state after initial
load.

Withdrawn Employee was active during initial load Considered (default position is not trans-
and changed to withdrawn state after ini- ferred, but the last valid position would
tial load. be transferred to Employee Central)

Employee was inactive during initial load Not considered

and changed to withdrawn state after ini-
tial load.

Employee was moved from retired to Not considered

withdrawn state.

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

Implementing Data Migration and Replication to Employee Central

Migrating Data to Employee Central PUBLIC 381
3.1.2 Sequence of Data Extraction and Import Steps for
Dierent Object Types

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

Prerequisites

Make sure that the Parent eld is not a required eld 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.

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 eld 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 elds from SAP S∕4HANA to department elds in Employee Central. You assign the
Employee Central entity DEPARTMENTImportTemplate to both of the transformation templates and map the
elds as shown below.

DEPARTMENT_WO_PARENT

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

Name Infotype Mapping 1000 STEXT

Code BAdI Mapping

DEPARTMENT_W_PARENT

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

Name Infotype Mapping 1000 STEXT

Implementing Data Migration and Replication to Employee Central

382 PUBLIC Migrating Data to Employee Central
 Employee Central
Field Mapping Mode Infotype Subtype SAP S∕4HANA Field

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 elds
to department elds and that does not map the Parent eld. Deselect this checkbox for the other
transformation template that you use for mapping organizational units (the one that contains the Parent
eld).

 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 eld since you've set the
Is Active checkbox for this transformation template. The other transformation template, which maps the
Parent eld, 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 classications 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
elds from SAP S∕4HANA to job classication elds 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 elds from SAP S∕4HANA to position elds 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 elds to
department elds and that maps the Parent eld. Deselect this checkbox for the other transformation
template that you use for mapping organizational units (the one that doesn't contain the Parent eld).

Implementing Data Migration and Replication to Employee Central

Migrating Data to Employee Central PUBLIC 383
  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 eld since you've set the Is
Active checkbox for this transformation template. The other transformation template, which doesn't map
the Parent eld, 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 rst 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 elds from SAP S∕4HANA to job classication elds 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 elds from SAP S∕4HANA to position elds in
Employee Central.

3.1.3 Importing Organizational Data into Employee Central

Learn how to upload CSV les containing organizational data to Employee Central.

Prerequisites

You have extracted the data from the SAP S∕4HANA system into CSV les 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
Dierent Object Types.

Procedure

1. Go to the Admin Center.

Implementing Data Migration and Replication to Employee Central

384 PUBLIC Migrating Data to Employee Central
 2. Choose the Import and Export Data tool.

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 le containing the data that was extracted from the SAP S∕4HANA system.
7. Select the Full Purge purge type.
8. Choose Import.

3.1.4 Importing Employee Data into Employee Central

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

Prerequisites

You have extracted the data from the SAP S∕4HANA system into CSV les using the Employee Data Extraction
(ECPAO_EMPL_EXTRACTION) program. For more information about the data extraction program, refer to
Replicating Employee Data from SAP S/4HANA to Employee Central.

Context

Make sure that you follow the sequence we recommend for data extraction and import and that you upload the
CSV les for the dierent employee data entities in the recommended order. For more information, refer to For
Which Employee Data-Related Employee Central Entities Can I Use Data Replication? in Replicating Employee Data
from SAP S/4HANA to Employee Central, where you can nd a sequence number for each employee data entity.

Implementing Data Migration and Replication to Employee Central

Migrating Data to Employee Central PUBLIC 385
 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 les, select the Composite (Zip) Data
Upload option.

3.1.5 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 set up work schedule rules in your SAP S∕4HANA system.

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

You have to make sure that the Upsert Data from SAP ERP or SAP S4HANA to SAP SuccessFactors Employee
Central Using the OData API integration ow from the SAP ERP or SAP S/4HANA Integration with SAP
SuccessFactors Employee Central: Employee and Organizational Data integration package is set up when you use
SAP Cloud Integration as the middleware.

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

Implementing Data Migration and Replication to Employee Central

386 PUBLIC Migrating Data to Employee Central
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)

Here's an overview of the tables in Employee Central SAP S∕4HANA:

Work Schedule Rules: Tables in SAP S∕4HANA

Implementing Data Migration and Replication to Employee Central

Migrating Data to Employee Central PUBLIC 387
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 denes 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 eld – 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.
• 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. Dene 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 specic day variant assigned (meaning, for which the Daily Work Schedule
Variant (VARIA) eld in the Daily Work Schedule (T550A) table is not empty).
• You can omit work schedule rules that use multiple daily work schedule variants.
4. Dene 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) eld in the Break Schedules (T550P) table has
an entry other than 0).
5. Select the time recording variant.

Implementing Data Migration and Replication to Employee Central

388 PUBLIC Migrating Data to Employee Central
 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 eld
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.

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 congurations.
• 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 ex time bandwidths in the day work schedule. Hence the
report skips the work schedules which have at least one such day work schedule.
6. Dene whether the program is to carry out a test run rst.

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 dened 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.

Implementing Data Migration and Replication to Employee Central

Migrating Data to Employee Central PUBLIC 389
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 rst eight characters of the
external key from Employee Central to the Work Schedule Rule (SCHKZ) eld in SAP S∕4HANA.

3.1.6 Employee Having Global Assignment in SAP ERP HCM

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

In SAP S∕4HANA, you should 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 should use the Details on Global
Assignment (0710) infotype. This infotype is mandatory to be maintained for the infoporter tool to identify the
global assignment employment type. Else the HR process is identied incorrectly.
• To determine which personnel number is used to send biographical and personal information to Employee
Central, you should 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. 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 dened a cuto date for data replication, this can aect the start date of the global assignment: If
the cuto date is later than the actual start date of the global assignment, the cuto date is used. If the cuto
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.

Implementing Data Migration and Replication to Employee Central

390 PUBLIC Migrating Data to Employee Central
  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 there is a global assignment from PERNR 1 to PERNR 2, the personal information (infotype 0002), Global
information (0002 or its secondary infotypes), 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 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 Employee Central, you will have to make sure that the host address type is available in the Employee
Central 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 Employee Central system.

 Note

Emp_users_sys_id eld should be added into perAddress enitity with the congurations: Enabled = True,
Visibility = view & allow import = Yes in the Employee Central system. This eld has to be included in the
view cluster (VC_ECPAO_MAP) eld 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 is always extrated from the home PERNR only irrespective of the
employment status.
• 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 if it is inactive.

Implementing Data Migration and Replication to Employee Central

Migrating Data to Employee Central PUBLIC 391
  Note

When global assignment conguration 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 Employee Central will be
deleted as the upsert is a full purge.

3.1.7 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 eort is required while replicating the data into
Employee Central. In contrast, the CSV-based data replication mode is a two-step process, where the les have
to be rst downloaded and then imported manually into the Employee Central.
• 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 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 eort. 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 les will be downloaded to a pre-dened 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 le 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 eld level attributes are not available in the CSV metadata les.

3.1.8 Migrating Pay Calendar to Employee Central

You can migrate the pay calendar data to Employee Central. You will have to rst export the pay calendar data
information from SAP ERP and then import the data to Employee Central.

Implementing Data Migration and Replication to Employee Central

392 PUBLIC Migrating Data to Employee Central
3.1.8.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 le.

Context

You can do this by running the Export Payroll Calendar Dates (PAOCF_EC_PAY_CALENDAR_INFO) report.

Procedure

1. Go to transaction SE38.
2. Enter program: PAOCF_EC_PAY_CALENDAR_INFO.
3. On the Selection Criteria screen:

• Enter the Country Grouping.

• Choose the Payroll Area in ERP.
• Enter the From Payroll Year.
• Enter the To Payroll Year.
4. On the Value Mapping Details:

• Choose EC Instance from the F4 help for the EC Instance ID with which the value mapping entity is
associated.
• Choose Value Mapping Entity that should be used for fetching the EC paygroup code values for the given
ERP payroll areas.

 Note

Value mapping entity should be of type Generic Object Key. If no value mapping entity name is
specied, then payroll area mappings are not considered.

5. On the Download Options:

• If you select the Use Server Path option, you can later transfer the data from the application server location
to a local drive.

 Note

Default option to download the report le is application server.

• If you select the Use Local Drive Path option, you must specify where the CSV le is to be stored.

Pay Calendar report supports downloading the pay calendar information into a CSV le either to application
server or local drive. The download log le shows all the success, error, and warning messages. It will also
include the number of les that were downloaded and from where the le is downloaded from.

Implementing Data Migration and Replication to Employee Central

Migrating Data to Employee Central PUBLIC 393
  Note

Please note that the les might contain sensitive data. Additional authorization is performed to check if
the user has the right to download the CSV le. Only specic authorized users should be allowed for this
operation. The downloads that are triggered by a user to the application server or local server are logged
via table ECPAO_OBJ_DWNLD along with the timestamp details.

Further, it is your responsibility for the retention and deletion of these les from the application server or
local machine.

The below authorizations are required to be able to download the CSV les:

Authorization Object Authorization Field Authorization Value

S_DATASET(for application server) ACTVT 34

S_DATASET(for application server) FILENAME /usr/*

S_DATASET(for application server) PROGRAM CL_ECPAO_FILE_ON_SERVER*

PAOCF_EC_PAY_CALENDAR_INFO

S_TABU_NAM ACTVT 02

S_TABU_NAM TABLE ECPAO_OBJ_DWNLD

6. Execute the report to export the Pay Calendar information into a csv le.

Results

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

Implementing Data Migration and Replication to Employee Central

394 PUBLIC Migrating Data to Employee Central
  Example

3.1.8.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 eld, enter Import and Export Data.
2. Choose Import Data.

Implementing Data Migration and Replication to Employee Central

Migrating Data to Employee Central PUBLIC 395
3. Choose Pay Calendar.
4. Choose Incremental Load.
5. Click Choose File to browse for the csv le.
6. Click Import.

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

Implementing Data Migration and Replication to Employee Central

396 PUBLIC Migrating Data to Employee Central
3.1.9 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.

3.1.9.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 set up work schedule rules in your SAP S∕4HANA system.

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

Implementing Data Migration and Replication to Employee Central

Migrating Data to Employee Central PUBLIC 397
You have set up the middleware. Make sure that the Upsert Data from SAP ERP or SAP S4HANA to SAP
SuccessFactors Employee Central Using the OData API integration ow from the SAP ERP or SAP S/4HANA
Integration with SAP SuccessFactors Employee Central: Employee and Organizational Data integration package is
set up.

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)

Implementing Data Migration and Replication to Employee Central

398 PUBLIC Migrating Data to Employee Central
Here's an overview of the tables in Employee Central SAP S∕4HANA:

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 denes 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 eld – 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.
• 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.

Implementing Data Migration and Replication to Employee Central

Migrating Data to Employee Central PUBLIC 399
 • 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. Dene 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 specic day variant assigned (meaning, for which the Daily Work Schedule
Variant (VARIA) eld in the Daily Work Schedule (T550A) table is not empty).
• You can omit work schedule rules that use multiple daily work schedule variants.
4. Dene 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) eld 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 eld
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.

Handling of day schedules with Flextime across midnight:

Implementing Data Migration and Replication to Employee Central

400 PUBLIC Migrating Data to Employee Central
 • 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 congurations.
• 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 ex time bandwidths in the day work schedule. Hence the
report skips the work schedules which have at least one such day work schedule.
6. Dene whether the program is to carry out a test run rst.

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 dened 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 rst eight characters of the
external key from Employee Central to the Work Schedule Rule (SCHKZ) eld in SAP S∕4HANA.

Implementing Data Migration and Replication to Employee Central

Migrating Data to Employee Central PUBLIC 401
3.1.9.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:

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 skips

Implementing Data Migration and Replication to Employee Central

402 PUBLIC Migrating Data to Employee Central
 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 data record 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 specic 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 record for the work schedule rule in SAP S∕4HANA, using the same start date as for the new day
model record.
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 data records 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

You assign this work schedule in an employee's Job Information.

Implementing Data Migration and Replication to Employee Central

Migrating Data to Employee Central PUBLIC 403
 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.

 Note

Planned working hours dene the duration of an employee's working time. If planned working hours of a day
model in ERP is 0, then no work schedule day model is created in Employee Central. The Work Schedule Day
Model Assignment is sent with category OFF denoting non-working day.

WorkScheduleDayModelSegment

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

3.1.9.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 eld with a key that is concatenated from the values of the following elds 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)

Implementing Data Migration and Replication to Employee Central

404 PUBLIC Migrating Data to Employee Central
  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 rst 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 denition 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 elds. You can access the customizing activity at Personnel
Management Integration with SuccessFactors Employee Central Business Integration Builder Data Migration
and Replication to Employee Central Business Add-Ins BAdI: Mapping of External Code during the Work
Schedule Migration .

Work Schedule Day Model

When creating the WorkScheduleDayModel object, the program populates the externalCode eld with a key that is
concatenated from the values of the following elds 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..

Implementing Data Migration and Replication to Employee Central

Migrating Data to Employee Central PUBLIC 405
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

3.1.10 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 les. And you can run the migration for the remaining entities using the data migration tool. The
employee identier elds in Employee Central, user-id and person-id-external, have to be same in both the data
migration tool and in the CSV le-based migration from the third-party system. Meaning, the third-party CSV
les 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 block in Employee Central, such as
compensation and recurring pay components, personal info and global info, payment info details and
county specic 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 le-based imports either
for all related entities belonging to the same blocks in Employee Central or for none of them.

 Example

The compensation entity has this data record: January 1, 2012 to December 31, 9999. The recurring
pay components entity has this data record: 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 elds of an Employee Central entity from a third-party system and the remaining elds
of the same entity from SAP S∕4HANA system. In this scenario, you can store the data of the elds from the

Implementing Data Migration and Replication to Employee Central

406 PUBLIC Migrating Data to Employee Central
 third-party system using a custom table in the SAP S∕4HANA system. Then you can use the eld mapping BAdI
( EX_ECPAO_EMP_DATA_EXTRACT_OUT) to read the custom table and populate in the relevant elds of the
Employee Central entities.

3.1.11 Starting Data Replication from Employee Central to the

SAP S∕4HANA System

Once you've nished 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 lled 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 modied 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 specic 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 eld of the event
reason.

Implementing Data Migration and Replication to Employee Central

Migrating Data to Employee Central PUBLIC 407
 Event Reason in Employee Central

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 eects:
• 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 specied a
specic action in the Payroll Event eld, 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 rst Job History record in
Employee Central starting with July 1, 2015. This Job History record is created using a specic Cutover
event reason. Now you replicate this employee's data from Employee Central to SAP S∕4HANA. The data

Implementing Data Migration and Replication to Employee Central

408 PUBLIC Migrating Data to Employee Central
 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 eld of the Cutover event reason in Employee Central.

Note that if you don't specify the SAP S∕4HANA action in the Payroll Event eld 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.

3.1.12 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 le or in other formats. After
executing the transaction you can choose the required format in which you want to export the log le 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.

Implementing Data Migration and Replication to Employee Central

Migrating Data to Employee Central PUBLIC 409
  Note

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

Implementing Data Migration and Replication to Employee Central

410 PUBLIC Migrating Data to Employee Central
4 Side-by-Side Deployment Option

4.1 Introduction to the Side-By-Side Deployment Option

Get an overview of how to integration on-premise SAP S∕4HANA systems with SAP SuccessFactors Employee
Central using the Side-by-Side deployment option.

The Side-by-Side deployment option is for customers who want to transition their HCM system to the Cloud while
still leveraging investments into employee administration on premise. It comprises the coexistence of HR core in
the Cloud (SAP SuccessFactors Employee Central) and on premise (SAP S∕4HANA). In this scenario, Employee
Central is used as the cloud-based core HR system for a subset of employees. SAP S∕4HANA as still retained as
the core HR system for another subset of employees. Changes are being made in the system of record of the
employee's data. The core HR system landscape is inhomogeneous or distributed and needs to be consolidated to
enable centralized access, reporting, and so on.

The Side-by-Side deployment option comprises a regular web service-based replication of organizational and
employee-related data from SAP S∕4HANA to Employee Central. For more information about how to set up this
replication, see the following integration guides:

• Replicating Employee Data from SAP ERP HCM to Employee Central

• Replicating Organizational Data from SAP ERP HCM to Employee Central

Find the most current version of these guides at http://help.sap.com/hr_ecintegration.

 Restriction

The Side-by-Side deployment option is released under the condition that data replication from SAP S∕4HANA
systems to Employee Central is generally available for:

• Existing SAP SuccessFactors customers leveraging SAP SuccessFactors Performance & Goals, SAP
SuccessFactors Succession & Development, Employee Prole and Organization Chart as part of the
Foundational Capabilities, and the related Reporting capabilities.
• Net new SAP SuccessFactors customers who don't use any of the SAP SuccessFactors solutions yet,
but have implemented or plan to implement SAP SuccessFactors Employee Central for parts of their
organization.

 Note

This guide doesn't describe the Core Hybrid deployment option. The Core Hybrid deployment option means
that Employee Central is used as the system of record holding the employee data and reporting lines of
all employees, but existing processes such as Payroll, Time Management, or custom HR processes still run
in an SAP S∕4HANA on-premise system landscape. This deployment option is generally available. For more
information see 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

Implementing Data Migration and Replication to Employee Central

Side-by-Side Deployment Option PUBLIC 411
 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 SAP
Cloud Support for more information.

4.1.1 Business Scenario: Side-by-Side Deployment Option

The following is an example of a typical business scenario that takes advantage of the side-by-side deployment
option: The size and complexity of your enterprise don't allow for a one-step migration of your HCM systems to the
Cloud. Therefore, you plan to deploy certain countries step-by-step in the Cloud while keeping them integrated with
your productive on-premise SAP ERP HCM installations.

Some characteristics of the side-by-side deployment option are:

• The workforce is split across Employee Central and on-premise SAP ERP HCM. Both systems are used as a
system of record depending on the employee's country assignment.
• There can be multiple ERP systems which can store the employee data based on the employee country.
• HR processes run in the respective system of record while employee data is to be kept in sync across the
distributed HCM system landscape.
• UI mash-ups within Employee Central provide access to HR data and processes that are mastered in Employee
Central as well as in on-premise SAP ERP HCM.

Implementing Data Migration and Replication to Employee Central

412 PUBLIC Side-by-Side Deployment Option
4.2 How to Migrate from Talent Hybrid Integration to
Integration with Employee Central

This section is relevant if you want to start using the employee data replication from on-premise SAP ERP HCM
systems to SAP SuccessFactors Employee Central, where you have previously used either the integration add-on
for SAP ERP HCM and SAP SuccessFactors HCM Suite provided by SAP (also known as Talent Hybrid integration)
or another integration process to replicate employee data from an on-premise SAP ERP HCM system to the
Employee Prole in the SAP SuccessFactors Talent Suite.

If you are in this situation, you need to carry out the steps described in this section for all employees whose data
was previously replicated to the SAP SuccessFactors Talent Suite. This is necessary since the Human Resource
Information System (HRIS) synchronization (the exchange of data between Employee Central and other SAP
SuccessFactors modules) runs automatically for all employees in Employee Central (independent of whether
they are mastered in Employee Central or not) and can't be switched o. Since SAP SuccessFactors Employee
Central and the SAP SuccessFactors Talent Suite handle the users-sys-id and the person-id-external in dierent
ways, you need to make sure to ll these elds correctly in order to keep the employees' and managers' talent
processes history. When you replicate employee data to Employee Central, reuse the IDs for all employees who
were previously replicated to the SAP SuccessFactors Talent Suite.

Note that Talent Hybrid integration and HRIS synchronization between Employee Central and the SAP
SuccessFactors Talent Suite provide dierent values for elds:

• HRIS synchronization provides the values using the Name(Code) convention.

• Talent Hybrid integration provides either the eld name or the eld code/ID as a value.

This is important to know if you have implemented any processes based on eld values (such as ltering in reports
or role-based permissions).

You need to set the SFSFI SBSER switch to specify that you now using the employee data replication from
Enterprise Resource Planning (ERP) to SAP SuccessFactors Employee Central instead of the so called Talent
Hybrid integration using the Switch O Talent Hybrid Integration for Employee Data (ECPAO_VV_SFSFI_SBSER)
customizing activity.

You need to make settings in this Customizing activity if you have previously used the integration add-on for ERP
and SAP SuccessFactors HCM Suite to replicate employee data from an on-premise ERP system to the Employee
Prole in the SAP SuccessFactors Talent Suite (which is also known as Talent Hybrid integration). Setting the
switch tells your ERP system that employee data is no longer replicated to the Talent Suite, but to Employee
Central, and that the Employee Data Extraction (ECPAO_EMPL_EXTRACTION) program is used for the replication.

Migrating from Talent Hybrid Integration to ERP Integration when Assignment ID Field is Enabled [page 414]
This section tells you on how to update the assignment ID external eld for a user

Determining the User ID [page 420]

To replicate the correct users-sys-id from SAP S∕4HANA to Employee Central, implement the
GET_USERSYSID method of the Mapping of User ID, Person ID, Username, and Object ID
(EX_ECPAO_EMP_USYID_PRN_UNM_MAP) Business Add-In (BAdI).

Determining the Person ID [page 421]

When replicating the employee's data from SAP S∕4HANA to Employee Central, make sure to use the same
person-id-external as was previously used for replicating the employee's data to the SAP SuccessFactors
Talent Suite.

Handling the Dierent Integration Scenarios [page 422]

Implementing Data Migration and Replication to Employee Central

Side-by-Side Deployment Option PUBLIC 413
 The steps for checking if a personnel number was previously replicated from SAP ERP HCM to the SAP
SuccessFactors Talent Suite and for nding out which user ID was used for this replication dier depending
on your integration scenario.

Switching from One Replication to the Other [page 423]

Take a look at what's important when you actually switch from Talent Hybrid integration to integation with
Employee Central.

Making Additional Customizing Settings [page 424]

If you have previously used the integration add-on for SAP S∕4HANA and SAP SuccessFactors HCM Suite,
in Customizing, set the value of the SFSFI SBSER switch to X to indicate that the employee data replication
to Employee Central is active in your system.

Changing the Employment Status to Inactive Before and to Active Again After Switching from One Replication
to the Other [page 424]
Here's what you need to do to reuse a users-sys-id if an employee becomes inactive and then active again.

Handling Concurrent Employment and Global Assignment Situations [page 425]

Here's what you should know about concurrent employment and global assignment when switching from
Talent Hybrid integration to integration with Employee Central.

4.2.1 Migrating from Talent Hybrid Integration to ERP

Integration when Assignment ID Field is Enabled

This section tells you on how to update the assignment ID external eld for a user

Prerequisites

To include the assignment ID during the migration process, you need to enable the switch ERP to EC/EC to ERP
(BIB): Activate Assignment ID External in the view V_ECPAO_CONSTANT using the Maintain the Constant Values
customizing activity.

Context

A value would have been automatically assigned for the assignment ID external eld when the talent hybrid report
was executed based on the business rule which was congured earlier. Now you will have to update this assignment
ID external eld to the PERNR number of the employee before running the employee extraction report.

Procedure

1. Update the assignment ID external to PERNR number. Refer the Updating the Assignment ID external eld topic
in the related information section.

Implementing Data Migration and Replication to Employee Central

414 PUBLIC Side-by-Side Deployment Option
 2. Change the mapping mode for the User ID eld to BAdi mapping in the Dene Employee Data Settings for
Employee Central Company Customizing activity (view V_ECPAO_CMPNY_EE). Check the value of the User ID
that was created by the talent hybrid report and then use the same User ID value in the BAdi for the User
ID eld. And check the entry for T77S0 for Group SFSFI and Sem abbr to SBSER switch using the function
module HR_READ_T77S0 in the EX_ECPAO_EMP_USYID_PRN_UNM_MAP BAdI.

If the value of the switch under Switch o Talent Hybrid Integration for Employee Data is set to 'X' (Group name
SFSFI and Semantic Abbreviation SBSER in table T77S0) then you will have to assign the user ID value as what
you have used in the talent hybrid integration. If the switch is blank, then the User ID has to be set to PERNR.
3. You can alternatively also use the standard mapping for the User ID eld in the Dene Employee Data Settings
for EC company Customizing activity. And execute the ECPAO_TH_EC_MIGR_EEKMAP_UPDATE report to update
the key mapping table (ECPAO_EE_KMAP) for the PERNR which were replicated via talent hybrid integration,
which will update the User ID eld in the key mapping table.
4. Execute the employee data extraction ECPAO_EMPL_EXTRACTION report.

Task overview: How to Migrate from Talent Hybrid Integration to Integration with Employee Central [page 413]

Related Information

Determining the User ID [page 420]

Determining the Person ID [page 421]
Handling the Dierent Integration Scenarios [page 422]
Switching from One Replication to the Other [page 423]
Making Additional Customizing Settings [page 424]
Changing the Employment Status to Inactive Before and to Active Again After Switching from One Replication to
the Other [page 424]
Handling Concurrent Employment and Global Assignment Situations [page 425]
Updating the Assignment ID external eld

4.2.1.1 Migrating from Talent Hybrid Integration to ERP

Integration for Global Assignment

This section tells you the steps to be performed for migrating a global assignment employee using the
employee extraction report who was previously replicated to employee prole using the talent hybrid report
RH_SFI_SYNCHRONIZE_EMPL_DATA

Prerequisites

To include the assignment ID during the migration process, you need to enable the switch ERP to EC/EC to ERP
(BIB): Activate Assignment ID External in the view V_ECPAO_CONSTANT using the Maintain the Constant Values
customizing activity. In addition, you will have to activate the T77S0 switch for group SFSFI and Sem abbr SBSER
denoting that Talent Hybrid integration was used before in the Switch O Talent Hybrid Integration for Employee
Data customizing activity.
Context

Implementing Data Migration and Replication to Employee Central

Side-by-Side Deployment Option PUBLIC 415
Employee having global assignment scenario was replicated previously by talent hybrid report. Now the employee
in being migrated from the SAP ERP HCM to Employee Central using the infoporter tool. Since talent hybrid report
allows you to replicate either the home or host PERNR, you can either replicate the home or host PERNR to the
Employee prole.

Based on if the home PERNR or the host PERNR was replicated using talent hybrid report, we have dierent steps
to be followed while using employee extraction report:

To migrate the employee to Employee Central using info-porter where the home
PERNR was previously replicated by talent hybrid report:

1. Update the assignment ID external from the existing value to the home PERNR. Refer the Updating the
Assignment ID external eld topic in the related information section.
2. Execute the ECPAO_TH_EC_MIGR_EEKMAP_UPDATE report to update the key mapping table (ECPAO_EE_KMAP)
for the home PERNR which were replicated via talent hybrid integration.
3. Change the mapping mode for the User ID mapping to standard mapping in the Dene Employee Data Settings
for Employee Central Company Customizing activity (view V_ECPAO_CMPNY_EE) for your EC instance ID.
4. Execute the employee data extraction ECPAO_EMPL_EXTRACTION report which will migrate the data of host
PERNR along with home PERNR to Employee Central.

To migrate the employee to Employee Central using info-porter where the host
PERNR was previously replicated by talent hybrid report:

1. Update the assignment ID external from the existing value to the host PERNR. Refer the Updating the
Assignment ID external eld topic in the related information section.
2. Execute the ECPAO_TH_EC_MIGR_EEKMAP_UPDATE report to update the key mapping table (ECPAO_EE_KMAP)
for the host PERNR which got migrated during the talent hybrid integration.
3. Change the mapping mode for the User ID mapping to standard mapping in the Dene Employee Data Settings
for Employee Central Company Customizing activity (view V_ECPAO_CMPNY_EE) for your EC instance ID.
4. Filter the home PERNR which was not replicated using the talent hybrid report. We can lter the PERNR using
the lter BAdi Validity Periods for Data Replication to EC (EX_ECPAO_EMP_VALIDITY_TAB). Since talent hybrid
has created the host PERNR on Employee prole, we cannot create the home PERNR on existing host PERNR
in Employee Central. Due to this we can only migrate host PERNR using the employee extraction report in this
case.
5. Execute the employee data extraction ECPAO_EMPL_EXTRACTION report which will migrate the data of host
PERNR to Employee Central.

Related Information

Updating the Assignment ID external eld

Implementing Data Migration and Replication to Employee Central

416 PUBLIC Side-by-Side Deployment Option
4.2.1.2 Migrating from Talent Hybrid Integration to ERP
Integration for International Transfer

This section tells you the steps to be performed for migrating an international transfer employee using
the employee extraction report who was previously replicated to employee prole using talent hybrid report
RH_SFI_SYNCHRONIZE_EMPL_DATA.

Prerequisites

To include the assignment ID during the migration process, you need to enable the switch ERP to EC/EC to ERP
(BIB): Activate Assignment ID External in the view V_ECPAO_CONSTANT using the Maintain the Constant Values
customizing activity. In addition, you will have to activate the T77S0 switch for group SFSFI and Sem abbr SBSER
denoting that Talent Hybrid integration was used before in the Switch O Talent Hybrid Integration for Employee
Data customizing activity.

Context

While migrating an international transfer employee using the talent hybrid report, leading PERNR or the active
PERNR on the current date or the PERNR selected by the BAdi is migrated by the talent hybrid report.

To migrate the employee to Employee Central using info-porter where the employment in the second country
was previously replicated by talent hybrid report:

Procedure

1. Update the assignment ID external from the existing value to the PERNR of the employment in the second
country. Refer the Updating the Assignment ID external eld topic in the related information section.
2. Execute the ECPAO_TH_EC_MIGR_EEKMAP_UPDATE report to update the key mapping table ECPAO_EE_KMAP
for the employment in the second country which got replicated using the talent hybrid report during the talent
hybrid migration.
3. Change the mapping mode for the User ID mapping to standard mapping in the Dene Employee Data Settings
for Employee Central Company Customizing activity (view V_ECPAO_CMPNY_EE) for your EC instance ID.
4. Filter the employment in the rst country which was not migrated using the talent hybrid report. We can lter
the PERNR using the lter BAdi Validity Periods for Data Replication to EC (EX_ECPAO_EMP_VALIDITY_TAB).
Since the talent hybrid has created an employment for second country on employee prole, we cannot create
an employment in rst country which is starting before the start date of second employment in Employee
Central using the employee extraction report.
5. Execute the employee data extraction ECPAO_EMPL_EXTRACTION report which will migrate the data of
employment in second country to Employee Central.

Implementing Data Migration and Replication to Employee Central

Side-by-Side Deployment Option PUBLIC 417
Related Information

Updating the Assignment ID external eld

4.2.1.3 Migrating from Talent Hybrid Integration to ERP

Integration for Concurrent Employment

This section tells you the steps to be performed for migrating a concurrent employment employee using
the employee extraction report who was previously replicated to employee prole using talent hybrid report
RH_SFI_SYNCHRONIZE_EMPL_DATA.

Prerequisites

To include the assignment ID during the migration process, you need to enable the switch ERP to EC/EC to ERP
(BIB): Activate Assignment ID External in the view V_ECPAO_CONSTANT using the Maintain the Constant Values
customizing activity. In addition, you will have to activate the T77S0 switch for group SFSFI and Sem abbr SBSER
denoting that Talent Hybrid integration was used before in the Switch O Talent Hybrid Integration for Employee
Data customizing activity.
Context

While migrating a concurrent employment employee using the talent hybrid report, leading PERNR or the active
PERNR on the current date or the PERNR selected by the BAdi.

To migrate the employee to Employee Central using info-porter tool, where the
rst employment of concurrent employment was previously replicated by talent
hybrid report:

1. Update the assignment ID external from the existing value to the rst employment PERNR. Refer the Updating
the Assignment ID external eld topic in the related information section.
2. Execute the ECPAO_TH_EC_MIGR_EEKMAP_UPDATE report to update the key mapping table ECPAO_EE_KMAP
for rst employment PERNR which got migrated using the talent hybrid report.
3. Change the mapping mode for the User ID mapping to standard mapping in the Dene Employee Data Settings
for Employee Central Company Customizing activity (view V_ECPAO_CMPNY_EE) for your EC instance ID.
4. Execute the employee data extraction ECPAO_EMPL_EXTRACTION report which will migrate the data of rst
and second employment PERNR to Employee Central.

To migrate the employee to Employee Central using info-porter tool, where the
second employment of concurrent employment was previously replicated by
talent hybrid report:

1. Update the assignment ID external from the existing value to the second employment PERNR. Refer the
Updating the Assignment ID external eld topic in the related information section.

Implementing Data Migration and Replication to Employee Central

418 PUBLIC Side-by-Side Deployment Option
 2. Execute the ECPAO_TH_EC_MIGR_EEKMAP_UPDATE report to update the key mapping table for the second
employment PERNR which got migrated using the talent hybrid migration.
3. Change the mapping mode for the User ID mapping to standard mapping in the Dene Employee Data Settings
for Employee Central Company Customizing activity (view V_ECPAO_CMPNY_EE) for your EC instance ID.
4. Filter the rst employment PERNR which was not migrated using the talent hybrid report. We can lter the
PERNR using the lter BAdi Validity Periods for Data Replication to EC (EX_ECPAO_EMP_VALIDITY_TAB). Since
talent hybrid has created the second employment PERNR on Employee prole, we cannot create the rst
employment PERNR which is starting before the second employment PERNR. Due to this we can only migrate
second employment PERNR using the employee extraction report in this case.
5. Execute the employee data extraction ECPAO_EMPL_EXTRACTION report which will migrate the data of second
employment PERNR to Employee Central.

 Note

If the centralized services switch is on then the migration of concurrent employment to Employee Central
would create a secondary assignment on Employee Central.

Related Information

Updating the Assignment ID external eld

4.2.1.4 Updating the Key Value Mapping Table for Talent

Hybrid Migration to Employee Central

We provide a program to update the key value mapping table (ECPAO_EE_KMAP) so that you don't need to create a
report by yourself to update the employee key mapping table manually.

Prerequisites

Before executing this program, ensure that the following steps have been performed:

• In the Employee Central instance, run the convertAssignmentIdExternal API manually to convert the
ASSIGNMENT_ID_EXTERNAL value to PERNR for Talent Hybrid employees.
• Enable the constant ERP to EC/EC to ERP (BIB): Activate Assignment ID External in the V_ECPAO_CONSTANT
view.
• Activate the T77S0 switch for group SFSFI and semantic abbreviation SBSER denoting that Talent Hybrid
integration was used before.
• Export the employees/users using the Employee Export action in the Employee Central Admin Center. Make
sure that the option Include additional identiers under Specify Export Options is selected before exporting the
employees/users.

Implementing Data Migration and Replication to Employee Central

Side-by-Side Deployment Option PUBLIC 419
Context

The Update Key Value Mapping Table for Talent hybrid to EC migration program
(ECPAO_TH_EC_MIGR_EEKMAP_UPDATE) updates the employee key mapping table ECPAO_EE_KMAP with the
PERNR, USER_ID, and PERSON_ID_EXTERNAL elds of those personnel numbers that were replicated before via
Talent Hybrid integration.

Procedure

1. Go to the Update Key Value Mapping Table for Talent hybrid to EC migration (ECPAO_TH_EC_KMAP_UPD)
transaction to run the Update Key Value Mapping Table for Talent hybrid to EC migration
(ECPAO_TH_EC_MIGR_EEKMAP_UPDATE) program.

The program updates the employee key mapping table ECPAO_EE_KMAP with the PERNR, USER_ID, and
PERSON_ID_EXTERNAL elds of those personnel numbers that were replicated before via Talent Hybrid
integration.
2. On the selection screen, select the CSV le, which you have downloaded from Employee Central.
3. In the action type, choose Test Run to carry out a test run of the program to check the data that will be updated.

If you run the program in a test system or client with the Test Run checkbox deselected, the program asks for a
transport request.

4.2.2 Determining the User ID

To replicate the correct users-sys-id from SAP S∕4HANA to Employee Central, implement the GET_USERSYSID
method of the Mapping of User ID, Person ID, Username, and Object ID (EX_ECPAO_EMP_USYID_PRN_UNM_MAP)
Business Add-In (BAdI).

For more information about this BAdI, see the Replicating Employee Data from SAP S/4HANA to Employee Central
integration guide. Find the most current version of this guide at http://help.sap.com/hr_ecintegration.

When implementing the BAdI, check the following:

Is the employee's current personnel number (PERNR) one of several personnel numbers that are assigned to the
same central person (CP) and are transferred to the same Job Information record in Employee Central? This is the
case if the following conditions are ullled for all personnel numbers:

• They are assigned to dierent countries.

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

• If yes: Check if any of the employee's personnel numbers was previously replicated to the SAP SuccessFactors
Talent Suite.
• If yes: Find out which user ID was used for replicating the employee's data to the SAP SuccessFactors
Talent Suite. Use the same ID as the user-sys-id when replicating the employee's data to Employee Central.

Implementing Data Migration and Replication to Employee Central

420 PUBLIC Side-by-Side Deployment Option
 • If no: Either use the standard logic of the data replication to Employee Central to determine the users-sys-
id for the personnel number. Or implement the EX_ECPAO_EMP_USYID_PRN_UNM_MAP BAdI if you have
specic requirements.
• If no: You only need to check if the current personnel number was previously replicated to the SAP
SuccessFactors Talent Suite. Then proceed as described above.

Parent topic: How to Migrate from Talent Hybrid Integration to Integration with Employee Central [page 413]

Related Information

Migrating from Talent Hybrid Integration to ERP Integration when Assignment ID Field is Enabled [page 414]
Determining the Person ID [page 421]
Handling the Dierent Integration Scenarios [page 422]
Switching from One Replication to the Other [page 423]
Making Additional Customizing Settings [page 424]
Changing the Employment Status to Inactive Before and to Active Again After Switching from One Replication to
the Other [page 424]
Handling Concurrent Employment and Global Assignment Situations [page 425]

4.2.3 Determining the Person ID

When replicating the employee's data from SAP S∕4HANA to Employee Central, make sure to use the same
person-id-external as was previously used for replicating the employee's data to the SAP SuccessFactors Talent
Suite.

To replicate the correct person-id-external, implement the GET_PERSONID method of the Mapping of User ID,
Person ID, Username, and Object ID (EX_ECPAO_EMP_USYID_PRN_UNM_MAP) BAdI. For more information about
this BAdI, see the Employee Data Extraction (ECPAO_EMPL_EXTRACTION) program. For more information about
the data extraction program, refer to Replicating Employee Data from SAP S/4HANA to Employee Central.

Parent topic: How to Migrate from Talent Hybrid Integration to Integration with Employee Central [page 413]

Related Information

Migrating from Talent Hybrid Integration to ERP Integration when Assignment ID Field is Enabled [page 414]
Determining the User ID [page 420]
Handling the Dierent Integration Scenarios [page 422]
Switching from One Replication to the Other [page 423]
Making Additional Customizing Settings [page 424]
Changing the Employment Status to Inactive Before and to Active Again After Switching from One Replication to
the Other [page 424]

Implementing Data Migration and Replication to Employee Central

Side-by-Side Deployment Option PUBLIC 421
Handling Concurrent Employment and Global Assignment Situations [page 425]

4.2.4 Handling the Dierent Integration Scenarios

The steps for checking if a personnel number was previously replicated from SAP ERP HCM to the SAP
SuccessFactors Talent Suite and for nding out which user ID was used for this replication dier depending on
your integration scenario.

Scenario 1

You have installed the integration add-on 1.0 for SAP ERP HCM and SAP SuccessFactors HCM Suite, support
package 02 or higher and use the Sync Employee Data with SuccessFactors (with Delta and Inactive Logic)
(RH_SFI_SYNCHRONIZE_EMPL_DATA) program to replicate employee data to the SAP SuccessFactors Talent
Suite.

In this case, you can check the HRSFI_D_EXTR_LOG database table to nd out if a personnel number was
previously replicated to the SAP SuccessFactors Talent Suite and which user ID was used.

The person-id-external eld is lled with the same value as the users-sys-id eld.

Scenario 2

You have installed the integration add-on 1.0 for SAP ERP HCM and SAP SuccessFactors HCM Suite, support
package 00 and use the Extraction of Employee Data for SuccessFactors (RH_SFI_TRIGGER_EMPL_DATA_REPL)
program to replicate employee data to the SAP SuccessFactors Talent Suite.

In this case, the HRSFI_D_EXTR_LOG database table isn't available. The key mapping is not persisted in the
SAP ERP HCM system. Therefore we recommend to upgrade to support package 02 or higher and to use
the RH_SFI_SYNCHRONIZE_EMPL_DATA program instead of the RH_SFI_TRIGGER_EMPL_DATA_REPL program.
Otherwise you need to implement a custom logic to nd out if a personnel number was previously replicated to the
SAP SuccessFactors Talent Suite and which user ID was used.

As in scenario 1, the person-id-external eld is lled with the same value as the users-sys-id eld.

Scenario 3

You don't use the integration add-on for SAP ERP HCM and SAP SuccessFactors HCM Suite, but another
integration process to replicate employee data from an on-premise SAP ERP HCM system to the Employee Prole
in the SAP SuccessFactors Talent Suite.

In this case, you need to implement a custom logic to nd out if a personnel number was previously replicated to
the SAP SuccessFactors Talent Suite and which users-sys-id and person-id-external were used.

Implementing Data Migration and Replication to Employee Central

422 PUBLIC Side-by-Side Deployment Option
Parent topic: How to Migrate from Talent Hybrid Integration to Integration with Employee Central [page 413]

Related Information

Migrating from Talent Hybrid Integration to ERP Integration when Assignment ID Field is Enabled [page 414]
Determining the User ID [page 420]
Determining the Person ID [page 421]
Switching from One Replication to the Other [page 423]
Making Additional Customizing Settings [page 424]
Changing the Employment Status to Inactive Before and to Active Again After Switching from One Replication to
the Other [page 424]
Handling Concurrent Employment and Global Assignment Situations [page 425]

4.2.5 Switching from One Replication to the Other

Take a look at what's important when you actually switch from Talent Hybrid integration to integation with
Employee Central.

To keep the data consistent, we recommend that you run a nal employee data transfer to the SAP SuccessFactors
Talent Suite and ensure that no employee data that is aected by data replication is changed in the SAP ERP HCM
system before you start replicating employee data to SAP SuccessFactors Employee Central.

Once you've started using the data replication to Employee Central, the Employee Prole is fed from Employee
Central using HRIS synchronization. Therefore, make sure that you no longer replicate employee data to the
Employee Prole using the previous replication of employee data to the SAP SuccessFactors Talent Suite.

This applies if you use the rst or the second of the possible scenarios applicable to migration from Talent Hybrid
integration to integation with Employee Central.

Parent topic: How to Migrate from Talent Hybrid Integration to Integration with Employee Central [page 413]

Related Information

Migrating from Talent Hybrid Integration to ERP Integration when Assignment ID Field is Enabled [page 414]
Determining the User ID [page 420]
Determining the Person ID [page 421]
Handling the Dierent Integration Scenarios [page 422]
Making Additional Customizing Settings [page 424]
Changing the Employment Status to Inactive Before and to Active Again After Switching from One Replication to
the Other [page 424]
Handling Concurrent Employment and Global Assignment Situations [page 425]

Implementing Data Migration and Replication to Employee Central

Side-by-Side Deployment Option PUBLIC 423
4.2.6 Making Additional Customizing Settings

If you have previously used the integration add-on for SAP S∕4HANA and SAP SuccessFactors HCM Suite, in
Customizing, set the value of the SFSFI SBSER switch to X to indicate that the employee data replication to
Employee Central is active in your system.

For more information about the Customizing settings, see the Replicating Employee Data from SAP S/4HANA
to Employee Central integration guide. Find the most current version of this guide at http://help.sap.com/
hr_ecintegration.

Setting this switch tells your system that the employee data replication programs of the integration add-on for SAP
S∕4HANA and SAP SuccessFactors HCM Suite can no longer be run.

This applies if you use the rst or the second of the possible scenarios applicable to migration from Talent Hybrid
integration to integration with Employee Central.

Parent topic: How to Migrate from Talent Hybrid Integration to Integration with Employee Central [page 413]

Related Information

Migrating from Talent Hybrid Integration to ERP Integration when Assignment ID Field is Enabled [page 414]
Determining the User ID [page 420]
Determining the Person ID [page 421]
Handling the Dierent Integration Scenarios [page 422]
Switching from One Replication to the Other [page 423]
Changing the Employment Status to Inactive Before and to Active Again After Switching from One Replication to
the Other [page 424]
Handling Concurrent Employment and Global Assignment Situations [page 425]

4.2.7 Changing the Employment Status to Inactive Before and

to Active Again After Switching from One Replication to
the Other

Here's what you need to do to reuse a users-sys-id if an employee becomes inactive and then active again.

The following situation might occur: An active employee is replicated from SAP S∕4HANA to the SAP
SuccessFactors Talent Suite. Then the employee becomes inactive in SAP S∕4HANA. The employee's data is
replicated to the SAP SuccessFactors Talent Suite again. The employee is set to inactive in SAP SuccessFactors.
You switch to the employee data replication to Employee Central. Then the employee becomes active again.

In this situation, the employee data replication to Employee Central does not know that the same employee
was previously replicated to the SAP SuccessFactors Talent Suite and which users-sys-id was used. So based on
employee data replication to Employee Central, the employee might get a dierent userd-sys-id than he or she had
before.

Therefore, implement a custom logic if you are in this situation. To do so:

Implementing Data Migration and Replication to Employee Central

424 PUBLIC Side-by-Side Deployment Option
 • Store the information which personnel numbers were previously replicated to the SuccessFactors Talent Suite
and which users-sys-id was used.
• Implement the Mapping of User ID, Person ID, Username, and Object ID
(EX_ECPAO_EMP_USYID_PRN_UNM_MAP) Business Add-In (BAdI) using a custom method so that data
replication to Employee Central can use the same users-sys-id when the aected employee is rehired.

This applies to all three of the possible scenarios applicable to migration from Talent Hybrid integration to
integation with Employee Central.

 Caution

In the situation described above, the entry in the HRSFI_D_EXTR_LOG database table in SAP S∕4HANA that
refers to the employee who is set to inactive is deleted. So even if you use scenario 1, you can't use the
HRSFI_D_EXTR_LOG database table to retrieve the information you need.

Parent topic: How to Migrate from Talent Hybrid Integration to Integration with Employee Central [page 413]

Related Information

Migrating from Talent Hybrid Integration to ERP Integration when Assignment ID Field is Enabled [page 414]
Determining the User ID [page 420]
Determining the Person ID [page 421]
Handling the Dierent Integration Scenarios [page 422]
Switching from One Replication to the Other [page 423]
Making Additional Customizing Settings [page 424]
Handling Concurrent Employment and Global Assignment Situations [page 425]

4.2.8 Handling Concurrent Employment and Global Assignment

Situations
Here's what you should know about concurrent employment and global assignment when switching from Talent
Hybrid integration to integration with Employee Central.

Using the Talent Hybrid integration provided by SAP, you can only replicate the data of one of the assignments
from SAP S∕4HANA to the SAP SuccessFactors Talent Suite for employees who have global assignments or are
concurrently employed. HRIS synchronization between Employee Central and the SAP SuccessFactors Talent
Suite, however, takes both assignments into account. The data that already had been replicated using Talent
Hybrid are now been replicated using Infoporter tool. Therefore be aware of the following aspects:

Concurrent Employment and Global Assignment

If an employee's data was replicated from the on-premise SAP S∕4HANA system to the SAP SuccessFactors
Talent Suite before and the employee is concurrently employed or has a global assignment, make sure that the

Implementing Data Migration and Replication to Employee Central

Side-by-Side Deployment Option PUBLIC 425
employee's data is replicated to the same employment and that the employee doesn't get a second user ID when
replicating his or her data to SAP SuccessFactors Employee Central. To do so, set the EV_SKIP_USER_ENTITY
parameter to True when implementing the GET_USERSYSID method of the Mapping of User ID, Person ID,
Username, and Object ID (EX_ECPAO_EMP_USYID_PRN_UNM_MAP) Business Add-In (BAdI). This parameter
indicates that the generation of the Basic Import template in Employee Central should be skipped for the
employee.

Global Assignment

When using data replication from the on-premise SAP S∕4HANA system to the SAP SuccessFactors Talent Suite,
you can decide if the host or the home assignment is to be transferred for employees with a global assignment.
However, when you switch to data replication to SAP SuccessFactors Employee Central, both assignments are
transferred using dierent users-sys-ids. This means you see two Employee Proles, one for the employee's host
assignment and one for his or her home assignment. You need to decide which of the assignments you want to use
for the talent processes in SAP SuccessFactors.

Parent topic: How to Migrate from Talent Hybrid Integration to Integration with Employee Central [page 413]

Related Information

Migrating from Talent Hybrid Integration to ERP Integration when Assignment ID Field is Enabled [page 414]
Determining the User ID [page 420]
Determining the Person ID [page 421]
Handling the Dierent Integration Scenarios [page 422]
Switching from One Replication to the Other [page 423]
Making Additional Customizing Settings [page 424]
Changing the Employment Status to Inactive Before and to Active Again After Switching from One Replication to
the Other [page 424]

4.3 HR Business Processes for the Side-by-Side Deployment

Option in Employee Data Migration

Find out how the HR business processes work when you use the side-by-side deployment option.

Prerequisites and Restrictions [page 427]

This section provides the prerequisites information that you need to set when using the HR business
processes.

Hire [page 428]

You can hire new employees either in SAP S∕4HANA or in Employee Central.

Rehire [page 432]

Implementing Data Migration and Replication to Employee Central

426 PUBLIC Side-by-Side Deployment Option
 You can rehire employees either in SAP S∕4HANA or in Employee Central.

Transfer [page 435]

You can transfer employees either within SAP S∕4HANA or within Employee Central.

International Transfer [page 437]

You can transfer employees between countries that are mastered in SAP S∕4HANA or in Employee Central.

Global Assignment [page 441]

You can have global assignments within SAP S∕4HANA, within Employee Central, or between both systems.

Concurrent Employment [page 446]

Concurrent employment can either be within SAP S∕4HANA or within Employee Central.

Termination [page 451]

You can terminate employees either in SAP S∕4HANA or in Employee Central, depending on which is the
system of record.

4.3.1 Prerequisites and Restrictions

This section provides the prerequisites information that you need to set when using the HR business processes.

When using HR business processes in the side-by-side deployment option make sure that the following
prerequisites are ullled.

• You use Employee Central as a global HCM system that stores the master data of all employees, including the
employees mastered in SAP S∕4HANA.
• SAP S∕4HANA stores the master data of the employee that are mastered in SAP S∕4HANA and the employees
that are mastered in EC and then replicated to ERP to leverage the Payroll.
• You can congure the source of record eld in the employee information template/entity to store the source
ERP system name for the employee.
• The number ranges you use in SAP S∕4HANA and Employee Central don't overlap.
• To dene number ranges in Employee Central, go to the Admin Center and choose the Company System
and Logo Settings tool. On the Company System Setting page, ll in the Next Person Id Assigned eld.

• To dene number ranges in SAP S∕4HANA, go to Customizing for Personnel Management. Under
Personnel Administration Basic Settings , carry out the Maintain number range intervals for personnel
numbers and Determine defaults for number ranges Customizing activites.
• You use role-based permissions to make sure that an employee's data can only be changed in the system of
record.

Implementing Data Migration and Replication to Employee Central

Side-by-Side Deployment Option PUBLIC 427
  Recommendation

We recommend you use the following standard mappings:

• The central person from SAP S∕4HANA is mapped to the person_id_external eld in Employee Central.
• The personnel number from SAP S∕4HANA is mapped to the user_id eld in Employee Central.

If you use other mappings, make sure that a unique ID is used when you replicate an employee's data from SAP
S∕4HANA to Employee Central. For more information about the standard mappings and mapping options, 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.

 Restriction

The side-by-side deployment option currently doesn't support some business processes, such as:

• Rehiring an employee in SAP S∕4HANA whose data was previously mastered in Employee Central
• Concurrently employing an employee within SAP S∕4HANA and Employee Central

Parent topic: HR Business Processes for the Side-by-Side Deployment Option in Employee Data Migration [page
426]

Related Information

Hire [page 428]

Rehire [page 432]
Transfer [page 435]
International Transfer [page 437]
Global Assignment [page 441]
Concurrent Employment [page 446]
Termination [page 451]

4.3.2 Hire

You can hire new employees either in SAP S∕4HANA or in Employee Central.

Hiring a New Employee in SAP S∕4HANA [page 429]

You hire a new employee in SAP S∕4HANA and replicate the employee's master data to Employee Central.

Hiring a New Employee in Employee Central [page 431]

Parent topic: HR Business Processes for the Side-by-Side Deployment Option in Employee Data Migration [page
426]

Implementing Data Migration and Replication to Employee Central

428 PUBLIC Side-by-Side Deployment Option
Related Information

Prerequisites and Restrictions [page 427]

Rehire [page 432]
Transfer [page 435]
International Transfer [page 437]
Global Assignment [page 441]
Concurrent Employment [page 446]
Termination [page 451]

4.3.2.1 Hiring a New Employee in SAP S∕4HANA

You hire a new employee in SAP S∕4HANA and replicate the employee's master data to Employee Central.

In Employee Central, the personnel number (PERNR) is mapped to the user_id eld and the central person (CP)
is mapped to the person_id_external eld. The employee's data is stored in Employee Central according to the
eld mapping that you have dened 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 dene 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 dene a cuto
date. If you use the cuto date, the Hire Date and Original Start Date elds in Employee Central are lled in dierent
ways, depending on whether the employee’s hire date is before or after the cuto date:

• If the cuto date is before the hire date in SAP S∕4HANA, the Hire Date and Original Start Date elds in
Employee Central are both lled with the SAP S∕4HANA hire date.

Implementing Data Migration and Replication to Employee Central

Side-by-Side Deployment Option PUBLIC 429
 Cuto Date is Before Hire Date

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

Cuto Date is After Hire Date

The employee's data is extracted starting with the cuto date for all eective-dated entities, including Job Info
(Job History) and also for Non-Recurring Pay Components.
• If the hire date is before the cuto date and data is changed in SAP S∕4HANA before the cuto date, the SAP
S∕4HANA hire date is mapped to the Original Start Date eld and the cuto date is mapped to the Hire Date
eld in Employee Central. The employee has only one Job Information record in Employee Central representing
the data valid at the cuto date.
Also in this case a Hire event with the PSEUDO_HIRE event reason is carried out in Employee Central.

Implementing Data Migration and Replication to Employee Central

430 PUBLIC Side-by-Side Deployment Option
 Cuto Date is After Hire Date

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

Parent topic: Hire [page 428]

Related Information

Hiring a New Employee in Employee Central [page 431]

4.3.2.2 Hiring a New Employee in Employee Central

The hire process in Employee Central works as usual. In the side-by-side deployment option described in this guide,
employees whose data is mastered in Employee Central are replicated to SAP ERP HCM.

Parent topic: Hire [page 428]

Related Information

Hiring a New Employee in SAP S∕4HANA [page 429]

Implementing Data Migration and Replication to Employee Central

Side-by-Side Deployment Option PUBLIC 431
4.3.3 Rehire

You can rehire employees either in SAP S∕4HANA or in Employee Central.

The business processes dier depending on where the employee's data was mastered before.

Rehiring an Employee in SAP S∕4HANA Who Was Previously Mastered in SAP S∕4HANA [page 432]
You rehire an employee in SAP S∕4HANA system and migrate the employee's master data to Employee
Central.

Rehiring an Employee in Employee Central Who Was Previously Mastered in Employee Central [page 434]

Rehiring an Employee in Employee Central Who Was Previously Mastered in SAP ERP HCM [page 434]

Rehiring an Employee in SAP S∕4HANA Who Was Previously Mastered in Employee Central [page 435]

Parent topic: HR Business Processes for the Side-by-Side Deployment Option in Employee Data Migration [page
426]

Related Information

Prerequisites and Restrictions [page 427]

Hire [page 428]
Transfer [page 435]
International Transfer [page 437]
Global Assignment [page 441]
Concurrent Employment [page 446]
Termination [page 451]

4.3.3.1 Rehiring an Employee in SAP S∕4HANA Who Was

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

If you use the cuto date, the following situations can occur:

• If the cuto date is after the rehire date, meaning, the employee was hired, terminated, and then rehired in
SAP S∕4HANA before the cuto date, the rst hire date (rst entry into the company) is mapped to the Original
Start Date eld in Employee Central. The cuto date is mapped to the Hire Date eld in Employee Central. You
can still use the date of the employee's rst entry into the company to calculate, for example, the employee's
seniority, since this date is stored in the Original Start Date eld.

Implementing Data Migration and Replication to Employee Central

432 PUBLIC Side-by-Side Deployment Option
 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.

Cuto Date is After Rehire Date

The employee's data is extracted starting with the cuto date for all eective-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 cuto 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 rst hire date (rst entry into the company) is mapped to the Original Start Date eld and the Hire Date
eld of Employment Info template in Employee Central.

Cuto Date is Before Rehire Date

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

Implementing Data Migration and Replication to Employee Central

Side-by-Side Deployment Option PUBLIC 433
• If the cuto date is after the termination date and the employee is not rehired, no data is extracted for all
eective-dated templates and the Non-Recurring Pay Components template.

Parent topic: Rehire [page 432]

Related Information

Rehiring an Employee in Employee Central Who Was Previously Mastered in Employee Central [page 434]
Rehiring an Employee in Employee Central Who Was Previously Mastered in SAP ERP HCM [page 434]
Rehiring an Employee in SAP S∕4HANA Who Was Previously Mastered in Employee Central [page 435]

4.3.3.2 Rehiring an Employee in Employee Central Who Was

Previously Mastered in Employee Central

The rehire process in Employee Central works as usual. In the side-by-side deployment option described in this
guide, employees whose data is mastered in Employee Central aren't replicated to SAP ERP HCM.

Parent topic: Rehire [page 432]

Related Information

Rehiring an Employee in SAP S∕4HANA Who Was Previously Mastered in SAP S∕4HANA [page 432]
Rehiring an Employee in Employee Central Who Was Previously Mastered in SAP ERP HCM [page 434]
Rehiring an Employee in SAP S∕4HANA Who Was Previously Mastered in Employee Central [page 435]

4.3.3.3 Rehiring an Employee in Employee Central Who Was

Previously Mastered in SAP ERP HCM

When an employee leaves the company, you carry out a Leaving action in SAP ERP HCM and replicate the
employee's master data to Employee Central. In Employee Central, a Termination event is carried out and the
employee is set to inactive.

When you try to rehire the same person in Employee Central, the duplicate check nds this employee because his
or her data was replicated from SAP ERP HCM. You therefore create a new employment in Employee Central using
the Add Employment feature.

Implementing Data Migration and Replication to Employee Central

434 PUBLIC Side-by-Side Deployment Option
  Note

You can't use a Rehire event within the Add Employment feature. Only the Hire event is available there. We
therefore recommend you create an own event reason for the rehire process across system borders and attach
it to the Hire event.

A new user is created in Employee Central for the new employment.

In the side-by-side deployment option described in this guide, the employee rehired in Employee Central isn't
replicated to SAP ERP HCM.

Parent topic: Rehire [page 432]

Related Information

Rehiring an Employee in SAP S∕4HANA Who Was Previously Mastered in SAP S∕4HANA [page 432]
Rehiring an Employee in Employee Central Who Was Previously Mastered in Employee Central [page 434]
Rehiring an Employee in SAP S∕4HANA Who Was Previously Mastered in Employee Central [page 435]

4.3.3.4 Rehiring an Employee in SAP S∕4HANA Who Was

Previously Mastered in Employee Central

You can rehire an employee in SAP S∕4HANA who was previously mastered in Employee Central when the
terminated employee is mastered in Employee Central, then replicated to ERP, and then he/she is rehired in ERP.

Parent topic: Rehire [page 432]

Related Information

Rehiring an Employee in SAP S∕4HANA Who Was Previously Mastered in SAP S∕4HANA [page 432]
Rehiring an Employee in Employee Central Who Was Previously Mastered in Employee Central [page 434]
Rehiring an Employee in Employee Central Who Was Previously Mastered in SAP ERP HCM [page 434]

4.3.4 Transfer

You can transfer employees either within SAP S∕4HANA or within Employee Central.

In SAP S∕4HANA, the transfer is called organizational reassignment.

Implementing Data Migration and Replication to Employee Central

Side-by-Side Deployment Option PUBLIC 435
 Transferring an Employee Within SAP S∕4HANA [page 436]
You can transfer an employee within SAP S∕4HANA whose data is mastered in the SAP S∕4HANA system.

Transferring an Employee Within Employee Central [page 437]

Parent topic: HR Business Processes for the Side-by-Side Deployment Option in Employee Data Migration [page
426]

Related Information

Prerequisites and Restrictions [page 427]

Hire [page 428]
Rehire [page 432]
International Transfer [page 437]
Global Assignment [page 441]
Concurrent Employment [page 446]
Termination [page 451]

4.3.4.1 Transferring an Employee Within SAP S∕4HANA

You can transfer an employee within SAP S∕4HANA whose data is mastered in the 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

You can replicate 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 eective start date of this Job
Information record.

Parent topic: Transfer [page 435]

Related Information

Transferring an Employee Within Employee Central [page 437]

Implementing Data Migration and Replication to Employee Central

436 PUBLIC Side-by-Side Deployment Option
4.3.4.2 Transferring an Employee Within Employee Central

The transfer process in Employee Central works as usual. In the side-by-side deployment option described in this
guide, employees whose data is mastered in Employee Central aren't replicated to SAP ERP HCM.

Parent topic: Transfer [page 435]

Related Information

Transferring an Employee Within SAP S∕4HANA [page 436]

4.3.5 International Transfer

You can transfer employees between countries that are mastered in SAP S∕4HANA or in Employee Central.

Employees in International Transfer [page 438]

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

Transferring an Employee from a Country Mastered in Employee Central to Another Country Mastered in
Employee Central [page 439]

Transferring an Employee from a Country Mastered in SAP ERP HCM to a Country Mastered in Employee
Central [page 440]

Transferring an Employee from a Country Mastered in Employee Central to a Country Mastered in SAP
S∕4HANA [page 441]
You can transfer employees from countries that use Employee Central as the system of record to countries
that use SAP S∕4HANA as the system of record.

Parent topic: HR Business Processes for the Side-by-Side Deployment Option in Employee Data Migration [page
426]

Related Information

Prerequisites and Restrictions [page 427]

Hire [page 428]
Rehire [page 432]
Transfer [page 435]
Global Assignment [page 441]
Concurrent Employment [page 446]
Termination [page 451]

Implementing Data Migration and Replication to Employee Central

Side-by-Side Deployment Option PUBLIC 437
4.3.5.1 Employees 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 S∕4HANA 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 as International transfer to Employee Central if the following conditions are ullled for both personnel
numbers:

• They are assigned to dierent countries.

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

When the centralized services switch in Employee Central is enabled, the isRehire eld is set as true or false for
the international transfer scenario. The isRehire eld is considered as a standard eld and the value is set as false
for the rst employment and true for the second employment (rehire) record. In case this eld is not sent, then
the secondary assignments are created in Employee Central, which is not intended for international transfer. For
more information on the IsRehire eld, refer the Non-Congurable (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 dierent
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 rst 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 dierent types of HR processes like Global Assignment, International Transfer
and Concurrent employment for the same employee is not supported.

The behaviour of the infoporter tool for international transfer is as below:

• Infoporter tool creates a new employment for the same employee in Employee Central for every international
transfer.

Implementing Data Migration and Replication to Employee Central

438 PUBLIC Side-by-Side Deployment Option
 • When there is a global transfer from PERNR 1 to PERNR 2, the personal information (infotype 0002), Global
information, 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 rst
assignment before International Transfer mapped with the same person.
• Biographical information of an employee is always extrated from the home PERNR only irrespective of the
employment status.
• For National ID information block, system will extract both the assignment data.

 Note

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.

 Note

The infoporter tool currently migrates the dependent data based on the ERP personnel number. In case of an
international transfer employee, if the same dependent is maintained in both the PERNR's, then the dependent
data is considered for migration twice. If you want to remove the duplicate dependent data, then you need
to use the modify BAdI denition EX_ECPAO_ERP_EMP_DATA_MODIFY for deleting the duplicate dependent
details.

Parent topic: International Transfer [page 437]

Related Information

Transferring an Employee from a Country Mastered in Employee Central to Another Country Mastered in Employee
Central [page 439]
Transferring an Employee from a Country Mastered in SAP ERP HCM to a Country Mastered in Employee Central
[page 440]
Transferring an Employee from a Country Mastered in Employee Central to a Country Mastered in SAP S∕4HANA
[page 441]

4.3.5.2 Transferring an Employee from a Country Mastered

in Employee Central to Another Country Mastered in
Employee Central

The international transfer process in Employee Central works as usual. In the side-by-side deployment option
described in this guide, employees whose data is mastered in Employee Central aren't replicated from SAP
S∕4HANA.

Implementing Data Migration and Replication to Employee Central

Side-by-Side Deployment Option PUBLIC 439
Parent topic: International Transfer [page 437]

Related Information

Employees in International Transfer [page 438]

Transferring an Employee from a Country Mastered in SAP ERP HCM to a Country Mastered in Employee Central
[page 440]
Transferring an Employee from a Country Mastered in Employee Central to a Country Mastered in SAP S∕4HANA
[page 441]

4.3.5.3 Transferring an Employee from a Country Mastered

in SAP ERP HCM to a Country Mastered in Employee
Central

You carry out a Leaving action for the original country in SAP ERP HCM, which has a date in the future. You
replicate the employee's master data to Employee Central. In Employee Central, a Termination event is carried out
for the original country and the employee is set to inactive for the future. You create an additional employment in
Employee Central to assign the employee to the new country.

 Note

A new user is created in Employee Central for the new employment.

Parent topic: International Transfer [page 437]

Related Information

Employees in International Transfer [page 438]

Transferring an Employee from a Country Mastered in Employee Central to Another Country Mastered in Employee
Central [page 439]
Transferring an Employee from a Country Mastered in Employee Central to a Country Mastered in SAP S∕4HANA
[page 441]

Implementing Data Migration and Replication to Employee Central

440 PUBLIC Side-by-Side Deployment Option
4.3.5.4 Transferring an Employee from a Country Mastered
in Employee Central to a Country Mastered in SAP
S∕4HANA

You can transfer employees from countries that use Employee Central as the system of record to countries that use
SAP S∕4HANA as the system of record.

The scenario is this: An employee was hired and then terminated in Employee Central. Then he or she is hired
again in a dierent country, for which you still use SAP S∕4HANA as the system of record. This means, a personnel
assignment (PERNR) is created for the employee in SAP S∕4HANA. Now the employment/personnel assignment
from the country mastered in SAP S∕4HANA is replicated to Employee Central. Both employments (the old,
terminated and the new, replicated employment) coexist there.

To make this process work:

• Select the BAdI Mapping mapping mode for the person_id_external eld in the V_ECPAO_COMPANY
Customizing view.
• Implement the Mapping of User ID, Person ID, User Name, and Object ID
(EX_ECPAO_EMP_USYID_PRN_UNM_MAP) BAdI. Make sure that your BAdI implementation maps the
employee’s person ID from Employee Central to the person ID of the employee's personnel number in SAP
S∕4HANA so that the second employment is replicated to the correct employee in Employee Central.

For more information about the Customizing settings and BAdIs, 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.

Parent topic: International Transfer [page 437]

Related Information

Employees in International Transfer [page 438]

Transferring an Employee from a Country Mastered in Employee Central to Another Country Mastered in Employee
Central [page 439]
Transferring an Employee from a Country Mastered in SAP ERP HCM to a Country Mastered in Employee Central
[page 440]

4.3.6 Global Assignment

You can have global assignments within SAP S∕4HANA, within Employee Central, or between both systems.

Assigning an Employee Globally Within SAP S∕4HANA [page 442]

You can assign an employee globally within SAP S∕4HANA system and store the information in specic
infotypes.

Assigning an Employee Globally Within Employee Central [page 444]

Assigning an Employee Globally in SAP S∕4HANA and Employee Central [page 445]

Implementing Data Migration and Replication to Employee Central

Side-by-Side Deployment Option PUBLIC 441
Parent topic: HR Business Processes for the Side-by-Side Deployment Option in Employee Data Migration [page
426]

Related Information

Prerequisites and Restrictions [page 427]

Hire [page 428]
Rehire [page 432]
Transfer [page 435]
International Transfer [page 437]
Concurrent Employment [page 446]
Termination [page 451]

4.3.6.1 Assigning an Employee Globally Within SAP S∕4HANA

You can assign an employee globally within SAP S∕4HANA system and store the information in specic infotypes.

In SAP S∕4HANA, you should 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 should use the Details on Global
Assignment (0710) infotype. This infotype is mandatory to be maintained for the infoporter tool to identify the
global assignment employment type. Else the HR process is identied incorrectly.
• To determine which personnel number is used to send biographical and personal information to Employee
Central, you should 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. 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 dened a cuto date for data replication, this can aect the start date of the global assignment: If
the cuto date is later than the actual start date of the global assignment, the cuto date is used. If the cuto
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

Implementing Data Migration and Replication to Employee Central

442 PUBLIC Side-by-Side Deployment Option
 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), Global
information (0002 or its secondary infotypes), 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 host address will be created in Employee Central 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 Employee Central 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 Employee Central system.

 Note

Emp_users_sys_id eld should be added into perAddress enitity with the congurations: Enabled = True,
Visibility = view & allow import = Yes in the Employee Central system. This eld has to be included in the
view cluster (VC_ECPAO_MAP) eld 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 is always extrated from home PERNR only irrespective of the
employment status.
• 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 if it is inactive.

When the ERP to EC: Determine Personal Data of Global Employees switch in the V_ECPAO_CONSTANT view is
disabled, the following behavior is applicable: The biographical, personal, global, email address, and phone number
information of an employee will be extracted only from the home PERNR even if the infotype 0712 is maintained
and mentioned for a dierent PERNR as the main assignment.

Implementing Data Migration and Replication to Employee Central

Side-by-Side Deployment Option PUBLIC 443
  Note

When global assignment conguration 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 SAP
S∕4HANA 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 SAP S∕4HANA sent to home
assignment or when the replication from SAP S∕4HANA is triggered again, the automatic events created in EC
will be deleted as the upsert is a full purge.

 Note

The infoporter tool currently migrates the dependent data based on the ERP personnel number. In case of
global assignment for an employee, if the same dependent is maintained in both the PERNR's, then the
dependent data is considered for migration twice. If you want to remove the duplicate dependent data, then
you need to use the modify BAdI denition EX_ECPAO_ERP_EMP_DATA_MODIFY for deleting the duplicate
dependent details.

Parent topic: Global Assignment [page 441]

Related Information

Assigning an Employee Globally Within Employee Central [page 444]

Assigning an Employee Globally in SAP S∕4HANA and Employee Central [page 445]

4.3.6.2 Assigning an Employee Globally Within Employee

Central

Global assignment management in Employee Central works as usual. In the side-by-side deployment option
described in this guide, employees whose data is mastered in Employee Central aren't replicated to SAP ERP
HCM.

Parent topic: Global Assignment [page 441]

Related Information

Assigning an Employee Globally Within SAP S∕4HANA [page 442]

Implementing Data Migration and Replication to Employee Central

444 PUBLIC Side-by-Side Deployment Option
Assigning an Employee Globally in SAP S∕4HANA and Employee Central [page 445]

4.3.6.3 Assigning an Employee Globally in SAP S∕4HANA and

Employee Central

Home assignment in Employee Central, host assignment in SAP S∕4HANA

If an employee has a home assignment (employment) in Employee Central and a host assignment in SAP
S∕4HANA, his or her data can be replicated from SAP S∕4HANA to Employee Central. Both assignments can
coexist.

To make this process work:

• Select the BAdI Mapping mapping mode for the person_id_external eld in the V_ECPAO_COMPANY
Customizing view.
• Implement the Mapping of User ID, Person ID, User Name, and Object ID
(EX_ECPAO_EMP_USYID_PRN_UNM_MAP) BAdI. Make sure that your BAdI implementation contains the
employee's person ID from Employee Central so that the data from the host assignment in SAP S∕4HANA
is replicated to the correct employee in Employee Central.

For more information about the Customizing settings and BAdIs, see the Replicating Employee Data from
SAP S∕4HANA to Employee Central integration guide. Find the most current version of this guide at http://
help.sap.com/hr_ecintegration.

Home assignment in SAP S∕4HANA, host assignment in Employee Central

If an employee has a home assignment in SAP S∕4HANA and his or her data is replicated to Employee Central, you
can just add the host assignment (employment) in Employee Central. Both assignments can coexist.

You can choose any mapping for the user_id, person_id_external, and user eld in the V_ECPAO_COMPANY
Customizing view.

In this scenario, the person-related employee master data is kept up to date in the SAP S∕4HANA system for the
home assignment. Changes are replicated to Employee Central.

Deactivating the home assignment

To deactivate the home assignment during the host assignment period, terminate the employee's home
assignment when the host assignment starts and rehire the employee when the host assignment ends.

Parent topic: Global Assignment [page 441]

Implementing Data Migration and Replication to Employee Central

Side-by-Side Deployment Option PUBLIC 445
Related Information

Assigning an Employee Globally Within SAP S∕4HANA [page 442]

Assigning an Employee Globally Within Employee Central [page 444]

4.3.7 Concurrent Employment

Concurrent employment can either be within SAP S∕4HANA or within Employee Central.

Employee Having Concurrent Employment in SAP S∕4HANA [page 446]

You can migrate an employee who has several personnel assignments.

Concurrently Employing an Employee Within Employee Central [page 450]

Parent topic: HR Business Processes for the Side-by-Side Deployment Option in Employee Data Migration [page
426]

Related Information

Prerequisites and Restrictions [page 427]

Hire [page 428]
Rehire [page 432]
Transfer [page 435]
International Transfer [page 437]
Global Assignment [page 441]
Termination [page 451]

4.3.7.1 Employee Having Concurrent Employment in SAP

S∕4HANA

You can migrate an employee who has several personnel assignments.

In SAP S∕4HANA, an employee who has several personnel assignments (personnel numbers) with the employment
status Active within the same country is considered as concurrently employed. While creating the second
employment, the rst employment should be still active. In Employee Central, an employment is created for each of
the employee's personnel assignments.

In the employment info entity, the IsRehire ag value is extracted as false for both the employments. This ag
setting make sure that the secondary assignment entity is created in theEmployee Central system denoting it as
concurrent employment.

Implementing Data Migration and Replication to Employee Central

446 PUBLIC Side-by-Side Deployment Option
For concurrent employment by default, the entities like personal info (WS_5), address (WS_10), email (WS_7), and
phone (WS_8) are extracted from rst employment only, irrespective of whether the rst employment is active or
withdrawn.

A new switch ERP to EC: Determine Personal Data for Concurrent Employment has been introduced to fetch
information (Personal information and Address information) from all concurrently employed PERNR's. When you
enable the constant ERP to EC: Determine Personal Data for Concurrent Employment in the V_ECPAO_CONSTANT
view, eective templates like personal information and the address information are sent from all the PERNR's
related to that concurrent employment based upon the earliest transfer date. For non-eective dated templates,
like email and phone number information will be sent from the latest active PERNR on the earliest transfer date.

If you want to migrate the information (Personal information and Address information) from only one
particular active or leading PERNR for your EC instance ID. PERNR then you can use the BAdI
EX_ECPAO_IDNTFY_MAIN_PERNR. The BAdI classies the main PERNR when more than one PERNR's are
concurrently employed. The same PERNR is then used to migrate the entities like (personal Info(WS_5) and
address info(WS_10)) and, email (WS_7), and phone (WS_8) entities.

 Note

If the BAdI EX_ECPAO_IDNTFY_MAIN_PERNR is implemented in the system and returns the main PERNR then
the switch is not considered. In case the switch is active and if the BAdI implementation does not return the
main PERNR, then the switch is considered.

When EX_ECPAO_IDNTFY_MAIN_PERNR BAdI is not implemented and ERP to EC: Determine Personal Data for
Concurrent Employment switch is inactive in the constants table, following points are applicable:

• The user (WS_1), biographical (WS_2), personal info (WS_5), email (WS_7), phone (WS_8), address (WS_10),
national ID (WS_17), global info (WS_18), personal relationship (WS_19) are extracted from the rst
employment only.
• For the employment details (WS_3), job information (WS_4), job relationship (WS_9), compensation (WS_11),
pay comp recurring (WS_12), pay comp non recurring (WS_13), PIV3 details (WS_14), termination (WS_15),
PIV3 (WS_16), cost distribution (WS_20), and cost distribution item (WS_21) both the PERNR's are extracted.
• Based on the employment info, user API will create the user and biographical entity data for secondary
assignment in the Employee Central system by default.
• The termination entity is extracted, in case of any employment is terminated.
• When the rst employment is terminated before the cut o date:
• If additional events are not maintained, rst employment details will be skipped from the data extraction
process and the secondary employment details will be extracted when the rst employment is terminated
before the cuto date.
• When additional events are maintained, all non-eective dated entities with personal data (personal
information and address information) will be extracted from the rst employment and eective dated
entities will be extract data from both the employments.

When the constant switch ERP to EC: Determine Personal Data for Concurrent Employment is active and the BAdI
does not return value for the PERNR, then the following options are applicable:

• If the switch is active, then the personal infomation and address information is fetched from all the PERNR's.
The email and phone number information is fetched from the latest active PERNR.
• In a scenario where the 1st PERNR and 2nd PERNR have the same start date and the 3rd PERNR started later,
the personal information and address data will be extracted from the 2nd PERNR (based on number range if
the begin date is same for 2 PERNR's) and 3rd PERNR. The email and phone data will be extracted from the
latest active PERNR if it has data. In this case, the 3rd PERNR is the latest active PERNR.

Implementing Data Migration and Replication to Employee Central

Side-by-Side Deployment Option PUBLIC 447
• In a scenario where the 1st PERNR and 2nd PERNR have the same start date and the 3rd PERNR started later
and terminated after some time, the personal information and address data will be extracted from the 2nd
PERNR and 3rd PERNR (till the 3rd PERNR termination date) and remaining information from 1st PERNR. The
email and phone data will be extracted from the latest active PERNR, in this case, the 2nd PERNR is the latest
active PERNR.
• If an employee does not have their personal data or address data on the cutover date, then that time interval
will be skipped, and the later time interval will be extracted instead.

 Example

As of the cutover date, PERNR2 is active but does not have any address data maintained. As a result, no
address data is being extracted from PERNR2. Address data is currently being extracted from PERNR3
creation date onwards.

When the BAdI EX_ECPAO_IDNTFY_MAIN_PERNR is implemented, then the following options are applicable:

• If the BAdI is implemented and returns the main PERNR, then the personal information, address information,
phone, and email address is fetched from the BAdI-dened PERNR.
• If the constant switch is enabled and BAdI implementation is active and returns the main PERNR at the
same time, then the constant switch will no longer have any eect and will be overridden by the BAdI
implementation.
• If a BAdI-dened PERNR is terminated, then the email and phone data will still be extracted from the same
PERNR. If the data is not maintained, then a compound deletion will be triggered if the PERNR already
migrated email and phone.
• When the BAdI is implemented and returns the main PERNR and if there is a record before the BAdI-dened
PERNR, the personal and address information would be split into two segments. The rst segment would cover
the time period from the rst PERNR's cutover date to the BAdI-dened PERNR creation date, and the second
segment would cover the time period from the BAdI-dened PERNR creation date to the end date.

Implementing Data Migration and Replication to Employee Central

448 PUBLIC Side-by-Side Deployment Option
Here are some of the use case scenariors where the PERNR details are fetched based on the switch and BAdI
status:

Scenario 1:

Scenario 2:

Implementing Data Migration and Replication to Employee Central

Side-by-Side Deployment Option PUBLIC 449
Scenario 3:

BAdI returns PERNR2 (PERNR2 is the leading or the main PERNR in this case)

 Note

With the current enhancement the global information entity is not supported.

The infoporter tool currently migrates the dependent data based on the ERP personnel number. In case of
concurrent employment, if the same dependent is maintained in both the PERNR's, then the dependent data is
considered for migration twice. If you want to remove the duplicate dependent data, then you need to use the
modify BAdI denition EX_ECPAO_ERP_EMP_DATA_MODIFY for deleting the duplicate dependent details.

Parent topic: Concurrent Employment [page 446]

Related Information

Concurrently Employing an Employee Within Employee Central [page 450]

4.3.7.2 Concurrently Employing an Employee Within

Employee Central

The concurrent employment process in Employee Central works as usual. In the side-by-side deployment option
described in this guide, employees whose data is mastered in Employee Central aren't replicated to SAP ERP HCM.

Implementing Data Migration and Replication to Employee Central

450 PUBLIC Side-by-Side Deployment Option
Parent topic: Concurrent Employment [page 446]

Related Information

Employee Having Concurrent Employment in SAP S∕4HANA [page 446]

4.3.8 Termination

You can terminate employees either in SAP S∕4HANA or in Employee Central, depending on which is the system of
record.

Terminating an Employee Mastered in SAP S∕4HANA [page 451]

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

Terminating an Employee Mastered in Employee Central [page 452]

Parent topic: HR Business Processes for the Side-by-Side Deployment Option in Employee Data Migration [page
426]

Related Information

Prerequisites and Restrictions [page 427]

Hire [page 428]
Rehire [page 432]
Transfer [page 435]
International Transfer [page 437]
Global Assignment [page 441]
Concurrent Employment [page 446]

4.3.8.1 Terminating an Employee Mastered 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
Employee Central, a Termination event with the Termination event reason is carried out and a new Job Information
record is created.

Implementing Data Migration and Replication to Employee Central

Side-by-Side Deployment Option PUBLIC 451
  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: Termination [page 451]

Related Information

Terminating an Employee Mastered in Employee Central [page 452]

4.3.8.2 Terminating an Employee Mastered in Employee

Central

The termination process in Employee Central works as usual. In the side-by-side deployment option described in
this guide, employees whose data is mastered in Employee Central aren't replicated to SAP S∕4HANA.

Parent topic: Termination [page 451]

Related Information

Terminating an Employee Mastered in SAP S∕4HANA [page 451]

4.4 Special Use Cases in Data Replication to Employee

Central

Take a look at special use cases that can occur during data replication to Employee Central.

Implementing Data Migration and Replication to Employee Central

452 PUBLIC Side-by-Side Deployment Option
4.4.1 How to Use Country Filtering for the Side-by-Side
Deployment Option
This section is relevant if you want to perform country ltering in the side-by-side deployment option.

Context

You can use the country ltering when you want to restrict the migration of data based on the country grouping.
Using this, you can migrate the full scope of data to Employee Central for a set of countries, which are in scope will
be mastered in EC and mini master data for another set of countries, which are not in scope are mastered in ERP. If
an EC entity has been ltered out for a country, then this entity will be not extracted for a PERNR belonging to that
country even if that template is active in the template group conguration.

Procedure

Choose the EC templates, which are not in scope against a country using the customizing activity: Filter EC Entities
for Migrating Employee Data to EC based on Country (view V_ECPAO_ECTM_FIL).

 Example

If country Switzerland is mastered in EC and Greece is mastered in ERP, then full scope will be used for
Switzerland and mini-master scope for Greece. You can dene the mini-master scope by specifying the EC
entities which should be ltered out during the extraction process from ERP. In this case, you can lter all the
templates other than the mini master scope for country Greece using the view V_ECPAO_ECTM_FIL.

Country Grouping EC Entity

45 WS_7

45 WS_8

45 WS_9

45 WS_10

4.4.2 How to Use SAP SuccessFactors Compensation Together

with the Side-by-Side Deployment Option
This section is relevant if you use SAP SuccessFactors Compensation and now want to start using the side-by-side
deployment option.

This means you start employee data replication from on-premise SAP S∕4HANA systems to SAP SuccessFactors
Employee Central, where you have previously used either the integration add-on for SAP S∕4HANA and SAP

Implementing Data Migration and Replication to Employee Central

Side-by-Side Deployment Option PUBLIC 453
SuccessFactors HCM Suite provided by SAP (also known as Talent Hybrid integration) or another integration
process to replicate employee data from an on-premise SAP S∕4HANA system to the Employee Prole in the SAP
SuccessFactors Talent Suite.

When you use the side-by-side deployment option, Employee Central contains two dierent types of data records
for employees:

• Employees whose data is mastered in Employee Central

The Source of Record eld in the Employment Information of these employees shows the entry EC. The data is
editable in Employee Central.
• Employees whose data is mastered in SAP S∕4HANA and replicated to Employee Central
The Source of Record eld in the Employment Information of these employees shows an entry that's dierent
from EC (for example, ERP). The data is not editable in Employee Central.

This has some inuence on how you need to set up compensations plan templates and compensation plans:

• Make sure that your compensation plan template is EC-enabled.

This can be done by entering an eective date in the Plan Settings page. "EC-enabled" means that you've set
up Employee Central- Compensation integration and use the compensation plan templates in this integrated
environment.
• Make sure that you enable your compensation plan to be a hybrid plan.
This can be done by selecting the hybrid setting on the Settings page. "Hybrid" in general means that the
compensation plan retrieves employee data from both Employee Central and other sources. In the side-by-
side context it means in particular that Employee Central feeds general user data (such as the user ID and
the employee's name and supervisor/manager) of all employees to the Employee Prole using the Human
Resource Information System (HRIS) synchronization (the exchange of data between Employee Central
and other SAP SuccessFactors modules). This is independent of whether an employee's data is mastered
in Employee Central or in SAP S∕4HANA. Compensation-specic data, however, is retrieved from dierent
sources, depending on the employee's master system:
• For employees whose data is mastered in Employee Central, compensation-specic information is passed
from Employee Central to the compensation worksheet. The Employee Central- Compensation integration
lters out employees whose data is not mastered in Employee Central. The results of a compensation cycle
are published back to Employee Central.
• For employees whose data is mastered in SAP S∕4HANA, compensation-specic data is transferred from
SAP S∕4HANA to Compensation. SAP S∕4HANA pulls the results of a compensation cycle from SAP
SuccessFactors Compensation.

 Note

When you use the side-by-side deployment option, the following features are not available:

• You can't retrieve performance ratings from two dierent sources (which would be SAP SuccessFactors
Performance Management for employees whose data is mastered in Employee Central and SAP
S∕4HANA's Performance Management module for employees whose data is mastered in SAP S∕4HANA).
• You can't use variable pay templates in SAP SuccessFactors Compensation.

Implementing Data Migration and Replication to Employee Central

454 PUBLIC Side-by-Side Deployment Option
4.4.3 How to Use Employee Central Advanced Reporting in the
Side-by-Side Deployment Option
This section is relevant if you want to use Employee Central standard reports in the side-by-side deployment
option.

Context

You can use the standard reports of Employee Central Advanced Reporting for employees whose data is mastered
in SAP S∕4HANA and replicated to Employee Central using the employee data replication described in this guide.
This enables you to run global reports on all employees in Employee Central, independent of the system of
record in which the employees' data is mastered. We recommend to do local reporting in the system in which the
employee's data is mastered.

To use standard reports in the side-by-side deployment option, carry out the steps described below.

Procedure

1. Enable the advanced reporting for your company instance.

For more information refer to the Online Report Designer implementation guide. Find the most current version
of these guides at http://help.sap.com/hr_analytics.
2. Get an overview of the existing reports, create new reports, or adjust standard reports to suit your
requirements.

Pre-delivered standard reports are available in Advanced Reporting in Employee Central. You can copy and
adapt these reports as according to your company's needs. The resulting data can also be easily exported
and reused in other tools or applications such as Microsoft Excel. Advanced reports can be roughly classied
according to the following categories:
• Benets
• Compensation
• Employment information, such as Employee Register, Employment Changes, Headcount and FTEs, New
Hires, Terminated Employment
• Global assignments, such as Global Assignment: Contact Details and Global Assignment: Accompanying
Dependents
• Payment information
• Payroll, such as the Data Replication Monitor
• Pension plans, such as Pension Overview
• Personal information, such as Challenged Employees, Dependents, and contact information
• Position management, such as Position Details and Position Overview
• Time-o reports, such as Absence Overview, Time Account Overview and Time Account Snapshot
• Workow information

For more information about the existing standard reports refer to the Employee Central Advanced Reporting:
Standard Reports reference guide. For more information abut how to change standard reports refer to the

Implementing Data Migration and Replication to Employee Central

Side-by-Side Deployment Option PUBLIC 455
 Advanced Reporting in the Online Report Designer administration guide. Find the most current version of these
guides at http://help.sap.com/hr_analytics.
3. Use specic reports in the side-by-side deployment option.

When you replicate employee master data from the SAP S∕4HANA system to Employee Central as described
in this guide, you can use some standard reports for global reporting on all employees whose data is mastered
in Employee Central and all employees whose data is mastered in SAP S∕4HANA and replicated to Employee
Central. The following reports are available for both groups of employees:
• Age Ranges
• Headcount and FTEs
• Service Anniversaries
• Birthday List
• Job Assignment
• Terminated Employments
• Employee Register
• Job Relationships
• Employment Changes
• New Hires

When using these reports take into account the following preconditions:
• Only data which is part of the replication can be included in the reports. For a list of the data that can
be replicated by default, 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.
• If a eld is not lled by the data replication from SAP S∕4HANA to Employee Central, it must be part of the
SuccessFactors data options. If the eld is not lled at all, the corresponding report dumps.
• We recommend to use the validation tool to check if a reports runs in your specic environment. To do so:
1. Go to Home Analytics , then click Analytics and choose Report Designer from the Tools panel.

Implementing Data Migration and Replication to Employee Central

456 PUBLIC Side-by-Side Deployment Option
 2. Click the report name.

3. Right-click the report and choose Validate this component from the context menu.

Implementing Data Migration and Replication to Employee Central

Side-by-Side Deployment Option PUBLIC 457
 • The Source of Record eld must be correctly lled for each employee whose data is replicated from SAP
S∕4HANA to Employee Central. Otherwise the employee can't be included in any reporting. In the standard,
this eld is lled as required. For more information see the Replicating Employee Data from SAP ERP HCM
to Employee Central integration guide.

4.4.4 Supporting the Migration of Long Term Absence Records

Learn how to congure the migration of the long term absence leave record.

Prerequisites

You will have to create two new event reasons of event type DATACHG with status paid or un-paid leave in Employee
Central.

 Example

• PSEUDO_DATACHG_LOA_START
• PSEUDO_DATACHG_LOA_END

Context

Irrespective of the switch (When Time O or Time O for Leave of Absence Only) status the job info records with
event reason corresponding to leave of absence (LOA) cannot be imported to Employee Central. You need to
use the MDF object EmployeeTime and create the leave of absence dates and time period for a particular user
through the Import and Export data tool. This will inturn create the LOA events (LOA start and LOA end) in the

Implementing Data Migration and Replication to Employee Central

458 PUBLIC Side-by-Side Deployment Option
job information as per congurations. These events will be appearing in the job info as part of sync jobs from
EmployeeTime Object (parent object).

For more information, refer to3228287 .

Procedure

1. In your SAP S∕4HANA system, go to the (SPRO) transaction and choose SAP Reference IMG. In
the SAP Customizing Implementation Guide structure, open Personnel Management Integration with
SuccessFactors Employee Central Business Integration Builder Data Migration and Replication to Employee
Central Employee Data Dene Field Mapping for Employee Data .
2. Choose the transformation template group that you are using.
3. Choose transformation template corresponding to Job Info (WS_4).
4. In the Primary mapping screen, double click the Event reason eld.
5. In the value mapping section, click the Dene value mapping entries button.
6. In the Value Mapping Details view, for the ERP value corresponding to Leave of Absence and Return to work,
maintain the new event reasons (Eg: PSEUDO_DATACHG_LOA_START and PSEUDO_DATACHG_LOA_END)
created in Employee Central.
7. Save the changes.
8. Run the migration report for the employee. Run the migration as often as needed.
9. For employees who have their system of record as ERP, the time data need not be maintained in SAP
SuccessFactors Employee Central. Later over time, when you move away from Side-by-Side deployment option
to Core hybrid model making their system of record as Employee Central, you would have to import the
absence information into Employee Central via the EmployeeTime object.

There is no automatic migration from these Data Change events to Employee Time (Leave of Absence and
Return to Work events). This should be a manual activity. Further as long as the employee data is mastered in
ERP, you should consider this DATAchange event for their reporting and other purposes.
10. For the employees which as the system of record as Employee Central, after all the migration is done,
you can use the Import and Export Data tool to create the Employee Time Object containing the leave of
absence information. After the import, as per congurations in your system, the job info shall show the
PSEUDO_DATACHG_LOA_START and the actual LOA START events.

Implementing Data Migration and Replication to Employee Central

Side-by-Side Deployment Option PUBLIC 459
5 Change History

Learn about changes to the documentation for Implementing Data Migration and Replication to Employee Central
in recent releases.

1H 2024 / SP03 of ECS4HCM Add-On

Type of Change Description More Info

New You can now connect multiple Employee Connecting Multiple Employee Central
Central instances to the same client of Instances to the Same SAP S∕4HANA Cli-
your SAP S/4HANA system. ent [page 242]

Changed You can now migrate data from all con- Employee Having Concurrent Employ-
current employments based on the new ment in SAP S∕4HANA [page 446]
conguration options in SAP S/4HANA
system.

Changed You can now migrate the Manager ID eld Extracting Employees Manager Informa-
value in the employee job information tion [page 212]
entity by using the variant concept and
by choosing the dierent transformation
template groups in each step.

2H 2023 / SP02 of ECS4HCM Add-On

Type of Change Description More Info

Changed Support package 02 of the SFSF EC S4 Installing the Required Software Compo-
nent Versions and Support Packages in
HCM INTEGRATION (ECS4HCM) add-on
SAP S∕4HANA [page 48]
must be installed in your SAP S/4HANA
system.

Added In the conguration of the SAP S∕4HANA Enabling and Testing the SAP S∕4HANA
outbound web services, we've added in- Outbound Web Service [page 55]
formation about which settings are avail-
able in the corresponding integration
ow for which authentication option, de-
pending on whether you use SAP Cloud
Integration in the Cloud Foundry or the
Neo environment.

Added New picklist writer report import picklists Import Picklists from Employee Central
and picklist values from Employee Central using Web Service [page 89]
to the SAP S∕4HANA system system by
using OData query.

Implementing Data Migration and Replication to Employee Central

460 PUBLIC Change History
1H 2023

Type of Change Description More Info

New We have updated how the concurrent em- Employee Having Concurrent Employ-
ployees behave for non-eective dated ment in SAP S∕4HANA [page 446]
entities data and eective dated entities.

Changed Support package 01 of the SFSF EC S4 Installing the Required Software Compo-
HCM INTEGRATION (ECS4HCM) add-on nent Versions and Support Packages in
must be installed in your SAP S/4HANA SAP S∕4HANA [page 48]
system.

Changed We are currently supporting the global For Which Employee Data-Related Em-
info data migration for additional info-
ployee Central Entities Can I Use Data
types.
Replication? [page 68]

Employee Having Global Assignment in

SAP ERP HCM [page 390]

Employees in International Transfer

[page 438]

Changed Employee and organizational object data Extracting Employee Data [page 202]
report has been enhanced to update the
change pointer table. Parallelization of Employee Data Extrac-
tion with the Job Scheduler Report [page
238]

Extracting Organizational Data [page

324]

Parallelization of Organizational Data Ex-

traction Via Job Scheduler Report [page
337]

Changed We have enhanced the work schedule re- Work Schedule Objects Created in Em-
port to support zero working hours. ployee Central [page 402]

Implementing Data Migration and Replication to Employee Central

Change History PUBLIC 461
Important Disclaimers and Legal Information

Hyperlinks
Some links are classied 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 an 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 ofcially 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 sufciently backed up.
The purpose of experimental features is to get feedback early on, allowing customers and partners to inuence 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.

Implementing Data Migration and Replication to Employee Central

462 PUBLIC Important Disclaimers and Legal Information
Implementing Data Migration and Replication to Employee Central
Important Disclaimers and Legal Information PUBLIC 463
www.sap.com/contactsap

© 2024 SAP SE or an SAP afliate 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
afliate 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 specications may vary.

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

informational purposes only, without representation or warranty of any
kind, and SAP or its afliated companies shall not be liable for errors or
omissions with respect to the materials. The only warranties for SAP or
SAP afliate 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 afliate 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