Replicating Employee Time Data from ... - help.sap.com

Implementation Guide | PUBLICDocument Version: 1H 2022 – 2022-04-22

Replicating Employee Time Data from Employee Central to SAP ERP HCM Using SAP Cloud Integration as the Middleware

© 2

022

SAP

SE o

r an

SAP affi

liate

com

pany

. All r

ight

s re

serv

ed.

THE BEST RUN

Content

1 Before Starting: Am I reading the right documentation?. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5

2 Introduction to Employee Time Data Replication. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 92.1 What's Good to Know Before You Start Replicating Employee Time Data. . . . . . . . . . . . . . . . . . . . . 102.2 Your Integration Team. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 122.3 Target Group of This Document. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 122.4 Country/Region-Specific Information. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13

3 System Preparation for Employee Time Data Replication. . . . . . . . . . . . . . . . . . . . . . . . . . . . . 143.1 Checking the Minimum Setup Required for Your Systems. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 143.2 How to Keep Your Systems in Sync. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 183.3 Permissions for Employee Time Data Replication. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 19

Permissions Required for API Access. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 19Permissions Required to Access the Data Replication Objects. . . . . . . . . . . . . . . . . . . . . . . . . . 20Granting SAP ERP HCM Permissions for Employee Time Data Replication. . . . . . . . . . . . . . . . . . 21

3.4 Employee Central Preparation for Replication of Employee Time Data. . . . . . . . . . . . . . . . . . . . . . . 22Enabling the OData API Audit Log. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 23External Codes Must Not Be Longer Than 32 Characters. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 23Creating Replication Target System. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 24Creating Data Replication Configuration Objects. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .24Configuring Data Replication Configuration Object for Leave of Absence (LoA) Scenarios. . . . . . . 27Creating a Value Help for Employee Class for Time Sheet Data Replication. . . . . . . . . . . . . . . . . 28

4 Concepts of Employee Time Data Replication. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 304.1 Why Replicate Employee Time Data from Employee Central?. . . . . . . . . . . . . . . . . . . . . . . . . . . . . 304.2 APIs and Web Services Used for Time Data Replication. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 314.3 Terminology. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 32

5 SAP ERP HCM System Configuration for Replication of Employee Time Data. . . . . . . . . . . . . . 335.1 Enabling the SAP ERP HCM Inbound Web Service to Set Up the Connection from the Middleware

to SAP ERP HCM. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 335.2 Enabling Creation of the Confirmation Message. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .345.3 Configuration of Time Off Data Replication in the SAP ERP HCM System. . . . . . . . . . . . . . . . . . . . . 35

Disabling Collision Checks for Overlapping Time Infotype Records. . . . . . . . . . . . . . . . . . . . . . . 36Disabling Quota Deduction. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 37Configuring Absence Input Checks. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 38Configuring Attendances and Absences to Be Recorded Without Clock Times. . . . . . . . . . . . . . . 39Mapping Time Types with Absence Types and Work Schedules with Work Schedule Rules. . . . . . 40

2 PUBLIC


Content

Configuring Time Evaluation Schema for Payroll Processing. . . . . . . . . . . . . . . . . . . . . . . . . . . 42Disabling the Default Work Schedule Logic. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 43

5.4 Configuration of Time Sheet Data Replication in the SAP ERP HCM System. . . . . . . . . . . . . . . . . . . 44Mapping Time Pay Types with Time Wage Types. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 45Enabling Time Wage Types for Multiple Entries Per Day. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 46Configuring Basis Unit and Allowed Input Combination for Time Wage Types. . . . . . . . . . . . . . . . 47Mapping Cost Center Keys. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 48

6 Middleware Setup. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 506.1 Middleware Content for Employee Time Data Replication. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 516.2 Prerequisites for Using SAP Cloud Integration. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 536.3 Communication Within the Employee Time Data Integration Scenario. . . . . . . . . . . . . . . . . . . . . . . 546.4 Configuration of SAP Cloud Integration for Employee Time Data Replication. . . . . . . . . . . . . . . . . . 55

Configuring Certificates and Permissions. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .56Configuring Credentials for Communication Between SAP Cloud Integration and the Integrated Systems. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 57How to Find the Endpoint URLs and Target System. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 58Copying the Integration Package to Your Workspace. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 62Configuring the Integration Flows for Employee Time Data Replication. . . . . . . . . . . . . . . . . . . . 63Scheduling the Integration Flows for Employee Time Data Replication. . . . . . . . . . . . . . . . . . . . .67Testing Connectivity of the Integration Flows for Employee Time Data Replication. . . . . . . . . . . . 68

6.5 Monitoring in SAP Cloud Integration. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .686.6 How to Report a Middleware Incident. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 68

7 Replication of Employee Time Data. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 707.1 Example: Replication of Absences to SAP ERP HCM. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 707.2 Example: Replication of Employee Time Valuation Result to SAP ERP HCM. . . . . . . . . . . . . . . . . . . .737.3 Replication of Country/Region-Specific Time Off Data. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 77

Replication of Time Off Data for Colombia. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 77Replication of Time Off Data for Germany. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 80Replication of Time Off Data for Mexico. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 88Replication of Time Off Data for Spain. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 91

8 You're done! What's Next?. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 958.1 Monitoring of Employee Time Data Replication. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 95

Employee Central Data Replication Monitor. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 96Monitoring Tools in the SAP ERP HCM System: Web Service Utilities and Application Log. . . . . . . 96

8.2 How to Avoid Unnecessary Time Data Replication. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 978.3 How to Trigger Replication of Existing Absences or Time Sheets. . . . . . . . . . . . . . . . . . . . . . . . . . . 978.4 Deleting Inconsistent Employee Time Data in SAP ERP HCM. . . . . . . . . . . . . . . . . . . . . . . . . . . . . .988.5 HTTPS Connectivity. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1008.6 Performance Optimization of This Integration. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1008.7 Handling of Data Purge in the Replication. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 101

Replicating Employee Time Data from Employee Central to SAP ERP HCM Using SAP Cloud Integration as the MiddlewareContent PUBLIC 3

Purge of Employee Time Data Replicated to SAP ERP HCM. . . . . . . . . . . . . . . . . . . . . . . . . . . 102Purge of Application Logs in SAP ERP HCM. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .105

4 PUBLIC


Content

1 Before Starting: Am I reading the right documentation?

Before you start looking for information in this guide, you need to be sure you're looking in the right place.

This guide describes how to set up integration between SAP ERP HCM and SAP SuccessFactors Employee Central. It assumes that you have a team of experts in place who know their ways in the systems involved in the integration.

What this guide does not describe:

● How to set up and use Employee Central. For example:○ How to configure object types in Employee Central. We tell you which prerequisites object types must

fulfill so that they can be replicated between SAP ERP HCM and Employee Central. For example, whether a length restriction applies to a specific field. For basics such as how to restrict the length of a field, please see the Employee Central documentation.

○ Why and how to enable Position Management in Employee Central. We tell you what happens in the integration if Position Management is or is not enabled. For basics such as when and how to enable it, please see the Employee Central documentation.

● How to set up and use the SAP ERP HCM system. For example:○ How to use the Customizing Implementation Guide (IMG) in your system. We tell you which

Customizing activities and settings are relevant for integration. For basics such as how to make entries in Customizing views or how to implement a Business Add-In, please see the SAP ERP HCM documentation.

○ How to create a variant for a program or schedule it to be run in the background. We tell you which programs you need to execute or schedule. For basics such as how to define variants or background jobs, please see the SAP ERP HCM documentation.

● How to set up and use the middleware. For example:○ How to find and use the monitoring UI. We tell you what you should pay attention to when monitoring

integration flows. For basics such as how to use middleware monitoring in general, please see the middleware documentation.

○ How to upload a certficate. We tell you when a certificate is required. For basics such as how to upload it, please see the middleware documentation.

Check out the information below to learn how to set up and use the systems that are involved in the integration.

Table 1: Relevant Documentation

Looking for information about... See...

Employee Central https://help.sap.com/viewer/p/SAP_SUCCESSFACTORS_EMPLOYEE_CENTRAL > Implementation

Replicating Employee Time Data from Employee Central to SAP ERP HCM Using SAP Cloud Integration as the MiddlewareBefore Starting: Am I reading the right documentation? PUBLIC 5

https://help.sap.com/viewer/p/SAP_SUCCESSFACTORS_EMPLOYEE_CENTRAL

https://help.sap.com/viewer/p/SAP_SUCCESSFACTORS_EMPLOYEE_CENTRAL

Looking for information about... See...

SAP ERP HCM For platform information: https://help.sap.com/viewer/p/SAP_NETWEAVER > choose your SAP NetWeaver release

For information about SAP ERP in general: https://help.sap.com/viewer/p/SAP_ERP

For specific information about SAP ERP HCM: https://help.sap.com/viewer/p/ERP_HCM

Middleware https://help.sap.com/viewer/p/CLOUD_INTEGRATION

6 PUBLIC


Before Starting: Am I reading the right documentation?

https://help.sap.com/viewer/p/SAP_NETWEAVER


https://help.sap.com/viewer/p/SAP_ERP

https://help.sap.com/viewer/p/SAP_ERP

https://help.sap.com/viewer/p/ERP_HCM


https://help.sap.com/viewer/p/CLOUD_INTEGRATION

Change History

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

1H 2022 / PA_SE_IN SP33

Type of Change Description More Info

Changed Support package 33 of the PA_SE_IN software component is required in the SAP ERP HCM system.

Checking the Minimum Setup Required for Your Systems [page 14]

Added Reasons to exclude absence records from electronic communication with public health insurance companies are now replicated from Employee Central so that payroll in the SAP ERP HCM system can exclude these absence records from the communication.

NoteThis feature is in the Early Adoption phase. For more information, refer to Including an eAU Exclusion Reason in an Absence in Implementing Time Management in SAP SuccessFactors.

Replication of Exclusion Reasons for the Electronic Certificate of Incapacity for Work (eAU) in Germany [page 83]

Mapping Exclusion Reasons from Employee Central to Exclusion Reasons in SAP ERP HCM [page 84]

How Absence Fields Are Mapped for Germany [page 86]

2H 2021


Added We added that the integration add-on for SAP ERP HCM and SAP SuccessFactors Employee Central (SFSF EC INTEGRATION 1210) can be used to integrate the cloud HR solution provided by SAP (SAP SuccessFactors) with on-premise ERP applications provided by SAP (SAP ERP HCM) only.

Introduction to Employee Time Data Replication [page 9]

Replicating Employee Time Data from Employee Central to SAP ERP HCM Using SAP Cloud Integration as the MiddlewareChange History PUBLIC 7

https://help.sap.com/viewer/68de09dff990417b9f0acf6ccc13a14d/latest/en-US/7443ed78634f4caf8b5a9e8963e226b0.html



Changed The middleware now ensures that the URL you enter for ERP receivers in the integration flows starts with https:// if the proxy type is set to Internet.

Configuring the Integration Flows for Employee Time Data Replication [page 63]

Added We added the OAuth2 SAML Bearer Assertion authentication option in the configuration of Employee Central receivers for the integration flows.

Configuring Credentials for Communication Between SAP Cloud Integration and the Integrated Systems [page 57]

Configuring the Integration Flows for Employee Time Data Replication [page 63]

8 PUBLIC


Change History

2 Introduction to Employee Time Data Replication

Learn about replication of employee time data from Employee Central to your SAP ERP HCM system.

The integration we explain here is about replicating employee time data from SAP SuccessFactors Employee Central Time Off and Time Sheet to an SAP ERP HCM system in which you run an SAP Payroll.

RestrictionThe integration add-on for SAP ERP HCM and SAP SuccessFactors Employee Central (SFSF EC INTEGRATION 1210) can be used to integrate the cloud HR solution provided by SAP (SAP SuccessFactors) with on-premise ERP applications provided by SAP (SAP ERP HCM) only. The add-on is included in the license for these systems.

The add-on cannot be licensed to use for integration between non-SAP cloud HR solutions and SAP ERP HCM.

Employee time data integration supports the Core Hybrid HXM deployment option. Core Hybrid HXM means that Employee Central is used as the system of record holding the employee data and reporting lines of all employees. But existing HR processes such as Payroll or custom HR processes still run in an SAP ERP HCM system landscape. If you’re using the Core Hybrid HXM deployment option and want to replicate employee time data to SAP ERP HCM, go through all implementation steps we describe in this document. The integration sequence covers the main integration points in the most efficient order. However, each customer has their own special requirements. Various factors, such as the country/region in which your customer’s company is located and your company’s line of business influence how you set up the integration between SAP ERP HCM and Employee Central.

If you’re interested in more information about the Core Hybrid HXM deployment option, go to this guide: Integrating SAP ERP HCM with Employee Central Using the Core Hybrid Deployment Option

What's Good to Know Before You Start Replicating Employee Time Data [page 10]There are a number of things that need to be in place before you start building the integration between Employee Central and SAP ERP HCM for time data replication.

Your Integration Team [page 12]The implementation and integration process of SAP SuccessFactors Employee Central with SAP ERP HCM is a collaborative effort that leverages the skills of various experts.

Target Group of This Document [page 12]Take a look at the target groups this document is intended for.

Country/Region-Specific Information [page 13]You can replicate some country-specifc or region-specific employee time data from Employee Central to the SAP ERP HCM system.

Replicating Employee Time Data from Employee Central to SAP ERP HCM Using SAP Cloud Integration as the MiddlewareIntroduction to Employee Time Data Replication PUBLIC 9

https://help.sap.com/viewer/ed305ea08ebc4c4880b2a2ddd498e6d0

Related Information

System Preparation for Employee Time Data Replication [page 14]Concepts of Employee Time Data Replication [page 30]SAP ERP HCM System Configuration for Replication of Employee Time Data [page 33]Middleware Setup [page 50]Replication of Employee Time Data [page 70]

2.1 What's Good to Know Before You Start Replicating Employee Time Data

There are a number of things that need to be in place before you start building the integration between Employee Central and SAP ERP HCM for time data replication.

Employee Central Must Be Your System of Record for Time Management

Replication of employee time data from Employee Central to SAP ERP HCM requires that Employee Central is your system of record for Time Management, which handles the time off data (absences) and the time sheet data of your employees. Time data replication to SAP ERP HCM is meant for use in payroll processing only. You can’t use the replicated data to operate Time Management in the SAP ERP HCM system. Not all time data is replicated, so not all use cases can be supported. Clock times aren't replicated for absences, for example. You must not change the replicated data in the SAP ERP HCM system either.

You can, however, view the replicated data in display transactions such as Display Time Data (PA51) or Time Management Workbench (PTMW). You can also use it in reports such as absence statistics.

Modules Required by Employee Time Data Integration

The following modules must already be set up and running in your system landscape:

● SAP SuccessFactors Employee CentralFor more information, refer to Implementing Employee Central Core.

● SAP SuccessFactors Time OffFor more information, refer to Implementing Employee Central Time Management.

● SAP SuccessFactors Time SheetFor more information, refer to Implementing Employee Central Time Management.

● SAP ERP HCMFor more information, refer to the component-based product documentation for SAP ERP HCM at https://help.sap.com/viewer/p/ERP_HCM.

● Employee master data replication from Employee Central to SAP ERP HCM, including the confirmation message

10 PUBLIC


Introduction to Employee Time Data Replication

https://help.sap.com/viewer/b14dd15ca58f43e0856184a740a4b212

https://help.sap.com/viewer/68de09dff990417b9f0acf6ccc13a14d

https://help.sap.com/viewer/68de09dff990417b9f0acf6ccc13a14d



For more information, refer to Replicating Employee Master Data and Organizational Assignments from Employee Central to SAP ERP HCM.

Employee Master Data Must Have Been Replicated

All employee master data must already be replicated successfully to SAP ERP HCM, before you can replicate payroll-relevant time data to SAP ERP HCM.

Don't Change Replicated Data

NoteDon't change any data that was replicated from Employee Central in the SAP ERP HCM system. Your changes would probably be overwritten by the next replication run from Employee Central. They wouldn't be replicated back to Employee Central either. That is, the systems would no longer be in sync.

Time Off Data Replication Requires Specific Configurations

NoteClock time information is not replicated from Employee Central to the SAP ERP HCM system. Therefore, make sure that SAP ERP HCM is set up in a way so that absences and attendances are recorded without clock times.

CautionIt's crucial that data consistency checks and employee time-related calculations such as quota deductions are carried out in Employee Central. Therefore, please make sure that you disable these checks in SAP ERP HCM. Or else, checks and calculations being done in SAP ERP HCM might prevent data from being updated, but the related error messages will only be shown to admins in the Employee Central Data Replication Monitor and won't be visible for the end user who enters time data in Employee Central. That's why all checks must take place in Employee Central and not in the SAP ERP HCM system.


https://help.sap.com/viewer/a7f164924edd4dfe817b7bdc2fc4927a


2.2 Your Integration Team

The implementation and integration process of SAP SuccessFactors Employee Central with SAP ERP HCM is a collaborative effort that leverages the skills of various experts.

You need to pull together a team of experts for your implementation project when integrating SAP SuccessFactors Employee Central with SAP ERP HCM. The key experts typically involved in the process are as follows:

Table 2: Your Integration Team

This expert… Does these activities…

SAP SuccessFactors consultant ● Is the main point of contact for the entire implementation and integration process.

● Ensures that all required system settings for Employee Central are done.

● Works closely with the SAP ERP HCM team, to ensure successful data replication.

Middleware consultant Provides support on setting up the middleware.

SAP ERP HCM consultant ● Is the main point of contact for the configuration of SAP ERP HCM according to the needs of the customer.

● Works closely with the SAP SuccessFactors consultant to ensure successful data replication.

2.3 Target Group of This Document

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

The following groups of people will benefit from reading this document:

● Implementation partners, consultants, and Product Support, for fast support of customers and prospective customers

● Cloud operations● SAP-certified administrators at customer site

12 PUBLIC


Introduction to Employee Time Data Replication

2.4 Country/Region-Specific Information

You can replicate some country-specifc or region-specific employee time data from Employee Central to the SAP ERP HCM system.

Table 3: The following table provides an overview of country/region specifics in this guide

Country/Region More Info

Colombia Replication of Time Off Data for Colombia [page 77]

Germany Replication of Time Off Data for Germany [page 80]

Mexico Replication of Time Off Data for Mexico [page 88]

Spain Replication of Time Off Data for Spain [page 91]


3 System Preparation for Employee Time Data Replication

Learn more about what needs to be in place if you want to replicate employee time data from Employee Central.

Checking the Minimum Setup Required for Your Systems [page 14]Check if your systems are ready so that you can set up time data replication from Employee Central to SAP ERP HCM.

How to Keep Your Systems in Sync [page 18]Why we recommend installing the latest support package of the integration add-on in your on-premise SAP ERP HCM system.

Permissions for Employee Time Data Replication [page 19]Set up the permissions needed by API users and administrators in Employee Central, as well as permissions for technical users in the SAP ERP HCM system.

Employee Central Preparation for Replication of Employee Time Data [page 22]How to configure Employee Central so that it can communicate time data to SAP ERP HCM.

3.1 Checking the Minimum Setup Required for Your Systems

Check if your systems are ready so that you can set up time data replication from Employee Central to SAP ERP HCM.

Procedure

1. Is Employee Central set up?

For more information, refer to Implementing Employee Central Core.2. Is the middleware already set up?

For more information about how to set up SAP Cloud Integration, refer to SAP Cloud Integration.

CautionYou are only allowed to configure the content as described in this guide. If you make modifications not described in this guide, SAP will not provide support for the modified content.

The middleware content described in this guide is meant for use in SAP Cloud Integration. You are not allowed to deploy it in an on-premise SAP Process Orchestration system. For more information, see SAP Note 2428801 .

14 PUBLIC


System Preparation for Employee Time Data Replication

https://help.sap.com/viewer/b14dd15ca58f43e0856184a740a4b212

https://help.sap.com/viewer/368c481cd6954bdfa5d0435479fd4eaf/Cloud/en-US

http://help.sap.com/disclaimer?site=https://launchpad.support.sap.com/#/notes/2428801

3. Do you meet the minimum setup for SAP ERP HCM systems?

Table 4: Required Software Component Versions and Support Packages

Component... Required Software Component Version

SAP NetWeaver SAP_BASIS with one of the following versions:

○ 700 with SP27 or a higher SP○ 701 with SP12 or a higher SP○ 702 with SP08 or a higher SP○ 710 with SP15 or a higher SP○ 711 with SP10 or a higher SP○ 730 with SP03 or a higher SP

Replicating Employee Time Data from Employee Central to SAP ERP HCM Using SAP Cloud Integration as the MiddlewareSystem Preparation for Employee Time Data Replication PUBLIC 15


SAP ERP HCM The following software component versions are required in your system:○ SAP_APPL

SAP_APPL 600 SP15 or a higher version/SP

○ SAP_HRThe required minimum is one of the following versions:○ SAP_HR 600 SP59

○ SAP_HR 604 SP25

○ SAP_HR 608 (initial delivery version, no SP required)

The minimum version ensures that the integration works, but you most probably need to implement additional SAP Notes. Which SAP Notes are required depends on the exact SP level available in your system.To prevent additional effort caused by investigating the required SAP Notes and by implementing them, we recommend that you use at least one of the following versions:○ SAP_HR 600 SPC7 (127)

○ SAP_HR 604 SP93

○ SAP_HR 608 SP21

○ EA-HRThe required minimum is one of the following versions:○ EA-HR 600 SP59

○ EA-HR 602 SP38

○ EA-HR 603 SP33

○ EA-HR 604 SP25

○ EA-HR 605 SP02

○ EA-HR 606 (initial delivery version, no SP required)



The minimum version ensures that the integration works, but you most probably need to implement additional SAP Notes. Which SAP Notes are required depends on the exact SP level available in your system.

16 PUBLIC




To prevent additional effort caused by investigating the required SAP Notes and by implementing them, we recommend that you use at least one of the following versions:○ EA-HR 603 SPA1

○ EA-HR 604 SP93

○ EA-HR 605 SP64

○ EA-HR 606 SP49

○ EA-HR 607 SP38

○ EA-HR 608 SP21

Integration add-on for SAP ERP HCM and SAP SuccessFactors Employee Central

PA_SE_IN 100 SP33

For more information, refer to SFSF EC INTEGRATION 1210 in the SAP Software Center. You can access the Software Center from SAP ONE Support Launchpad by choosing Software Downloads.

CautionThe PA_SE_IN software component can be installed in Unicode systems only. Non-Unicode systems are not supported.

The Unicode conversion was already announced in the year 2006. The support of non-Unicode systems ends soon. The SFSF EC INTEGRATION 1210 add-on, which comprises the PA_SE_IN software component, has been developed and tested in a Unicode environment. It's not planned to offer it for non-Unicode systems. This means that Unicode is a prerequisite if you want to run the integrations provided by this add-on. For more information, refer to:

○ SAP Note 838402 (Problems within non-Unicode systems and landscape) and the customer letter attached to this SAP Note

○ SAP Note 1322715 (Unicode FAQs)○ SAP Knowledge Base Article (KBA) 2033243 (End of non-Unicode Support: Release Details)

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 in the SAP ONE Support Launchpad at https://launchpad.support.sap.com/ . Check the LOD-EC-INT-TIM application area for SAP Notes that are relevant for employee time data replication from Employee Central to SAP ERP HCM.


http://help.sap.com/disclaimer?site=https%3A%2F%2Flaunchpad.support.sap.com%2F%23%2Fsoftwarecenter%2Ftemplate%2Fproducts%2F%2520_APP%3D00200682500000001943%26_EVENT%3DDISPHIER%26HEADER%3DY%26FUNCTIONBAR%3DN%26EVENT%3DTREE%26NE%3DNAVIGATE%26ENR%3D67837800100900007903%26V%3DINST%26TA%3DACTUAL%26PAGE%3DSEARCH%2FSFSF%2520EC%2520INTEGRATION%25201210

http://help.sap.com/disclaimer?site=https%3A%2F%2Flaunchpad.support.sap.com%2F




http://help.sap.com/disclaimer?site=https%3A%2F%2Flaunchpad.support.sap.com%2F

Install SAP Notes that aren’t contained in the minimum version of the PA_SE_INPA_SE_IN 100 software component mentioned above:

Table 5: Required SAP Notes

SAP Note Number TitleIssue Corrected by the SAP Note

Correction Will Be Contained in Support Package

1043195 Configuration of Web service runtime

You don't know how to set up the technical configura-tion of the Web service runtime environment in your SAP ERP HCM system and how to check it.

none

2581802 [MX] Maternity Leave absences not working in HR Renewal and Employee Central Payroll

Implement this note (or install the corresponding support package) to enable replication of the Days Already Cumulated For Same Sickness field for linked sickness absences for Mexico from Employee Central Time Off. The field is mapped to the Days Credited for Continued Pay field of the Absences (2001) infotype in SAP ERP HCM.

.

Software component version SAP_HRCMX 600: support package F6

Software component version SAP_HRCMX 604: support package C2

Software component version SAP_HRCMX 608: support package 50

3.2 How to Keep Your Systems in Sync

Why we recommend installing the latest support package of the integration add-on in your on-premise SAP ERP HCM system.

The main use case of the SFSF EC INTEGRATION 1210 add-on, which comprises the PA_SE_IN 100 software component version, is to synchronize data between the cloud solution SAP SuccessFactors Employee Central and an on-premise SAP ERP HCM system.

Cloud solutions are regularly upgraded by SAP. Upgrades of on-premise systems are customer-managed.

New features in Employee Central often require enhancements of the PA_SE_IN software component. New integration features are also made available in the latest version of the PA_SE_IN software component only. You can use these new features only if your on-premise system is up to date. Furthermore, the data synchronization between Employee Central and the SAP ERP HCM system can only run smoothly if regular upgrades are performed on both sides. Therefore, the on-premise add-on must also be upgraded regularly.

Ideally, you install the latest support package of the add-on together with each new Employee Central release.

18 PUBLIC





If this isn’t possible due to upgrade restrictions concerning your on-premise system, we recommend installing the latest support package of the add-on at least once a year. Only then we can ensure that the integration runs smoothly.

3.3 Permissions for Employee Time Data Replication

Set up the permissions needed by API users and administrators in Employee Central, as well as permissions for technical users in the SAP ERP HCM system.

Permissions Required for API Access [page 19]Data replication between SAP SuccessFactors Employee Central and the SAP ERP HCM system requires administrator and user permissions for SAP SuccessFactors APIs.

Permissions Required to Access the Data Replication Objects [page 20]Replication of employee time data from SAP SuccessFactors Employee Central requires the permissions to access the Data Replication Configuration object and the Data Replication Proxy object in Employee Central.

Granting SAP ERP HCM Permissions for Employee Time Data Replication [page 21]To ensure that the middleware can successfully communicate with SAP ERP HCM, create a technical user in the SAP ERP HCM system and then set up permissions for this user.

3.3.1 Permissions Required for API Access

Data replication between SAP SuccessFactors Employee Central and the SAP ERP HCM system requires administrator and user permissions for SAP SuccessFactors APIs.

The permissions listed here grant users and administrators access to the SAP SuccessFactors OData API and SFAPI. SFAPI access includes access to CompoundEmployee API.

For more information about role-based permissions – what they are, how they work, how you set them up – refer to Implementing Role-Based Permissions in the SAP Help Portal.

Table 6: Permissions Required for API Access

Who's This Permission For? Permission Location Permission Name

User General User Permissions SFAPI User Login

Administrator Employee Central API Employee Central Foundation SOAP API


https://help.sap.com/viewer/cdd844b5f0744d238284e937deb73f39


Administrator Employee Central API Employee Central HRIS SOAP API or Employee Central Compound Employee API (restricted access)

NoteEither grant the Employee Central HRIS SOAP API permission, to give the administrator unrestricted access to the CompoundEmployee API. Or grant the Employee Central Compound Employee API (restricted access) permission, to restrict the access to the data of specific employees. Don't select both permissions for the same permission role. For more information, see Granting Permissions for Full Access to the CompoundEmployee API and Granting Permissions for Restricted Access to the CompoundEmployee API in the Employee Central Compound Employee API guide.

Administrator Employee Central API Employee Central Foundation OData API (read-only)

Administrator Employee Central API Employee Central HRIS OData API (read-only)

Administrator Employee Central API Employee Central Foundation OData API (editable)

Administrator Employee Central API Employee Central HRIS OData API (editable)

3.3.2 Permissions Required to Access the Data Replication Objects

Replication of employee time data from SAP SuccessFactors Employee Central requires the permissions to access the Data Replication Configuration object and the Data Replication Proxy object in Employee Central.

For more information about role-based permissions – what they are, how they work, how you set them up – refer to Implementing Role-Based Permissions in the SAP Help Portal.

Table 7: Permissions Required to Access the Data Replication Objects


User Payroll Integration Permission View, Edit, and Import/Export for Data Replication Configuration

20 PUBLIC



https://help.sap.com/viewer/5bb9a5b997a843c88e769a105e4af4d4/latest/en-US/bc3eb7d3fca64b4a8d6f56c66183d8ef.html



https://help.sap.com/viewer/5bb9a5b997a843c88e769a105e4af4d4/latest/en-US/d82ea6082db64daa94b8010e70699d5e.html



https://help.sap.com/viewer/cdd844b5f0744d238284e937deb73f39


User Payroll Integration Permission View, Edit, and Import/Export for Data Replication Proxy

3.3.3 Granting SAP ERP HCM Permissions for Employee Time Data Replication

To ensure that the middleware can successfully communicate with SAP ERP HCM, create a technical user in the SAP ERP HCM system and then set up permissions for this user.

Context

For employee time data replication from Employee Central, you need to set up a user of type B (System User) in SAP ERP HCM, with specific authorizations and restrictions. For your convenience, we have created a template role you can copy and assign to this user: SAP_HR_TIM_EC_REPL. We strongly recommend that you create the user with this template role.

For more information about technical users and roles, see Creating System Users and Role Administration Functions in the SAP NetWeaver documentation. Find the documentation for your SAP NetWeaver release in SAP Help Portal, at https://help.sap.com/viewer/p/SAP_NETWEAVER.

Procedure

1. Create the user.a. Go to the User Maintenance (SU01) transaction in your SAP ERP HCM system.b. Create a user of type B.c. Mark the user as a customer user by assigning it to the user group CUSTOMER.

If you don’t assign the user to the CUSTOMER group, it will be deleted automatically by the system.2. Set up permissions for the user.

a. Go to the Role Maintenance (PFCG) transaction in your SAP ERP HCM system.b. Copy the SAP_HR_TIM_EC_REPL role.

NoteYou must copy this role from client 000 into your Customizing client.

c. Set up permissions for the copied role to suit your specific requirements.

For example, if users should be allowed to use the clean-up tool in SAP ERP HCM to repair data inconsistencies, they require these permissions:

○ Authorization to run transaction ECTIM_CLEANUP_DB


https://help.sap.com/viewer/129f228c6c5310149e9aa0aaff94173a/latest/en-US/4b04a2c01fa00a95e10000000a421937.html

https://help.sap.com/viewer/129affcf6c531014b28cae6d2a9cf86f/latest/en-US/4c93141f5c153c91e10000000a42189c.html

https://help.sap.com/viewer/129affcf6c531014b28cae6d2a9cf86f/latest/en-US/4c93141f5c153c91e10000000a42189c.html


○ Change authorization for the PAOCFEC_REFMAP tabled. Assign the copied role to the user you created.

Related Information

Deleting Inconsistent Employee Time Data in SAP ERP HCM [page 98]

3.4 Employee Central Preparation for Replication of Employee Time Data

How to configure Employee Central so that it can communicate time data to SAP ERP HCM.

Enabling the OData API Audit Log [page 23]Activate the OData API Audit Log for data compliance. Once it is on, all time data changes are recorded and you can see history.

External Codes Must Not Be Longer Than 32 Characters [page 23]Be careful when defining external codes in Employee Central for objects that are relevant for employee time data replication to SAP ERP HCM.

Creating Replication Target System [page 24]Define the target SAP ERP HCM system for replication of time off and time sheet data from Employee Central so that Employee Central and the middleware know which system to address.

Creating Data Replication Configuration Objects [page 24]Create configurations for replication of Time Off and Time Sheet data from Employee Central to your SAP ERP HCM system, to define what data is to be replicated to which target system.

Configuring Data Replication Configuration Object for Leave of Absence (LoA) Scenarios [page 27]Filter out absences entered in a Leave of Absence (LoA) scenario in time data replication if you use local versions that don't allow absences for inactive employees.

Creating a Value Help for Employee Class for Time Sheet Data Replication [page 28]Create an Employee Class value help in Employee Central, to prepare for Time Sheet data replication to SAP ERP HCM.

22 PUBLIC



3.4.1 Enabling the OData API Audit Log

Activate the OData API Audit Log for data compliance. Once it is on, all time data changes are recorded and you can see history.

Context

OData API is enabled by default, but the OData API Audit Log must be enabled in Provisioning.

RememberAs a customer, you don't have access to Provisioning. To complete tasks in Provisioning, contact your implementation partner or Account Executive. For any non-implementation tasks, contact Product Support.

Procedure

1. Go to API Settings & Tools OData API Audit Log Setting .2. Select the Enable checkbox for Enable/Disable OData API Audit Log.

3.4.2 External Codes Must Not Be Longer Than 32 Characters

Be careful when defining external codes in Employee Central for objects that are relevant for employee time data replication to SAP ERP HCM.

In Employee Central, the external code of Employee Time and Time Valuation objects can be up to 255 characters long. In SAP ERP HCM, however, the corresponding key can't have more than 32 characters. When defining Employee Time and Time Valuation objects in Employee Central, make sure that you enter an external code that isn't longer than 32 characters. Also ensure that external codes of Employee Time and Time Valuation objects aren't longer than 32 characters before you upload the objects to Employee Central by file import.

If an external code is longer than 32 characters, the replication fails and the middleware shows a corresponding error message.


3.4.3 Creating Replication Target System

Define the target SAP ERP HCM system for replication of time off and time sheet data from Employee Central so that Employee Central and the middleware know which system to address.

Procedure

1. In Admin Center, choose the Manage Data tool and create a new Replication Target System object.2. In the Replication Time Offset in Minutes field enter the amount of minutes you want the resend of data to

be delayed by when the payroll area is locked or in correction phase. If you leave this field empty, the default time until resend is 60 minutes.

3. Enter an externalCode and externalName for your object.

You'll need the externalCode when you set up the Data Replication Configuration objects in Employee Central and the integration flows in the middleware.

4. Set Relevant for Payroll Integration to Yes. Set the other Relevant for … parameters to No.

Related Information

Finding and Setting the Replication Target System [page 61]

3.4.4 Creating Data Replication Configuration Objects

Create configurations for replication of Time Off and Time Sheet data from Employee Central to your SAP ERP HCM system, to define what data is to be replicated to which target system.

Prerequisites

The Data Replication Configuration permission is required for this task.

Context

Create and configure Data Replication Configuration objects that use the Replication Target System object you created in a previous step. The replication process is triggered by an OData call from the middleware to the respective Data Replication Proxy object in Employee Central.

24 PUBLIC



Procedure

1. To set up replication of Time Off data, create a data replication configuration for absence data.a. In Admin Center, choose the Manage Data tool and create a Data Replication Configuration object.b. Enter an external code and a name for your object.c. Enter the external code of the Replication Target System object you created for data replication from

Employee Central.d. Select the Replication Content Type. For Time Off data, select Employee Absence Data.

As a result, Replication Scenario is shown with Absences only selected.e. Define the Earliest Selection Date.

Many integrations call this date the full transmission start date (FTSD). It means that only absences with an end date on or after the earliest selection date are considered for replication.

ExampleLet's say, an approved absence for an employee exists for December 27 – January 2. You specify the earliest selection date of January 1. Replication is performed in this case. However, if the earliest selection date was on January 3, the absence wouldn’t be replicated, because the end date of the absence is before the earliest selection date.

TipNote that the format of the date depends on your logon language. Let's take the date from our example, January 3, 2018, to illustrate it:○ English UK: 03/01/2018○ English US: 01/03/2018

f. Choose either Yes or No for Always Allow Replication In Payroll Correction Phase. The payroll cycle foresees a correction phase where a limited number of changes are performed before the actual payroll run is executed. If you set Always Allow Replication In Payroll Correction Phase to Yes, your entire absences are replicated and saved in the SAP ERP HCM system, including those entries generated in any correction phase.

g. If there are absences that don't have proxies yet, for example because the absences were created before the Data Replication Configuration object was set up, choose Yes for Execute Proxy Creation Job. A job is started that creates proxies for the current configuration settings. This also creates proxies for time objects that have already been replicated, as of Earliest Selection Date.

NoteAfter saving, this setting switches automatically back to No because the job is triggered directly during the save.

This feature is only available when changing the Data Replication Configuration object using Manage Data, but not when using Import Data.

h. If you don't want to replicate data assigned to contingent workers, set the Exclude Contingent Workers field to Yes. Note that this setting overrules other filter criteria of this configuration object.


ExampleIf you want to replicate employees assigned to country/region Mexico and the Exclude Contingent Workers field is set to Yes, contingent workers from Mexico aren’t included in the time replication process.

i. Make the relevant assignments:○ Country/Region Assignment

Enter the Employee Central country/region code, and only data from employees employed in the specified country/region are replicated. It’s possible to enter multiple countries/regions. Separate them with commas.

○ Pay Group AssignmentEnter the Employee Central pay group code to only replicate data of employees of that specific pay group. You can enter multiple pay groups. Separate them with commas.

○ Time Type AssignmentEnter the Employee Central time type code to only replicate absences of that specific time type. You can enter multiple time types. Separate them with commas.

○ Company AssignmentEnter the Employee Central company code to only replicate the data of employees of a specific company/legal entity. You can enter multiple company codes. Separate them with commas.

○ Employee Class AssignmentEnter the Employee Central employee class to only replicate data of employees of a specific employee class are replicated. It’s possible to enter multiple employee classes. Separate them with commas.

NoteChanging these settings doesn't affect data from the past.

2. To set up replication of Time Sheet data, create a data replication configuration for time sheet data and make the same settings, apart from:○ Replication Content Type

Is Time Pay Components in this case. When you select Time Pay Components, Use Cost Center External Object Id is shown with No selected. Replication Scenario isn't relevant and therefore not shown for Time Sheet.

○ Time Type AssignmentThis setting isn't relevant for Time Sheet either.

Next Steps

A single absence or time pay component can only be replicated to one target system. If you have set up more than one data replication configuration involving more than one replication target system, ensure that your filter criteria are replication-specific.

26 PUBLIC



Related Information

Finding and Setting the Replication Target System [page 61]Permissions Required to Access the Data Replication Objects [page 20]

3.4.5 Configuring Data Replication Configuration Object for Leave of Absence (LoA) Scenarios

Filter out absences entered in a Leave of Absence (LoA) scenario in time data replication if you use local versions that don't allow absences for inactive employees.

Prerequisites

The Data Replication Configuration permission is required for this task.

Context

In a Leave of Absence (LoA) scenario, the employee in question might be inactive in Employee Central. But when absences entered in an LoA scenario are replicated to the SAP ERP HCM system, the fact that an employee is inactive or active isn’t considered when creating the Absences (2001) infotype.

In SAP ERP HCM, absences for periods when the status of an employee is set to Inactive in the Actions (0000) infotype aren’t allowed for most countries/regions. For most countries/regions, the ACTIV parameter of the Read absences (RAB) payroll function doesn’t allow absences when the status of an employee is Inactive.

This means that the payroll run fails for the corresponding employee each time a leave of absence is replicated to SAP ERP HCM. That's why you might want to prevent leaves of absence from being replicated for the countries/regions that don't allow absences when the status of an employee is Inactive.

NoteWe strongly recommend that you check your Data Replication Configuration object before migrating legacy LoA to Time Off LoA in order to upgrade to the new Fiori user experience for Time Off. For more information, see Migrating from Legacy LoA to Time Off LoA in Implementing Employee Central Time Off.

Procedure

1. In Admin Center, choose the Manage Data tool and search for the Data Replication Configuration object you've created for replication of Time Off data.


https://help.sap.com/viewer/8b4f98853bb44ed8a7ba1fdb0cc0ddeb/latest/en-US/f85090b51e234740bb22a65d959b8fdb.html

https://help.sap.com/viewer/8b4f98853bb44ed8a7ba1fdb0cc0ddeb

2. Configure the object in a way that makes sure that you don't include any Leave of Absence time type in the Time Type Filter.

Be aware that you maintain all other absences that need to be replicated as usual by including them in the Time Type Filter.

Related Information

Creating Replication Target System [page 24]Permissions Required to Access the Data Replication Objects [page 20]

3.4.6 Creating a Value Help for Employee Class for Time Sheet Data Replication

Create an Employee Class value help in Employee Central, to prepare for Time Sheet data replication to SAP ERP HCM.

Context

To create a value help for Employee Class, you first download the HRIS picklist for Employee Class. Then you create a new MDF Employee Class picklist using the HRIS picklist you downloaded.

NoteEmployee Class must also be maintained at the employee level for master data replication. Therefore, you must ensure it is maintained within the Job Information of employees, enabling proxy creation and subsequent replication.

Procedure

1. In Admin Center, choose the Picklists Management tool.2. Export a CSV file to download the existing HRIS picklist.

a. Select Export all picklist(s) and deselect Include System Generated Job Codes.b. Choose Submit.c. When the request has completed, choose Download export.

3. Go back to Admin Center and choose the Configure Object Definitions tool.a. Create a new Employee Class MDF picklist.b. Add the picklist values using the HRIS picklist you downloaded in the previous step.

28 PUBLIC



NoteYou must ensure that the external code of each element of the new MDF picklist is equal to the corresponding external code in the original HRIS picklist.


4 Concepts of Employee Time Data Replication

Look at some concepts used in employee time data replication from Employee Central.

Why Replicate Employee Time Data from Employee Central? [page 30]Get an overview about why you would replicate employee time data from Employee Central to your SAP ERP HCM system.

APIs and Web Services Used for Time Data Replication [page 31]What Application Service Interface (API) and web service does employee time data replication from Employee Central use?

Terminology [page 32]Find out where Time Management terminology used in Employee Central differs from what SAP ERP HCM uses.

4.1 Why Replicate Employee Time Data from Employee Central?

Get an overview about why you would replicate employee time data from Employee Central to your SAP ERP HCM system.

Time Off Data

Typically employees enter their absences into Employee Central. SAP ERP HCM processes this information in the payroll run, and the employees see the results in their pay statements.

To make this possible, you replicate absence data entered by employees in Employee Central Time Off to SAP ERP HCM, so that absences such as vacation or sickness are reflected on the pay statement. You achieve this by building an integration that replicates absence data from Employee Centrale Time Off to the Absences (2001) infotype in SAP ERP HCM.

Time Sheet Data

Typically employees enter their attendance times or overtime in their time sheet in Employee Central. Integrating the Employee Central Time Sheet with SAP ERP HCM allows the replication of all payroll-relevant time data to the payroll you run in your SAP ERP HCM system. SAP ERP HCM processes this information in the payroll run, and the employees see the results in their pay statements.

30 PUBLIC


Concepts of Employee Time Data Replication

To make this possible, you replicate payroll-relevant time data entered by employees in their time sheet to SAP ERP HCM, so that employees can be paid on the basis of this recorded time, along with other payroll-relevant data. You achieve this by building an integration that replicates individual employee time valuation results from the Employee Central Time Sheet to the Employee Remuneration Info (2010) infotype in SAP ERP HCM.

4.2 APIs and Web Services Used for Time Data Replication

What Application Service Interface (API) and web service does employee time data replication from Employee Central use?

APIs

Both, replication of Time Off and of Time Sheet data from Employee Central to SAP ERP HCM, use the SAP SuccessFactors OData API.

Web Services

Both, replication of Time Off and of Time Sheet data, use the same SAP ERP HCM inbound service interface: EmployeeTimeECToERPRequest_In.

Related Information

Enabling the OData API Audit Log [page 23]Permissions Required for API Access [page 19]Enabling the SAP ERP HCM Inbound Web Service to Set Up the Connection from the Middleware to SAP ERP HCM [page 33]

Replicating Employee Time Data from Employee Central to SAP ERP HCM Using SAP Cloud Integration as the MiddlewareConcepts of Employee Time Data Replication PUBLIC 31

4.3 Terminology

Find out where Time Management terminology used in Employee Central differs from what SAP ERP HCM uses.

For some concepts related to employee time data, Employee Central uses different terms than SAP ERP HCM:

Table 8: Different Terminology Used in Employee Central and SAP ERP HCM

Term in Employee Central Term in SAP ERP HCM

time off absence

time type absence type

time pay type time wage type

work schedule work schedule rule

identical sickness subsequent illness

overlapping sickness repeated illness

32 PUBLIC


Concepts of Employee Time Data Replication

5 SAP ERP HCM System Configuration for Replication of Employee Time Data

Learn more about how to configure SAP ERP HCM so that time data can be communicated from Employee Central.

Enabling the SAP ERP HCM Inbound Web Service to Set Up the Connection from the Middleware to SAP ERP HCM [page 33]

Activate the SAP ERP HCM inbound web service used by employee time data replication to set up the connection for communication from the middleware to SAP ERP HCM.

Enabling Creation of the Confirmation Message [page 34]Enable creation of confirmations for data replication from Employee Central to SAP ERP HCM to ensure that the Employee Central Data Replication Monitor is updated the current replication status.

Configuration of Time Off Data Replication in the SAP ERP HCM System [page 35]Make settings in SAP ERP HCM Customizing to enable replication of time off data from Employee Central.

Configuration of Time Sheet Data Replication in the SAP ERP HCM System [page 44]Make settings in SAP ERP HCM Customizing to enable replication of time sheet data from Employee Central.

5.1 Enabling the SAP ERP HCM Inbound Web Service to Set Up the Connection from the Middleware to SAP ERP HCM

Activate the SAP ERP HCM inbound web service used by employee time data replication to set up the connection for communication from the middleware to SAP ERP HCM.

Context

The inbound web service for employee time data replication is: EmployeeTimeECToERPRequest_In. This web service is used for the integration of both, Employee Central Time Off and Employee Central Time Sheet with SAP ERP HCM. Activate this web service by enabling the service definition in your SAP ERP HCM system.

NoteThe Simplified Web Service Configuration tool described here is available from SAP NetWeaver 7.0 enhancement package 2 (SAP_BASIS 702). If you’re using a lower SAP NetWeaver release, you must use the Web Service Configuration tool instead. For more information, refer to Configuring a Service Provider in the SAP NetWeaver documentation for release 7.0. For a detailed how-to description of Web Service

Replicating Employee Time Data from Employee Central to SAP ERP HCM Using SAP Cloud Integration as the MiddlewareSAP ERP HCM System Configuration for Replication of Employee Time Data PUBLIC 33

https://help.sap.com/viewer/12aa7f056c531014aa5bca7aee037e55/7.0.33/en-US/3306820d9d174c2884576bd78ac5629d.html

Configuration and Simplified Web Service Configuration refer to the SAP Community Network, at ABAP Connectivity - Web Services ABAP > How to configure a Service Provider and How to configure a Service Provider (Simplified). To find the SOA Manager documentation for your SAP NetWeaver release, go to http://help.sap.com and search for working with soamanager. Then filter the search result for your SAP NetWeaver release and support package.

Procedure

1. In the SOA Management (SOAMANAGER) transaction, choose Simplified Web Service Configuration.

2. Enter the web service definition name, EmployeeTimeECToERPRequest_In, and choose Go.

3. Select the User Name / Password (Basic) checkbox and choose Save.

5.2 Enabling Creation of the Confirmation Message

Enable creation of confirmations for data replication from Employee Central to SAP ERP HCM to ensure that the Employee Central Data Replication Monitor is updated the current replication status.

Prerequisites

For employee time data replication, this setting is only required if you haven’t enabled the Business Integration Builder (BIB) mode in your SAP ERP HCM system for employee master data, employee organizational assignment, or organizational object replication.

To check whether the BIB mode is enabled, go to Customizing for Personnel Management in your SAP ERP HCM system and choose Integration with SuccessFactors Employee Central Business Integration BuilderBasic Settings Maintain the Constant Values . If the constant Activate BIB for EC to ERP Employee Replication is entered here and the constant value is X, the BIB mode is enabled.

If you’ve enabled the BIB mode, the confirmation message is turned on by default for employee time data replication. You can't turn it off in this case. That is, the setting described here isn’t relevant.

For more information about BIB-based data replication from Employee Central, see the following integration guides:

● Replicating Employee Master Data and Organizational Assignments from Employee Central to SAP ERP HCM

● Replicating Organizational Objects from Employee Central to SAP ERP HCM

Find the most current version of these guides in SAP Help Portal at http://help.sap.com/hr_ecintegration.

34 PUBLIC


SAP ERP HCM System Configuration for Replication of Employee Time Data

http://help.sap.com/disclaimer?site=https%3A%2F%2Fwiki.scn.sap.com%2Fwiki%2Fx%2FmoWvC


http://help.sap.com



https://help.sap.com/viewer/45372a91942140518d37370208c8525d

http://help.sap.com/hr_ecintegration

Context

Confirmations are being sent by the SAP ERP HCM system to Employee Central for employee master data, employee organizational assignment, and employee time data replication, to update the Data Replication Monitor with the replication status. You need to enable them in your SAP ERP HCM system.

Procedure

1. Go to the Maintain Table Views (SM30) transaction in your SAP ERP HCM system.2. Enter V_T77S0 in the Table/View field and choose Maintain (or Edit).

3. Choose New Entries and enter the following data:○ Group: YSFEC○ Sem.abbr (Semantical Abbreviation): YRESP○ Value abbr (Value Abbreviation): X

4. Save your entries.

5.3 Configuration of Time Off Data Replication in the SAP ERP HCM System

Make settings in SAP ERP HCM Customizing to enable replication of time off data from Employee Central.

Use the Customizing activities in the integration add-on for SAP ERP HCM and SAP SuccessFactors Employee Central (PA_SE_IN). In your SAP ERP HCM system, go to the Customizing: Execute Project (SPRO) transaction and choose SAP Reference IMG. Two main sections here are relevant for replication of time off data:

● Time Management Time Data Recording and Administration for general Time Management settings

● Personnel Management Integration with SuccessFactors Employee Central Other Integration SettingsReplicating Data from Employee Central to SAP ERP for replication-specific settings

Go through the following steps to set up time off integration in SAP ERP HCM.

1. Disabling Collision Checks for Overlapping Time Infotype Records [page 36]Disable collision checks in the SAP ERP HCM system to ensure that new time infotype records replicated from Employee Central can be created even if they overlap with existing time infotype records.

2. Disabling Quota Deduction [page 37]Disable quota deduction in the SAP ERP HCM system if you replicate employee time date from Employee Central, because deductions and related calculations are done in Employee Central.

3. Configuring Absence Input Checks [page 38]If you replicate employee time data from Employee Central, define what checks the SAP ERP HCM system performs when you enter an absence.


4. Configuring Attendances and Absences to Be Recorded Without Clock Times [page 39]Define that only durations are stored for time data in the SAP ERP HCM, to prevent the system from generating clock times.

5. Mapping Time Types with Absence Types and Work Schedules with Work Schedule Rules [page 40]Define customer-specific code values to map Employee Central time types to SAP ERP HCM absence types and Employee Central work schedules to work schedule rules from SAP ERP HCM.

6. Configuring Time Evaluation Schema for Payroll Processing [page 42]Define that SAP ERP HCM is to do time evaluation for payroll processing based on duration, not on clock times.

7. Disabling the Default Work Schedule Logic [page 43]Turn off the default logic used to determine work schedules in the SAP ERP HCM system because the work schedule logic from Employee Central is used if you replicate time off data.

5.3.1 Disabling Collision Checks for Overlapping Time Infotype Records

Disable collision checks in the SAP ERP HCM system to ensure that new time infotype records replicated from Employee Central can be created even if they overlap with existing time infotype records.

Context

Disable collision checks for overlapping time infotypes in SAP ERP HCM to prevent errors such as a new infotype record can't be replicated because it overlaps with an existing record.


Procedure

1. In SAP ERP HCM Customizing, go to Time Management Time Data Recording and AdministrationSpecify System Reaction to Overlapping Time Infotypes .

2. Double-click the time constraint class and set the Reaction Indicator to N for all subtypes. N means: You can create the new record, but the old record remains unchanged. Collisions are not displayed.

NoteChange settings for each time constraint class and not for each subtype within an infotype.

36 PUBLIC



Task overview: Configuration of Time Off Data Replication in the SAP ERP HCM System [page 35]

Next task: Disabling Quota Deduction [page 37]

5.3.2 Disabling Quota Deduction

Disable quota deduction in the SAP ERP HCM system if you replicate employee time date from Employee Central, because deductions and related calculations are done in Employee Central.

Context

Absence quotas are not replicated into the SAP ERP HCM system. Quota deduction and related calculations are done in Employee Central. That's why you need to disable quota deduction in SAP ERP HCM for absence types you use in time data replication from Employee Central.


Procedure

1. In SAP ERP HCM Customizing, go to Time Management Time Data Recording and AdministrationAbsences Absence Catalog Absence Counting Assign Counting Rules to Absence Types .

2. Choose an absence type you would like to use for the integration between Employee Central and SAP ERP HCM, such as Leave.

3. Assign a counting rule, such as 010 (Leave), leaving the Quota Deduction checkbox empty.4. Do the same for all other absence types you would like to use for the integration.


Previous task: Disabling Collision Checks for Overlapping Time Infotype Records [page 36]

Next task: Configuring Absence Input Checks [page 38]


5.3.3 Configuring Absence Input Checks

If you replicate employee time data from Employee Central, define what checks the SAP ERP HCM system performs when you enter an absence.

Context

We recommend disabling absence input checks to prevent error messages from being sent when first day and/or last day of the absence are non-working days. However, if all absence days are non-working days, it does make sense to send an error, in this case set E for Error Message. The idea behind this is that these kinds of error messages are already sent to the user in Employee Central. As long as the Employee Central and SAP ERP HCM calendars and the work schedules are in sync, no errors are sent anyway.

Procedure

1. In SAP ERP HCM Customizing, go to Time Management Time Data Recording and AdministrationAbsences Absence Catalog Define Absence Types .

2. Choose an absence type you would like to use for the integration between Employee Central and SAP ERP HCM, such as Leave.

3. Make sure that the fields for First day is day off and Last day is day off are empty.4. Do the same for all other absence type you would like to use in the integration.


Previous task: Disabling Quota Deduction [page 37]

Next task: Configuring Attendances and Absences to Be Recorded Without Clock Times [page 39]

38 PUBLIC



5.3.4 Configuring Attendances and Absences to Be Recorded Without Clock Times

Define that only durations are stored for time data in the SAP ERP HCM, to prevent the system from generating clock times.

Context

Use feature HRSIF to specify that time data is to be recorded without clock times. Recording without clock times means that only durations and not times are stored in the Absences (2001) infotype.


Procedure

1. In SAP ERP HCM Customizing, go to Time Management Time Data Recording and AdministrationPermit Attendances/Absences to be Recorded Without Clock Times .

2. Enter 1 as the return code of the HRSIF feature to record time data without clock times

Figure 1: Feature HRSIF

Don't set a different return code for this feature. Or else SAP ERP HCM will try to generate clock times because they aren't replicated from Employee Central.


Previous task: Configuring Absence Input Checks [page 38]

Next task: Mapping Time Types with Absence Types and Work Schedules with Work Schedule Rules [page 40]


5.3.5 Mapping Time Types with Absence Types and Work Schedules with Work Schedule Rules

Define customer-specific code values to map Employee Central time types to SAP ERP HCM absence types and Employee Central work schedules to work schedule rules from SAP ERP HCM.

Procedure

1. Go to Customizing for Personnel Management and choose Integration with SuccessFactors Employee Central Other Integration Settings Replicating Data from SuccessFactors to SAP ERP Assignment of Code Values .

2. Go to the Define Standard Code Value Lists step and define standard code value lists to be used in the activities described in the next steps.

3. Go to the Define Country Dependency of Code Value Lists step and assign the code value lists so they’re country/region-dependent.

4. Go to the Define Mapping Code Value Lists step and map all relevant external code values (meaning the code values from Employee Central) to the code value lists of the SAP ERP HCM system.a. Map all relevant time type codes (TIME_TYPE_CODE) of Employee Central to the corresponding

absence types (GDT Code) in your SAP ERP HCM system. Time type is included in the replication of time off data to the Absences (2001) infotype in the SAP ERP HCM system.

If the Employee Central and SAP ERP HCM codes for time type are the same, no further mapping is needed. If they aren’t, you need to map time type values.

The SAP ERP HCM GDT code is limited to 10 characters. In Employee Central, the time type codes can be longer. If any time pay type codes replicated from Employee Central Time Off are longer, any characters beyond the 10th character are cut off by the middleware during replication.

ExampleHere's an example of time type codes mapped to absence type GDT codes:

Table 9: Sample Mapping of Time Type Codes to Absence Types

GDT Name Code List ID List Version ID List Agency ID GDT Code ERP Key

TIME_TYPE_CODE

91201 310 VACATION 0100

TIME_TYPE_CODE

92001 310 SICK LEAVE 0200

TIME_TYPE_CODE

92010 310 FULL HOUR 0100

40 PUBLIC




TIME_TYPE_CODE

92010 310 HALF DAY 0100

TIME_TYPE_CODE

92010 310 SICK LEAVE 0200

TIME_TYPE_CODE

92010 310 PTO 0140

b. Map all relevant work schedules (WORK_SCHEDULE_RULE) of Employee Central to the corresponding work schedule rules (GDT Code) in your SAP ERP HCM system. The time off work schedule is located in the Job Information block in Employee Central and is included in the replication of time off data to the Planned Working Time (0007) infotype in the SAP ERP HCM system.

If the Employee Central and SAP ERP HCM codes for work schedules and work schedule rules are the same, no further mapping is needed. If they aren’t, you need to map them.

The SAP ERP HCM GDT code is limited to 10 characters. In Employee Central, the work schedule codes can be longer. If any work schedule codes replicated from Employee Central Time Off are longer, any characters beyond the 10th character are cut off by the middleware during replication.

ExampleHere's an example of mapped work schedule rules:

Table 10: Sample Mapping of Work Schedule Rules


WORK_SCHEDULE_RULE

91801 310 NORM

WORK_SCHEDULE_RULE

91801 310 8H5D GLZ

WORK_SCHEDULE_RULE

91801 310 NORM 1970 NORM

WORK_SCHEDULE_RULE

91804 310 NORM

WORK_SCHEDULE_RULE

91804 310 NO NO

WORK_SCHEDULE_RULE

91804 310 NORM NORM



Previous task: Configuring Attendances and Absences to Be Recorded Without Clock Times [page 39]

Next task: Configuring Time Evaluation Schema for Payroll Processing [page 42]

5.3.6 Configuring Time Evaluation Schema for Payroll Processing

Define that SAP ERP HCM is to do time evaluation for payroll processing based on duration, not on clock times.

Context

SAP ERP HCM uses a so called Personnel Calculation Schema to evaluate time information for processing in payroll. Make sure that your Personnel Calculation Schema doesn't require clock times.


Procedure

1. Go to the Personnel Calculation Schemas (PE01) transaction in your SAP ERP HCM system and check the calculation schema that is used in payroll processing.

The schema includes several sub schemas. For the evaluation of time information you should use the INTERNATIONAL WT Generation for Time Evaluation w/o Clock Times (TC04) sub schema instead of Wage Type Generation INTERNATIONAL (TC00) because TC04 doesn't require clock times.

2. Turn off function KNTAG in the TC04 sub schema or don't use time evaluation schemas at all.


Previous task: Mapping Time Types with Absence Types and Work Schedules with Work Schedule Rules [page 40]

Next task: Disabling the Default Work Schedule Logic [page 43]

42 PUBLIC



5.3.7 Disabling the Default Work Schedule Logic

Turn off the default logic used to determine work schedules in the SAP ERP HCM system because the work schedule logic from Employee Central is used if you replicate time off data.

Prerequisites

● Make sure that the Input control for working hour fields/weekly workdays (WRKHR) feature has been maintained correctly. Go to the Features (PE03) transaction in your SAP ERP HCM system and make sure that its return value is set to D/X.If WRKHR isn’t maintained in this way, employment percentage is set to 0.

● If the Employee Central and SAP ERP HCM codes for work schedule are the same, no further mapping is needed. If not, map the work schedule values manually in the Define Mapping of External Code Value Lists to Internal Code Value Lists Customizing activity. Use the following example as an aid:

GDT Name Code List ID List Agency ID GDT Code Value ERP Key

WORK_SCHEDULE_RULE

920XX (XX = country/region grouping)

310 <Employee Central Value>

<ERP Value>

Context

The time off work schedule is located in the Job Information block in Employee Central and is replicated to the Planned Working Time (0007) infotype in the SAP ERP HCM system.

Procedure

1. Go to the Edit Table Views (SM30) transaction in your SAP ERP HCM system.

2. Enter view V_T77S0.3. Choose Maintain.4. Choose New entries.5. Enter the following data:

○ Group: YSFEC○ Semantical abbreviation (sem.abbr): YSCHK○ Value abbreviation (value abbr.): X○ Description: Disable default logic to determine work schedule

6. Choose Save.


Next Steps

Remember that as soon as you implement custom fields, these fields overwrite the default work schedule determination and any manual mapping you've made.


Previous task: Configuring Time Evaluation Schema for Payroll Processing [page 42]

5.4 Configuration of Time Sheet Data Replication in the SAP ERP HCM System

Make settings in SAP ERP HCM Customizing to enable replication of time sheet data from Employee Central.

Use the Customizing activities in the integration add-on for SAP ERP HCM and SAP SuccessFactors Employee Central (PA_SE_IN). In your SAP ERP HCM system, go to the Customizing: Execute Project (SPRO) transaction and choose SAP Reference IMG. In the SAP Customizing Implementation Guide structure, open Personnel Management . Two main sections here are relevant for replication of time sheet data:

● Personnel Management Personnel Administration Payroll Data Employee Remuneration Information Wage Types for general time wage type settings

● Personnel Management Integration with SuccessFactors Employee Central Other Integration SettingsReplicating Data from Employee Central to SAP ERP for replication-specific settings

Go through the following steps to set up time sheet integration in SAP ERP HCM.

1. Mapping Time Pay Types with Time Wage Types [page 45]Define customer-specific code values to map Employee Central time pay types to SAP ERP HCM time wage types.

2. Enabling Time Wage Types for Multiple Entries Per Day [page 46]Define that all SAP ERP HCM time wage types that are mapped to Employee Central time pay types are allowed for multiple entries per day sot that the time pay types can be replicated on multiple occasions each day.

3. Configuring Basis Unit and Allowed Input Combination for Time Wage Types [page 47]For all wage types used in the replication of Time Sheet data from Employee Central, verify the basis unit to be used (hours) and the allowed input combination (number and unit).

4. Mapping Cost Center Keys [page 48]Map cost center keys in Customizing if the cost center codes in Employee Central differ from the corresponding codes in SAP ERP HCM.

44 PUBLIC



5.4.1 Mapping Time Pay Types with Time Wage Types

Define customer-specific code values to map Employee Central time pay types to SAP ERP HCM time wage types.

Procedure

1. Go to SAP ERP HCM Customizing for Personnel Management and choose Integration with SuccessFactors Employee Central Other Integration Settings Replicating Data from SuccessFactors to SAP ERP Assignment of Code Values .

2. Go to the Define Standard Code Value Lists step and define standard code value lists to be used in the activities described in the next steps.

3. Go to the Define Country Dependency of Code Value Lists step and assign the code value lists so they’re country/region-dependent.

4. Go to the Define Mapping Code Value Lists step and map all relevant external code values (meaning code values from Employee Central) to the code value lists of the SAP ERP HCM system.

Map all relevant time pay type codes (TIME_PAY_TYPE_CODE) of Employee Central to the corresponding time wage types (GDT Code) in your SAP ERP HCM system.

Time pay type is an attribute of the employee time valuation result and is included in the replication of time sheet data to the Employee Remuneration Info (2010) infotype in the SAP ERP HCM system.

If the Employee Central and SAP ERP HCM codes for time pay type and time wage type are the same, no further mapping is needed. If they aren’t, you need to map time pay type and time wage type values.

The SAP ERP HCM GDT code is limited to 10 characters. In Employee Central the time pay type codes can have 255 characters. If any time pay type codes replicated from the Employee Central Time Sheet are longer, any characters beyond the 10th character are cut off by the middleware during replication.

If you’re reusing the existing 4-character ERP Key as the external code for your time pay types in Employee Central, you don’t need to perform this activity as no mapping is required.

Example

Here's an example of time pay type codes mapped to time wage type GDT codes. You can see that different mappings are possible per country/region. In this example, the country/region codes are 92301 for Germany and 92310 for the US.

Table 11: Sample Mapping of Time Pay Type Codes to Wage Type GDT Codes


TIME_PAY_TYPE_CODE

91301 310 SCHEDULED MO10



TIME_PAY_TYPE_CODE

91301 310 WORK_REGPA MO10

TIME_PAY_TYPE_CODE

91301 310 W_REGPAY MO10

TIME_PAY_TYPE_CODE

91310 310 CALC_OT M811

TIME_PAY_TYPE_CODE

91310 310 M010 M800

TIME_PAY_TYPE_CODE

91310 310 OT_ADVPAY M811

TIME_PAY_TYPE_CODE

91310 OT_STDPAY M800

TIME_PAY_TYPE_CODE

91310 OVERTIME M807

TIME_PAY_TYPE_CODE

91310 PAIDABSENCE M851

Task overview: Configuration of Time Sheet Data Replication in the SAP ERP HCM System [page 44]

Next task: Enabling Time Wage Types for Multiple Entries Per Day [page 46]

5.4.2 Enabling Time Wage Types for Multiple Entries Per Day

Define that all SAP ERP HCM time wage types that are mapped to Employee Central time pay types are allowed for multiple entries per day sot that the time pay types can be replicated on multiple occasions each day.

Context

The SAP ERP HCM wage types you have previously mapped with Employee Central time pay types must be enabled so that they can be replicated on multiple occasions each day to the Employee Remuneration Info (2010) infotype.

46 PUBLIC



Procedure

1. In SAP ERP HCM Customizing, go to Personnel Management Personnel Administration Payroll DataEmployee Remuneration Information Wage Types Check Wage Type Catalog Check Entry

Permissibility per Infotype .2. Select the country grouping.

You need to customize this setting per country grouping.3. Define allowed wage types for multiple entries per day.

To do this, select the radio button in the Sev.times column for all wage types you have previously mapped to time pay types.


Previous task: Mapping Time Pay Types with Time Wage Types [page 45]

Next task: Configuring Basis Unit and Allowed Input Combination for Time Wage Types [page 47]

5.4.3 Configuring Basis Unit and Allowed Input Combination for Time Wage Types

For all wage types used in the replication of Time Sheet data from Employee Central, verify the basis unit to be used (hours) and the allowed input combination (number and unit).

Context

Define that Hours is used as the basis unit and that number and unit must be maintained for the time wage types and amount can’t be used.

Procedure

1. In SAP ERP HCM Customizing, go to Personnel Management Personnel Administration Payroll DataEmployee Remuneration Information Wage Types Check Wage Type Catalog Check Wage Type

Characteristics .2. In the Number/unit section, ensure that the Time unit/meas. field is filled with the unit Hours.3. In the Input combination section, ensure you make the settings required to allow Number/unit (by selecting

+) and disallow Amount (by selecting -).



Previous task: Enabling Time Wage Types for Multiple Entries Per Day [page 46]

Next task: Mapping Cost Center Keys [page 48]

5.4.4 Mapping Cost Center Keys

Map cost center keys in Customizing if the cost center codes in Employee Central differ from the corresponding codes in SAP ERP HCM.

Context

If the cost center key in Employee Central has 10 characters and has the same value as in SAP ERP HCM, no mapping is needed. If it is exactly 14 characters and after cutting off the first 4 characters it is still a valid 10-character value for a cost center in SAP ERP HCM (length of key field KOSTL of CSKS), no mapping is required either.

You must perform mapping between Employee Central and SAP ERP HCM, however, if you want to use cost centers from a company code not assigned within the Organizational Assignment (0001) infotype. The system first tries to derive the cost center from Employee Central directly. However, if a cost center is entered in Employee Central that belongs to a different company code than assigned in the Organizational Assignment infotype and no mapping is maintained, the SAP ERP HCM system takes the company code assigned in the Organizational Assignment infotype. This might cause errors where the entered cost center belongs to a different company code. Therefore, a mapping must be maintained from the Employee Central cost center to the SAP ERP HCM company code and cost center to avoid this potential error.

Procedure

1. In SAP ERP HCM Customizing, go to Personnel Management Integration with SuccessFactors Employee Central Other Integration Settings Replicating Data from SuccessFactors to SAP ERP Key Mapping of Organizational Terms Assign Cost Center Keys .

2. In the Cost Center ID column, enter the cost center external key from Employee Central.3. In the Company and Cost Center columns, enter the company code and the internal cost center key from

your SAP ERP HCM system, which you want to map.

Figure 2: Example: Mapping of Employee Central and SAP ERP HCM Cost Center ID

48 PUBLIC




Previous task: Configuring Basis Unit and Allowed Input Combination for Time Wage Types [page 47]


6 Middleware Setup

Set up SAP Cloud Integration as the middleware, to use it in integration between and the SAP ERP HCM system.

NoteFor more information about which versions of the middleware content provided for this integration are still supported and which have been deprecated, refer to SAP Note 2684991 .

CautionYou are only allowed to configure the content as described in this guide. If you make modifications not described in this guide, SAP will not provide support for the modified content.

The middleware content described in this guide is meant for use in SAP Cloud Integration. You are not allowed to deploy it in an on-premise SAP Process Orchestration system. For more information, see SAP Note 2428801 .

Middleware Content for Employee Time Data Replication [page 51]Get an overview of the integration content that's available in SAP Cloud Integration for replicating time off and time sheet data from Employee Central to SAP ERP HCM, for use in payroll.

Prerequisites for Using SAP Cloud Integration [page 53]Before you start configuring SAP Cloud Integration for employee time data replication from Employee Central to SAP ERP HCM, make sure that the prerequisites are fulfilled.

Communication Within the Employee Time Data Integration Scenario [page 54]Get an overview of how time off and time sheet data are replicated from Employee Central to the SAP ERP HCM using the cloud middleware.

Configuration of SAP Cloud Integration for Employee Time Data Replication [page 55]Some configuration steps are required to set up the integration flows. Their sequence depends on the communication used by the integration scenario.

Monitoring in SAP Cloud Integration [page 68]Use the monitoring features of SAP Cloud Integration to check whether any issues occurred in your middleware processes.

How to Report a Middleware Incident [page 68]If you have issues that you can't solve using the monitoring in SAP Cloud Integration, please report an incident and provide information about the process run.

50 PUBLIC


Middleware Setup



6.1 Middleware Content for Employee Time Data Replication

Get an overview of the integration content that's available in SAP Cloud Integration for replicating time off and time sheet data from Employee Central to SAP ERP HCM, for use in payroll.

Replication of employee time data (that is, absences and time pay components) from Employee Central uses the following integration packages and integration flows:

Table 12: Integration Packages and Integration Flows Used in This Integration

Integration package... And contained integration flows...

SAP SuccessFactors Employee Central Integration with SAP ERP: Employee Time for Payroll

Replicate Time Off Data from SAP SuccessFactors Employee Central to SAP ERP

Replicate Time Sheet Data from SAP SuccessFactors Employee Central to SAP ERP

SAP ERP or SAP S/4HANA Integration with SAP SuccessFactors Employee Central: Confirmation v2

Send Confirmations from SAP ERP or SAP S4HANA to SAP SuccessFactors Employee Central

NoteThe integration flow for the confirmation message is the same for employee master data replication and employee time data replication. Since we recommend that you set up the confirmation message for employee master data replication, you don't need to set it up again for employee time data replication.

In case you haven't set up the confirmation message yet, see Setting up the Integration Flow for Confirmation in the integration guide Replicating Employee Master Data and Organizational Assignments from Employee Central to SAP ERP HCM.

Find the most current version of the integration guide in SAP Help Portal, at http://help.sap.com/hr_ecintegration

Replicating Employee Time Data from Employee Central to SAP ERP HCM Using SAP Cloud Integration as the MiddlewareMiddleware Setup PUBLIC 51

https://help.sap.com/viewer/a7f164924edd4dfe817b7bdc2fc4927a/latest/en-US/fada9f90983c4464a4ad7c5b40866abf.html



Here's graphical overview of how the integration flows work and how the systems interact with each other:

Figure 3: Overview of Employee Time Data Replication

52 PUBLIC


Middleware Setup

6.2 Prerequisites for Using SAP Cloud Integration

Before you start configuring SAP Cloud Integration for employee time data replication from Employee Central to SAP ERP HCM, make sure that the prerequisites are fulfilled.

Some basic things need to be in place before you can set up the integration flows in SAP Cloud Integration. For more information, refer to Initial Setup.

● Employee master data replication is up and running. This means:○ The integration package for employee master data replication must already be installed and running

before you can start installing the integration package for the replication of time data.○ The integration package for the confirmation message must be installed and running.




○ Employee time data replication can only work if employee master data has already been replicated. For this reason, it is important that employee master data replication is running smoothly.

For more information, refer to the following implementation guides:○ Standard integration based on the Business Integration Builder (BIB): Replicating Employee Master

Data and Organizational Assignments from Employee Central to SAP ERP HCM○ Previous integration version: Replicating Employee Master Data from Employee Central to SAP ERP

HCM Using SAP Cloud Integration as the MiddlewareFind the most current version of these guides in SAP Help Portal at http://help.sap.com/hr_ecintegration.

● You’ve been provided with an SAP Cloud Integration account.● You have access to the web-based SAP Cloud Integration tools.

For details, refer to Tool Access.● You have access to the runtime node.

For details, refer to Runtime in Detail.● You have an SAP Cloud Integration communication user, which enables the customer system for

authentication based on user credentials. SAP Community Network (SCN) users are used for this purpose.For details, refer to the SAP Cloud Integration notification email you’ve received from SAP and to Creating a User for Cloud Integration, Neo Environment.

● You’ve enabled the CompoundEmployee API.● You have given the OData and CompoundEmployee API user the required permissions.


https://help.sap.com/viewer/368c481cd6954bdfa5d0435479fd4eaf/Cloud/en-US/0a556d5599ec4495ae1fb2ada6369744.html







https://help.sap.com/viewer/f69be9cbab414acdbeb3abdeaa1deed6



https://help.sap.com/viewer/368c481cd6954bdfa5d0435479fd4eaf/Cloud/en-US/30e39fa243914254982ac8329e85559a.html

https://help.sap.com/viewer/368c481cd6954bdfa5d0435479fd4eaf/Cloud/en-US/bdbc3f0224864ad5b163355ec537f6c6.html

https://help.sap.com/viewer/368c481cd6954bdfa5d0435479fd4eaf/Cloud/en-US/f489d66b6edc4eb682e65076e0d873f8.html

https://help.sap.com/viewer/368c481cd6954bdfa5d0435479fd4eaf/Cloud/en-US/f489d66b6edc4eb682e65076e0d873f8.html

Related Information

Enabling the OData API Audit Log [page 23]Permissions Required for API Access [page 19]

6.3 Communication Within the Employee Time Data Integration Scenario

Get an overview of how time off and time sheet data are replicated from Employee Central to the SAP ERP HCM using the cloud middleware.

The integration scenario for employee time data replication from Employee Central consists of these integration flows:

● Replicate Time Off Data from SAP SuccessFactors Employee Central to SAP ERP ● Replicate Time Sheet Data from SAP SuccessFactors Employee Central to SAP ERP● Send Confirmations from SAP ERP or SAP S4HANA to SAP SuccessFactors Employee Central




The communication within this scenario is as follows:

Figure 4: Communication Within Time Data Integration Scenario

1. The middleware queries Employee Central through the OData API and receives all the changed Time Off and Time Sheet records as the response.

2. The middleware pushes the data to SAP ERP HCM for inbound processing.3. Inbound processing writes the records to the relevant SAP ERP HCM infotypes.

54 PUBLIC


Middleware Setup





4. After inbound processing, the SAP ERP HCM system pushes the confirmation message back to the middleware.

5. The middleware upserts the data to the Employee Central Data Replication Monitor through the OData API.6. The Data Replication Monitor displays the replication status.

6.4 Configuration of SAP Cloud Integration for Employee Time Data Replication

Some configuration steps are required to set up the integration flows. Their sequence depends on the communication used by the integration scenario.

Configuring the integration scenario for employee time data replication from Employee Central to SAP ERP HCM means that you set up two integration flows:

● Replicate Time Off Data from SAP SuccessFactors Employee Central to SAP ERP ● Replicate Time Sheet Data from SAP SuccessFactors Employee Central to SAP ERP




Go through the following steps to set up the time data integration flows.

1. Configuring Certificates and Permissions [page 56]Configure certificates and permissions to enable a secure connection between your SAP ERP HCM system and SAP Cloud Integration.

2. Configuring Credentials for Communication Between SAP Cloud Integration and the Integrated Systems [page 57]

Create and deploy the credentials for the technical integration users. SAP Cloud Integration needs the credentials for communication with SAP SuccessFactors Employee Central and with SAP ERP HCM.

3. How to Find the Endpoint URLs and Target System [page 58]Find the URLs you need to specify in the middleware so that the integration flows know which system to address. And the target system you need to configure in the integration flows.

4. Copying the Integration Package to Your Workspace [page 62]Copy and deploy the integration content provided for replication of employee time data from Employee Central to SAP ERP HCM.

5. Configuring the Integration Flows for Employee Time Data Replication [page 63]Configure the receivers and the externalized parameters of the integration flows we provide for replication of employee time data from Employee Central.






6. Scheduling the Integration Flows for Employee Time Data Replication [page 67]Set up when and how often SAP Cloud Integration triggers the integration flows for time data replication from Employee Central to SAP ERP HCM.

7. Testing Connectivity of the Integration Flows for Employee Time Data Replication [page 68]Test if connectivity of the integration flows for time data replication from Employee Central to SAP ERP HCM works.

6.4.1 Configuring Certificates and Permissions

Configure certificates and permissions to enable a secure connection between your SAP ERP HCM system and SAP Cloud Integration.

Context

Even if you use basic authentication for your integration, certificates are needed to enable a secure HTTPS communication between SAP ERP HCM and SAP Cloud Integration. For more information, refer to Connecting a Customer System to Cloud Integration. The SAP Cloud Integration user must also have the required permissions.

Procedure

1. Add the root certificate from SAP Cloud Integration in the Trust Manager (STRUST) transaction in your SAP ERP HCM system, for connections initiated by the SAP ERP HCM system to SAP Cloud Integration.

For more information, refer to Trust Manager in the SAP NetWeaver documentation.2. Verify that the root certificate from your SAP ERP HCM system was added in the keystore in your SAP

Cloud Integration tenant, for connections initiated by SAP Cloud Integration to the SAP ERP HCM system.

This step has been taken care of during the initial setup phase by the Cloud Operations team.3. Make sure that the SAP Cloud Integration user that is used to trigger calls from outside the middleware to

SAP Cloud Integration has the necessary permission for sending messages.

For more information, refer to Persona for the Cloud Foundry Environment or Persona for the Neo Environment.

Task overview: Configuration of SAP Cloud Integration for Employee Time Data Replication [page 55]

Next task: Configuring Credentials for Communication Between SAP Cloud Integration and the Integrated Systems [page 57]

56 PUBLIC


Middleware Setup

https://help.sap.com/viewer/368c481cd6954bdfa5d0435479fd4eaf/Cloud/en-US/7cfe913ba85d463a9c5fce101c3ae460.html

https://help.sap.com/viewer/368c481cd6954bdfa5d0435479fd4eaf/Cloud/en-US/7cfe913ba85d463a9c5fce101c3ae460.html

https://help.sap.com/viewer/280f016edb8049e998237fcbd80558e7/latest/en-US/4c5bdb17f85640f1e10000000a42189c.html

https://help.sap.com/viewer/368c481cd6954bdfa5d0435479fd4eaf/Cloud/en-US/4b4ba1c553474259b5be661f4ef0702c.html

https://help.sap.com/viewer/368c481cd6954bdfa5d0435479fd4eaf/Cloud/en-US/2937e5ca6ef448cfb21451a2461cc2a6.html

6.4.2 Configuring Credentials for Communication Between SAP Cloud Integration and the Integrated Systems

Create and deploy the credentials for the technical integration users. SAP Cloud Integration needs the credentials for communication with SAP SuccessFactors Employee Central and with SAP ERP HCM.

Prerequisites

Determine the SAP SuccessFactors credentials for the API user you want to use for the integration. The user must have the permission to call SAP SuccessFactors OData APIs.

Determine the SAP ERP HCM credentials for the user that you want to use for the integration.

Context

For more information about credentials artifacts and other security material in SAP Cloud Integration, refer to Managing Security Material.

Procedure

1. Go to the SAP Cloud Integration Web UI and choose Operations View from the top-level menu on the left.

2. Choose Manage Security Security Material .3. To create a credentials artifact for the communication between SAP Cloud Integration and Employee

Central, choose Create and select a credentials type.○ If you want to use the Basic authentication type for Employee Central receivers, select User Credentials

and deploy two credentials artifacts with the following attributes:

Table 13: Credentials Artifact with Type SuccessFactors

Field Name User Action and Values

Name Enter any name.

Type Select SuccessFactors.

User Enter the name of the SAP SuccessFactors API user.

Password Enter the password of the SAP SuccessFactors API user.

Company ID Enter the name of your SAP SuccessFactors Employee Central instance.

○ If you want to use the OAuth2 SAML Bearer Assertion authentication type for Employee Central receivers, select OAuth2 SAML Bearer Assertion and deploy a corresponding credentials artifact.


https://help.sap.com/viewer/368c481cd6954bdfa5d0435479fd4eaf/Cloud/en-US/b8ccb53b9ec44652b885476f02184a0f.html

For more information, refer to Deploying an OAuth2 SAML Bearer Assertion.

4. To create a credentials artifact for the communication between SAP Cloud Integration and SAP ERP HCM, select User Credentials again.

5. Deploy a credentials artifact with the following attributes:

Table 14: Credentials Artifact with Type User Credentials for SAP ERP HCM

Field Name User Action and Values

Name Enter any name.

Type Select User Credentials.

User Enter the name of the SAP ERP HCM integration user.

Password Enter the password of the SAP ERP HCM integration user.

Next Steps

You enter the names given to these credentials artifacts when you configure the integration flows.


Previous task: Configuring Certificates and Permissions [page 56]

Next: How to Find the Endpoint URLs and Target System [page 58]

6.4.3 How to Find the Endpoint URLs and Target System

Find the URLs you need to specify in the middleware so that the integration flows know which system to address. And the target system you need to configure in the integration flows.

Finding the URLs for Communication from the Middleware to SAP ERP HCM [page 59]Determine the endpoint URL for SAP ERP HCM that you need to enter in the middleware.

Finding the URL for Communication from the Middleware to Employee Central [page 60]Determine the endpoint URL for Employee Central that you need to enter in the middleware.

Finding and Setting the Replication Target System [page 61]Find the externalCode of the SAP ERP HCM target system in Employee Central and enter it in the middleware.

Parent topic: Configuration of SAP Cloud Integration for Employee Time Data Replication [page 55]

Previous task: Configuring Credentials for Communication Between SAP Cloud Integration and the Integrated Systems [page 57]

58 PUBLIC


Middleware Setup

https://help.sap.com/viewer/DRAFT/4e2b95bfe5f84915b5e54a6dd9213b46/IAT/en-US/3ee658286bac40829fcfa4e0c9044f75.html

Next task: Copying the Integration Package to Your Workspace [page 62]

6.4.3.1 Finding the URLs for Communication from the Middleware to SAP ERP HCM

Determine the endpoint URL for SAP ERP HCM that you need to enter in the middleware.

Context

Time data replication is scheduled in the middleware. That's why the integration flows for time data replication need to know the endpoint URL they are to call in the SAP ERP HCM system.

Figure 5: Endpoint URL in the SAP ERP HCM System

Here's how you can find these endpoint URLs in the SAP ERP HCM system:

Procedure

1. Go to the SOA Management (SOAMANAGER) transaction.

2. Choose Simplified Web Service Configuration.

NoteThe Simplified Web Service Configuration tool described here is available from SAP NetWeaver 7.0 enhancement package 2 (SAP_BASIS 702). If you’re using a lower SAP NetWeaver release, you must use the Web Service Configuration tool instead. For more information, refer to Configuring a Service Provider in the SAP NetWeaver documentation for release 7.0. For a detailed how-to description of Web Service Configuration and Simplified Web Service Configuration refer to the SAP Community Network, at ABAP Connectivity - Web Services ABAP > How to configure a Service Provider and How to configure a Service Provider (Simplified). To find the SOA Manager documentation for your SAP NetWeaver release, go to http://help.sap.com and search for working with soamanager. Then filter the search result for your SAP NetWeaver release and support package.

3. Search for the EMPLOYEETIMEECTOERPREQUEST_IN service definition.





http://help.sap.com

4. Select the entry and choose Show Details.5. Copy these URLs from the details popup:

○ The WSDL URL is the URL shown for With WS Policy in the WSDL URLs section.○ The SOAP endpoint URL is the Access URL shown in the Configuration Details section.

NoteThe URLs shown on the details popup are only accessible internally. To access the URLs externally, copy the first part of the URL from the SOA Management browser window, for example https://xxxx.sap.corp:44311/. Then replace the first part of the WSDL and endpoint URLs displayed on the details popup with the external part you copied from SOA Management.

In case you can't show the details, select the User/Password checkbox and choose Save. Afterwards, you can find the URLs in the details.

6.4.3.2 Finding the URL for Communication from the Middleware to Employee Central

Determine the endpoint URL for Employee Central that you need to enter in the middleware.

Context

To be able to trigger calls to Employee Central, the middleware needs to know the ODAta API endpoint URL it is to call there.

Figure 6: Endpoint URL in Employee Central

Procedure

1. Check which is your data center.2. When setting up the integration flow, choose Select next to the Address field to add the base URL of your

SAP SuccessFactors system, depending on your data center.

60 PUBLIC


Middleware Setup

6.4.3.3 Finding and Setting the Replication Target System

Find the externalCode of the SAP ERP HCM target system in Employee Central and enter it in the middleware.

Procedure

1. Log on to Employee Central as an administrator.2. Go to Admin Center, choose the Manage Data tool, and search for the Replication Target System object you

created for the replication of employee time data.3. Copy the externalCode of the Replication Target System object and save it.4. Go to the middleware system.5. Go to the configuration of the integration flow in the middleware.6. Enter the replication target system you copied in step 3 in the relevant parameter of the integration flow.

NoteMake sure that the replication target system you enter here is the same as configured in the confirmation message. For setup of the confirmation message, see the following integration guides:

○ Standard integration based on the Business Integration Builder (BIB): Replicating Employee Master Data and Organizational Assignments from Employee Central to SAP ERP HCM

○ Previous integration version: Replicating Employee Master Data from Employee Central to SAP ERP HCM Using SAP Cloud Integration as the Middleware

Find the most current version of these guides in SAP Help Portal at http://help.sap.com/hr_ecintegration.

Related Information

Creating Replication Target System [page 24]Creating Replication Target System [page 24]








6.4.4 Copying the Integration Package to Your Workspace

Copy and deploy the integration content provided for replication of employee time data from Employee Central to SAP ERP HCM.

Context

You use the SAP Cloud Integration Web UI to access and manage integrations configured in SAP Cloud Integration. For more information, refer to Developing Integration Content With SAP Cloud Integration.

Procedure

1. Go to the SAP Cloud Integration tenant for which you want to set up the integration content.2. Browse the content catalog to find the SAP SuccessFactors Employee Central Integration with SAP ERP:

Employee Time for Payroll integration package.3. Copy the content of the integration package to your workspace so you can configure and deploy it.4. Configure the integration flows.

Next Steps

Configure the integration flows.


Previous: How to Find the Endpoint URLs and Target System [page 58]

Next task: Configuring the Integration Flows for Employee Time Data Replication [page 63]

Related Information

Replication of Country/Region-Specific Time Off Data [page 77]How to Find the Endpoint URLs and Target System [page 58]Configuring Credentials for Communication Between SAP Cloud Integration and the Integrated Systems [page 57]

62 PUBLIC


Middleware Setup

https://help.sap.com/viewer/368c481cd6954bdfa5d0435479fd4eaf/Cloud/en-US/e6b43b4c5a5042fda30a9dfdab97eff3.html

6.4.5 Configuring the Integration Flows for Employee Time Data Replication

Configure the receivers and the externalized parameters of the integration flows we provide for replication of employee time data from Employee Central.

Context

You make the following settings for both, the Replicate Time Off Data from SAP SuccessFactors Employee Central to SAP ERP and Replicate Time Sheet Data from SAP SuccessFactors Employee Central to SAP ERP integration flows.

Procedure

1. On the first tab, schedule the processes as shown in the next section.2. On the second tab, configure the SAP_ERP receiver:

Table 15: SAP_ERP Receiver Configuration

Field What to Enter

Receiver Choose SAP_ERP.

Adapter Type Choose SOAP (no other entries are possible).

For more information, refer to SOAP (SAP RM) Adapter.

Address Enter the endpoint URL of the SAP ERP HCM inbound web service for replication of employee time data.

If you don't use SAP Cloud Connector, the URL must start with https://.

If you use SAP Cloud Connector, the URL must start with http://. For more information about using SAP Cloud Connector, refer to Outbound: SAP Cloud Connector.

Proxy Type If you don't use SAP Cloud Connector, choose Internet.

If you use SAP Cloud Connector, choose On-Premise.


https://help.sap.com/viewer/368c481cd6954bdfa5d0435479fd4eaf/Cloud/en-US/6bd724f37f29493eb619338c94982b01.html

https://help.sap.com/viewer/368c481cd6954bdfa5d0435479fd4eaf/Cloud/en-US/642e87f1492146998a8eb0779cd07289.html

Field What to Enter

Location ID (only in case On-Premise is selected for Proxy Type)

To connect to a cloud connector instance associated with your account, enter the location ID that you defined for this instance in the destination configuration on the cloud side. Or else enter ${header.headername} to dynamically read the value from a header.

The location ID identifies the location of this cloud connector for a specific account. It’s used as routing information. Thus, it's possible to connect multiple cloud connectors to a single account. If you don't specify any value for Location ID, the default is used, which is representing the behavior of previous cloud connector versions. The location ID must be unique per account and must be an identifier that can be used in a URI.

Authentication In case Internet is selected for Proxy Type: Choose either Basic or Client Certificate. Don't use the other options.

In case On-Premise is selected for Proxy Type: Choose either Basic or Principal Propagation. Don't use the other options. For more information about principal propagation, refer to Setting Up Principal Propagation (Example Scenario).

Credential Name (only in case Basic is selected for Authentication)

Enter the name of the credentials artifact with the type User Credentials that you created before.

For more information, refer to Basic Authentication.

Private Key Alias (only in case Client Certificate is selected for Authentication)

Upload the appropriate certificate and enter it in the Private Key Alias field.

For more information, refer to Client Certificate Authentication (Outbound).

Timeout (in ms) Use the default value. Only change this value if you’re facing issues. In that case, try a higher number.

Allow Chunking By default, this checkbox is selected. This setting is supported by all HTTP 1.1 servers. If you use an HTTP server that doesn't support chunking and therefore face connection issues, deselect this checkbox.

3. Configure the EC_System receiver on the same tab:

Table 16: EC_System Receiver Configuration

Field What to Enter

Receiver Choose EC_System.

64 PUBLIC


Middleware Setup

https://help.sap.com/viewer/368c481cd6954bdfa5d0435479fd4eaf/Cloud/en-US/34eff846cfb84011b09ad1fb1894ce14.html

https://help.sap.com/viewer/368c481cd6954bdfa5d0435479fd4eaf/Cloud/en-US/34eff846cfb84011b09ad1fb1894ce14.html

https://help.sap.com/viewer/368c481cd6954bdfa5d0435479fd4eaf/Cloud/en-US/a5d77b12ff16483c965cce936aa1b698.html

https://help.sap.com/viewer/368c481cd6954bdfa5d0435479fd4eaf/Cloud/en-US/c4e4a1570d6b4896b7426f67ae053a5e.html

https://help.sap.com/viewer/368c481cd6954bdfa5d0435479fd4eaf/Cloud/en-US/c4e4a1570d6b4896b7426f67ae053a5e.html

Field What to Enter

Adapter Type Choose SuccessFactors (no other entries are possible).

For more information, refer to SuccessFactors (OData V2) Adapter.

Address Choose Select to add the base URL of your SAP SuccessFactors system, depending on your data center.

RestrictionWe don’t support IP addresses in URLs as part of our reference architecture. Use domain names instead. If you think you have a special case that requires IP addresses instead of domain names, contact Product Support.

Address Suffix Enter /odata/v2.

Authentication Choose either Basic or OAuth2 SAML Bearer Assertion.

Credential Name If you've selected Basic for Authentication: Enter the name of the credentials artifact with the type SuccessFactors that you created before.

If you've selected OAuth2 SAML Bearer Assertion for Authentication: Enter the name of the credentials artifact with the type OAuth2 SAML Bearer Assertion that you created before.

Page Size Default is 200. Only change if you're facing timeouts. In that case, try a smaller page size.

Timeout (in min) Use the default value. Only change this value if you’re facing issues. In that case, try a higher number.

4. On the last tab, configure the process parameters:


https://help.sap.com/viewer/368c481cd6954bdfa5d0435479fd4eaf/Cloud/en-US/b27829c720db4773a147b8bb2b61c2ba.html

https://help.sap.com/viewer/368c481cd6954bdfa5d0435479fd4eaf/Cloud/en-US/b27829c720db4773a147b8bb2b61c2ba.html

Table 17: Process Parameters

Field What to Enter

ENABLE_COUNTRY_SPECIFIC_FIELDS (only for the Replicate Time Off Data from SAP SuccessFactors Employee Central to SAP ERP integration flow)

Select TRUE to transfer country/region-specific information.

ExampleUsing this parameter you can replicate the attributes for identical and overlapping sickness absences. These attributes show that an employee is sick more than once in a given period and that the sickness absences are to be considered together in continued pay processing for specific countries/regions. The SAP ERP HCM system calls these attributes Indicator for Subsequent Illness and Indicator for Repeated Illness and stores them in the Absences (2001) infotype.

ENABLE_PAYLOAD_LOGGING Enter TRUE to transfer extended information to the process log in the middleware to be able to analyze issues more easily. You can also reset the parameter to FALSE again if you no longer need the extended log.

CautionFor data protection reasons, enable this extended log for troubleshooting purposes only. Make sure to disable the parameter again afterwards.

If you enable the extended log, the complete message payload containing all data that is to be transferred is stored in the log. Make sure that you configure permissions in a way that only authorized persons can view the payload in the log. Also ensure that you're compliant with the data protection and privacy regulations so that your data gets the highest level of protection.

For more information, refer to:

○ Data Protection and Privacy○ Identity and Access Management and Persona

for the Cloud Foundry Environment○ Managing Users and Role Assignments and Per

sona for the Neo Environment

REPLICATION_TARGET_SYSTEM Enter your replication target system.

66 PUBLIC


Middleware Setup

https://help.sap.com/viewer/368c481cd6954bdfa5d0435479fd4eaf/Cloud/en-US/c43df85c454f4da18dc80c17d512be33.html

https://help.sap.com/viewer/368c481cd6954bdfa5d0435479fd4eaf/Cloud/en-US/f805b2275dd84dfca0e6e57c91d95e91.html


https://help.sap.com/viewer/368c481cd6954bdfa5d0435479fd4eaf/Cloud/en-US/1d470b08132f428d97ed4b2128df0c13.html



Field What to Enter

SAP_CC_LOCATION_ID (only for the Replicate Time Sheet Data from SAP SuccessFactors Employee Central to SAP ERP integration flow)

If you want to connect multiple SAP Cloud Connectors to a single account inSAP Cloud Integration, for communication with multiple SAP ERP HCM systems, enter the location ID you've defined when setting up your Cloud Connectors. This ID makes sure that all connections of this integration flow instance with a specific SAP ERP HCM system use the same SAP Cloud Connector.

For more information, refer to Using SAP Cloud Connector with Cloud Integration Adapters.


Previous task: Copying the Integration Package to Your Workspace [page 62]

Next task: Scheduling the Integration Flows for Employee Time Data Replication [page 67]

6.4.6 Scheduling the Integration Flows for Employee Time Data Replication

Set up when and how often SAP Cloud Integration triggers the integration flows for time data replication from Employee Central to SAP ERP HCM.

Procedure

1. In integration flow configuration, choose the Scheduler tab.2. For initial load, choose Run once.3. After initial load and when the system is ready for regularly recurring replication, choose Schedule to Recur

and make the required time settings.


Previous task: Configuring the Integration Flows for Employee Time Data Replication [page 63]

Next task: Testing Connectivity of the Integration Flows for Employee Time Data Replication [page 68]


https://help.sap.com/viewer/368c481cd6954bdfa5d0435479fd4eaf/Cloud/en-US/65a60e750eca49328fef93c0723ad4b8.html

https://help.sap.com/viewer/368c481cd6954bdfa5d0435479fd4eaf/Cloud/en-US/65a60e750eca49328fef93c0723ad4b8.html

6.4.7 Testing Connectivity of the Integration Flows for Employee Time Data Replication

Test if connectivity of the integration flows for time data replication from Employee Central to SAP ERP HCM works.

Procedure

1. In integration flow configuration, choose the Scheduler tab.2. Choose the option Run Once and deploy the integration flow.

The process will execute once by selecting all the relevant time data records from Employee Central.3. Check the message shown under Message Monitoring.


Previous task: Scheduling the Integration Flows for Employee Time Data Replication [page 67]

6.5 Monitoring in SAP Cloud Integration

Use the monitoring features of SAP Cloud Integration to check whether any issues occurred in your middleware processes.

SAP Cloud Integration provides a web-based monitoring UI that allows you to check the status of messages and integration content artifacts for a tenant cluster. For more information, see Monitoring.

Use the log ID that you find in the monitoring to find the log of a specific process that didn't run successfully and to filter the log for detailed information.

6.6 How to Report a Middleware Incident

If you have issues that you can't solve using the monitoring in SAP Cloud Integration, please report an incident and provide information about the process run.

If you face an issue with your SAP Cloud Integration-based integration scenario and want to report an incident, make sure that the failed process run was carried out with the extended logging option activated. You can enable this option using the externalized parameter ENABLE_PAYLOAD_LOGGING in integration flow configuration. Switching on the extended log ensures that the data that's needed for analyzing the issue is written to the log. Add the log ID to the incident so that the support team can find the log easily.

68 PUBLIC


Middleware Setup

https://help.sap.com/viewer/368c481cd6954bdfa5d0435479fd4eaf/Cloud/en-US/05446d0616d44e1daf821c273b69fcc6.html

CautionFor data protection reasons, enable this extended log for troubleshooting purposes only. Make sure to disable the parameter again afterwards.

If you enable the extended log, the complete message payload containing all data that is to be transferred is stored in the log. Make sure that you configure permissions in a way that only authorized persons can view the payload in the log. Also ensure that you're compliant with the data protection and privacy regulations so that your data gets the highest level of protection.

For more information, refer to:

● Data Protection and Privacy● Identity and Access Management and Persona for the Cloud Foundry Environment● Managing Users and Role Assignments and Persona for the Neo Environment

NoteWhen reporting a middleware incident, please make sure that you include all required information, as listed in the SAP Knowledge Base Article (KBA) 2763716 .


https://help.sap.com/viewer/368c481cd6954bdfa5d0435479fd4eaf/Cloud/en-US/c43df85c454f4da18dc80c17d512be33.html

https://help.sap.com/viewer/368c481cd6954bdfa5d0435479fd4eaf/Cloud/en-US/f805b2275dd84dfca0e6e57c91d95e91.html


https://help.sap.com/viewer/368c481cd6954bdfa5d0435479fd4eaf/Cloud/en-US/1d470b08132f428d97ed4b2128df0c13.html



7 Replication of Employee Time Data

Look at examples of how Time Off and Time Sheet data is replicated from Employee Central and learn more about the country/region specifics of Time Off data replication.

Example: Replication of Absences to SAP ERP HCM [page 70]Let's look at an example of how data is being replicated from Employee Central Time Off to SAP ERP HCM.

Example: Replication of Employee Time Valuation Result to SAP ERP HCM [page 73]Let's look at an example of how data is being replicated from Employee Central Time Sheet to SAP ERP HCM.

Replication of Country/Region-Specific Time Off Data [page 77]You can replicate country-specific or region-specific fields from Employee Central Time Off to the Absences (2001) infotype in SAP ERP HCM.

7.1 Example: Replication of Absences to SAP ERP HCM

Let's look at an example of how data is being replicated from Employee Central Time Off to SAP ERP HCM.

Replication Overview

The overall process for replication of absences from Employee Central to the SAP ERP HCM system in this example is broken down into seven main phases, preceded by a preliminary phase where the absence is approved. The example focuses on the replication of a single absence for a single employee.

70 PUBLIC


Replication of Employee Time Data

Figure 7: Replication Process for Time Off Data

Phase 0: Absence Approval and Creation of Employee Time in Employee Central

An employee requests time off, for example PTO (paid time off). The absence is approved by the supervisor or manager and the approval status changes to Approved.

Phase 1: Create or Update Data Replication Proxy and Trigger Replication Process

The status change for the absence from To be Approved to Approved creates the data replication proxy, which triggers the replication of the absence to the SAP ERP HCM system.

The replication process is triggered by an OData call from the middleware to the Employee Central generic object Data Replication Proxy.

Phase 2: Collect Data Replication Proxy

The middleware checks if there are data replication proxies available. If yes, the middleware collects them from the Employee Central generic object Data Replication Proxy, for each distinct employee time to be replicated. The data replication proxy in Employee Central tracks the status of employee time and controls that only objects with status Out of Sync or status Deleted are selected for replication.

Replicating Employee Time Data from Employee Central to SAP ERP HCM Using SAP Cloud Integration as the MiddlewareReplication of Employee Time Data PUBLIC 71

Phase 3: Map Employee Central Time Type to SAP ERP HCM Absence Type

Replication continues with the mapping of the time type from Employee Central to the SAP ERP HCM absence type.

Phase 4: Replicate Absence to Infotype 2001 in SAP ERP HCM

The absence is replicated to SAP ERP HCM. In this example and based on pre-configured mapping, the Absences (2001) infotype in SAP ERP HCM is filled.

Phase 5: Send Replication Status to Data Replication Monitor

The status of the replication to infotype 2001 is sent from SAP ERP HCM to the Employee Central Data Replication Monitor.

Phase 6: Update Data Replication Monitor

The Employee Central Data Replication Monitor is updated with the status of the replication. A successful replication results in a status of Successful, and no more replication attempts are made. The corresponding data replication proxies are deleted.

An unsuccessful replication receives the status Failed in the Data Replication Monitor.

Phase 7: Retry for Unsuccessful Replication

Any replication with the status Failed is retried until the status Successful is achieved in the Data Replication Monitor. When replication was successful, the corresponding data replication proxies are deleted.

Setting up a Replication Confirmation Process

To enable the status for the replication of employee absences to be directly updated, you must set up a replication confirmation process during the initial setup of this replication, and not at a later point in time.

You enable the replication confirmation process as part of setting up the middleware between Employee Central and SAP ERP HCM for employee master data replication. Setting up this confirmation process is essential because once the replication is set up in Employee Central, data is continually replicated if no confirmation mechanism is configured within the middleware to control the replication itself.

72 PUBLIC



TipIf you need to replicate employee time valuation results that were created before the configuration of the replication process was completed, you must trigger the replication explicitely (see the related information).

Related Information

How to Trigger Replication of Existing Absences or Time Sheets [page 97]

7.2 Example: Replication of Employee Time Valuation Result to SAP ERP HCM

Let's look at an example of how data is being replicated from Employee Central Time Sheet to SAP ERP HCM.

Replication Overview

The overall process for replication of time sheet data from Employee Central to the SAP ERP HCM system in this example is broken down into seven main phases, preceded by a preliminary phase where the time sheet is approved. The example focuses on the replication of a single time pay type, Regular Pay, within a replicated time valuation result for a single employee.


Figure 8: Replication Process for Time Sheet Data

In the following example, you will see how 8 hours of Regular Time recorded by the employee for Tuesday, May 26 is replicated to SAP ERP HCM, as part of a replicated employee time valuation result.

Phase 0: Time Sheet Approval and Creation of Employee Time Valuation Result in Employee Central

An employee records only overtime in her time sheet. She has a standard weekly working time (time pay type Regular Time) of Tuesday to Friday, 8 hours per day, which is recorded automatically in her time sheet. In this week, she works 10 hours of overtime which she records manually in her time sheet, 2.5 hours of which is paid at the basic overtime rate, and the remainder at a premium overtime rate.

This time sheet is approved by her assigned supervisor or manager and the time sheet status changes to Approved.

The status change for the time sheet from To be Approved to Approved triggers Employee Central to derive a time valuation result for this employee from her approved time sheet. A single time valuation result is created and replicated to the SAP ERP HCM system.

A data replication proxy is created at this point.

74 PUBLIC



Phase 1: Create/Update Data Replication Proxy and Trigger Replication Process

A data replication proxy is created or updated after approval or cancellation of a time sheet in Employee Central.

The replication process is triggered by an OData call from the middleware to the Employee Central generic object Data Replication Proxy.

Phase 2: Collect Data Replication Proxy

The middleware checks if there are data replication proxies available. If yes, the middleware collects them from the Employee Central generic object DataReplicationProxy, for each distinct employee time valuation result to be replicated. The data replication proxy in Employee Central tracks the status of employee time valuation results and controls that only objects with status Out of Sync or status Deleted are selected for replication.

Phase 3: Map Employee Central Time Pay Type to SAP ERP HCM Wage Type

Replication continues with mapping of the Regular Pay time pay type from the time sheet to the SAP ERP HCM wage type MI01 in the SAP ERP HCM system.

Table 18: Example: Mapping Employee Central Time Pay Type to SAP ERP HCM Wage Type


TIME_PAY_TYPE_CODE

92301 310 W_REGPAY MI01

Phase 4: Replicate Employee Time Valuation Result to Infotype 2010 in SAP ERP HCM

The complete time valuation result for the employee is replicated to SAP ERP HCM. In this example and based on pre-configured mapping, the Employee Remuneration Info (2010) infotype in SAP ERP HCM is filled as shown in this table:

Table 19: Example: Infotype 2010

Date Wage Type Text Hours Number Unit

Oct. 21, 2016 MI01 Norm. Hrs. 0,00 8,00 Hours



Date Wage Type Text Hours Number Unit




Phase 5: Send Replication Status to Data Replication Monitor

The status of the replication to infotype 2010 is sent from SAP ERP HCM to the Employee Central Data Replication Monitor.

Phase 6: Update Data Replication Monitor

The Employee Central Data Replication Monitor is updated with the status of the replication. A successful replication results in a replication monitor status of Successful and no more replication attempts are made.

An unsuccessful replication receives the status Failed in the Data Replication Monitor.

Phase 7: Retry for Unsuccessful Replication

Any replication with the status Failed is retried until the status Successful is achieved in the Data Replication Monitor.

Setting up a Replication Confirmation Process

To enable the status for the replication of employee time valuation results to be directly updated, you must set up a replication confirmation process during the initial set up of this replication, and not at a later point in time.

You enable the replication confirmation process as part of setting up the middleware between Employee Central and SAP ERP HCM for employee master data replication. Setting up this confirmation process is essential because once the replication is set up in Employee Central, data is continually replicated if no confirmation mechanism is configured within the middleware to control the replication itself.

TipIf you need to replicate employee time valuation results that were created before the configuration of the replication process was completed, you must trigger the replication explicitely (see the related information).

76 PUBLIC



Related Information

How to Trigger Replication of Existing Absences or Time Sheets [page 97]

7.3 Replication of Country/Region-Specific Time Off Data

You can replicate country-specific or region-specific fields from Employee Central Time Off to the Absences (2001) infotype in SAP ERP HCM.

The rules for calculation of continued pay and sick pay supplements if an employee is sick for a longer period of time vary from country/region to country/region. That's why country/region-specific object definitions are defined in Employee Central, which contain the fields needed for continued pay processing. These object definitions are associated to the EmployeeTime object definition. Currently, country/region-specific object definitions are available for Colombia (EmployeeTimeCOL), Germany (EmployeeTimeDEU), Mexico (EmployeeTimeMEX), and Spain (EmployeeTimeESP). Replication of country/region-specific fields for continued pay are replicated into the relevant country/region-specific sickness subtype of the Absences (2001) infotype in SAP ERP HCM for these countries.

For more information about country/region specifics for Employee Central Time Off, refer to Country/Region Specific Features in Employee Central Time Off in Implementing Employee Central Time Management.

Replication of Time Off Data for Colombia [page 77]Replication of Time Off data enables payroll in SAP ERP HCM to process continued pay for Colombian employees.

Replication of Time Off Data for Germany [page 80]Replication of Germany-specific time off data enables payroll in SAP ERP HCM to process this data for German employees.

Replication of Time Off Data for Mexico [page 88]Replication of Time Off data for Mexico enables payroll in SAP ERP HCM to process continued pay for Mexican employees.

Replication of Time Off Data for Spain [page 91]Replication of Time Off data for Spain enables payroll in SAP ERP HCM to process continued pay for Spanish employees.

7.3.1 Replication of Time Off Data for Colombia

Replication of Time Off data enables payroll in SAP ERP HCM to process continued pay for Colombian employees.

Indicators for sickness absences that have been linked with the reason Identical in Employee Central for Colombian employees are replicated to the SAP ERP HCM system.

Continued Pay and Linking of Absences for Colombia [page 78]Employee Central groups together sickness records entered for country version Colombia when they are linked for continued pay processing.


https://help.sap.com/viewer/68de09dff990417b9f0acf6ccc13a14d/latest/en-US/a66df761c913488e92415b201843da1d.html

https://help.sap.com/viewer/68de09dff990417b9f0acf6ccc13a14d/latest/en-US/a66df761c913488e92415b201843da1d.html

Replication of Linked Absences for Colombia to SAP ERP HCM [page 79]When linked sickness absences are replicated from Employee Central Time Off, they’re linked in the SAP ERP HCM system using a system-generated link index. Colombia handles identical sickness absences.

How Absence Fields Are Mapped for Colombia [page 80]Country/region-specific field mapping is used for replication of linked sickness absences from Employee Central to the SAP ERP HCM system.

7.3.1.1 Continued Pay and Linking of Absences for Colombia

Employee Central groups together sickness records entered for country version Colombia when they are linked for continued pay processing.

The HR admin can link sickness records in Employee Central for Colombia if they are related. A related sickness absence is called identical sickness in Employee Central. In SAP ERP HCM this corresponds to a subsequent illness.

ExampleAn employee has an illness or accident for the first time. Then he or she comes back to work. After some time, the employee has another illness or accident that is related to the first one. In this case, sickness records shall be linked even though the employee has worked in between. The HR admin links them when creating the sick leaves for the employee. If the admin selects a Colombia-specific time type with the Sickness absence class, he or she can select the reason Identical and link the sick leaves.

If sick leaves are linked, an EmployeeTimeGroup object is generated automatically in Employee Central that groups them together in the background. An external code (a 32-characters UUID) is generated for the EmployeeTimeGroup object. This code is stored in the identicalSicknessGroup field of the corresponding EmployeeTimeCOL object. The EmployeeTimeCOL object then has a <CountrySpecificFields> node with a <Name> and a <Value> attribute, as shown in this example:

Sample Code

<CountrySpecificFields> <Name>identicalSicknessGroup</Name> <Value>258ZzRet9867hUpnF085527GirhN9783</Value> </CountrySpecificFields>

NoteLinking of sick leaves is only available when People Profile is enabled in your Employee Central instance.

78 PUBLIC



7.3.1.2 Replication of Linked Absences for Colombia to SAP ERP HCM

When linked sickness absences are replicated from Employee Central Time Off, they’re linked in the SAP ERP HCM system using a system-generated link index. Colombia handles identical sickness absences.

SAP ERP HCM stores link indices in the Linking Index for Employee Time Groups (ECTIM_LINK_INDEX) table. The link indices tell the SAP ERP HCM system which sick leaves are to be linked.

Let's take a closer look at the processing in the SAP ERP HCM system using an example.

Example

Table 20: Example: Linking Index in SAP ERP HCM

Employee's Personnel Number Linking Reason

External Code of the Employee Time Group Object Linking Index

00482236 Subsequent Illness (= Identical Sickness)

258ZzRet9867hUpnF085527GirhN9783

1


ouKTre56294246Per746Nm93627LZk83

2

When the first sick leave is replicated for the employee with the personnel number 00482236, SAP ERP HCM checks whether the Linking Index for Employee Time Groups table already contains an entry for this personnel number, linking reason, and EmployeeTimeGroup. Since this isn’t the case, it creates one, generating the linking index 1 (first row in the example above). Then it creates a record of the Absences infotype for this sick leave, storing the linking index it has generated, 1, in the KENN1 field of the infotype record.

When the next sick leave is transferred, SAP ERP HCM checks again whether the Linking Index for Employee Time Groups table contains an entry with the same personnel number, linking reason, and EmployeeTimeGroup. Since this is the case, it considers the sick leave to be linked with the first sick leave that was transferred for this employee. That's why SAP ERP HCM stores the same linking index, 1, in the KENN1 field when creating a record of the Absences infotype. Since both infotype records have the same linking index, the SAP ERP HCM system knows that these two infotype records are linked and are to be handled together.

Then the next sick leave is transferred for the same employee. Again, SAP ERP HCM checks whether the Linking Index for Employee Time Groups table contains an entry with the same personnel number, linking reason, and EmployeeTimeGroup. This time, personnel number and linking reason are the same, but a different EmployeeTimeGroup object is assigned. That's why SAP ERP HCM generates a new linking index, 2 (second row in the example). Meaning, it stores 2 this time in the KENN1 field when creating the infotype record. Since the linking index differs from the one stored in the first two infotype records created for this employee, this new record is considered not to be linked to the other two.


7.3.1.3 How Absence Fields Are Mapped for Colombia

Country/region-specific field mapping is used for replication of linked sickness absences from Employee Central to the SAP ERP HCM system.

The table shows you the Colombia-specific fields for an employee's absence data in Employee Central and the equivalent fields in the Absences (2001) infotype in SAP ERP HCM.

Table 21: Colombia-Specific Field Mapping

Employee Central Time Off Field Description

SAP ERP HCM Infotype Infotype Field

Meaning of Infotype Field

countryExtensionCOL-identicalSicknessGroup

Employee time group that groups sickness absences to be treated as identical

2001 KENN1 (Indicator for Subsequent Illness)

Indicates whether sickness absences are logically related

NoteIf absences are linked by the KENN1 field, a corresponding entry in the LFZED (End of Continued Pay) field is generated. The LFZED field is evaluated when calculating the payroll.

The prerequisite required for this is that you’ve implemented either support package 34 of the SAP_HRCCO 608 software component version or SAP Note 2632928 .

7.3.2 Replication of Time Off Data for Germany

Replication of Germany-specific time off data enables payroll in SAP ERP HCM to process this data for German employees.

Continued Pay and Linking of Absences for Germany [page 81]

80 PUBLIC




Indicators for sickness absences that have been linked with one of the reasons Identical or Overlapping in Employee Central for German employees are replicated to the SAP ERP HCM system so that payroll can process them accordingly.

How Sickness Absences for Germany Are Linked in SAP ERP HCM [page 82]When linked sickness absences are replicated from Employee Central Time Management, they’re linked in the SAP ERP HCM system using a system-generated link index. Germany handles identical as well as overlapping sickness absences.

Replication of Exclusion Reasons for the Electronic Certificate of Incapacity for Work (eAU) in Germany [page 83]

Reasons to exclude absence records from electronic communication with public health insurance companies are replicated from Employee Central so that payroll in the SAP ERP HCM system can exclude these absence records from the communication.

Mapping Exclusion Reasons from Employee Central to Exclusion Reasons in SAP ERP HCM [page 84]Define customer-specific code values to map exclusion reasons for the electronic certificate of incapacity for work (eAU) from Employee Central to corresponding exclusion reasons in SAP ERP HCM.

How Absence Fields Are Mapped for Germany [page 86]Country/region-specific field mapping is used for replication of linked sickness absences and exclusion reasons for the electronic certificate of incapacity for work from Employee Central to the SAP ERP HCM system.

7.3.2.1 Continued Pay and Linking of Absences for Germany

Indicators for sickness absences that have been linked with one of the reasons Identical or Overlapping in Employee Central for German employees are replicated to the SAP ERP HCM system so that payroll can process them accordingly.

Employee Central groups together sickness records entered for country version Germany when they are linked for continued pay processing. According to the German regulation Continued Remuneration Act (Entgeltfortzahlungsgesetz), employees who fall sick are entitled to continue to be paid by their employer while they are incapable of working for a period of up to 6 weeks (42 calendar days). If the sickness is longer than 42 days, the employee receives payment from the health insurance. The HR admin can link sickness records if they are related, or not related but occur one after the other directly and fall within the same period of time (less than 6 months in between).

A related sickness absence is called identical sickness in Employee Central. In SAP ERP HCM this corresponds to a subsequent illness.

ExampleAn employee sends a sickness certificate for 10 days. Then he or she comes back and works for 2 weeks, and then he or she is sick again for a similar sickness and sends a new certificate for 20 days. In this case, according to the regulation from the health insurance, even though the employee has worked in between, sickness records that happen within 6 months shall be linked. The HR admin links them when creating the sick leaves for the employee. If the admin selects a Germany-specific time type with the Sickness absence class, he or she can select the reason Identical and then link the sick leaves accordingly.


Sickness absences that aren't necessarily related but occur one after the other directly are called overlapping sickness in Employee Central and repeated illness in SAP ERP HCM.

ExampleAn employee sends a sickness certificate for 20 days. Then a new certificate comes for the same sickness for another 22 days. In this case, the two absences can be linked because the two sickness records happen one after the other directly. So the employee receives 6 weeks his normal payment. After 6 weeks, the health insurance takes care. That's why the HR admin links the sick leaves for the employee. This is done in the same way as shown in the first case, but this time the admin selects the reason Overlapping and then links the sick leaves.

If Sickness absences are linked, an EmployeeTimeGroup object is generated automatically that groups them together in the background. An external code (a 32-characters UUID) is generated for the EmployeeTimeGroup object. This code is stored in the identicalSicknessGroup or the overlappingSicknessGroup field of the corresponding EmployeeTimeDEU object – depending on the linking reason the HR admin selected. The EmployeeTimeDEU object then has a <CountrySpecificFields> node with a <Name> and a <Value> attribute, as shown in this example:

Sample Code

<CountrySpecificFields> <Name>overlappingSicknessGroup</Name> <Value>be9874Dm936ji0764nBR2p6138jgn63T</Value> </CountrySpecificFields>

7.3.2.2 How Sickness Absences for Germany Are Linked in SAP ERP HCM

When linked sickness absences are replicated from Employee Central Time Management, they’re linked in the SAP ERP HCM system using a system-generated link index. Germany handles identical as well as overlapping sickness absences.



Example





lkh73562TdgBN8563tsjiRnFb78354tr

1

82 PUBLIC






93Uzd9375oU902Hie46nBmi39582Lp72

2

00627626 Repeated Illness (= Overlapping Sickness)

be9874Dm936ji0764nBR2p6138jgn63T

1

When the first sick leave is replicated for the employee with the personnel number 00627626, SAP ERP HCM, checks whether the Linking Index for Employee Time Groups table already contains an entry for this personnel number, linking reason, and EmployeeTimeGroup. Since this isn’t the case, it creates one, generating the linking index 1 (first row in the example above). Then it creates a record of the Absences infotype for this sick leave, storing the linking index it has generated, 1, in the KENN1 field of the infotype record.

When the next sick leave is transferred, SAP ERP HCM checks again whether the Linking Index for Employee Time Groups table contains an entry with the same personnel number, linking reason, and EmployeeTimeGroup. Since this is the case, it considers the sick leave to be linked with the first sick leave that was transferred for this employee. That's why SAP ERP HCM stores the same linking index, 1, in the KENN1 field when creating a record of the Absences infotype. Since both infotype records have the same entry in the KENN1 field, the SAP ERP HCM system knows that these two entries are linked and are to be handled together.


The next sick leave is transferred. This one has a different linking reason and a different EmployeeTimeGroup object assigned. That's why SAP ERP HCM generates a new linking index again (third row in the example). It's 1 again because it's the first entry with this combination of personnel number, linking reason, and EmployeeTimeGroup object. When creating the infotype record, SAP ERP HCM stores this linking index, 1, in the KENN2 field this time. Meaning, this infotype record isn’t linked to the other records created for this employee either.

7.3.2.3 Replication of Exclusion Reasons for the Electronic Certificate of Incapacity for Work (eAU) in Germany

Reasons to exclude absence records from electronic communication with public health insurance companies are replicated from Employee Central so that payroll in the SAP ERP HCM system can exclude these absence records from the communication.

The electronic certificate of incapacity for work (Elektronische Arbeitsunfähigkeitsbescheinigung, eAU) is used for the communication between employers and public health insurance companies in Germany. Payroll in the


SAP ERP HCM system retrieves the sickness certificate details electronically from the employee's public health insurance company using eAU communication.

But in certain cases, the sickness information is still transferred manually on paper. For example, when the employee received a sickness certificate from a private doctor or from a doctor abroad in a foreign country/region. In such cases, the Time Management administrator selects a corresponding exclusion reason (Ausschlussgrund), such as Private Doctor or Sickness in Foreign Country, for the sick leave absence record in Employee Central.

The EmployeeTimeDEU object in Employee Central then has a <CountrySpecificFields> node with a <Name> and a <Value> attribute, as shown in this example:

Sample Code

Sample Code

<CountrySpecificFields> <Name>electronicSicknessCertificateExclusionReason</Name> <Value>PRIVATE_DR</Value> </CountrySpecificFields>

In this example the Time Management administrator selected the exclusion reason Private Doctor. The corresponding picklist entry has the external code PRIVATE_DR.

The external code of the exclusion reason is replicated to the SAP ERP HCM system so that payroll can exclude the corresponding absence record from the eAU communication. SAP ERP HCM stores code of the exclusion reason in the Code for Description of Illness (UMSKD) field in the Absences (2001) infotype.


7.3.2.4 Mapping Exclusion Reasons from Employee Central to Exclusion Reasons in SAP ERP HCM

Define customer-specific code values to map exclusion reasons for the electronic certificate of incapacity for work (eAU) from Employee Central to corresponding exclusion reasons in SAP ERP HCM.

Context

Exclusion reasons are replicated from Employee Central Time Management to the Code for Description of Illness (UMSKD) field of the Absences (2001) infotype in the SAP ERP HCM system. The SAP ERP HCM code for the exclusion reason is limited to 6 characters. If you don't map the codes for exclusion reasons and a code is transferred from Employee Central, the SAP ERP HCM system tries to use the Employee Central code. SAP ERP HCM is able to use the Employee Central code if it isn't longer than 6 characters. If the code is longer, the SAP ERP HCM system raises an error message.

84 PUBLIC






Procedure

1. Go to Customizing for Personnel Management and choose Integration with SuccessFactors Employee Central Other Integration Settings Replicating Data from SuccessFactors to SAP ERP Assignment of Code Values .

2. Optional: Go to the Define Standard Code Value Lists activity to check the list ID defined for the eAU exclusion reason.

Table 23: List ID for eAU Exclusion Reason

Code List ID Code List ID Text

93001 Employee Time eAU Exclusion Reason - DE

3. Optional: Go to the Define Country Dependency of Code Value Lists activity and check the GDT name and ISO code assigned to the list ID.

Table 24: Country/Region Dependency for eAU Exclusion Reason

GDT Name ISO CodeModificator List ID End Date Start Date Code List ID

List Version ID

List Agency ID

EE_TIME_EAU_EXCLUSION_REASON

DE 31.12.9999 01.01.1800 93001 310

4. Go to the Define Mapping Code Value Lists step.5. Enter the following information for all exclusion reasons that you want to map:

○ GDT Name: EE_TIME_EAU_EXCLUSION_REASON○ Code List ID: 93001○ List Agency ID: 310

6. Enter the external codes of the exclusion reasons from Employee Central in the GDT Code Value field.7. Enter the corresponding codes from SAP ERP HCM in the ERP Key field.

Table 25: Example: Code Value Mapping for eAU Exclusion Reason

GDT Name Code List ID List Version ID List Agency ID GDT Code Value ERP Key


93001 310 PRIVATE_DR PRIVAT




GDT Name Code List ID List Version ID List Agency ID GDT Code Value ERP Key


93001 310 FOREIGN_DR AUSL

In this example, the exclusion reason PRIVAT is stored in the Code for Description of Illness (UMSKD) field of the Absences infotype in SAP ERP HCM when the employee received a sickness certificate from a private doctor. The exclusion reason AUSL is stored there when the employee received a sickness certificate from a doctor abroad.

7.3.2.5 How Absence Fields Are Mapped for Germany

Country/region-specific field mapping is used for replication of linked sickness absences and exclusion reasons for the electronic certificate of incapacity for work from Employee Central to the SAP ERP HCM system.

The table shows the Germany-specific fields for an employee's absence data in Employee Central and the equivalent fields in the Absences (2001) infotype in SAP ERP HCM.

Table 26: Germany-Specific Field Mapping




countryExtensionDEU-sicknessCertificateStartDate

Certified Start Date of Sickness

2001 KBBEG (Certified Start of Sickness)

The start date of the sickness as certified by the health insurance fund

countryExtensionDEU-paySupplementStartDate

Start Date of Sick Pay Supplement

2001 RMDDA (Date on Which Illness Was Confirmed)

The date of the day when the employer pays a sick pay supplement. Typically it’s the date of the day after the end of continued pay. The employer only pays a sick pay supplement if the sick pay is paid by the health insurance fund

countryExtensionDEU-continuedPayCreditedDays

Days credited for continued pay

2001 ANRTG (Days Credited for Continued Pay)

Value in this field indicates the number of days off due to previous or repeated sickness

86 PUBLIC






countryExtensionDEU-paySupplementEndDate

End Date of Sick Pay Supplement

2001 KRGED (End of Sick Pay)

The date up to which a sick pay supplement is paid

countryExtensionDEU-continuedPayEndDate

Date up to and including which continued pay is being made

2001 LFZED (End of Continued Pay)

countryExtensionDEU-identicalSicknessGroup

Employee time group that groups sickness absences to be treated as identicalThe employee receives continued pay up to and including this date.



countryExtensionDEU-overlappingSicknessGroup

Employee time group that groups sickness absences for which the period of absence overlaps with an absence for another reason, such as a different sickness

2001 KENN2 (Indicator for Repeated Illness)

Indicates whether sickness records follow on directly from one another

countryExtensionDEU-electronicSicknessCertificateExclusionReason

External code of the reason to exclude an absence from requesting the electronic certificate of incapacity for work (eAU)

2001 UMSKD (Code for Description of Illness)

Holds the codes of exclusion reasons in SAP ERP HCM







7.3.3 Replication of Time Off Data for Mexico

Replication of Time Off data for Mexico enables payroll in SAP ERP HCM to process continued pay for Mexican employees.

Indicators for sickness absences that have been linked with the reason Identical in Employee Central for Mexican employees are replicated to the SAP ERP HCM system, together with some additional information such as the reference number and the number of days already cumulated for the same sickness.

Continued Pay and Linking of Absences for Mexico [page 88]Employee Central groups together sickness records entered for country version Mexico when they are linked for continued pay processing.

Replication of Linked Absences for Mexico to SAP ERP HCM [page 89]When linked sickness absences are replicated from Employee Central Time Off, they’re linked in the SAP ERP HCM system using a system-generated link index. Mexico handles identical sickness absences.

How Absence Fields Are Mapped for Mexico [page 90]Country/region-specific field mapping is used for replication of linked sickness absences from Employee Central to the SAP ERP HCM system.

Related Information

Checking the Minimum Setup Required for Your Systems [page 14]

7.3.3.1 Continued Pay and Linking of Absences for Mexico

Employee Central groups together sickness records entered for country version Mexico when they are linked for continued pay processing.

For Mexico, the HR admin can link sickness records if they are related. A related sickness absence is called identical sickness in Employee Central. In SAP ERP HCM this corresponds to a subsequent illness.

ExampleAn employee has an illness or accident for the first time. Then he or she comes back to work. After some time, the employee has another illness or accident that is related to the first one. In this case, sickness records shall be linked even though the employee has worked in between. The HR admin links them when creating the sick leaves for the employee. If the admin selects a Mexico-specific time type with the Sickness absence class, he or she can select the reason Identical and enter the reference number provided by the Social Security Institute. Then the admin can link the sick leaves.

If sick leaves are linked, an EmployeeTimeGroup object is generated automatically that groups them together in the background. An external code (a 32-characters UUID) is generated for the EmployeeTimeGroup object. This code is stored in the identicalSicknessGroup field of the corresponding EmployeeTimeMEX object. The

88 PUBLIC



EmployeeTimeMEX object then has a <CountrySpecificFields> node with a <Name> and a <Value> attribute, as shown in this example:

Sample Code

<CountrySpecificFields> <Name>identicalSicknessGroup</Name> <Value>258ZzRet9867hUpnF085527GirhN9783</Value> </CountrySpecificFields>


7.3.3.2 Replication of Linked Absences for Mexico to SAP ERP HCM

When linked sickness absences are replicated from Employee Central Time Off, they’re linked in the SAP ERP HCM system using a system-generated link index. Mexico handles identical sickness absences.



Example





258ZzRet9867hUpnF085527GirhN9783

1


ouKTre56294246Per746Nm93627LZk83

2

When the first sick leave is replicated for the employee with the personnel number 00482236, SAP ERP HCM checks whether the Linking Index for Employee Time Groups table already contains an entry for this personnel number, linking reason, and EmployeeTimeGroup. Since this isn’t the case, it creates one, generating the linking index 1 (first row in the example above). Then it creates a record of the Absences infotype for this sick leave, storing the linking index it has generated, 1, in the KENN1 field of the infotype record.

When the next sick leave is transferred, SAP ERP HCM checks again whether the Linking Index for Employee Time Groups table contains an entry with the same personnel number, linking reason, and EmployeeTimeGroup. Since this is the case, it considers the sick leave to be linked with the first sick leave that was transferred for this employee. That's why SAP ERP HCM stores the same linking index, 1, in the


KENN1 field when creating a record of the Absences infotype. Since both infotype records have the same linking index, the SAP ERP HCM system knows that these two infotype records are linked and are to be handled together.


7.3.3.3 How Absence Fields Are Mapped for Mexico


The table shows the Mexico-specific fields for an employee's absence data in Employee Central and the equivalent fields in the Absences (2001) infotype in SAP ERP HCM.

Table 28: Mexico-Specific Field Mapping




countryExtensionMEX-identicalSicknessGroup




countryExtensionMEX-referenceNumber

Reference number 2001 REFNR (Reference Number)

This should be the reference number you've received from the Social Security Institute. It can be up to 8 characters long. (Make sure the maximum length of this field in Employee Central is 8 or less characters.)

90 PUBLIC






countryExtensionMEX-daysAlreadyCumulatedForSameSickness

Days already cumulated for same sickness

2001 ANRTG (Days Credited for Continued Pay)

Value in this field indicates the number of days off due to previous or repeated sickness. That is, incapacity days for the same absence event, which are stored in previous absence records.

NoteSAP Note 2581802 (or a support package containing this SAP Note) needs to be installed in your SAP ERP HCM to replicate this field.

7.3.4 Replication of Time Off Data for Spain

Replication of Time Off data for Spain enables payroll in SAP ERP HCM to process continued pay for Spanish employees.

Indicators for sickness absences that have been linked with the reason Identical in Employee Central for Spanish employees are replicated to the SAP ERP HCM system, together with the indicator for the original sickness absence.

Continued Pay and Linking of Absences for Spain [page 92]Employee Central groups together sickness records entered for country version Spain when they are linked for continued pay processing.

Replication of Linked Absences for Spain to SAP ERP HCM [page 93]When linked sickness absences are replicated from Employee Central Time Off, they’re linked in the SAP ERP HCM system using a system-generated link index. Spain handles identical sickness absences.

How Absence Fields Are Mapped for Spain [page 94]Country/region-specific field mapping is used for replication of linked sickness absences from Employee Central to the SAP ERP HCM system.



7.3.4.1 Continued Pay and Linking of Absences for Spain

Employee Central groups together sickness records entered for country version Spain when they are linked for continued pay processing.

The HR admin can link sickness records if they are related. The admin can also identify which sickness absence in a series of linked absences is the original one. By default, the absence with the earliest validity start date is identified as the original absence. It is also possible to change which absence is treated as the original absence.

A related sickness absence is called identical sickness in Employee Central. In SAP ERP HCM this corresponds to a subsequent illness.

ExampleAn employee sends a sickness certificate for 10 days. Then he or she comes back and works for 2 weeks. Then the employee falls sick again with a similar sickness and sends a new certificate for 20 days. In this case, according to the regulation from the health insurance, even though the employee has worked in between, sickness records shall be linked. The HR admin links them when creating the sick leaves for the employee. If the admin selects a Spain-specific time type with the Sickness absence class, he or she can select the reason Identical, link the sick leaves accordingly, and identify one of them as the original absence.

If sick leaves are linked, an EmployeeTimeGroup object is generated automatically that groups them together in the background. An external code (a 32-characters UUID) is generated for the EmployeeTimeGroup object. This code is stored in the identicalSicknessGroup field of the corresponding EmployeeTimeESP object. The originalAbsence field of the EmployeeTimeESP object is also updated. The EmployeeTimeESP object then has two <CountrySpecificFields> nodes with a <Name> and a <Value> attribute each, as shown in this example:

Sample Code

<CountrySpecificFields> <Name>originalAbsence</Name> <Value>true</Value></CountrySpecificFields><CountrySpecificFields> <Name>identicalSicknessGroup</Name> <Value>834OzRet9837hUpnF073527KirhN9783</Value> </CountrySpecificFields>


92 PUBLIC



7.3.4.2 Replication of Linked Absences for Spain to SAP ERP HCM

When linked sickness absences are replicated from Employee Central Time Off, they’re linked in the SAP ERP HCM system using a system-generated link index. Spain handles identical sickness absences.


Example





834OzRet9837hUpnF073527KirhN9783

1


ouHTre56285746Uer746Nm93627LOk83

2

When the first sick leave is replicated for the employee with the personnel number 00827628, SAP ERP HCM checks whether the Linking Index for Employee Time Groups table already contains an entry for this personnel number, linking reason, and EmployeeTimeGroup. Since this isn’t the case, it creates one, generating the linking index 1 (first row in the example above). Then it creates a record of the Absences infotype for this sick leave. The sick leave is identified as the original one in Employee Central, meaning, the originalAbsence indicator of the EmployeeTimeESP object is set to true. That's why SAP ERP HCM stores the linking index it has generated, 1, in the KENN1 field of the infotype record.

When the next sick leave is transferred, SAP ERP HCM checks again whether the Linking Index for Employee Time Groups table contains an entry with the same personnel number, linking reason, and EmployeeTimeGroup. Since this is the case, it considers the sick leave to be linked with the first sick leave that was transferred for this employee. But this sick leave isn’t identified as the original one in Employee Central. Meaning, the originalAbsence indicator is set to false this time. That's why SAP ERP HCM uses the same linking index, 1, when creating a record of the Absences infotype. But this time it stores it in the KENN2 field. Since both infotype records have the same linking index, stored in the KENN1 field for the original absence and in the KENN2 field for the related absence, the SAP ERP HCM system knows that these two infotype records are linked and are to be handled together, and which of the sickness absences is the original one.

Then the next sick leave is transferred for the same employee. Again, SAP ERP HCM checks whether the Linking Index for Employee Time Groups table contains an entry with the same personnel number, linking reason, and EmployeeTimeGroup code. This time, personnel number and linking reason are the same, but a different EmployeeTimeGroup object is assigned. That's why SAP ERP HCM generates a new linking index, 2 (second row in the example). Again the sick leave is identified as the original one in Employee Central, so SAP ERP HCM stores the linking index in the KENN1 field of the infotype record. Since the linking index differs from the one stored in the first two infotype records created for this employee, this new record is considered not to be linked to the other two.


7.3.4.3 How Absence Fields Are Mapped for Spain


The table shows the Spain-specific fields for an employee's absence data in Employee Central and the equivalent fields in the Absences (2001) infotype in SAP ERP HCM.

Table 30: Spain-Specific Field Mapping




countryExtensionESP-identicalSicknessGroup


2001 KENN1 if countryExtensionESP-originalAbsence is true

KENN2 if countryExtensionESP-originalAbsence is false

The KENN1 field indicates that this sickness absence is logically related to others and that it’s the original one in a series of linked absences

The KENN2 field indicates that this sickness absence is logically related to others and that it isn’t the original one

94 PUBLIC



8 You're done! What's Next?

You've set up employee time data replication from Employee Central – now go through the follow-up steps.

Monitoring of Employee Time Data Replication [page 95]You can use monitoring tools in Employee Central and in the SAP ERP HCM system to check employee time data replication.

How to Avoid Unnecessary Time Data Replication [page 97]To avoid unnecessary replication of Time Off and Time Sheet data especially in test systems because configuration errors are not corrected, replication is automatically rescheduled.

How to Trigger Replication of Existing Absences or Time Sheets [page 97]How you can replicate absences or time sheets from Employee Central to SAP ERP HCM that weren't replicated before you set up the integration.

Deleting Inconsistent Employee Time Data in SAP ERP HCM [page 98]Use a clean-up tool in SAP ERP HCM to repair data inconsistencies that may have been caused by replication of employee time data from Employee Central.

HTTPS Connectivity [page 100]Use the ICM Monitor (SMICM) transaction to ensure that HTTPS connectivity is activated in your SAP ERP HCM system.

Performance Optimization of This Integration [page 100]Here are some best practices to help you improve the performance of employee time data replication.

Handling of Data Purge in the Replication [page 101]Look at how the purge of data is handled in the replication from Employee Central to the SAP ERP HCM system.

8.1 Monitoring of Employee Time Data Replication

You can use monitoring tools in Employee Central and in the SAP ERP HCM system to check employee time data replication.

Employee Central Data Replication Monitor [page 96]Employee Central provides an admin tool for monitoring data replication to the SAP ERP HCM system.

Monitoring Tools in the SAP ERP HCM System: Web Service Utilities and Application Log [page 96]Two monitoring tools in the SAP ERP HCM system will help you identify errors that occur during the replication of employee time data.

Replicating Employee Time Data from Employee Central to SAP ERP HCM Using SAP Cloud Integration as the MiddlewareYou're done! What's Next? PUBLIC 95

8.1.1 Employee Central Data Replication Monitor

Employee Central provides an admin tool for monitoring data replication to the SAP ERP HCM system.

The integration processes update the status in the Employee Central Data Replication Monitor by sending notifications and confirmations. Use the Data Replication Monitor to check the replication status, view alerts, and analyze error messages related to data replication from Employee Central to SAP ERP HCM. For more information, refer to the Employee Central Data Replication Monitor administration guide.

8.1.2 Monitoring Tools in the SAP ERP HCM System: Web Service Utilities and Application Log

Two monitoring tools in the SAP ERP HCM system will help you identify errors that occur during the replication of employee time data.

The SAP ERP HCM monitoring tools cover different stages of the replication process:

Web Service Utilities: Error Log

Replication messages are first received by the Web Service Framework. Here the system performs a technical check on the compliance of the received message with the XML schema required by the inbound service interface. The error log in the Web Service Utilities (SRTUTIL) transaction shows errors that come up in this check. Use interface name II_TIM_SFEC_II_EETME_ELMNTS_RQ to narrow the search in the Re-select dialog, if necessary. Erroneous messages are not further processed.

Application Log

Correct messages are passed on to the application logic that maps the data to the structures of the SAP ERP HCM employee infotypes and performs the updates on the SAP ERP HCM time data records. Numerous checks are performed here. Examples of errors are unknown code values, missing mandatory field data, or editing locks if records are currently being edited by another user. These errors can be monitored in the Application Log (SLG1) transaction.

Make these entries on the Application Log selection screen:

● In the Object field, enter PAOC_SFI_PA.● In the Subobject field, enter EE_TIME.● To search for all employments of an employee, enter the External ID and asterisk (*).● To search for a specific employment per employee, enter the External ID and User ID in that order

separated by a slash (/).

96 PUBLIC


You're done! What's Next?

https://help.sap.com/viewer/cf468e8b48d442dea461979849923972

Web Service Utilities: Message Monitor

Often it may be useful to look in detail at the data of the replication message to better understand why an error has occurred. This can be done in the message monitor of the Web Service Utilities transaction. On the selection screen enter EmployeeTimeECToERPRequest_In for the input field Interface Name at the bottom of the screen and choose appropriate entries for the timestamp fields. Here every received replication message is logged. By double clicking on a message its content can be displayed. It can also be displayed as an XML.

8.2 How to Avoid Unnecessary Time Data Replication

To avoid unnecessary replication of Time Off and Time Sheet data especially in test systems because configuration errors are not corrected, replication is automatically rescheduled.

If the replication per employment and replication content type fails 100 times, the next replication is automatically rescheduled one hour later. Later on, the replication is restarted 24 times per day to replicate the time data again. If the replication fails again, the data is replicated only once a day (101-125 times failed: 1 replication per hour; more than 125 times failed: 1 replication per day).

To return to the replication frequency of the employment and the replication content type as previously scheduled, you can choose one of these options:

● Resend the employment in the Employee Central Data Replication Monitor.● Create or update a time object for this employment and replication content type in Employee Central to

reset the replication frequency. Do it for all time data not replicated so far that belongs to the same replication content type and the relevant employment.

● Trigger a proxy creation job at the Data Replication Configuration. Be aware that this action applies to all time objects corresponding to this configuration and not only to a given employment.

8.3 How to Trigger Replication of Existing Absences or Time Sheets

How you can replicate absences or time sheets from Employee Central to SAP ERP HCM that weren't replicated before you set up the integration.

To replicate existing absences, proceed as described in How to Trigger Replication of Existing Absences in the guide Employee Central Time Off and Employee Central Payroll.

To replicate existing time sheets, proceed as described in How to Trigger Replication of Existing Time Sheets in the guide Employee Central Time Sheet and Employee Central Payroll.


https://help.sap.com/viewer/0377d826832f445e82d09fdac7228f34/latest/en-US/862ef46286a64b029fab90f96964e372.html

https://help.sap.com/viewer/542d82a01af34800a7d947ae15906197/latest/en-US/533b7cbf2a314197a6dbfc451d5295fa.html

8.4 Deleting Inconsistent Employee Time Data in SAP ERP HCM

Use a clean-up tool in SAP ERP HCM to repair data inconsistencies that may have been caused by replication of employee time data from Employee Central.

Prerequisites

In addition to the authorization for transaction ECTIM_CLEANUP_DB itself, the user who does the clean-up needs to have the change authorization for the PAOCFEC_REFMAP table.

Context

Time data replication creates records of the Absences (2001) and Employee Remuneration Info (2010) infotypes in the SAP ERP HCM system, which must not be changed manually. If an admin tries to change such an infotype record, the Maintain HR Master Data (PA30) transaction shows the warning that this infotype record was created by an external application (which means Employee Central here). In case the admin ignores or overlooks this warning and changes the infotype record nevertheless, this can lead to data inconsistencies.

Data inconsistencies can also result from testing (for example, if you trigger an XML message again that was already processed).

You can clean up such inconsistencies using the Clean-Up of Employee Time Data Replicated from Employee Central program (transaction ECTIM_CLEANUP_DB). The program repairs inconsistencies between the following tables:

● HR Time Record: Infotype 2001 (Absences) (PA2001) or HR Time Record: Infotype 2010 (Employee Remuneration Info) (PA2010) and Reference Key Mapping (PAOCFEC_REFMAP)PA2001 and PA2010 store the SAP ERP HCM infotype data. PAOCFEC_REFMAP stores the mapping information between the Employee Time object from Employee Central and the corresponding SAP ERP HCM infotype record.The program makes sure that the data is consistent in both tables. That is, it removes all entries that have no valid counterpart in the respective other table.

● HR Time Record: Infotype 2001 (Absences) (PA2001) and Linking Index for Employee Time Groups (ECTIM_LINK_INDEX)ECTIM_LINK_INDEX is filled when sickness absences that were linked by an admin in Employee Central Time Off because they’re identical or overlapping are replicated to the SAP ERP HCM system. The SAP ERP HCM system then generates a link index and stores it in the ECTIM_LINK_INDEX table and also in the Absences (2001) infotype.The program removes link indices from the ECTIM_LINK_INDEX table that are no longer used in an Absences infotype record.

98 PUBLIC



Procedure

1. Go to the Clean-Up of Employee Time Data Replicated from Employee Central (ECTIM_CLEANUP_DB) transaction in your SAP ERP HCM system.

2. Specify from which date on the tables are to be cleaned up. This program then deletes data that has an end date after or on this date. After a successful clean-up, a new replication from Employee Central that uses the same date will restore the data as it was before.

3. Choose a clean-up option:○ You can delete inconsistent entries. Deleting inconsistent entries means that data is removed from

either PA2001 or PA2010 (depending on your infotype selection) and PAOCFEC_REFMAP that doesn't have a valid counterpart in the respective other table and is after the clean-up date. Data is removed in these cases:○ Entries are missing in one of the tables.○ Entries exist in both tables, but have different keys.

Use this option when you’re already running employee time data replication productively.○ You can delete all entries. Deleting all entries means that all data is removed from both tables (PA2001

and PAOCFEC_REFMAP or PA2010 and PAOCFEC_REFMAP respectively) that is after the clean-up date.Use this mode when you aren't running employee time data replication productively yet.

If you select the Absences option in the next step, the program also removes link indices from the ECTIM_LINK_INDEX table that are no longer used in an Absences infotype record. This is regardless of whether you select Delete Inconsistent Entries or Delete All Entries.

4. Choose the infotype you want to clean up:○ Absences (2001)

In this case the program compares and cleans up the tables PA2001 and PAOCFEC_REFMAP, and it also cleans up ECTIM_LINK_INDEX.

○ Employee Remuneration Info (2010)In this case, the program compares and cleans up the tables PA2010 and PAOCFEC_REFMAP.

5. When deleting inconsistent entries, make additional settings.

If you’ve selected the Delete Inconsistent Entries option, you can restrict processing to a specific set of data, using these options:

○ You can restrict the clean-up to one or more specific employees. This restriction also applies to cleaning up the ECTIM_LINK_INDEX table.

○ If you've selected the Absences infotype, you can restrict the clean-up to one or more absence types, such as Leave or Illness.

○ If you've selected the Employee Remuneration Info infotype, you can restrict the clean-up to one or more time wage types, such as Paid Absences.

Next Steps

For detailed information about this program settings and result, see the program documentation in your SAP ERP HCM system.


Related Information

Granting SAP ERP HCM Permissions for Employee Time Data Replication [page 21]

8.5 HTTPS Connectivity

Use the ICM Monitor (SMICM) transaction to ensure that HTTPS connectivity is activated in your SAP ERP HCM system.

8.6 Performance Optimization of This Integration

Here are some best practices to help you improve the performance of employee time data replication.

The replication of employee time data is scheduled in the middleware. The middleware requests data from Employee Central and sends it to SAP ERP HCM. Some recommendations for improving the performance of employee time data replication are:

Parallelization

You could parallelize the replication of employee time data by deploying the integration process multiple times in the middleware and defining appropriate selection parameters to make sure that each of these process instances transfers a different set of data. But since the middleware sends the data asynchronously to SAP ERP HCM, rather the SAP ERP HCM system than the middleware is the limiting factor. This means, parallelization wouldn’t improve the performance significantly. That’s why we don’t recommend parallelizing employee time data replication processes.

Scheduling

We don’t recommend trying to achieve a real-time integration by using very short replication cycles (such as replicating every minute).

If you use multiple Employee Central–SAP ERP HCM integrations, we recommend scheduling them with the same interval, but with different timelines to avoid multiple replication processes running at the same point in time.

100 PUBLIC



Confirmation and Logging

If you haven’t enabled the Business Integration Builder (BIB) mode in your SAP ERP HCM system for employee master data, employee organizational assignment, or organizational object replication, you can disable confirmations being sent from SAP ERP HCM to Employee Central during initial load. You can turn confirmations back on when initial load is finished and you switch to delta replication. To turn off confirmations, leave the value of the YSFEC / YRESP switch in table T77S0 blank. Even with confirmations being disabled, you can analyze errors occurring during initial load using the application log in the SAP ERP HCM system.

If you’ve enabled the BIB mode in your SAP ERP HCM system, the confirmation is turned on by default for employee time data replication. You can't turn it off in this case.

We recommend that you disable payload logging in the middleware. Only enable payload logging if an issue occurs in employee time data replication, to be able to analyze the problem.

General Recommendations

Check your firewall and your proxy for restrictions regarding the maximum package size. If necessary, adjust the firewall and proxy settings or the package size of your integration accordingly.

Disable integration processes you no longer use.

Latest when switching from your development and test environment to your productive environment, disable any integrations that you’ve set up for development and test purposes. Only trigger them on demand.

Check whether an integration really needs to run around the clock. Maybe for some types of data it is sufficient to replicate only from time to time. You can increase the time interval for the affected processes to replicate this data less frequently.

If the integration runs into an error, stop the scheduler. It doesn’t make sense to continue a replication that constantly generates error messages. This just jams the logs and makes error analysis more difficult.

Related Information

Enabling Creation of the Confirmation Message [page 34]

8.7 Handling of Data Purge in the Replication

Look at how the purge of data is handled in the replication from Employee Central to the SAP ERP HCM system.

Purging data in SAP ERP HCM is independent of purging data in Employee Central. Each system has its own business reasons for keeping or purging data, and retention times can differ in both systems. That's why you decide for each system what data is to be purged.


ExampleYou might purge an employee's address in Employee Central. But the address can still be required in SAP ERP HCM for specific processes such as payroll.

If you purge data in Employee Central, this information isn’t replicated to the SAP ERP HCM system automatically. If you want to purge the same data on the SAP ERP HCM side, you need to trigger this purge in addition.

The guiding principle is that unwanted data deletion in SAP ERP HCM must be prevented. That is, Employee Central and SAP ERP HCM aren't kept in sync regarding data purge.

NotePurging data isn’t the same as deleting data. While it’s often possible to "undelete" data and recover the deleted record, a data purge is permanent and the purged records are irrevocably removed.

Purge of Employee Time Data Replicated to SAP ERP HCM [page 102]Some things you should know about purging employee time data in the SAP ERP HCM system, and how to trigger a purge run.

Purge of Application Logs in SAP ERP HCM [page 105]Purge application logs in the SAP ERP HCM system that you no longer need.

8.7.1 Purge of Employee Time Data Replicated to SAP ERP HCM

Some things you should know about purging employee time data in the SAP ERP HCM system, and how to trigger a purge run.

What You Should Know About Data Purge

If employee time data records are purged in Employee Central, no data replication proxies are created for the purged data. Preventing the creation of data replication proxies ensures that purged employee time data isn’t replicated to the SAP ERP HCM system. This is the default setup, there's no need for you to configure anything in Employee Central.

The following restriction currently applies to data purge in Employee Central:

NotePlease note that, in the current release, this function is fully available in test and preview environments only. You can set it up and test it, but unfortunately you won’t be able to work with any live data in a productive environment just yet. The function will be available productively in a future release.

102 PUBLIC



How to Purge Employee Time Data

To purge employee time data in SAP ERP HCM, use the default tools provided there:

● Using the corresponding archiving object in the Archive Administration (SARA) transaction, you can destroy employee time data in SAP ERP HCM.For more information, see Destroying Time Management Data (PT).

● Using the program Destruction of Personnel Numbers in Live Systems (RPUDELPP) or the Delete Personal Data (PU00) transaction, you can destroy personnel numbers and the related infotype records – which includes employee time-related infotype records.

NoteIn non-productive systems, use the program Delete Personnel Numbers Completely (RPUDELPN) instead of the RPUDELPP program.

For more information, see Destruction of Personnel Numbers in the application help for SAP ERP HCM.

What Other Data Is Purged

In both cases the following additional data needs to be purged:

● Data stored in the Reference Key Mapping (PAOCFEC_REFMAP) tableThis table stores the mapping information between the Employee Time object from Employee Central and the corresponding infotype record in SAP ERP HCM. It must always be in sync with the HR Time Record: Infotype 2001 (Absences) (PA2001) and HR Time Record: Infotype 2010 (Employee Remuneration Info) (PA2010) tables.

TipIn case data inconsistencies occur between the PAOCFEC_REFMAP table and table PA2001 or PA2010, you can also use the Clean-Up of Employee Time Data Replicated from Employee Central (ECTIM_CLEANUP_REFMAP_INFTY_TAB) program to clean them up.

● Data stored in the Linking Index for Employee Time Groups (ECTIM_LINK_INDEX) tableThis table stores link indices for identical or overlapping sickness absences, which are linked in Employee Central Time Off and replicated to the SAP ERP HCM system.


https://help.sap.com/viewer/79bf89044e8e484fabad18711260f13a/latest/en-US/155cb1954a954fb8a7604b1d7f959a19.html

https://help.sap.com/viewer/d3bc4479e3344626be836c03a5c6962f/latest/en-US/ec6aa852c8296028e10000000a441470.html

We provide Business Add-In (BAdI) implementations, which delete the relevant data from these tables:

Table 31: BAdI Implementations for Deleting Employee Time Data

If you delete employee time data using...

The system calls this implementation... Of this BAdI definition... What's good to know...

Archive Administration (transaction SARA)

EC Time Integration BLP-Save: Delete Refmap/Link-Index (ECTIM_PT_BLP_SAV)

Enhance Business Logic for Time Data (PT_BLP_USER)

By default, this BAdI implementation isn’t called. We strongly recommend that you activate it. To do this, you have two options, depending on whether you’ve already implemented the Enhance Business Logic for Time Data (PT_BLP_USER) BAdI or not:

● If you haven’t implemented the PT_BLP_USER BAdI yet, activate this implementation. To do so:1. Go to transaction

SE19.

2. In the Classic BAdI Implementation field, enter ECTIM_PT_BLP_SAV and choose Change.

3. Choose Activate Business Add-In Implementation.

● If you’ve already implemented the PT_BLP_USER BAdI, don't activate the implementation. Instead, add the PROCESS_DATA method of the implementing class CL_IM_ECTIM_PT_BLP_SAV in your customer-specific implementation for the SAV time point.

104 PUBLIC



If you delete employee time data using...

The system calls this implementation... Of this BAdI definition... What's good to know...

Delete Personnel Numbers Completely (program RPUDELPN) or Delete Personal Data (transaction PU00)

Delete EE Time Key Mapping Record for Given Pers. Number (TIM_SFEC_DEL_PERNR)

BAdI for Reports Deleting Personnel Numbers (HRPAYXX_DELETE_PERNR)

This BAdI implementation is called by default

Related Information

Replication of Time Off Data for Germany [page 80]Replication of Time Off Data for Mexico [page 88]Replication of Time Off Data for Spain [page 91]

8.7.2 Purge of Application Logs in SAP ERP HCM

Purge application logs in the SAP ERP HCM system that you no longer need.

What Data Can Be Purged

Data replication between Employee Central and SAP ERP HCM uses the following objects when writing messages to the application log:

● Combined employee master data and organizational assignments replication from Employee Central to SAP ERP HCM:Object ECPAO_IN with subobjects:○ GEN for generic messages○ EE for employee master data○ VERBOSE for the Verbose message log

● Employee master data replication from Employee Central to SAP ERP HCM:Object PAOC_SFI_PA with subobject EE

● Organizational data or organizational objects replication from Employee Central to SAP ERP HCM:Object PAOC_SFI_OM with subobjects:○ REPL_REQ_PROCESSING for the log created by the replication to the SAP ERP HCM system○ REPL_REQ_PROXY for the log created when processing the inbound message in SAP ERP HCM

● Employee time data replication from Employee Central to SAP ERP HCM:Object PAOC_SFI_PA with subobject EE_TIME


How to Purge Data

Use the BC_SBAL archiving object in the Archive Administration (SARA) transaction to delete these application logs in SAP ERP HCM if you no longer need them. The archiving object calls the SBAL_ARCHIVE_DELETE program, which deletes the data from the archived logs from the original tables.

On the selection screen of the SBAL_ARCHIVE_DELETE program, enter the following data:

● Object and Subobject: Select all application log objects and subobjects whose logs you want to delete● From (Date/Time): To delete all logs, enter 18000101● To (Date/Time): Enter the latest possible date, keeping in mind that only the logs written after that date will

still be available in SAP ERP HCM

For more information, see Archiving Object BC_SBAL in the SAP NetWeaver documentation.

106 PUBLIC



https://help.sap.com/viewer/addb96cd90c945dfb3182865363bbc47/latest/en-US/4e4a2209872c3b0fe10000000a42189e.html

Important Disclaimers and Legal Information

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

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

● The content of the linked-to site is not SAP documentation. You may not infer any product claims against SAP based on this information.● SAP does not agree or disagree with the content on the linked-to site, nor does SAP warrant the availability and correctness. SAP shall not be liable for any

damages caused by the use of such content unless damages have been caused by SAP's gross negligence or willful misconduct.

● Links with the icon : You are leaving the documentation for that particular SAP product or service and are entering a SAP-hosted Web site. By using such links, you agree that (unless expressly stated otherwise in your agreements with SAP) you may not infer any product claims against SAP based on this information.

Videos Hosted on External PlatformsSome videos may point to third-party video hosting platforms. SAP cannot guarantee the future availability of videos stored on these platforms. Furthermore, any advertisements or other content hosted on these platforms (for example, suggested videos or by navigating to other videos hosted on the same site), are not within the control or responsibility of SAP.

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

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

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

Replicating Employee Time Data from Employee Central to SAP ERP HCM Using SAP Cloud Integration as the MiddlewareImportant Disclaimers and Legal Information PUBLIC 107

www.sap.com/contactsap

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

No part of this publication may be reproduced or transmitted in any form or for any purpose without the express permission of SAP SE or an SAP affiliate company. The information contained herein may be changed without prior notice.

Some software products marketed by SAP SE and its distributors contain proprietary software components of other software vendors. National product specifications may vary.

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

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

Please see https://www.sap.com/about/legal/trademark.html for additional trademark information and notices.

THE BEST RUN

https://www.sap.com/about/legal/trademark.html

Documents

Replicating Employee Time Data from ... - help.sap.com