employee central and sap erp: side-by-side deployment...

SuccessFactors HCM SuiteQ1 2015 ReleaseDocument Version: 1.0 – February 6, 2015

Employee Central and SAP ERP: Side-by-Side Deployment ModelIntegration Guide - INTERNAL

Content

1 Introduction. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 51.1 Target Group. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6

1.2 Terminology. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6

1.3 Business Scenario: Side-by-Side Deployment Model. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .7

2 Check if the Customer System is Prepared to Integrate with Employee Central. . . . . . . . . . . . . . . 9

3 Replication of Employee Master Data from the On-Premise SAP ERP HCM System to Employee Central. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 11

3.1 Setting up the On-Premise SAP ERP HCM System. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .11

Business Scenario: Employee Data Replication. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 11

Supported Employee Central Entities. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 11

Communication Channels for the Replication of Employee Master Data. . . . . . . . . . . . . . . . . . . . . . 13

Defining Customer-Specific Activities. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 15

3.2 Setting up Employee Central for the Replication of Employee Data. . . . . . . . . . . . . . . . . . . . . . . . . . . . 51

Create Event Reasons in Employee Central. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 51

3.3 Master Data Replication Information. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 53

Standard Employee Central Fields. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 53

Standard Mapping of SAP ERP HCM Fields to Employee Central Fields. . . . . . . . . . . . . . . . . . . . . . 54

Preconfigured Mapping of SAP ERP HCM Fields to Employee Central Fields. . . . . . . . . . . . . . . . . . 54

Sample Mapping of SAP ERP HCM Fields to Employee Central Fields. . . . . . . . . . . . . . . . . . . . . . . 55

3.4 Setting up the Middleware. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 55

Preparing the Middleware System. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 55

Configuring the Middleware System. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 56

Configuring the SAP ERP HCM System. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .59

3.5 Setting up Employee Central Time Off for Employees Mastered in SAP ERP HCM. . . . . . . . . . . . . . . . . 63

Create a Business Rule. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 63

Configure the Succession Data Model. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 64

Configure the Company System Settings. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 65

Check the Company Code Mapping. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 66

Configure the Template Group. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 68

Map the Employee Central Time Types to SAP ERP Absence Types. . . . . . . . . . . . . . . . . . . . . . . . 69

Set up the Middleware. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 72

Extract Employee Data. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 72

Request Time Off in Employee Central. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 72

Check Replicated Time-Off Information in SAP ERP HCM. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 75

2 © 2015 SAP SE or an SAP affiliate company. All rights reserved.Employee Central and SAP ERP: Side-by-Side Deployment Model

Content

4 How to Migrate from Employee Data Integration with the SuccessFactors Talent Suite to Employee Data Integration in the Side-by-Side Deployment Model. . . . . . . . . . . . . . . . . . . . . . . . 78

4.1 Determining the User ID. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 784.2 Determining the Person ID. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 794.3 Handling the Different Integration Scenarios. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 794.4 Switching from One Replication to the Other. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 804.5 Making Additional Customizing Settings. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 804.6 Changing the Employment Status to Inactive Before and to Active Again After Switching from One

Replication to the Other. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 804.7 Constraints. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 81

5 HR Business Processes in the Side-by-Side Deployment Model. . . . . . . . . . . . . . . . . . . . . . . . . . 825.1 Prerequisites and Restrictions. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 825.2 Hire. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 83

Hiring a New Employee in SAP ERP HCM. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 83Hiring a New Employee in Employee Central. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 85

5.3 Rehire. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 85Rehiring an Employee in SAP ERP HCM Who Was Previously Mastered in SAP ERP HCM. . . . . . . . . 85Rehiring an Employee in Employee Central Who Was Previously Mastered in Employee Central. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 87Rehiring an Employee in Employee Central Who Was Previously Mastered in SAP ERP HCM. . . . . . . 87Rehiring an Employee in SAP ERP HCM Who Was Previously Mastered in Employee Central. . . . . . . 87

5.4 Transfer. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 88Transferring an Employee Within SAP ERP HCM. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 88Transferring an Employee Within Employee Central. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .88

5.5 International Transfer. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 88Transferring an Employee from a Country Mastered in SAP ERP HCM to Another Country Mastered in SAP ERP HCM. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 88Transferring an Employee from a Country Mastered in Employee Central to Another Country Mastered in Employee Central. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 89Transferring an Employee from a Country Mastered in SAP ERP HCM to a Country Mastered in Employee Central. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .89Transferring an Employee from a Country Mastered in Employee Central to a Country Mastered in SAP ERP HCM. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 90

5.6 Global Assignment. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 90Assigning an Employee Globally Within SAP ERP HCM. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .90Assigning an Employee Globally Within Employee Central. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 90Assigning an Employee Globally in SAP ERP HCM and Employee Central. . . . . . . . . . . . . . . . . . . . .90

5.7 Concurrent Employment. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 91Concurrently Employing an Employee Within SAP ERP HCM. . . . . . . . . . . . . . . . . . . . . . . . . . . . . .91Concurrently Employing an Employee Within Employee Central. . . . . . . . . . . . . . . . . . . . . . . . . . . 92Concurrently Employing an Employee Within SAP ERP HCM and Employee Central. . . . . . . . . . . . . 92

5.8 Termination. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 92

Employee Central and SAP ERP: Side-by-Side Deployment ModelContent © 2015 SAP SE or an SAP affiliate company. All rights reserved. 3

Terminating an Employee Mastered in SAP ERP HCM. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 92Terminating an Employee Mastered in Employee Central. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 92

6 Integration of the Employee Central UI with the On-Premise SAP ERP HCM System. . . . . . . . . . .936.1 Manager Self-Service Use Cases. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .94

Configuring the UI Integration in the SAP ERP HCM System. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 946.2 Manager Self-Service and Employee Self-Service Use Cases. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 101

Configuring the UI Integration in Employee Central. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .101

7 You're done! What’s Next?. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1097.1 Troubleshooting. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 109

Check the Data Replication Results. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 109

8 Change History. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 110


Content

1 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 Employee Central and 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 several systems of record: Employee Central and one or more SAP ERP HCM systems.This is the scenario that is described in this guide.

NoteSection Integration of the Employee Central UI with the On-Premise SAP ERP HCM System [page 93] of this guide is also valid for the consolidated scenario.

RestrictionThe distributed scenario is released under the following condition: The employee data integration from SAP ERP HCM systems to Employee Central is generally available only for SuccessFactors customers leveraging Performance & Goals, Succession & Development, Employee Profile and Organization Chart as part of the Foundational Capabilities, and the related Reporting capabilities.

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 that we recommend you to set up your different systems.

CautionUsage 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.

Employee Central and SAP ERP: Side-by-Side Deployment ModelIntroduction © 2015 SAP SE or an SAP affiliate company. All rights reserved. 5

http://help.sap.com/disclaimer?site=http://service.sap.com/ec-ondemand

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.

1.1 Target Group

This guide is intended for Professional Services and consultants for fast support of customers and prospective customers.

1.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.

effective dated -- Effective dated Employee Central fields have a history associated with them while non-effective dated fields do not have a history. For example, compensation-specific fields are effective dated while fields like Name and National ID are not effective dated.

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


Introduction

Term Abbreviation Definition

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.

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.

1.3 Business Scenario: Side-by-Side Deployment Model

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.

Employee Central and SAP ERP: Side-by-Side Deployment ModelIntroduction © 2015 SAP SE or an SAP affiliate company. All rights reserved. 7

Some characteristics of the distributed scenario in the side-by-side deployment model are:

● The workforce is split across Employee Central and on-premise SAP ERP HCM. Both systems are used as a system of record depending on the employee's country assignment.

● 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.


Introduction

2 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. Is Employee Central already set up?For more information, see the SuccessFactors Employee Central implementation guide. Find the most current version of this guide on SAP Service Marketplace at http://service.sap.com/ec-ondemand .

2. Is the middleware, Dell Boomi AtomSphere, already set up?3. Do you meet the minimum setup requirements 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 SP09 or higher

4. Are the required SAP Notes installed?Make sure that you have the up-to-date version of each SAP Note, which you can find on SAP Service Marketplace at http://service.sap.com/notes .

Employee Central and SAP ERP: Side-by-Side Deployment ModelCheck if the Customer System is Prepared to Integrate with Employee Central © 2015 SAP SE or an SAP affiliate company. All rights reserved. 9


http://help.sap.com/disclaimer?site=http://service.sap.com/notes

Table 1:

SAP Note Number Title Description Contained in Support Package

2120966 SbS EE ERPtoEC: PaymentInformationDetailV3 replication via ODATA

Previously, the replication of MDF object PaymentInformationDetailV3 via OData failed if the parent MDF object PaymentInformationV3 wasn't upserted. OData API changes are made with this SAP Note so that now PaymentInformationDetailV3 object data can be replicated using OData.

PA_SE_IN 100 SP10

5. Have you already installed the SAP GUI? If not, download it from the SAP Service Marketplace at http://service.sap.com/swdc .


Check if the Customer System is Prepared to Integrate with Employee Central

http://help.sap.com/disclaimer?site=https://service.sap.com/sap/support/notes/2120966

http://help.sap.com/disclaimer?site=http://service.sap.com/swdc

http://help.sap.com/disclaimer?site=http://service.sap.com/swdc

3 Replication of Employee Master Data from the On-Premise SAP ERP HCM System to Employee Central

3.1 Setting up the On-Premise SAP ERP HCM System

3.1.1 Business Scenario: Employee Data Replication

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.

CautionMake sure that the data of employees who are mastered in SAP ERP HCM and replicated to Employee Central can't be edited in Employee Central. Use role-based permissions to disable the edit mode in Employee Central.

3.1.2 Supported Employee Central Entities

Different Employee Central entities form the employee data in Employee Central. You can use the following CSV-based and OData-based entities or generic objects (MDF entities):

Sequence No. CSV Data Import Template OData / MDF Entity

1 Basic Import User

2 Biographical Information PerPerson

3 Personal Information PerPersonal

4 Employment Details EmpEmployment

5 Global Assignment EmpGlobalAssignment

6 Job History EmpJob

Employee Central and SAP ERP: Side-by-Side Deployment ModelReplication of Employee Master Data from the On-Premise SAP ERP HCM System to Employee Central © 2015 SAP SE or an SAP affiliate company. All rights reserved. 11

Sequence No. CSV Data Import Template OData / MDF Entity

7 Email Info PerEmail

8 Phone Info PerPhone

9 Job Relationships EmpJobRelationships

10 Addresses PerAdressDEFLT

11 Compensation Info EmpCompensation

12 Pay Component Recurring EmpPayCompRecurring

13 Pay Component Non Recurring EmpPayCompNonRecurring

14 Payment Information-Details PaymentInformationDetailV3

15 Employment Termination Information EmpEmploymentTermination

Custom generic objects (custom MDF entities) are also supported. For more information, refer to section Replicate Employee Master Data to Custom Entities in Employee Central [page 47].

NoteIn 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 [page 54].

More information about some of these entities:

Basic Import / User

You can't configure the Basic Import template or User entity in the SAP ERP HCM system.

Addresses

In the SAP ERP HCM system, the Addresses (0006) infotype has time constraint 2, which means that there can be gaps between address records. The Employee Central addresses entities are able to handle these gaps, but the user doesn't see them on the UI.

Recurring and non-recurring pay components

For each wage type that you want to replicate to Employee Central, you need to create a separate ERP template and assign it to the Employee Central template, since each wage type is itself a subtype of the Recurring Payments/Deductions (0014) infotype. The wage types include directly- and indirectly-evaluated wage types.

Wage types with time constraint 3 (which means that any number of valid records can exist at any one time) are not supported by Employee Central recurring and non-recurring pay component entities.

12 © 2015 SAP SE or an SAP affiliate company. All rights reserved.

Employee Central and SAP ERP: Side-by-Side Deployment ModelReplication of Employee Master Data from the On-Premise SAP ERP HCM System to

Employee Central

Non-recurring pay components can have a future date.

Payment information

When you import payment information metadata from Employee Central into the SAP ERP HCM system, note that:

● If you use the CSV-based data replication, you only need to import the child entity PaymentInformationDetailV3, since the parent entity Payment InformationV3 associated with this child entity is created automatically during CSV imports.

● If you use the Web service-based data replication, you need to import the parent entity PaymentInformationV3 as well as the associated child entity PaymentInformationDetailV3.

For more information refer to section Import Metadata from Employee Central [page 20].

The new MDF-based Payment Information in Employee Central has to be enabled in Provisioning. For more information refer to section Setting up MDF-based Payment Information in the SuccessFactors Employee Central implementation guide. Find the most current version of this guide on SAP Service Marketplace at http://service.sap.com/ec-ondemand .

3.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 CentralTo 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




CSV-Based Employee Data Extraction

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.

Web Service-Based Employee Data Extraction

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

Related Information

Define Template Groups [page 35]Extract Employee Master Data [page 43]Setting up the Middleware [page 55]

3.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


Customizing Implementation Guide structure, open Personnel Management Personnel AdministrationInterfaces and Integration Integration of SAP ERP HCM to SuccessFactors Employee Central Side by Side :



Employee Central

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

3.1.4.1 Import Default Customizing Into Your Working Client in the SAP ERP HCM System

Context

The SAP reference client (000) contains default Customizing settings, which you can copy into other clients. To copy the entries delivered by SAP to the working client that you use in your SAP ERP HCM system for the employee master data, carry out the steps described below.

Procedure

1. Create an RFC connection from client 000 (the comparison client) to your working client.a. Log on to client 000.b. Go to the Configuration of RFC Connections (SM59) transaction.c. Create an ABAP connection to your working client.d. Log off from client 000.

2. Copy the view and view cluster entries from client 000 to your working client.a. Log on to your working client.b. Go to the Maintain Table Views (SM30) transaction.c. Enter the view name and click Maintain. These are the views that contain default Customizing settings:

○ V_ECPAO_COMPANY○ V_ECPAO_FLD

NoteThis Customizing view is only used for displaying data. Entries in this view can't be made directly, but only using the Import of Metadata from Employee Central (ECPAO_ECFLD_METADATA_WRITER) program.

○ V_ECPAO_TEMPLSET from the VC_ECPAO_MAP view cluster○ V_ECPAO_ERPTEMPL from the VC_ECPAO_MAP view cluster


○ V_ECPAO_FLDMAP from the VC_ECPAO_MAP view cluster

The other Customizing views don't contain any default Customizing settings.

d. For each Customizing view, choose Utilities Adjustments .e. Select the RFC connection that you have created in step 1.f. Select the entries listed below and click Adjust.

These are the default entries that you need to copy:

○ V_ECPAO_COMPANY: SBS_MODEL company○ V_ECPAO_FLD: SBS_MODEL company○ V_ECPAO_TEMPLSET: template groups that are assigned to the SBS_MODEL company○ V_ECPAO_ERPTEMPL: SBS_MODEL_CSV for the CSV template, SBS_MODEL_WS for the Web service-

based template○ V_ECPAO_FLDMAP: all entries that are assigned to the template groups and templates you have

selected beforeg. Click Copy All Entries, then save your changes.

3.1.4.2 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 want to start using the employee master data replication from on-premise SAP ERP HCM systems to SuccessFactors Employee Central with the side-by-side deployment model, where you have previously used the integration add-on for SAP ERP HCM and SuccessFactors HCM Suite to replicate employee data from SAP ERP HCM to the Employee Profile in the SuccessFactors Talent Suite. For more information, refer to section How to Migrate from Employee Data Integration with the SuccessFactors Talent Suite to Employee Data Integration in the Side-by-Side Deployment Model [page 78].

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



Employee Central

This is because the same data must 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.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.

3.1.4.3 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_idYou 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_externalYou can choose from the following mapping modes:

○ Standard mapping: The person_id_external field is mapped to the central person (CP) in SAP ERP HCM.


○ Infotype mapping: The person_id_external field is mapped to the SAP ERP HCM infotype Person ID (0709).

○ BAdI mapping (see above)○ username

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)3. Decide how employments are to be handled in Employee Central when an employee is transferred from one

country to another in SAP ERP HCM. When you transfer an employee in SAP ERP HCM from one country to another, the employee gets a new personnel number (PERNR), which is assigned to the same central person (CP). When extracting data, the employee data extraction program analyzes the personnel numbers assigned to one central person. You can decide how these personnel numbers are to be handled in Employee Central. Currently, only the option Reuse Existing Employment for International Transfer is available. This means that the personnel numbers are handled together and the data of both is transferred to one employment in Employee Central.

ExampleFor an example, see the Employee Central company SBS_MODEL in the delivered sample Customizing.

3.1.4.4 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 (using the ECPAO_ECFLD_METADATA_WRITER program).

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

You can also delete the entries you have imported for a specific Employee Central company and template.



Employee Central

CautionDon't delete metadata that you have already used for field mappings in the Define Template Group Customizing activity. Otherwise your mappings become invalid.

In the Check Imported Employee Metadata Customizing activity, you can display the metadata that was imported from Employee Central.

Procedure

1. Download the metadata that you want to import from Employee Central:

○ CSV-Based Employee Data ExtractionTo download metadata of the CSV Data Import Entity type:


2. In the Manage Employees portlet, select Update User Information Import Employee Data .3. Click the Download a blank CSV template link.4. A list of templates is displayed.

○ Web Service-Based Employee Data ExtractionTo download metadata of the Web Service Entity type:


2. In the Company Processes & Cycles portlet, select Company Settings OData API Data Dictionary .

NoteThis option in 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.Employee Central and SAP ERP: Side-by-Side Deployment ModelReplication of Employee Master Data from the On-Premise SAP ERP HCM System to Employee Central © 2015 SAP SE or an SAP affiliate company. All rights reserved. 21

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:

3. Select the Update Metadata checkbox to import the metadata.4. Optional: Carry out a test run of the program to check the data that will be uploaded to SAP ERP HCM.5. Clear the Test Run checkbox and execute the program to upload the data from the Employee Central

metadata file into the EC Template Field Mapping (ECPAO_FLD) table or delete data from this table.

CautionThe 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 [page 54].

6. Optional: To delete the entries you have imported for the Employee Central company and template that you have specified on the selection screen, select the Delete Metadata checkbox and execute the program.

7. Check the metadata that you have imported or deleted in the Check Imported Employee Metadata Customizing activity.



Employee Central

NoteYou can't make any changes to the metadata in this Customizing view. Always use the ECPAO_ECFLD_METADATA_WRITER program to update the entries in this view.

3.1.4.5 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 Employee Central and SAP ERP: Side-by-Side Deployment ModelReplication of Employee Master Data from the On-Premise SAP ERP HCM System to Employee Central © 2015 SAP SE or an SAP affiliate company. All rights reserved. 23

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. Define country-independent and country-dependent value mapping entities in the Define Value Mapping Entities Customizing activity (view V_ECPAO_VALUENTY)

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 picklistUse 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.

ExampleThe 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 picklistUse this type if the picklist value you want to map is an option ID. This is the case for most of the picklists.



Employee Central

ExampleThe 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 picklistUse this type if the picklist value you want to map is the picklist label.

○ Foundation Object Key mappingUse this type to map Employee Central event reasons to personnel actions from SAP ERP HCM.

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

○ Standard mappingUse 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 country-independent value mapping entity that you have defined in the first step.

3. Define country-dependent value mappings in the Define Country-Specific Value Mapping Details Customizing activity (view V_ECPAO_VALENTYC).


Here you map SAP ERP HCM keys and the corresponding Employee Central keys as described above, and additionally assign ISO codes.

ExampleFor 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 country-independent mappings, such as EVENT_REASON or LANGUAGE_CODE.

3.1.4.6 Handling Manager Relationships

3.1.4.6.1 Define Types of Manager Relationships

Context

You define different types of employee-manager relationships (such as a line manager or a matrix manager relationship) and the corresponding evaluation paths in the Customizing structure Integration of SAP ERP HCM to SuccessFactors Employee Central Side by Side, in the Define Relationship Types for Managers and Organizational Management Data activity (view V_ECPAO_MNGRTYPE).

The Determination of Managers and Organizational Management Data (ECPAO_MNGR_TYPES_EXTRACTION) program uses the types of manager relationships you define here to determine the different types of managers for a given selection of employees. For more information, refer to section Determine the Employees' Managers [page 28].

In the Mapping of EC and SAP ERP Templates for Employee Replication (VC_ECPAO_MAP) view cluster, you can use the types of manager relationships you define here to map managers from SAP ERP HCM to Employee Central, for example, to use them in the Job Relationship template. For more information, refer to section Define Template Groups [page 35].



Employee Central

For each type of manager relationship you want to use, carry out the steps described below.

Procedure

1. Enter a unique ID and a description of the relationship type.You can enter any description. The ID you enter here is used in the VC_ECPAO_MAP view cluster, in the Primary Mapping view. In this view cluster, you enter the ID in the Subtype field.

2. Select the evaluation path that is to be used to determine the managers for this type of relationship.The evaluation path describes a chain of relationships between objects in a hierarchical structure, such as

organizational unit position person . The SAP ERP HCM system evaluates the structure along this evaluation path and takes into account the objects that it finds using this path. You can use evaluation paths that start with the object types * (any), O (organizational unit), S (position), or P (person).

3. Enter the structure depth.This is a number of one to six digits. The number corresponds with the different levels of an organizational structure, with 1 being the highest level in a structure, and all subsequent numbers representing lower levels. The level number determines how much of a structure is processed. For example, if the structure depth is 3, the SAP ERP HCM system processes down three levels of the structure, beginning from the object that you select as the root object. If you don't want to limit processing, leave the structure depth blank.

4. To define whether the type of manager relationship is currently active and used by the manager extraction report or not, select or clear the Is Active checkbox.

Results


3.1.4.6.2 Determine the Employees' Managers

Context

You can determine different types of managers for a given selection of employees, based on the types of manager relationships you have defined in the Relationship Types for Managers and Organizational Mgmt Data (V_ECPAO_MNGRTYPE) view (see section Define Types of Manager Relationships [page 26]). The managers are stored in the Managers and Org. Mgmt Fields for Employee Replication (ECPAO_EE_MGNR) table so that manager relationships can be transferred to Employee Central. Employee Central uses the manager relationships, for example, in the Job Relationships and the Job Information templates to identify different types of managers, such as matrix managers, second managers, custom managers, or HR managers.

Procedure

1. Go to the Define Background Job (SM36) transaction.

2. Schedule the Determination of Managers and Organizational Management Data (ECPAO_MNGR_TYPES_EXTRACTION) program as a regular background job.

3. On the selection screen, specify the personnel numbers for which you want to determine the managers.4. The program reads the active types of manager relationships from the V_ECPAO_MNGRTYPE view and uses

the evaluation paths stored there to determine the managers for the given selection of employees.5. To check the messages issued by the program, go to the Analyze Application Log (SLG1) transaction.

6. Enter the ECPAO object and ECPAO_MANAGER subobject, optionally specify additional selection criteria, and click Execute.



Employee Central

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.

3.1.4.6.3 Manager Extraction Logic for Different Types of Managers

In the SAP ERP HCM system, an employee can be assigned to different types of managers as well as to several managers of the same type in overlapping periods. In Employee Central, an employee can only be assigned to one manager of the same type (for example, to one matrix manager) at a specific point in time. If the employee is assigned to several types of managers, the assignment periods must match. The extraction logic adapts the manager assignments in the two cases described below.

Employee is assigned to several types of managers in overlapping periods in SAP ERP HCM

In this case, the extraction logic modifies the time slices so that the assignment periods of the same employee to different types of managers match.

NoteTo make this work, you need to map the end date field of the Job Relationships template to the ENDDA field as described in section Define Template Groups [page 35].

ExampleAn employee has the following manager assignments in SAP ERP HCM:

● 01/01/2010 to 12/31/2014: Custom manager C● 01/01/2013 to 12/31/2015: Matrix manager M

The manager assignments are replicated to Employee Central as follows:

● 01/01/2010 to 12/31/2012: Custom manager C● 01/01/2013 to 12/31/2014: Custom manager C and matrix manager M● 01/01/2015 to 12/31/2015: Matrix manager M


Employee is assigned to several managers of the same type in overlapping periods in SAP ERP HCM

In this case, the extraction logic delimits the records accordingly.

ExampleAn employee has the following manager assignments in SAP ERP HCM:

● 01/01/2010 to 12/31/2014: Supervisor M1● 01/01/2012 to 12/31/9999: Supervisor M2

The manager assignments are replicated to Employee Central as follows:

● 01/01/2010 to 12/31/2014: Supervisor M1● 01/01/2015 to 12/31/9999: Supervisor M2

The second manager assignment starts after the first assignment has ended.

3.1.4.6.4 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 Determination of Managers and Organizational Management Data (ECPAO_MNGR_TYPES_EXTRACTION) program then stores these managers' users instead of the personnel numbers in the Managers and Org. Mgmt Fields for Employee Replication (ECPAO_EE_MGNR) table.

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.



Employee Central

RestrictionThe 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 and assign the user to the corresponding organizational structure.

5. Go to the Define Relationship Types for Managers and Organizational Management Data Customizing activity and select an appropriate evaluation path for the User (US) object type. For more information, refer to section Define Types of Manager Relationships [page 26].

3.1.4.7 Transferring Additional Organizational Management Data to Employee Central

3.1.4.7.1 Map Organizational Management Fields from SAP ERP HCM to Employee Central

You can transfer additional data from Organizational Management, such as the functional area or job family, from SAP ERP HCM to custom-string# fields in Employee Central.

Prerequisites

You have created suitable custom-string# fields in Employee Central (# means a number). The custom-string# fields can be contained in any employee-related entity in Employee Central. The Human Resource Information System (HRIS) synchronization process provides the information from these fields to the employee profile.


Context

To map the Organizational Management fields to custom-string# fields in Employee Central, make these settings:

Procedure

1. Define a relationship type for Organizational Management data.To do so, go to the Define Relationship Types for Managers and Organizational Management Data Customizing activity and define a relationship type for which you select the Use BAdI Implementation checkbox. You don't need to select an evaluation path or enter a structure depth for this relationship type. For more information about this Customizing activity, refer to section Define Types of Manager Relationships [page 26].

2. Add the fields to the Managers and Org. Mgmt Fields for Employee Replication table.To do so, create a custom structure containing the fields that you want to map and add it to the ECPAO_EE_MGNR table using the CI_EE_PD_DATA include.

3. Implement the Extraction of Organizational Management Data Business Add-In (BAdI).Create an implementation of the EX_ECPAO_ERP_MNGR_TYP_PDDATA BAdI that retrieves the content for the fields you want to map. The Determination of Managers and Organizational Management Data (ECPAO_MNGR_TYPES_EXTRACTION) program calls your BAdI implementation, extracts the content based on this implementation, and stores it in the corresponding fields that you have defined in the custom structure included in the ECPAO_EE_MGNR table. For information, refer to section Extract Organizational Management Data [page 33].

4. Map the Organizational Management fields to the custom-string# fields.

To do so, go to the Map EC Templates and SAP ERP Templates for Employee Replication Customizing activity. In the Primary Mapping view, carry out the following steps for each custom-string# field from Employee Central to which you map an Organizational Management field from SAP ERP HCM:

1. Select the Infotype Mapping mapping mode.2. In the Infotype field, select MNGR.3. In the Subtype field, select the relationship type that you have defined in the V_ECPAO_MNGRTYPE view.4. Select the suitable field from the include in the ECPAO_EE_MGNR table.

For more information about this Customizing activity, refer to section Define Template Groups [page 35].

ExampleLet's say that you use the Employee Central field custom-string12 to store the employee's functional area. You want to fill this field with content from the FKBER field from the Functional Areas (V_TFKB) view in the SAP ERP HCM system. In this view, in Customizing for Financial Accounting, you can define different functional areas. In SAP ERP Organizational Management, the functional area corresponds to the object type IE.

Therefore, you define the relationship type FCTL in the Define Relationship Types for Managers and Organizational Management Data Customizing activity and select the Use BAdI Implementation checkbox for it. You create a custom structure containing the FKBER field and add it to the ECPAO_EE_MGNR table. You create a suitable implementation of the EX_ECPAO_ERP_MNGR_TYP_PDDATA BAdI. The ECPAO_MNGR_TYPES_EXTRACTION program retrieves the content from the FKBER field based on your BAdI implementation and stores it in the ECPAO_EE_MGNR table. In the Map EC Templates and SAP ERP Templates



Employee Central

for Employee Replication Customizing activity, you select the custom-string12 field and map it to the MNGR infotype, the FCTL subtype, and the FKBER field from the ECPAO_EE_MGNR table.

The content from the FKBER field is then read from the ECPAO_EE_MGNR table during employee extraction and transferred to the custom-string12 field in Employee Central.

3.1.4.7.2 Extract Organizational Management Data

You can extract Organizational Management data, such as the functional area or job family, from SAP ERP HCM, which you want to transfer to a custom-string field in Employee Central.

Context

The Determination of Managers and Organizational Management Data (ECPAO_MNGR_TYPES_EXTRACTION) program extracts the data for a given selection of employees, based on the relationship types you have defined in the Relationship Types for Managers and Organizational Mgmt Data (V_ECPAO_MNGRTYPE) view (see section Define Types of Manager Relationships [page 26]). The data is stored in the Managers and Org. Mgmt Fields for Employee Replication (ECPAO_EE_MGNR) table. The Employee Data Extraction (ECPAO_EMPL_EXTRACTION) program then reads data from this table and transfers it to Employee Central.

Procedure

Proceed as described in section Determine the Employees' Managers [page 28].

3.1.4.8 Define Employee Central Templates

Prerequisites

If you create an Employee Central template for an MDF entity (also called generic object), make sure that the MDF entity in Employee Central has an externalCode field with the User data type.

Context

You define Employee Central templates in the Customizing structure Integration of SAP ERP HCM to SuccessFactors Employee Central Side by Side, in the Define EC Templates activity (view V_ECPAO_ECTMPL). An


Employee Central template represents an entity from Employee Central, such as a CSV data import template, an OData entity, or an MDF entity, that is related to employee data. You define Employee Central templates if you want to transfer employee master data from SAP ERP HCM to an Employee Central entity for which SAP hasn't provided a template. The Define EC Templates Customizing activity also shows the Employee Central templates defined by SAP. For a list of the standard templates, refer to section Supported Employee Central Entities [page 11]).

If you want to define your own Employee Central templates, carry out the steps described below for each template that you add.

Procedure

1. Enter a unique template ID. The ID has to start with a number.2. Enter the template name. You must use the exact name of the corresponding entity in Employee Central.

To find out about the name for OData entities and MDF entities/generic objects), go to Administration Tools and in the Company Processes & Cycles portlet, select Company Settings OData API Data Dictionary . For CSV data import templates, go to Administration Tools and in the Manage Employees portlet, select

Update User Information Import Employee Data .3. Enter a description. You can enter any description.4. Depending on the type of Employee Central entity for which you use the template, select the import object

type (file-based or Web service-based data transfer).5. If your template refers to an MDF entity in Employee Central, make the following settings:

○ Select the MDF Entity checkbox.○ In the MDF User Field column, enter the name of the field in the MDF entity that has the User data type

assigned and that contains the Employee Central user ID to which the employee ID information from SAP ERP is to be transferred.Which ID is transferred depends on the mapping that you have defined in Define Employee Central Company [page 19]. In the standard mapping, the personnel number (PERNR) is used as the employee ID.



Employee Central

For more information, refer to section Standard Mapping of SAP ERP HCM Fields to Employee Central Fields [page 54].

6. Specify if the Employee Central entity is effective dated7. If you want to be able to assign your Employee Central template to several SAP ERP templates, select the

Multiple Use checkbox.8. Enter a sequence number.

The sequence in which the Employee Central templates delivered by SAP are transferred from SAP ERP HCM Employee Central is defined by SAP. You can't change this sequence. If you define your own template, we recommend to use a sequence number that is higher than the numbers assigned to the Employee Central templates that are delivered by SAP.

3.1.4.9 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:

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 EntityChoose this import type if you want to use the template group for the CSV-based extraction of employee master data.

○ Web Service EntityChoose 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.Employee Central and SAP ERP: Side-by-Side Deployment ModelReplication of Employee Master Data from the On-Premise SAP ERP HCM System to Employee Central © 2015 SAP SE or an SAP affiliate company. All rights reserved. 35

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 being replicated from SAP ERP HCM to Employee Central. For more information, refer to the following sections:

○ Create Event Reasons in Employee Central [page 51]○ Hiring a New Employee in SAP ERP HCM [page 83]○ Rehiring an Employee in SAP ERP HCM Who Was Previously Mastered in SAP ERP HCM [page 85]

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 [page 46].

NoteYou 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. Define a set of SAP ERP templates for each template group.



Employee Central

For each SAP ERP template, make these settings:

a. Enter a name and description for the template and assign it to one of the predefined Employee Central entities (see section Supported Employee Central Entities [page 11]) or to an Employee Central template that you've created before (see section Define Employee Central Templates [page 33]).

b. Select the Is 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.

If you want to map managers from SAP ERP HCM to the Job Relationship template in Employee Central, you need a separate ERP template for each type of manager. You could, for example, define the ERP templates ERP_JOBREL_CUSTOM (Job Relationship - Custom Manager) and ERP_JOBREL_MATRIX (Job Relationship - Matrix Manager).

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:


○ 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). You can use the preconfigured mapping only for mapping cost centers in the Job entity and for mapping the source of record in the Employment entity.

○ 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 50].

c. To map managers from SAP ERP HCM to Employee Central, carry out the following steps for each ERP template that defines a type of manager:

1. In the Infotype field, select MNGR.2. In the Subtype field, select the suitable type of manager relationship that you have defined in the

V_ECPAO_MNGRTYPE Customizing view as described in section Define Types of Manager Relationships [page 26].



Employee Central

3. Select one of the following fields from the Manager Assignments for Employee Replication (ECPAO_EE_MGNR) table as the infotype field to be mapped:

○ RELATION_CODEYou can map the relation-type field in the Job Relationships template to the RELATION_CODE field.You also need to define a value mapping entity for the relation-type field using the type of manager relationship that you have defined in the V_ECPAO_MNGRTYPE Customizing view as the ERP key.


For more information about value mapping, refer to section Define Value Mappings [page 23].○ EC_MGNR_USER

If the manager's data is mastered in Employee Central, you can map the manager-id field in the Job Information template or the rel-user-id field in the Job Relationships template to the EC_MNGR_USER field.

○ MNGR_USER_IDIf the manager's data is mastered in SAP ERP HCM, you can map the manager-id field in the Job Information template or the rel-user-id field in the Job Relationships template to the MNGR_USER_ID field.

○ ENDDAIf an employee has assignments to different types of managers in SAP ERP HCM in overlapping time slices, you need to map the end date field of the Job Relationships template to the ENDDA field. For more information, refer to section Manager Extraction Logic for Different Types of Managers [page 29].

ExampleYou want to map the Employee Central field Supervisor in the Job Information template with a suitable manager from SAP ERP HCM. Therefore, you select the MNGR infotype, the 0001 subtype (which is defined in the V_ECPAO_MNGRTYPE Customizing view with an evaluation path that determines the supervisor of an employee), and the MNGR_USER_ID infotype field. The content from the MNGR_USER_ID field is then read from the ECPAO_EE_MGNR table during employee extraction and transferred to Job Information in Employee Central.



Employee Central

d. To map Organizational Management fields (such as the functional area or job family) from SAP ERP HCM to custom-string# fields in Employee Central, carry out the steps described in section Map Organizational Management Fields from SAP ERP HCM to Employee Central [page 31].

e. 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 [page 43].

f. 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:

○ Based on a linking fieldThis 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)


ExampleFor 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

You can also use the template group SBS_MODEL_WS as an example. This template group is also defined for the Employee Central company SBS_MODEL in the delivered sample Customizing. 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.

3.1.4.10 Extract Employee Master Data

Procedure

1. Go to the ABAP: Program Execution (SA38) transaction.

2. Execute the Employee Data Extraction (ECPAO_EMPL_EXTRACTION) program to initially extract employee master data from the SAP ERP HCM system based on your 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 13]○ Define Template Groups [page 35]

If you select the File Transfer Using Local Drive Path option and store several CSV files on your local disk, you can also combine them into a .zip file. Please note that this doesn't work for CSV files that you create for MDF entities (generic objects).

You can also carry out a test run of the program to check if the data can be extracted from SAP ERP HCM without 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

Next Steps

Make sure that the data of employees who are mastered in SAP ERP HCM can't be edited in Employee Central. 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 46]. You can run the Employee Data Extraction program to extract data for selected employees.


3.1.4.11 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.

NoteThe 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.

In SAP ERP, all infotype data is effective dated. In Employee Central, some data, such as email or phone information, isn't effective dated. If you change data in SAP ERP HCM for the future that isn't effective dated in Employee Central, the corresponding change pointers will only be executed at this future date.

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

3.1.4.12 Replicate Employee Master Data to Custom Entities in Employee Central

Prerequisites

You have created a custom MDF entity (or custom generic object) in Employee Central. To do so, go to Administration Tools. In the Company Processes & Cycles portlet, select Company Settings Configure Object Definitions . When you create your entity, make sure to set the API Visibility option to Editable.

Context

If you want to transfer employee master data from SAP ERP HCM to your custom entity, carry out the steps described below.

Procedure

1. Import metadata from your custom entity in Employee Central into the SAP ERP HCM system.

a. Download the metadata from your custom entity in Employee Central.

○ To download metadata of the CSV Data Import Entity type:

1. Go to Administration Tools.2. In the Metadata Framework section, click Import and Export Data.3. In the Select the action to perform field choose Download Template.4. Select your object definition in the Select Generic Object field and click Download.

○ To download metadata of the Web Service Entity type:


2. In the Company Processes & Cycles portlet, select Company Settings OData API Data Dictionary .

3. A list of templates is displayed.If your custom template isn't shown here, go back to the Company Processes & Cycles portlet and select Company Settings OData API Metadata Refresh and Export , then click Refresh.

4. Expand your custom 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.b. Import the metadata into the SAP ERP HCM system using the Import of Metadata from Employee Central

(ECPAO_ECFLD_METADATA_WRITER) program as described in section Import Metadata from Employee Central [page 20]


2. Define an Employee Central template for your custom entity as described in section Define Employee Central Templates [page 33].

3. Map the fields of your Employee Central template to an ERP template as described in section Define Template Groups [page 35].

3.1.4.13 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.



Employee Central

The file is then downloaded to the folder you have specified.

3.1.4.14 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


2. Execute the Update Key Values Mapping Table with Manually Replicated Employee Data (ECPAO_EEREPCSV_EEKEYMAP_UPDATE) program.

3. On the selection screen, specify the employee and Employee Central company for which the employee key mapping table is to be updated, then click Execute.

4. 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


3.1.4.15 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.

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 35].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. Here, a Data Change event with the DATINAVAL event reason is triggered in Employee Central. For more information about these event reasons, refer to section Create Event Reasons in Employee Central [page 51].

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.

5. Optional: If you want to transfer additional Organizational Management data (such as the functional area or job family) from SAP ERP HCM to custom-string fields in Employee Central, implement the Extraction of Organizational Management Data (EX_ECPAO_ERP_MNGR_TYP_PDDATA) BAdI.

For more information, refer to section Map Organizational Management Fields from SAP ERP HCM to Employee Central [page 31].



Employee Central

3.2 Setting up Employee Central for the Replication of Employee Data

3.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 such as the rehire process. For more information, refer to section HR Business Processes in the Side-by-Side Deployment Model [page 82].

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 where this cutoff date is after the hire date of the employee. For more information, refer to the following sections:

○ Define Template Groups [page 35]○ Rehiring an Employee in SAP ERP HCM Who Was Previously Mastered in SAP ERP HCM [page 85]


2. Create a DATAVAL event reason for the Data Change event using the Active employee status as shown here:

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 50].

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 50]



Employee Central

3.3 Master Data Replication Information

3.3.1 Standard Employee Central Fields

The tables below list the standard fields for the CSV-based and OData-based entities in Employee Central.

Table 2: CSV-Based Entities

Basic Import Biographical Information

Employment Details

Job History Personal Information

Global Assignment

Email Info Phone Info

STATUS user-id user-id manager-id start-date user-id personInfo.person-id-external

personInfo.person-id-external

USERID person-id-external

start-date start-date personInfo.person-id-external

person-id-external

FIRSTNAME person-id-external

user-id start-date

LASTNAME originalStartDate

planned-end-date

MI

HR

manager-id

USERNAME

Table 3: OData-Based Entities

SFOData.User

SFOData.PerPer-son

SFOData.EmpEmploy-ment

SFOData.EmpJob

SFOData.PerPer-sonal

SFOData.EmpGlo-balAssign-ment

SFOData.PerE-mail

SFOData.Per-Phone

status userId userId managerId startDate userId personIdExternal

personIdExternal

userId personIdExternal

startDate startDate personIdExternal

personIdExternal

firstName personIdExternal

userId startDate

lastName originalStartDate

seqNumber plannedEndDate

username


3.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.

CautionThese 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

3.3.3 Preconfigured Mapping of SAP ERP HCM Fields to Employee Central Fields

The following mappings of SAP ERP HCM entities and Employee Central entities are preconfigured. This means that the mapping is defined by SAP in the Preconfigured Mapping tables (ECPAO_PREMAPPING, ECPAO_PREMAP_TT).

Table 4:

Employee Central Entity SAP ERP HCM Entity

Cost Center in Job Information Concatenation of Controlling Area (KOKRS) and Cost Center (KOSTL) fields from Organizational Assignment (0001) infotype

Source of Record* in Employment Information Logical System (LOGSYS) field in Clients (T000) table

* You use the Source of Record field to define which is the master system for the employee's data. If an employee's data is mastered in SAP ERP HCM, the Source of Record field should indicate the corresponding SAP ERP HCM system.

If a country that used to be mastered in SAP ERP HCM is now mastered in Employee Central, you need to change the Source of Record field for all employments assigned to this country.

ExampleLet's say, the data of all your employees in France is mastered in SAP ERP HCM and replicated to Employee Central. So the Source of Record field of all employments assigned to France contains the logical system ID of the corresponding SAP ERP HCM system, indicating that this data is mastered in SAP ERP HCM. Now you switch the system of record for employees in France so that their data is mastered in Employee Central.



Employee Central

Therefore, the entry in the Source of Record field of all employments assigned to France needs to be changed so that it now indicates Employee Central as the master system. For employees who have employments in several countries, only the employment assigned to France needs to be changed. The other employments should stay as they are. After having changed the Source of Record field, you stop replicating the data of your employees in France from SAP ERP HCM to Employee Central.

To do so, download the Employment Information data for all affected employments from SAP ERP HCM as a CSV file and upload it to Employee Central. Make sure that you have filled the Source of Record field with the entry EC from the external code of the SourceOfRecord picklist and the user_id field with the correct user IDs of the affected employees. If you want to leave the other fields empty, use the NO_OVERWRITE notation. For more information, see the FAQs: Importing Data section in the SuccessFactors Employee Central implementation guide. Find the most current version of this guide on SAP Service Marketplace at http://service.sap.com/ec-ondemand

.

3.3.4 Sample Mapping of SAP ERP HCM Fields to Employee Central Fields

The template groups SBS_MODEL_CSV 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.

You can copy the delivered sample Customizing and use it as an example for your own field mappings. To copy the Customizing settings, proceed as described in section Import Default Customizing Into Your Working Client in the SAP ERP HCM System [page 17].

3.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 [page 13].

This section describes how to set up the middleware.

3.4.1 Preparing the Middleware System

An Application Programming Interface (API) is implemented in Employee Central for inserting and updating employee data from other systems. Currently, the side-by-side deployment model uses Dell's Boomi AtomSphere to call this API in Employee Central and insert or update the employee master data. In addition, an API is provided for querying employee data. This API is needed to retrieve key data.

SAP delivers two processes for the middleware, which handle the message processing for all data fields sent and queried by the on-premise SAP ERP HCM system.Employee Central and SAP ERP: Side-by-Side Deployment ModelReplication of Employee Master Data from the On-Premise SAP ERP HCM System to Employee Central © 2015 SAP SE or an SAP affiliate company. All rights reserved. 55



3.4.1.1 Install the Integration Pack

Context

To install the integration pack in the middleware system, carry out these steps:

Procedure

1. Log on to Boomi AtomSphere and navigate to Deploy.2. Browse for the available integration packs.3. Click View for the Packaged Integration: SAP ERP to EC Employee Replication v1.0 integration pack.4. Click Install.5. Choose a new name (optional) and click Complete Installation.6. If the installation was successful, you get a confirmation popup.

3.4.2 Configuring the Middleware System

This section describes how to make the settings in Boomi AtomSphere after you have installed the integration pack.

3.4.2.1 Configure the Employee Data Replication Process

Procedure

1. In Boomi AtomSphere, go to the Environment Extensions.2. Configure the Packaged Integration: SAP ERP to EC Employee Replication v1.0 process:



Employee Central

○ Process Filter: Select Packaged Integration: SAP ERP to EC Employee Replication v1.0.○ Connection: Select the CON EC HTTP OData Upsert v1.0 connection.○ Clear the Use Default? checkboxes to add customer-specific input.○ URL: Enter the service endpoint URL for the OData upsert service in your Employee Central system.

To do so, find out the base URL of the endpoint and put together a URL that corresponds to this schema:<base_URL>/odata/v2/upsert?suppressUpdateOfIdenticalData=true&purgeType=full

ExampleThe final URL could look like this:

https://salesdemo4.successfactors.com/odata/v2/upsert?suppressUpdateOfIdenticalData=true&purgeType=full

○ Use Basic Authentication: Select this checkbox.○ User: Enter the user name in the form username@companyID.

To do so, put together the name of your user for OData API calls and your company ID, connected with @.

ExampleThe entry in the User field could be admin@company1234.

○ Password: Enter the password of this user.


NoteThe user must have the permission to use OData APIs. An admin of your SuccessFactors system can grant this permission. For more information about how to grant permissions, refer to the Managing Role-Based Permissions section in the SuccessFactors Employee Central implementation guide. Find the most current version of this guide on SAP Marketplace at http://service.sap.com/ec-ondemand .

3.4.2.2 Configure the Employee Key Data Query Process

Procedure

1. In Boomi AtomSphere, go to the Environment Extensions.2. Configure the Packaged Integration: SAP ERP to EC Employee Key Data Query v1.0 process:

○ Process Filter: Select Packaged Integration: SAP ERP to EC Employee Key Data Query v1.0.○ Connection: Select the CON EC SFSF Query v1.0 connection.



Employee Central


○ Clear the Use Default? checkboxes to add customer-specific input.○ Endpoint: Select the endpoint system or select Other.○ Other Endpoint: If you have selected the Other option in the Endpoint field, enter the SFAPI URL for the

Employee Central system.○ Company Id: Enter your Employee Central company ID.○ Username / Password: Enter the user name and password of the SFAPI user.

NoteEach SFAPI user must have the API log-in permission. An admin of your SuccessFactors system can grant this permission. For more information about how to grant permissions, refer to the Managing Role-Based Permissions section in the SuccessFactors Employee Central implementation guide. Find the most current version of this guide on SAP Marketplace at http://service.sap.com/ec-ondemand

.

3. Configure the process properties. To do so, select Employee Key Query Properties v1.0 and set the parameters listed below. To add customer-specific input, deselect the Use Default? flag.

○ INCLUDE_LOG_DATA [default = blank]Set to X to transfer extended error information back to the SAP ERP HCM system to be able to analyze issues more easily.

3.4.3 Configuring the SAP ERP HCM System

The integration add-on for SAP ERP master data and SuccessFactors Employee Central for the SAP ERP HCM system contains consumer proxies for triggering a Web service call for the replication of employee master data Employee Central and SAP ERP: Side-by-Side Deployment ModelReplication of Employee Master Data from the On-Premise SAP ERP HCM System to Employee Central © 2015 SAP SE or an SAP affiliate company. All rights reserved. 59



and for the query of employee key data. For these proxies you have to configure logical ports, which connect the SAP ERP HCM system with Boomi AtomSphere.

3.4.3.1 Configure the Logical Ports

Procedure

1. Log on to your SAP ERP HCM system and go to the SOA Management (SOAMANAGER) transaction.

2. Click Web Service Configuration.3. On the Design Time Object Search tab, search for the CO_ECPAO_GET_GENERIC_ODATA_UPS consumer proxy

and select the entry in the search result.

4. From the Create menu choose Manual Configuration to create a new logical port.

5. Select the User ID / Password authentication option and enter the credentials from your Boomi Atom. For more information, refer to section Find the URLs and Log-On Data [page 61].



Employee Central

6. Set up the messaging as shown here:

7. Set up the transport settings as shown here:

For more information about how to find the URLs, refer to section Find the URLs and Log-On Data [page 61].8. Configure the CO_ECPAO_GET_EMPLOYEE_KEY_DATA consumer proxy in the same way.

3.4.3.2 Find the URLs and Log-On Data

Procedure

1. Log on to Boomi AtomSphere and go to Atom Management.2. Open the Atom where you deployed the processes and click Shared Web Server Settings.


3. On the Shared Web Server Settings popup, you can find the base URL, the user name, and the password as shown here:



Employee Central

The URL access path to be entered in both logical ports is /ws/soap?wsdl.

3.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.

3.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 ProfileEmployee Central and SAP ERP: Side-by-Side Deployment ModelReplication of Employee Master Data from the On-Premise SAP ERP HCM System to Employee Central © 2015 SAP SE or an SAP affiliate company. All rights reserved. 63

Procedure


2. In the Company Processes & Cycles portlet, select Company Settings Configure Business Rules .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:

3.5.2 Configure the Succession Data Model

Procedure

1. Log on to Provisioning of the relevant instance and download the current Succession Data Model configuration.

2. Open the XML file in a suitable editor.3. Assign the rule created in the previous step by adding the trigger-rule event as in this example:

In this example, the trigger-rule event is OnSave:



Employee Central

4. Save your changes.5. Upload the changed Succession Data Model.

3.5.3 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. Make sure that the Enable rules execution during Job Information import checkbox is selected as shown here:Employee Central and SAP ERP: Side-by-Side Deployment ModelReplication of Employee Master Data from the On-Premise SAP ERP HCM System to Employee Central © 2015 SAP SE or an SAP affiliate company. All rights reserved. 65

3.5.4 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

3. Display the Organizational Assignment (0001) infotype and check the value stored in the Company Code field.


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 23].

CautionIn 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.

3.5.5 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 35].

2. Go to the Primary Mapping view of your template group and add the following fields:

○ Holiday Calendar○ Time Profile○ Work Schedule

3. Select the BAdI Mapping mapping mode for each field.



Employee Central

NoteYou 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.

3.5.6 Map the Employee Central Time Types to SAP ERP Absence Types

Procedure

1. In the SAP Customizing Implementation Guide structure, open Personnel Management Personnel Administration Interfaces and Integration Integration of SAP ERP HR Master Data and SuccessFactors Employee Central Assignment of Code Values Define Mapping Code Value Lists .


2. Map the time types you use in Employee Central to the absence types used in SAP ERP HCM.

NoteIf 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

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


3.5.7 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.

Procedure

To be able to replicate time-off data of employees whose data is mastered in SAP ERP HCM from Employee Central to SAP ERP HCM, set up the middleware accordingly.For more information, refer to the Setting up the Middleware section in the Time Off and Employee Central Payroll integration guide. Find the most current version of this guide on SAP Service Marketplace at http://service.sap.com/ec-ondemand .

3.5.8 Extract Employee Data

Procedure


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 68].

3.5.9 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.



Employee Central



2. Go to the Manage Time Off portlet of an employee whose data is mastered in SAP ERP HCM and click Request Time Off.


Next Steps

The middleware replicates the time-off data from Employee Central to the Absences (2001) infotype in SAP ERP HCM.



Employee Central

3.5.10 Check Replicated Time-Off Information in SAP ERP HCM

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.


4. Click Infotype Overview to see all of the employee's time-off requests.



Employee Central

4 How to Migrate from Employee Data Integration with the SuccessFactors Talent Suite to Employee Data Integration in the Side-by-Side Deployment Model

This section is relevant if you want to start using the employee master data replication from on-premise SAP ERP HCM systems to SuccessFactors Employee Central with the side-by-side deployment model, where you have previously used either the integration add-on for SAP ERP HCM and SuccessFactors HCM Suite provided by SAP or another integration process to replicate employee data from an on-premise SAP ERP HCM system to the Employee Profile in the SuccessFactors Talent Suite.

If you are in this situation, you need to carry out the steps described in this section for all employees whose data was previously replicated to the SuccessFactors Talent Suite. Since SuccessFactors Employee Central and the SuccessFactors Talent Suite handle the user-sys-id and the person-id-external in different ways, you need to make sure to fill these fields correctly. When you replicate employee data using the side-by-side deployment model, reuse the IDs for all employees who were previously replicated to the SuccessFactors Talent Suite.

4.1 Determining the User ID

To replicate the correct user-sys-id from SAP ERP HCM to Employee Central, implement the GET_USERSYSID method of the Mapping of User ID, Person ID, and User Name (EX_ECPAO_EMP_USYID_PRN_UNM_MAP) Business Add-In (BAdI). For more information, refer to section Implement Business Add-Ins for the Replication of Employee Master Data [page 50].

When implementing the BAdI, check the following:

Is the employee's current personnel number (PERNR) one of several personnel numbers that are assigned to the same central person (CP) and are transferred to the same Job Information record in Employee Central as described in section Transferring an Employee from a Country Mastered in SAP ERP HCM to Another Country Mastered in SAP ERP HCM [page 88]?

● If yes: Check if any of the employee's personnel numbers was previously replicated to the SuccessFactors Talent Suite.

○ If yes: Find out which user ID was used for replicating the employee's data to the SuccessFactors Talent Suite. Use the same ID as the user-sys-id when replicating the employee's data to Employee Central using the side-by-side deployment model.

○ If no: Either use the standard logic of the side-by-side deployment model to determine the user-sys-id for the personnel number. Or implement the EX_ECPAO_EMP_USYID_PRN_UNM_MAP BAdI if you have specific requirements.

● If no: You only need to check if the current personnel number was previously replicated to the SuccessFactors Talent Suite. Then proceed as described above.


Employee Central and SAP ERP: Side-by-Side Deployment ModelHow to Migrate from Employee Data Integration with the SuccessFactors Talent Suite

to Employee Data Integration in the Side-by-Side Deployment Model

4.2 Determining the Person ID

When replicating the employee's data from SAP ERP HCM to Employee Central using the side-by-side deployment model, make sure to use the same person-id-external as was previously used for replicating the employee's data to the SuccessFactors Talent Suite. To replicate the correct person-id-external, implement the GET_PERSONID method of the Mapping of User ID, Person ID, and User Name (EX_ECPAO_EMP_USYID_PRN_UNM_MAP) BAdI. For more information, refer to section Implement Business Add-Ins for the Replication of Employee Master Data [page 50].

4.3 Handling the Different Integration Scenarios

The steps for checking if a personnel number was previously replicated from SAP ERP HCM to the SuccessFactors Talent Suite and for finding out which user ID was used for this replication differ depending on your integration scenario.

Scenario 1

You have installed the integration add-on 1.0 for SAP ERP HCM and SuccessFactors HCM Suite, support package 02 or higher and use the Sync Employee Data with SuccessFactors (with Delta and Inactive Logic) (RH_SFI_SYNCHRONIZE_EMPL_DATA) program to replicate employee data to the SuccessFactors Talent Suite.

In this case, you can check the HRSFI_D_EXTR_LOG database table to find out if a personnel number was previously replicated to the SuccessFactors Talent Suite and which user ID was used.

The person-id-external field is filled with the same value as the user-sys-id field.

Scenario 2

You have installed the integration add-on 1.0 for SAP ERP HCM and SuccessFactors HCM Suite, support package 00 and use the Extraction of Employee Data for SuccessFactors (RH_SFI_TRIGGER_EMPL_DATA_REPL) program to replicate employee data to the SuccessFactors Talent Suite.

In this case, the HRSFI_D_EXTR_LOG database table isn't available. The key mapping is not persisted in the SAP ERP HCM system. Therefore we recommend to upgrade to support package 02 or higher and to use the RH_SFI_SYNCHRONIZE_EMPL_DATA program instead of the RH_SFI_TRIGGER_EMPL_DATA_REPL program. Otherwise you need to implement a custom logic to find out if a personnel number was previously replicated to the SuccessFactors Talent Suite and which user ID was used.

As in scenario 1, the person-id-external field is filled with the same value as the user-sys-id field.Employee Central and SAP ERP: Side-by-Side Deployment ModelHow to Migrate from Employee Data Integration with the SuccessFactors Talent Suite to Employee Data Integration in the Side-by-Side Deployment Model © 2015 SAP SE or an SAP affiliate company. All rights reserved. 79

Scenario 3

You don't use the integration add-on for SAP ERP HCM and SuccessFactors HCM Suite, but another integration process to replicate employee data from an on-premise SAP ERP HCM system to the Employee Profile in the SuccessFactors Talent Suite.

In this case, you need to implement a custom logic to find out if a personnel number was previously replicated to the SuccessFactors Talent Suite and which user-sys-id and person-id-external were used.

4.4 Switching from One Replication to the Other

To keep the data consistent, we recommend that you run a final employee data transfer to the SuccessFactors Talent Suite and ensure that no employee data that is affected by data replication is changed in the SAP ERP HCM system before you start replicating employee data to SuccessFactors Employee Central using the side-by-side deployment model.

Once you've started using the side-by-side deployment model, the Employee Profile is fed from Employee Central. Therefore, make sure that you no longer replicate employee data to the Employee Profile using the previous replication of employee data to the SuccessFactors Talent Suite.

This applies to all scenarios described in section Handling the Different Integration Scenarios [page 79].

4.5 Making Additional Customizing Settings

If you have previously used the integration add-on for SAP ERP HCM and SuccessFactors HCM Suite, in Customizing, set the value of the SFSFI SBSER switch to X to indicate that the side-by-side employee data replication is active in your system. For more information, refer to section Define if Side-by-Side Employee Data Replication to Employee Central Is Active [page 18].

Setting this switch tells your system that the employee data replication programs of the integration add-on for SAP ERP HCM and SuccessFactors HCM Suite can no longer be run.

This applies to the scenarios 1 and 2 described in section Handling the Different Integration Scenarios [page 79].

4.6 Changing the Employment Status to Inactive Before and to Active Again After Switching from One Replication to the Other

The following situation might occur: An active employee is replicated from SAP ERP HCM to the SuccessFactors Talent Suite. Then the employee becomes inactive in SAP ERP HCM. The employee's data is replicated to the


Employee Central and SAP ERP: Side-by-Side Deployment ModelHow to Migrate from Employee Data Integration with the SuccessFactors Talent Suite

to Employee Data Integration in the Side-by-Side Deployment Model

SuccessFactors Talent Suite again. The employee is set to inactive in Employee Central. You switch to the employee data replication based on the side-by-side deployment model. Then the employee becomes active again.

In this situation, the employee data replication based on the side-by-side deployment model does not know that the same employee was previously replicated to the SuccessFactors Talent Suite and which user-sys-id was used. So in the side-by-side deployment model, the employee might get a different user-sys-id than he or she had before.

Therefore, implement a custom logic if you are in this situation. To do so:

● Store the information which personnel numbers were previously replicated to the SuccessFactors Talent Suite and which user-sys-id was used.

● Implement the Mapping of User ID, Person ID, and User Name (EX_ECPAO_EMP_USYID_PRN_UNM_MAP) Business Add-In (BAdI) using a custom method so that the side-by-side employee data replication can use the same user-sys-id when the affected employee is rehired.

This applies to all scenarios described in section Handling the Different Integration Scenarios [page 79].

CautionIn the situation described above, the entry in the HRSFI_D_EXTR_LOG database table in SAP ERP HCM that refers to the employee who is set to inactive is deleted. So even if you use scenario 1, you can't use the HRSFI_D_EXTR_LOG database table to retrieve the information you need.

4.7 Constraints

Currently the side-by-side deployment model doesn't support the following use cases for employees whose data was previously replicated to the SuccessFactors Talent Suite. This applies to all scenarios described in section Handling the Different Integration Scenarios [page 79].

Global assignment

An employee has several personnel numbers in different countries that are mastered in SAP ERP HCM. The employee's data is replicated to the SuccessFactors Talent Suite using the personnel number in the host country as the leading personnel number.

Concurrent employment

An employee has several personnel numbers in one country that is mastered in SAP ERP HCM. The employee's data is replicated to the SuccessFactors Talent Suite using the second number as the leading personnel number.Employee Central and SAP ERP: Side-by-Side Deployment ModelHow to Migrate from Employee Data Integration with the SuccessFactors Talent Suite to Employee Data Integration in the Side-by-Side Deployment Model © 2015 SAP SE or an SAP affiliate company. All rights reserved. 81

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.


HR Business Processes in the Side-by-Side Deployment Model

RecommendationWe recommend you use the following standard mappings:

● The central person from SAP ERP HCM is mapped to the person_id_external field in Employee Central.● The personnel number from SAP ERP HCM is 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 54]. 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 Employee Central. For more information about the mapping options, refer to section Define Employee Central Company [page 19].

RestrictionThe distributed scenario of the side-by-side deployment model currently doesn't support some business processes, such as:

● Rehiring an employee in SAP ERP HCM whose data was previously mastered in Employee Central● Transferring an employee from a country mastered in Employee Central to a country mastered in SAP ERP

HCM● Concurrently employing an employee within SAP ERP HCM and 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 35].

NoteIn 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

Employee Central and SAP ERP: Side-by-Side Deployment ModelHR Business Processes in the Side-by-Side Deployment Model © 2015 SAP SE or an SAP affiliate company. All rights reserved. 83

date. If you use the cutoff date, the Hire Date and Original Start Date fields in Employee Central are filled in different ways, depending on whether the employee’s hire date is before or after the cutoff date:

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

● 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.



5.2.2 Hiring a New Employee in Employee Central

The hire process in Employee Central works as usual. In the side-by-side deployment model described in this guide, employees whose data is 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, as outlined below.

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.

CautionSince 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.


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 83].



Related Information

Create Event Reasons in Employee Central [page 51]

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. In the side-by-side deployment model described in this guide, 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 Add Employment feature.

NoteYou can't use a Rehire event within the Add Employment feature. Only the Hire event is available there. We therefore recommend you create an own event reason for the rehire process across system borders and attach it to the Hire event.

A new user is created in Employee Central for the new employment.

In the side-by-side deployment model described in this guide, 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.

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. In the side-by-side deployment model described in this guide, 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 record in Employee Central if the following conditions are fulfilled for both personnel numbers:

● They are assigned to different countries.● Only one of them is active.● The Leaving and Hiring actions were carried out for them.

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

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

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. In the side-by-side deployment model described in this guide, 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.

NoteA new user is created in Employee Central for the new employment.


5.5.4 Transferring an Employee from a Country Mastered in Employee Central to a Country Mastered in SAP ERP HCM


5.6 Global Assignment

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.

5.6.2 Assigning an Employee Globally Within Employee Central

Global assignment management in Employee Central works as usual. In the side-by-side deployment model described in this guide, 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

Home assignment in Employee Central, host assignment in SAP ERP HCM

If an employee has a home assignment (employment) in Employee Central and a host assignment in SAP ERP HCM, his or her data can be replicated from SAP ERP HCM to Employee Central. Both assignments can coexist.

To make this process work:



● Select the BAdI Mapping mapping mode for the person_id_external field in the V_ECPAO_COMPANY Customizing view. For more information, refer to section Define Employee Central Company [page 19].

● Implement the Mapping of User ID, Person ID, and User Name (EX_ECPAO_EMP_USYID_PRN_UNM_MAP) BAdI. Make sure that your BAdI implementation contains the employee's person ID from Employee Central so that the data from the host assignment in SAP ERP HCM is replicated to the correct employee in Employee Central.

Home assignment in SAP ERP HCM, host assignment in Employee Central

If an employee has a home assignment in SAP ERP HCM and his or her data is replicated to Employee Central, you can just add the host assignment (employment) in Employee Central. Both assignments can coexist.

You can choose any mapping for the user_id, person_id_external, and user field in the V_ECPAO_COMPANY Customizing view.

In this scenario, the person-related employee master data is kept up to date in the SAP ERP HCM system for the home assignment. Changes are replicated to Employee Central.

Deactivating the home assignment

To deactivate the home assignment during the host assignment period, terminate the employee's home assignment when the host assignment starts and rehire the employee when the host assignment ends.

5.7 Concurrent Employment

5.7.1 Concurrently Employing an Employee Within SAP ERP HCM

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

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


5.7.2 Concurrently Employing an Employee Within Employee Central

The concurrent employment process in Employee Central works as usual. In the side-by-side deployment model described in this guide, employees whose data is mastered in Employee Central aren't replicated to SAP ERP HCM.

5.7.3 Concurrently Employing an Employee Within SAP ERP HCM and Employee Central


5.8 Termination

You can terminate employees either in SAP ERP HCM or in Employee Central.

5.8.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 ensures 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.8.2 Terminating an Employee Mastered in Employee Central

The termination process in Employee Central works as usual. In the side-by-side deployment model described in this guide, employees whose data is mastered in Employee Central aren't replicated to SAP ERP HCM.



6 Integration of the Employee Central UI with the On-Premise SAP ERP HCM System

You can use the UI integration in different scenarios of the side-by-side deployment model.

In the distributed scenario of the side-by-side deployment model, managers and employees can use the SuccessFactors 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. This is possible since all employees whose data is mastered in SAP ERP HCM are replicated to Employee Central using the employee data integration of the side-by-side deployment model. Example use cases of this scenario are:

● A manager wants to trigger a change for one of his or her employees using a workflow. The employee is mastered in the SAP ERP HCM system. The manager uses the SuccessFactors homepage as his or her global UI hub to manage all relevant HR processes and his or her team. So the manager can trigger changes for employees from the SuccessFactors homepage, independent of whether their data is mastered in SAP ERP HCM or in Employee Central. The UI integration allows for Manager Self-Service screens from SAP ERP HCM to be embedded as iFrames within the Employee Central screens.

● An employee wants to change his or her address data. The employee's data is mastered in the SAP ERP HCM system. The employee uses the SuccessFactors homepage as his or her global UI hub to handle all relevant HR processes. So the employee can change his or her address data from the SuccessFactors homepage. The UI integration allows for Employee Self-Service screens from SAP ERP HCM to be embedded as iFrames within the Employee Central screens.

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. Example use cases of this scenario are:

● A manager wants to trigger a change for one of his or her employees using a workflow. The manager uses the SuccessFactors homepage as his or her global UI hub to manage all relevant HR processes and his or her

Employee Central and SAP ERP: Side-by-Side Deployment ModelIntegration of the Employee Central UI with the On-Premise SAP ERP HCM System © 2015 SAP SE or an SAP affiliate company. All rights reserved. 93

team. All employees are mastered in Employee Central, but the local SAP ERP HCM system is still used for some local (for example, country-specific) processes. So the manager can also trigger such a local process from the SuccessFactors homepage.The UI integration allows for screens from SAP ERP HCM that are used to carry out local processes to be embedded as iFrames within the Employee Central screens. All global Manager Self-Service processes run in Employee Central.

● An employee wants to trigger a change of his or her data. The employee uses the SuccessFactors homepage as his or her global UI hub to handle all relevant HR processes. All employees are mastered in Employee Central, but the local SAP ERP HCM system is still used for some local (for example, country-specific) processes. So the employee can also trigger such a local process from the SuccessFactors homepage.The UI integration allows for screens from SAP ERP HCM that are used to carry out local processes to be embedded as iFrames within the Employee Central screens. All global Employee Self-Service processes run in Employee Central.

For more information about the scenarios, refer to section Introduction [page 5].

NoteYou 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.

To avoid users having to log on several times, make sure that browser single sign-on works for your Web browser if you use the UI integration.

6.1 Manager Self-Service Use Cases

6.1.1 Configuring the UI Integration in the SAP ERP HCM System

You only need to configure the SAP ERP HCM system for Manager Self-Service use cases.

In this section we describe the configuration steps for a Manager Self-Service scenario based on Web Dynpro for ABAP, which uses the HCM Processes and Forms technology when managers carry out processes such as changing an employee's working time or transferring an employee to a new position.

For Employee Self-Service 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 UI Integration in Employee Central [page 101].


Integration of the Employee Central UI with the On-Premise SAP ERP HCM System

6.1.1.1 Create an SICF Handler for the Communication of Employee Central with SAP ERP HCM

For Manager Self-Service use cases, you must create a new SICF handler in the SAP ERP HCM system that can be called in Employee Central within the iFrame on the Profile Update page.

Context

You can use the standard handler class CL_SFIUI_REDIRECT_HANDLER for your SICF handler. This handler class displays the HR Processes and Forms process overview for processes using forms based on Adobe Forms. The class performs the following actions:

1. It takes into account the parameters users_sys_id, employment_id, company_code, and legal_entity 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 instead of ASR_PROCESS_EXECUTE, you can use the standard handler class CL_SFIUI_REDIRECT_HANDLER as a template, which you can copy and adapt to your needs.

To create an SICF handler, carry out these steps:

Procedure

1. Log on to your SAP ERP HCM system, go to the Maintain Services (SICF) transaction, and press F8 .


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:

○ 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.

4. Save and activate your service.



6.1.1.2 Optional: Adjust the ASR_PROCESS_EXECUTE Web Dynpro Application to Hide the Roadmap

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 .


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:



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


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.



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 Manager Self-Service and Employee Self-Service Use Cases

6.2.1 Configuring the UI Integration in Employee Central

Configuration in Employee Central is needed for Manager Self-Service and Employee Self-Service use cases.

6.2.1.1 Activate the UI Integration in Provisioning

Procedure

1. Log on to Provisioning of the relevant instance and choose Edit Company Settings Company Settings .2. Select the Enable UI Integration with SAP ERP Systems checkbox.3. Click Save Feature.


6.2.1.2 Create a Picklist for the RuleType Field

Procedure


2. In the Company Processes & Cycles portlet, select Company Settings Configure Object Definitions .3. Create a picklist for the RuleType field (if it doesn't exist yet) and configure it as shown in this example:

These picklist values represent the events to be used for the business rule that will be triggered.

NoteIf there's already a picklist, make sure that it contains the values as shown above.



6.2.1.3 Configure Navigation Groups and Assigned Navigation Targets to Define the URLs

Prerequisites

If you've already created customer-specific generic objects such as cust_ThirdPartySystem that were required for the previous delivery of the side-by-side deployment model, delete the corresponding data records and object definitions before you start configuring navigation groups as described below.

Procedure

1. Go back to Administration Tools.

2. In the Company Processes & Cycles portlet, select Employee Files Manage Data .3. Add instances to the Navigation Group object specifying the Navigation Group information such as code and

external name and the associated navigation targets (URLs) as shown in this example:

The Code field of the entries in the Navigation Target Assignment section must not contain spaces. The External Name fields of the navigation group and the navigation target assignments can be translated.

4. In the Type of Service field, enter Employee Self-Service or Manager Self-Service to specify when which link is to be displayed.The Employee Self-Service 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 Manager Self-Service type means that the link is displayed when the user who is logged on to Employee Central changes data of another user.

5. In the URL field of each navigation target, enter the URL to your new SICF handler(s) that you’ve created as described in section Create an SICF Handler for the Communication of Employee Central with SAP ERP HCM [page 95]. You can also enter links to external services or direct links to applications within your SAP ERP system.For URLs with the Manager Self-Service type, Employee Central automatically adds the URL parameter users_sys_id to the URL before calling the target system. This parameter is filled with the PersonId from the Employment Information. In addition, the URL parameters employment_id, company_code, and legal_entity are added to ensure that the called application can identify the person whose data is to be changed.


6.2.1.4 Configure the Succession Data Model

Procedure

1. Log on to Provisioning of the relevant instance and download the current Succession Data Model configuration.

2. Open the XML file in a suitable editor.3. Search for the HRIS element with the ID employmentInfo and make the following changes only for this

element (between the last label for the employmentInfo HRIS element and the first hris-field element):a. Add a trigger-rule tag with the type onView using a suitable rule ID as shown in this example:

<trigger-rule event="onView" rule="EMPLOYMENT_ONVIEW" />

b. Define a custom field in the custom field range for employmentInfo that will store the information about the target system to be called, as shown in this example:

<hris-field max-length="256" id="custom-string23" visibility="view" type="NavigationGroup"> <label>Navigation Group</label> </hris-field>

The ID doesn't necessarily have to be custom-string23. You can choose any custom field that is not yet used in the customer's data model, such as custom-string20 or custom-string12. The type has to be NavigationGroup, but you can choose any label.

4. Upload the changed Succession Data Model.

6.2.1.5 Configure the Business Rule to Define Which Set of URLs Is to Be Called for Which Group of Employees

Procedure


2. In the Company Processes & Cycles portlet, select Company Settings Configure Business Rule .3. Create an onView rule that fills the custom field created in the Succession Data Model for storing information

about the target system to be called based on data that is stored in the employee's Job Information record (such as the Business Unit), as shown in this example:



CautionThe 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.

6.2.1.6 Set Up Role-Based Permissions to Display the URLs in the Take Action Menu

Use role-based permissions to display the URLs you have created as described in the previous steps in the Take Action menu of specific employees.

Procedure


2. In the Manage Employees portlet, select Set User Permissions Manage Permission Roles .3. Select your permission role.4. On the Permission Role Detail screen, click Permission....5. Click Employee Data.6. Scroll down to the Employment Details section.7. Select the View checkbox for Navigation Group.8. Select the Edit checkbox for Navigation Group Entry in Take Action Menu.

It's not sufficient to select the View checkbox for this permission.

Next Steps

If you use the employee data replication from SAP ERP HCM to Employee Central, make sure that every employee whose data is mastered in SAP ERP HCM and replicated to Employee Central gets these permissions.


6.2.1.7 You're done! Now Check the Result

Procedure

1. After executing all steps described above, check the Take Action menu in Employee Central.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 these examples:

○ Manager's view

In this example, you see the Take Action menu for Karen Martha Smith when she looks at her employee Daniela Deutsch. Her menu contains all URLs that you have configured with the Manager Self-Service type in addition to the standard Employee Central actions (such as Give a badge).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.

○ Employee's view



In this example, you see the Take Action menu for Daniela Deutsch. Her menu contains the URLs that you have configured with the Employee Self-Service type in addition to the standard Employee Central actions (such as Add Note).

Next Steps

You can reduce the number of entries in the Take Action menu using role-based permissions. For employees whose data is mastered in SAP ERP HCM and replicated to Employee Central, you might, for example, hide all actions that can't be carried out in Employee Central because the corresponding data needs to be changed in SAP ERP HCM.

To hide, for example, the Add Employment Details entry, carry out these steps:


2. In the Manage Employees portlet, select Set User Permissions Manage Permission Roles .3. Select your permission role.4. On the Permission Role Detail screen, click Permission....5. Click Employee Data.6. Scroll down to the Employment Details section.7. Deselect the Edit checkbox for Employment Details MSS.

For the other entries, deactivate the corresponding permissions accordingly.


6.2.1.8 Disabling the Edit Mode in Employee Central for Data Mastered in Another System

If data is mastered in another system (for example, in an on-premise SAP ERP HCM system) and only replicated to Employee Central, make sure that this data can't be changed in Employee Central.

Use the conditions that you have used to define the business rule for setting the Navigation Group field value also to define for which groups of employees the edit mode in Employee Central should be enabled or disabled. If you have, for example, used a specific Business Unit as the condition, you should also use the Business Unit to define for which employees data editing in Employee Central is not allowed.

Use role-based permissions to disable the edit mode in Employee Central.

Related Information

Configure the Business Rule to Define Which Set of URLs Is to Be Called for Which Group of Employees [page 104]



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.

NoteDepending 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.

Employee Central and SAP ERP: Side-by-Side Deployment ModelYou're done! What’s Next? © 2015 SAP SE or an SAP affiliate company. All rights reserved. 109

8 Change History

The following table provides an overview of the changes made to this document since the last release.


Change History

Table 5:

Release Version Date Description

Q1 2015 1.0 February 6, 2015 New sections:

● Map Organizational Management Fields from SAP ERP HCM to Employee Central [page 31]

● Extract Organizational Management Data [page 33]● Preconfigured Mapping of SAP ERP HCM Fields to Employee Central

Fields [page 54]● How to Migrate from Employee Data Integration with the Success

Factors Talent Suite to Employee Data Integration in the Side-by-Side Deployment Model [page 78]

● Concurrent Employment with subsections:

○ Concurrently Employing an Employee Within SAP ERP HCM [page 91]

○ Concurrently Employing an Employee Within Employee Central [page 92]

○ Concurrently Employing an Employee Within SAP ERP HCM and Employee Central [page 92]

● Set Up Role-Based Permissions to Display the URLs in the Take Action Menu [page 105]

Changed sections:

● Introduction [page 5] and Integration of the Employee Central UI with the On-Premise SAP ERP HCM System [page 93]: Restriction about UI integration removed - leveraging Employee Central as the UI navigation hub for Employee Self-Service and Manager Self-Service use cases is now generally available

● Check if the Customer System is Prepared to Integrate with Employee Central [page 9]: Required PA_SE_IN 100 support package changed

● Supported Employee Central Entities [page 11]: List updated● Import Default Customizing Into Your Working Client in the SAP ERP

HCM System [page 17]: Transporting the entries in the ECPAO_FLD Customizing table from client 000 to your working client is no longer necessary since a new V_ECPAO_FLD Customizing view is now available

● Import Metadata from Employee Central [page 20]: Information about new Check Imported Employee Metadata Customizing activity added

● Define Types of Manager Relationships [page 26], Determine the Employees' Managers [page 28], Handle Managers in the SAP ERP HCM System Whose Data Is Mastered in Employee Central [page 30]: System object names and screenshots updated, sections moved to new Handling Manager Relationships section

Employee Central and SAP ERP: Side-by-Side Deployment ModelChange History © 2015 SAP SE or an SAP affiliate company. All rights reserved. 111

Release Version Date Description

● Define Employee Central Templates [page 33]: Restriction removed that name of Employee Central templates for MDF entities has to start with the prefix cust_

● Extract Employee Master Data [page 43]: Information about new .zip option added

● Implement Business Add-Ins for the Replication of Employee Master Data [page 50]: Information about new Extraction of Organizational Management Data BAdI added

● Configure the Employee Key Data Query Process [page 58]: Information about new INCLUDE_LOG_DATA process parameter added

● Prerequisites and Restrictions [page 82]: Restrictions updated● Rehiring an Employee in Employee Central Who Was Previously

Mastered in SAP ERP HCM [page 87]: Information about event reason added

● Integration of the Employee Central UI with the On-Premise SAP ERP HCM System [page 93]: Some detailed information added, for example, about the use cases


Change History

Important Disclaimers and Legal Information

Coding SamplesAny 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.

AccessibilityThe 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 LanguageAs 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 HyperlinksThe 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 ModelImportant Disclaimers and Legal Information © 2015 SAP SE or an SAP affiliate company. All rights reserved. 113

http://help.sap.com/disclaimer/

www.sap.com/contactsap

© 2015 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.

http://www.sap.com/contactsap

http://www.sap.com/corporate-en/legal/copyright/index.epx

http://www.sap.com/corporate-en/legal/copyright/index.epx

employee central and sap erp: side-by-side deployment...

Documents