1. technology and computing
2. enterprise technology
3. enterprise resource planning

SuccessFactors HCM Suite
August 2014 Release
Document Version: 1.2 - November 11, 2014
Employee Central and SAP ERP: Sideby-Side Deployment Model
Administration Guide
Table of Contents
1
Change History. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4
2
Introduction. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5
2.1
Target Group. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6
2.2
Terminology. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6
2.3
Business Scenario. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7
3
Check if the Customer System is Prepared to Integrate with Employee Central. . . . . . . . . . . . . . . 8
4
Replication of Employee Master Data from the On-Premise SAP ERP HCM System to
Employee Central. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .9
4.1
4.2
Setting up the On-Premise SAP ERP HCM System. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9
4.1.1
Business Scenario. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .9
4.1.2
Supported Employee Central Entities. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9
4.1.3
Communication Channels for the Replication of Employee Master Data. . . . . . . . . . . . . . . . . 10
4.1.4
Defining Customer-Specific Activities. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 12
Setting up Employee Central for the Replication of Employee Data. . . . . . . . . . . . . . . . . . . . . . . . . . . .34
4.2.1
4.3
Create Event Reasons in Employee Central. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 34
Master Data Replication Information. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 36
4.3.1
Standard Employee Central Fields. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 36
4.3.2
Standard Mapping of SAP ERP HCM Fields to Employee Central Fields. . . . . . . . . . . . . . . . . .37
4.3.3
Sample Mapping of SAP ERP HCM Fields to Employee Central Fields. . . . . . . . . . . . . . . . . . . 38
4.4
Setting up the Middleware. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 39
4.5
Setting up Employee Central Time Off for Employees Mastered in SAP ERP HCM. . . . . . . . . . . . . . . . . 39
4.5.1
Create a Business Rule. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 39
4.5.2
Configure the Company System Settings. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 40
4.5.3
Check the Company Code Mapping. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 41
4.5.4
Configure the Template Group. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 43
4.5.5
Map the Employee Central Time Types to SAP ERP Absence Types. . . . . . . . . . . . . . . . . . . . 44
4.5.6
Set up the Middleware. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 47
4.5.7
Extract Employee Data. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .47
4.5.8
Request Time Off in Employee Central. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .47
4.5.9
Check Replicated Time-Off Information in SAP ERP HCM. . . . . . . . . . . . . . . . . . . . . . . . . . . 50
5
HR Business Processes in the Side-by-Side Deployment Model. . . . . . . . . . . . . . . . . . . . . . . . . . .53
5.1
Prerequisites and Restrictions. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 53
5.2
Hire. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 54
5.3
2
5.2.1
Hiring a New Employee in SAP ERP HCM. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 54
5.2.2
Hiring a New Employee in Employee Central. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 56
Rehire. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 56
© 2014 SAP SE or an SAP affiliate company. All rights reserved.
Employee Central and SAP ERP: Side-by-Side Deployment Model
Table of Contents
5.3.1
Rehiring an Employee in SAP ERP HCM Who Was Previously Mastered in SAP ERP HCM
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 56
5.3.2
Rehiring an Employee in Employee Central Who Was Previously Mastered in Employee
Central. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 58
5.3.3
Rehiring an Employee in Employee Central Who Was Previously Mastered in SAP ERP HCM
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 58
5.3.4
Rehiring an Employee in SAP ERP HCM Who Was Previously Mastered in Employee Central
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 58
5.4
5.5
Transfer. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 58
5.4.1
Transferring an Employee Within SAP ERP HCM. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 59
5.4.2
Transferring an Employee Within Employee Central. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 59
International Transfer. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 59
5.5.1
Transferring an Employee From a Country Mastered in SAP ERP HCM to Another Country
Mastered in SAP ERP HCM. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .59
5.5.2
Transferring an Employee From a Country Mastered in Employee Central to Another
Country Mastered in Employee Central. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 60
5.5.3
Transferring an Employee from a Country Mastered in SAP ERP HCM to a Country
Mastered in Employee Central. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 60
5.6
5.7
Global Assignment. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 60
5.6.1
Assigning an Employee Globally Within SAP ERP HCM. . . . . . . . . . . . . . . . . . . . . . . . . . . . . 60
5.6.2
Assigning an Employee Globally within Employee Central. . . . . . . . . . . . . . . . . . . . . . . . . . . 61
5.6.3
Assigning an Employee Globally in SAP ERP HCM And Employee Central. . . . . . . . . . . . . . . . 61
Termination. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 61
5.7.1
Terminating an Employee Mastered in SAP ERP HCM. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 61
5.7.2
Terminating an Employee Mastered in Employee Central. . . . . . . . . . . . . . . . . . . . . . . . . . . .61
6
Integration of the Employee Central UI with the On-Premise SAP ERP HCM System. . . . . . . . . . .62
6.1
Configuring the Third-Party System in the SAP ERP HCM System. . . . . . . . . . . . . . . . . . . . . . . . . . . . 62
6.2
6.1.1
Create an SICF Handler. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 63
6.1.2
Optional: Adjust the ASR_PROCESS_EXECUTE Web Dynpro Application. . . . . . . . . . . . . . . . 65
Configuring the Third-Party System in Employee Central. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 69
6.2.1
Create a Picklist for the RuleType Field. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 69
6.2.2
Create Generic Object Configurations. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 70
6.2.3
Configure the Business Rule. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 75
6.2.4
You're done! Now Check the Result. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 76
6.2.5
Disabling the Edit Mode for Third-Party System Records in Employee Central. . . . . . . . . . . . .76
7
You're done! What’s Next?. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 78
7.1
Troubleshooting. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 78
7.1.1
Check the Data Replication Results. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 78
Employee Central and SAP ERP: Side-by-Side Deployment Model
Table of Contents
© 2014 SAP SE or an SAP affiliate company. All rights reserved.
3
1
Change History
The following table provides a historical overview of the most important changes made to this document since its
initial publication.
Version
Date
Description
1.0
August 22, 2014
Initial release
1.1
September 23, 2014
Changed:
●
1.2
4
November 11, 2014
© 2014 SAP SE or an SAP affiliate company. All rights reserved.
Section Extract Changed Employee
Master Data Using Delta Replication
[page 31] explains now in more
detail how the RBDMIDOC program
is used for the delta replication
Changed:
●
In section Define Employee Central
Company [page 15], more
detailed information about the
user_id, person_id_external, and
username mapping was added
●
In section Prerequisites and
Restrictions [page 53], more
information about number ranges
was added and the prerequisite
about standard mappings was
changed into a recommendation
●
In section Rehiring an Employee in
Employee Central Who Was
Previously Mastered in SAP ERP
HCM [page 58], more details
were added about the rehire
process
●
In section Transferring an Employee
From a Country Mastered in SAP
ERP HCM to Another Country
Mastered in SAP ERP HCM [page
59], the information was added
that a Transfer event is carried out
in Employee Central
●
In section Create Generic Object
Configurations [page 70], step 5,
the information was added that the
name of the association has to be
cust_thirdPartyURL
Employee Central and SAP ERP: Side-by-Side Deployment Model
Change History
2
Introduction
The purpose of this guide is to help implement the integration of on-premise SAP ERP HCM systems with
SuccessFactors Employee Central in the side-by-side context. The side-by-side deployment model is for
customers who want to transition their HCM system to the Cloud while still leveraging investments into employee
administration on premise. It comprises the coexistence of HR core in the Cloud (SuccessFactors Employee
Central) and on premise (SAP ERP HCM).
The side-by-side deployment model supports these deployment scenarios:
●
A consolidated scenario, which means that Employee Central is leveraged as the system of record for all
global HR Core processes while SAP ERP HCM is used for local HR processes.
This scenario is generally available. For more information about this scenario, refer to the SuccessFactors
Employee Central Payroll with SAP ERP: Employee Master Data Replication integration guide. Find the most
current version of this guide on SAP Service Marketplace at http://service.sap.com/ec-ondemand
●
.
A distributed scenario, which means that the workforce is split between two systems of record, Employee
Central and SAP ERP HCM.
This is the scenario that is described in this guide.
Restriction
The distributed scenario is released under the following conditions:
○
Leveraging Employee Central as the UI navigation hub for Employee Self-Service and Manager SelfService use cases is available as a public beta shipment.
○
The employee data integration from one SAP ERP HCM system to Employee Central is generally
available only for SuccessFactors net new customers leveraging Performance & Goals, platform
features, and reporting.
After executing all steps described in this document you will be able to:
●
Transfer employee master data from an on-premise SAP ERP HCM system to Employee Central
●
Run core HR processes in on-premise SAP ERP HCM systems and Employee Central while employee data is
kept in sync across the distributed system landscape
●
Leverage Employee Central as a common UI hub for employee self-service and manager self-service
scenarios, such as job changes or look-up of the job history for employees mastered in on-premise SAP ERP
HCM systems
This guide is structured in a sequence in which the different systems should be set up. It describes only the steps
that you as an admin can perform. Additional activities are needed that only SuccessFactors Professional
Services or an SAP consultant can carry out. You will therefore need their support to set up the complete side-byside deployment model.
Caution
Usage of any integration software and content provided with the SAP Business Suite or SAP ERP software and
applicable to an integration between the SAP Business Suite or SAP ERP and SuccessFactors Employee
Central is permitted only with SAP ERP and a valid, current contract for SuccessFactors Employee Central.
Some SAP Cloud Services are available for use with on-premise SAP ERP systems. SAP Cloud Services must
be integrated through a Professional Services engagement. Please contact the Customer Success team for
more information.
Employee Central and SAP ERP: Side-by-Side Deployment Model
Introduction
© 2014 SAP SE or an SAP affiliate company. All rights reserved.
5
2.1
Target Group
This guide is intended for SAP certified administrators.
2.2
Terminology
This table explains some terms used in this guide.
Term
Abbreviation
Definition
Application Programming Interface
API
An interface technology for connecting
application systems with one another.
Business Add-In
BAdI
A technology used to adapt SAP
software to specific requirements.
BAdIs are used to create predefined
enhancement options in SAP ERP,
which can be implemented by partners
and customers.
Central Person
CP
An object in the SAP ERP HCM system
that links the employee to the business
partner, which means, to a party in
which a company has a business
interest.
Feature
--
An object in the SAP ERP HCM system
that determines default values by
querying different personnel and data
structure fields.
Handler Class
--
The ABAP Objects class that is behind
an HTTP request handler. When you
create an ICF service in transaction
SICF, it is created as an element in the
handler list.
Intermediate Document
IDoc
A format for electronic data interchange
between systems.
Internet Communication Framework
ICF
A software layer in the SAP ERP HCM
system that provides an ABAP interface
for HTTP, HTTPS, and SMTP requests.
The ABAP environment uses Internet
Communication Framework to
communicate with Web applications in
the server role and in the client role.
Personnel Number
PERNR
The identification of an employee in the
SAP ERP HCM system.
6
© 2014 SAP SE or an SAP affiliate company. All rights reserved.
Employee Central and SAP ERP: Side-by-Side Deployment Model
Introduction
Term
Abbreviation
Definition
System of Record
--
The system in which an employee is
mastered, meaning, the system that is
the authoritative data source for the
employee's master data.
Third-Party System
--
Any system other than the system to
which the user is currently logged on.
For example, for an Employee Central
user, the on-premise SAP ERP HCM
system is a third-party system.
2.3
Business Scenario
The following is an example of a typical business scenario that takes advantage of the side-by-side deployment
model: The size and complexity of your enterprise don't allow for a one-step migration of your HCM systems to
the Cloud. Therefore, you plan to deploy certain countries or legal entities step-by-step in the Cloud while keeping
them integrated with your productive on-premise SAP ERP HCM installations.
Some characteristics of the distributed scenario in the side-by-side deployment model are:
●
The workforce is split among Employee Central and on-premise SAP ERP HCM. Both systems are used as a
system of record depending on the employee's country assignment.
●
HR processes run in the respective system of record while employee data is to be kept in sync across the
distributed HCM system landscape.
●
UI mash-ups within Employee Central provide access to HR data and processes that are mastered in
Employee Central as well as in on-premise SAP ERP HCM.
Employee Central and SAP ERP: Side-by-Side Deployment Model
Introduction
© 2014 SAP SE or an SAP affiliate company. All rights reserved.
7
3
Check if the Customer System is Prepared
to Integrate with Employee Central
Context
In this section, we describe the preparatory steps for using the side-by-side deployment model.
Procedure
1.
2.
Do you meet the minimum setup for on-premise SAP ERP HCM systems?
For this component ...
... you need this software component version
SAP NetWeaver
SAP_BASIS 700 SP18 or higher
SAP ERP
SAP_APPL 600 SP15 or higher
Integration add-on for SAP ERP master data and
SuccessFactors Employee Central
PA_SE_IN 100 SP07 or higher
Have you already installed the SAP GUI? If not, download it from the SAP Service Marketplace at http://
service.sap.com/swdc
8
.
© 2014 SAP SE or an SAP affiliate company. All rights reserved.
Employee Central and SAP ERP: Side-by-Side Deployment Model
Check if the Customer System is Prepared to Integrate with Employee Central
4 Replication of Employee Master Data from
the On-Premise SAP ERP HCM System to
Employee Central
4.1
Setting up the On-Premise SAP ERP HCM System
4.1.1
Business Scenario
The on-premise SAP ERP HCM system is configured to manage your company's employee master data. You are
running HR processes in this system. You now want to make sure that your employee master data is replicated
from the on-premise SAP ERP HCM system to Employee Central so that the Cloud-based system is synchronized
at all times with the on-premise system while you are running HR processes in the distributed system landscape.
Restriction
The current shipment of the side-by-side deployment model handles the employee master data replication
from a single on-premise SAP ERP HCM system to Employee Central.
Caution
Make sure that the data of employees who are mastered in SAP ERP HCM and replicated to Employee Central
can't be edited there. Use role-based permissions to disable the edit mode in Employee Central.
4.1.2
Supported Employee Central Entities
Different Employee Central entities form the employee data in Employee Central. Currently we support the
following CSV-based and OData-based entities:
Sequence No.
CSV Data Import Template
OData Entity
1
Basic Import
User
2
Biographical Information (Personal
Information)
PerPersonal
3
Person
PerPerson
Employee Central and SAP ERP: Side-by-Side Deployment Model
© 2014
Replication of Employee Master Data from the On-Premise SAP ERP HCM System to Employee
Central
SAP SE or an SAP affiliate company. All rights reserved.
9
Sequence No.
CSV Data Import Template
OData Entity
4
Employment Details
EmpEmployment
5
Job History
EmpJob
6
Global Assignments
EmpGlobalAssignment
7
Email Information
PerEmail
8
Phone Information
PerPhone
Note
You can't configure the Basic Import template or User entity in the SAP ERP HCM system.
In all Employee Central entities listed above there are standard mappings which are predefined by the system.
You can't configure them while defining primary mappings in the template group configuration. For more
information, refer to section Standard Mapping of SAP ERP HCM Fields to Employee Central Fields.
4.1.3 Communication Channels for the Replication of
Employee Master Data
You can transfer employee master data from SAP ERP HCM to Employee Central in the following ways:
●
●
Using CSV-based template files and the manual import framework in Employee Central
To use this framework:
1.
Go to Administration Tools.
2.
In the Manage Employees portlet, select
Update User Information
Import Employee Data .
Using a synchronous Web service call and the Boomi Atomsphere middleware
To extract employee master data from SAP ERP HCM into CSV-based templates, make these settings for the
Employee Data Extraction program:
●
Choose a template group with the Employee Central import object type CSV Data Import Entity.
●
Choose the communication channel File Transfer Using Server Path or File Transfer Using Local Drive Path.
10
© 2014 SAP SE or an SAP affiliate company. All rights reserved.
Employee Central and SAP ERP: Side-by-Side Deployment Model
Replication of Employee Master Data from the On-Premise SAP ERP HCM System to
Employee Central
To send employee master data using a synchronous Web service call, make these settings for the Employee Data
Extraction program:
●
Choose a template group with the Employee Central import object type Web Service Entity.
●
Choose the communication channel Web Service Transfer.
Employee Central and SAP ERP: Side-by-Side Deployment Model
© 2014
Replication of Employee Master Data from the On-Premise SAP ERP HCM System to Employee
Central
SAP SE or an SAP affiliate company. All rights reserved.
11
For more information, refer to the sections listed below.
Related Information
Define Template Groups [page 21]
Extract Employee Master Data [page 28]
Setting up the Middleware [page 39]
4.1.4
Defining Customer-Specific Activities
To define customer-specific settings, use the Customizing activities and Business Add-Ins (BAdIs) in the
Integration of SAP ERP Master Data and SuccessFactors Employee Central (PA_SE_IN) add-on. In the SAP
12
© 2014 SAP SE or an SAP affiliate company. All rights reserved.
Employee Central and SAP ERP: Side-by-Side Deployment Model
Replication of Employee Master Data from the On-Premise SAP ERP HCM System to
Employee Central
Customizing Implementation Guide structure, open
Interfaces and Integration
Personnel Management
Personnel Administration
Integration of SAP ERP HCM to SuccessFactors Employee Central Side by Side :
Employee Central and SAP ERP: Side-by-Side Deployment Model
© 2014
Replication of Employee Master Data from the On-Premise SAP ERP HCM System to Employee
Central
SAP SE or an SAP affiliate company. All rights reserved.
13
In the Customizing structure, you can find detailed information for each Customizing activity and BAdI:
4.1.4.1
Define if Side-by-Side Employee Data Replication to
Employee Central Is Active
Context
You specify if you use the side-by-side employee data replication from SAP ERP HCM to SuccessFactors
Employee Central in the Customizing structure Integration of SAP ERP HCM to SuccessFactors Employee Central
Side by Side, in the Define If Side-by-Side Employee Replication to Employee Central Is Active Customizing activity
(view V_ECPAO_T77S0_SFSFI_SBSER).
You need to set the switch in this Customizing activity if you use the integration add-on for SAP ERP HCM and
SuccessFactors HCM Suite. Setting the switch tells your SAP ERP HCM system that employee data is replicated
to Employee Central using the Employee Data Extraction (ECPAO_EMPL_EXTRACTION) program. Setting the
switch has the following effects on the integration add-on for SAP ERP HCM and SuccessFactors HCM Suite:
●
You can no longer use the following programs:
○
Sync Employee Data with SuccessFactors in Pre-Hire Period (RH_SFI_PREHIRE_EMPL_DATA)
○
Sync Employee Data with SuccessFactors (with Delta and Inactive Logic)
(RH_SFI_SYNCHRONIZE_EMPL_DATA)
○
Extraction of Employee Data for SuccessFactors (RH_SFI_TRIGGER_EMPL_DATA_REPL)
This is because the same data should only be transferred from one source to the SuccessFactors system.
Otherwise, data from different sources in SAP ERP HCM could be transferred to the same field in the
SuccessFactors system, which would lead to data inconsistencies.
●
In the Replication of Employee's Compensation Data (RH_SFI_SYNCH_COMP_DATA) program, you can no
longer select an option for transferring the user ID to SuccessFactors. The User ID Determination field is
removed from the selection screen.
14
© 2014 SAP SE or an SAP affiliate company. All rights reserved.
Employee Central and SAP ERP: Side-by-Side Deployment Model
Replication of Employee Master Data from the On-Premise SAP ERP HCM System to
Employee Central
This is because in the side-by-side deployment model the user ID is determined by the Employee Data
Extraction (ECPAO_EMPL_EXTRACTION) program and stored in the Employee Key Mapping
(PAOCFEC_EEKEYMAP) table.
Procedure
Set the value of the SFSFI SBSER switch to X or leave it empty.
4.1.4.2
Define Employee Central Company
Context
You define the Employee Central company instance to which you replicate the employee master data from SAP
ERP HCM in the Customizing structure Integration of SAP ERP HCM to SuccessFactors Employee Central Side by
Side, in the Specify Employee Central Company ID Customizing activity (view V_ECPAO_COMPANY).
Procedure
1.
Enter the company ID that you use in SuccessFactors and a description.
2.
Specify how the following Employee Central fields are to be mapped to SAP ERP HCM:
○
user_id
You can choose from the following mapping modes:
○
Standard mapping: The user_id field is mapped to the Personnel Number (PERNR) field in SAP ERP
HCM.
○
○
BAdI mapping: If you have specific requirements, you create a Business Add-In (BAdI)
implementation of the Mapping of User ID, Person ID, and User Name
(EX_ECPAO_EMP_USYID_PRN_UNM_MAP) BAdI to define the mapping.
person_id_external
You can choose from the following mapping modes:
○
Standard mapping: The person_id_external field is mapped to the central person (CP) in SAP ERP
○
Infotype mapping: The person_id_external field is mapped to the SAP ERP HCM infotype Person ID
(0709).
○
BAdI mapping (see above)
HCM.
○
username
Employee Central and SAP ERP: Side-by-Side Deployment Model
© 2014
Replication of Employee Master Data from the On-Premise SAP ERP HCM System to Employee
Central
SAP SE or an SAP affiliate company. All rights reserved.
15
You can choose from the following mapping modes:
○
Standard mapping: The username field is mapped to the Personnel Number (PERNR) field in SAP ERP
HCM.
○
Infotype mapping: The username field is mapped to the SAP ERP HCM infotype Communication
(0105), subtype System User Name (SY-UNAME) (0001).
○
BAdI mapping (see above)
For more information about these mappings, refer to the documentation of this Customizing activity.
Example
For an example, see the Employee Central company SBS_MODEL in the delivered sample Customizing.
4.1.4.3
Import Metadata from Employee Central
Context
You import metadata from SuccessFactors Employee Central in the Customizing structure Integration of SAP
ERP HCM to SuccessFactors Employee Central Side by Side, in the Import Metadata from Employee Central
Customizing activity (program ECPAO_ECFLD_METADATA_WRITER).
The Import of Metadata from Employee Central (ECPAO_ECFLD_METADATA_WRITER) program makes Employee
Central fields available in the SAP ERP HCM system so that you can use them for field mappings in the Define
Template Group Customizing activity. You can import metadata of the following types:
●
CSV-Data Import Entity
●
Web Service Entity
Procedure
1.
Download the metadata from Employee Central:
○
16
To download metadata of the CSV Data Import Entity type:
1.
Go to Administration Tools.
2.
In the Manage Employees portlet, select
© 2014 SAP SE or an SAP affiliate company. All rights reserved.
Update User Information
Import Employee Data .
Employee Central and SAP ERP: Side-by-Side Deployment Model
Replication of Employee Master Data from the On-Premise SAP ERP HCM System to
Employee Central
○
3.
Click the Download a blank CSV template link.
4.
A list of templates is displayed.
To download metadata of the Web Service Entity type:
1.
Go to Administration Tools.
2.
In the Company Processes & Cycles portlet, select
Company Settings
OData API Data
Dictionary .
Note
This option in the Administration Tools has to be enabled in Provisioning using the relevant OData
dictionary configuration.
3.
A list of templates is displayed.
4.
Expand a template and copy the complete content of the table displayed below Fields, including the
table header:
5.
Paste the content to a spreadsheet and save the spreadsheet using the .csv file extension.
Download all templates that are supported.
2.
On the selection screen of the program, specify which metadata you want to import to SAP ERP HCM and
from which file you want to upload it:
For more information about the selection options, refer to the documentation of the Customizing activity.
3.
Carry out a test run of the program to see the data that will be uploaded to SAP ERP HCM or upload the data
from the Employee Central metadata file directly into the EC Template Field Mapping (ECPAO_FLD) table.
Employee Central and SAP ERP: Side-by-Side Deployment Model
© 2014
Replication of Employee Master Data from the On-Premise SAP ERP HCM System to Employee
Central
SAP SE or an SAP affiliate company. All rights reserved.
17
Caution
The standard fields are also uploaded into the EC Template Field Mapping table. In this table, the Is
Standard Field (IS_FLD_STANDARD) indicator is set to True for these fields. Since a standard mapping is
defined for them, they are not available in the Customizing of the template groups. For more information,
refer to section Standard Mapping of SAP ERP HCM Fields to Employee Central Fields.
4.1.4.4
Define Value Mappings
Context
If you need to map Employee Central field values to values of SAP ERP HCM fields, you can define value mappings
in the Customizing structure Integration of SAP ERP HCM to SuccessFactors Employee Central Side by Side, in the
Define Value Mapping section.
The Employee Data Extraction (ECPAO_EMPL_EXTRACTION) program uses the value mappings that are assigned
in the Primary Mapping and Secondary Mapping views of the template group, which you specify on the selection
screen of this program. When extracting employee master data it replaces the SAP ERP HCM keys by the
corresponding Employee Central keys if a value mapping is defined for the corresponding field mapping.
Procedure
1.
18
Define country-independent and country-dependent value mapping entities in the Define Value Mapping
Entities Customizing activity (view V_ECPAO_VALUENTY)
© 2014 SAP SE or an SAP affiliate company. All rights reserved.
Employee Central and SAP ERP: Side-by-Side Deployment Model
Replication of Employee Master Data from the On-Premise SAP ERP HCM System to
Employee Central
a) Provide a name and description for the value mapping entity.
b) Specify how the values are to be mapped. You have these options:
○
Picklist mapping using the External Code field from the picklist
Use this type if the picklist value you want to map is an external code. This is the case, for example,
for Employee Central fields such as Address Type and Country.
Example
The picklist for the address type contains the external codes home and vacation. You want to map
these to the SAP ERP HCM address types, which are stored as subtypes of the infotype Addresses
(0006).
○
Picklist mapping using the Option ID field from the picklist
Use this type if the picklist value you want to map is an option ID. This is the case for most of the
picklists.
Example
The picklist for the gender code contains the option IDs F and M. You want to map these to the SAP
ERP gender codes.
○
Picklist mapping using the Label field from the picklist
Use this type if the picklist value you want to map is the picklist label.
○
Foundation Object Key mapping
Use this type to map Employee Central event reasons to personnel actions from SAP ERP HCM.
Employee Central and SAP ERP: Side-by-Side Deployment Model
© 2014
Replication of Employee Master Data from the On-Premise SAP ERP HCM System to Employee
Central
SAP SE or an SAP affiliate company. All rights reserved.
19
Example
You want to map the Employee Central event reason DATAREORG to the personnel action 02
(Organizational Reassignment).
○
Standard mapping
Use this type for a standard mapping of Employee Central and SAP ERP HCM values, for which no
picklist ID is required. Standard mappings are predefined in the SAP ERP HCM system and can't be
changed.
Define the value mapping entities based on the type of communication channel that you use for the
employee master data replication. If you use CSV-based files and the manual import framework in
Employee Central, define value mappings with the mapping type Label. If you use the Web service-based
replication, the suitable mapping type is usually the Option ID type.
2.
Define country-independent value mappings in the Define Value Mapping Details Customizing activity (view
V_ECPAO_VALENTY).
Here you map SAP ERP HCM keys and the corresponding Employee Central keys for each countryindependent value mapping entity that you have defined in the first step.
3.
20
Define country-dependent value mappings in the Define Country-Specific Value Mapping Details Customizing
activity (view V_ECPAO_VALENTYC).
© 2014 SAP SE or an SAP affiliate company. All rights reserved.
Employee Central and SAP ERP: Side-by-Side Deployment Model
Replication of Employee Master Data from the On-Premise SAP ERP HCM System to
Employee Central
Here you map SAP ERP HCM keys and the corresponding Employee Central keys as described above, and
additionally assign ISO codes.
Example
For an example, see the value mapping entities defined for the Employee Central company SBS_MODEL in the
delivered sample Customizing. The SBS_MODEL company contains example value mapping entities for countryindependent mappings, such as EVENT_REASON or LANGUAGE_CODE.
4.1.4.5
Define Template Groups
Context
You create template groups in the Customizing structure Integration of SAP ERP HCM to SuccessFactors
Employee Central Side by Side, in the Map EC Templates and SAP ERP Templates for Employee Replication
Customizing activity (view cluster VC_ECPAO_MAP). The template group configuration determines how the
employee master data extraction is carried out and maps SAP ERP HCM fields to Employee Central fields.
Procedure
1.
Define the template group:
Employee Central and SAP ERP: Side-by-Side Deployment Model
© 2014
Replication of Employee Master Data from the On-Premise SAP ERP HCM System to Employee
Central
SAP SE or an SAP affiliate company. All rights reserved.
21
a) Enter a name and description for the template group and assign it to the Employee Central company
defined in the Specify Employee Central Company ID Customizing activity.
b) Assign one of these Employee Central import object types to the template group:
○
CSV Data Import Entity
Choose this import type if you want to use the template group for the CSV-based extraction of
employee master data.
○
Web Service Entity
Choose this import type if you want to use the template group to transfer employee master data
using a Web service call.
c) Optional: Define a cutoff date.
You can specify this date to start the replication of employee master data at a specific point in time. This
prevents the complete history of data records for the given employees to be replicated from SAP ERP
HCM to Employee Central. For more information, refer to the following sections:
○
Create Event Reasons in Employee Central
○
Hiring a New Employee in SAP ERP HCM [page 54]
○
Rehiring an Employee in SAP ERP HCM Who Was Previously Mastered in SAP ERP HCM [page 56]
d) Define if the template group is available for delta replication.
For more information, refer to section Extract Changed Employee Master Data Using Delta Replication.
Note
You can only use template groups with the Employee Central import object type Web Service Entity for
delta replication. To make sure that the delta replication works, use a template group that has the
import object type Web Service Entity and for which the Delta Replication checkbox is selected.
2.
22
Define a set of SAP ERP templates for each template group.
© 2014 SAP SE or an SAP affiliate company. All rights reserved.
Employee Central and SAP ERP: Side-by-Side Deployment Model
Replication of Employee Master Data from the On-Premise SAP ERP HCM System to
Employee Central
For each SAP ERP template, you make these settings:
a) Enter a name and description for the template and assign it to one of the predefined Employee Central
entities. For more information, refer to section Supported Employee Central Entities.
b) Select the Active checkbox to define if the template is to be used for the extraction of employee master
data.
c) Specify if the template is based on the hire date of the employee.
If you select this checkbox, the employee data to be extracted based on the SAP ERP template is
retrieved using the hire date of the employee as the start date for the data records.
3.
Define the primary field mappings for each SAP ERP template.
a) Assign Employee Central fields that you have imported into the SAP ERP HCM system using the Import
Metadata from Employee Central Customizing activity.
b) Map each Employee Central field to an SAP ERP HCM field using a suitable mapping mode:
Employee Central and SAP ERP: Side-by-Side Deployment Model
© 2014
Replication of Employee Master Data from the On-Premise SAP ERP HCM System to Employee
Central
SAP SE or an SAP affiliate company. All rights reserved.
23
○
When you select the mapping mode Infotype Mapping, you assign an infotype or subtype field in the
primary mapping.
○
When you select the mapping mode Preconfigured Mapping, you can use mappings that were defined
by SAP in the Preconfigured Mapping tables (ECPAO_PREMAPPING, ECPAO_PREMAP_TT).
○
When you select the mapping mode BAdI Mapping, you can use an implementation of the Mapping of
EC and SAP ERP Data for Employee Replication (EX_ECPAO_EMP_DATA_EXTRACT_OUT) BAdI to
define the field mapping. For more information, refer to section Implement Business Add-Ins for the
Replication of Employee Master Data [page 33].
c) Specify if the Employee Central field is a required field based on the Succession Data Model configured in
your Employee Central company instance.
If an Employee Central field is set to Required, the Employee Data Extraction program must extract data
from the SAP ERP HCM system for this field. If there is no data available, it writes an error message to the
application log. For more information, refer to section Extract Employee Master Data.
d) If the value from the SAP ERP field needs to be converted, enter the value mapping entity that you have
defined in the Define Value Mapping Entities Customizing activity.
4.
If there are country-specific mappings for an Employee Central field, map it using the secondary mapping.
You can use the secondary mapping in the following ways:
○
24
Based on a linking field
© 2014 SAP SE or an SAP affiliate company. All rights reserved.
Employee Central and SAP ERP: Side-by-Side Deployment Model
Replication of Employee Master Data from the On-Premise SAP ERP HCM System to
Employee Central
This is one of the fields from the infotype or subtype that you have defined in the primary mapping. You
can choose the linking field from the value help in the Secondary Mapping view. The linking field is
dynamically populated based on the infotype or subtype you have specified in the Primary Mapping view.
○
Based on the infotype view indicator (field VIEKN from the Payroll Status (0003) infotype)
Example
For an example, see the template group SBS_CSV_MODEL_TMPL defined for the Employee Central company
SBS_MODEL in the delivered sample Customizing. This template group has the Employee Central import object
type CSV Data Import Entity. You can copy this template group to your Employee Central company and change
the field mapping of the SAP ERP templates to suit your requirements. The employee master data extracted
from the SAP ERP HCM system is downloaded to a CSV file based on the template group you have specified.
You can store this file on the application server or on your local drive.
Employee Central and SAP ERP: Side-by-Side Deployment Model
© 2014
Replication of Employee Master Data from the On-Premise SAP ERP HCM System to Employee
Central
SAP SE or an SAP affiliate company. All rights reserved.
25
You can also use the template group SBS_MODEL_WS as an example. This template group is defined for the
Employee Central company SBS_MODEL in the delivered sample Customizing as well. It has the Employee
Central object type Web Service Entity. This object type is used for the replication of employee master data to
Employee Central via a Web service call.
4.1.4.6
Determine the Employees' Managers
Procedure
1.
Go to the Define Background Job (SM36) transaction.
2.
Schedule the Manager Determination for Employees (ECPAO_MNGR_EXTRACTION) program as a regular
background job to determine all managers within the root organizational unit that you specify on the selection
screen.
26
© 2014 SAP SE or an SAP affiliate company. All rights reserved.
Employee Central and SAP ERP: Side-by-Side Deployment Model
Replication of Employee Master Data from the On-Premise SAP ERP HCM System to
Employee Central
3.
The program uses the Is managed by... (B012) relationship to determine the managers and stores their
personnel numbers in the Manager Assignments for Employee Replication (ECPAO_EE_MGNR) table, together
with the personnel numbers of the employees who are assigned to the organizational units managed by the
B012 relationships.
If a central person (CP) is assigned to the manager position instead of a personnel number, you get an error
message such as the following in the program log and the application log:
4.
To check the messages, go to the Analyze Application Log (SLG1) transaction.
5.
Enter the ECPAO object and ECPAO_MANAGER subobject, optionally specify additional selection criteria, and
click Execute.
Next Steps
The Employee Data Extraction program reads the information about the managers from the ECPAO_EE_MGNR
table. If it finds the manager for an employee, it transfers this information to Employee Central. Otherwise, the
entry NO_MANAGER is transferred.
4.1.4.7
Handle Managers in the SAP ERP HCM System
Whose Data Is Mastered in Employee Central
Context
Managers whose data is mastered in Employee Central don't have a personnel number in the SAP ERP HCM
system. To be able to transfer the manager relationships of employees who are assigned to these managers from
SAP ERP HCM to Employee Central, you must therefore create users for these managers in SAP ERP HCM. The
Manager Determination for Employees (ECPAO_MNGR_EXTRACTION) program then stores these managers' users
instead of the personnel numbers in the Manager Assignments for Employee Replication (ECPAO_EE_MGNR) table.
Employee Central and SAP ERP: Side-by-Side Deployment Model
© 2014
Replication of Employee Master Data from the On-Premise SAP ERP HCM System to Employee
Central
SAP SE or an SAP affiliate company. All rights reserved.
27
Procedure
1.
Go to the User Maintenance (SU01) transaction.
2.
Create a user for each manager whose data is mastered in Employee Central and who has employees
assigned whose data is mastered in SAP ERP HCM.
3.
Maintain an alias for each user that corresponds to the unique identifier of this employee in Employee Central.
Restriction
The managers' users have to be absolutely identical in SAP ERP HCM and in Employee Central. In the SAP
ERP HCM system, user names can only have 40 characters and have to be in uppercase. Therefore, this
approach only works for new Employee Central customers who make sure that their user names in
Employee Central comply with the SAP ERP HCM user definition.
4.
Go to the Organization and Staffing (PPOME) transaction.
5.
Using the Holder (B008) relationship, assign each user to a position that has the Manages... (B012)
relationship to the organizational unit of the employee or employees in question.
4.1.4.8
Extract Employee Master Data
Procedure
1.
28
Go to the ABAP: Program Execution (SA38) transaction.
© 2014 SAP SE or an SAP affiliate company. All rights reserved.
Employee Central and SAP ERP: Side-by-Side Deployment Model
Replication of Employee Master Data from the On-Premise SAP ERP HCM System to
Employee Central
2.
Execute the Employee Data Extraction (ECPAO_EMPL_EXTRACTION) program to initially extract employee
master data from the SAP ERP HCM system based on the given selection criteria.
On the selection screen you specify the template group to be used for the data extraction and the relevant
communication channel. For more information refer to the following sections:
○
Communication Channels for the Replication of Employee Master Data [page 10]
○
Define Template Groups [page 21]
You can also carry out a test run of the program to check if the data can be extracted from SAP ERP HCM
without any errors.
You can select the Detailed Message Log checkbox to get a detailed log containing all warning and error
messages for each employee.
3.
The program writes messages to the application log.
4.
To check the messages, go to the Analyze Application Log (SLG1) transaction.
5.
Enter the ECPAO object and subobject, optionally specify additional selection criteria, and click Execute.
Employee Central and SAP ERP: Side-by-Side Deployment Model
© 2014
Replication of Employee Master Data from the On-Premise SAP ERP HCM System to Employee
Central
SAP SE or an SAP affiliate company. All rights reserved.
29
Next Steps
Make sure that the data of employees who are mastered in SAP ERP HCM and replicated to Employee Central
can't be edited there. Use role-based permissions to disable the edit mode in Employee Central.
After the initial run of the program, changed data is replicated using delta replication. For more information, refer
to section Extract Changed Employee Master Data Using Delta Replication [page 31]. You can run the Employee
Data Extraction program to extract data for selected employees.
30
© 2014 SAP SE or an SAP affiliate company. All rights reserved.
Employee Central and SAP ERP: Side-by-Side Deployment Model
Replication of Employee Master Data from the On-Premise SAP ERP HCM System to
Employee Central
4.1.4.9 Extract Changed Employee Master Data Using Delta
Replication
Prerequisites
You can only use template groups with the Employee Central object type Web Service Entity for delta replication.
Context
When HR admins change master data in Personnel Administration in the SAP ERP HCM system, change pointers
are created. The Creating IDoc Type from Change Pointers (RBDMIDOC) program (or BD21 transaction) reads the
change pointers with the ECPAO message type, replicates the changed data using the Employee Data Extraction
(ECPAO_EMPL_EXTRACTION) program, and marks the change pointers as processed.
Note
The employee master data replication does not use Application Link Enabling (ALE) or IDocs. The RBDMIDOC
program uses the ECPAO message type to trigger the replication of changed master data to Employee Central
using a synchronous Web service call.
Procedure
1.
Go to the Define Background Job (SM36) transaction.
2.
Schedule the Creating IDoc Type from Change Pointers (RBDMIDOC) program as a regular background job
using the ECPAO message type.
Employee Central and SAP ERP: Side-by-Side Deployment Model
© 2014
Replication of Employee Master Data from the On-Premise SAP ERP HCM System to Employee
Central
SAP SE or an SAP affiliate company. All rights reserved.
31
4.1.4.10 Download CSV Files from the Application Server
Prerequisites
●
The logical file path ECPAO_TMPL_DIR is defined in the Logical File Path Definition (FILE) transaction.
●
You have selected the File Transfer using Server Path option on the selection screen of the Employee Data
Extraction (ECPAO_EMPL_EXTRACTION) program, executed the program, and received a success message.
Context
The extracted data is stored on the application server. To transfer the data from the application server location to
a local drive, carry out the steps described below.
Procedure
1.
Go to the SAP Directories (AL11) transaction.
2.
Double-click DIR_GLOBAL to see the files in this directory and note the name of the file that you want to
download, such as BASIC_IM.
3.
Go to the Download File (CG3Y) transaction.
4.
Enter the source file, such as /usr/sap/<SYSTEM>/SYS/global/BASIC_IM.
5.
Enter the target folder and file name, such as C:\temp\BASIC_IN, and add the file format .csv.
6.
Click Download.
The file gets downloaded to the folder you have specified.
32
© 2014 SAP SE or an SAP affiliate company. All rights reserved.
Employee Central and SAP ERP: Side-by-Side Deployment Model
Replication of Employee Master Data from the On-Premise SAP ERP HCM System to
Employee Central
4.1.4.11
Update Employee Key Mapping Table
Context
The Employee Key Mapping (PAOCFEC_EEKEYMAP) table is updated when the employee data replication from SAP
ERP HCM to Employee Central was successful. This table contains the unique identifier of the employee from the
SAP ERP HCM system and the Employee Central system. If you use the Web service-based data replication, the
employee key mapping table is updated automatically. If you use the CSV file-based data replication, you have to
update the table manually. To do so, carry out the steps described below.
Procedure
1.
Execute the Update Key Values Mapping Table with Manually Replicated Employee Data
(ECPAO_EEREPCSV_EEKEYMAP_UPDATE).
2.
The program updates the employee key mapping table with the following key values:
○
Employee ID from Employee Central
○
Employment ID from Employee Central
○
Work agreement ID from Employee Central
○
User ID from Employee Central
○
Personnel number from SAP ERP HCM
○
Company code from SAP ERP HCM
○
Central person from SAP ERP HCM
4.1.4.12 Implement Business Add-Ins for the Replication of
Employee Master Data
Context
You can use the Business Add-Ins (BAdIs) provided in the Customizing structure Integration of SAP ERP HCM to
SuccessFactors Employee Central Side by Side, in the Business Add-Ins (BAdIs) section to adapt the replication of
employee master data from SAP ERP HCM to Employee Central to your specific requirements.
Employee Central and SAP ERP: Side-by-Side Deployment Model
© 2014
Replication of Employee Master Data from the On-Premise SAP ERP HCM System to Employee
Central
SAP SE or an SAP affiliate company. All rights reserved.
33
Procedure
1.
If you have selected the BAdI Mapping mapping mode in the Map EC Templates and SAP ERP Templates for
Employee Replication Customizing activity, you must implement the Mapping of EC and SAP ERP Data for
Employee Replication (EX_ECPAO_EMP_DATA_EXTRACT_OUT) BAdI.
Your BAdI implementation must provide the mapping for all fields for which you have selected this mapping
mode. Using this BAdI, you read the relevant SAP ERP HCM data based on any condition or calculation you
define and map it to an Employee Central field.
For more information about field mappings, refer to section Define Template Groups [page 21].
2.
Optional: If you want to to overwrite the employee master data extracted from the SAP ERP HCM system,
implement the Change of Mapping Result for Employee Replication (EX_ECPAO_ERP_EMP_DATA_MODIFY)
BAdI.
3.
Optional: If you want to define segments of employees whose data is to be replicated to Employee Central,
implement the Validity Periods for Replication of Employee Data to EC (EX_ECPAO_EMP_VALIDITY_TAB)
BAdI.
Using this BAdI, you can classify employee master data extracted from the SAP ERP HCM system as relevant
or not relevant for the replication to Employee Central, based on specific time segments and organizational
criteria. To do so, you define periods in which the data is valid for the replication. In this case, a Data Change
event with the DATAVAL event reason is triggered in Employee Central. Data that is outside these periods is
classified as invalid for the replication. In this case, a Data Change event with the DATINAVAL event reason is
triggered in Employee Central. For more information about these even reasons, refer to section Create Event
Reasons in Employee Central [page 34].
4.
If you have selected the BAdI Mapping mapping mode in the Specify Employee Central Company ID
Customizing activity for the User ID Mapping, User Name Mapping, or Person ID Mapping field, you must
implement the Mapping of User ID, Person ID, and User Name (EX_ECPAO_EMP_USYID_PRN_UNM_MAP) BAdI.
Your BAdI implementation must provide the mapping for all fields for which you have selected this mapping
mode.
4.2 Setting up Employee Central for the Replication of
Employee Data
4.2.1
Create Event Reasons in Employee Central
Context
You must create new event reasons in Employee Central to handle the HR processes related to the replication of
employee master data from SAP ERP HCM to Employee Central. The event reasons are needed for special cases
34
© 2014 SAP SE or an SAP affiliate company. All rights reserved.
Employee Central and SAP ERP: Side-by-Side Deployment Model
Replication of Employee Master Data from the On-Premise SAP ERP HCM System to
Employee Central
such as the rehire process. For more information, refer to section HR Business Processes in the Side-by-Side
Deployment Model [page 53].
Procedure
1.
Create a PSEUDO_HIRE event reason for the Hire event using the Active employee status as shown here:
This event reason is used when you have specified a cutoff date for the template group and the cutoff date is
after the hire date of the employee. For more information, refer to the following sections:
2.
○
Define Template Groups [page 21]
○
Rehiring an Employee in SAP ERP HCM Who Was Previously Mastered in SAP ERP HCM [page 56]
Create a DATAVAL event reason for the Data Change event using the Active employee status as shown here:
Employee Central and SAP ERP: Side-by-Side Deployment Model
© 2014
Replication of Employee Master Data from the On-Premise SAP ERP HCM System to Employee
Central
SAP SE or an SAP affiliate company. All rights reserved.
35
This event reason is used when the employee master data being extracted is valid for the replication to
Employee Central, based on the implementation of the Validity Periods for Replication of Employee Data to EC
(EX_ECPAO_EMP_VALIDITY_TAB) BAdI. For more information, refer to section Implement Business Add-Ins
for the Replication of Employee Master Data [page 33].
3.
Create a DATAINVAL event reason for the Data Change event using the Furlough employee status as shown
here:
This event reason is used when the employee master data being extracted is not valid for the replication to
Employee Central, based on the implementation of the Validity Periods for Replication of Employee Data to EC
(EX_ECPAO_EMP_VALIDITY_TAB) BAdI. For more information, refer to section Implement Business Add-Ins
for the Replication of Employee Master Data [page 33]
4.3
Master Data Replication Information
4.3.1
Standard Employee Central Fields
The tables below list the standard fields for the CSV-based and OData-based entities in Employee Central.
36
© 2014 SAP SE or an SAP affiliate company. All rights reserved.
Employee Central and SAP ERP: Side-by-Side Deployment Model
Replication of Employee Master Data from the On-Premise SAP ERP HCM System to
Employee Central
Table 1: CSV-Based Entities
Basic Im­
port
Biographical
Information
Employment Job History
Details
Personal
Informa­
tion
Global As­
signment
Email Info
Phone Info
STATUS
user-id
user-id
manager-id
start-date
user-id
person­
O8˜áÀk3ñ²;<;8ë)5^
son-id-ex­
ternal
person­
O8˜áÀk3ñ²;<;8ë)5^
son-id-ex­
ternal
USERID
person-id-ex­ start-date
ternal
start-date
person­
O8˜áÀk3ñ²;<;8ë)5^
son-id-ex­
ternal
person-idexternal
SFO­
O8áÌ€y3ÿ²;<˙8ë)5^
Phone
FIRST­
NAME
person-idexternal
LASTNAME
originalStart­
Date
user-id
start-date
plannedend-date
MI
HR
manager-id
USERNAME
Table 2: OData-Based Entities
SFO­
Data.User
SFO­
O8áÌ€y3ÿ²;<˙8ë)5^
Person
SFO­
O8áÌ€y3ÿ²;<8ã'K
O8&áè€`3î²y<$8÷'K
ment
SFO­
O8áÌ€y3ÿ²;<8ã+5^
Job
SFO­
O8áÌ€y3ÿ²;<˙8ë)5^
Personal
SFO­
O8áÌ€y3ÿ²;<8ã+5^
O8áÁ€b3ü²t<'8Ï(5^
signment
SFO­
O8áÌ€y3ÿ²;<˙8ë)˝�
mail
status
userId
userId
managerId
startDate
userId
personIdEx­ personIdEx­
ternal
ternal
userId
personIdEx­ startDate
ternal
startDate
personIdEx­ personIdEx­
ternal
ternal
firstName
personIdEx­ userId
ternal
startDate
lastName
original­
StartDate
planne­
dEndDate
seqNumber
username
4.3.2 Standard Mapping of SAP ERP HCM Fields to Employee
Central Fields
The following mappings of SAP ERP HCM fields and Employee Central fields are considered to be standard
mappings.
Employee Central and SAP ERP: Side-by-Side Deployment Model
© 2014
Replication of Employee Master Data from the On-Premise SAP ERP HCM System to Employee
Central
SAP SE or an SAP affiliate company. All rights reserved.
37
Caution
These fields aren't available for configuration in the Customizing of your template groups, independent of
which Employee Central import object type you assign.
Sequence No.
Employee Central Field
SAP ERP HCM Field
1
user_id
Personnel Number (PERNR) of the
employee
2
person_id_external
Central Person (CP) of the employee
3
start_date
Hire date of the employee
4
originalStartDate
First hire date of the employee
5
manager_id
The ID of the employee's manager is not
available in a standard infotype in SAP
ERP HCM. Instead, it's read from the
Manager Assignments for Employee
Replication (ECPAO_EE_MGNR) table. In
this table, the B012 relationships are
stored for the organizational unit to
which the employee belongs. For more
information, refer to section Determine
the Employees' Managers [page 26].
4.3.3 Sample Mapping of SAP ERP HCM Fields to Employee
Central Fields
The template groups SBS_CSV_MODEL_TMPL and SBS_MODEL_WS are delivered with the sample Customizing.
These template groups provide some mappings of SAP ERP HCM fields and Employee Central fields for the
following Employee Central entities:
●
●
SBS_CSV_MODEL_TMPL:
○
Biographical Information
○
Employment Details
○
Job History
○
Personal Information
SBS_MODEL_WS:
○
SFOData.PerPerson
○
SFOData.EmpEmployment
○
SFOData.EmpJob
○
SFOData.PerPersonal
○
SFOData.EmpGlobalAssignment
○
SFOData.PerEmail
○
SFOData.PerPhone
You can use the delivered sample Customizing as an example for your own field mappings.
38
© 2014 SAP SE or an SAP affiliate company. All rights reserved.
Employee Central and SAP ERP: Side-by-Side Deployment Model
Replication of Employee Master Data from the On-Premise SAP ERP HCM System to
Employee Central
4.4
Setting up the Middleware
You need the middleware to transfer employee master data from SAP ERP HCM to Employee Central using a
synchronous Web service call. For more information about the ways data is transferred to Employee Central, refer
to section Communication Channels for the Replication of Employee Master Data.
The middleware is set up by Professional Services or consultants.
4.5 Setting up Employee Central Time Off for Employees
Mastered in SAP ERP HCM
To use time off in Employee Central for employees whose data is mastered in SAP ERP HCM and replicated to
Employee Central, carry out the steps described below.
4.5.1
Create a Business Rule
Context
You create a business rule in Employee Central to fill the following fields of the Job Information entity with default
values when the rule is successfully executed for an employee:
●
Holiday Calendar
●
Work Schedule
●
Time Profile
Procedure
1.
Go to Administration Tools.
2.
In the Company Processes & Cycles portlet, select
3.
Create a business rule based on your requirements.
In this example, the ruleTime rule is executed for all employees belonging to the ACE_DEU company. It fills the
Holiday Calendar, Work Schedule, and Time Profile fields with the values shown here:
Company Settings
Configure Business Rules .
Employee Central and SAP ERP: Side-by-Side Deployment Model
© 2014
Replication of Employee Master Data from the On-Premise SAP ERP HCM System to Employee
Central
SAP SE or an SAP affiliate company. All rights reserved.
39
Next Steps
Make sure that Professional Services or a consultant assign this rule in the Succession Data Model.
4.5.2
Configure the Company System Settings
Procedure
1.
Go back to Administration Tools.
2.
In the Company Processes & Cycles portlet, select
Company Settings
Company System and Logo
Settings .
3.
40
Make sure that the Enable rules execution during Job Information import checkbox is selected as shown here:
© 2014 SAP SE or an SAP affiliate company. All rights reserved.
Employee Central and SAP ERP: Side-by-Side Deployment Model
Replication of Employee Master Data from the On-Premise SAP ERP HCM System to
Employee Central
4.5.3
Check the Company Code Mapping
Procedure
1.
In your SAP ERP HCM system, go to the Maintain HR Master Data (PA30) transaction.
2.
Search for the employee whose data you want to replicate to Employee Central.
Employee Central and SAP ERP: Side-by-Side Deployment Model
© 2014
Replication of Employee Master Data from the On-Premise SAP ERP HCM System to Employee
Central
SAP SE or an SAP affiliate company. All rights reserved.
41
3.
42
Display the Organizational Assignment (0001) infotype and check the value stored in the Company Code field.
© 2014 SAP SE or an SAP affiliate company. All rights reserved.
Employee Central and SAP ERP: Side-by-Side Deployment Model
Replication of Employee Master Data from the On-Premise SAP ERP HCM System to
Employee Central
4.
Go to the Define Value Mapping Details Customizing activity and check if this company code (stored in the
ERP Key field) is mapped to the company (stored in the EC Key field) that is configured in your business rule.
For more information, refer to section Define Value Mappings [page 18].
Caution
In Employee Central, the company is represented by an instance of the Legal Entity foundation object.
Make sure that both the legal entity code in Employee Central and the Employee Central key that you
specify in the value mapping Customizing are in upper case.
4.5.4
Configure the Template Group
Procedure
1.
Go to the Map EC Templates and SAP ERP Templates for Employee Replication Customizing activity.
For more information about this Customizing activity, refer to section Define Template Groups [page 21].
2.
3.
Go to the Primary Mapping view of your template group and add the following fields:
○
Holiday Calendar
○
Time Profile
○
Work Schedule
Select the BAdI Mapping mapping mode for each field.
Employee Central and SAP ERP: Side-by-Side Deployment Model
© 2014
Replication of Employee Master Data from the On-Premise SAP ERP HCM System to Employee
Central
SAP SE or an SAP affiliate company. All rights reserved.
43
Note
You don't have to fill these fields with content from SAP ERP HCM since the business rule you have created
in Employee Central provides the values for these fields.
4.5.5 Map the Employee Central Time Types to SAP ERP
Absence Types
Procedure
1.
In the SAP Customizing Implementation Guide structure, open
Administration
Interfaces and Integration
Employee Central
44
Assignment of Code Values
© 2014 SAP SE or an SAP affiliate company. All rights reserved.
Personnel Management
Personnel
Integration of SAP ERP HR Master Data and SuccessFactors
Define Mapping Code Value Lists .
Employee Central and SAP ERP: Side-by-Side Deployment Model
Replication of Employee Master Data from the On-Premise SAP ERP HCM System to
Employee Central
2.
Map the time types you use in Employee Central to the absence types used in SAP ERP HCM.
Note
If the time type name isn't longer than four characters, you can use the Employee Central value directly
and don't need to define a mapping.
Employee Central and SAP ERP: Side-by-Side Deployment Model
© 2014
Replication of Employee Master Data from the On-Premise SAP ERP HCM System to Employee
Central
SAP SE or an SAP affiliate company. All rights reserved.
45
To see which SAP ERP HCM absence types you can use, go to the Display HR Master Data (PA20) transaction
and display the subtypes of the Absences (2001) infotype.
3.
46
In the Customizing activity, you can also find the code list ID for each country. To determine the absence type,
the country from the employee's Job Information record is evaluated that is valid at the end date of the
absence.
© 2014 SAP SE or an SAP affiliate company. All rights reserved.
Employee Central and SAP ERP: Side-by-Side Deployment Model
Replication of Employee Master Data from the On-Premise SAP ERP HCM System to
Employee Central
4.5.6
Set up the Middleware
Context
When an employee whose data is mastered in SAP ERP HCM requests time off in Employee Central, the
middleware replicates the time-off data from Employee Central to the Absences (2001) infotype in SAP ERP HCM.
The middleware is set up by Professional Services or consultants.
4.5.7
Extract Employee Data
Procedure
1.
Go to the ABAP: Program Execution (SA38) transaction.
2.
Execute the Employee Data Extraction (ECPAO_EMPL_EXTRACTION) program for the employee in question.
On the selection screen of the program, specify the template group that you have configured as described in
section Configure the Template Group [page 43].
4.5.8
Request Time Off in Employee Central
Procedure
1.
Check in Employee Central if the time information of employees whose data is mastered in SAP ERP HCM was
updated in the Job Information portlet.
2.
Go to the Manage Time Off portlet of an employee whose data is mastered in SAP ERP HCM and click Request
Time Off.
Employee Central and SAP ERP: Side-by-Side Deployment Model
© 2014
Replication of Employee Master Data from the On-Premise SAP ERP HCM System to Employee
Central
SAP SE or an SAP affiliate company. All rights reserved.
47
48
© 2014 SAP SE or an SAP affiliate company. All rights reserved.
Employee Central and SAP ERP: Side-by-Side Deployment Model
Replication of Employee Master Data from the On-Premise SAP ERP HCM System to
Employee Central
Next Steps
The middleware replicates the time-off data from Employee Central to the Absences (2001) infotype in SAP ERP
HCM.
Employee Central and SAP ERP: Side-by-Side Deployment Model
© 2014
Replication of Employee Master Data from the On-Premise SAP ERP HCM System to Employee
Central
SAP SE or an SAP affiliate company. All rights reserved.
49
4.5.9
HCM
Check Replicated Time-Off Information in SAP ERP
Context
Check if the time-off data of an employee whose data is mastered in SAP ERP HCM is replicated from Employee
Central to the Absences (2001) infotype in SAP ERP HCM.
Procedure
1.
In your SAP ERP HCM system, go to the Maintain HR Master Data (PA30) transaction.
2.
Search for the employee whose data was replicated to Employee Central.
3.
Display the Absences (2001) infotype to see the latest time-off request.
50
© 2014 SAP SE or an SAP affiliate company. All rights reserved.
Employee Central and SAP ERP: Side-by-Side Deployment Model
Replication of Employee Master Data from the On-Premise SAP ERP HCM System to
Employee Central
4.
Click Infotype Overview to see all of the employee's time-off requests.
Employee Central and SAP ERP: Side-by-Side Deployment Model
© 2014
Replication of Employee Master Data from the On-Premise SAP ERP HCM System to Employee
Central
SAP SE or an SAP affiliate company. All rights reserved.
51
52
© 2014 SAP SE or an SAP affiliate company. All rights reserved.
Employee Central and SAP ERP: Side-by-Side Deployment Model
Replication of Employee Master Data from the On-Premise SAP ERP HCM System to
Employee Central
5
HR Business Processes in the Side-by-Side
Deployment Model
In this section, you can find out how the HR business processes work when you use the distributed scenario in the
side-by-side deployment model. For more information about this scenario, refer to section Introduction [page 5].
5.1
Prerequisites and Restrictions
Make sure that the following prerequisites are fulfilled:
●
You use Employee Central as a global HCM system that stores the master data of all employees, including the
employees mastered in SAP ERP HCM.
●
SAP ERP HCM only stores the master data of the employees that are mastered in SAP ERP HCM.
●
Employee master data is replicated from SAP ERP HCM to Employee Central, but not from Employee Central
to SAP ERP HCM.
●
You identify the system in which an employee's data is mastered based on the employee's country
assignment.
●
The number ranges you use in SAP ERP HCM and Employee Central don't overlap.
○
To define number ranges in Employee Central, go to Administration Tools. In the Company Processes &
Cycles portlet, select Company Settings Company System and Logo Settings . On the Company
System Setting page, fill in the Next Person Id Assigned field.
○
To define number ranges in SAP ERP HCM, go to Customizing for Personnel Management. Under
Personnel Administration Basic Settings , carry out the Maintain number range intervals for
personnel numbers and Determine defaults for number ranges Customizing activites.
●
You use role-based permissions to make sure that an employee's data can only be changed in the system of
record.
Recommendation
We recommend to use the following standard mappings:
●
The central person from SAP ERP HCM should be mapped to the person_id_external field in Employee
Central.
Employee Central and SAP ERP: Side-by-Side Deployment Model
HR Business Processes in the Side-by-Side Deployment Model
© 2014 SAP SE or an SAP affiliate company. All rights reserved.
53
●
The personnel number from SAP ERP HCM should be mapped to the user_id field in Employee Central.
For more information about the standard mappings, refer to section Standard Mapping of SAP ERP HCM Fields
to Employee Central Fields [page 37]. If you use other mappings, make sure that a unique ID is used when you
replicate an employee's data from SAP ERP HCM to Emplyoee Central. For more information about the
mapping options, refer to section Define Employee Central Company [page 15].
Restriction
The distributed scenario of the side-by-side deployment model currently doesn't support all business
processes. The following processes, for example, aren't supported:
●
Concurrent employment (employees can be concurrently employed in either SAP ERP HCM or Employee
Central, but their data can't be replicated from one system to the other)
●
Rehiring an employee in SAP ERP HCM whose data was previously mastered in Employee Central
●
Assigning an employee globally in SAP ERP HCM and in Employee Central
5.2
Hire
You can hire new employees either in SAP ERP HCM or in Employee Central.
5.2.1
Hiring a New Employee in SAP ERP HCM
You hire a new employee in SAP ERP HCM and replicate the employee's master data to Employee Central. In
Employee Central, the personnel number (PERNR) is mapped to the user_id field and the central person (CP) is
mapped to the person_id_external field. The employee's data is stored in Employee Central according to the field
mapping that you have defined in Customizing. For more information, refer to section Define Template Groups
[page 21].
Note
In SAP ERP HCM, you can define how the hire date is determined using the Rule for Determining Entry Date
(ENTRY) feature. The employee's hire date provided by this feature is replicated to Employee Central.
If you have stored your employees' data in SAP ERP HCM for several years already and want to start the employee
master data replication from SAP ERP HCM to Employee Central at a certain point in time, you can define a cutoff
date. If you use the cutoff date, the Hire Date and Original Start Date fields in Employee Central are filled in
different ways, depending on whether the employee’s hire date is before or after the cutoff date:
●
54
If the cutoff date is before the hire date in SAP ERP HCM, the Hire Date and Original Start Date fields in
Employee Central are both filled with the SAP ERP HCM hire date.
© 2014 SAP SE or an SAP affiliate company. All rights reserved.
Employee Central and SAP ERP: Side-by-Side Deployment Model
HR Business Processes in the Side-by-Side Deployment Model
●
If the cutoff date is after the hire date in SAP ERP HCM, the SAP ERP HCM hire date is mapped to the Original
Start Date field and the cutoff date is mapped to the Hire Date field in Employee Central.
●
If the hire date is before the cutoff date and data is changed in SAP ERP HCM before the cutoff date, the SAP
ERP HCM hire date is mapped to the Original Start Date field and the cutoff date is mapped to the Hire Date
field in Employee Central. The employee has only one Job Information record in Employee Central
representing the data valid at the cutoff date.
Employee Central and SAP ERP: Side-by-Side Deployment Model
HR Business Processes in the Side-by-Side Deployment Model
© 2014 SAP SE or an SAP affiliate company. All rights reserved.
55
5.2.2
Hiring a New Employee in Employee Central
The hire process in Employee Central works as usual. Employees that are mastered in Employee Central aren't
replicated to SAP ERP HCM.
5.3
Rehire
You can rehire employees either in SAP ERP HCM or in Employee Central. The business processes differ
depending on where the employee's data was mastered before.
5.3.1
Rehiring an Employee in SAP ERP HCM Who Was
Previously Mastered in SAP ERP HCM
When you try to hire a person in SAP ERP HCM, a duplicate check is carried out. If an employee with the same
name and birth date already existed before, you have to carry out a rehire action instead of the hire action. When
you rehire an employee, he or she gets the same personnel number (PERNR) as before, which is assigned to the
same central person (CP). Once the employee is rehired, you can replicate the employee's master data to
Employee Central.
Caution
Since employees aren't replicated from Employee Central to SAP ERP HCM, the duplicate check doesn't cover
employees whose data is mastered in Employee Central. Therefore, you have to manually double-check if an
employee already exists in Employee Central.
56
© 2014 SAP SE or an SAP affiliate company. All rights reserved.
Employee Central and SAP ERP: Side-by-Side Deployment Model
HR Business Processes in the Side-by-Side Deployment Model
If you use the cutoff date, the following situations can occur:
●
If the cutoff date is after the rehire date, meaning, the employee was hired, terminated, and then rehired in
SAP ERP HCM before the cutoff date, the first hire date (first entry into the company) is mapped to the
Original Start Date field in Employee Central. The cutoff date is mapped to the Hire Date field in Employee
Central. You can still use the date of the employee's first entry into the company to calculate, for example, the
employee's seniority, since this date is stored in the Original Start Date field.
Since this is not a usual hire in Employee Central (because the employee was already hired before), a Hire
event with the PSEUDO_HIRE event reason is carried out.
●
If the cutoff date is between the termination and the rehire dates in SAP ERP HCM, the first hire date (first
entry into the company) is mapped to the Original Start Date field and the rehire date (second entry into the
company) is mapped to the Hire Date field in Employee Central.
A Hire event with the PSEUDO_HIRE event reason is carried out in Employee Central.
For more information about the cutoff date, refer to section Hiring a New Employee in SAP ERP HCM [page 54].
Employee Central and SAP ERP: Side-by-Side Deployment Model
HR Business Processes in the Side-by-Side Deployment Model
© 2014 SAP SE or an SAP affiliate company. All rights reserved.
57
Related Information
Create Event Reasons in Employee Central [page 34]
5.3.2 Rehiring an Employee in Employee Central Who Was
Previously Mastered in Employee Central
The rehire process in Employee Central works as usual. Employees whose data is mastered in Employee Central
aren't replicated to SAP ERP HCM.
5.3.3 Rehiring an Employee in Employee Central Who Was
Previously Mastered in SAP ERP HCM
When an employee leaves the company, you carry out a Leaving action in SAP ERP HCM and replicate the
employee's master data to Employee Central. In Employee Central, a Termination event is carried out and the
employee is set to inactive.
When you try to rehire the same person in Employee Central, the duplicate check finds this employee because his
or her data was replicated from SAP ERP HCM. You therefore create a new employment in Employee Central
using the Rehire event.
Note
A new user is created in Employee Central for the new employment. The employee rehired in Employee Central
isn't replicated to SAP ERP HCM.
5.3.4 Rehiring an Employee in SAP ERP HCM Who Was
Previously Mastered in Employee Central
The side-by-side deployment model currently doesn't support this business scenario.
5.4
Transfer
You can transfer employees either within SAP ERP HCM or within Employee Central. In SAP ERP HCM, the
transfer is called organizational reassignment.
58
© 2014 SAP SE or an SAP affiliate company. All rights reserved.
Employee Central and SAP ERP: Side-by-Side Deployment Model
HR Business Processes in the Side-by-Side Deployment Model
5.4.1
Transferring an Employee Within SAP ERP HCM
When you carry out an organizational reassignment for an employee whose data is mastered in SAP ERP HCM,
the Organizational Reassignment (0001) infotype is changed. An organizational reassignment means that
●
the employee’s country assignment and personnel number (PERNR) stay the same
●
only one personnel number exists for the employee
You can replicate the changes regarding the organizational assignment to Employee Central. In Employee Central,
a Data Change event with the DATAREORG event reason is carried out and a new Job Information record is created.
The date of the organizational reassignment in SAP ERP HCM is used as the effective start date of this Job
Information record.
5.4.2
Transferring an Employee Within Employee Central
The transfer process in Employee Central works as usual. Employees whose data is mastered in Employee Central
aren't replicated to SAP ERP HCM.
5.5
International Transfer
You can transfer employees between countries that are mastered in SAP ERP HCM or in Employee Central.
5.5.1
Transferring an Employee From a Country Mastered in
SAP ERP HCM to Another Country Mastered in SAP ERP HCM
When you transfer an employee in SAP ERP HCM from one country to another, you usually carry out a Leaving
action in the original country and a Hiring action in the new country. This means that the employee gets a new
personnel number (PERNR) which is assigned to the same central person (CP).
When extracting data, the Employee Data Extraction (ECPAO_EMPL_EXTRACTION) program analyzes the
personnel numbers assigned to one central person. The personnel numbers are handled together and the data of
both is transferred to the same Job Information and Job History records in Employee Central if the following
conditions are fulfilled for both personnel numbers:
●
They are assigned to different countries.
●
Only one of them is active.
●
The Leaving and Hiring actions were carried out for them.
In Employee Central, a Transfer event is carried out with an international transfer event reason.
Employee Central and SAP ERP: Side-by-Side Deployment Model
HR Business Processes in the Side-by-Side Deployment Model
© 2014 SAP SE or an SAP affiliate company. All rights reserved.
59
5.5.2 Transferring an Employee From a Country Mastered in
Employee Central to Another Country Mastered in Employee
Central
The international transfer process in Employee Central works as usual. Employees whose data is mastered in
Employee Central aren't replicated to SAP ERP HCM.
5.5.3 Transferring an Employee from a Country Mastered in
SAP ERP HCM to a Country Mastered in Employee Central
You carry out a Leaving action for the original country in SAP ERP HCM, which has a date in the future. You
replicate the employee's master data to Employee Central. In Employee Central, a Termination event is carried
out for the original country and the employee is set to inactive for the future. You create an additional
employment in Employee Central to assign the employee to the new country.
Note
A new user is created in Employee Central for the new employment.
5.6
Global Assignment
An employee can be globally assigned either within SAP ERP HCM or within Employee Central.
5.6.1
Assigning an Employee Globally Within SAP ERP HCM
In SAP ERP HCM, you store information about an employee's global assignment in the following infotypes:
●
To determine which is the host and which the home assignment, you use the Details on Global Assignment
(0710) infotype.
●
To determine which personnel number is used to send biographical and personal information to Employee
Central, you use the Main Personnel Assignment (0712) infotype with the SuccessFactors (SFSF) subtype.
The data from both the host and the home assignments is replicated to Employee Central. The second
assignment is sent using a separate API. In Employee Central, the employee's biographical and personal
information is taken from the personnel number that you have marked as the main personnel assignment in SAP
ERP HCM.
60
© 2014 SAP SE or an SAP affiliate company. All rights reserved.
Employee Central and SAP ERP: Side-by-Side Deployment Model
HR Business Processes in the Side-by-Side Deployment Model
5.6.2 Assigning an Employee Globally within Employee
Central
Global assignment management in Employee Central works as usual. Employees whose data is mastered in
Employee Central aren't replicated to SAP ERP HCM.
5.6.3 Assigning an Employee Globally in SAP ERP HCM And
Employee Central
The side-by-side deployment model currently doesn't support this business scenario.
5.7
Termination
You can terminate employees either in SAP ERP HCM or in Employee Central.
5.7.1
Terminating an Employee Mastered in SAP ERP HCM
When you terminate an employee in SAP ERP HCM, the information about the termination is replicated to
Employee Central. This is to ensure that the employee is also terminated in Employee Central and becomes
inactive there. When you carry out the Leaving action in SAP ERP HCM, the employee's employment status is
changed to Withdrawn. When the termination is replicated to Employee Central, a Termination event with the
Termination event reason is carried out and a new Job Information record is created.
5.7.2 Terminating an Employee Mastered in Employee
Central
The termination process in Employee Central works as usual. Employees whose data is mastered in Employee
Central aren't replicated to SAP ERP HCM.
Employee Central and SAP ERP: Side-by-Side Deployment Model
HR Business Processes in the Side-by-Side Deployment Model
© 2014 SAP SE or an SAP affiliate company. All rights reserved.
61
6 Integration of the Employee Central UI
with the On-Premise SAP ERP HCM System
In the distributed scenario of the side-by-side deployment model, managers and employees can use the Success
Factors homepage as a global UI hub. They can view data or trigger data changes for employees whose data is
mastered in SAP HCM ERP using the navigation on the Employee Central UI.
In the consolidated scenario of the side-by-side deployment model, the UI navigation can be used to trigger
processes in the local SAP HCM ERP system from the Employee Central UI. In this scenario, all global processes
run directly in Employee Central.
Note
You only need to perform the steps described in this section if you want to use Employee Central as the UI
navigation hub. If you want to use the distributed scenario of the side-by-side deployment model only to
replicate employee master data from SAP ERP HCM to Employee Central, you don't need to set up the UI
integration.
You can also use Employee Central as the UI navigation hub for the consolidated scenario of the side-by-side
deployment model.
For more information about the scenarios, refer to section Introduction [page 5].
Restriction
Using Employee Central as the UI navigation hub for Employee Self-Service and Manager Self-Service use
cases is available as a public beta shipment only.
6.1 Configuring the Third-Party System in the SAP ERP HCM
System
You only need to configure the SAP ERP HCM system for Manager Self-Service use cases. For Employee SelfService use cases, no configuration steps are needed in the SAP ERP HCM system. You can directly continue with
the configuration steps described in section Configuring the Third-Party System in Employee Central [page 69].
62
© 2014 SAP SE or an SAP affiliate company. All rights reserved.
Employee Central and SAP ERP: Side-by-Side Deployment Model
Integration of the Employee Central UI with the On-Premise SAP ERP HCM System
6.1.1
Create an SICF Handler
Context
For Manager Self-Service use cases, you must create a new SICF handler in the SAP ERP HCM system, which can
be called in Employee Central within the iFrame on the Profile Update page.
Note
The standard handler class CL_SFIUI_REDIRECT_HANDLER displays the HR Processes and Forms process
overview for processes using forms based on Adobe Forms. This handler class performs the following actions:
1.
It takes into account the parameters users_sys_id, employment_id, and company_code and uses them to
retrieve the personnel number (PERNR) of the employee whose data is to be changed.
2.
It writes the personnel number to the memory ID MSS which is used by HCM Processes and Forms for the
user who is logged in.
3.
It redirects to the standard Web Dynpro application ASR_PROCESS_EXECUTE, which displays all available
processes for the selected employee.
If you want to use another standard or customer-specific Web Dynpro application, you can use the
standard handler class as a template that you can copy and adapt to your needs.
Procedure
1.
Log on to your SAP ERP HCM system, go to the Maintain Services (SICF) transaction, and press F8 .
Employee Central and SAP ERP: Side-by-Side Deployment Model
Integration of the Employee Central UI with the On-Premise SAP ERP HCM System
© 2014 SAP SE or an SAP affiliate company. All rights reserved.
63
2.
Select the place in the tree where the new service should be created and click Wizard: Create Service.
3.
In the wizard, enter the following data:
4.
64
○
Create Host/Service/Internal Alias: Select the Service option
○
Service Name: Enter a name, such as redirect.
○
Description: Enter a description, such as Redirect Handler for EC UI Integration.
○
Handler: Enter CL_SFIUI_REDIRECT_HANDLER.
Save and activate your service.
© 2014 SAP SE or an SAP affiliate company. All rights reserved.
Employee Central and SAP ERP: Side-by-Side Deployment Model
Integration of the Employee Central UI with the On-Premise SAP ERP HCM System
6.1.2 Optional: Adjust the ASR_PROCESS_EXECUTE Web
Dynpro Application
Context
The standard ASR_PROCESS_EXECUTE Web Dynpro application is called in the CL_SFIUI_REDIRECT_HANDLER
handler class to execute the process that the user has selected on the Employee Central user interface. In the
standard, this Web Dynpro application displays a roadmap in the upper section of the screen. If you would like to
have more space in the iFrame for displaying the process steps, you can hide this roadmap. To do this, you create
an enhancement implementation.
Procedure
1.
Start the Object Navigator (SE80) transaction and display the HRASR00_PROCESS_EXECUTE Web Dynpro
component.
2.
Double-click it, then click Enhance or press CTRL + F4 .
3.
In the Select or Create Enhancement Implementation popup, click Create Enhancement Implementation or
press F8 .
4.
Enter a name and a short text and press Enter .
Employee Central and SAP ERP: Side-by-Side Deployment Model
Integration of the Employee Central UI with the On-Premise SAP ERP HCM System
© 2014 SAP SE or an SAP affiliate company. All rights reserved.
65
5.
Save your enhancement implementation in a suitable package.
6.
Double-click the PROCESS_START view and click the Methods tab.
7.
Click Enhance again and create a post-exit for the ROADMAP_STEP_VISIBILITY method:
66
© 2014 SAP SE or an SAP affiliate company. All rights reserved.
Employee Central and SAP ERP: Side-by-Side Deployment Model
Integration of the Employee Central UI with the On-Premise SAP ERP HCM System
a) Click Create in the corresponding column.
b) Paste the following code to the method (if necessary, adapt it to suit your requirements):
Code Syntax
DATA node_roadmap
TYPE REF TO if_wd_context_node.
DATA elem_roadmap
TYPE REF TO if_wd_context_element.
DATA stru_roadmap
TYPE if_process_start=>element_roadmap.
DATA node_ui_parameter TYPE REF TO if_wd_context_node.
DATA elem_ui_parameter TYPE REF TO if_wd_context_element.
DATA stru_ui_parameter TYPE if_process_start=>element_ui_parameter.
* Roadmap visibility
node_roadmap = wd_context->get_child_node( name =
if_process_start=>wdctx_roadmap ).
elem_roadmap = node_roadmap->get_element(
).
elem_roadmap->get_static_attributes( importing static_attributes =
stru_roadmap ).
stru_roadmap-is_roadmap_visible = wd_assist->false.
elem_roadmap->set_static_attributes( static_attributes = stru_roadmap ).
* Title visibility
Employee Central and SAP ERP: Side-by-Side Deployment Model
Integration of the Employee Central UI with the On-Premise SAP ERP HCM System
© 2014 SAP SE or an SAP affiliate company. All rights reserved.
67
node_ui_parameter = wd_context->get_child_node( name =
if_process_start=>wdctx_ui_parameter ).
elem_ui_parameter = node_ui_parameter->get_element(
).
elem_ui_parameter->get_static_attributes( importing static_attributes =
stru_ui_parameter ).
stru_ui_parameter-is_title_visible = wd_assist->false.
elem_ui_parameter->set_static_attributes( static_attributes =
stru_ui_parameter ).
c) To save your changes, press CTRL + S .
d) To check the method, press CTRL + F2 .
e) To activate the method, press CTRL + F3 .
8.
Carry out the steps described above again to create a second post-exit for the SET_BUTTON_VISIBILITY
method using the following code (if necessary, adapt it to suit your requirements):
Code Syntax
DATA node_buttons TYPE REF TO if_wd_context_node.
DATA elem_buttons TYPE REF TO if_wd_context_element.
68
© 2014 SAP SE or an SAP affiliate company. All rights reserved.
Employee Central and SAP ERP: Side-by-Side Deployment Model
Integration of the Employee Central UI with the On-Premise SAP ERP HCM System
DATA buttons
TYPE if_process_start=>element_buttons.
node_buttons = wd_context->get_child_node( name =
if_process_start=>wdctx_buttons ).
elem_buttons = node_buttons->get_element(
).
elem_buttons->get_static_attributes( importing static_attributes = buttons ).
buttons-is_save_draft_visible = abap_false.
elem_buttons->set_static_attributes( static_attributes = buttons ).
6.2
Configuring the Third-Party System in Employee Central
Make sure that the following steps are carried out by Professional Services or consultants:
●
The UI integration has to be activated in Provisioning.
●
A custom field has to be created in the Succession Data Model, which contains the information about the
third-party system
6.2.1
Create a Picklist for the RuleType Field
Procedure
1.
Go to Administration Tools.
2.
In the Company Processes & Cycles portlet, select
3.
Create a picklist for the RuleType field (if it doesn't exist yet) and configure it as shown in this example:
Company Settings
Employee Central and SAP ERP: Side-by-Side Deployment Model
Integration of the Employee Central UI with the On-Premise SAP ERP HCM System
Configure Object Definitions .
© 2014 SAP SE or an SAP affiliate company. All rights reserved.
69
These picklist values represent the events to be used for the business rule that will be triggered.
Note
If there's already a picklist, make sure that it contains the values as shown above.
6.2.2
Create Generic Object Configurations
Procedure
1.
Go back to Administration Tools.
2.
In the Company Processes & Cycles portlet, select
3.
Create a generic object to store the URLs and configure it as shown in this example:
70
© 2014 SAP SE or an SAP affiliate company. All rights reserved.
Company Settings
Configure Object Definitions .
Employee Central and SAP ERP: Side-by-Side Deployment Model
Integration of the Employee Central UI with the On-Premise SAP ERP HCM System
Employee Central and SAP ERP: Side-by-Side Deployment Model
Integration of the Employee Central UI with the On-Premise SAP ERP HCM System
© 2014 SAP SE or an SAP affiliate company. All rights reserved.
71
Caution
Mark cust_URL and cust_URLType as Required in the Details view of the respective field.
Note
You need to define this generic object in the customer namespace.
4.
72
Create a generic object that saves the data about the third-party system and configure it as shown in this
example:
© 2014 SAP SE or an SAP affiliate company. All rights reserved.
Employee Central and SAP ERP: Side-by-Side Deployment Model
Integration of the Employee Central UI with the On-Premise SAP ERP HCM System
Caution
In the Code field, specify exactly the type that is used for the custom field in the data model. For example, if
the data model says type=cust_ThirdPartySystem, enter cust_ThirdPartySystem here.
Employee Central and SAP ERP: Side-by-Side Deployment Model
Integration of the Employee Central UI with the On-Premise SAP ERP HCM System
© 2014 SAP SE or an SAP affiliate company. All rights reserved.
73
Note
You need to define this generic object in the customer namespace.
5.
Create an association with the name cust_thirdPartyURL that links the cust_ThirdPartySystem object to the
cust_ThirdPartyURL object as shown in this example:
6.
Go back to Administration Tools.
7.
In the Company Processes & Cycles portlet, select
8.
Add instances to the cust_ThirdPartySystem object specifying the third-party system information and the
associated URLs as shown in this example:
Employee Files
Manage Data .
Caution
The externalCode field of cust_ThirdPartyURL must not contain spaces. The cust_URLType field must be
filled with the literal ess or mss to specify when which link is displayed. The ess type means that the link is
displayed when the user who is logged on to Employee Central performs an action on his or her own data.
The mss type means that the link is displayed when the user who is logged on to Employee Central changes
data of another user.
74
© 2014 SAP SE or an SAP affiliate company. All rights reserved.
Employee Central and SAP ERP: Side-by-Side Deployment Model
Integration of the Employee Central UI with the On-Premise SAP ERP HCM System
In the cust_URL field(s), enter the URL(s) to your new SICF handler(s) that you’ve created as described in
section Create an SICF Handler. You can also enter links to external services or direct links to applications
within your SAP ERP system.
For URLs with the mss type, Employee Central automatically adds the URL parameter users_sys_id to the
URL before calling the third-party system. This parameter is filled with the employee’s user ID. In addition, the
URL parameters employment_id and company_code are added to ensure that the called application can
identify the person whose data is to be changed.
6.2.3
Configure the Business Rule
Procedure
1.
Go to Administration Tools.
2.
In the Company Processes & Cycles portlet, select
3.
Create an onView rule that fills the custom field created in the Succession Data Model for storing information
about the third-party system based on data that is stored in the employee's Job Information record (such as
the Business Unit), as shown in this example:
Company Settings
Configure Business Rule .
Caution
The rule name must be the same as specified in the Succession Data Model. In the example used in this
guide, the rule name is EMPLOYMENT_ONVIEW.
Employee Central and SAP ERP: Side-by-Side Deployment Model
Integration of the Employee Central UI with the On-Premise SAP ERP HCM System
© 2014 SAP SE or an SAP affiliate company. All rights reserved.
75
6.2.4
You're done! Now Check the Result
Procedure
1.
After executing all steps described above, check the Take Action menu.
2.
If an employee fulfills the conditions defined by the business rule, the Take Action menu will show the entries
you have configured, as shown in this example:
Note
In this example, you see the Take Action menu for Karen Martha Smith. Her menu contains all URLs that
you have configured with the mss type in addition to the standard Employee Central actions (such as Add
Note). You can reduce the number of entries in the Take Action menu using role-based permissions. The
data is filled into the Employment Information object at runtime when the onView rule is executed. It's not
persisted in the database table for employments.
6.2.5 Disabling the Edit Mode for Third-Party System
Records in Employee Central
The conditions you have used to define the rule for setting the Third Party System field value should also be used
to define the target groups for which the edit mode for third-party system data records in Employee Central
76
© 2014 SAP SE or an SAP affiliate company. All rights reserved.
Employee Central and SAP ERP: Side-by-Side Deployment Model
Integration of the Employee Central UI with the On-Premise SAP ERP HCM System
should be enabled or disabled. If you have, for example, used a specific Legal Entity, Business Unit, or Division as
the condition, you should use the same condition to define the target group for which it should not be allowed to
edit the data in Employee Central.
Use role-based permissions to disable the edit mode in Employee Central.
Employee Central and SAP ERP: Side-by-Side Deployment Model
Integration of the Employee Central UI with the On-Premise SAP ERP HCM System
© 2014 SAP SE or an SAP affiliate company. All rights reserved.
77
7
You're done! What’s Next?
7.1
Troubleshooting
7.1.1
Check the Data Replication Results
Context
You can monitor outgoing messages for the replication of employee master data in your SAP ERP HCM system.
Procedure
1.
Go to the SOA Management (SOAMANAGER) transaction.
2.
On the Logs and Traces tab, click SOA Runtime Log/Trace Viewer or SOA Runtime Error Log.
Note
Depending on the release of your SAP ERP HCM system, this option can have different names.
3.
Specify which calls and which time frame you would like to see.
4.
Check the entries for the CO_ECPAO_SFSFGENERIC_UPSERT_RE and CO_ECPAO_GET_EMPLOYEE_KEY_DATA
interfaces.
78
© 2014 SAP SE or an SAP affiliate company. All rights reserved.
Employee Central and SAP ERP: Side-by-Side Deployment Model
You're done! What’s Next?
Important Disclaimers and Legal Information
Coding Samples
Any software coding and/or code lines / strings ("Code") included in this documentation are only examples and are not intended to be used in a productive system
environment. The Code is only intended to better explain and visualize the syntax and phrasing rules of certain coding. SAP does not warrant the correctness and
completeness of the Code given herein, and SAP shall not be liable for errors or damages caused by the usage of the Code, unless damages were caused by SAP
intentionally or by SAP's gross negligence.
Accessibility
The information contained in the SAP documentation represents SAP's current view of accessibility criteria as of the date of publication; it is in no way intended to be a
binding guideline on how to ensure accessibility of software products. SAP in particular disclaims any liability in relation to this document. This disclaimer, however, does
not apply in cases of wilful misconduct or gross negligence of SAP. Furthermore, this document does not result in any direct or indirect contractual obligations of SAP.
Gender-Neutral Language
As far as possible, SAP documentation is gender neutral. Depending on the context, the reader is addressed directly with "you", or a gender-neutral noun (such as "sales
person" or "working days") is used. If when referring to members of both sexes, however, the third-person singular cannot be avoided or a gender-neutral noun does not
exist, SAP reserves the right to use the masculine form of the noun and pronoun. This is to ensure that the documentation remains comprehensible.
Internet Hyperlinks
The SAP documentation may contain hyperlinks to the Internet. These hyperlinks are intended to serve as a hint about where to find related information. SAP does not
warrant the availability and correctness of this related information or the ability of this information to serve a particular purpose. SAP shall not be liable for any damages
caused by the use of related information unless damages have been caused by SAP's gross negligence or willful misconduct. All links are categorized for transparency
(see: http://help.sap.com/disclaimer).
Employee Central and SAP ERP: Side-by-Side Deployment Model
Important Disclaimers and Legal Information
© 2014 SAP SE or an SAP affiliate company. All rights reserved.
79
www.sap.com/contactsap
© 2014 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 http://www.sap.com/corporate-en/legal/copyright/
index.epx for additional trademark information and notices.