SF ERP EC UPGRADE ECS4HCM en-US

PUBLIC
Document Version: 2H 2022 – 2023-06-16
Upgrading from PA_SE_IN to ECS4HCM for Data

Replication from Employee Central
© 2023 SAP SE or an SAP affiliate company. All rights reserved.
THE BEST RUN

Content
1 Introduction to the Upgrade from PA_SE_IN to ECS4HCM. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4

1.1 Target Group of This Document. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5
1.2 Benefits of Using BIB Based Employee Master Data and Organizational Assignment Replication
Solution. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .6
1.3 Maintenance Strategy for the SFSF EC INTEGRATION Add-On. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6
2 Upgrade from SFSF EC INTEGRATION (PA_SE_IN) on BIB to SFSF EC S4 INTEGRATION

(ECS4HCM). . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8
2.1 What's Different in the ECS4HCM Add-On Compared to the BIB-Based PA_SE_IN Add-On. . . . . . . . . . . . 8
SAP Cloud Integration Is Used as the Only Middleware. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10
Business Integration Builder Is Now Default. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10
Customizing Restructured Based on Replication Direction. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 11
Constants Removed from Table ECPAO_CONSTANTS. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 11
Switches Removed from T77S0 Table. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .12
Authorization Roles in SAP S∕4HANA Revised. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13
Replication Direction Is Required for Transformation Template Groups. . . . . . . . . . . . . . . . . . . . . . . 17
Initiating Full Load from Query Program for Replication of Employee Data. . . . . . . . . . . . . . . . . . . . . 18
New Staging Area for Employee Data. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 18
Purge Status Overview Option Is Now Standard for Purge Validation. . . . . . . . . . . . . . . . . . . . . . . . . 19
Staging Area for Organizational Assignment Replication No Longer Available. . . . . . . . . . . . . . . . . . 20
New Configurable Replication of Employee Organizational Assignments. . . . . . . . . . . . . . . . . . . . . . 20
Use of New Infotype Framework for Integration Between Organizational Management and
Personnel Administration (PA/PD Integration) Is Mandatory. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 21
Object-Specific Replication and Processing of Organizational Objects No Longer Available. . . . . . . . . 22
Full Transmission Start Date for Organizational Object Replication Defined in Transformation
Template Group. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .23
Full Load No Longer Performed Automatically When Full Transmission Start Date for
Organizational Object Replication Is Moved Into the Past. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 23
New Status Added and Replication Content Type Removed in the Data Replication Monitor. . . . . . . . 23
Use of New Point-to-Point Time Data Replication from Employee Central Is Mandatory. . . . . . . . . . . 24
2.2 Preparing the Upgrade. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 24
Stopping Data Replication from Employee Central . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 25
Processing Open Replication Requests. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 27
Checking Switch Settings Made in Table T77S0. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 28
Checking Usage of Data from Tables That Will Be Deleted. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 30
Retaining Settings Before Upgrade for Comparison After Upgrade. . . . . . . . . . . . . . . . . . . . . . . . . . 31
2.3 Upgrade Steps. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 32
2.4 Post-Upgrade Steps. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 32
Upgrading from PA_SE_IN to ECS4HCM for Data Replication from Employee Central
2 PUBLIC Content
Undeploying Obsolete Integration Flows. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 34
Checking and Adjusting Implicit Enhancements. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 35
Replicating Selected Employees from Employee Central and Performing Spot Checks. . . . . . . . . . . . 36
Deleting Constants That Are No Longer Required. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 37
Transferring Switch Settings Made in Table T77S0. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 38
Enabling Use of New Infotype Framework for Integration Between Organizational Management and
Personnel Administration (PA/PD Integration). . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 40
Checking and Adjusting Authorization Roles. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 41
Splitting Transformation Template Groups and Defining Replication Direction. . . . . . . . . . . . . . . . . . 44
Getting Started with the New Employee Staging Area. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 45
Disabling Background Jobs for Staging Area for Organizational Assignment Replication. . . . . . . . . . . 46
Getting Started with Configuring Organizational Assignment Replication in Customizing. . . . . . . . . . 47
Replacing Object-Specific with Generic Replication and Processing of Organizational Objects. . . . . . .49
Moving Full Transmission Start Date for Organizational Object Replication from Query Program to
Transformation Template Group. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 50
Removing Records with Replication Content Type Employee Organizational Assignment from the
Data Replication Monitor. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 51
Upgrading to Point-to-Point Time Data Replication. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 52
Converting the Dependent Mapping Data. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .54
3 Upgrade from SFSF EC INTEGRATION (PA_SE_IN) Non-BIB to SFSF EC S4 HCM INTEGRATION

(ECS4HCM). . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 55
3.1 Non-BIB Employee Master Data Compared to BIB Employee Master Data Replication. . . . . . . . . . . . . . . 55
Additional Features in Business Integration Builder (BIB). . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 56
What's Different in Non-BIB and BIB. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 58
How Infotypes are Handled in Non-BIB and BIB. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 62
3.2 Direct Move from SFSF EC INTEGRATION (PA_SE_IN) Non-BIB to SFSF EC S4 HCM INTEGRATION
(ECS4HCM). . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 65
Preparing the Upgrade. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 66
Upgrade Steps. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 69
Post-Upgrade Steps. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .70
3.3 Move from SFSF EC INTEGRATION (PA_SE_IN) Non-BIB via SFSF EC INTEGRATION (PA_SE_IN) on
BIB to SFSF EC S4 HCM INTEGRATION (ECS4HCM). . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 84
Preparing the Upgrade. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 84
Upgrade Steps. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 88
Post-Upgrade Steps. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .89
4 Change History. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 94
Content PUBLIC 3
1 Introduction to the Upgrade from PA_SE_IN
to ECS4HCM
This guide provides step-by-step instructions for upgrading from PA_SE_IN integration to ECS4HCM Business
Integration Builder (BIB) Integration.
You are currently using one of our Employee Central standard replication solutions based on the PA_SE_IN add-on
either the Employee Central to SAP ERP replication based on BIB or based on Non-BIB. This document provides
guidance on upgrading your current solution to the ECS4HCM add-on solution.
 Remember
We use the following naming convention in this document to refer to the integration add-ons:
Official Product Name Technical Product Name Software Component
SAP SuccessFactors Employee Central SFSF EC S4 HCM INTEGRATION ECS4HCM

integration with SAP Human Capital
Management for SAP S/4HANA
SAP SuccessFactors Employee Central SFSF EC INTEGRATION PA_SE_IN

integration to SAP Business Suite
Since the official product name is rather long, we use the technical product name instead for better readability.
Since the technical product names are similar, we also add the name of the software component to differentiate
between the add-ons. For reasons of brevity, we sometimes use only the name of the software component to
name the add-ons.
This guide provides information on different upgrade scenarios from PA_SE_IN add-on to ECS4HCM add-on:
• If you are using ERP or S/4HANA system with PA_SE_IN add-on Non-BIB integration and would like to migrate
to S/4HANA using ECS4HCM add-on
• If you are using ERP or S/4HANA system with PA_SE_IN add-on BIB integration and would like to migrate to
S/4HANA using ECS4HCM add-on
Here are the advantages when you upgrade to ECS4HCM add-on and configure BIB:
• One time implementation or configuration effort.
 Note
PA_SE_IN add-on Non-BIB integration framework’s objects will not be available after the upgrade since BIB is
mandatory in the ECS4HCM add-on.
Here are the advantages when you first migrate to PA_SE_IN add-on BIB and then migrate to S/4HANA using
ECS4HCM add-on:
• Most of the configurations except setting the BIB switch ON, can be done in the system when the PA_SE_IN
add-on Non-BIB integration replication is still ON. i.e., no need to stop the replication for performing BIB
configurations.
4 PUBLIC Introduction to the Upgrade from PA_SE_IN to ECS4HCM
• After the BIB configurations are performed in the PA_SE_IN system, the system can be upgraded to
ECS4HCM.
• If you want to refer to PA_SE_IN add-on Non-BIB integration configurations and code enhancements in BAdIs
of PA_SE_IN add-on Non-BIB integration framework, it is still available in the system.
 Note
• After the upgrade there would be some more post-upgrade configurations or activities that are required to
be carried out.
• We do not recommend you to perform any implicit enhancements to the code, as new ECS4HCM add-on
code might have been refactored.
• Some of the constants and configurations are not available in ECS4HCM. So configure only the BIB
configuration which are available in ECS4HCM.
• PA_SE_IN add-on Non-BIB integration tables logic is not available in ECS4HCM add-on hence earlier
configurations and old BAdIs cannot be referred in the system after the upgrade.
Target Group of This Document [page 5]

Take a look at the target groups this document is intended for.
Benefits of Using BIB Based Employee Master Data and Organizational Assignment Replication Solution [page
6]
Read about the benefits that you would be getting by using the BIB based employee master data and
organizational assignment replication solution.
Maintenance Strategy for the SFSF EC INTEGRATION Add-On [page 6]

Find out how the maintenance strategy for the SFSF EC INTEGRATION (PA_SE_IN) add-on makes an
upgrade to the SFSF EC S4 HCM INTEGRATION (ECS4HCM) add-on useful.
1.1 Target Group of This Document
Take a look at the target groups this document is intended for.
The following groups of people will benefit from reading this document:
• Implementation partners, consultants, and Product Support, for fast support of customers and prospective
customers
• Cloud operations
• SAP-certified administrators at customer site
Introduction to the Upgrade from PA_SE_IN to ECS4HCM PUBLIC 5
1.2 Benefits of Using BIB Based Employee Master Data and
Organizational Assignment Replication Solution
Read about the benefits that you would be getting by using the BIB based employee master data and organizational
assignment replication solution.
With the Business Integration Builder (BIB) we leverage our employee master data integration by offering a flexible
and easy to use integration configuration tool available in the S/4HANA system.
Let us give you a brief insight into how you benefit from our BIB based employee master data replication solution:
• Field and value mapping is simple and easily configured using standard customizing activity. Importing the
Employee Central meta data model from your Employee Central instance directly into your S/4HANA system
ensures getting the right Employee Central data needed for configuring the field and value mapping quick and
easy.
• Extensibility based on configuration rather than BAdI ABAP implementations for handling infotypes in the
replication processing.
• Support of country-specific mappings by easy and simple standard configuration.
• Support transporting configuration settings between SAP S/4HANA systems. For example, between a test
system and a productive system.
• Ability to choose and apply pre-delivered sample content consisting of pre-delivered standard field and value
mappings to most common S/4HANA Infotypes. This will reduce the time spent configuring the mapping.
• Ability to consider secondary S/4HANA infotypes through standard configuration.
• No unnecessary infotype record splits anymore at full transmission start date (FTSD). You can also move
your FTSD to keep the data transfer straight-forward and focused on HCM business processes in your SAP
S/4HANA system. Reduces data traffic by avoiding old historical data that are not needed anymore in your
HCM processes in your SAP S/4HANA system that have been already replicated.
• Gain from additional features available only with our BIB integration covering important use cases such as
move of hire date, replicate multiple status changing actions at the same day, and support replicating No
Shows. You do not need to invest in custom developments to cover such use cases, instead you can use
standard BIB features.
1.3 Maintenance Strategy for the SFSF EC INTEGRATION

Add-On
Find out how the maintenance strategy for the SFSF EC INTEGRATION (PA_SE_IN) add-on makes an upgrade to
the SFSF EC S4 HCM INTEGRATION (ECS4HCM) add-on useful.
To enable planning security and support a sufficient transition phase from SAP Business Suite 7 to SAP S/4HANA,
SAP provides mainstream maintenance for core applications of SAP Business Suite 7 software, including SAP ERP
6.0, until December 31, 2027. The mainstream maintenance of the SFSF EC INTEGRATION add-on therefore also
ends on December 31, 2027. An optional extended maintenance is offered for the SFSF EC INTEGRATION add-on
until December 31, 2030.
The SFSF EC INTEGRATION add-on will be released up to SAP S/4HANA 2023, but not for subsequent SAP
S/4HANA releases because mainstream maintenance of SAP S/4HANA 2023 ends on December 31, 2030. For any
6 PUBLIC Introduction to the Upgrade from PA_SE_IN to ECS4HCM
releases after SAP S/4HANA 2023, only the SFSF EC S4 HCM INTEGRATION is available for integration with SAP
SuccessFactors Employee Central.
To make the transition from the SFSF EC INTEGRATION add-on to the SFSF EC S4 HCM INTEGRATION add-on as
easy as possible, both add-ons are offered for both of the SAP S/4HANA releases 2022 and 2023. You can use both
these SAP S/4HANA releases to move from SFSF EC INTEGRATION to SFSF EC S4 HCM INTEGRATION.
For more information about the maintenance strategy for the SFSF EC INTEGRATION add-on, refer to SAP Note
3250816 .
Introduction to the Upgrade from PA_SE_IN to ECS4HCM PUBLIC 7
2 Upgrade from SFSF EC INTEGRATION
(PA_SE_IN) on BIB to SFSF EC S4
INTEGRATION (ECS4HCM)
How to upgrade if you are using the SAP ERP HCM or SAP S/4HANA system with the PA_SE_IN add-on based in
BIB and would like to migrate to SAP S/4HANA using the ECS4HCM add-on.
What's Different in the ECS4HCM Add-On Compared to the BIB-Based PA_SE_IN Add-On [page 8]
Get an overview of the changes we've made in the SFSF EC S4 HCM INTEGRATION (ECS4HCM) add-on
compared to the SFSF EC INTEGRATION (PA_SE_IN) add-on if you've used it with the Business Integration
Builder (BIB).
Preparing the Upgrade [page 24]

What you should do in the SFSF EC INTEGRATION (PA_SE_IN) BIB add-on before you start the upgrade to
SFSF EC S4 HCM INTEGRATION (ECS4HCM) add-on.
Upgrade Steps [page 32]

Perform the upgrade to the SFSF EC S4 HCM INTEGRATION (ECS4HCM) add-on.
Post-Upgrade Steps [page 32]

What you should do in your SAP S∕4HANA system after you've upgraded to the SFSF EC S4 HCM
INTEGRATION (ECS4HCM) add-on from SFSF EC INTEGRATION (PA_SE_IN) BIB.
2.1 What's Different in the ECS4HCM Add-On Compared to

the BIB-Based PA_SE_IN Add-On
Get an overview of the changes we've made in the SFSF EC S4 HCM INTEGRATION (ECS4HCM) add-on compared
to the SFSF EC INTEGRATION (PA_SE_IN) add-on if you've used it with the Business Integration Builder (BIB).
What's Changed in ECS4HCM More Info
SAP Cloud Integration is used as the only middleware for SAP Cloud Integration Is Used as the Only Middleware [page
replication of employee data (including organizational assign 10]
ments) and organizational objects from Employee Central.
Use of the Business Integration Builder (BIB) is mandatory. Business Integration Builder Is Now Default [page 10]
The Customizing has been structured more clearly based on Customizing Restructured Based on Replication Direction
the replication direction. [page 11]
We deleted some constants because they were either used for Constants Removed from Table ECPAO_CONSTANTS [page
the non-BIB integration version or the function activated with 11]
them is now implemented differently.
We removed some switches from the T77S0 table because Switches Removed from T77S0 Table [page 12]
they have been converted to constants in table ECPAO_CON
STANTS or their functionality is no longer needed.
Upgrade from SFSF EC INTEGRATION (PA_SE_IN) on BIB to SFSF EC S4 INTEGRATION
8 PUBLIC (ECS4HCM)
What's Changed in ECS4HCM More Info
We've reworked our template roles so that you can clearly sep Authorization Roles in SAP S∕4HANA Revised [page 13]
arate the replication of data from Employee Central and the
processing of the data in SAP S∕4HANA.
We recommend that you use separate transformation tem Replication Direction Is Required for Transformation Template
plate groups for the replication from SAP S∕4HANA to Em Groups [page 17]
ployee Central and from Employee Central to SAP S∕4HANA.
You can initiate a full load directly from the selection screen Initiating Full Load from Query Program for Replication of Em
of the Create and Execute Employee Master Data and Org. ployee Data [page 18]
Assignment Query (ECPAO_EE_ORG_REPL_QUERY) program in
the ECS4HCM add-on.
We introduced a staging area for employee data (including New Staging Area for Employee Data [page 18]
employee organizational assignments) to decouple replication
of the employee data from processing of the data in the SAP
S∕4HANA system.
Using the purge status overview is now the standard when data Purge Status Overview Option Is Now Standard for Purge Vali
replication to the SAP S∕4HANA system validates and reacts to dation [page 19]
a purge of employee data in Employee Central.
We've removed the staging area for organizational assign Staging Area for Organizational Assignment Replication No
ments replicated from Employee Central because organiza Longer Available [page 20]
tional assignment replication is now part of employee data
replication.
You can configure replication of organizational assignments New Configurable Replication of Employee Organizational As
from Employee Central as part of the Business Integration signments [page 20]
Builder.
Using the new infotype framework in PA/PD integration for Use of New Infotype Framework for Integration Between
organizational data that was replicated from Employee Central Organizational Management and Personnel Administration
is mandatory. (PA/PD Integration) Is Mandatory [page 21]
The ECS4HCM add-on uses the generic replication of organiza Object-Specific Replication and Processing of Organizational
tional objects with generic processing only. Objects No Longer Available [page 22]
You now define the full transmission start date (FTSD) for the Full Transmission Start Date for Organizational Object Replica
replication of organizational objects from Employee Central in tion Defined in Transformation Template Group [page 23]
the transformation template group.
The query program no longer automatically performs a full Full Load No Longer Performed Automatically When Full Trans
data load from Employee Central if you move the FTSD into the mission Start Date for Organizational Object Replication Is
past after you've already replicated organizational objects. Moved Into the Past [page 23]
We added a new status and removed the replication content New Status Added and Replication Content Type Removed in
type for organizational assignments to enable the Employee the Data Replication Monitor [page 23]
Central Data Replication Monitor for use of the new staging
area for employee data in SAP S∕4HANA.
Point-to-point (PTP) time data replication is mandatory if you Use of New Point-to-Point Time Data Replication from Em
want to replicate employee time data from Employee Central. ployee Central Is Mandatory [page 24]
(ECS4HCM) PUBLIC 9
2.1.1 SAP Cloud Integration Is Used as the Only Middleware
The SFSF EC S4 HCM INTEGRATION (ECS4HCM) add-on uses SAP Cloud Integration as the middleware for
replication of employee data (including organizational assignments) and organizational objects from Employee
Central.
In the SFSF EC INTEGRATION (PA_SE_IN) add-on, Boomi AtomSphere was supported for some previous
integration versions that were still in use. Boomi is now no longer supported.
The SFSF EC S4 HCM INTEGRATION (ECS4HCM) add-on uses the following integration packages and integration
flows for data replication from Employee Central.
Integration Package Integration Flows
SAP SuccessFactors Employee Central Integration with SAP Replicate Employee Master Data and Org. Assignments from
ERP or SAP S/4HANA: Employee and Organizational Data
SAP SuccessFactors Employee Central to SAP ERP or SAP
S4HANA
Replicate Organizational Objects from SAP SuccessFactors

Employee Central to SAP ERP or SAP S4HANA
SAP ERP or SAP S/4HANA Integration with SAP Send Confirmations from SAP ERP or SAP S4HANA to SAP
SuccessFactors Employee Central: Confirmation v2 SuccessFactors Employee Central
SAP SuccessFactors Employee Central Integration with SAP Push Employee Master Data from SAP SuccessFactors
ERP or SAP S/4HANA: Push Notification Employee Central to SAP ERP or SAP S4HANA
Related Information
Undeploying Obsolete Integration Flows [page 34]
2.1.2 Business Integration Builder Is Now Default
Use of the Business Integration Builder (BIB) is mandatory in the SFSF EC S4 HCM INTEGRATION (ECS4HCM)
add-on.
The non-BIB configuration options are no longer available. The activities that were available in Customizing for
Personnel Management under Integration with SuccessFactors Employee Central Other Integration Settings
Replicating Data from Employee Central to SAP ERP are no longer used with a few exceptions.
The activities that are also relevant in the new add-on have been transferred to Customizing for the Business
Integration Builder:
• Assign Cost Center Keys (customizing view PAOCFEC_KMAPCOSC)

• Restrict Employee Master Data Replication to Certain Countries (customizing view PAOCFEC_COUNTRY)
• BAdI: Enhancements for Adapting Employee Organizational Assignment (BAdI definition
EX_SFIOM_ADAPT_EE_ORG_ASSGNMNT)
10 PUBLIC (ECS4HCM)
• BAdI: Enhancements for Adapting Employee Organizational Assignment Request (BAdI definition
EX_SFIOM_ADAPT_EE_ORG_ASS_REQ)
2.1.3 Customizing Restructured Based on Replication Direction
The Customizing has been structured more clearly based on the replication direction.
The Customizing structure in the SFSF EC S4 HCM INTEGRATION (ECS4HCM) add-on consists of the following
sections:
• Prerequisites
Settings that you must make independently of the replication direction and the type of replication data.
• Data Migration and Replication to Employee Central
• Basic Setting
• Employee Data
• Organizational Data
• Foundation Object Data
• Business Add-Ins
• Data Replication from Employee Central
• Basic Setting
• Employee Data
Settings for replication of employee master data and employee organizational assignments
• Organizational Objects
• Business Add-Ins
• Additional Tools
Tools for comparison and transfer of configurations
Many settings are the same as in the SFSF EC INTEGRATION (PA_SE_IN) add-on. But new customizing activities
have also been added, for example, for replication of foundation objects to Employee Central or for configurable
replication of organizational assignments from Employee Central.
Individual customizing activities can appear more than once in the structure if they belong to several sections. But
the underlying customizing views are the same. If you make entries in one place in the customizing activity and call
the same customizing activity elsewhere, you see the entries that you made previously.
2.1.4 Constants Removed from Table ECPAO_CONSTANTS
We deleted some constants because they were either used for the non-BIB integration version or the function
activated with them is implemented differently in the SFSF EC S4 HCM INTEGRATION (ECS4HCM) add-on.
The following constants are obsolete and have been removed from the Constants for Integration with
SuccessFactors (ECPAO_CONSTANTS) table in the SFSF EC S4 HCM INTEGRATION add-on.
(ECS4HCM) PUBLIC 11
Constant ID Constant Name
0001 EC to ERP (BIB) / EC to ERP (Non-BIB): Simulation Mode
0010 ERP to EC/EC to ERP (BIB): Activate BIB for EC to ERP Employ
4000 EC to ERP (Non-BIB): Default Date of Birth
4010 EC to ERP (Non-BIB): Default Pay Group
4020 EC to ERP (BIB): Move of FTSD
5000 Default Template group for P. Api
Related Information
Deleting Constants That Are No Longer Required [page 37]
2.1.5 Switches Removed from T77S0 Table
We removed some switches from the T77S0 table in the SFSF EC S4 HCM INTEGRATION add-on.
The following switches have been converted to constants in table ECPAO_CONSTANTS.
Constant in ECPAO_CON
Group Semantic Abbreviation Description STANTS
SFSFI OANSC Don't Create Position to Job EC to ERP: Omit Position-Job

Relation Rel. in Non-Config. Org As
signm
SFSFI OANSK Don't Create Position to Cost EC to ERP: Omit Pos.-Cost

Center Relation C. Rel. in Non-Config. Org As
signm
SFSFI OANSO Don't Create Position to Org. EC to ERP: Omit Pos.-Org

Unit Relation Unit Rel. in Non-Config. Or
gAssignm
SFSFI OANSS Don't Create Position to Man EC to ERP: Omit Pos.-Man

ager Position Relation ager Rel. in Non-Config. Org
Assignm
SFSFI VCNCY Handle Relations of Vacant EC to ERP: Pos. Relations: Va

and Staffed Positions cant/Staffed fr. Diff. Sources
The following switches have been completely removed because their functionality is no longer needed.
Group Semantic Abbreviation Description
SFSFI SPOMP Use Specific Processing for Organiza

tional Objects
12 PUBLIC (ECS4HCM)
SFSFI PMACT Position Management Is Enabled in Em

ployee Central
Related Information
Object-Specific Replication and Processing of Organizational Objects No Longer Available [page 22]
Checking Switch Settings Made in Table T77S0 [page 28]
Transferring Switch Settings Made in Table T77S0 [page 38]
2.1.6 Authorization Roles in SAP S∕4HANA Revised
We've reworked our template roles in the SFSF EC S4 HCM INTEGRATION (ECS4HCM) add-on so that you can
clearly separate the replication of data from Employee Central and the processing of the data in SAP S∕4HANA.
Our template roles allow you to split the tasks among different users:
• A technical user for data replication, who doesn't need to maintain any HR data in the SAP S∕4HANA system.
• A processing user, who requires the authorization to edit personnel data.
Here's an overview of the changes we've made to the roles.
Previous Role Previous Role De New Role Descrip Change in Role Change in Authori
Name New Role Name scription tion Purpose zations
SAP_HR_EC SAP_HR_EC Employee Master n/a (stays the The role is now for Authorization ob
PAO_BIB_WEB PAO_WEBSERVI Data and Org As same) the technical user
ject PLOG
SERVICES CES signment Replica only. The process
(Personnel
tion from EC - Tech ing of replication
nical User requests for or Planning) removed
ganizational assign
Authorization ob
ments in the stag
ject P_ORGIN (HR
ing area, including
the update of data Master Data) with
in the relevant info read and write au
type records, has thorization for info
been removed. types removed
Authorization ob
ject S_TABU_NAM
(Table Access)
with table EC
PAO_RPRQ_EE re
moved
(ECS4HCM) PUBLIC 13
SAP_HR_EC SAP_HR_EC Employee Master n/a (stays the Use of the replica Authorization ob
PAO_BIB_PROC PAO_PROCESSING Data and Org As same) tion request viewer
ject S_TCODE
ESSING signment Replica for the new em
(Transaction
tion from EC - Busi ployee staging area
ness User and processing of Code Check):
replication requests Transactions EC
for employee mas PAO_EE_VIEWER,
ter data and or ECPAO_EE_DELE
ganizational assign
TION, and
ments in the stag
SRT_MONI added
ing area, including
the update of data Authorization ob
in the relevant info ject S_TABU_NAM
type records, have
(Table Access):
been added.
Table EC
PAO_RPRQ_EE with
read and write au
thorization added
Authorization ob
ject S_APPL_LOG
(Application Log):
Display authoriza
tion for log objects
PAOC_SFI_OM and
REPL_REQ_PROC
ESSING added
Authorization ob
ject PLOG
(Personnel
Planning) added
Authorization ob
ject P_ORGIN (HR
Master Data) with
read and write au
thorization for info
types added
Authorization ob
ject P_PERNR
(Personnel Number
Check) with
read authorization
added
Authorization ob
ject P_PCR (Payroll
Control Record)
14 PUBLIC (ECS4HCM)
with display author

ization added
SAP_HR_SFIOM_BI SAP_HR_SFIOM_W Organizational Ob n/a (stays the The role now Authorization ob
B_WEBSERVICES EBSERVICES ject Replication same) checks whether the ject S_TABU_NAM
from Employee user has permis (Table
Central - Technical sion to access Access): Table
User the staging area SFIOM_GENRQ_HD
for replication of added
organizational ob
jects.
(ECS4HCM) PUBLIC 15
SAP_HR_SFIOM_P n/a (stays the Organizational Data Organizational Ob The role is now Authorization ob
ROCESSING same) Replication from ject Replication used for organiza
ject S_TCODE
Employee Central - from Employee tional objects only.
(Transaction Code
Business User Central - Business The processing of
User replication requests Check): Transac
for organizational tion SRT_MONI
assignments in the added, transac
staging area, in tions
cluding the update
SFIOM_DEL_ORG_
of data in the rel
ASS and
evant infotype re
cords, has been re SFIOM_VIEW_RE
moved. QUESTS removed
Authorization ob
ject S_TABU_NAM
(Table Access):
Tables
SFIOM_RPRQ_EE
and
SFIOM_RPRQ_OSI
(Change, Display)
removed
Authorization ob
ject P_PCR (Payroll
Control Record)
with display author
ization added
Authorization ob
ject S_SRT_MONI
(Web Service
Message
Monitoring) with in
terface namespace
http://
sap.com/xi/
PASEIN and inter
face name
OrganisationalO
bjectReplicatio
nResponse_In
added
 Note
The Role
Maintenance
transaction
16 PUBLIC (ECS4HCM)
truncates the
name of the
web service in
terface after
40 characters.
SAP_HR_SFIOM_W n/a n/a n/a The role has been n/a

EBSERVICES deleted.
SAP_HR_TIM_EC_ n/a n/a n/a The role has been n/a

REPL deleted.
Related Information
Checking and Adjusting Authorization Roles [page 41]
2.1.7 Replication Direction Is Required for Transformation

Template Groups
We recommend that you use separate transformation template groups in the SFSF EC S4 HCM INTEGRATION
(ECS4HCM) add-on for the replication from SAP S∕4HANA to Employee Central and from Employee Central to SAP
S∕4HANA.
In the SFSF EC INTEGRATION (PA_SE_IN) add-on, you could use transformation template groups for both
directions and then define within the template group the direction in which, for example, a conversion rule was
used. However, this made the use of template groups more complex because you always had to check within the
template group which template or conversion rule you could use for which direction. That's why we recommend
that you use different template groups for the different replication directions in the SFSF EC S4 HCM INTEGRATION
add-on. You can keep template groups that you've used for both directions if you don't change anything in the
field mapping and don't use validations. However, we recommend that you use different template groups for the
replication directions. When you create new transformation template groups, Replication Direction is a mandatory
field.
Related Information
Splitting Transformation Template Groups and Defining Replication Direction [page 44]
(ECS4HCM) PUBLIC 17
2.1.8 Initiating Full Load from Query Program for Replication of
Employee Data
You can initiate a full load directly from the selection screen of the Create and Execute Employee Master Data
and Org. Assignment Query (ECPAO_EE_ORG_REPL_QUERY) program in the SFSF EC S4 HCM INTEGRATION
(ECS4HCM) add-on.
Initiating a full load is required, for example, when you move the full transmission start date for replication of
employee data from Employee Central into the past.
In the SFSF EC S4 HCM INTEGRATION add-on, you can select the Initiate Full Load checkbox on
the selection screen of the Create and Execute Employee Master Data and Org. Assignment Query
(ECPAO_EE_ORG_REPL_QUERY) program when you run the program manually.
In the SFSF EC INTEGRATION (PA_SE_IN) add-on, the option to initiate a full load wasn't available on the selection
screen of the query program. You had to go to the Delete Employee Queries (ECPAO_DEL_QRY_ADM) transaction
and delete the entry for the corresponding query from the Administration of Employee Master Data and Org Assign.
Query (ECPAO_QRY_ADM) table to initiate a full load.
Related Information
Querying Employee Master Data and Organizational Assignments Manually from Employee Central
2.1.9 New Staging Area for Employee Data
We introduced a staging area for employee data (including employee organizational assignments) in the SFSF EC
S4 HCM INTEGRATION (ECS4HCM) add-on to decouple replication of the employee data from processing of the
data in the SAP S∕4HANA system.
In the SFSF EC INTEGRATION (PA_SE_IN) add-on, the BIB-based replication of employee master data updated
the data in the corresponding Personnel Management infotypes as soon as it arrived from Employee Central in
the SAP S∕4HANA system. Now, the new staging area separates data replication from updating the data in the
SAP S∕4HANA infotypes. You can divide these tasks between different users. The processing user requires the
authorization to edit personnel data. The data replication user is a technical user and doesn't need to maintain any
HR data. We provide template roles that you can copy and use for this purpose.
We provide the following programs for the new staging area:
Program Program Title Transaction for Accessing the Program
ECPAO_RPRQ_EE_VIEWER View Employee Replication Requests ECPAO_EE_VIEWER
ECPAO_RPRQ_EE_PROCESSING Process Employee Replication Requests ECPAO_EE_PROCESSING
ECPAO_RPRQ_EE_DELETION Delete Employee Replication Requests ECPAO_EE_DELETION
The options Enable Extended Verbose Logging (for Employee Master Data) and Test Mode have been removed
from the Create and Execute Employee Master Data and Org. Assignment Query (ECPAO_EE_ORG_REPL_QUERY)
18 PUBLIC (ECS4HCM)
program because they are now available in the staging area viewer (that is, the View Employee Replication Requests
(ECPAO_EE_VIEWER) transaction).
Related Information
Using the Staging Area for Employee Replication Requests

Authorization Roles in SAP S∕4HANA Revised [page 13]
Getting Started with the New Employee Staging Area [page 45]
2.1.10 Purge Status Overview Option Is Now Standard for Purge

Validation
Using the purge status overview is now the standard when data replication to the SAP S∕4HANA system validates
and reacts to a purge of employee data in Employee Central.
Using the purge status overview means that the SAP S∕4HANA system evaluates the
DRTMPurgeStatusOverview segment provided by the CompoundEmployee API. This segment contains detailed
information about the purge of employee data in Employee Central, which enables the SAP S∕4HANA system to
react appropriately to the purge.
In the SFSF EC INTEGRATION (PA_SE_IN) add-on, you could still decide whether the SAP S∕4HANA system should
use the validation against the effective end date filter provided by the CompoundEmployee API. This option is no
longer available in the SFSF EC S4 HCM INTEGRATION (ECS4HCM) add-on. Therefore, we’ve removed the query
parameter Use Purge Status Overview for Data Purge from the customizing activity Define Parameters for Employee
Master Data and Org. Assignment Query. If you haven’t yet used the purge status overview in the PA_SE_IN add-on,
your system may behave differently if you purge employee data in Employee Central that is contained in the
replication to SAP S∕4HANA.
 Remember
If you grant the CompoundEmployee API user access only to defined segments, you must add the permission
for the DRTMPurgeStatusOverview segment if you haven't used the purge status overview before.
You can find all information about data purge in the SAP SuccessFactors guide Implementing and Managing Data
Protection and Privacy (see Related Information).
Related Information
Validation of Employee Data Purge in Data Replication from Employee Central (SFSF EC S4 HCM INTEGRATION)
(ECS4HCM) PUBLIC 19
2.1.11 Staging Area for Organizational Assignment Replication
No Longer Available
We've removed the staging area for organizational assignments replicated from Employee Central because
organizational assignment replication is now part of employee data replication.
In the SFSF EC INTEGRATION (PA_SE_IN) add-on, there was a staging area for organizational assignments
replicated from Employee Central. In the SFSF EC S4 HCM INTEGRATION (ECS4HCM) add-on, replication of
employee organizational assignment is part of employee data replication. We introduced a new staging area for
employee data, which also covers employee organizational assignments. Therefore, we removed the separate
staging area for organizational assignments. This has the following effects:
The following tables are no longer used.
Table Purpose of Table
SFIOM_RPRQ_OSCXT Replication Request Org. Structure Item Country fields
SFIOM_RPRQ_OSI Replication Request Organizational Structure Item
SFIOM_RPRQ_OSIDT Replication Request Organizational Structure Item Details
SFIOM_RPRQ_OSXT Replication Request Org. Structure Item Customer fields
SFIOM_RPRQ_TEXT Replication Request Org. Structure Item Texts
The following programs are obsolete and no longer available for use in the SFSF EC S4 HCM INTEGRATION
(ECS4HCM) add-on.
• Display Employee Org. Assignment Replication Requests (RH_SFIOM_VIEW_EE_ORG_ASS_RPRQ)

• Replicate Employee Org. Assignments from EC to ERP Org. Mgmt (RH_SFIOM_PROC_EE_ORG_ASS_RPRQ)
• Delete Employee Org. Assignment Replication Requests (RH_SFIOM_DEL_EE_ORG_ASS_RPRQ)
• Display Employee Organizational Assignment Replications (RH_SFIOM_CHECK_EE_ORG_ASS)
Organizational assignment replication requests have been removed from the Replication Request Monitor
(SFIUI_A_REPL_REQ_MONITOR Web Dynpro application).
Related Information
New Staging Area for Employee Data [page 18]

Disabling Background Jobs for Staging Area for Organizational Assignment Replication [page 46]
2.1.12 New Configurable Replication of Employee

Organizational Assignments
You can configure replication of organizational assignments from Employee Central in Customizing of the Business
Integration Builder in the SFSF EC S4 HCM INTEGRATION (ECS4HCM) add-on.
In the SFSF EC INTEGRATION (PA_SE_IN) add-on, the replication of organizational assignments wasn't
configurable. The way how position relationships were created in the SAP S∕4HANA system based on the
20 PUBLIC (ECS4HCM)
employee's job information and job relationships in Employee Central was hard-coded. You were able to influence
the behavior only by implementing a Business Add-In (BAdI).
 Example
You had to implement a BAdI to fill the Weighting Percentage (PROZT) field of a position relationship with the
value from Employee Central.
In the SFSF EC S4 HCM INTEGRATION (ECS4HCM) add-on, you can now configure the replication of organizational
assignments in Customizing of the Business Integration Builder.
 Example
You can map the Weighting Percentage (PROZT) field of a position relationship with the corresponding Employee
Central field in Customizing.
The SAP S∕4HANA system uses the configurable organizational assignment for the corresponding transformation
template group as soon as the Select Position to Be Used for Relationship to Personnel Number customizing activity
has at least one entry. Making an entry in this customizing activity has the following effects:
• The system doesn't call any implementations of the BAdIs Enhancements for Adapting Employee
Organizational Assignment (EX_SFIOM_ADAPT_EE_ORG_ASSGNMNT) and Enhancements for Adapting
Employee Organizational Assignment Request (EX_SFIOM_ADAPT_EE_ORG_ASS_REQ).
• The system ignores the following constants in the customizing activity Maintain Constant Values for Data
Replication from EC:
• EC to ERP: Omit Position-Job Rel. in Non-Config. Org Assignm
• EC to ERP: Omit Pos.-Cost C. Rel. in Non-Config. Org Assignm
• EC to ERP: Omit Pos.-Org Unit Rel. in Non-Config. OrgAssignm
• EC to ERP: Omit Pos.-Manager Rel. in Non-Config. Org Assignm
If you want to exclude position relationships from the replication of organizational assignments (in particular, if
you've configured the replication of organizational objects to create the relationships), simply don't configure
them in the customizing activities Define Relationship Mapping for Position or Define Job Relationship Mapping
for Position.
Related Information
Previous (Non-Configurable) Approach to Create Position Relationships in SAP S∕4HANA

Getting Started with Configuring Organizational Assignment Replication in Customizing [page 47]
2.1.13 Use of New Infotype Framework for Integration

Between Organizational Management and Personnel
Administration (PA/PD Integration) Is Mandatory
Using the new infotype framework in PA/PD integration for organizational data that was replicated from Employee
Central is mandatory in the SFSF EC S4 HCM INTEGRATION (ECS4HCM) add-on.
If you've activated the integration between Organizational Management and Personnel Administration (PA/PD
integration) in your SAP S∕4HANA system, the organizational data is synchronized between the infotypes
(ECS4HCM) PUBLIC 21
Relationships (1001) and Organizational Assignment (0001). Using the new infotype framework for this
synchronization improves performance and enables better message handling in the replication processes.
Therefore, the usage of the new infotype framework is a required prerequisite for the replication of organizational
objects and organizational employee assignments from Employee Central in the SFSF EC S4 HCM INTEGRATION
add-on.
 Note
The new infotype framework doesn't support dynamic actions. But since the Business Integration Builder (BIB)
uses the new infotype framework, you can't use dynamic actions in BIB-based data replication from Employee
Central anyway.
Related Information
Enabling Use of New Infotype Framework for Integration Between Organizational Management and Personnel
Administration (PA/PD Integration) [page 40]
2.1.14 Object-Specific Replication and Processing of

Organizational Objects No Longer Available
The SFSF EC S4 HCM INTEGRATION (ECS4HCM) add-on uses the generic replication of organizational objects with
generic processing only.
In the SFSF EC INTEGRATION (PA_SE_IN) add-on, you could still use object-specific replication and processing for
the standard objects (departments, divisions, business units, job classifications, and positions). You could set the
SFSFI SPOMP switch in the customizing activity Define Specific Processing for Organizational Objects to instruct
the SAP S∕4HANA system to use the previous, object-specific processing for these objects.
This option is no longer available. We've made the following changes in the SFSF EC S4 HCM INTEGRATION add-on:
• The T77S0 switch SFSFI SPOMP has been deleted.

• The following Business Add-Ins (BAdIs) have been deleted:
• Enhancements for Setting the Parent of Organizational Structure Items (EX_SFIOM_SET_PARENT)
• Enhancements for Processing Customer-Specific Fields (EX_SFIOM_PROC_CUSTOMER_FIELDS)
• Enhancements for Processing Country Specific Fields (EX_SFIOM_PROC_COUNTRY_FIELDS)
Your implementations of these BAdIs are no longer called after the upgrade.
• You now configure the replication of organizational objects exclusively in Business Integration Builder (BIB).
Related Information
Switches Removed from T77S0 Table [page 12]

Replacing Object-Specific with Generic Replication and Processing of Organizational Objects [page 49]
22 PUBLIC (ECS4HCM)
2.1.15 Full Transmission Start Date for Organizational Object
Replication Defined in Transformation Template Group
You now define the full transmission start date (FTSD) for the replication of organizational objects from Employee
Central in the transformation template group.
In the SFSF EC INTEGRATION (PA_SE_IN) add-on, you entered this date on the selection screen of the Create and
Execute Organizational Object Replication Query (RH_SFIOM_ORG_OBJ_REPL_QUERY) program. We've removed the
Full Transmission Start Date field from the selection screen of the program.
Related Information
Moving Full Transmission Start Date for Organizational Object Replication from Query Program to Transformation
Template Group [page 50]
2.1.16 Full Load No Longer Performed Automatically When

Full Transmission Start Date for Organizational Object
Replication Is Moved Into the Past
In the SFSF EC S4 HCM INTEGRATION (ECS4HCM) add-on, the query program doesn't perform the full data load
from Employee Central automatically if you move the full transmission start date (FTSD) into the past after you've
already replicated organizational objects.
If you move the FTSD into the past, ensure that you initiate a full load of the data from Employee Central. To do so,
run the Create and Execute Organizational Object Replication Query (RH_SFIOM_ORG_OBJ_REPL_QUERY) program
with the option Initiate Full Load selected.
Related Information
Querying Organizational Objects Manually from Employee Central
2.1.17 New Status Added and Replication Content Type

Removed in the Data Replication Monitor
We added a new status and removed the replication content type for organizational assignments to enable the
Employee Central Data Replication Monitor for use of the new staging area for employee data in SAP S∕4HANA.
The new status Awaiting Processing updates the Data Replication Monitor about employee replication requests that
have been added to the staging area in the SAP S∕4HANA system but haven't been processed yet. The status is
also used when employee replication requests have been processed with temporary errors.
(ECS4HCM) PUBLIC 23
The Data Replication Monitor now only uses the Employee Master Data replication content type to report the
status of the replication of employee data (including organizational assignments) from Employee Central to SAP
S∕4HANA. The Employee Organizational Assignment replication content type is no longer used.
 Caution
The updates in the Employee Central Data Replication Monitor will only be available after your SAP
SuccessFactors instance has been upgraded to the 2H 2022 release.
Related Information

Removing Records with Replication Content Type Employee Organizational Assignment from the Data Replication
Monitor [page 51]
2.1.18 Use of New Point-to-Point Time Data Replication from

Employee Central Is Mandatory
Point-to-point (PTP) time data replication is mandatory for the SFSF EC S4 HCM INTEGRATION (ECS4HCM)
add-on if you want to replicate employee time data from Employee Central.
If you've been using middleware-based replication of employee time data from Employee Central in the SFSF EC
INTEGRATION (PA_SE_IN) add-on, upgrade to PTP time data replication.
For more information about point-to-point time data replication, refer to Implementing Point-to-Point Time Data
Replication.
Related Information
Upgrading to Point-to-Point Time Data Replication [page 52]
2.2 Preparing the Upgrade
What you should do in the SFSF EC INTEGRATION (PA_SE_IN) BIB add-on before you start the upgrade to SFSF EC
S4 HCM INTEGRATION (ECS4HCM) add-on.
Read more about the points you need to consider when you plan to migrate your BIB Employee Master data
replication and Organizational Assignment replication solution in PA_SE_IN to the corresponding integration
solution based on BIB in ECS4HCM add-on.In In addition you might have to check the topics in the Post-Upgrade
Steps section before you start the upgrade process.
24 PUBLIC (ECS4HCM)
Stopping Data Replication from Employee Central [page 25]
Stop data replication from Employee Central to your SAP S/4HANA or SAP ERP HCM system before you
start the upgrade.
Processing Open Replication Requests [page 27]

Before the upgrade to the SFSF EC S4 HCM INTEGRATION (ECS4HCM) add-on, make sure that no open
or pending requests for organizational assignments and for the object-specific replication of organizational
objects remain in the corresponding staging areas. You can no longer process them after the upgrade.

Before the upgrade, check the switch settings that you've made in the T77S0 table for the SFSF EC
INTEGRATION (PA_SE_IN) add-on, to be able to make the settings again after the upgrade to the SFSF EC
Checking Usage of Data from Tables That Will Be Deleted [page 30]
Before the upgrade, check whether you use data from tables and table columns that we've deleted in the
SFSF EC S4 HCM INTEGRATION (ECS4HCM) add-on in customer-specific processes.
Retaining Settings Before Upgrade for Comparison After Upgrade [page 31]
Don't change any settings before the upgrade to the SFSF EC S4 HCM INTEGRATION (ECS4HCM) add-on
so that you can compare whether the replication is running as before after the upgrade.
2.2.1 Stopping Data Replication from Employee Central
Stop data replication from Employee Central to your SAP S/4HANA or SAP ERP HCM system before you start the
upgrade.
Procedure
1. Sign in to your SAP S/4HANA or SAP ERP HCM system.

2. Go to the Simple Job Selection (SM37) transaction and search for all jobs that you scheduled for data
replication from Employee Central.
3. Pause all jobs.
For more information, refer to Managing Jobs from the Job Overview.
For some replications, the scheduling was done in the middleware. Continue with the following steps if you've used
these integration versions.
4. If you've scheduled integration flows in SAP Cloud Integration, sign in to the SAP Cloud Integration web UI.
5. Undeploy the following integration flows.
Purpose Integration Flow
Previous version of employee master data replication from Replicate Employee Master Data from SAP SuccessFactors
Employee Central (for initial implementation before Q2 Employee Central to SAP ERP or SAP S4HANA
2017)
(ECS4HCM) PUBLIC 25
Purpose Integration Flow
Previous version of organizational assignment replication Replicate Organizational Assignments from SAP
from Employee Central (for initial implementation before Q2 SuccessFactors Employee Central to SAP ERP or SAP
2017) S4HANA
Employee time data replication from Employee Central Replicate Time Off Data from SAP SuccessFactors Employee
Central to SAP ERP
Employee time data replication from Employee Central Replicate Time Sheet Data from SAP SuccessFactors
Employee Central to SAP ERP
For more information, refer to Managing Integration Content in the SAP Cloud Integration documentation.
6. If you've scheduled processes in Boomi, sign in to Boomi AtomSphere.

7. Undeploy the following processes.
Purpose Process
Previous version of employee master data replication from Packaged Integration: SuccessFactors Employee Central to
Employee Central (for initial implementation before Q2 ERP Employee Data Replication
2017)
Previous version of organizational assignment replication Packaged Integration: EC to ERP - Employee Organizational
from Employee Central (for initial implementation before Q2 Assignment Replication v2.0
2017)
Employee time data replication from Employee Central Packaged Integration: SuccessFactors Employee Central to
ERP - Absence Data Replication
Employee time data replication from Employee Central Packaged Integration: SuccessFactors Employee Central to
ERP - Time Pay Component Replication
Next Steps
Some programs have been deprecated. For example, the programs intended for the staging area for organizational
assignments, which is now obsolete. You no longer need to schedule jobs for them after the upgrade. Some
programs, such as programs intended for the new staging area for employee data, have been added. Schedule new
background jobs for them.
Related Information
26 PUBLIC (ECS4HCM)
2.2.2 Processing Open Replication Requests
Before the upgrade to the SFSF EC S4 HCM INTEGRATION (ECS4HCM) add-on, make sure that no open or pending
requests for organizational assignments and for the object-specific replication of organizational objects remain in
the corresponding staging areas. You can no longer process them after the upgrade.
Context
Before the upgrade, process all replication requests for employee organizational assignments that have one of the
statuses Open or Pending because the staging area for organizational assignments is no longer available after the
upgrade. Replication requests with the status Failed are replicated again after the upgrade, when you run the first
query to replicate employee master data and organizational assignments.
Also process all replication requests from the object-specific replication of organizational objects with the statuses
Open, Pending, or Failed. Object-specific processing of organizational objects is removed from the SFSF EC S4
HCM INTEGRATION add-on. Therefore, you can no longer process these requests after the upgrade.
 Remember
Object-specific processing means that the value of the T77S0 switch SFSFI SPOMP is set to X in the Define If
You Use Specific Processing for Organizational Objects customizing activity in your system.
If you haven't used object-specific processing of organizational objects in the SFSF EC INTEGRATION (PA_SE_IN)
add-on, you don't need to process any replication requests for organizational objects before the upgrade.
Procedure
1. Sign in to your SAP S∕4HANA or SAP ERP HCM system in which the SFSF EC INTEGRATION add-on is still
installed.
2. Go to the Display Employee Org. Assignment Replication Requests (SFIOM_VIEW_REQUESTS) transaction.
3. Process all requests that have one of the statuses Open or Pending.
4. When replication requests with one of these statuses remain after processing, correct the corresponding errors
and then process them again.
5. Continue until there are no more open entries.
6. If you've used object-specific processing of organizational objects, go to the Display Organizational Object
Replication Requests (SFIOM_VIEW_ORG_REQS) transaction.
7. Process all requests that refer to object-specific replication and have one of the statuses Open, Pending, or
Failed.
8. Proceed in the same way as you did for organizational assignments.
(ECS4HCM) PUBLIC 27
Results
No replication requests with status Open or Pending should remain in the staging area for employee organizational
assignments. No replication requests related to the object-specific processing of organizational objects should
remain in the staging area for organizational objects.
Next Steps
If you can’t correct the errors and still want to perform the upgrade, make a note of the IDs of the relevant
employees and organizational objects. Then replicate these employees and objects again after the upgrade.
Related Information
Staging Area for Organizational Assignment Replication No Longer Available [page 20]
2.2.3 Checking Switch Settings Made in Table T77S0
Before the upgrade, check the switch settings that you've made in the T77S0 table for the SFSF EC INTEGRATION
(PA_SE_IN) add-on, to be able to make the settings again after the upgrade to the SFSF EC S4 HCM INTEGRATION
(ECS4HCM) add-on.
Context
We've replaced some T77S0 switches with constants in the ECPAO_CONSTANTS table. To be able to make the
same settings for the constants that you stored for the T77S0 switches, make a note of your settings before the
upgrade. After the upgrade, you can no longer see the settings that you've stored for these switches in table T77S0.
Procedure
1. Sign in to your SAP S∕4HANA or SAP ERP HCM system in which the SFSF EC INTEGRATION add-on is still
installed.
2. Go to Customizing for the Business Integration Builder and choose Organizational Data Integration Restrict
Relations Created When Replicating Organizational Assignments .
3. Note down the settings you made for the following switches.
28 PUBLIC (ECS4HCM)
SFSFI OANSO Don't Create Position to Org. Unit Rela

tion
SFSFI OANSC Don't Create Position to Job Relation
SFSFI OANSS Don't Create Position to Manager Posi

tion Relation
SFSFI OANSK Don't Create Position to Cost Center

Relation
4. Choose Organizational Data Integration Replicate Relations of Vacant and Staffed Positions from Different
Sources in the same customizing structure.
5. Note down the settings you made for the following switch.
SFSFI VCNCY Handle Relations of Vacant and Staffed

Positions
Next Steps
The following switches are no longer used in the SFSF EC S4 HCM INTEGRATION add-on and have been deleted.
You don't need to take note of the settings you made for these switches.

tional Objects

ployee Central
Related Information

Excluding Position Relationships from Organizational Assignment Replication
Replicating Relationships of Vacant and Staffed Positions from Different Sources in Employee Central
(ECS4HCM) PUBLIC 29
2.2.4 Checking Usage of Data from Tables That Will Be Deleted
Before the upgrade, check whether you use data from tables and table columns that we've deleted in the SFSF EC
S4 HCM INTEGRATION (ECS4HCM) add-on in customer-specific processes.
Context
We've deleted some tables and table fields that were used in data replication from Employee Central in the SFSF EC
S4 HCM INTEGRATION add-on because they’re no longer needed. Before the upgrade, check whether you use any
data from these tables or fields because the data will no longer be available after the upgrade.
Procedure
1. Check whether you use any data from the following tables in customer-specific processes.
ECPAO_INFTY_BLST Excluded Infotypes in Business Integration Builder
ECPAOX_PROXY_FLD Proxy Node Field Details
ECPAOX_PROXY_NOD Proxy Node Details
ODFIN_MAP_BUKRS Key Mapping Company - Company Code
ODFIN_MAP_KOSTL Key Mapping Cost Center - Cost Center
PAOCFEC_ADR_IMPC Customer-specific address implementation class per coun

try
PAOCFEC_ADR_IMPS SAP delivered address implementation class per country
PAOCFEC_CURR Currency of Wage Type
PAOCFEC_EXTMAP Employee Central Extensibility Mapping Configuration
PAOCFEC_FIELD EC field with values
PAOCFEC_IT_FILT Filtering of Infotypes and Subtypes in Replication
PAOCFEC_JOB_POS Job Key and Position Mapping
PAOCFEC_KMAPPEST Permanent Establishment Key Mapping
PAOCFEC_MAP_DATE Employee Central Date Type Mapping
PAOCFEC_S_DATE Allowed Dates for Date Type Mapping
PAOCFEC_S_INFTY Allowed Infotypes for Extensibility Mapping
PAOCFEC_S_NODE Allowed Node Names for Extensibility Mapping
PAOCFEC_WT_PROC Processing of Wage Types in EC Replication
PAOCFEC_WTP_ADPY Processing of Non-Recurring Payment Wage Types
30 PUBLIC (ECS4HCM)
SFIOM_RPRQ_OSCXT Replication Request Org. Structure Item Country fields
SFIOM_RPRQ_OSI Replication Request Organizational Structure Item
SFIOM_RPRQ_OSIDT Replication Request Organizational Structure Item Details
SFIOM_RPRQ_OSXT Replication Request Org. Structure Item Customer fields
SFIOM_RPRQ_TEXT Replication Request Org. Structure Item Texts
2. Check whether you use any data from the following table fields in customer-specific processes.
Table Purpose of Table Field Purpose of Field
SFIOM_RPRQ_EE Replication Request Em DEPARTM_REL_IND ID of Related Department

ployee
SFIOM_RPRQ_EE Replication Request Em ENFORCE_UPDATE Enforce Update Although No

ployee Changes Found
ECPAO_COMPANY EC Instance EMPLY_INTTRF International Transfers Han

dling
3. Adjust your processes before the upgrade if you use any of this data.
2.2.5 Retaining Settings Before Upgrade for Comparison After

Upgrade
Don't change any settings before the upgrade to the SFSF EC S4 HCM INTEGRATION (ECS4HCM) add-on so that
you can compare whether the replication is running as before after the upgrade.
Before the upgrade to the SFSF EC S4 HCM INTEGRATION add-on, don't make any changes in the SFSF EC
INTEGRATION (PA_SE_IN) add-on that could affect the behavior of the replication. For example, don't change the
following settings:
• Customizing: Don't change your settings, for example, regarding the field mapping defined in the
transformation templates, the filtering, or the parameters you configured for the query programs.
• Metadata: Don't import new metadata from Employee Central and also don't change the imported metadata in
SAP S∕4HANA.
• Full transmissiion start date (FTSD): Keep the same FTSD right before and after the upgrade.
• BAdI implementations: If you've implemented our Business Add-Ins (BAdIs) to enhance the replication, don't
change your implementation before the upgrade.
You can, of course, change the settings once you've successfully completed the upgrade. You can perform spot
checks to see if the data is replicated as expected.
Related Information
Replicating Selected Employees from Employee Central and Performing Spot Checks [page 36]
(ECS4HCM) PUBLIC 31
2.3 Upgrade Steps
Context
Now that you've prepared your system, you perform the upgrade from the software component version PA_SE_IN
100 (product version SFSF EC INTEGRATION 1210) to the software component version ECS4HCM 100 (product
version SFSF EC S4 HCM INTEGRATION 1.0).
Procedure
1. Go to the Maintenance Planner and choose Plan for SAP S/4HANA Upgrade or Update Existing SAP S/
4HANA System Next .
2. Select Upgrade or Update Existing SAP S/4HANA System and choose Next.
3. Select your existing system and select the target product version SAP S/4HANA 2022 or a higher version as
the minimum version.
4. Select Install or Maintain an Add-On.
5. Select SFSF EC S4 HCM INTEGRATION.
6. Select at least one instance, for example, PA Inbound Service Enabling, and the highest support package stack.
7. Follow the process to download the software packages and the target.xml file to your download directory.
8. Use the Software Update Manager (SUM) to upgrade your system.
For more information, refer to Software Update Manager 2.0 and SAP Note 1841471 .
2.4 Post-Upgrade Steps
What you should do in your SAP S∕4HANA system after you've upgraded to the SFSF EC S4 HCM INTEGRATION
(ECS4HCM) add-on from SFSF EC INTEGRATION (PA_SE_IN) BIB.

Undeploy integration flows in SAP Cloud Integration and in Boomi AtomSphere that are no longer used in
the SFSF EC S4 HCM INTEGRATION (ECS4HCM) add-on.
Checking and Adjusting Implicit Enhancements [page 35]

Check your implicit enhancements, if you've made any, after the upgrade to the SFSF EC S4 HCM
INTEGRATION (ECS4HCM) add-on.
Replicating Selected Employees from Employee Central and Performing Spot Checks [page 36]
32 PUBLIC (ECS4HCM)
After the upgrade, we recommend replicating some employees from Employee Central again and
processing them in simulation mode to ensure that the replication still behaves as before regarding your
use cases.

After the upgrade, delete all entries that still exist for obsolete constants from the Constants for Integration
with SuccessFactors (ECPAO_CONSTANTS) table in the SFSF EC S4 HCM INTEGRATION (ECS4HCM) add-
on.

After the upgrade, transfer the switch settings that you've made in table T77S0 in the SFSF EC
INTEGRATION (PA_SE_IN) add-on to the corresponding constants in the SFSF EC S4 HCM INTEGRATION
(ECS4HCM) add-on.
Determine that the new infotype framework is to be used in PA/PD integration for organizational data that
was replicated from Employee Central, to improve the performance and allow for better message handling
in the replication processes.

Adjust your custom roles that you've copied from our template roles if you want to make a clear separation
of tasks between technical user and business user.
Splitting Transformation Template Groups and Defining Replication Direction [page 44]
After the upgrade, split transformation template groups according to the direction of replication and assign
the respective direction to the template groups.
Start using the new staging area for employee data (including employee organizational assignments) in
the SFSF EC S4 HCM INTEGRATION (ECS4HCM) add-on that we introduced to decouple replication of the
employee data from processing of the data in the SAP S∕4HANA system.
Delete any background jobs that you scheduled for the staging area for organizational assignments
replicated from Employee Central because the separate staging area for organizational assignment
replication has been deleted in the SFSF EC S4 HCM INTEGRATION (ECS4HCM) add-on.
Getting Started with Configuring Organizational Assignment Replication in Customizing [page 47]
Configure replication of organizational assignments from Employee Central in Customizing of the Business
Integration Builder after you've upgraded to the SFSF EC S4 HCM INTEGRATION (ECS4HCM) add-on.
Replacing Object-Specific with Generic Replication and Processing of Organizational Objects [page 49]
Configure the replication of organizational objects in the Business Integration Builder (BIB) in the SFSF EC
S4 HCM INTEGRATION (ECS4HCM) add-on after the upgrade.
Moving Full Transmission Start Date for Organizational Object Replication from Query Program to
Transformation Template Group [page 50]
Remove the full transmission start date (FTSD) for the replication of organizational objects from Employee
Central from the query program and add it in the transformation template group.
Removing Records with Replication Content Type Employee Organizational Assignment from the Data
Replication Monitor [page 51]
After the upgrade to the SFSF EC S4 HCM INTEGRATION (ECS4HCM) add-on, manually delete data
records with replication content type Employee Organizational Assignment from the Data Replication
Monitor as soon as you no longer need them.
(ECS4HCM) PUBLIC 33
Switch to point-to-point time data replication for the SFSF EC S4 HCM INTEGRATION add-on if you've
been using middleware-based replication of employee time data from Employee Central in the SFSF EC
INTEGRATION (PA_SE_IN) add-on.
Converting the Dependent Mapping Data [page 54]

After the upgrade, you might have to use the dependents migration report to migrate the data from
dependent old key mapping table to the current key mapping table.
2.4.1 Undeploying Obsolete Integration Flows
Undeploy integration flows in SAP Cloud Integration and in Boomi AtomSphere that are no longer used in the SFSF
EC S4 HCM INTEGRATION (ECS4HCM) add-on.
Context
integration versions that were still in use. The SFSF EC S4 HCM INTEGRATION (ECS4HCM) add-on uses SAP
Cloud Integration as the only middleware for replication of employee data (including organizational assignments)
and organizational objects from Employee Central. And it uses only the latest versions of the integration flows. All
other integration flows that were available for previous integration versions are obsolete.
Procedure
1. Sign in to the SAP Cloud Integration web UI.

2. Undeploy all integration flows that you used for data replication from Employee Central, except for the
following ones.
ERP or SAP S/4HANA: Employee and Organizational Data SAP SuccessFactors Employee Central to SAP ERP or SAP
S4HANA

34 PUBLIC (ECS4HCM)
3. Sign in to Boomi AtomSphere.
4. Undeploy all processes that you used for data replication from Employee Central.
Related Information
SAP Cloud Integration Is Used as the Only Middleware [page 10]
2.4.2 Checking and Adjusting Implicit Enhancements
Check your implicit enhancements, if you've made any, after the upgrade to the SFSF EC S4 HCM INTEGRATION
(ECS4HCM) add-on.
Context
Take a look at the implicit enhancements if you have made any in the SAP S∕4HANA system. We have performed
code refactoring and restructuring so that the implicit enhancements may no longer be usable in the SFSF EC
S4 HCM INTEGRATION add-on because the new version of a development object may no longer be compatible
with your extension. For example, if an enhanced development object was deleted or a data type used in the
enhancement no longer exists.
The existing Business Add-In (BAdI) definitions in the Business Integration Builder (BIB) are retained.
Procedure
1. Check you implicit enhancements.
For more information, refer to Enhancement Framework.

2. Adjust your enhancements if necessary to ensure data consistency.
(ECS4HCM) PUBLIC 35
2.4.3 Replicating Selected Employees from Employee Central
and Performing Spot Checks
After the upgrade, we recommend replicating some employees from Employee Central again and processing them
in simulation mode to ensure that the replication still behaves as before regarding your use cases.
Prerequisites
You've retained your settings before the upgrade for comparison after the upgrade.
You've checked your implicit enhancements if you have any after the upgrade and corrected them if necessary.
Context
Simulation of the processing is only possible for employee master data. Verbose logging is also available for
employee master data only.
Procedure
1. Go to the Create Employee Queries (ECPAO_EE_ORG_QUERY) transaction in your SAP S∕4HANA system to run
the query program.
2. Select the transformation template group that you use for replication of employee data from Employee Central.
3. Enter the IDs of the employees that you want to check.
4. Execute the query.
5. Go to the View Employee Replication Requests (ECPAO_EE_VIEWER) transaction after the query has run.
6. Select one ore more of the employees that you just replicated.
You can select up to 50 employees by holding down the Ctrl key as you select entries in the list.
7. Choose Simulate Processing With Verbose Log or Without Verbose Log to simulate the processing.
If you don’t select the verbose logging, the application log shows the errors that have occurred while
processing the employee. If you select the verbose logging, the application log additionally shows the internal
sequence of how the employee details are processed in the SAP S∕4HANA system. It shows, for example, the
transformation template group used in the configuration, the processed infotype records, and details about the
updated SAP S∕4HANA fields.
8. Analyze the application log for the employees.
9. Go to the Message Monitor if you want to check the payload that was transferred from Employee Central.
10. Replicate more employees and simulate their processing to do more spot-checks.
11. Continue until you're sure that the replication is running as before.
36 PUBLIC (ECS4HCM)
Related Information
Retaining Settings Before Upgrade for Comparison After Upgrade [page 31]
Managing Employee Replication Requests in the Staging Area
Checking and Adjusting Implicit Enhancements [page 35]
Querying Employee Master Data and Organizational Assignments Manually from Employee Central
2.4.4 Deleting Constants That Are No Longer Required
After the upgrade, delete all entries that still exist for obsolete constants from the Constants for Integration with
SuccessFactors (ECPAO_CONSTANTS) table in the SFSF EC S4 HCM INTEGRATION (ECS4HCM) add-on.
Context
We removed some constants because they are no longer needed in the SFSF EC S4 HCM INTEGRATION add-on. If
you've made customizing settings for these constants in the PA_SE_IN add-on, there may still be entries for them
in the ECPAO_CONSTANTS, which are no longer required. Delete these entries after you've successfully completed
the upgrade.
 Note
You'll see the constant ID, but not the constant name of the obsolete constants.
Procedure
1. Go to Customizing of the Business Integration Builder and choose Data Replication from Employee Central
Basic Settings Maintain Constant Values for Data Replication from EC .
2. Delete all entries that still exist for the following constants.
0004 ERP to EC: Additional Event Records
0005 ERP to EC: Determine Personal Data of Global Employees
0006 ERP to EC: Set Inactive User Status w/ SAP Cloud Integra
tion
0010 ERP to EC/EC to ERP (BIB): Activate BIB for EC to ERP

Employ
(ECS4HCM) PUBLIC 37
Related Information
Constants Removed from Table ECPAO_CONSTANTS [page 11]
2.4.5 Transferring Switch Settings Made in Table T77S0
After the upgrade, transfer the switch settings that you've made in table T77S0 in the SFSF EC INTEGRATION
(PA_SE_IN) add-on to the corresponding constants in the SFSF EC S4 HCM INTEGRATION (ECS4HCM) add-on.
Prerequisites
You checked and noted down the settings you made in table T77S0 before the upgrade.
Context
Add the corresponding constant in table ECPAO_CONSTANTS for T77S0 switches that had the switch value X. If
the switch value of the T77S0 switch was empty before the upgrade, don't add the corresponding constant.
Procedure
2. Choose New Entries and select the constants that you want to add.
38 PUBLIC (ECS4HCM)
Corresponding Constant in EC
Group in T77S0 Semantic Abbreviation in T77S0 PAO_CONSTANTS
SFSFI OANSC EC to ERP: Omit Position-Job Rel. in

Non-Config. Org Assignm
SFSFI OANSK EC to ERP: Omit Pos.-Cost C. Rel. in

SFSFI OANSO EC to ERP: Omit Pos.-Org Unit Rel. in

Non-Config. OrgAssignm
SFSFI OANSS EC to ERP: Omit Pos.-Manager Rel. in

SFSFI VCNCY EC to ERP: Pos. Relations: Vacant/Staf

fed fr. Diff. Sources
3. Enter X in the Constant Value field for each constant that you add.
4. Save and transport your entries.
Next Steps
The following T77S0 switches are no longer used in the SFSF EC S4 HCM INTEGRATION add-on and have been
deleted.

tional Objects

ployee Central
No upgrade steps are required for the deleted switches.
Related Information

Excluding Position Relationships from Organizational Assignment Replication
Replicating Relationships of Vacant and Staffed Positions from Different Sources in Employee Central
(ECS4HCM) PUBLIC 39
2.4.6 Enabling Use of New Infotype Framework for Integration
Between Organizational Management and Personnel
Administration (PA/PD Integration)
Determine that the new infotype framework is to be used in PA/PD integration for organizational data that was
replicated from Employee Central, to improve the performance and allow for better message handling in the
replication processes.
Context
objects and organizational employee assignments from Employee Central.
 Note
Central anyway.
Procedure
1. Go to Customizing for the Business Integration Builder and choose Data Replication from Employee
Central Employee Data Employee Organizational Assignment Enable Use of New Infotype Framework
When Processing Replicated Org. Data or Data Replication from Employee Central Organizational
Objects Enable Use of New Infotype Framework When Processing Replicated Org. Data .
2. Check whether the following entry exists.
Group Sem.Abbr. Value Abbr. Description
PLOGI NITF X For example: Update Infotype

0001 Using New Infotype
Framework
3. Create the entry if it doesn't exist and transport the new entry.
40 PUBLIC (ECS4HCM)
Next Steps
If you use the non-configurable approach for the replication of organizational assignments from Employee Central,
you've possibly implemented a Business Add-In (BAdI) to enhance the replication. If you've done so, check
your implementation. Ensure that you use the classes provided for the new infotype framework in your BAdI
implementations to prevent runtime errors.
2.4.7 Checking and Adjusting Authorization Roles
Adjust your custom roles that you've copied from our template roles if you want to make a clear separation of tasks
between technical user and business user.
Context
We've reworked our template roles in the SFSF EC S4 HCM INTEGRATION (ECS4HCM) add-on. Our changed
template roles allow you to split the tasks among different users. Here's an overview of the changes we've made to
the roles.
Previous Role Name New Role Name Change in Authorizations
SAP_HR_ECPAO_BIB_WEBSERVICES SAP_HR_ECPAO_WEBSERVICES Authorization object PLOG (Personnel

Planning) removed
Authorization object P_ORGIN (HR

Master Data) with read and write authori
zation for infotypes removed
Authorization object S_TABU_NAM

(Table Access) with table EC
PAO_RPRQ_EE removed
(ECS4HCM) PUBLIC 41
SAP_HR_ECPAO_BIB_PROCESSING SAP_HR_ECPAO_PROCESSING Authorization object S_TCODE

(Transaction Code Check): Transactions
ECPAO_EE_VIEWER, ECPAO_EE_DELE
TION, SRT_MONI added

(Table Access): Tables ECPAO_RPRQ_EE
(Change, Display) added
Authorization object S_APPL_LOG

(Application Log): Display authorization
for log objects PAOC_SFI_OM and
REPL_REQ_PROCESSING added
Authorization object PLOG (Personnel

Planning) added

zation for infotypes added
Authorization object P_PERNR

(Personnel Number Check) with read au
thorization added
Authorization object P_PCR (Payroll

Control Record) with display authoriza
tion added
SAP_HR_SFIOM_BIB_WEBSERVICES SAP_HR_SFIOM_WEBSERVICES Authorization object S_TABU_NAM

(Table Access): Table SFIOM_GENRQ_HD
added
42 PUBLIC (ECS4HCM)
SAP_HR_SFIOM_PROCESSING n/a (stays the same) Authorization object S_TCODE

(Transaction Code Check): Trans
action SRT_MONI added, transac
tions SFIOM_DEL_ORG_ASS and
SFIOM_VIEW_REQUESTS removed

(Table Access): Tables SFIOM_RPRQ_EE
and SFIOM_RPRQ_OSI (Change, Display)
removed

tion added
Authorization object S_SRT_MONI (Web

Service Message Monitoring) with inter
face namespace http://sap.com/xi/
PASEIN and interface name
OrganisationalObjectReplication
Response_In added
 Note
The Role Maintenance transaction
truncates the name of the web serv
ice interface after 40 characters.
SAP_HR_SFIOM_WEBSERVICES n/a (role has been deleted) n/a (role has been deleted)
SAP_HR_TIM_EC_REPL n/a (role has been deleted) n/a (role has been deleted)
Procedure
1. Go to the Role Maintenance (PFCG) transaction in your SAP S∕4HANA system.
For more information about the role administration tools in the SAP S∕4HANA system, refer to User and Role
Administration of Application Server ABAP in the SAP NetWeaver documentation.
2. Copy the template roles to the customer namespace if you haven't yet created any customer-specific roles.
3. Compare your customer-specific roles with our new template roles if you've already created customer-specific
roles for the SFSF EC INTEGRATION (PA_SE_IN) add-on and adjust your roles as applicable.
4. In both cases, add or remove permissions if you want to set up your roles differently.
Related Information
Authorization Roles in SAP S∕4HANA Revised [page 13]

(ECS4HCM) PUBLIC 43
Granting Permissions in SAP S∕4HANA to Replicate Employee Master Data and Organizational Assignments from
Employee Central
Granting Permissions in SAP S∕4HANA to Process Employee Master Data and Organizational Assignments
Replicated from Employee Central
Granting Permissions in SAP S∕4HANA to Replicate Organizational Objects from Employee Central
Granting Permissions in SAP S∕4HANA to Process Organizational Objects Replicated from Employee Central
2.4.8 Splitting Transformation Template Groups and Defining

Replication Direction
After the upgrade, split transformation template groups according to the direction of replication and assign the
respective direction to the template groups.
Context
If you used transformation template groups for both replication directions in the SFSF EC INTEGRATION
(PA_SE_IN) add-on, split them after the upgrade so that each template group contains only field mappings for
one direction.
 Note
You can add descriptions for the transformation templates in a transformation template group. But when you
copy a template group, the reference to the description stays same. If you change the description for the new
template group, it is also changed for the template group from which you copied. Run the Update Template
Group in Text Table (ECPAO_UPDATE_TEMP_GRP_TT) program to fix this issue and make the reference to the
description unique for each template group.
You can keep template groups that you've used for both directions if you don't change anything in the field
mapping. However, we recommend that you use different template groups for the replication directions. When you
create new transformation template groups, Replication Direction is a mandatory field.
Procedure
1. Go to Customizing for the Business Integration Builder and choose Additional Tools Copy Configuration
from One EC Instance to Another EC Instance .
2. Select the Employee Central instance and a transformation template group that you want to copy in the Source
Configuration section.
3. Enter the same Employee Central instance in the Target Configuration section.
4. Enter a name for your new transformation template group in the Target Configuration section.
5. Deselect the Copy Replication Direction and Test Run checkboxes.
6. Choose Execute.
44 PUBLIC (ECS4HCM)
7. Repeat these steps for all template groups that you want to split according to the direction of replication.
8. Go the following customizing activities to add the replication direction.
Type of Data Customizing Path
Employee data replication from Employee Central Data Replication from Employee Central Employee
Data Field Mapping for Employee Data Replication from
Employee Central Define Field Mapping for Employee
Data
Organizational data replication from Employee Central Data Replication from Employee Central Organizational
Objects Field Mapping for Organizational Object
Replication from Employee Central Define Field Mapping
for Organizational Data
9. Select your transformation template groups one by one.

10. Add the applicable replication direction ERP to EC or EC to ERP to each template group.
Related Information
Replication Direction Is Required for Transformation Template Groups [page 17]
2.4.9 Getting Started with the New Employee Staging Area
Start using the new staging area for employee data (including employee organizational assignments) in the SFSF
EC S4 HCM INTEGRATION (ECS4HCM) add-on that we introduced to decouple replication of the employee data
from processing of the data in the SAP S∕4HANA system.
Context
The new staging area separates data replication from updating the data in the SAP S∕4HANA infotypes. You can
divide these tasks between different users. The processing user requires the authorization to edit personnel data.
The data replication user is a technical user and doesn't need to maintain any HR data. We provide template roles
that you can copy and use for this purpose.
Procedure
1. Adapt the authorizations of the technical and business users.
Technical users don't need any permissions to process HR data any longer. Business users for employee data
now also need the permissions required for organizational assignment replication.
(ECS4HCM) PUBLIC 45
2. Schedule a background job to regularly process employee replication requests.
3. Schedule a background job to regularly clean up the staging area for employee replication requests.
This background job deletes employee master data and organizational assignment requests that aren’t needed
anymore in your system.
4. Check the replication status in the Employee Central Data Replication Monitor.
5. Optional: Use the staging area viewer (transaction ECPAO_EE_VIEWER) to access the staging area for
employee replication requests in the SAP S∕4HANA system.
The staging area viewer is useful in the setup phase of the replication, for example, when errors occur more
frequently. You can analyze these errors, simulate the processing of replication requests for employee master
data, or process requests manually from the staging area viewer.
Related Information

Managing Employee Replication Requests in the Staging Area
Using Data Replication Monitor
Processing Employee Replication Requests Regularly
Cleaning Up the Staging Area for Employee Replication Requests
2.4.10 Disabling Background Jobs for Staging Area for

Organizational Assignment Replication
Delete any background jobs that you scheduled for the staging area for organizational assignments replicated from
Employee Central because the separate staging area for organizational assignment replication has been deleted in
Procedure
1. Go to the Simple Job Selection (SM37) transaction in your SAP S∕4HANA system.
For more information, refer to Managing Jobs from the Job Overview.
2. Search for all jobs that you scheduled for the following programs.
• Replicate Employee Org. Assignments from EC to ERP Org. Mgmt (RH_SFIOM_PROC_EE_ORG_ASS_RPRQ)
• Delete Employee Org. Assignment Replication Requests (RH_SFIOM_DEL_EE_ORG_ASS_RPRQ)
3. Delete these jobs.
46 PUBLIC (ECS4HCM)
2.4.11 Getting Started with Configuring Organizational
Assignment Replication in Customizing
Configure replication of organizational assignments from Employee Central in Customizing of the Business
Integration Builder after you've upgraded to the SFSF EC S4 HCM INTEGRATION (ECS4HCM) add-on.
Context
If you are a new customer who's implementing and configuring replication of employee organizational assignments
from Employee Central for the first time, use the new, configuration-based approach. We also recommend
switching to the new approach if you've set up and used the replication of organizational assignments from
Employee Central before, based on the SFSF EC INTEGRATION (PA_SE_IN) add-on.
However, under certain circumstances, you can also stay with the previous, non-configurable approach. You may
want to stay with the previous approach for the following reasons:
• The default processing works out of the box for you. You don't have the requirement to change the default
relationships or add new relationships.
• You've implemented the Enhancements for Adapting Employee Organizational Assignment BAdI or the
Enhancements for Adapting Employee Organizational Assignment Request BAdI to adapt the configuration
to your requirements and want to retain this implementation.
• You don't create the position relationships in SAP S∕4HANA based on the replication of organizational
assignments. Instead, you use the generic replication of organizational objects and replicate the organizational
objects together with their associations from Employee Central. This means that the position relationships in
SAP S∕4HANA are created based on Employee Central Position Management.
We provide sample content for the configuration, which you can copy and adapt to your needs. If you want to use
the sample content, the template group must have the Employee Data EC to ERP: Replication (EE_WS_3) sample
content assigned.
Procedure
1. Go to Customizing for the Business Integration Builder and choose Data Replication from Employee Central
Employee Data Employee Organizational Assignment Configurable Organizational Assignment Select
Position to Be Used for Relationship to Personnel Number .
In this customizing activity, you configure which Position field from the Job Information entity in Employee
Central is used to create the employee position relationship in SAP S∕4HANA.
 Note
You can use only one Position field from Employee Central in the configuration. Either the standard Position
field or a custom field. You can't configure multiple Position fields.
(ECS4HCM) PUBLIC 47
As soon as you've made one entry in this customizing activity, the SAP S∕4HANA system no longer
uses the non-configurable approach for the corresponding transformation template group. This has the
following effects:
• The system no longer calls any implementations of the BAdIs Enhancements for Adapting
Employee Organizational Assignment (EX_SFIOM_ADAPT_EE_ORG_ASSGNMNT) and Enhancements
for Adapting Employee Organizational Assignment Request (EX_SFIOM_ADAPT_EE_ORG_ASS_REQ).
• The system ignores the following constants in the customizing activity Maintain Constant Values for
Data Replication from EC:
• EC to ERP: Omit Position-Job Rel. in Non-Config. Org Assignm
• EC to ERP: Omit Pos.-Cost C. Rel. in Non-Config. Org Assignm
• EC to ERP: Omit Pos.-Org Unit Rel. in Non-Config. OrgAssignm
• EC to ERP: Omit Pos.-Manager Rel. in Non-Config. Org Assignm
If you want to exclude position relationships from the replication of organizational assignments (in
particular, if you've configured the replication of organizational objects to create the relationships),
simply don't configure them in the customizing activities Define Relationship Mapping for Position or
Define Job Relationship Mapping for Position.
2. Go to the next customizing activity, Define Relationship Mapping for Position.
In this customizing activity, you map Employee Central fields to create appropriate position relationships in
SAP S∕4HANA:
• position to organizational unit (S-O)
• position to job (S-C)
• position to cost center (S-K)
• position to position (S-S)
You can also define priorities in case multiple Employee Central fields are mapped to the same relationship.
 Example
You map the Employee Central fields Department, Division, and Business Unit to the SAP S∕4HANA
relationship of the position to the organizational unit, to reflect the organizational hierarchy from Employee
Central in the SAP S∕4HANA system. When Employee Central transfers all three assignments for an
employee, you want to create the position to organizational unit relationship in the SAP S∕4HANA system
based on the assigned department. If no department assignment is transferred, you want to create the
position to organizational unit relationship based on the assigned division, and so on.
You can fill the fields Weighting Percentage (PROZT) and Priority (PRIOX) of the corresponding relationship in
SAP S∕4HANA from the desired Employee Central fields.
And you can map Employee Central fields to any other SAP S∕4HANA relationships that have the source field
Position.
3. Go to the next customizing activity, Define Job Relationship Mapping for Position.
In this customizing activity, you create the relationship of a position to another position in SAP S∕4HANA
based on the employee's job relationships in Employee Central. You can create, for example, an employee to
matrix manager or an employee to HR manager relationship to reflect the corresponding job relationships from
Employee Central in the SAP S∕4HANA system.
You can also fill the fields Weighting Percentage and Priority of these relationships from the desired Employee
Central fields.
48 PUBLIC (ECS4HCM)
Related Information
Reflecting Job Information and Job Relationships from Employee Central in the SAP S∕4HANA System
2.4.12 Replacing Object-Specific with Generic Replication and

Processing of Organizational Objects
Configure the replication of organizational objects in the Business Integration Builder (BIB) in the SFSF EC S4 HCM
INTEGRATION (ECS4HCM) add-on after the upgrade.
Context
If you've still used object-specific replication and processing for the standard objects (departments, divisions,
business areas, job classifications, and positions) in the SFSF EC INTEGRATION (PA_SE_IN) add-on, you must now
switch them to generic replication and processing.
 Note
Even if you used object-specific processing in the SFSF EC INTEGRATION (PA_SE_IN) add-on, you may have
already added organizational objects to the replication and made customizing settings for them in BIB. These
settings remain unchanged.
Procedure
Organizational Objects .
2. Go through the customizing activities in this section and make the settings that are relevant for your use case
of replicating organizational objects from Employee Central.
3. Use the field mapping in the Define Field Mapping for Organizational Data customizing activity to replace
your implementation of the Business Add-Ins (BAdIs) Enhancements for Processing Customer-Specific
Fields (EX_SFIOM_PROC_CUSTOMER_FIELDS) or Enhancements for Processing Country Specific Fields
(EX_SFIOM_PROC_COUNTRY_FIELDS) if you've created one.
4. Use conditional mapping and generic value conversion in the same customizing activity to replace
your implementation of the Enhancements for Setting the Parent of Organizational Structure Items
(EX_SFIOM_SET_PARENT) BAdI if you've created one.
(ECS4HCM) PUBLIC 49
Related Information
Replication of Organizational Objects from Employee Central
Configuring Primary Field Mapping for Organizational Object Replication from Employee Central
Configuring Conditional Mapping for Organizational Object Replication from Employee Central
Formatting Organizational Object Fields Replicated from Employee Central Using Value Conversion
2.4.13 Moving Full Transmission Start Date for

Organizational Object Replication from Query Program
to Transformation Template Group
Remove the full transmission start date (FTSD) for the replication of organizational objects from Employee Central
from the query program and add it in the transformation template group.
Context
In the SFSF EC INTEGRATION (PA_SE_IN) add-on, you entered the FTSD on the selection screen of the Create and
Execute Organizational Object Replication Query (RH_SFIOM_ORG_OBJ_REPL_QUERY) program. We've removed the
Full Transmission Start Date field from the selection screen of the program in the SFSF EC S4 HCM INTEGRATION
(ECS4HCM) add-on. You now enter the FTSD in the Earliest Transfer Date field for the transformation template
group that you use for organizational object replication.
Procedure
1. Go to the ABAP: Program Execution (SA38) transaction in your SAP S∕4HANA system.
2. Enter RH_SFIOM_ORG_OBJ_REPL_QUERY and choose Goto Variants .

3. Select your variant and choose Display.
4. Check the date stored in the Full Transmission Start Date field.
Organizational Objects Field Mapping for Organizational Object Replication from Employee Central Define
Transformation Template Group for Organizational Data .
6. Select the transformation template group that you use for replication of organizational objects from Employee
Central and choose Details.
7. Enter the FTSD stored in your program variant in the Earliest Transfer Date field.
8. Go back to the ABAP: Program Execution transaction.
9. Delete your program variant for the query program and create a new program variant without FTSD.
50 PUBLIC (ECS4HCM)
Related Information
Full Transmission Start Date for Organizational Object Replication Defined in Transformation Template Group [page
23]
2.4.14 Removing Records with Replication Content Type

Employee Organizational Assignment from the Data
Replication Monitor
After the upgrade to the SFSF EC S4 HCM INTEGRATION (ECS4HCM) add-on, manually delete data records with
replication content type Employee Organizational Assignment from the Data Replication Monitor as soon as you no
longer need them.
Context
The Employee Central Data Replication Monitor only uses the Employee Master Data replication content type to
report the status of the replication of employee data (including organizational assignments) from Employee Central
to SAP S∕4HANA. The Employee Organizational Assignment replication content type is no longer used.
 Caution
The updates in the Employee Central Data Replication Monitor will only be available after your SAP
SuccessFactors instance has been upgraded to the 2H 2022 release.
Procedure
1. Sign in to SAP SuccessFactors Employee Central.

2. Go to the Admin Center and choose the Data Replication Monitor admin tool.
3. Select all records with the replication content type Employee Organizational Assignment.
4. Check whether you still need one or more of these records, for example, because you haven't yet corrected the
relevant errors and want to display the corresponding error messages.
5. Delete all records with the replication content type Employee Organizational Assignment that you no longer
need.
Related Information
New Status Added and Replication Content Type Removed in the Data Replication Monitor [page 23]
(ECS4HCM) PUBLIC 51
2.4.15 Upgrading to Point-to-Point Time Data Replication
Switch to point-to-point time data replication for the SFSF EC S4 HCM INTEGRATION add-on if you've been
using middleware-based replication of employee time data from Employee Central in the SFSF EC INTEGRATION
(PA_SE_IN) add-on.
Context
Replication.
Procedure
1. Sign in to your SAP S∕4HANA system after the upgrade.

2. Go to the SOA Management (SOAMANAGER) transaction and disable the Web Service
EmployeeTimeECToERPRequest_In.
3. Sign in to the SAP Cloud Integration web UI if you've used the SAP Cloud Integration version of employee time
data replication.
4. Undeploy the integration flows Replicate Time Off Data from SAP SuccessFactors Employee Central to SAP ERP
and Replicate Time Sheet Data from SAP SuccessFactors Employee Central to SAP ERP.
5. Sign in to Boomi AtomSphere if you've used the Boomi version of employee time data replication.
6. Undeploy the processes Packaged Integration: SuccessFactors Employee Central to ERP - Absence Data
Replication and Packaged Integration: SuccessFactors Employee Central to ERP - Time Pay Component
Replication.
7. Go to the Switch Framework: Display Business Function Status (SFW5) transaction in your SAP S∕4HANA
system.
8. Activate the business function HCM_SFEC_TDEC2HR (HCM, Time Data Replication Employee Central to HR
(Reversible)).
9. Sign in to SAP SuccessFactors Provisioning and make sure that Enable Payroll Integration is enabled and
Enable Employee Central Payroll is disabled.
 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.
10. Configure the communication as described in Set up Connection Between an SAP Payroll System and
Employee Central in the guide Implementing Point-to-Point Time Data Replication.
11. If you used the non-BIB employee key mapping in the SFSF EC INTEGRATION (PA_SE_IN) add-on, go to the
Convert Employee Key Mapping from Non-BIB to BIB-Based Version (ECPAO_CONV_EEKEYMAP) transaction
52 PUBLIC (ECS4HCM)
in your SAP S∕4HANA system to migrate the key mapping from the PAOCFEC_EEKEYMAP table to the
ECPAO_EE_KMAP table.
12. Go to the Time Replication: Migrate Application Tables (HRSFEC_TIMREPL_A2S_A) transaction to migrate the
content of the following tables.
Table Used in Middleware-Based Rep Table Used in Point-to-Point Replica

Purpose lication tion
Reference key mapping PAOCFEC_REFMAP HRSFEC_D_REFMAP
Linking index for employee time groups ECTIM_LINK_INDEX HRSFEC_LINK_IDX
We recommend that you select All Countries/Regions on the initial screen of the transaction.
13. Go to the Time Replication: Migrate IMG Tables (HRSFEC_TIMREPL_A2S_C) transaction to migrate the content
of the following tables.

Customer-specific code value mapping PAOCFEC_MAP_CC T77SFEC_CVMAPC
Code value mapping properties PAOCFEC_LIST_ID, PAOC T77SFEC_CVPROPS and

FEC_MAP_MOD, PAOC T77SFEC_CVPROPC
FEC_MAP_MODC
Results
After you've successfully completed the upgrade, you can start using the following transactions in your SAP
S∕4HANA to replicate time data from Employee Central:
• Replication of Absence Data (HRSFEC_PTP_ABSE_REPL) for time off data

• Replication of Time Pay Component Data (HRSFEC_PTP_ATTE_REPL) for time sheet data
Next Steps
Point-to-point time data replication uses the same customizing settings that were used by middleware-based
replication of employee time data from Employee Central in the SFSF EC INTEGRATION (PA_SE_IN) add-on.
Therefore, you don't need to change your customizing settings. However, in addition to the listed upgrade steps,
consider country/region-specific requirements if you made country/region-specific settings for the middleware-
based replication.
(ECS4HCM) PUBLIC 53
2.4.16 Converting the Dependent Mapping Data
After the upgrade, you might have to use the dependents migration report to migrate the data from dependent old
key mapping table to the current key mapping table.
Context
If you were using the Non-BIB solution for replicating the employees from Employee Central
before using the BIB (PA_SE_IN) solution, then you need to use the dependents migration report
ECPAO_CONV_DEPNDT_TO_OBJPS_MAP (ECPAO_CONV_DEPENDENT transaction code) to migrate the data from
dependent old key mapping table to the current key mapping table. Without performing this step, you would face
issues when you are migrating the data which has a dependent data.
Procedure
1. Enter the specific Personnel Number.
 Note
If you do not enter any personnel number, then the report would consider the entire data present in the
table.
2. Specify if you want to carry out a test run. If you run this program in the test mode by selecting the Test Run
checkbox, then the data will not be updated in the database table.
Results
In the result screen, the data would be displayed in an ALV grid format.
54 PUBLIC (ECS4HCM)
3 Upgrade from SFSF EC INTEGRATION
(PA_SE_IN) Non-BIB to SFSF EC S4 HCM
INTEGRATION (ECS4HCM)
You are using Non-BIB framework in PA_SE_IN add-on for the replication and you are planning to upgrade to
ECS4HCM add-on.
You have two different approach to upgrade the add-on to the new ECS4HCM add-on:
• Upgrading from SFSF EC INTEGRATION (PA_SE_IN) Non-BIB to SFSF EC S4 HCM INTEGRATION (ECS4HCM)
(Direct Move from SFSF EC INTEGRATION (PA_SE_IN) Non-BIB to SFSF EC S4 HCM INTEGRATION
(ECS4HCM)) and configure the BIB.
• Upgrading from SFSF EC INTEGRATION (PA_SE_IN) Non-BIB to SFSF EC INTEGRATION (PA_SE_IN) on BIB
and then upgrading to SFSF EC S4 HCM INTEGRATION (ECS4HCM).
Non-BIB Employee Master Data Compared to BIB Employee Master Data Replication [page 55]
You might have to understand the differences between the both integration solutions before you start the
upgrade process.
Direct Move from SFSF EC INTEGRATION (PA_SE_IN) Non-BIB to SFSF EC S4 HCM INTEGRATION (ECS4HCM)
[page 65]
How to upgrade if you are using the SAP ERP HCM or SAP S/4HANA system with the PA_SE_IN add-on
(non-BIB) and would like to directly migrate to SAP S/4HANA using the ECS4HCM add-on.
Move from SFSF EC INTEGRATION (PA_SE_IN) Non-BIB via SFSF EC INTEGRATION (PA_SE_IN) on BIB to
SFSF EC S4 HCM INTEGRATION (ECS4HCM) [page 84]
How to upgrade if you are using the SAP ERP HCM or SAP S/4HANA system with the PA_SE_IN add-on
(non-BIB) and would like to migrate to the BIB-based PA_SE_IN add-on first. In a second step, you then
migrate to SAP S/4HANA using the ECS4HCM add-on.
3.1 Non-BIB Employee Master Data Compared to BIB

Employee Master Data Replication
You might have to understand the differences between the both integration solutions before you start the upgrade
process.
Before you start migrating your Non-BIB solution it is helpful to understand the differences between both
integration solutions. This will help during your preparation phase to plan necessary steps you have to do before
you upgrade to the Employee Master data and Organizational Assignment replication based on BIB ECS4HCM
AddOn.
• Additional Features in Business Integration Builder (BIB) chapter consist of an overview of additional features
that we provide as standard capability in our BIB based replication solution.
Additional Features in Business Integration Builder (BIB) [page 56]
• Feature parity between both solutions based on improved approaches and concepts:
Upgrade from SFSF EC INTEGRATION (PA_SE_IN) Non-BIB to SFSF EC S4 HCM
INTEGRATION (ECS4HCM) PUBLIC 55
• General differences & Extensibility
You will get an overview of general features and details on different concepts and approaches the feature
was realized and in addition you will get an overview on BAdI options we offer in Non-BIB compared to BIB.
What's Different in Non-BIB and BIB [page 58]
• Infotype handling:
You will get an insight into different handling of infotypes during the replication processing.
How Infotypes are Handled in Non-BIB and BIB [page 62]
Additional Features in Business Integration Builder (BIB) [page 56]

Here is an overview of features we offer only in our Employee Master Data and Organizational Assignment
Replication solution based on BIB.

Get an overview of the differences that we have between the Non-BIB and BIB based integration solution.
How Infotypes are Handled in Non-BIB and BIB [page 62]

Understand how infotype are handled differently in Non-BIB and BIB
3.1.1 Additional Features in Business Integration Builder (BIB)
Here is an overview of features we offer only in our Employee Master Data and Organizational Assignment
Replication solution based on BIB.
The overview gives an insight into major feature we delivered already. For new features in our Employee Master
data and Organizational Assignment replication based on BIB in ECS4HCM see What's Different in the ECS4HCM
Add-On Compared to the BIB-Based PA_SE_IN Add-On topic.
Additional Features in BIB ECS4HCM Short Description
Support replicating EC employee data to additional infotypes. You can configure the field mapping and value mapping re
quired between an additional EC entity and infotype. You can
find the standard delivered infotypes in the sample content.
Support Move of hire date. If the hire date of an employment has been changed and the
new hire date is replicated to the SAP S∕4HANA system, then
the replication supports a move of hire date in Employee Cen
tral:
• to a past date.
• to a future date only if the payroll for such an employee
has not yet run.
Replicating rehired employees on same employments whose You can replicate the updated or newly added email communi
email address was purged in the SAP ERP system. cation data of the rehired employments from SAP SuccessFac
tors Employee Central to SAP ERP whose SAP ERP communi
cation data has been (partially) purged in SAP ERP.
Allow which employment you want to be replicated during pay You can specify payroll areas for which you want to allow or not
roll correction phase based on the specified payroll areas allow data replication from Employee Central when they are in
correction phase. You can specify payroll areas and exceptions.
56 PUBLIC INTEGRATION (ECS4HCM)
Decide how two Employee Central event reason resulting in two You can decide how the replication would react when two
employment status changing ERP actions with the same start
Employee Central event reason result in two employment sta
data would be treated in SAP S4HANA.
tus-changing actions with the same start date for the same
personnel number in SAP S4HANA.
You can specify how the system would react for each unique
sequence of status-changing event reasons replicated from
Employee Central.
Support replicating Assignment ID External You can use the Employee Central field Assignment ID (assign
ment ID external) for the purpose of a Core Hybrid integration
scenario in line with the SAP S∕4HANA personnel number
(PERNR) format across all systems. The SAP S∕4HANA per
sonnel number is stored in the Employee Central employment
field Assignment ID during data migration (SAP ERP data mi
gration to SAP SAP SuccessFactors Employee Central).
A new Assignment ID/PERNR will be created after the com

plete data migration to the SAP SuccessFactors Employee
Central system. During the replication of the newly created
employments (for example, new hires) in Employee Central,
an 8-digit assignment ID is generated in Employee Central
through specified business rules. In the Employee Central to
ERP replication the assignment ID is transferred to the ERP
system and used as a personnel number for new hires.
Support replicating employees who have partially purged EC Employees with partially purged EC entity data are considered
entity data per standard in the replication and BIB now uses the purge
status overview as default.
Replication of no-shows from Employee Central When you enable reporting of new hires as no-shows in Em
ployee Central, this information is transferred to SAP S∕4HANA
system. By this, you can store the information that a new hire
was reported as no-show also in your SAP S∕4HANA system to
avoid problems for follow-on HR processes as well as payroll.
Support standard sample content for replicating contractual We have introduced sample content in Business Integration
data to Infotype Contract Element (IT0016) Builder (BIB) to replicate contractual employee data (IT0016)
from Employee Central to SAP S∕4HANA for 13 countries Ar
gentina, Australia, Brazil, Canada, Chile, Colombia, Italy, Mex
ico, Netherlands, Saudi Arabia, Singapore, Great Britain, and
United States.
Support replicating localized biographical information for 5 Employee Central offers in the biographical information block
countries the option to maintain country-specific Region of Birth and
Place of birth fields for 5 countries Brazil, Chile, France, Italy,
and Venezuela. We support replicating the country-specific
information to SAP S4HANA Infotype personnel information
(IT0002) for the 5 countries.
Support 3rd gender for additional countries You can now replicate 3rd gender for India, Germany, US, Aus
tria, and Canada. If you require replicating a 3rd gender for
further countries because you use in Employee Central a coun
try-specific gender for further countries, then you can easily
configure the mapping. Prerequisite is that the corresponding
country/region-specific gender field for the country and pick
list are available in Employee Central.
Support replicating multiple compensation events on the same Customer with subsidiaries in Brazil can now replicate multiple
day to Infotype IT0008 for country Brazil compensation events at the same day to IT0008 subtype 0
and subtype BR01.
Support replicating Indian income tax declaration for country Support replicating Indian income tax declaration data from
India Employee Central to:
• Section 80 Deductions - IT0585

• Section 80 C Deductions - IT0586
• Housing (HRA/CLA/COA) - IT0581 (Rented Accommo
dation type only) fields from Employee Central to SAP
S4HANA.
Please check if you might have already implemented a custom solution in your Non-BIB solution to cover the above
mentioned features. If yes, please plan to replace the custom solution with a corresponding standard BIB feature
during your post-upgrade phase.
If you would like to explore details, please refer to the Implementing Data Replication from Employee Central guide.
Related Information
What's Different in the ECS4HCM Add-On Compared to the BIB-Based PA_SE_IN Add-On [page 8]
Implementing Data Replication from Employee Central guide
3.1.2 What's Different in Non-BIB and BIB
Get an overview of the differences that we have between the Non-BIB and BIB based integration solution.
In our Non-BIB based integration compared to the BIB based integration different concepts and common
approaches are used to cover the same general feature. Following table gives an overview on general features
and how the feature was covered in Non-BIB compared to BIB.
General Differences
Feature Non-BIB BIB
SAP pre-deliver a subset of Field & Value The field mappings and field value Pre-defined field mappings and value
sample mapping between EC entity fields mappings based on BIB is delivered as
(standard code value lists) mappings
and SAP ERP infotype fields for most sample content. You can use our sample
are delivered as a static mapping (Serv
common infotypes and use cases includ content template and apply the sample
ing value conversion rules for fields. ice EmployeeMasterDateReplicationRe content for the Employee Central to ERP
quest_IN) employee data replicating directly in the
BIB configuration tool.
Provide options to adjust the field and You use BAdI In BIB you can use the BIB standard con
value mapping. For example, to enable EX_PAOC_EC_CHANGE_INFOTYE_DA to figuration tools to map Employee Central
transferring Employee Central customer- implement the mapping required for fields to infotype fields. You can also con
specific field values to required SAP additional fields such as customer-spe figure a specific value mapping and value
S4HANA infotype fields. cific fields. You use custom fields in Em conversion rule if needed. BIB allows you
ployee Central and you have configured to also configure mappings to secondary
infotypes and change mapping to cover
in IMG activity Define Extensibility of Field
mapping (PAOCFEC_V_EXTMAP) user-de country-specific needs. BIB supports
fined fields in Employee Central to fields replicating further infotypes provided the
of infotypes in SAP S4HANA. required processing logic matches a rep
lication logic pattern we already provide
for an infotype of our sample content.
Determination of start date of infotypes How the start date is determined is info Default behaviour for the 3 mapping sce
type specific. See Infotype specific han narios:
dling for details.
• Non-effective dated EC entity map
ped 1:1 to one SAP S4HANA info
type. Start date is set as default al
ways with the hire/rehire date of the
last employment. Beside the default
approach, you have the option to
choose also the last_modified date
or a custom date or the payroll pe
riod start date.
• Effective dated EC entity mapped 1:1
to one SAP S4HANA infotype. Start
date is set as default with the effec-
tive date of the EC entity transferred
from Employee Central.
• Mix between non-effective dated
and effective dated EC entities map
ped to one SAP S4HANA infotype.
Start date is set as default with the
effective date of the EC entity trans
ferred from Employee Central.
 Note
Exceptions are described in info
type-specific handling.
Feature Non-BIB BIB
Control for which employee & employ You would like to avoid for some em You would like to avoid for some employ
ment as of when data shall be considered ployees replicating data and changes ees replicating data and changes valid af
in the replication by using the assign valid after the FTSD and before a spe ter the FTSD and before a specific date
ment-specific FTSD. As a result changes cific date greater than FTSD. For that greater than FTSD. For that purpose, you
valid after the FTSD and before the purpose, you can use the Assignment- can use the assignment-specific FTSD. In
assignment-specific date greater than specific FTSD. You can use the BAdI BIB we provide a maintenance view that
FTSD are not replicated. EX_PAOCF_EC_DECIDE_HIRE_REHIRE allows you to specify employees and an
for the purpose. assignment-specific FTSD.
Infotype filters capability allows to spec In the Non-BIB Filter infotype customiz BIB customizing activity Define Filtering
ify which infotypes and subtypes per ing activity you can specify which info of Infotypes and subtypes for EC allows
country shall be considered during repli type and subtype per country you would to define infotypes and subtypes, which
cation like to consider in the replication. If you should be ignored during the replication
do not specify any infotype/subtypes process at country grouping level based
then automatically all are considered in on a workforce.
the replication processing.
 Note
Per standard IT0000, 0001, 0002,
0003, and 0709 are always repli
cated.
Extensibility Options
Feature Non-BIB BIB
You change infotype data that has been You use BAdI You can use BAdI
replicated to SAP S4HANA EX_PAOC_EC_CHANGE_INFOTYE_DA to ECPAO_IN_EXT_PROCESS_INFOTYPE to
change infotype data. change infotype data.
You decide if a newly hired employee You use BAdI In Employee Central an employee must
in Employee Central shall be hired or re- EX_PAOCF_EC_DECIDE_HIRE_REHIRE have a hire record as the first job in
hired in SAP S4HANA. to decide if a newly hired employee in formation record. Hence, we are rec
Employee Central shall be hired or re- ommending migrating the historical em
hired. For that purpose additional manual ployee contracts from SAP S4HANA to
changes related to Employee Central job Employee Central by using the place
information events/event reasons are re holder concept. As a result, the deci
quired. sion if the employee shall be hired or re-
hired is made in Employee Central. If you
have not used the placeholder concept a
new personnel number is created in SAP
S4HANA.
You can replicate cost centers and cus You use BAdI You can use the standard BIB configura-
tomer specific cost objects such as in EX_PAOCF_EC_DETERM_COST_OBJECT tion to specify the corresponding field
ternal orders, WBS elements from Em to replicate cost objects from Employee mappings.
ployee Central. Central to SAP S4HANA
You exclude subtypes from deletion dur You use BAdI In BIB only subtypes who have an exist
ing replication. EX_PAOCF_EC_EXCLUDE_FROM_DELET ing field mapping (Transformation tem
to exclude subtypes from deletion if the plate group) are considered during the
subtypes are directly maintained in SAP replication.
S4HANA.
Feature Non-BIB BIB
You extend the mappings needed for ad You use BAdI You can use the standard BIB configura-
ditional fields in Infotype Family Mem EX_PAOCF_EC_EXTEND_FMAP_IT0021 tion to specify the corresponding field
ber/Dependent (IT0021) to specify the mappings for additional mappings.
field to IT0021
You define which Employee Central ID You use BAdI You can use BAdI
field you would like to map to the SAP EX_PAOCF_EC_EXT_PERNR_MAP to ECPAO_IN_EXT_PERNR_MAP to define
S4HANA personnel number. specify which Employee Central field the personnel number (PERNR) for a
shall be used to determine the personnel combination of user ID and country
number. grouping. The BAdI is called only if no key
mapping entry is stored for this user ID
and country grouping in the key mapping
table ECPAO_EE_KMAP. That is, if a new
hire is transferred from Employee Cen
tral, meaning that the personnel number
doesn’t exist yet in the SAP S4HANA sys
tem
You define which Employee Central ID You use BAdI You can use BAdI
field you would like to map to the SAP EX_PAOCF_EC_MAP_EXTERNAL_CP to ECPAO_IN_EXT_PERNR_MAP to define
S4HANA Central person (CP). specify the ID field that shall be used. the central person (CP) ID for a combina
tion of user ID and country grouping. The
BAdI is called only if no entry is stored for
this user ID and country grouping in the
key mapping table ECPAO_EE_KMAP.
You exclude personnel actions from be You use BAdI You can use BAdI
ing replicated to Infotype Additional Ac EX_PAOCF_EC_NO_MASSN_DELETION to ECPAO_IN_NO_MASS_DELETION for the
tion IT0302 because you need to main specify which personnel actions in info same purpose.
tain the personnel actions manually in type additional actions IT0302 shall be
SAP S4HANA and need to ensure they excluded from deletion during the rep
are not deleted by the replication. lication. This is required because they
were directly maintained in SAP S4HANA
and thus shall not be considered in the
replication processing.
You need to fill infotypes outside of the You use BAdI You can use the standard BIB configura-
standard set of infotypes for Employee EX_PAOCF_EC_PROCESS_EMPLOYEE to tion to specify corresponding field map
Central employee data. fill additional infotypes with employee pings.
data (EC person object) in the SAP
S4HANA backend system based on the
information passed-on in the inbound
message for employee master data repli
cation.
You need to fill infotypes outside of the You use BAdI You can use the standard BIB configura-
standard set of infotypes for Employee EX_PAOCF_EC_PROCESS_EMPLOYMENT tion to specify corresponding field map
Central employment data. to fill additional infotypes from employ pings.
ment data (EC employment object) in the
SAP S4HANA backend system based on
the information passed on in the inbound
message for employee master data repli
cation.
3.1.3 How Infotypes are Handled in Non-BIB and BIB
Understand how infotype are handled differently in Non-BIB and BIB
Feature Non-BIB BIB
Actions (IT0000) & Additional Actions (IT0302)
Standard mapping between EC event You use the standard static mapping You can use the flexibility of the BIB
types/event reasons to SAP ERP actions. between event types in Employee Cen configuration tool to map event types &
tral mapped to SAP ERP actions (field event reasons to SAP ERP actions (field
MASSN) MASSN).
Control which event types/event reasons You have specified in the IMG activity You can use the flexibility of the BIB
shall be considered during the replication Maintain the Employee Central Values for configuration to specify which fields and
process. Employee Central Fields event types and value should be considered in the replica
event reasons which are not relevant for tion by configuring a corresponding map
the replication. ping between fields and values.
You are enabled to control if you would You use a custom imple You can use the BIB standard customiz
like to prevent personnel actions in mentation by using BAdI ing activity Define Actions to be protected
IT0302 logged directly in SAP ERP from EX_PAOCF_EC_NO_MASSN_DELETION to that enables you to specify which addi
being overwritten by the employee data exclude personnel actions from deletion. tional action you would like to protect in
replication from SAP SuccessFactors SAP S/4HANA during replication of em
Employee Central. ployee data from Employee Central.
Organizational Assignment (IT0001)
Update IT0001 information in case an You have this use case and you have In BIB you can use IMG activity Maintain
organizational change happens by using specified an own default action in T77S0 Constant Values for Data Replication from
technical actions. switch YSFEC/YCHAT so that technically EC and choose a Fall-back action for this
an organizational change can be consid purpose to specify a default action.
ered. If no value was specified then ac
tion type '02' is used.
Replicating job and position information IT0001 fields like STELL/PLANS are filled If the PA-PD is switched off then you have
in case the PA-PD integration is switched based on the switch YSFEC/YJBPS in ta to specify in BIB the mapping of the Or
off. You do not use the integration be ble T77S0 since the PA-PD integration is ganizational fields that should be trans
tween SAP ERP Organizational Manage switched off. ferred. If no position information is trans
ment and SAP ERP Personnel adminis ferred then the default position is used.
tration.
Personal Data (IT0002)
Feature Non-BIB BIB
Determination of start date during hiring. During the first replication of a newly The start date determination follows the
hired employment the birth date of the common approach for mixed mapped EC
employee is used. To ensure that always entities to one infotype scenario thus the
a birth date value is transferred also if start date is determined by the effective
no Employee Central value exist it is pos date of the personal info EC entity.
sible to specify a default birth date in
the IMG activity Maintain the Constant  Example
Values (ECPAO CONSTANTS table). You
A newly hired employee who has a
have specified in the constant table value
first EC personal info record effective
4000, a default birth date that you use
date equal with the hire date result
in case no birth date is transferred. For
in a start date of IT0002 = effective
more information refer How Start Date
date = hire date.
of Infotypes from Non-Effective Dated
Employee Central Entities is Configured
topic in the Implementing Data Replica
tion from Employee Central guide.
Support of country specific secondary in You have implemented a mapping to You can use the standard BIB configura-
fotype data. secondary infotypes by using BAdI tion to specify in the transformation tem
EX_PAOCF_EC_CHANGE_Infotype_DA. plate a mapping to a secondary infotype.
Country-specific handling of fields The replication is based on the static You can use the EC localized biographical
Region of Birth and Country of Birth for mapping between the generic EC fields information for Italy, France, Venezuela,
Italy, France, Venezuela, Brazil and Chile and corresponding IT0002 fields. For Brazil, and Chile to Infotype 0002. In EC
to support legal requirements. Italy, France, Venezuela, Brazil, and Chile entity biographical information country-
a special logic to handle replicating coun specific fields Region of Birth and Place
try-specific region of birth data (GBLND, of Birth and picklists are available for
GBDEP, GBORT) to infotype 0002 is Brazil, Chile, France, Italy, and Venezuela.
available. You can replicate the country-specific in
formation to SAP S/4HANA infotype per
 Note sonnel information (IT0002).
Support of EC localized biographical

information for Italy, France, Vene
zuela, Brazil, and Chile requires a
BAdI implementation.
Replicating the National ID information. You replicate country-specific National You can use the standard BIB configu-
IDs to IT0002 for countries such as Can ration to map the National ID to the
ada, France, Spain, Sweden, UK, and US. corresponding IT0002 field and to coun
try-specific and/or secondary infotype
fields. It is also possible to replicate tem
porary National IDs to IT0002.
Address Data (IT0006)
Replicating EC address information to You can use our pre-delivered sample

You use our pre-delivered static stand
SAP ERP infotype address including lo content for address infotype subtype
ard address mapping to address in
calized mapping. fotype subtype Permanent residence
Permanent residence (1) Transformation
(1) and Mailing address (5). You use
Template WS_10. Mappings to further
also a mapping to further Time Con
subtypes can be added through BIB con
straint 2 address subtypes by usfiguration. It is possible to configure a
ing a BAdI implementation. (BAdI mapping not only for address subtypes
EX_PAOCF_EC_CHANGE_INFOTYPE_DA). of Time Constraint 2 but also for Time
Constraint 3 subtypes.
Feature Non-BIB BIB
Determination of address infotype start You use the standard logic for determin The infotype start date is evaluated
date for newly hired employees. ing the address infotype subtype perma based on the common start date de
nent residence start date. If the effective termination approach. For replicating ad
start date of the EC home address is be dress data this is the mapping scenario,
fore or equal to the hire date then the one effective dated EC entity mapped to
permanent residence address start date one infotype. As address infotype start
= hire date. date always the effective start date of the
Employee Central home address is used.
Replicating address information for You use the standard behaviour in Non- If you need to replicate a different ad
global assignments. BIB. If in Employee Central no host ad dress to the host PERNR then you have
dress is available then the Employee Cen to use host address type in Employee
tral home address is always replicated Central. Only then the host address is re
to both home and host SAP S/4HANA plicated to the host PERNR.
PERNR. If a host address is replicated
then the host address is replicated to the
host PERNR and the home address is re
plicated to the home PERNR.
Replicating foreign address information You use a BAdI implementation to In BIB you can configure a mapping to
to a localized address infotype/subtype cover replicating a foreign address
secondary infotype fields. BIB also sup
with a secondary infotype. with a secondary infotype. (BAdI ports the processing of foreign addresses
EX_PAOCF_EC_CHANGE_INFOTYPE_DA). with secondary infotypes.
Planned Working Time (IT0007)
Replicating working hour and working The Non-BIB replication supports the BIB supports the IT0007 replication
day information in EC Job information to WRKHR feature based on daily work based on the working hours mapped
SAP S/4HANA infotype Planned working ing hours ie D/X. Daily working hours from Employee Central and based on
time (IT0007) (ARBST) will be filled based on weekly the WRKHR feature. For example, if you
working hours/working days from Em maintain WRKHR feature as W/X, then
ployee Central. If the WRKHR feature you can map weekly working hours from
is maintained differently, then you need Employee Central to WOSTD and working
to implement an own solution by days to WKWDY.
using a BAdI implementation. (BAdI
EX_PAOCF_EC_CHANGE_INFOTYPE_DA).
Basic Pay (IT0008)
Replicating pay scale group and pay scale You have activated the standard mapping In BIB, we provide a standard mapping
level. to pay scale group and pay scale level for the pay scale group and pay scale
in IMG activity Switches for Employee level fields in our sample content. You
Replication Settings so that the corre can also configure the mapping to your
sponding Employee Central fields are re needs. If the pay scale group and level
plicated to the IT0008 pay scale group changes then the BIB logic enforces a
and pay scale level fields. recalculation of BIB fields BSGRD and
DIVGC using HCM framework logic.
Replicating pay components to IT0008 In Non-BIB processing the sequence is In BIB we are processing the wage-types
wage types. adjusted when the EC pay component based on how we receive the data from
and the wage type on the ERP database Employee Central.
are the same. Hence no update will be
triggered.
Date specification (IT0041)
Feature Non-BIB BIB
Mapping of date types. You use configuration option Assign date You can use the standard BIB field &
type to assign available static delivered value mapping configuration to map Em
date types to SAP S/4HANA IT0041 date ployee Central date types to IT0041 date
types. types.
Start date determination for dates in Replication creates time slices for IT0041 By default for non-effective dated EC En
case only date types of the non-effective according to rule choose the validity as tities, the hire/rehire date is used as start
dated employment info EC Entity is repli long as possible without affecting payroll date. The end date is the system high
cated. history - during inbound processing, start date (31.12.9999).
date of current pay period is determined
(or if the period is closed, the start date
of the next pay period) and this date is
taken as the begin date of the record to
be created. The end date is the system
high date (31.12.9999). If there are no
data changes, no record is created.
Replicating dates from job info and em If you replicate dates from job info and In BIB the time slices of the job info
ployment info and record split. employment info, then only one time- records get the preference, and the em
split is retained. ployment info dates are considered in
those time slices.
Cost Distribution (IT0027)
Replicating alternative wage/salary costs You use a BAdI implementation to cover You can use the standard BIB configura-
distributed to different cost center. the required additional field mapping of tion to set up the mapping of the cost
cost objects such as to an WBS element, object to corresponding T0027 fields. In
an internal order etc. BIB, you can also consider public sector
specific cost objects.
Communication (IT0105)
Start date determination when non-ef The start date is always the last modified The start date determination is in accord
fective EC entity contact information date for IT0105 subtype EMAIL. ance with the common BIB approach for
email mapped to IT0105 subtype email the mapping scenario one non-effective
are replicated. dated EC entity mapped to one SAP ERP
Infotype.
Replicating of EC user to IT0105 subtype You replicate a newly hired employees, You can use the BIB configuration to
ECUS. an Employee Central user, and info do the mapping between the EC user
type/subtype IT0105 ECUS containing to IT0105 subtype ECUS for example in
the EC User ID is created. WS_2 (Biographical info).
3.2 Direct Move from SFSF EC INTEGRATION (PA_SE_IN)

Non-BIB to SFSF EC S4 HCM INTEGRATION (ECS4HCM)
How to upgrade if you are using the SAP ERP HCM or SAP S/4HANA system with the PA_SE_IN add-on (non-BIB)
and would like to directly migrate to SAP S/4HANA using the ECS4HCM add-on.

What you should do in the SFSF EC INTEGRATION (PA_SE_IN) Non-BIB add-on before you start the
upgrade to SFSF EC S4 HCM INTEGRATION (ECS4HCM) add-on.


INTEGRATION (ECS4HCM) add-on from SFSF EC INTEGRATION (PA_SE_IN) Non-BIB.
3.2.1 Preparing the Upgrade
What you should do in the SFSF EC INTEGRATION (PA_SE_IN) Non-BIB add-on before you start the upgrade to
Read more about the points you need to consider when you plan to transition your Non-BIB Employee Master
data replication and Organizational Assignment replication solution in PA_SE_IN to the corresponding integration
solution based on BIB in ECS4HCM add-on.
Checking the Configurations in the SFSF EC INTEGRATION (PA_SE_IN) Non-BIB Add-on [page 66]
Before the upgrade to the SFSF EC S4 HCM INTEGRATION (ECS4HCM) add-on, check the configurations
available in the legacy system that will be deleted when you run the Legacy configuration overview report
(PAOCF_EC_EE_CONFIG_OVR).
Checking the BAdI Implementations [page 67]

There might be some BAdI implementations that might not be available after you upgrade to the SFSF EC
Checking the Non-BIB Extensibility Mapping [page 68]

Before the upgrade to the SFSF EC S4 HCM INTEGRATION (ECS4HCM) add-on, you need to check the
current extensibility configurations defined in the Employee Central Extensibility Mapping Configuration
view.
Setting the Full Transmission Start Date [page 68]

Understand how full transmission start date works in Non-BIB and BIB solution.
Replicating Employee Master Data and Organizational Assignment [page 69]

Before the upgrade to the SFSF EC S4 HCM INTEGRATION (ECS4HCM) add-on, make sure that the
employee master data and organization assignment replication is successful for all employees.
3.2.1.1 Checking the Configurations in the SFSF EC

INTEGRATION (PA_SE_IN) Non-BIB Add-on
Context
Before the upgrade to the SFSF EC S4 HCM INTEGRATION add-on, you can run the report
PAOCF_EC_EE_CONFIG_OVR to check the BAdI implementation status and the customizing table data in the
current PA_SE_IN Non-BIB solution. This report is available as part of the SP34 package of PA_SE_IN. If you are
using the older or lower version of the PA_SE_IN add-on, then you can apply the note 3246644 .
Procedure
Go to SE38 transaction or use the PAOCF_EC_EE_CONF_OVR transaction to run the report

PAOCF_EC_EE_CONFIG_OVR.
Results
The configuration overview report screen will show a detailed view of all the Non-BIB specific configurations.
3.2.1.2 Checking the BAdI Implementations
There might be some BAdI implementations that might not be available after you upgrade to the SFSF EC S4 HCM
INTEGRATION (ECS4HCM) add-on.
After the upgrade is completed, Non-BIB BAdI’s will not be available with the new solution. Hence you might
have to check the BAdI implementations and the same could be achived in the BIB solution by using the BIB
configurations or BIB BAdIs (Business Add Ins) after the upgrade. For more information refer to the Implementing
Data Replication from Employee Central guide.
 Example
If you have implemented any additional mapping to infotype or for any custom EC field mapping to infotype
using the EX_PAOCF_EC_CHANGE_INFOTYPE_DA BAdI, the same can be achieved by using BIB standard
configurations. For more information on the BAdI comparision, you can refer to BAdI Comparision topic.
Check the implicit enhancements added to your system. This will not be available after the upgrade to ECS4HCM.
You can check if the functionality can be achieved in standard BIB configurations.
Related Information
3.2.1.3 Checking the Non-BIB Extensibility Mapping
Before the upgrade to the SFSF EC S4 HCM INTEGRATION (ECS4HCM) add-on, you need to check the current
extensibility configurations defined in the Employee Central Extensibility Mapping Configuration view.
Context
The PAOCFEC_V_EXTMAP table stores the mapping details of the custom fields from Employee Central objects. You
can achieve the same via BIB mappings in the BIB system after the upgrade.
Procedure
Access the PAOCFEC_V_EXTMAP maintenance view. To access this view, go to the IMG structure and open
SAP Customizing Implementation Guide Personnel Management Integration with SuccessFactors Employee
Central Other Integration Settings Replicating Data from Employee Central to SAP ERP Extensibility Define
Extensibility of Field Mapping .
3.2.1.4 Setting the Full Transmission Start Date
Context
Deciding the full transmission start date (FTSD) helps you to move only the required data that you want to be
transferred from Employee Central to SAP S∕4HANA system. Handling of FTSD in Non-BIB and BIB solutions are
different. In the Non-BIB solution, there should be a record with the start date as FTSD date. We create a split on
FTSD in ERP database whereas in BIB, the split in ERP database will be created only if there is a data change on
FTSD. For more information, refer to Using the Full Transmission Start Date topic.
Procedure
Enter the full transmission start date you've chosen as the earliest transfer date of the transformation template
group you use for employee data replication.
Related Information
Using the Full Transmission Start Date
3.2.1.5 Replicating Employee Master Data and Organizational

Assignment
Before the upgrade to the SFSF EC S4 HCM INTEGRATION (ECS4HCM) add-on, make sure that the employee
master data and organization assignment replication is successful for all employees.
To ensure a clean transition between the Non-BIB to BIB solution, make sure the replications are successful for all
employees. So that the data is synchronized in the ERP system and there are no other open replications. So after
the upgrade, you can smoothly run the BIB based replication jobs.
3.2.2 Upgrade Steps
Context
Procedure
4HANA System Next .
3.2.3 Post-Upgrade Steps
(ECS4HCM) add-on from SFSF EC INTEGRATION (PA_SE_IN) Non-BIB.

Undeploy integration flows in SAP Cloud Integration and in Boomi AtomSphere that are no longer used in
Deciding on the Full Transmission Start Date [page 72]

After the system upgade before you prepare for integration between Employee Central and SAP S∕4HANA
by decide on the date when the data replication is to start.

Activating the Webservices for BIB Replication [page 75]

After the upgrade, you will have to setup the web services for the successful replication of employee master
data and organizational assignments from Employee Central to SAP S∕4HANA.

After the upgrade, delete all entries that still exist for obsolete constants from the Constants for Integration
with SuccessFactors (ECPAO_CONSTANTS) table in the SFSF EC S4 HCM INTEGRATION (ECS4HCM) add-
on.
Setting up the Middleware [page 76]

Set up SAP Cloud Integration as the middleware for the combined employee master data and
organizational assignment replication from SAP SuccessFactors Employee Central to SAP S∕4HANA.
Preparing the System [page 77]

Learn more about what needs to be in place if you want to replicate data from SAP S∕4HANA to Employee
Central after you upgrade the system.
Business Add-In (BAdI) Implementations [page 77]

You might have to transfer your Non-BIB implementations or the implicit enhancements to the ECS4HCM
BIB BAdIs based on your business requirement.
Determine that the new infotype framework is to be used in PA/PD integration for organizational data that
was replicated from Employee Central, to improve the performance and allow for better message handling
in the replication processes.
Start using the new staging area for employee data (including employee organizational assignments) in
the SFSF EC S4 HCM INTEGRATION (ECS4HCM) add-on that we introduced to decouple replication of the
employee data from processing of the data in the SAP S∕4HANA system.
Migrating the Employee Key Mapping [page 80]

You might have to migrate the key mapping table entries from non-BIB to new employee key mapping table
after the upgrade.
Migrating the Employee Key Mapping Table Entries from Dependents Key Mapping Table [page 80]
You might have to migrate the dependents key mapping table entries from legacy to new employee
dependents key mapping table after the upgrade.
Switch to point-to-point time data replication for the SFSF EC S4 HCM INTEGRATION add-on if you've
been using middleware-based replication of employee time data from Employee Central in the SFSF EC
INTEGRATION (PA_SE_IN) add-on.
Scheduling the Employee Replication Query Report [page 83]

After the upgrade you will have to schedule the employee replication query report as a background job.
3.2.3.1 Undeploying Obsolete Integration Flows
Undeploy integration flows in SAP Cloud Integration and in Boomi AtomSphere that are no longer used in the SFSF
EC S4 HCM INTEGRATION (ECS4HCM) add-on.
Context
integration versions that were still in use. The SFSF EC S4 HCM INTEGRATION (ECS4HCM) add-on uses SAP
Cloud Integration as the only middleware for replication of employee data (including organizational assignments)
and organizational objects from Employee Central. And it uses only the latest versions of the integration flows. All
other integration flows that were available for previous integration versions are obsolete.
Procedure
1. Sign in to the SAP Cloud Integration web UI.

2. Undeploy all integration flows that you used for data replication from Employee Central, except for the
following ones.
ERP or SAP S/4HANA: Employee and Organizational Data SAP SuccessFactors Employee Central to SAP ERP or SAP
S4HANA

3. Sign in to Boomi AtomSphere.

4. Undeploy all processes that you used for data replication from Employee Central.
3.2.3.2 Deciding on the Full Transmission Start Date
After the system upgade before you prepare for integration between Employee Central and SAP S∕4HANA by
decide on the date when the data replication is to start.
Context
Post upgrade, it is recommended that the FTSD is set to a future date (for example: go-live date). This is to ensure
that the infotype data which were replicated as part of Non-BIB replication remain untouched during replication
using BIB in ECS4HCM. For more information refer to this KBA 2332900
Procedure
1. Decide the date when the data replication from Employee Central to SAP S∕4HANA is to start.
2. Enter the full transmission start date you've chosen as the earliest transfer date of the transformation
template group that you use for employee data replication. For the replication of employee master data and
organizational objects, enter the date on the selection screen of the Create and Execute Organizational Object
Replication Query (RH_SFIOM_ORG_OBJ_REPL_QUERY) program.
3.2.3.3 Checking and Adjusting Authorization Roles
Context
the roles.

Planning) removed


PAO_RPRQ_EE removed




Planning) added


thorization added

tion added

added


removed

tion added

Response_In added
 Note
Procedure
3.2.3.4 Activating the Webservices for BIB Replication
After the upgrade, you will have to setup the web services for the successful replication of employee master data
and organizational assignments from Employee Central to SAP S∕4HANA.
Employee master data and org assignment replication from Employee Central uses the following web services:
• getEmployeeMasterDataAndOrgAssignmentBundleReplicationQuery_Out
This SAP S∕4HANA outbound service triggers data replication from Employee Central. It contains a query that
is based on the configuration you made in the SAP S∕4HANA system. The service first reaches the middleware,
which then triggers a Compound Employee API call to query the data from Employee Central.
The service has a ProcessingParameter node, which contains a list of the processing parameters you have
configured in SAP S∕4HANA.
• EmployeeMasterDataAndOrgAssignmentBundleReplicationRequest_In
This SAP S∕4HANA inbound service returns information back to the SAP S∕4HANA system. It either contains
the response, that is, the result of the query made to Employee Central in the Base64 XML format.
Or it contains a notification, that is, status information about the query, together with general, employee-
independent error information. Note that either the response or the notification are transferred, but not both
together.
The service also contains the time stamp of when the Compound Employee API started processing. This time
stamp is used to determine the last modified date for the next call.
The service also has a ProcessingParameter node, which contains a list of parameters from Employee Central.
You can use these parameters to further control the processing.
• EmployeeMasterDataReplicationConfirmation_Out
This SAP S∕4HANA outbound service updates the Employee Central Data Replication Monitor with information
about whether data transfer to the SAP S∕4HANA system was successful or not.
• If you use push replication: EmployeeMasterDataAndOrgAssignmentPushNotification_In
This SAP S∕4HANA inbound service tells the SAP S∕4HANA that a push event was carried out in Employee
Central that is relevant for the SAP S∕4HANA system. The notification contains the list of employees, that is,
a list of user IDs or external person IDs. It also contains the transformation template group to be used in SAP
S∕4HANA.
3.2.3.5 Deleting Constants That Are No Longer Required
After the upgrade, delete all entries that still exist for obsolete constants from the Constants for Integration with
SuccessFactors (ECPAO_CONSTANTS) table in the SFSF EC S4 HCM INTEGRATION (ECS4HCM) add-on.
Context
We removed some constants because they are no longer needed in the SFSF EC S4 HCM INTEGRATION add-on. If
you've made customizing settings for these constants in the PA_SE_IN add-on, there may still be entries for them
in the ECPAO_CONSTANTS, which are no longer required. Delete these entries after you've successfully completed
the upgrade.
 Note
You'll see the constant ID, but not the constant name of the obsolete constants.
Procedure
2. Delete all entries that still exist for the following constants.
0004 ERP to EC: Additional Event Records
0005 ERP to EC: Determine Personal Data of Global Employees
0006 ERP to EC: Set Inactive User Status w/ SAP Cloud Integra
tion
0010 ERP to EC/EC to ERP (BIB): Activate BIB for EC to ERP

Employ
3.2.3.6 Setting up the Middleware
Set up SAP Cloud Integration as the middleware for the combined employee master data and organizational
assignment replication from SAP SuccessFactors Employee Central to SAP S∕4HANA.
Related Information
Basic Steps in SAP Cloud Integration
3.2.3.7 Preparing the System
Learn more about what needs to be in place if you want to replicate data from SAP S∕4HANA to Employee Central
after you upgrade the system.
Here some of the configurations/settings that you need to perform after the upgrade:
• Accessing the customizing structure in the SAP S∕4HANA system

• Defining Your Employee Central Instance
• Importing Metadata from Employee Central
• Defining Value Mapping Entities
• Defining Custom Employee Central Entities for Employee Data Entities
• Defining Value Mappings
• Creating Transformation Template Group for Employee Data
• Copying the Sample Content
3.2.3.8 Business Add-In (BAdI) Implementations
You might have to transfer your Non-BIB implementations or the implicit enhancements to the ECS4HCM BIB
BAdIs based on your business requirement.
Below are the list of BAdIs which are offered in ECS4HCM.
BAdI Implementations Description
ECPAO_IN_FILTER_EMP_JOB_DATA For filtering employments or a whole employee.
ECPAO_IN_EXT_PERNR_MAP For defining the personnel number (PERNR) and the central
person (CP) ID for a combination of user ID and country group
ing.
ECPAO_IN_ASSIGNMENT_FTSD To set the full transmission start date (FTSD) for an assign
ment (a personnel number).
ECPAO_IN_EXT_PROCESS_INFOTYPE For modifying the payload data for an infotype.
3.2.3.9 Enabling Use of New Infotype Framework for
Integration Between Organizational Management and
Personnel Administration (PA/PD Integration)
Determine that the new infotype framework is to be used in PA/PD integration for organizational data that was
replicated from Employee Central, to improve the performance and allow for better message handling in the
replication processes.
Context
objects and organizational employee assignments from Employee Central.
 Note
Central anyway.
Procedure
1. Go to Customizing for the Business Integration Builder and choose Data Replication from Employee
Central Employee Data Employee Organizational Assignment Enable Use of New Infotype Framework
When Processing Replicated Org. Data or Data Replication from Employee Central Organizational
Objects Enable Use of New Infotype Framework When Processing Replicated Org. Data .
2. Check whether the following entry exists.
Group Sem.Abbr. Value Abbr. Description
PLOGI NITF X For example: Update Infotype

0001 Using New Infotype
Framework
3. Create the entry if it doesn't exist and transport the new entry.
Next Steps
If you use the non-configurable approach for the replication of organizational assignments from Employee Central,
you've possibly implemented a Business Add-In (BAdI) to enhance the replication. If you've done so, check
your implementation. Ensure that you use the classes provided for the new infotype framework in your BAdI
implementations to prevent runtime errors.
3.2.3.10 Getting Started with the New Employee Staging Area
Start using the new staging area for employee data (including employee organizational assignments) in the SFSF
EC S4 HCM INTEGRATION (ECS4HCM) add-on that we introduced to decouple replication of the employee data
from processing of the data in the SAP S∕4HANA system.
Context
The new staging area separates data replication from updating the data in the SAP S∕4HANA infotypes. You can
divide these tasks between different users. The processing user requires the authorization to edit personnel data.
The data replication user is a technical user and doesn't need to maintain any HR data. We provide template roles
that you can copy and use for this purpose.
Procedure
1. Adapt the authorizations of the technical and business users.
Technical users don't need any permissions to process HR data any longer. Business users for employee data
now also need the permissions required for organizational assignment replication.
2. Schedule a background job to regularly process employee replication requests.
3. Schedule a background job to regularly clean up the staging area for employee replication requests.
This background job deletes employee master data and organizational assignment requests that aren’t needed
anymore in your system.
4. Check the replication status in the Employee Central Data Replication Monitor.
5. Optional: Use the staging area viewer (transaction ECPAO_EE_VIEWER) to access the staging area for
employee replication requests in the SAP S∕4HANA system.
The staging area viewer is useful in the setup phase of the replication, for example, when errors occur more
frequently. You can analyze these errors, simulate the processing of replication requests for employee master
data, or process requests manually from the staging area viewer.
3.2.3.11 Migrating the Employee Key Mapping
You might have to migrate the key mapping table entries from non-BIB to new employee key mapping table after
the upgrade.
Context
Information stored in the non-BIB employee key mapping table PAOCFEC_EEKEYMAP needs to be
updated to the new BIB employee key mapping table ECPAO_EE_KMAP. You can do so by using the
ECPAO_CONV_EEKEYMAP_TO_EE_KMAP report.
Procedure
1. Go to transaction SE38.
2. Enter program: ECPAO_CONV_EEKEYMAP_TO_EE_KMAP.
3. Enter the external employee ID.
If you want to restrict the selection to the key mapping entries of a specific employee or employees, enter the
employee ID or IDs in the External Employee ID field. If you don't enter any IDs here, the program converts all
key mapping entries that exist in the PAOCFEC_EEKEYMAP table.
4. Choose if you want to ignore or overwrite the key mapping entries or show the details of the existing entries.
5. Choose Test Mode if you want to execute the report in test mode.
3.2.3.12 Migrating the Employee Key Mapping Table Entries

from Dependents Key Mapping Table
You might have to migrate the dependents key mapping table entries from legacy to new employee dependents key
mapping table after the upgrade.
Context
Information stored in the legacy employee dependents key mapping table PAOCFEC_KMAPDEPN needs to be
updated to the new BIB employee dependents key mapping table ECPAO_OBJPS_KMAP. You can do so by using
the ECPAO_CONV_DEPNDT_TO_OBJPS_MAP report (ECPAO_CONV_DEPENDENT transaction code).
Procedure
1. Go to transaction SE38.
2. Enter program: ECPAO_CONV_DEPNDT_TO_OBJPS_MAP.
3. Enter the Personnel Number for which you want to migrate the table data.
 Note
If you do not enter any PERNR number, then the entire table entries would be considered.
4. Choose Test Mode if you want to execute the report in test mode.
3.2.3.13 Upgrading to Point-to-Point Time Data Replication
Switch to point-to-point time data replication for the SFSF EC S4 HCM INTEGRATION add-on if you've been
using middleware-based replication of employee time data from Employee Central in the SFSF EC INTEGRATION
(PA_SE_IN) add-on.
Context
Replication.
Procedure
1. Sign in to your SAP S∕4HANA system after the upgrade.

2. Go to the SOA Management (SOAMANAGER) transaction and disable the Web Service
EmployeeTimeECToERPRequest_In.
3. Sign in to the SAP Cloud Integration web UI if you've used the SAP Cloud Integration version of employee time
data replication.
4. Undeploy the integration flows Replicate Time Off Data from SAP SuccessFactors Employee Central to SAP ERP
and Replicate Time Sheet Data from SAP SuccessFactors Employee Central to SAP ERP.
5. Sign in to Boomi AtomSphere if you've used the Boomi version of employee time data replication.
6. Undeploy the processes Packaged Integration: SuccessFactors Employee Central to ERP - Absence Data
Replication and Packaged Integration: SuccessFactors Employee Central to ERP - Time Pay Component
Replication.
7. Go to the Switch Framework: Display Business Function Status (SFW5) transaction in your SAP S∕4HANA
system.
8. Activate the business function HCM_SFEC_TDEC2HR (HCM, Time Data Replication Employee Central to HR
(Reversible)).
9. Sign in to SAP SuccessFactors Provisioning and make sure that Enable Payroll Integration is enabled and
Enable Employee Central Payroll is disabled.
 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.
10. Configure the communication as described in Set up Connection Between an SAP Payroll System and
Employee Central in the guide Implementing Point-to-Point Time Data Replication.
11. If you used the non-BIB employee key mapping in the SFSF EC INTEGRATION (PA_SE_IN) add-on, go to the
Convert Employee Key Mapping from Non-BIB to BIB-Based Version (ECPAO_CONV_EEKEYMAP) transaction
in your SAP S∕4HANA system to migrate the key mapping from the PAOCFEC_EEKEYMAP table to the
ECPAO_EE_KMAP table.
12. Go to the Time Replication: Migrate Application Tables (HRSFEC_TIMREPL_A2S_A) transaction to migrate the
content of the following tables.

Reference key mapping PAOCFEC_REFMAP HRSFEC_D_REFMAP
Linking index for employee time groups ECTIM_LINK_INDEX HRSFEC_LINK_IDX
13. Go to the Time Replication: Migrate IMG Tables (HRSFEC_TIMREPL_A2S_C) transaction to migrate the content
of the following tables.

Customer-specific code value mapping PAOCFEC_MAP_CC T77SFEC_CVMAPC
Code value mapping properties PAOCFEC_LIST_ID, PAOC T77SFEC_CVPROPS and

FEC_MAP_MOD, PAOC T77SFEC_CVPROPC
FEC_MAP_MODC
Results
After you've successfully completed the upgrade, you can start using the following transactions in your SAP
S∕4HANA to replicate time data from Employee Central:
• Replication of Absence Data (HRSFEC_PTP_ABSE_REPL) for time off data

• Replication of Time Pay Component Data (HRSFEC_PTP_ATTE_REPL) for time sheet data
Next Steps
Point-to-point time data replication uses the same customizing settings that were used by middleware-based
replication of employee time data from Employee Central in the SFSF EC INTEGRATION (PA_SE_IN) add-on.
Therefore, you don't need to change your customizing settings. However, in addition to the listed upgrade steps,
consider country/region-specific requirements if you made country/region-specific settings for the middleware-
based replication.
3.2.3.14 Scheduling the Employee Replication Query Report
Prerequisites
You've created a suitable variant if you want to adjust the selection criteria for the Create and Execute Employee
Master Data and Org. Assignment Query (ECPAO_EE_ORG_REPL_QUERY) program.
Context
Procedure
1. Go to the Define Job (SM36) transaction in your SAP S∕4HANA system.

2. Schedule the Create and Execute Employee Master Data and Org. Assignment Query program (or your program
variant) as a regular background job with the Date/Time start condition.
3. Select Periodic Job for the job to repeat.
For more information, refer to Scheduling Background Jobs in the SAP NetWeaver documentation.
Results
The program performs a full load when it is run for the first time. After the first data extraction, the time stamp of
the query is stored as the last modified date and the program switches over to delta replication. That is, the next
query uses the last modified date as a lower limit. Only records that have a newer time stamp are considered as
changed and are replicated.
With each run, the program updates the following administration tables:
• Administration of Employee Master Data and Org Assign. Query (ECPAO_QRY_ADM)

This table stores an entry for each run of the program, that is, for each query.
• Selection Parameters for EE Master Data and Org. Ass. Query (ECPAO_QRY_ADMDT)
This table stores the parameters you entered on the selection screen of the program.
With each run of the program, the system writes error, warning, and information messages to the application log.
3.3 Move from SFSF EC INTEGRATION (PA_SE_IN) Non-BIB

via SFSF EC INTEGRATION (PA_SE_IN) on BIB to SFSF EC
S4 HCM INTEGRATION (ECS4HCM)
How to upgrade if you are using the SAP ERP HCM or SAP S/4HANA system with the PA_SE_IN add-on (non-BIB)
and would like to migrate to the BIB-based PA_SE_IN add-on first. In a second step, you then migrate to SAP
S/4HANA using the ECS4HCM add-on.

What you should do in the SFSF EC INTEGRATION (PA_SE_IN) Non-BIB add-on before you start the
upgrade to SFSF EC S4 HCM INTEGRATION (ECS4HCM) add-on.


INTEGRATION (ECS4HCM) add-on from SFSF EC INTEGRATION (PA_SE_IN) Non-BIB and SFSF EC
INTEGRATION (PA_SE_IN) BIB.
3.3.1 Preparing the Upgrade
What you should do in the SFSF EC INTEGRATION (PA_SE_IN) Non-BIB add-on before you start the upgrade to
Read more about the points you need to consider when you plan to transition your Non-BIB Employee Master
data replication and Organizational Assignment replication solution in PA_SE_IN to the corresponding integration
solution based on BIB PA_SE_IN and then to BIB in ECS4HCM add-on.
Checking the Configurations in the SFSF EC INTEGRATION (PA_SE_IN) Non-BIB Add-on [page 85]
Configuring the BIB System [page 86]

Before the upgrade to the SFSF EC S4 HCM INTEGRATION (ECS4HCM) add-on, you would have to
configure the BIB system.
Checking the BAdI Implementations [page 86]

There might be some Non-BIB BAdI implementations that might not be available after you upgrade to the
Checking the Non-BIB Extensibility Mapping [page 87]

Before the upgrade to the SFSF EC S4 HCM INTEGRATION (ECS4HCM) add-on, you need to check the
current extensibility configurations defined in the Employee Central Extensibility Mapping Configuration
view.
Setting the Full Transmission Start Date [page 87]

Replicating Employee Master Data and Organizational Assignment [page 88]

Before the upgrade to the SFSF EC S4 HCM INTEGRATION (ECS4HCM) add-on, make sure that the
employee master data and organization assignment replication is successful for all employees.
3.3.1.1 Checking the Configurations in the SFSF EC

INTEGRATION (PA_SE_IN) Non-BIB Add-on
Context
Before the upgrade to the SFSF EC S4 HCM INTEGRATION add-on, you can run the report
PAOCF_EC_EE_CONFIG_OVR to check the BAdI implementation status and the customizing table data in the
current PA_SE_IN Non-BIB solution. This report is available as part of the SP34 package of PA_SE_IN. If you are
using the older or lower version of the PA_SE_IN add-on, then you can apply the note 3246644 .
Procedure
Go to SE38 transaction or use the PAOCF_EC_EE_CONF_OVR transaction to run the report

PAOCF_EC_EE_CONFIG_OVR.
Results
The configuration overview report screen will show a detailed view of all the Non-BIB specific configurations.
3.3.1.2 Configuring the BIB System
Before the upgrade to the SFSF EC S4 HCM INTEGRATION (ECS4HCM) add-on, you would have to configure the
BIB system.
There are some BIB configurations that you would have to do in the system once you upgrade from the Non-BIB
PA_SE_IN to the corresponding integration solution based on BIB PA_SE_IN.
There is change in the view cluster where it allows you to choose the transformation template group based on
the replication direction. This will ensure that you would be able to use the transformation templatefor either for
replication or migration of the data.
For more information on how to configure the settings in the BIB system, refer to the Replicating Employee Master
Data and Organizational Assignments from Employee Central to SAP ERP HCM guide.
Related Information
Replicating Employee Data from SAP ERP HCM to Employee Central Using SAP Cloud Integration as the
Middleware
3.3.1.3 Checking the BAdI Implementations
There might be some Non-BIB BAdI implementations that might not be available after you upgrade to the SFSF EC
After the upgrade is completed, Non-BIB BAdI’s will not be available with the new solution. Hence you might
have to check the BAdI implementations and the same could be achived in the BIB solution by using the BIB
configurations or BIB BAdIs (Business Add Ins) after the upgrade. For more information refer to the Implementing
Data Replication from Employee Central guide.
 Example
If you have used Non-BIB BAdI enhancement for custom field mappings, the same can be achieved via BIB field
mapping configuration. In case the same cannot achieved then go for the BIB BAdI implementation. For more
information on the BAdI comparision, you can refer to Extensibility Options section in the What's Different in
Non-BIB and BIB topic.
3.3.1.4 Checking the Non-BIB Extensibility Mapping
Before the upgrade to the SFSF EC S4 HCM INTEGRATION (ECS4HCM) add-on, you need to check the current
extensibility configurations defined in the Employee Central Extensibility Mapping Configuration view.
Context
The PAOCFEC_V_EXTMAP table stores the mapping details of the custom fields from Employee Central objects. You
can achieve the same via BIB mappings in the BIB system after the upgrade.
Procedure
Access the PAOCFEC_V_EXTMAP maintenance view. To access this view, go to the IMG structure and open
SAP Customizing Implementation Guide Personnel Management Integration with SuccessFactors Employee
Central Other Integration Settings Replicating Data from Employee Central to SAP ERP Extensibility Define
Extensibility of Field Mapping .
3.3.1.5 Setting the Full Transmission Start Date
Context
Deciding the full transmission start date (FTSD) helps you to move only the required data that you want to be
transferred from Employee Central to SAP S∕4HANA system. Handling of FTSD in Non-BIB and BIB solutions are
different. In the Non-BIB solution, there should be a record with the start date as FTSD date. We create a split on
FTSD in ERP database whereas in BIB, the split in ERP database will be created only if there is a data change on
FTSD. For more information, refer to Using the Full Transmission Start Date topic.
Procedure
Enter the full transmission start date you've chosen as the earliest transfer date of the transformation template
group you use for employee data replication.
3.3.1.6 Replicating Employee Master Data and Organizational
Assignment
Before the upgrade to the SFSF EC S4 HCM INTEGRATION (ECS4HCM) add-on, make sure that the employee
master data and organization assignment replication is successful for all employees.
To ensure a clean transition between the Non-BIB to BIB solution, make sure the replications are successful for all
employees. So that the data is synchronized in the ERP system and there are no other open replications. So after
the upgrade, you can smoothly run the BIB based replication jobs.
3.3.2 Upgrade Steps
Context
Procedure
4HANA System Next .
3.3.3 Post-Upgrade Steps
(ECS4HCM) add-on from SFSF EC INTEGRATION (PA_SE_IN) Non-BIB and SFSF EC INTEGRATION (PA_SE_IN)
BIB.
Setting up the Middleware [page 89]

Set up SAP Cloud Integration as the middleware for the combined employee master data and
organizational assignment replication from SAP SuccessFactors Employee Central to SAP S∕4HANA.

Business Add-In (BAdI) Implementations [page 92]

You might have to transfer your Non-BIB implementations or the implicit enhancements to the ECS4HCM
BIB BAdIs based on your business requirement.
Scheduling the Employee Replication Query Report [page 92]

3.3.3.1 Setting up the Middleware
Set up SAP Cloud Integration as the middleware for the combined employee master data and organizational
assignment replication from SAP SuccessFactors Employee Central to SAP S∕4HANA.
3.3.3.2 Checking and Adjusting Authorization Roles
Context
the roles.

Planning) removed


PAO_RPRQ_EE removed




Planning) added


thorization added

tion added

added


removed

tion added

Response_In added
 Note
Procedure
3.3.3.3 Business Add-In (BAdI) Implementations
You might have to transfer your Non-BIB implementations or the implicit enhancements to the ECS4HCM BIB
BAdIs based on your business requirement.
Below are the list of BAdIs which are offered in ECS4HCM.
BAdI Implementations Description
ECPAO_IN_FILTER_EMP_JOB_DATA For filtering employments or a whole employee.
ECPAO_IN_EXT_PERNR_MAP For defining the personnel number (PERNR) and the central
person (CP) ID for a combination of user ID and country group
ing.
ECPAO_IN_ASSIGNMENT_FTSD To set the full transmission start date (FTSD) for an assign
ment (a personnel number).
ECPAO_IN_EXT_PROCESS_INFOTYPE For modifying the payload data for an infotype.
3.3.3.4 Scheduling the Employee Replication Query Report
Prerequisites
You've created a suitable variant if you want to adjust the selection criteria for the Create and Execute Employee
Master Data and Org. Assignment Query (ECPAO_EE_ORG_REPL_QUERY) program.
Context
Procedure
1. Go to the Define Job (SM36) transaction in your SAP S∕4HANA system.

2. Schedule the Create and Execute Employee Master Data and Org. Assignment Query program (or your program
variant) as a regular background job with the Date/Time start condition.
3. Select Periodic Job for the job to repeat.
For more information, refer to Scheduling Background Jobs in the SAP NetWeaver documentation.
Results
The program performs a full load when it is run for the first time. After the first data extraction, the time stamp of
the query is stored as the last modified date and the program switches over to delta replication. That is, the next
query uses the last modified date as a lower limit. Only records that have a newer time stamp are considered as
changed and are replicated.
With each run, the program updates the following administration tables:
• Administration of Employee Master Data and Org Assign. Query (ECPAO_QRY_ADM)

This table stores an entry for each run of the program, that is, for each query.
• Selection Parameters for EE Master Data and Org. Ass. Query (ECPAO_QRY_ADMDT)
This table stores the parameters you entered on the selection screen of the program.
With each run of the program, the system writes error, warning, and information messages to the application log.
4 Change History
Learn about changes to the documentation for Upgrading from PA_SE_IN to ECS4HCM for Data Replication from
Employee Central in recent releases.
1H 2023
Type of Change Description More Info
New You can now initiate a full load di What's Different in the ECS4HCM
rectly from the selection screen of
Add-On Compared to the BIB-Based
the Create and Execute Employee
PA_SE_IN Add-On [page 8]
Master Data and Org. Assignment Query
(ECPAO_EE_ORG_REPL_QUERY) program. Initiating Full Load from Query Program
for Replication of Employee Data [page
18]
Added We added a note for the purge sta Purge Status Overview Option Is Now
tus overview option: If you grant Standard for Purge Validation [page 19]
the CompoundEmployee API user
access only to defined segments,
you must add the permission for
the DRTMPurgeStatusOverview
segment if you haven't used the purge
status overview before.
New You now define the full transmission start Full Transmission Start Date for Organ
date (FTSD) for the replication of organ
izational Object Replication Defined in
izational objects from Employee Central
Transformation Template Group [page
in the transformation template group in
stead of on the selection screen of the 23]
query program.
Moving Full Transmission Start Date for
Organizational Object Replication from
Query Program to Transformation Tem
plate Group [page 50]
Changed If you move the FTSD into the past after Full Load No Longer Performed Automat
you've already replicated organizational ically When Full Transmission Start Date
objects from Employee Central, you must for Organizational Object Replication Is
now initiate a full data load manually using Moved Into the Past [page 23]
the query program.
New We've added the permissions for the Authorization Roles in SAP S∕4HANA Re
Message Monitor to the template role
vised [page 13]
SAP_HR_SFIOM_PROCESSING.
Checking and Adjusting Authorization
Roles [page 41]
94 PUBLIC Change History
2H 2022
Type of Change Description More Info
New This is the first version of this guide.
Change History PUBLIC 95
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.
96 PUBLIC Important Disclaimers and Legal Information
Important Disclaimers and Legal Information PUBLIC 97
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

SF ERP EC UPGRADE ECS4HCM en-US

Uploaded by

Copyright:

Available Formats

SF ERP EC UPGRADE ECS4HCM en-US

Uploaded by

Document Information

Original Title

Copyright

Available Formats

Share this document

Share or Embed Document

Sharing Options

Did you find this document useful?

Is this content inappropriate?

Copyright:

Available Formats

SF ERP EC UPGRADE ECS4HCM en-US

Uploaded by

Copyright:

Available Formats

PUBLIC

Document Version: 2H 2022 – 2023-06-16

Upgrading from PA_SE_IN to ECS4HCM for Data

THE BEST RUN

1 Introduction to the Upgrade from PA_SE_IN to ECS4HCM. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4

2 Upgrade from SFSF EC INTEGRATION (PA_SE_IN) on BIB to SFSF EC S4 INTEGRATION

Checking and Adjusting Implicit Enhancements. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 35

Deleting Constants That Are No Longer Required. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 37

Transferring Switch Settings Made in Table T77S0. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 38

Checking and Adjusting Authorization Roles. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 41

Splitting Transformation Template Groups and Defining Replication Direction. . . . . . . . . . . . . . . . . . 44

Getting Started with the New Employee Staging Area. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 45

Getting Started with Configuring Organizational Assignment Replication in Customizing. . . . . . . . . . 47

Upgrading to Point-to-Point Time Data Replication. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 52

Converting the Dependent Mapping Data. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .54

3 Upgrade from SFSF EC INTEGRATION (PA_SE_IN) Non-BIB to SFSF EC S4 HCM INTEGRATION

Additional Features in Business Integration Builder (BIB). . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 56

What's Different in Non-BIB and BIB. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 58

How Infotypes are Handled in Non-BIB and BIB. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 62

Preparing the Upgrade. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 66

Post-Upgrade Steps. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .70

Preparing the Upgrade. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 84

Post-Upgrade Steps. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .89

Official Product Name Technical Product Name Software Component

SAP SuccessFactors Employee Central SFSF EC S4 HCM INTEGRATION ECS4HCM

SAP SuccessFactors Employee Central SFSF EC INTEGRATION PA_SE_IN

• One time implementation or configuration effort.

Target Group of This Document [page 5]

Maintenance Strategy for the SFSF EC INTEGRATION Add-On [page 6]

1.1 Target Group of This Document

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

1.3 Maintenance Strategy for the SFSF EC INTEGRATION

Preparing the Upgrade [page 24]

Upgrade Steps [page 32]

Post-Upgrade Steps [page 32]

2.1 What's Different in the ECS4HCM Add-On Compared to

What's Changed in ECS4HCM More Info

Integration Package Integration Flows

Replicate Organizational Objects from SAP SuccessFactors

Undeploying Obsolete Integration Flows [page 34]

2.1.2 Business Integration Builder Is Now Default

• Assign Cost Center Keys (customizing view PAOCFEC_KMAPCOSC)

2.1.3 Customizing Restructured Based on Replication Direction

2.1.4 Constants Removed from Table ECPAO_CONSTANTS

0001 EC to ERP (BIB) / EC to ERP (Non-BIB): Simulation Mode

4000 EC to ERP (Non-BIB): Default Date of Birth

4010 EC to ERP (Non-BIB): Default Pay Group

4020 EC to ERP (BIB): Move of FTSD

5000 Default Template group for P. Api

Deleting Constants That Are No Longer Required [page 37]

2.1.5 Switches Removed from T77S0 Table

The following switches have been converted to constants in table ECPAO_CONSTANTS.

SFSFI OANSC Don't Create Position to Job EC to ERP: Omit Position-Job

SFSFI OANSK Don't Create Position to Cost EC to ERP: Omit Pos.-Cost

SFSFI OANSO Don't Create Position to Org. EC to ERP: Omit Pos.-Org

SFSFI OANSS Don't Create Position to Man­ EC to ERP: Omit Pos.-Man­

SFSFI VCNCY Handle Relations of Vacant EC to ERP: Pos. Relations: Va­

Group Semantic Abbreviation Description

SFSFI SPOMP Use Specific Processing for Organiza­

SFSFI OANSS Don't Create Position to Man EC to ERP: Omit Pos.-Man

SFSFI VCNCY Handle Relations of Vacant EC to ERP: Pos. Relations: Va

SFSFI SPOMP Use Specific Processing for Organiza

SFSFI PMACT Position Management Is Enabled in Em

with display author

SFSFI OANSO Don't Create Position to Org. Unit Rela

SFSFI OANSS Don't Create Position to Manager Posi

SFSFI SPOMP Use Specific Processing for Organiza

SFSFI PMACT Position Management Is Enabled in Em

PAOCFEC_ADR_IMPC Customer-specific address implementation class per coun