Employee Central and SAP ERP (1)

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. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 61.2 Terminology. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 61.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. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .11Business Scenario: Employee Data Replication. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 11Supported Employee Central Entities. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 11Communication Channels for the Replication of Employee Master Data. . . . . . . . . . . . . . . . . . . . . . 13Defining Customer-Specific Activities. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 15

3.2 Setting up Employee Central for the Replication of Employee Data. . . . . . . . . . . . . . . . . . . . . . . . . . . . 51Create Event Reasons in Employee Central. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 51

3.3 Master Data Replication Information. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 53Standard Employee Central Fields. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 53Standard Mapping of SAP ERP HCM Fields to Employee Central Fields. . . . . . . . . . . . . . . . . . . . . . 54Preconfigured Mapping of SAP ERP HCM Fields to Employee Central Fields. . . . . . . . . . . . . . . . . . 54Sample Mapping of SAP ERP HCM Fields to Employee Central Fields. . . . . . . . . . . . . . . . . . . . . . . 55

3.4 Setting up the Middleware. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 55Preparing the Middleware System. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 55Configuring the Middleware System. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 56Configuring the SAP ERP HCM System. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .59

3.5 Setting up Employee Central Time Off for Employees Mastered in SAP ERP HCM. . . . . . . . . . . . . . . . . 63Create a Business Rule. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 63Configure the Succession Data Model. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 64Configure the Company System Settings. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 65Check the Company Code Mapping. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 66Configure the Template Group. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 68Map the Employee Central Time Types to SAP ERP Absence Types. . . . . . . . . . . . . . . . . . . . . . . . 69Set up the Middleware. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 72Extract Employee Data. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 72Request Time Off in Employee Central. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 72Check 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! Whats 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

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 versionSAP NetWeaver SAP_BASIS 700 SP18 or higherSAP ERP SAP_APPL 600 SP15 or higherIntegration 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

Table 1:SAP Note Number Title Description Contained in Support Pack

age

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

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 User2 Biographical Information PerPerson3 Personal Information PerPersonal4 Employment Details EmpEmployment5 Global Assignment EmpGlobalAssignment6 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 PerEmail8 Phone Info PerPhone9 Job Relationships EmpJobRelationships10 Addresses PerAdressDEFLT11 Compensation Info EmpCompensation12 Pay Component Recurring EmpPayCompRecurring13 Pay Component Non Recurring EmpPayCompNonRecurring14 Payment Information-Details PaymentInformationDetailV315 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 Central

To use this framework:1. Go to Administration Tools.2. In the Manage Employees portlet, select Update User Information Import Employee Data .

Using a synchronous Web service call and the Boomi Atomsphere middleware


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

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 EntityYou 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 Extraction

To download metadata of the CSV Data Import Entity type:1. Go to Administration Tools.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:1. Go to Administration Tools.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.


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 Relationships3.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 MThe 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 M2The 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 M2The 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 DataYou 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 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. 33

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.

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

Choose 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_CODE

You 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 field

This is one of the fields from the infotype or subtype that you have defined in the primary mapping. You can choose the linking field from the value help in the Secondary Mapping view. The linking field is dynamically populated based on the infotype or subtype you have specified in the Primary Mapping view.

Based on the infotype view indicator (field VIEKN from the Payroll Status (0003) infotype)


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:1. Go to Administration Tools.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//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

1. Go to the ABAP: Program Execution (SA38) transaction.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 and SAP ERP: Side-by-Side Deployment Mod

Documents

Employee Central and SAP ERP (1)