SF EC TimeSheet ECPay PTP
SF EC TimeSheet ECPay PTP
4 Terminology. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9
7 Setting up Permissions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 19
7.1 Granting Permissions to API User. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 19
7.2 Granting Permissions for the Data Replication Configuration. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 20
This document describes changes to this guide for the recent releases.
Q2 2019
New checks added We've added new checks to the Data Using Checks for Data Replication Appli
Replication Application of the Check Tool. cation [page 42]
Q1 2019
Limitation added Make sure that your external codes for Make Sure that External Codes Aren't
time objects do not exceed 32 charac Longer Than 32 Characters [page 29]
ters.
Added information to the Replication of We've added information on how to han Replication of Employee Time Valuation
Time Sheet dle absences if an employee has two Result to Employee Central Payroll - Sce
PERNRs due to an employment change, nario Overview [page 12]
for example, a global assignment
Q4 2018
November, 16
Added information We've added information about the post Replication of Employee Time Valuation
ing target for time valuation result. Result to Employee Central Payroll - Sce
nario Overview [page 12]
September, 15
August, 15
New note on the date format We've illustrated how the data format de Data Replication Configuration for Time
Sheet Replication [page 27]
pends on the logon language.
New note on an improved logic to avoid We've added a note describing this logic Scheduling the Replication of Time Data
[page 34]
unnecessary replication of time sheets in detail.
especially in test systems because con
figuration errors are not corrected.
Please go to the central data protection and privacy guide for suite-wide information about our data protection and
privacy features.
Data protection and privacy is best when it is implemented suite-wide, and not product-by-product, so we
centralized data protection and privacy information. Please see the latest centralized content for information about
setting up and using data protection and privacy features.
Note
SAP SuccessFactors values data protection as essential and is fully committed to help customers complying
with applicable regulations – including the requirements imposed by the General Data Protection Regulation
(GDPR).
By delivering features and functionalities that are designed to strengthen data protection and security
customers get valuable support in their compliance efforts. However it remains customer’s responsibility to
evaluate legal requirements and implement, configure and use the features provided by SAP SuccessFactors in
compliance with all applicable regulations.
For Employee Central Payroll, see the SAP ERP HCM Security Guide for Human Resources Management
documentation and check information about security settings in the payroll system.
There are a number of things that need to be in place before you start building the integration between the Payroll
Time Sheet and Employee Central Payroll.
● Employee Central
● Employee Central Payroll
● Time Off
● Payroll Time Sheet
Caution
Note
The integration of Time Off with Employee Central Payroll is not a prerequisite for the Payroll Time Sheet
integration with Employee Central.
All employee master data must already be replicated successfully to Employee Central Payroll, before you can
replicate payroll-relevant time sheet data to Employee Central Payroll.
Note
User IDs must be unique and case sensitive. The Employee Central Payroll syste doesn't distinguish between
lower or uppercase. For example JMiller and JMILLER are the same User ID for Employee Central Payroll.
This table lists important differences in terminology between the Payroll Time Sheet and Employee Central Payroll.
Time Type Group Time Pay Type (Mapped to Employee Central wage type)
Learn how to integrate the SuccessFactors Payroll Time Sheet with SuccessFactors Employee Central Payroll.
Typically, employees enter their attendance times or overtime in their Payroll Time Sheet, in the Employee Central
system. Integrating the Payroll Time Sheet with Employee Central Payroll allows the replication of all payroll-
relevant time data from the Payroll Time Sheet to Employee Central Payroll.
Employee Central Payroll processes this information and the employees see the results in their pay statements.
To make this possible, you replicate payroll-relevant time data entered by employees in their time sheet to
Employee Central Payroll, 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 Employee Central Payroll.
Take a look at the overall replication process in the following section.
Payroll Time Sheet - Employee Central Payroll Employee Central Payroll is operated on HR Renewal 2.0 EHP7.
The minimum support package level you need is SAP_HR/EA-
HR SP28 to use Employee Central Payroll. However, in order to
use the full range of features as described in this guide you
need SAP_HR/EA-HR SP67.
In this guide, we assume you are using Employee Central Payroll point-to-point replication based on software
component EA-HRRXX for the replication of employee master data. If you are using Employee Central Payroll
middleware-based replication based on software component PA_SE_IN or EA-HRRXX and web service
EmployeeMasterDataReplicationRequest_In you can still replicate time sheet data as described in this
guide, however, we strongly recommend you migrate your Employee Central Payroll system to point-to-point as
soon as possible. For more information on specific settings you will have to do if you haven't migrated, please see
the appendix of this guide.
Caution
Remember that this guide is intended for initial implementation as of Q2 2016 only. If you started integrating
Time Sheet with Employee Central Payroll before Q2 2016 (b1605) on software component PA_SE_IN or EA-
HRRXX using Dell Boomi Atomsphere as the middleware this isn't the right guide for you. To find the right
guide, go to the Help Portal on the Employee Central Payroll product page, choose version Previous Releases
and click the link named Q1 2016 / b1602 Employee Central Payroll Guides to download the zip file containing
the guides relevant at that time.
To assist you in successfully integrating the Payroll Time Sheet with Employee Central Payroll, use the following
steps as a rough guideline. This is a simplified approach to a possible integration process. Based on your
customer’s business requirements, you will need to adjust this process.
This integration sequence is developed together with the product team and experts in the field. It covers the main
integration points in the most efficient order. However, each customer has their own special requirements. Various
factors, such as the country in which your customer’s company is located and your company’s line of business will
influence how you set up the integration between the Payroll Time Sheet and Employee Central Payroll.
You want to replicate payroll-relevant time data entered by employees in their Payroll Time Sheet to Employee
Central Payroll, 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 Payroll Time Sheet to the Employee Remuneration Info infotype (2010) in Employee Central Payroll.
For more information about the replication of time scheet, see the Replication of Employee Time Valuation Result to
Employee Central Payroll - Scenario Overview.
Here we provide an example of one approach you could take in building the integration between the Payroll Time
Sheet and Employee Central Payroll.
Configuring Employee Central Payroll Configuring Employee Central Payroll for Time Sheet Integra
tion [page 30]
Scheduling Replication of Time sheet Scheduling the Replication of Time Data [page 34]
Checking Data Replication Results Checking Data Replication Results [page 36]
Let's look at the replication process for individual employee time valuation results from Employee Central Time
Sheet replicated to Employee Central Payroll.
Replication Overview
The graphic below illustrates the overall replication process. The entire replication process is broken down into
seven main phases, preceded by a preliminary phase where a time sheet is approved.
Example
The example focuses on the replication of a single Time Pay Type Regular Pay, within a replicated time valuation
result for a single employee. In the following example, you will see how eight hours of Regular Time recorded by
the employee for Tuesday 26 May is replicated to Employee Central Payroll, as part of a replicated Employee
Time Valuation Result.
Prior to the Replication Process: Time Sheet Approval and Creation of Employee
Time Valuation Result in the Employee Central System
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, eight hours per day, which is recorded automatically in her time sheet. In this
Integrating Payroll Time Sheet with Employee Central Payroll
Replication of Employee Time Valuation Result to Employee Central Payroll - Scenario
12 CONFIDENTIAL Overview
week, she works ten 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 timesheet is approved by her assigned supervisor or manager and the time sheet status changes to Approved.
The picture below shows the time sheet entries and the Approved status of the time sheet.
The status change for the time sheet from To be Approved to Approved triggers the Employee Central system to
derive a time valuation result for this employee from the respective approved time sheet. A single time valuation
result is created for Tuesday 26 May and replicated to the Employee Central Payroll System.
A data replication proxy is created at this point if the posting target of the time valuation result is Payroll.
A sample time valuation result for this employee is shown in the picture below. Highlighted is the time pay type
Regular Time that we concentrate on in this scenario.
A data replication proxy is created/updated after approval/cancellation of a time sheet in Employee Central and if a
relevant Data Replication Configuration exists.
The point-to-point report checks if there are data replication proxies available. If yes, it collects them from the
Employee Central MDF 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.
Only Data Replication Proxies with status Out of Sync or status Deleted are selected for replication.
Note
Status Deleted means, that the proxy is replicated, and the time information will be deleted in Employee Central
Payroll accordingly.
Phase 3: Map Employee Central Time Pay Type to Employee Central Payroll
Wage Type
Replication continues with mapping of the Regular Pay time pay type from the time sheet to the Employee Central
Payroll wage type MI01 in the Employee Central Payroll system.
The complete time valuation result for the employee is replicated to Employee Central Payroll. In this example and
based on pre-configured mapping, infotype 2010 in Employee Central Payroll is filled as shown in the picture below:
The status of the replication to Infotype 2010 is sent from the Employee Central System to the Data Replication
Monitor in Employee Central.
The 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.
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 proxy objects are deleted.
A time sheet has been recorded for the employee in his or her current employment (PERNR). Due to an
employment change, a new PERNR is created. As a consequence, your employee now has two PERNRs, and the
employee time valuation results generated from the time sheet are only stored in the first PERNR. To ensure a
correct replication of employee time valuation results with the corresponding company and according to the
validity of each employment, please proceed as follows:
Here is an illustration of the process with the global assignment replication scenario:
Example
Lisa Cooper recorded her time from Monday 01/15 to Friday 01/19. As of Wednesday 01/17, she is on a global
assignment. To ensure a correct replication of the employee time valuation results with the corresponding
company, proceed as follows:
For more information about the PERNR in Employee Central Payroll, see the PERNR Creation documentation.
The following table gives you an overview of all source MDF fields in Employee Central relevant for the replication of
employee time valuation results from Employee Central and Payroll Time Sheet to Employee Central Payroll, and
their corresponding target destinations in the Employee Central Payroll system.
The table also shows which fields you need to map manually. This is indicated in the column Code mapping
required ?. Along with the table, you find descriptions on which mapping activities you need to do for which fields.
Data Replication External code of Employment - Time 2010 The first 10 digits
Proxy - sourceGe referenced time ob - SourceGeneri are filled into
nericObjectExter ject cObjectExternal AWREF
nalCode Code
Time Valuation Re External Code for Employment -Time Yes 2010 LGART
sult - Time Pay Time Pay Type - EmployeeTimeVa
Type - External luationResult - Pay
Code TypeName
Note
Character length in Employee Central Payroll is restricted to 128 characters for the PayTypeName.
Set up the permissions needed by API user in Employee Central, as well as permissions for data replication users
and users who process the replicated time data in Employee Central Payroll.
Set the permissions required by a user of the SAP SuccessFactors Application Programming Interface (API) and
the Data Replication Proxy and grant your replication (API) users the permission they require for running employee
time data replication in Employee Central.
Context
The permissions listed here give a user access to use the SAP SuccessFactors OData API and OData API for time
data replication. Please note that they do not grant any user interface logon.
Your API users need permission to access the Data Replication Proxy object, to be able to run the replication of
employee time data to Employee Central Payroll.
For more information about role-based permissions – what they are, how they work, how you set them up – please
see Implementing Role-Based Permissions in the SAP Help Portal.
Procedure
Note
The API user must have permissions to read the generic object Employee Time. If you change the default
security settings of this generic object, make sure that the API user has the respective permissions.
Next Steps
You can test that the API works by using any commonly available tools, such as the SOAP UI tool.
Grant your admin users the permissions they require for configuring employee time data replication in Employee
Central.
Context
Your admin users need permission to access the Data Replication Configuration object, to be able to make settings
for replication of employee time data to Employee Central Payroll.
For more information about role-based permissions – what they are, how they work, how you set them up – please
see Implementing Role-Based Permissions in the SAP Help Portal.
Procedure
Provides a step-by-step approach for configuring Employee Central and the Payroll Time Sheet so that they can
communicate employee time valuation result data to Employee Central Payroll.
In Employee Central Payroll you have to set the connection Set Connection Data [page 21]
data to Employee Central and create the Replication Target
Creating the Replication Target System Object [page 22]
System Object.
As preparation for the data replication configuration, you must Create a Value Help for Employee Class [page 24]
Ping the Employee Central APIs to ensure that communication Ping Employee Central APIs [page 23]
is up and running.
Context
Before creating the replication target system object and verify the connection with a ping test, start the report
Configuration report for Employee Central Payroll (RP_HRSFEC_PTP_CONFIGURATION) ussing the
HRSFEC_PTP_CONFIG transaction to set up the connection to Employee Central for the replication of employee
master data and time data.
Procedure
Caution
Make sure that your password does not contain any special character like "&".
The user needs permission to access the Employee Central APIs and OData Service Communication must
be enabled. For more information, see section Setting Permissions for API User and Enable OData-Service
Communication.
4. To create the Replication Target System Name for Employee Central, go under Set Connection Data and set the
Create Repl. Target System flag.
You can also create the replication target system manually in the Admin Center. For more information, see
section Creating the Replication Target System Object Manually.
5. Press Execute
The last three characters of the RFC destination name should be the same as the SAP client you used.
If you chose to create the replication target system with the report and the creation was successful, you should
see the following success message on the Configuration Status view:
○ Replication Target System XXXCLNTNNN is created successfully in Employee Central.
Related Information
Context
There are two ways to create the Replication Target System Object, you can create it automatically using the
Configuration Report for Employee Central Payroll (RP_HRSFEC_PTP_CONFIGURATION) as described in the
previous section or you can create it manually in Admin Center, as described in this section.
If you want to create the Replication Target System object manually, go to transaction SCC4.
a. Choose your client and press the magnifying glass.
b. Note down the logical system name. You will need it again later.
c. Go to Admin Center. In the Tools search field, enter Manage Data.
Related Information
Context
Procedure
If the test was successful, you will see the following success messages in the log:
○ SOAP login/logout HTTP status code: 200
○ OData query was successful with HTTP status code 200 for object EmployeeDataReplicationConfirmation.
○ OData query was successful with HTTP status code 200 for object DataReplicationProxy.
Context
As preparation for the data replication configuration required in the next step, you must create a value help for
Employee Class in the Employee Central system.
To achieve this, you first download the HRIS picklist for Employee Class. You then create a new MDF Employee
Class picklist using the existing HRIS picklist. The required steps are explained below:
Note
Employee 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
You 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.
Results
The Employee Class Assignment is available in the Data Replication Configuration object that you must configure
next.
Use the Configuration Report (RP_HRSFEC_PTP_CONFIGURATION) to set up the connection to Employee Central
for the replication of employee master data and absence data, create the replication target system object, and to
verify the connection with a ping test.
An overview of which settings you need to make in Employee Central to set up time sheet replication.
Make Sure that External Codes Aren't Longer Than 32 Characters [page 29]
Be careful when defining external codes in Employee Central for time sheets that are relevant for time data
replication to Employee Central Payroll.
Procedure
Note
The Earliest Selection Date is important here. Only time sheets with a booking date on or after the Earliest
Selection Date you specify in this step are considered for replication.
For example, an approved time sheet for an employee exists for December 27 - January 02. You specify the
Earliest Selection Date of January 01. Replication is performed in this case. However, if the Earliest Selection
Date were on January 3, 2018 the time sheet would not be replicated, because the booking date of the time
sheet is before the Earliest Selection Date.
Tip
Note 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
6. Set Correction Phase Indicator. 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 the Always Allow Replication In
Note
Note that after saving, it switches automatically back to No, because the job is triggered directly during the
save.
8. Set the Exclude Contingent Workers field to Yes if you don't want to replicate data assigned to contingent
workers. Note that this setting overrules other filter criteria of this configuration object.
Example
You want to replicate employees assigned to country Mexico and the Exclude Contingent Workers field is set
to Yes, contingent workers are not included in the time replication process.
Note
In Employee Central Payroll, the recommended value for this field is Yes since contingent workers are not
included in the master data replication process.
Country Assignment
Enter the Employee Central Country Code and only data from employees employed in the specified country are
replicated. It is possible to enter multiple countries.
Enter the Employee Central Pay Group Code to replicate only data of employees of that specific pay group. You
can enter multiple pay groups.
Company Assignment
Enter the Employee Central Company Code to replicate only the data of employees of a specific company/legal
entity. You can enter multiple company codes.
Enter the Employee Central Employee Class to replicate only data of employees of a specific employee class
are replicated. It is possible to enter multiple employee classes.
Note
Changing these settings does not affect data from the past.
Note
You don't make settings for the configuration of time sheet using Time Type Group.
You have successfully completed the configuration of time sheet data replication between your Employee Central
and Employee Central Payroll systems.
Remember
A single employee time valuation result for Time Sheet replication can only be replicated to one target system.
Be careful when defining external codes in Employee Central for time sheets that are relevant for time data
replication to Employee Central Payroll.
In Employee Central, the External Code of the Employee Time object can have 128 characters. However, in
Employee Central Payroll it can only have 32 characters. Make sure that the External Code in Employee Central isn't
longer than 32 characters. This is especially important when you upload time sheets to Employee Central by file
import. If an external code is longer than 32 characters, replication fails and a corresponding error message is
raised.
The following describes step-by-step how to configure Employee Central Payroll so that it can communicate data
for the Payroll Time Sheet integration.
The user needs to be of type B (System User), with specific authorizations and restrictions. For your convenience,
we have created a template role you can assign to this user: SAP_HR_TIM_EC_PTP_REPL. We strongly recommend
that you create the user with this template role. You will also have to mark this user as a customer user by assigning
it to the user group customer in transaction SU01, or else the user will be deleted automatically by the system.
Caution
You have to copy this role from client 000 into your customizing client.
For more information on creating users see Creating a Technical User in the SAP NetWeaver Library.
Find out about the Customizing settings you need to make in Employee Central Payroll.
The following outlines the customizing you must perform in the Employee Central Payroll system to enable
integration with the Payroll Time Sheet in Employee Central.
Context
In the IMG structure open SAP Customizing Implementation Guide Personnel Management Integration
Settings for SuccessFactors Employee Central Payroll Assignment of Code Values For Point-to-Point
Replication
Here you can see the code value mapping as it is delivered to you by default, maintain properties for code value
mapping and maintain code value mapping itself.
Procedure
1. In the IMG structure open SAP Customizing Implementation Guide Personnel Management Integration
Settings for SuccessFactors Employee Central Payroll Assignment of Code Values For Point-to-Point
Replication Display Code Value Mapping as Delivered by SAP
In this Customizing activity, you can display the code value mapping as it is delivered by default.
2. In the IMG structure open SAP Customizing Implementation Guide Personnel Management Integration
Settings for SuccessFactors Employee Central Payroll Assignment of Code Values For Point-to-Point
Replication Maintain Properties for Code Value Mapping
In this Customizing activity you define for each Data Type in Employee Central the end and start date,
alternative list IDs, the mapping mode, and whether or not the mapping is country-specific. You can also assign
specific countries to data types.
Remember
If you assign country-dependency to a data type here, you also have to maintain the ISO Code for the
corresponding code value mapping in Customizing activity Maintain Code Value Mapping
(T77SFEC_CVMAPC).
3. In the IMG structure open SAP Customizing Implementation Guide Personnel Management Integration
Settings for SuccessFactors Employee Central Payroll Assignment of Code Values For Point-to-Point
Replication Maintain Code Value Mapping
In this Customizing activity you can map the Employee Central code values to the Employee Central Payroll
code values.
Note
Time Pay Type is an attribute of the employee time valuation result. It is included in the replication of time sheet
data to Infotype 2010 in the Employee Central Payroll system.
If the Employee Central and Employee Central Payroll codes for Time Pay Type are the same, no further mapping is
needed. If they are not, you need to map Time Pay Type values from the time sheet manually in Employee Central
Payroll.
Perform this mapping in Customizing, under Personnel Management Integration Settings for SuccessFactors
Employee Central Payroll Assignment of Code Values Define Mapping of External Code Value Lists to Internal
Code Value Lists . (See also Assignment of Code Values ).
Note
In Employee Central the Time Pay Type Code can have 255 characters. In Employee Central Payroll, it can only
have 128 characters. Make sure that the External Code for each of your Time Pay Type Codes in Employee
Central is no longer than 128 characters. If it's longer than that, any characters after the 128th is cut off during
data replication.
You will need to perform cost center key mapping in Customizing, if the Cost Center IDs in the Employee Central
system differ from the corresponding codes in Employee Central Payroll.
Note
If the Cost Center ID in Employee Central has 10 characters and has the same value as in Employee Central
Payroll, 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 Employee Central Payroll (length of key field KOSTL of CSKS), no
mapping is required.
In Customizing, map the cost center external keys from the Employee Central system to the internal cost center
keys from your Employee Central Payroll system.
In the IMG structure open SAP Customizing Implementation Guide Personnel Management Integration
Settings for SuccessFactors Employee Central Payroll Assignment of Key Mapping of Organizational Data Assign
External Cost Center Keys to Internal Cost Center Keys
Note
You must perform mapping between the Employee Central and Employee Central Payroll systems if you
want to use cost centers from a company code not assigned within Infotype 0001. The system first tries to
derive the cost center from the Employee Central system directly. However, if a cost center is entered in the
Employee Central system that belongs to a different company code than assigned to Infotype 0001, and no
mapping is maintained, the Employee Central Payroll system takes the company code assigned to Infotype
0001. 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 Employee Central
Payroll company code and cost center to avoid this potential error. The same situation may occur also for
Infotypes 0015 and 0027, as described in the Implementing Employee Central Payroll Implementation and
Integration Guide.
Context
The Replication Report picks up the data from the OData API. The report runs as a batch job that you need to
schedule.
Procedure
Tip
To prevent master data and time data from being locked during the replication process, we recommend
that you schedule each report every 15 minutes and stagger the reports so that they run 5 minutes
apart.
Example
You get the status message Job TIME PAY COMPONENT REPLICATION saved with status: Released
Note
To avoid unnecessary replications of absences and time sheets especially in test systems because
configuration errors are not corrected, the following logic has been improved:
○ 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; > 125 times failed: 1 replication per day).
○ To return to the replication frequency of the employment and the replication content type as previously
scheduled in Employee Central Payroll (scheduling of point-to-point report), you can choose one of
these options:
○ Resend the employment in the Data Replication Monitor.
○ Create or update a time object for this employment and replication content type in Employee
Central to reset the replication frequency to the frequency planned in Employee Central Payroll. 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.
Using the Employee Central Data Replication Monitor When Replicating Time Sheet [page 36]
The Data Replication Monitor shows the replication status of individual employments of an employee for
the Replication Content Type Time Pay Components.
Monitoring Tools in the Employee Central Payroll system: Web Service Utilities and Application Log [page 36]
On the Employee Central Payroll side, there are two monitoring tools that help you identify errors that occur
during the replication of employee master and time data.
The Data Replication Monitor shows the replication status of individual employments of an employee for the
Replication Content Type Time Pay Components.
The monitor displays two statuses: Successful or Failed. Clicking the employee name will lead you to the respective
employee file. Clicking the respective Failed replication status brings up further information about the error. From
the error message you can switch to Payroll Time Sheet.
Manual Rescheduling
You can trigger a replication run for one or more employees in the Data Replication Monitor. Select the employees
and click Send. When you do this, the Scheduled Replication Time field is set to the current time and the flag Allow
Replication in Correction Phase is set for the respective employee(s). This means that the employee data will be
replicated during the next schedule cycle to the payroll system, even if it is in correction phase. In this case, the
error message Payroll area in correction phase will not be generated.
On the Employee Central Payroll side, there are two monitoring tools that help you identify errors that occur during
the replication of employee master and time data.
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 transaction SRTUTIL (Web Service Utilities) shows errors that come up in this check.
Application Log
Correct messages are passed on to the application logic that maps the data to the structures of the Employee
Central Payroll employee infotypes and performs the updates on the 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 transaction SLG1
(Application Log).
To search for a specific employment per employee enter the External ID and User ID in that order separated by a
slash (/).
It may be useful to look in detail at the data of the replication message to better understand why an error has
occurred. Do so in the message monitor of transaction SRTUTIL (Web Service Utilities). On the selection screen,
enter EmployeeTimeDataECToERPRequest_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. You can
display the content of a message by double-clicking the message. It can also be displayed as an XML.
Here's how to troubleshoot time sheet replication from Employee Central Time Off to Employee Central Payroll.
In the following, you can find some of the most common errors and how to prevent them in Employee Central.
This section points out the possibilities to trigger replication of exisiting time sheets.
When you want to replicate time sheets that were not replicated before you set up the integration itself, you can
This might also be necessary if the data replication configuration has been changed, or when time type groups,
time pay types or employee master data (e.g. employee class) have been amended, where time sheets approved
before such changes are still to be replicated.
Based on the Data Replication Configuration a Data Replication Proxy is created to be replicated to Employee
Central Payroll
Using the Proxy Creation Job at Data Replication Configuation, 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.
Note
Note that after saving, it switches automatically back to No, because the job is triggered directly during the
save.
Amending a time sheet results in a new time sheet being created. After approval of the new time sheet, the original
timesheet is cancelled. You can make amendments to a time sheet that has already been approved directly from
the time sheet itself:
1. Navigate to the approved time sheet you want to update and click Make Amendment.
A new version of the time sheet is created and opened up for you to make your amendments. At this point, the
time sheet has the status Draft Amendment.
2. Correct your time sheet and click Resubmit.
3. Check your amendments in the Submit popup and click Submit.
Clicking Submit changes the time sheet status to Amendment to be Approved and resends the time sheet for
approval.
Caution
You can only make amendments to time sheets with the status Approved.
Use the check tool to find potential problems and errors in your configuration before you call support about an
issue.
Prerequisites
Assign Access Check Tool and Allow Configuration Export to your role in Role Based Permissions (RBP).
1. Go to Admin Center.
2. In the tools search field, type Check Tool.
3. In Application, select the application you want to check.
Tip
For example, to run checks for Time Off, select Time Off.
You see the checks for the application you selected. The description for each check describes the situation you
hope to find in running the check. For example, in running the check Accrual lookup by seniority is consistent,
you hope to find that the lookup is indeed consistent.
4. Click the check the box at top left in the table to run all checks.
5. If you want to run only some checks, select them individually.
Tip
To understand what a check does, right click the Check ID. The system then displays some information on
the check.
6. Click Run Checks to check your applications for the checks you selected.
Next Steps
Evaluate the results and resolve the issues. If you encounter an error you cannot resolve, contact Support by
creating a ticket.
If your SAP SuccessFactors applications are behaving in unexpected ways, it is likely that it has a configuration or
data conflict: you have some data that is inconsistent or a configuration error. The check tool quickly identifies
● A list of issues in your configuration or data and the severity of each issue.
● A solution or recommendation to address the issue.
After you run checks in the check tool, it returns the results of the check so that you can resolve issues that it
found.
To see the results of the checks, look in the Results column. If you run the checks multiple times to see how you are
resolving issues, look in the Previous Result column to compare the current results to previous results.
Result Action
No issues found If the tool cannot find issues, you see a green check mark the Result.
Issues found If the tool finds issues, it reports the number of issues and a yellow warning icon or a red alarm
icon.
● The yellow icon indicates a low severity issue. The system proposes a solution.
● The red icon indicates a high severity issue. You must take action, which could include creat
ing a Support ticket.
Related Information
When the check tool reports a serious issue, you might need to contact Support. You can create a Support ticket
from within the check tool.
Prerequisites
Run the check tool. You can find the check tool by going to Admin Center Check Tool . You create the ticket
from the results page of the tool
1. On the results page, look in the Result column for the errors you want to report on.
You usually contact Support for high severity issues not low severity issues.
2. Click the error in the result to open the Detailed Result.
Note
If you cannot click the error, expand the list of checks from the Description column, and then click the error
from the Result column.
You can use the check tool to identify any Data Replication Proxies with configuration and data consistency issues.
You access the tool from the Admin Center by choosing Company Settings Check Tool .
1. Choose the application, in this case Data Replication, where you want to carry out checks.
2. You then see a list showing the objects for which checks are available. Click the object you’re interested in to list
the checks you can run for it.
3. You can run as many checks as you want. Note the Run Checks button at bottom right, which tells you how
many you have selected.
Another feature is that you can click the Check ID for an object to display some information on what that
particular check involves.
Notice also the message at the bottom of the display. This is telling you that, if you do need to create a ticket,
you must attach any relevant configuration information. You do this by clicking the link within the message. A
popup then appears, where you can choose what you want to export.
Caution
After the export, check whether there is person-specific data in the file. If there is, you need to delete it
before you do anything more with the file.
4. You can run as many checks as you want. Note the Run Checks button at bottom right, which tells you how
many you have selected.
Another feature is that you can right click the Check ID for an object to display some information on what that
particular check involves.
Related Information
In the following, you can find some of the most common errors and how to prevent them in Employee Central
Payroll.
For all wage types used in the replication of employee time valuation results , you must verify the following:
● Under Number/unit, that the Time unit/meas. field is filled with the unit Hours.
● Under Input combination, make sure that you make the settings required to allow Number/unit and disallow
Amount.
You do this in Customizing, under Personnel Management Personnel Administration Payroll Data Employee
Remuneration Information Wage Types Check Wage Type Catalog Check wage type characteristics .
The Employee Central Payroll wage types you have previously mapped to time pay types must be enabled so that
they can be replicated on multiple occasions each day to the Employee Remuneration Info (2010) infotype.
This is because multiple entries of the same wage type can be replicated on the same day.
Note
Make this setting to avoid the following error message during replication: Collision with other EE remuneration
info.
Prerequisites
The RFC destination is established in the running system by using the Configuration Report for Employee Central
Payroll. For more information, see Set Connection Data. If the RFC connection is not set up, it is displayed in the
application log.
Context
You use the Time Pay Types and Wage Types Configuration report to get an overview of the time pay types (from
SAP SuccessFactors Employee Central) and the equivalent mapped wage types (from SAP SuccessFactors
Employee Central Payroll). Time pay type is an attribute of the employee time valuation result in Employee Central
and is included in the replication of time sheet data to infotype 2010 in the Employee Central Payroll system. In
Employee Central, a time pay type is either an allowance type or a time type group with following attribute:
isPayComponent = YES. All the wage types in the payroll system are given even if they are not mapped to an
Employee Central time type group or allowance type - and vice versa. The report can help you to find inconsistent
data and check that the properties are set up correctly.
Procedure
1. Under Country Grouping, select the relevant country of the allowance types for Employee Central and of the
Employee Central Payroll mapping and wage types.
Note
2. In the Wage Type field, you can include or exclude wage types which should be used for the selection of the
data.
Note
Records belonging to the selected wage type are listed. Additionally, Employee Central time pay types are
being displayed.
3. If you want to hide any entries that do not require any further changes, choose Hide correct entries. Please note
the following:
○ Employee Central time pay types which are not mapped are displayed in the list and need further
configuration.
○ All records with an error are displayed in the list.
Results
The standard screen layout is divided into different sections, which are highlighted in the following colors:
Note
In the MDF object column, the Time Pay Type (A = Allowance Type or T = Time Type Group) is displayed.
If the time pay types and wage types have been changed in any of the systems, the system adds a row to the list,
which shows the changed values.
Hyperlinks
Some links are classified by an icon and/or a mouseover text. These links provide additional information.
About the icons:
● Links with the icon : You are entering a Web site that is not hosted by SAP. By using such links, you agree (unless expressly stated otherwise in your agreements
with SAP) to this:
● The content of the linked-to site is not SAP documentation. You may not infer any product claims against SAP based on this information.
● SAP does not agree or disagree with the content on the linked-to site, nor does SAP warrant the availability and correctness. SAP shall not be liable for any
damages caused by the use of such content unless damages have been caused by SAP's gross negligence or willful misconduct.
● Links with the icon : You are leaving the documentation for that particular SAP product or service and are entering 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.
Example Code
Any software coding and/or code snippets are examples. They are not for productive use. The example code is only intended to better explain and visualize the syntax and
phrasing rules. SAP does not warrant the correctness and completeness of the example code. SAP shall not be liable for errors or damages caused by the use of example
code unless damages have been caused by SAP's gross negligence or willful misconduct.
Gender-Related Language
We try not to use gender-specific word forms and formulations. As appropriate for context and readability, SAP may use masculine word forms to refer to all genders.
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.