PUBLIC

SAP Best Practices for SAP SuccessFactors Employee Central Integration

Document Version: 1H 2023 – 2023-04-27

Migrating Data from ERP HCM to Employee

Central: Configuration Guide
© 2023 SAP SE or an SAP affiliate company. All rights reserved.

THE BEST RUN

Content

1 Migrating Data from ERP HCM to Employee Central. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3

2 Change History. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4

3 Activation of Content. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5

4 Overview of Manual Activities to be Performed. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6

5 Assumptions. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .7
5.1 Organizational Data Migration Assumptions. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7
Business Units and Divisions. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .7
FTE for Positions Objects. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8
5.2 Employee Data Migration Assumptions. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .8

6 Configuration Steps. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10
6.1 Configuration Details. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .10
Basic Settings. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 11
6.2 Configuration Steps in Employee Central System . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 27
Creating Foundation Objects and MDFs for Migration. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 27
Extracting Employee Data with Additional Events Before Earliest Transfer Date. . . . . . . . . . . . . . 34
6.3 Adaptations. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 35
Updating Fields (Text in Employee Central but Dropdown in ERP HCM). . . . . . . . . . . . . . . . . . . . 36
Updating Metadata. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 36
Updating Picklist. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 37
Updating Value Mapping. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .38
Updating Field Mappings for Organizational Data/Employee Data. . . . . . . . . . . . . . . . . . . . . . . 38
Updating Field Mappings for Italy (Province and Comuni). . . . . . . . . . . . . . . . . . . . . . . . . . . . . 38
Cost Center Logic when Cost Center Being Replicated is not Exactly 14 Characters. . . . . . . . . . . 39
Cost Center Mapping for Organizational Objects. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .39
Copying Best Practices Templates. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .40

Migrating Data from ERP HCM to Employee Central: Configuration Guide

2 PUBLIC Content
1 Migrating Data from ERP HCM to
Employee Central

The purpose of this guide is to assist with the migration of organizational and employee data from an SAP
ERP on-premise system to an SAP SuccessFactors Employee Central using SAP Cloud Platform Integration
as the middleware. Configuration steps and field mappings best practices are delivered to jump start the
migration process.

The guide is primarily intended for the core hybrid deployment option. Core hybrid deployment option means
that Employee Central is used as the system of record holding all organizational data, but existing processes
such as Payroll, Time Management, or custom HR processes still run in an SAP ERP HCM on-premise system
landscape.

The delivered mappings can also be used for side-by-side deployment if needed but that is outside the scope of
this guide.

Migrating Data from ERP HCM to Employee Central: Configuration Guide

Migrating Data from ERP HCM to Employee Central PUBLIC 3
2 Change History

Learn about changes to the documentation for Migrating Data from ERP HCM to Employee Central in recent
releases.

2H 2022

Type of Change Description More Info

None We did not update this document

1H 2022

Type of Change Description More Info

Changed Replaced by the NextGen Admin opt-in All where path was given for One Admin
feature. opt-in feature.

Added We added localized content for Brazil,

India, and The Netherlands

2H 2021

Type of Change Description More Info

Added We added localized content for Italy and

France.

Migrating Data from ERP HCM to Employee Central: Configuration Guide

4 PUBLIC Change History
3 Activation of Content

The Best Practices content is shipped as Business Configuration Sets as part of the PA_SE_IN component,
however they are not active by default. In order to activate and see the configuration content, perform the
following steps.

Procedure

1. Log on to the SAP ERP HCM system.

2. Enter transaction code SA38 - ABAP Program Execution.
3. Execute the report RP_SBP_ECPAO_ACTIVATE_CONTENT.
4. Checkbox Overwrite Values: It is recommended to check this box for the first activation, since you do not
have any values that can be over-written.
5. Checkbox Test Mode: This can be used to run the activation in test mode prior to the first productive run.
6. Logs: After the execution of the program, choose the Back button to view the BC set activations log.

As a result of the execution of the program, the SAP Best Practices content for migration/replication is
automatically activated. The configuration is inserted into appropriate IMG activities which are described in
detail in the subsequent sections of this guide. Together with some manual steps described in Overview of
Manual Activities to be Performed [page 6] and some assumptions on the Assumptions [page 7], you
may be ready to run the EC-ERP migration.

 Note

If you need to modify/adapt the SAP Best Practices content, for example, for custom fields in the Employee
Central instance, refer to the Adaptations [page 35] section.

Migrating Data from ERP HCM to Employee Central: Configuration Guide

Activation of Content PUBLIC 5
4 Overview of Manual Activities to be
Performed

After the activation of automated content, it is still necessary to perform the following manual activities. This
section describes the manual activities required at a high-level. The details of each manual activity are found in
the corresponding sections of IMG activities.

1. Import Picklists into ERP: Import picklists from the EC instance into the ERP HCM system using the
program ECPAO_PICKLIST_WRITER.
2. Adjust the Value Mapping Entity Definitions: Execute transaction SPRO and choose SAP Reference
IMG for the SAP Implementation Guide. Navigate to Personnel Management Integration with
SuccessFactors Employee Central Business Integration Builder Basic Settings Define Value Mapping
Define Value Mapping Entities . Choose Employee Central instance SBP_MODEL_US. Replace the Dummy
Picklists (denoted by Picklist ID = 1) with the correct Picklist ID based on your latest picklist import from
the Employee Central instance.
3. Value Mapping Details: We provide sample Value Mapping Entries for certain fields. Review and enhance/
adapt as per your need. You can also refer to Updating Value Mapping [page 38] in this document.
4. Earliest Transfer Date: In sample content, we provide earliest transfer date as 01.09.2019. Ideally in real
business case scenarios, the earliest transfer date is the Go-Live Date and always greater than hire date of
existing employees in ERP. This has to be adapted as per requirements.
5. Work Schedule Migration: For migrating work schedules, it is necessary to change the properties of some
objects in the Employee Central instance. If the workschedule codes migrated from ERP to EC are not
same, then you would need to adapt the value mapping details for the work schedule.
6. Dummy Business Unit and Division: SAP Best Practices content configuration does not know which
Business Unit/Divisions a customer has. Therefore, as a placeholder, we assume a Dummy Business
Unit and Division. To make the content work immediately after activation, you need to create a Dummy
Business Unit and a Dummy Division in the Employee Central instance. This is explained in Creating
Foundation Objects and MDFs for Migration [page 27].
7. Business Add-Ins: The SAP Best Practices content provides sample implementation classes for the ERP-
EC migration. However, it is necessary that you create Business Add-In (BAdI) implementations using
those implementation classes. Refer to the Business Add-ins [page 23] for details.
8. Placeholder records (additional records before cut-off date): This is an optional activity that some
migrations may need. For more details please refer to Extracting Employee Data with Additional Events
Before Earliest Transfer Date [page 34].
9. If you would like to adapt the Best Practices content, refer to Adaptations [page 35].
10. Copying Best Practices into your own namespace is explained specifically in Copying Best Practices
Templates [page 40].

Migrating Data from ERP HCM to Employee Central: Configuration Guide

6 PUBLIC Overview of Manual Activities to be Performed
5 Assumptions

Overview:

SAP Best Practices Content for Migration provides configuration content intended to be used as an accelerator.
Since every customer’s specific configuration is unique, the content is built in a generic manner based on
the SAP Best Practices for SAP SuccessFactors Employee Central. This section describes some important
assumptions based on the design of the configuration templates .

5.1 Organizational Data Migration Assumptions

5.1.1 Business Units and Divisions

In the default solution, the department template is activated, and Division and Business Unit templates are
deactivated. This means every organizational unit is extracted as a Department. This is because the extraction
program extracts each organizational as a Department, Division or Business Unit, and will not extract the same
object as part of multiple templates. The identification characteristics of Business Units and Divisions differ
for every customer in their ERP system. If you wish to adapt this, you would need the appropriate logic to
distinguish between the Divisions, Business Units and Departments in your ERP system.

Once you identify which organizational objects are Divisions and Business Units, you can activate the Division
and Business Unit templates to extract those organizational objects. In order to facilitate the extraction, the
following options are available:

1. Providing a selection that consists of only one type of organizational object (Business Unit, Division or
Department) in the Organizational Data Migration Report and running the report separately for each
type.
2. Using the BAdI between Validity Periods for Data Replication to Employee Central to filter out/
distinguish Organizational Objects that are Business Units, Division and Department.

In addition, you would also have to:

1. Modify the logic in the Department template to assign the appropriate Division Organizational Object as a
reference.
2. Modify Value Mapping Entities for BUSINESS_UNIT_WS and DIVISION_WS, if needed.
3. Add the same logic to the field mapping of Business Unit and Division in the Position Template to ensure
that the appropriate Business Units and Divisions are assigned to the position object. By default, a
Dummy Business Unit and a Dummy Division are used in the Position template mappings (by using the
value mapping entities BUSINESS_UNIT_WS and DIVISION_WS) since these fields are required fields in
Employee Central.

Migrating Data from ERP HCM to Employee Central: Configuration Guide

Assumptions PUBLIC 7
5.1.2 FTE for Positions Objects

The default mapping for FTE delivered out of the box assumes that the target FTE field for the positions being
extracted from ERP systems will have a target value of 1 FTE. You can modify this for your requirement by
changing the field mapping and/or value mapping details or by using a BAdI.

5.2 Employee Data Migration Assumptions

When migrating employee data from ERP HCM, we make several assumptions primarily in the BAdI coding,
value mappings and field mappings. Below you will find an overview of the assumptions made. If your specific
situation does not meet these assumptions, consider the Adaptations [page 35].

1. Position Management functionality is enabled.

2. Location and Sub-location in Employee Central: The SAP Best Practices solution maps the Location
Foundation Object to Personnel Area (WERKS) from the ERP HCM system. The Personnel Sub Area
is mapped to Sub Location, a custom MDF Object created in Employee Central. For Sub Location, a
concatenation of Personnel Area and Personnel Sub Area is maintained as the key to keep it unique. This is
because the Personnel Sub Area Code has to be unique in Employee Central whereas in ERP HCM system,
the same personnel area can be reused across different Personnel Areas.
So, for example, if Personnel Areas in ERP are ES01 and ES02 (as shown in the image below), and
Personnel Sub Area 0001 is present for both Personnel Areas, then in Employee Central, the Sub Location
keys would be ES01-0001 and ES02-001.

 Note

The same logic is used when deriving Personnel Area and Personnel Sub Area from Location and Sub
Location for the EC-ERP replication.

3. Employment Type and Employee Class: The Employment Type and Employee Class are pre-delivered in
the SAP Best Practices Employee Central instance. Value mapping needs to be maintained between the
values maintained for Employee Class and Employment Type in the ERP system to the values in Employee
Central. You can choose country specific or global value mapping.
4. Other Foundation Objects: They have the same pattern as the current values in the SAP Best Practices for
Employee Central. Pay Scale Area, Pay Scale Group, Pay Scale Type are examples of this. Pay components
are created with the pattern <Wagetype><ISOCode>.

Migrating Data from ERP HCM to Employee Central: Configuration Guide

8 PUBLIC Assumptions
 5. Effective dated entries for Employee data: The BAdIs currently support bringing over the latest effective
dated entry in the infotypes. If you would like to change the behavior, for example, to bring multiple
effective dated entries, then you will need to modify the logic in the BAdI.

Migrating Data from ERP HCM to Employee Central: Configuration Guide

Assumptions PUBLIC 9
6 Configuration Steps

6.1 Configuration Details

The automated content activation already inserts the configuration below. This section is a description of what
is delivered as part of the Best Practices content and any additional activities needed.

The configuration steps for migration/integration with SuccessFactors Employee Central can be accessed via
the SAP Implementation Guide.

Procedure

1. Log on to the SAP ERP system.

2. Execute transaction SPRO for the SAP Implementation Guide.

The configuration steps are listed under Personnel Management Integration with SuccessFactors
Employee Central Business Integration Builder .

The path shown above is the starting point for all the IMG activities described in the sections below.

Migrating Data from ERP HCM to Employee Central: Configuration Guide

10 PUBLIC Configuration Steps
6.1.1 Basic Settings

Procedure

1. Log on to the SAP ERP HCM system.

2. Execute transaction SPRO for the SAP Implementation Guide and choose SAP Reference IMG.
3. Navigate to Personnel Management Integration with SuccessFactors Employee Central Business
Integration Builder Basic Settings .

The following configuration is delivered as part of the SAP Best Practices content.

6.1.1.1 Specify Employee Central Instance ID

Procedure

Execute transaction SPRO and choose SAP Reference IMG for the SAP Implementation Guide. Navigate to
Personnel Management Integration with SuccessFactors Employee Central Business Integration Builder
Basic Settings Specify Employee Central Instance ID .

The delivered EC Instance ID for Best Practices is SBP_MODEL_US – SAP Best Practices for USA. This
instance contains the metadata from the SAP Best Practices Employee Central instance and other related
configurations.

Migrating Data from ERP HCM to Employee Central: Configuration Guide

Configuration Steps PUBLIC 11
6.1.1.2 Constants for Integration with SuccessFactors

Procedure

Execute transaction SPRO and choose SAP Reference IMG for the SAP Implementation Guide. Navigate to
Personnel Management Integration with SuccessFactors Employee Central Business Integration Builder
Basic Settings Maintain the Constant Values .

The following constants are pre-delivered.

6.1.1.3 Define Additional Foundation Objects for Migrating

Data to Employee Central

Procedure

Execute transaction SPRO and choose SAP Reference IMG for the SAP Implementation Guide. Navigate to
Personnel Management Integration with SuccessFactors Employee Central Business Integration Builder
Basic Settings Define Additional Foundation Objects for Migrating Data to Employee Central .

The following Foundation Objects are pre-delivered. SAP Best Practices added: Location, Pay-scale Type, Pay-
scale area, Pay-scale Group, and Pay Group to the standard entries already delivered along with the PA_SE_IN
application.

Migrating Data from ERP HCM to Employee Central: Configuration Guide

12 PUBLIC Configuration Steps
6.1.1.4 Import Metadata from Employee Central

Metadata from the SAP Best Practices for Employee Central such as Field Names and Field Descriptions for
each of the Employee Central templates are pre-delivered in the system. They are used for field mappings to
ERP HCM fields. The delivered metadata corresponds to a standard Best Practices Employee Central instance
metadata and are delivered as part of the table ECPAO_FLD. They can be viewed by navigating to the following
path in IMG and specifying the EC Instance ID: Personnel Management Integration with SuccessFactors
Employee Central Business Integration Builder Basic Settings Import Metadata from Employee Central
Transport Imported Metadata and Check Metadata for File-Based Data Transfer .

 Note

Picklists from the Best Practices Employee Central system are not pre-imported as part of activation.

Ensure that the picklists have been migrated to MDF Picklists in the Employee Central instance. In
Constants for Integration with SuccessFactors [page 12], the constant value is set for using MDF picklists.

6.1.1.5 Import Picklists from Employee Central to SAP ERP

HCM system

Picklist option IDs can change from one SuccessFactors EC instance to another. Hence, it is required to import
picklists from the Employee Central instance. Prior to import, confirm that the picklists in Employee Central
have been migrated to MDF objects. This has been described in detail as part of the Getting Started guide and
should be already completed.

Migrating Data from ERP HCM to Employee Central: Configuration Guide

Configuration Steps PUBLIC 13
Procedure

1. Log on to the SAP SuccessFactors Employee Central instance.

2. Download the picklists from the EC instance:
• Go to Admin Center.
• Type Import and Export Data in the tool search box and select the feature/tool from the list.
• From the Select the action to perform dropdown, select Export Data.
• From the Select Generic Object dropdown, select Picklist.
• From the Include Dependencies dropdown, select Yes to include the dependencies.
• From Select all data records dropdown, select Yes to export all picklists.
• Choose Export.
• Type Monitor Job in the tool search box and select the feature/tool from the list.
• Download the Download Status zip file and extract the picklist csv.
3. Logon to the SAP ERP HCM system.
• Open program ECPAO_PICKLIST_WRITER in SA38 - ABAP Program Execution.
• On the selection screen, enter the following information:
• EC Instance: Enter SBP_MODEL_US if using SAP-delivered EC instance id for configuration.
• EC Picklist file: Choose the Picklist-Values.csv file downloaded from Employee Central.
• EC Locale: en_US.
• Choose Update Picklist.
• Optional, run in Test Mode.
• Deselect the Test Run checkbox and execute the program.

The picklist values are uploaded into the following tables:

ECPAO_PIKLST_ENT Picklists imported from Employee Central

ECPAO_PIKLST_VAL Picklist Values Imported from Employee Central

 Note

Picklists should be migrated to MDF objects.

If using a different EC instance ID other than SBP_MODEL_US, the other related configurations will have to
be copied over to the new instance.

6.1.1.6 Define Value Mapping Entities

Value mapping entries and value mapping details are delivered as part of the Best Practices content. To
view them, and modify if needed, execute transaction SPRO and choose SAP Reference IMG for the SAP
Implementation Guide. Navigate to Personnel Management Integration with SuccessFactors Employee
Central Business Integration Builder Basic Settings Define Value Mapping .

Migrating Data from ERP HCM to Employee Central: Configuration Guide

14 PUBLIC Configuration Steps
6.1.1.7 Change Picklist IDs in Value Mapping Entities

Best Practices Content associates a dummy picklist ID to some pre-delivered Value Mapping Entities. You
need to replace it with the correct Picklist IDs after you import picklists as described in Import Picklists from
Employee Central to SAP ERP HCM system [page 13].

Procedure

1. Log on to the ERP HCM system. Navigate to Personnel Management Integration with SuccessFactors
Employee Central Business Integration Builder Basic Settings Define Value Mapping
2. To change the EC Picklist ID associated to value mapping entities, navigate to Define Value Mapping
Entities.
3. Provide SBP_MODEL_US as the EC instance when prompted. The value mappings that have been shipped
as part of the SAP Best Practices content is displayed.
4. Switch to Change mode if you are in Display mode.
5. Find the EC Picklist IDs that have value 1 for Dummy Picklist IDs.
6. Replace each of them with the appropriate Picklist IDs by using the search help on the EC Picklist ID field.
The corresponding picklist fields are indicated below. Depending on any changes made to the standard
SAP Best Practices configuration, these may need to be adapted.

Value Mapping Entity Picklist Name

ASSIGNMENT_TYPE_WS global_assignment_type

CHALLENGED_WS typeOfChallenge

CHALLENGE_GROUP challengeGroup

CHALLENGE_GROUP_DEU challengeGroup_DEU

Migrating Data from ERP HCM to Employee Central: Configuration Guide

Configuration Steps PUBLIC 15
 Value Mapping Entity Picklist Name

COMMITMENT_INDICATOR commitmentIndicator

CONTINUED_PAY_MEASURE periodIndicator

CONTRACT_ID Contract_ID

CONTRACT_TYPE_WS contractType

COUNTRY_CODE_PHONE SFCC_PhoneCountryCode

COUNTRY_CODE_PHONE_ITA SFCC_PhoneCountryCode

COUNTY_GBR COUNTY_GBR

DEGREEOFCHALLENGE_DEP_ESP DEGREEOFCHALLENGE_ESP

DEGREEOFCHALLENGE_ESP DEGREEOFCHALLENGE_ESP

DEGREEOFCHALLENGE_ESP_REP DEGREEOFCHALLENGE_ESP

DEPARTMENT_FRA DEPARTMENT_FRA

DOCUMENT_TYPE_BRA permitdoctype

EDUCATION_LEVEL_BRA EDUCATIONLEVEL_BRA

EMAIL_TYPE ecEmailType

EMPLOYEE_CLASS_WS EMPLOYEECLASS

EMPLOYEE_CLASS_WS_GLOBAL EMPLOYEECLASS

EMPLOYMENT_RELATIONSHIP employmentRelationship

EMPLOYMENT_TYPE_WS employmentType

EMPLOYMENT_TYPE_WS_GLOBAL employmentType

ETHNIC_GROUP_USA ETHNICGROUP_USA

ETHNIC_GROUP_GBR ETHNICGROUP_GBR

EVENT_WS event

GENDER_DEU Gender Germany

GRADE_BRA GRADE_BRA

HARMFUL_AGENT_EXP harmfulAgentExposureCode

INTERNSHIP_LEVEL_BRA InternshipLevel_BRA

INTERNSHIP_SCHOOL_BRA InternshipSchool_BRA

ISOCOUNTRYCODE ISOCountryList

ISSUINGAUTHORITY_DEU IssuingAuthority_DEU

LANGUAGE_CODE_WS language

Migrating Data from ERP HCM to Employee Central: Configuration Guide

16 PUBLIC Configuration Steps
 Value Mapping Entity Picklist Name

MANDATORY_INTERNSHIP_BRA yesNo

MARITAL_STATUS_WS ecMaritalStatus

MILITARYSTATUS_GBR MILITARYSTATUS_GBR

MINIMUMFAMILYTAXBASIS_ESP MINIMUMFAMILYTAXBASIS_ESP

NAME_PREFIX nameprefix

PERMITDOCTYPE permitdoctype

PHONE_TYPE ecPhoneType

PHONE_TYPE_ITA ecPhoneType

PROVINCE_ESP PROVINCE_ESP

PROVINCE_ITA PROVINCE_ITA

RACE_BRA RACE_BRA

RELATION_TYPE_WS personRelationshipType

RELIGION_BRA RELIGION_BRA

RELIGION_IND RELIGION_IND

SALUTATION salutation

SALUTATION_DEP salutation

SPECIFICATION_BRA SPECIFICATION_BRA

STATE_BRA STATE_BRA

STATE_IND STATE_IND

STATE_WS STATE_USA

STREETTYPE_ESP STRTYPE_ESP

SUFFIX_WS namesuffix

TITLE_WS title

TYPE_OF_CHALLENGE typeOfChallenge

WORKER_CATEGORY workerCategory

YES_NO yesNo

Migrating Data from ERP HCM to Employee Central: Configuration Guide

Configuration Steps PUBLIC 17
6.1.1.8 Organizational Data Integration

Procedure

Execute transaction SPRO and choose SAP Reference IMG for the SAP Implementation Guide. Navigate to
Personnel Management Integration with SuccessFactors Employee Central Business Integration Builder
Organizational Data Integration .

The following configurations are required and are pre-delivered as part of the SAP Best Practices activation
report.

6.1.1.8.1 Map Languages from Employee Central and ERP

Procedure

Execute transaction SPRO and choose SAP Reference IMG for the SAP Implementation Guide. Navigate to
Personnel Management Integration with SuccessFactors Employee Central Business Integration Builder
Organizational Data Integration Map Languages from Employee Central and ERP .

Migrating Data from ERP HCM to Employee Central: Configuration Guide

18 PUBLIC Configuration Steps
The following mapping entry is maintained in this IMG activity:

6.1.1.8.2 Define Org Data Settings for Employee Central

Instance

Procedure

Execute transaction SPRO and choose SAP Reference IMG for the SAP Implementation Guide. Navigate to
Personnel Management Integration with SuccessFactors Employee Central Business Integration Builder
Organizational Data Integration Define Organizational Data Settings for Employee Central Instance .

The following Organizational Data setting configuration is pre-delivered as part of the SAP Best Practices
content:

6.1.1.8.3 Define Field Mappings for Organizational Data

(ERP_EC)

Procedure

Navigate to Personnel Management Integration with SuccessFactors Employee Central Business

Integration Builder Organizational Data Integration Define Field Mappings for Organizational Data .

Migrating Data from ERP HCM to Employee Central: Configuration Guide

Configuration Steps PUBLIC 19
Field mappings between ERP fields and Best Practices Employee Central fields for organizational data objects
are defined in this configuration activity. SAP Best Practices delivers the following as part of the content.

Transformation template groups:

Transformation Template Group Description

SBP_OM_ERP_EC SAP BP OM ERP to EC (via Web Services)

SBP_OM_ERP_EC_REL SAP BP OM ERP to EC – Relationships (Web Srv)

The following transformation templates are active by default in each of the template group:

Transformation Template Description

ERP_DEPARTMENT Department Template

ERP_JOBCODE Job Classification Template

ERP_POSITION Position Template

All organizational objects (Object type = O) will be extracted as Departments to the Employee Central system
by default.

If further segregation is desired for Divisions and Business Units, then the following two templates need
to be activated. Additionally, you would need to ensure that every organizational object is only extracted as
part of one template – i.e. as a division, business unit or a department – and should not appear in multiple
categories. This can be done either by selecting the appropriate objects during the execution of the migration
report (ECPAO_OM_OBJECT_EXTRACTION) or by implementing the logic in a BAdI (BAdI Validity Periods for
Data Replication to EC).

Transformation Template Description

ERP_DIVISION Division Template

ERP_BUSINESS_UNIT Business Unit Template

The standard delivered field mappings are also provided as an Excel workbook along with the Best Practices
package. If you wish to change the default templates or mappings, you can copy them into a separate template
group and modify as needed.

Migrating Data from ERP HCM to Employee Central: Configuration Guide

20 PUBLIC Configuration Steps
6.1.1.9 Employee Data Integration

Procedure

Execute transaction SPRO and choose SAP Reference IMG for the SAP Implementation Guide. Navigate to
Personnel Management Integration with SuccessFactors Employee Central Business Integration Builder
Employee Data Integration .

This section describes the configurations that are required and pre-delivered as part of the SAP Best Practices
content.

6.1.1.9.1 Define Employee Data Settings for Employee

Central Instance

Procedure

Execute transaction SPRO and choose SAP Reference IMG for the SAP Implementation Guide. Navigate to
Personnel Management Integration with SuccessFactors Employee Central Business Integration Builder
Employee Data Integration Define Employee Data Settings for Employee Central Instance .

Migrating Data from ERP HCM to Employee Central: Configuration Guide

Configuration Steps PUBLIC 21
The following configuration is delivered as part of the Best Practices content.

6.1.1.9.2 Define Relationship Types for Managers and

Employee-Related Org. Mgmt. Data

Procedure

Execute transaction SPRO and choose SAP Reference IMG for the SAP Implementation Guide. Navigate to
Personnel Management Integration with SuccessFactors Employee Central Business Integration Builder
Employee Data Integration Define Relationship Types for Managers and Employee-Related Org. Mgmt.
Data .

The following configuration is delivered as part of the Best Practices content.

 Note

SAP Best Practices uses the standard evaluation path MANAGER. You can change this if required.

6.1.1.9.3 Define Field Mappings for Employee Data

(ERP_EC)

Procedure

Execute transaction SPRO and choose SAP Reference IMG for the SAP Implementation Guide. Navigate to
Personnel Management Integration with SuccessFactors Employee Central Business Integration Builder
Employee Data Integration Define Field Mappings for Employee Data .

Migrating Data from ERP HCM to Employee Central: Configuration Guide

22 PUBLIC Configuration Steps
Field mappings between ERP fields and Best Practices Employee Central fields for employee master data are
defined in this configuration activity.

The following Transformation template groups are delivered as part of the SAP Best Practices content.

Transformation Template Group Description

SBP_EE_ERP_EC SAP Best Practices for Employee Integration

(EC-ERP HCM)

 Note

For troubleshooting, it is recommended to deactivate the templates and test one-by-one until the problem
template is identified and fixed. ERP_WS_18_GB template is delivered as inactive by default as most of the
customers in the UK do not use IT0004 (Challenge). Activate if it is required.

6.1.1.10 Business Add-ins

The Best Practice content uses BAdIs in cases where the logic for deriving the EC fields is complex or cannot be
achieved through infotype mapping.

Most of the BAdI logic delivered derives the values for EC fields from the ERP data. In these cases, the BAdI is
used in lieu of infotype mapping to map the ERP data to the EC fields.

The following BAdis have been used:

The BAdI EX_ECPAO_EMP_DATA_EXTRACT_OUT of enhancement spot

ES_ECPAO_EMP_DATA_EXTRACT_OUT needs to be implemented. To implement this, follow the steps below:

Procedure

1. Navigate to Personnel Management Integration with SuccessFactors Employee Central Business

Integration Builder Business Add-Ins (BAdIs) Data Transfer to Employee Central BAdI: Mapping of
EC and ERP Data for Data Replication to Employee Central .

This takes you to the BAdI implementation screen. Use the class CL_SBP_ECPAO_BADI_OUTBOUND as
the implementation class for the BAdI.
2. BAdI logic to modify the mapping results for EC fields from the ERP Data

Migrating Data from ERP HCM to Employee Central: Configuration Guide

Configuration Steps PUBLIC 23
 In a few cases, even though the derivation of the EC field has been done using infotype mapping,
subsequent modification of the data is necessary.
The BAdI EX_ECPAO_ERP_EMP_DATA_MODIFY of enhancement spot
ES_ECPAO_EMP_DATA_EXTRACT_OUT needs to be implemented.

 Note

It is recommended to copy the implementation class and then use the copied class to define the BAdI
implementation.

Procedure

1. Navigate to Personnel Management Integration with SuccessFactors Employee Central Business

Integration Builder Business Add-Ins (BAdIs) Data Transfer to Employee Central BAdI: Change of
Mapping Result for Data Replication to EC .

This takes you to the BAdI implementation screen. Use the class CL_SBP_ECPAO_ERP_EMP_DATA_MOD
as the implementation class for the BAdi.

 Note

It is recommended to copy the implementation class and then use the copied class to define the BAdI
implementation.

6.1.1.10.1 Organizational Data BAdI-Based Mapping

The following table lists the fields and the corresponding templates that have been mapped using BAdIs for
organizational data.

Migrating Data from ERP HCM to Employee Central: Configuration Guide

24 PUBLIC Configuration Steps
 Template EC Field Description of the BAdI

ERP_DEPARTMENT headOfUnit Get the holder of the leading position associated with
the department.

ERP_DEPARTMENT costCenter Get cost center of the Department that is directly as­
signed or inherited and format it appropriately for the
Employee Central field.

ERP_DIVISION headOfUnit Get the holder of the leading position associated with
the division.

ERP_POSITION Company Get the company code for the position that is directly
assigned or inherited.

ERP_POSITION Location Get the location for the position in the following

priority order – Directly on the Position entity

Inheritance From holder of the position in Personnel

Administration .

ERP_POSITION costCenter Get the cost center of the object and format it appro­
priately for Employee Central field.

ERP_POSITION standardHours Get the standard working hours.

ERP_POSITION targetFTE Derive target FTE value for Position.

ERP_POSITION cust_Sub_Location Get the sub-location for the position in the following

priority order – Directly on the Position entity

Inheritance From holder of the position in Personnel

Administration .

ERP_POSITION employeeClass Employee Class in EC Best Practices is maintained

at the country level. This BADI enables lookup of
the country specific mapping of employee class main­
tained in country specific value mapping entity EM­
PLOYEE_CLASS_WS. The country key is determined
by looking up the company code in the Position Object.

ERP_POSITION cust_employmentType Employment Type in EC Best Practices is maintained

at the country level. This BADI enables lookup of the
country specific mapping of employment type main­
tained in country specific value mapping entity EM­
PLOYMENT_TYPE_WS. The country key is determined
by looking up the company code in the Position Object.

Migrating Data from ERP HCM to Employee Central: Configuration Guide

Configuration Steps PUBLIC 25
6.1.1.10.2 Employee Data Fields with BAdI Logic

The following table lists the fields and the corresponding templates that have been mapped using BAdIs for
employee master data.

Template EC Field Description of the BAdI

ERP_WS_17 nationalID Formatting of national ID to NNN-NN-NNNN format

for USA. The formatting is done in the Change of Map­
ping Result for Data Replication to EC BAdI

ERP_WS_17_DEP nationalID Formatting of national ID to NNN-NN-NNNN format

for USA. The formatting is done in the Change of Map­
ping Result for Data Replication to EC BAdI

ERP_WS_18_USA genericNumber1(Veteran) Get the specified status for Veteran in Global Info USA
Template

ERP_WS_18_USA genericNumber2(Challenge Get the specified status for Veteran in Global Info USA
d Veteran) Template

ERP_WS_18_USA genericNumber3(Veterans Get the specified status for Veteran in Global Info USA
(who served on active Template
duty in war or camp)

ERP_WS_18_USA genericNumber4(Armed Get the specified status for Veteran in Global Info USA
Forces Medal Veteran) Template

ERP_WS_18_USA genericNumber5(Recently Get the specified status for Veteran in Global Info USA
Separated Veteran) Template

ERP_WS_18_USA genericNumber6(Special Get the specified status for Veteran in Global Info USA
Disabled Veteran) Template

ERP_WS_18_USA genericNumber7(Vietnam Get the specified status for Veteran in Global Info USA
Era Veteran) Template

ERP_WS_18_USA genericString13(Disclose Get the specified status for Veteran in Global Info USA
d Veteran Category) Template

ERP_WS_18_USA genericString6(Challenge Get the specified status for Veteran in Global Info USA
d) Template

ERP_WS_4 localJobTitle Get Job Title in the Job Info Template

ERP_WS_4 probationPeriodEndDate Get the probation end date from IT0016

ERP_WS_8_1 to ERP_WS_8_4 isPrimary Logic to fill isPrimary for various phone types

Migrating Data from ERP HCM to Employee Central: Configuration Guide

26 PUBLIC Configuration Steps
 Template EC Field Description of the BAdI

ERP_WS_18_ES_DEP genericString5 (Minimum Handle Minimum Family Tax Basis Picklist from
Family Tax Basis) ERMNR(1) IT0021

ERP_WS_18_ES_DEP genericString6 (Degree Handle Degree of Challenge ERMNR+1(3) (IT0021)

of Challenge)

6.1.1.10.3 Foundation Objects BAdIs

SAP Best Practice content delivers the following implementation classes to be used for Foundation Objects.
This is in addition to the Legal Entity and Pay Component Group that are delivered in the standard product.

CL_SBP_ECPAO_FOBJ_LOCATION Location Foundation Object BAdI

CL_SBP_ECPAO_FOBJ_PAYCOMP Pay Component Foundation Object BAdI

CL_SBP_ECPAO_FOBJ_PAYGROUP Pay Group Foundation Object BAdI

CL_SBP_ECPAO_FOBJ_PAYSCALEAREA Pay Scale Area Foundation Object BAdI

CL_SBP_ECPAO_FOBJ_PAYSCALEGRP Pay Scale Group Foundation Object BAdI

CL_SBP_ECPAO_FOBJ_PAYSCALETYPE Pay Scale Type Foundation Object BAdI

CL_SBP_ECPAO_FOBJ_SUBLOCATION Sub Location Foundation Object BAdI

For each custom Foundation Object, a BAdI implementation for the BAdI definition
EX_ECPAO_MAP_FOBJ_TRANS_TO_EC is to be defined. Each such BAdI implementation has a filter value
identified by the code used in Define Additional Foundation Objects activity.

 Note

It is recommended to copy the sample implementation classes before defining BAdI implementations. You
need to de-activate any existing implementations before creating new ones.

6.2 Configuration Steps in Employee Central System

6.2.1 Creating Foundation Objects and MDFs for Migration

The default implementation of the Best Practices solution results in all Organizational Units in ERP HCM
system to be migrated as Departments in Employee Central. The migrated positions are migrated with

Migrating Data from ERP HCM to Employee Central: Configuration Guide

Configuration Steps PUBLIC 27
Departments mapped from ERP. Business Units and Divisions are defaulted to a dummy Migration Business
Unit and Division. For this purpose, a dummy Business Unit and Division needs to be created in Employee
Central.

6.2.1.1 Create Dummy Business Unit for Migration

Procedure

1. Log on to the Employee Central Instance.

2. Go to Admin Center.
3. Type Manage Data in the tool search box and select the feature/tool from the list.
4. In the drop-down for Create New, choose Business Unit.
5. Enter the following information:
• Effective as of: <Date of migration>
• Code: DUMMY_BUSINESS_UNIT
• Name: Dummy Migration BU
• Status: Active
6. Choose Save to save the Business Unit.

6.2.1.2 Create Dummy Division for Migration

Procedure

1. Log on to the Employee Central Instance.

2. Go to Admin Center.
3. Type Manage Data in the tool search box and select the feature/tool from the list.
4. In the drop-down for Create New, choose Division.
5. Enter the following information
• Effective as of: <Date of migration>
• Code: DUMMY_DIVISION
• Name: Dummy Migration Division
• Status: Active
• Business Unit: DUMMY_BUSINESS_UNIT
6. Choose Save to save the Division.

Migrating Data from ERP HCM to Employee Central: Configuration Guide

28 PUBLIC Configuration Steps
6.2.1.3 Work Schedules

Prerequisite steps in the SAP SuccessFactors Employee Central system for the Visibility of Work Schedule Day
Model and Work Schedule:

• Go to Admin Center.
• Type Configure Object Definitions in the tool search box and select the feature/tool from the list.
• On the Configure Object Definitions screen in the Search field enter Object Definition and in the second
Search field enter Work Schedule Day Model.
• Choose Take Action Make Correction .
• In the Fields column choose the Details link for field mdfSystemStatus.
• On the Details window set the field Visibility to editable.
• Choose Done.
• Choose Save.
• Repeat the same for object Work Schedule.

6.2.1.4 Event Reasons

Procedure

1. Log on to the Employee Central Instance.

2. Go to Admin Center.
3. Type Manage Organization, Pay and Job Structures in the tool search box and select the feature/tool from
the list.
4. In the dropdown for Create New, choose Event Reason.
5. Enter the following information:

Migrating Data from ERP HCM to Employee Central: Configuration Guide

Configuration Steps PUBLIC 29
6. Choose Save to save the Event Reason.

6.2.1.5 Personal Sub Area (Sub Location) MDF

In SAP HCM we have two fields to represent a location: Personnel Area and Personnel Sub Area. But in
Employee Central, we have only one field location.

Having this kind of set up in ERP, the Location vs Personnel area and Subarea can be represented in EC as
follows:

1. The Personnel Area can be represented in EC as the Location foundation object. Attention is required not to
assign more than one legal entity to a Location object in EC, as this combination is not allowed in ERP.
2. The Personnel Subarea can be represented in EC via a custom MDF object. This object is to be associated
to the Location (wrapper) object.

Procedure

1. Log on to the Employee Central Instance.

2. Go to Admin Center.
3. Type Configure Object Definition in the tool search box and select the feature/tool from the list.
4. Under Create New option, select Object Definition.
5. Create the two fields as shown below:

6. Under the Associations section add the location wrapper as shown below:

7. Set the field API Visibility to Editable.

8. Choose Save to save the object definition.

Migrating Data from ERP HCM to Employee Central: Configuration Guide

30 PUBLIC Configuration Steps
6.2.1.6 Personal Sub Area (Sub Location) in Job
Information

Procedure

1. Log on to the Employee Central Instance.

2. Go to Admin Center.
3. Type Manage Business Configuration in the tool search box and select the feature/tool from the list.
4. Under jobInfo element, add the field SubLocation as shown below.

5. Choose Details and add the info below:

6. Add the field criteria under Details as shown below:

Migrating Data from ERP HCM to Employee Central: Configuration Guide

Configuration Steps PUBLIC 31
7. Choose Save to save the job info element in Business Configuration UI.
8. Ensure you also perform an OData metadata refresh from OData API Metadata Refresh And Export in
Admin Center.

6.2.1.7 Custom Field to Store Sequence Number of Child

for Dependents

In countries like Spain, it is required to migrate the sequence of child in dependents for reporting purposes.

Procedure

1. Log on to the Employee Central instance.

2. Go to Admin Center.
3. Type Manage Business Configuration in the tool search box and select the feature/tool from the list.
4. Select hris element personRelationshipInfo.
5. Add the custom field as shown below:

6. Choose Save.
7. Ensure you also perform an OData metadata refresh from OData API Metadata Refresh And Export in
Admin Center.

6.2.1.8 Custom Field to Store Contract ID (Only for Spain)

Procedure

1. Logon to the Employee Central instance.

2. Go to Admin Center.
3. Type Manage Business Configuration in the tool search box and select the feature/tool from the list.
4. Navigate to hris element jobInfo_ESP.
5. Add the custom field as shown below.

6. Enter the picklist in Details as shown.

Migrating Data from ERP HCM to Employee Central: Configuration Guide

32 PUBLIC Configuration Steps
 7. If you have not created picklist entries for Contract_ID already, create them using the sample below from
Picklist Center.

Migrating Data from ERP HCM to Employee Central: Configuration Guide

Configuration Steps PUBLIC 33
8. Finally save all your entries.
9. Ensure you also perform an OData metadata refresh from OData API Metadata Refresh and Export in
Admin Center.

6.2.2 Extracting Employee Data with Additional Events

Before Earliest Transfer Date

The employee extraction report extracts the employee data from or after the earliest transfer date that you
have defined at the transformation template group. Through this additional events feature, the employee
extraction report migrates the records (Job Information and Personnel Information) before the earliest transfer
date with additional data along with the records after the earliest transfer date, where you have an option to
migrate a constant or an actual database value based on the validity period.

Prerequisites

Activate the switch (ERP to EC: Additional Event Records) for an additional event by putting the value X in the
view V_ECPAO_CONSTANT using the Constant Values Customizing activity.

Context

During the employee extraction report, the employee records are extracted based upon the earliest transfer
date that you have defined 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 first event reason.

During this process:

• Employee records before the earliest transfer date are not extracted, which leads to an incorrect hire date
in Employee Central (Employment information).
• Start date of the pseudo hire event reason is considered to be the actual hire date in the Employee Central
(Employment information) system.

From Best Practices, we are delivering the following sample configuration for you to use/enhance according to
your needs.

Go to the Define Additional Event Types Configuration 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.

Migrating Data from ERP HCM to Employee Central: Configuration Guide

34 PUBLIC Configuration Steps
Next, go to the Define Additional Event Data Configuration 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 field available in the Job information or the Personal information.

In our sample, we have created sample legal entities, cost center, Job Classification, Location (Personal Area) ,
Position, Work Schedule, and Sub Location (Personal Sub Area).

As these entities can differ from country to country, you can create your own entities (Foundation objects and
MDFs) in the Employee Central instance. After that, you can maintain relevant values in the customizing view as
shown above.

6.3 Adaptations

If you have customized the SAP Best Practices Employee Central instance with custom fields, then you will
need to make adaptations to the delivered SAP Best Practices content.

Migrating Data from ERP HCM to Employee Central: Configuration Guide

Configuration Steps PUBLIC 35
  Note

Ensure that SAP Best Practices for Employee Central have been applied as described in the Getting Started
Guide.

6.3.1 Updating Fields (Text in Employee Central but

Dropdown in ERP HCM)

There could be some cases where the standard delivered field in Employee Central is a plain text field but in
ERP HCM it is a dropdown for example : Corporation field which is used for China Localization.

For such fields you would need to create a custom picklist in employee central and attach it to the field
definition in corresponding succession data model. Once this is done, create a separate value mapping to map
values from this picklist in employee central with values in ERP HCM.

6.3.2 Updating Metadata

Procedure

1. Log on to the Employee Central Instance.

2. Go to Admin Center.
3. Type OData API Metadata Refresh and Export in the tool search box and select the feature/tool from the
list.
4. To make sure that the metadata is up to date, choose Refresh.
5. Choose Export for the Export Metadata to File option.
6. Store the metadata in XML format on your local disk.
7. Log on to the ERP HCM system. Execute transaction SPRO and choose SAP Reference IMG for the SAP
Implementation Guide. Navigate to Personnel Management Integration with SuccessFactors Employee
Central Business Integration Builder Basic Settings Import Metadata from Employee Central
Import Metadata for Web Service-Based Data Transfer from Employee Central .
8. Specify the Employee Central instance to which you would like to upload the metadata.
9. Specify the .xml file previously downloaded in the EC Metadata File.
10. Choose Update Metadata as the Action Type.
11. Optionally, carry out a test run by checking the Test Run checkbox.
12. Clear the Test Run checkbook and execute the program to update/insert metadata in the specified
Employee Central instance.
13. If you have added custom fields to the organizational data, navigate to Personnel Management
Integration with SuccessFactors Employee Central Business Integration Builder Organizational Data

Migrating Data from ERP HCM to Employee Central: Configuration Guide

36 PUBLIC Configuration Steps
 Integration Define Field Mappings for Organizational Data . Establish the appropriate mapping with ERP
HCM data for the custom fields here.
14. If you have added custom fields to the organizational data, navigate to Personnel Management
Integration with SuccessFactors Employee Central Business Integration Builder Organizational Data
Integration . Establish the appropriate mapping with ERP HCM data for the custom fields here.

6.3.3 Updating Picklist

Procedure

1. Go to Admin Center in the Employee Central Instance.

2. Type Import and Export Data in the tool search box and select the feature/tool from the list.
3. From the Select the action to perform drop-down, select Export Data.
4. From the Select Generic Object drop-down, select Picklist.
5. From the Include Dependencies drop-down, select Yes to include the dependencies.
6. From Select all data records drop-down, select Yes to export all picklists.
7. Choose Export.
8. Type Monitor Job in the tool search box and select the feature/tool from the list.
9. Download the Download Status zip file and extract the picklist csv.
10. Log on to the ERP HCM system. Execute transaction SPRO and choose SAP Reference IMG for the SAP
Implementation Guide. Navigate to Personnel Management Integration with SuccessFactors Employee
Central Business Integration Builder Basic Settings Define Value Mapping Import Picklists from
Employee Central .
11. Specify the EC instance to which you would like to upload the picklists.
12. Specify the picklist file previously downloaded in EC Picklist File.
13. Specify EC Locale as en_US.
14. Choose Update Picklist as the Action Type.
15. Optionally, carry out a test run by checking the Test Run checkbox.
16. Clear the Test Run checkbox and execute the program to update/insert picklist in the specified EC
instance.

Migrating Data from ERP HCM to Employee Central: Configuration Guide

Configuration Steps PUBLIC 37
6.3.4 Updating Value Mapping

Procedure

1. Log on to the ERP HCM system. Execute transaction SPRO and choose SAP Reference IMG for the SAP
Implementation Guide. Navigate to Personnel Management Integration with SuccessFactors Employee
Central Business Integration Builder Basic Settings Define Value Mapping
2. To change the value mapping entities, navigate to Define Value Mapping Entities
3. Provide SBP_MODEL_US as the Employee Central Instance when prompted. The value mappings that have
been shipped as part of the SAP Best Practices content is displayed.
4. Switch to Change mode if you are in Display mode. You can now modify the value mapping entities here.
5. To change the value mapping details, navigate to Define Value Mapping Details
6. Provide the Employee Central instance as SBP_MODEL_US and the Value Mapping Entity you wish to
modify.
7. Switch to Change mode if you are in Display mode. You can now modify the value mapping details here.

6.3.5 Updating Field Mappings for Organizational Data/

Employee Data

Procedure

1. If you wish to update field mappings for Organizational data, navigate to Personnel Management
Integration with SuccessFactors Employee Central Business Integration Builder Organizational Data
Integration Define Field Mappings for Organizational Data . When prompted, provide the SAP Best
Practices Employee Central instance. You can now modify the field mappings in the change view.
2. If you have custom fields added to organizational data, navigate to Personnel Management
Integration with SuccessFactors Employee Central Business Integration Builder Organizational Data
Integration Define Field Mappings for Employee Data . When prompted, provide the SAP Best Practices
EC instance ID. You can now modify the field mappings in the change view.

6.3.6 Updating Field Mappings for Italy (Province and

Comuni)

In general, for Italy, the EC Solution applies 2 cascading picklists, PROVINCE_ITA and Comuni.

Migrating Data from ERP HCM to Employee Central: Configuration Guide

38 PUBLIC Configuration Steps
REGION_OF_BIRTH: Values depend on Country of birth field value (Parent Field for Picklist PROVINCE_ITA)

PLACE_OF_BIRTH: Values depend on REGION_OF_BIRTH field value (Parent Field for Picklist Comuni)

The same kind of check is applied also to STATE (PROVINCE_ITA) and CITY (Comuni) fields of
EMP_ADDR_INFO_T.

Currently the fields region of birth, place of birth and city are not picklists in EC. If you wish to adapt this, follow
the steps below.

1. Update these fields as picklists in EC Data Model (SDM).

2. Import these picklists into the EC system.
3. Import these picklists into the ERP System and import the metadata for person Info and address entities.
(Refer to sections Updating Metadata [page 36] and Updating Picklist [page 37] for the procedure).
4. Create Value Mapping Entities for these fields and use picklist External Code mapping.
5. Provide the relevant values to map external codes from EC with Code values in ERP.
6. Repeat the same logic for Replication Templates.

The picklist file is provided in the Migration workbook (Italy Picklists Tab).

6.3.7 Cost Center Logic when Cost Center Being Replicated

is not Exactly 14 Characters

If the cost centers in the ERP HCM system do not follow the pattern of 14 characters – Controlling
Area(4 chars) + Cost Center(10 chars), then as a result of the migration of organizational objects
from ERP HCM, the cost center keys in Employee Central will be less than 10 characters. During
generic organizational replication from Employee Central to ERP HCM, any template that brings a cost
center entity will trigger an error Error when mapping Employee Central field cost Center, field value
XXXYYYYYYYYYY (SFIOM_PROCESSING224). This happens as the system is unable to determine the
controlling area and cost center from the Cost Center key from Employee Central.

Refer to the KBA 2706481 that describes workarounds to overcome this error.

6.3.8 Cost Center Mapping for Organizational Objects

The default cost center mapping for organizational objects is performed using a BAdI. This ensures that the
cost centers are picked up correctly even if the inheritance of account assignment feature is set on. The BAdI
delivers the latest cost center for the mapping of organizational objects. If there are multiple changes to the
cost center assignments and if it is required to bring all of them, it is necessary to adapt accordingly. If you
are not using the inheritance feature, then you can switch off BAdI mapping and use infotype mapping for cost
center field. Another alternative would be to modify the BAdI.

Migrating Data from ERP HCM to Employee Central: Configuration Guide

Configuration Steps PUBLIC 39
6.3.9 Copying Best Practices Templates

You might want to copy the Field mapping (Template Groups) provided by SAP Best Practices and then adapt
(instead of modifying the delivered templates directly). In this case, the following option is available:

6.3.9.1 Copy with New Employee Central Instance

The Best Practices delivered transformation template groups can be copied from the delivered
SBP_MODEL_US Employee Central instance ID to a new Employee Central instance ID. In order to perform
this, the following steps are needed:

1. Open ECPAO_COPY_CONFIGURATION program using transaction code ECPAO_COPY_CONFIG or via

transaction code SA38 - ABAP Program Execution.
2. Provide the source EC Instance ID – SBP_MODEL_US.
3. Choose each source transformation template group that you would like to copy.
4. Provide a destination EC Instance ID and a new transformation template group name.
5. Execute the program.

Further details for the copying functionality are available in the Program documentation.

After copying, follow the steps below to make adjustments in the new Instance ID and transformation template
groups.

1. Update Metadata: You can do this under IMG activity Basic Settings Import Metadata from Employee
Central . Choose the first activity under this path.
2. Import Picklists: You can do this under IMG activity Basic Settings Define Value Mapping Import
Picklists from Employee Central (You will need the Picklists CSV from EC).
3. Define Value Mapping Entities: The value mapping entities associated with SBP_MODEL_US are already
delivered. You may need to adjust these based on your new/updated picklists.
4. Define Value Mapping Details: The value mapping details for the reference above Value Mapping Entities
are pre-delivered. However, based on new Picklist values or new Value mapping Entities you may have to
adjust.
5. Refine the Template mappings: Check the different templates in detail and look out for any new ‘deleted’
EC fields or more fields that you may need to map.
6. Lastly, you may need to copy the BAdI implementation classes and adjust the code accordingly. Regarding
BAdIs, you can refer to the Business Add-ins [page 23].

Migrating Data from ERP HCM to Employee Central: Configuration Guide

40 PUBLIC Configuration Steps
Important Disclaimers and Legal Information

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

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

• The content of the linked-to site is not SAP documentation. You may not infer any product claims against SAP based on this information.

• SAP does not agree or disagree with the content on the linked-to site, nor does SAP warrant the availability and correctness. SAP shall not be liable for any
damages caused by the use of such content unless damages have been caused by SAP's gross negligence or willful misconduct.

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

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

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

Migrating Data from ERP HCM to Employee Central: Configuration Guide

Important Disclaimers and Legal Information PUBLIC 41
www.sap.com/contactsap

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

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

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

Some software products marketed by SAP SE and its distributors

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

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

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

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

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

additional trademark information and notices.

THE BEST RUN