Script Integración Con EC - EN - US

Test Script PUBLIC
SAP S/4HANA
March 2016
Employee Central Integration (JB1_US)

Content
1 Test Description. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4
1.1 Purpose of the Document. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4
1.2 Purpose of Employee Central Integration. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4
2 Prerequisites. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5
2.1 System Access and Roles. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5
2.2 Master Data, Organizational Data, and Other Data. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6
2.3 Business Conditions. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7
2.4 Preliminary Steps . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8
Preliminary Steps for Cost Center Replication. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8
Preliminary Steps for Employee Data Replication. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10
Preliminary Steps for Employee Photo Replication. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 12
3 Overview Table. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 14
4 Test Procedures. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 22
4.1 Cost Center Replication. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .22
Maintain Cost Center. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 22
View Cost Center Data. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 30
4.2 Employee Data Replication. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 33
Enter Hiring Data. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 33
Enter Termination Data. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 45
Enter Rehiring Data. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 51
Monitor Employee Master Data Replication. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 65
View Personnel Master Data. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 67
Maintain Employee Information. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .83
Monitor Employee Master Data Delta Replication. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 96
View Updated Personnel Master Data. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 98
4.3 Contingent Worker Data Replication. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 109
Enter Master Data of Contingent Worker. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 109
Monitor Contingent Worker Master Data Replication 1. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 118
PUBLIC Employee Central Integration (JB1_US)
2 © 2016 SAP SE or an SAP affiliate company. All rights reserved. Content
View Contingent Worker Master Data. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .120
Maintain Contingent Worker Information. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 127
View Updated Contingent Worker Master Data. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 136
Re-Activate Contingent Worker. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 140
View Contingent Worker Master Data. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 148
4.4 Employee Photo Replication. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 155
Maintain Employee Photo. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 156
View Employee Photo. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 160
Handle Replication Exceptions (Optional). . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 161
Employee Central Integration (JB1_US) PUBLIC

Content © 2016 SAP SE or an SAP affiliate company. All rights reserved. 3
1 Test Description
1.1 Purpose of the Document
This document provides a detailed procedure for testing the scope item after solution deployment, reflecting the predefined scope of the solution. Each process step is
covered in its own section, providing the system interactions (that is, test steps) in a table view. Steps that are not in scope of the process but are needed for testing are
marked accordingly (see column Test Step). Customer-project-specific steps must be added.
1.2 Purpose of Employee Central Integration
The SuccessFactors Employee Central Integration to the SAP S/4HANA, cloud edition offers you predefined content for data integration to enable end-to-end business
processes across your core cloud HR and the SAP S/4HANA, cloud edition. In this scenario, SuccessFactors Employee Central as your core HR system in the cloud is the
system of record for all human resources (HR) data.
Integration of employee data and contingent worker data between SuccessFactors Employee Central and SAP S/4HANA cloud edition is supported. Employees are created as
business partners with the Employee role in SAP S/4HANA, cloud edition. Contingent workers are created as business partners of the Freelancer or Service Provider type.
Transferred data includes basic data (such as employee name and ID) and contact details (such as workplace address, email and telephone information). A vendor record is
automatically created for the same business partner for financial processes, such as travel expense reimbursement. Payment information - with payment method and bank
account information for bank transfers - is maintained, including a home address for reimbursements by check.
Integration of employment data between SuccessFactors Employee Central and SAP S/4HANA, cloud edition is also supported. This information is separated from the
Employee, encapsulating job information coming from SuccessFactors Employee Central. Relevant, time-dependent job information is maintained in the employment details.
This includes employment status, employment percentage, working hours per week, job title, and job information, such as business unit, division, department, and cost center
assignment. Additionally an attached photo is also transferred.
Financial data such as company code and cost center is also integrated.

4 © 2016 SAP SE or an SAP affiliate company. All rights reserved. Test Description
2 Prerequisites
This section summarizes all prerequisites to conducting the test in terms of systems, users, master data, organizational data, and other test data and business conditions.
2.1 System Access and Roles
The test is conducted in the following systems:
System Details
SuccessFactors Employee Central SuccessFactors instance URL
SAP S/4HANA SAP Fiori Launchpad URL
SAP HANA Cloud Integration The end-user does not perform any process step in this system; instead, the process steps exe
cuted in this system are automatic, based on scheduled background jobs.
Note
In the following, were appropriate, we will use the following abbreviations for the systems:
● SuccessFactors Employee Central will be shortened SFSF EC

● SAP HANA Cloud Integration will be shortened SAP HCI
Use the following standard test users or assign roles to testers, respectively:
In SAP S/4HANA, cloud edition
Business Catalog Role Name Business Catalog Role ID Log On
Controller
SAP_BCR_FIN_CO_MASTER_DATA Suggested sample user CONTROLLER representing the business role Control
ler
Customer Project Manager SAP_BCR_PSP_CUST_PROJ_MANAGE Suggested sample user PROJECTMGR representing the business role Cus
tomer Project Manager
In SuccessFactors Employee Central

Prerequisites © 2016 SAP SE or an SAP affiliate company. All rights reserved. 5
Business Role Business Role Description Business Role ID Log On
Administrator A person responsible for verifying the correct replication of cost as defined in role-based permission in SFSF EC; for testing pur Test user: <userid>
center data in SuccessFactors Employee Central. pose use the superuser role
Password: <password>
HR Manager A person who performs in SuccessFactors Employee Central all as defined in role-based permission in SFSF EC; for testing pur Test user: <userid>
tasks that relate to the administration of employees. pose use the superuser role
Password: <password>
In addition, some activities need to be executed by the SAP Service Center
Caution
The activities executed by this role as briefly mentioned under Preliminary Steps [page 8] do not have to be carried out by someone testing this test script!
Business Role Business Role Description
Middleware Administrator An employee of the SAP Service Center responsible for:
● deploying in the SAP HANA Cloud Integration middleware the relevant iFlow and scheduling the background job for replicating
changes in cost center data from SAP S/4HANA to SuccessFactors Employee Central;
changes in employee or contingent worker data from SuccessFactors Employee Central to SAP S/4HANA;
changed employee photos from SuccessFactors Employee Central to SAP S/4HANA.
2.2 Master Data, Organizational Data, and Other Data
The organizational structure and master data of your company has been created in your system during activation. The organizational structure reflects the structure of your
company. The master data reflects employee specific data.

6 © 2016 SAP SE or an SAP affiliate company. All rights reserved. Prerequisites
Use your own master data to go through the test procedure. The company code relevant for this test script is as given below:
Data Sample Value Details Comments
SAP S/4HANA: com 1710 Company code US SuccessFactors Employee Central: value is mapped to
pany code legal entity ID
2.3 Business Conditions
Before this scope item can be tested, the following business conditions must be met.
Business Condition Comment
1 The legal entities have been setup in SuccessFactors Employee

Central according to the company codes in SAP S/4HANA.
2 Cost centers have been defined in the SAP S/4HANA system.
3 Before hiring an employee, the cost centers must have been re See Preliminary Steps for Cost Center Replication [page 8]
plicated from SAP S/4HANA to SuccessFactors Employee
Central.
4 To rehire an employee, this particular employee must have left See Enter Termination Data [page 45]
the company before.

2.4 Preliminary Steps
2.4.1 Preliminary Steps for Cost Center Replication
Test Administration
Customer project: Fill in the project-specific parts.
Test Case ID <X.XX> Tester Name Testing Date Enter a test

date.
Business Role(s)
Responsibility <State Service Provider, Customer or Joint Service Duration Enter a

Provider and Customer> duration.
Deploying and Configuring Cost Center iFlow in SAP HANA Cloud Integration Middleware
After having received your SuccessFactors Employee Central master instance, all active cost centers defined in SAP S/4HANA need to be uploaded into SuccessFactors
Employee Central. This is done by the Middleware Administrator, and achieved by deploying and configuring the cost center iFlow in the SAP HANA Cloud Integration
middleware. The Middleware Administrator will also schedule the replication background job in the SAP HANA Cloud Integration middleware in order to trigger the delta
replication automatically. In a delta replication, only cost center data that has changed in SAP S/4HANA since the last synchronization will be replicated to SuccessFactors
Employee Central. It is recommended to schedule the replication background job with a relatively short interval, such as 10 minutes, to enable timely validation of changes
done in the SAP S/4HANA system.
Caution
These activities are performed in the SAP Service Center and you do not need to execute/test them!

Validating Replicated Cost Center Data in SuccessFactors Employee Central
Once the cost centers have been replicated successfully to the SuccessFactors Employee Central system, you can validate the replicated cost center data to make sure it is
synchronized between SuccessFactors Employee Central and SAP S/4HANA. For this, check the list of cost centers in SuccessFactors Employee Central and compare it with
the list of active cost centers in SAP S/4HANA.
You can obtain the list of active cost centers in SAP S/4HANA as follows:
1. Log on to the SAP Fiori Launchpad with the Controller role.

2. In the SAP Fiori Launchpad, open Manage Cost Centers.
3. Set the controlling area and choose the Go button.
The cost centers available in this controlling area are listed.
4. To export them, choose the Export to Spreadsheet icon in the top right corner of the Search Results table.
You can obtain the list of cost centers replicated to SuccessFactors Employee Central as follows:
1. Log on as Administrator
2. Go to Admin Center.
3. In the Company Processes & Cycles portlet, select Employee Files Import and Export Data .
4. In the Select the action to perform field, select Export Data.
5. In the Select Generic Object field, select Cost Center, for the Select all data records field, leave default value Yes; the values for the other fields, select as appropriate.
6. Choose the Export button.
Go back to Admin Center.
7. In the Company Processes & Cycles portlet,select Employee Files Monitor Job .
8. In the list of jobs, select the appropriate job and choose the Download Status link.
The list of cost centers is displayed as spreadsheet; open it, filter it for status value A (meaning Active) and compare the list of remaining cost centers with the list of cost
centers in SAP S/4HANA.
Check also sample cost center data to ensure that the cost center attributes have been correctly replicated. The Cost Center Information replicated is as follows:
Fields in SAP S/4HANA Fields in SuccessFactors Employee Cen Description/Comment

tral
Valid From Start Date Effective start date of cost center information.
Cost Center (Code) Code The cost center code as defined in the SAP S/4HANA system.
Cost Center (Name) Name
Cost Center Description Description

Fields in SAP S/4HANA Fields in SuccessFactors Employee Cen Description/Comment
tral
Status Status Active/InActive in SuccessFactors Employee Central depends on the validity end date of
the cost center in SAP S/4HANA. A cost center that has been delimited in SAP S/4HANA is set to inac
tive in SuccessFactors Employee Central.
External Object ID Combination of company code and cost center code defined in the SAP S/4HANA system.
Company Code Company Company Code of Cost Center
2.4.2 Preliminary Steps for Employee Data Replication
Test Administration

date.
Business Role(s)

Uploading Employee Data to SuccessFactors Employee Central Master Instance
After having received your SuccessFactors Employee Central master instance, the records of the employees and contingent workers already existing in your company must
be uploaded. This can be done in the SuccessFactors Employee Central master instance, for example, as follows: go to Admin Center; in the Manage Employee portlet, select
Update User Information Import Employee Data , and proceed as per the instructions on the Import Employee Data screen.
Note
Make sure to have maintained the data needed for successful replication to SAP S/4HANA.

Note
In case of uploading contingent worker data, make sure to follow below order: Basic import, Employment Details (Is Contingent Worker field should be Yes), Work Order
import, Job History.
Deploying and Configuring Employee iFlow in SAP HANA Cloud Integration Middleware
When the SuccessFactors Employee Central system is then connected to the SAP S/4HANA system, the existing employee and contingent worker master data must be
replicated into the SAP S/4HANA system. This is done by the Middleware Administrator, and obtained by deploying and configuring the employee iFlow in the SAP HANA
Cloud Integration middleware. The Middleware Administrator will also schedule in the SAP HANA Cloud Integration middleware the replication background job in order to
trigger the delta replication automatically. In a delta replication, only employee and contingent worker data that has changed in SuccessFactors Employee Central since the
last synchronization will be replicated to SAP S/4HANA. It is recommended to schedule the replication background job with a relatively short interval, such as 5 minutes, to
enable timely validation of employee / contingent worker data maintained in SuccessFactors Employee Central.
Caution
These activities are performed in the SAP Service Center and you need not to execute/test them!
Validating Replicated Employee Data in SAP S/4HANA
Each employee replicated from SuccessFactors Employee Central into SAP S/4HANA automatically leads to the creation of a business partner with role Employee and a
vendor for supporting check payout in SAP S/4HANA, like for example payout of travel expenses by check.
Each contingent worker replicated from SuccessFactors Employee Central into SAP S/4HANA automatically leads to the creation of a business partner with role Service
Provider or Freelancer. In addition, in case of Service Provider, a Supplier is automatically created in SAP S/4HANA.
Once the employees and contingent workers have been replicated successfully to the SAP S/4HANA system, you can validate the replicated data in SAP S/4HANA to make
sure the employee or contingent worker data is in-sync between SuccessFactors Employee Central and SAP S/4HANA. For this, compare the list of employees / contingent
workers you have uploaded to SuccessFactors Employee Central with the list of business users in SAP S/4HANA.
In addition, the Technical Support in the SAP Service Center can perform spot checks in the SAP S/4HANA backend system to validate whether the data has been
replicated correctly from SuccessFactors Employee Central.
1. For this, log on to the SAP S/4HANA backend system/client and enter transaction code se16.
2. On the Data Browser: Initial Screen, in the Table Name field, enter value IEMPLOYEE and choose Enter .
3. On the Data Browser: Table IEMPLOYEE: Selection Screen, enter selection criteria as appropriate and choose Execute icon, or alternatively F8 .
4. Mark the record of the employee or contingent worker of interest and choose the Display icon, or alternatively F7 .
5. View and check the correctness of the employee data as replicated from SFSF EC, for example, academic title, correspondence language, gender, business partner role.
2.4.3 Preliminary Steps for Employee Photo Replication
Test Administration

date.
Business Role(s)

Uploading Employee Photo to SuccessFactors Employee Central Master Instance
After successful replication to SAP S/4HANA of the employees already existing in your company, their photos can be uploaded, too.
Caution
As a customer, you must not add in SFSF EC photos to employees that are not intended to be transferred to SAP S/4HANA, like for example the superuser!
Deploying and Configuring Photo iFlow in SAP HANA Cloud Integration Middleware
After the photos have been uploaded to SuccessFactors Employee Central, they must be replicated into the SAP S/4HANA system. This is done by the Middleware
Administrator, and obtained by deploying and configuring the photo iFlow in the SAP HANA Cloud Integration middleware. The Middleware Administrator will also schedule in
the SAP HANA Cloud Integration middleware the replication background job in order to trigger the delta replication automatically. In a delta replication, only employee photos
that have changed in SuccessFactors Employee Central since the last synchronization will be replicated to SAP S/4HANA. It is recommended to schedule the replication
background job to run on a daily basis.
Caution
These activities are performed in the SAP Service Center and you need not to execute/test them!
Validating Replicated Employee Photo Data in SAP S/4HANA
Once the photos have been replicated, you can validate the correctness of the data created in SAP S/4HANA. For this, log on to the SAP Fiori Launchpad and make spot
checks whether the photos are visible on the employees' fact sheets.
In addition, the Technical Support in the SAP Service Center can perform spot checks in the SAP S/4HANA backend system to validate whether the data has been
replicated correctly from SuccessFactors Employee Central.
1. For this, log on to the SAP S/4HANA backend system/client and enter transaction code se16.
2. On the Data Browser: Initial Screen, in the Table Name field, enter value IEMPLOYEE and choose Enter .
3. On the Data Browser: Table IEMPLOYEE: Selection Screen, enter selection criteria as appropriate and choose the Execute icon or alternatively F8 .
4. Select the employee record you want to check and choose the Display icon or alternatively F7 .
5. Check if the Image URL field (technical field name EMPLOYEEIMAGEURL) is filled.
6. Launch the URL consisting of <SAP Fiori Launchpad URL/Image URL> and verify that the correct photo is shown.

3 Overview Table
The scope item Employee Replication from SuccessFactors Employee Central to SAP S/4HANA (Cloud) consists of several process steps provided in the table below.
Cost Center Replication
Process Step Business Condition Business Role Transaction Expected Results
Maintain Cost Center Change of cost center hierarchy information is required Controller SAP Fiori Launchpad A new cost center has been created and an existing has
URL been updated.
Trigger Cost Center Cost center data extraction triggered by the SAP HCI Background The changed data of the cost center has been extracted
Delta Replication
middleware to extract data from SAP S/4HANA. from SAP S/4HANA and sent to SFSF EC.
Update Cost Center Background The cost center data has been updated automatically in
Data in SFSF EC
SFSF EC.
View Cost Center Data Administrator SFSF EC URL The data of the new cost center and the updated cost
centers has been viewed.
Employee Data Replication
Enter Hiring Data HR Manager SFSF EC URL The hiring data for a newly hired employee has been en
tered into the system, and the employee has status
Active as of the date he or she has been hired.
Trigger Employee Employee data extraction is triggered by the SAP HCI Background The data of the new employee has been extracted from
Master Data Replica
middleware to extract data from SFSF EC. SFSF EC and sent to SAP S/4HANA.
tion 1

14 © 2016 SAP SE or an SAP affiliate company. All rights reserved. Overview Table
Create Employee Mas Background A business partner with role Employee has been cre
ter Data Record in
ated automatically in SAP S/4HANA. A vendor is auto
SAP S/4HANA
matically created with the same ID as the business part
ner for supporting financial processes in SAP S/4HANA.
Initiate Employee Background A confirmation message about the replication of em

Master Data Replica
ployee master data has been sent by the SAP S/4HANA
tion Confirmation
system.
Message 1
Receive Employee Background The confirmation message has been received by SFSF
Master Data Replica
EC.
tion Confirmation
Message 1
Enter Termination HR Manager SFSF EC URL The termination data for an employee has been entered
Data
into the system. The employee has status Terminated
beginning one day after the termination date entered.
Trigger Employee Employee data extraction is triggered by the SAP HCI Background The data of the terminated employee has been extracted
Master Data Replica
middleware to extract data from SFSF EC. from SFSF EC and sent to SAP S/4HANA.
tion 2
Update Employee Background The master data record of the terminated employee has
Master Data Record in
been updated automatically in SAP S/4HANA.
SAP S/4HANA 1

Master Data Replica
tion Confirmation
system.
Message 2
Master Data Replica
EC.
tion Confirmation
Message 2
Enter Rehiring Data Employee has been terminated before he or she can be HR Manager SFSF EC URL The data for an employee, who has previously left the
rehired. company and has then been rehired, has been entered
into the system. The employee has status Active as of
the date he or she has been rehired.

Overview Table © 2016 SAP SE or an SAP affiliate company. All rights reserved. 15
Trigger Employee Employee data extraction is triggered by the SAP HCI Background The data of the rehired employee has been extracted
Master Data Replica
tion 3
Update Employee Background The master data record of the business partner with role
Employee has been updated automatically in SAP S/
SAP S/4HANA 2
4HANA.
In addition, the available data of the vendor created dur

ing initial replication is updated accordingly.

Master Data Replica
tion Confirmation
system.
Message 3
Master Data Replica
EC.
tion Confirmation
Message 3
Monitor Employee HR Manager SFSF EC URL Possibly existing unsuccessfully processed replication re
Master Data Replica
quests have been identified. Their correction leads to a
tion
delta replication of the changes to SAP S/4HANA.
View Employee Basic Customer Project Man SAP Fiori Launchpad The basic data of the employee has been viewed after ini
Data
ager URL tial replication.
View Employee Pay Customer Project Man SAP Fiori Launchpad The payment information of the employee has been
ment Information
ager URL viewed after initial replication.
View Employee Ad Customer Project Man SAP Fiori Launchpad The home address of the employee has been viewed after
dress Information
ager URL initial replication.
Maintain Employee Change of employee's contact information is required. HR Manager SFSF EC URL Contact information has been maintained for the em
Contact Information
ployee.
Maintain Employee The employee's supervisor needs to be replaced without HR Manager SFSF EC URL A new supervisor has been maintained for the employee.
Supervisor
leading to changes in the employee's job information.
Maintain Employee Change of employee's payment information is required. HR Manager SFSF EC URL The payment information has been maintained for the
Payment Information
employee.

Maintain Employee Change of employee's address is required HR Manager SFSF EC URL The home address has been maintained for the em
Address Information
ployee.
Trigger Employee Employee data extraction is triggered by the SAP HCI Background The changed data of the employee has been extracted
Master Data Delta
Replication
Update Employee Background The master data record of the business partner with role
Employee has been updated automatically in SAP S/
SAP S/4HANA 3
4HANA.
In addition, the available data of the vendor created dur

ing initial replication is updated accordingly.
Initiate Changed Em Background A confirmation message about the replication of changed
ployee Master Data
employee master data has been sent by the SAP S/
Replication Confirma
4HANA system.
tion Message
Receive Changed Em Background The confirmation message has been received by SFSF
ployee Master Data
EC.
Replication Confirma
tion Message
Monitor Employee HR Manager SFSF EC URL Possibly existing unsuccessfully processed replication re
Master Data Delta
quests have been identified. After the errors have been
Replication
corrected, a new delta replication of the changes in the
employee data is triggered.
View Employee Com Customer Project Man SAP Fiori Launchpad The changed contact information of the employee, repli
munication Informa
ager URL cated as communication information into SAP S/4HANA,
tion
has been viewed.
View Employee Man Customer Project Man SAP Fiori Launchpad The changed supervisor of the employee, replicated as
ager Assignment
ager URL manager information into SAP S/4HANA, has been
viewed.
View Updated Em Customer Project Man SAP Fiori Launchpad The updated payment information of the employee has
ployee Payment Infor
ager URL been viewed.
mation

View Updated Em Customer Project Man SAP Fiori Launchpad The updated home address of the employee has been
ployee Address Infor
ager URL viewed.
mation
Contingent Worker Data Replication
Enter Master Data of Contingent Worker HR Manager SFSF EC URL The data for a contingent worker has been entered into
the system. He or she has status Active starting the date
he or she has been hired.
Trigger Contingent Worker Master Data Contingent worker data extraction is Background The data of the contingent worker has been extracted
Replication
triggered by the SAP HCI middle from SFSF EC and sent to SAP S/4HANA.
ware to extract data from SFSF EC.
Create Contingent Worker Master Data Background A business partner with role Service Provider or Free
Record in SAP S/4HANA
lancer has been created automatically in SAP S/4HANA.
In addition, in case of Service Provider, a relationship be
tween the contingent worker and the vendor maintained
in the work order in SFSF EC is automatically created in
SAP S/4HANA
Initiate Contingent Worker Master Data Background A confirmation message about the replication of contin
Replication Confirmation Message
gent worker master data has been sent by the SAP S/
4HANA system.
Receive Contingent Worker Master Data Background The confirmation message has been received by SFSF
Replication Confirmation Message EC.
Monitor Contingent Worker Master Data HR Manager SFSF EC URL Possibly existing unsuccessfully processed replication
Replication 1 requests have been identified. Their correction leads to a
View Contingent Worker Basic Data 1 Customer Project Man SAP Fiori Launchpad The basic data of the contingent worker has been viewed
ager URL after initial replication.

View Supplier Information for Contingent Customer Project Man SAP Fiori Launchpad The supplier information created for the contingent
Worker ager URL worker has been viewed after initial replication.
Maintain Contingent Worker Contact In Change of contingent worker's con HR Manager SFSF EC URL The contact information has been maintained for the
formation tact information is required. contingent worker.
Maintain Contingent Worker Work Order The work order to which the contin HR Manager SFSF EC URL The work order has been maintained for the contingent
worker.
Information gent worker is assigned needs to be
corrected.
Trigger Contingent Worker Master Data Contingent worker data extraction is Background The changed data of the contingent worker has been ex
Delta Replication triggered by the SAP HCI middle tracted from SFSF EC and sent to SAP S/4HANA.
Update Contingent Worker Master Data Background The master data record of the business partner with role
Record in SAP S/4HANA Service Provider or Freelancer has been up
dated automatically in SAP S/4HANA.
Initiate Changed Contingent Worker Mas Background A confirmation message about the replication of
ter Data Replication Confirmation Mes changed contingent worker master data has been sent
sage by the SAP S/4HANA system.
Receive Changed Contingent Worker Background The confirmation message has been received by SFSF
Master Data Replication Confirmation EC.
Message
Monitor Contingent Worker Master Data HR Manager SFSF EC URL Possibly existing unsuccessfully processed replication
Replication 2 requests have been identified. After the errors have been
corrected, a new delta replication of the changes in the
contingent worker data is triggered.
View Contingent Worker Communication Customer Project Man SAP Fiori Launchpad The changed contact information of the employee, repli
Information ager URL cated as communication information into SAP S/
4HANA, has been viewed.
View Updated Supplier Information for Customer Project Man SAP Fiori Launchpad The corrected supplier information of the contingent
Contingent Worker ager URL worker has been viewed.

Re-Activate Contingent Worker An inactive contingent worker needs HR Manager SFSF EC URL The data for a contingent worker, who in the past has al
to be assigned to another work or ready been assigned to a work order, has been entered
der. into the system. He or she has status Active starting
the date the new work order becomes effective.
Trigger Contingent Worker Master Data Contingent worker data extraction is Background The changed data of the employee has been extracted
from SFSF EC and sent to SAP S/4HANA.
Delta Replication triggered by the SAP HCI middle
Update Contingent Worker Master Data Background The master data record of the business partner with role
Record in SAP S/4HANA Service Provider or Freelancer has been up
dated automatically in SAP S/4HANA.
Initiate Changed Contingent Worker Mas Background A confirmation message about the replication of
ter Data Replication Confirmation Mes changed contingent worker master data has been sent
sage by the SAP S/4HANA system.
Receive Changed Contingent Worker Background The confirmation message has been received by SFSF
EC.
Master Data Replication Confirmation
Message
Monitor Contingent Worker Master Data HR Manager SAP Fiori Launchpad Possibly existing unsuccessfully processed replication
Replication 2 URL requests have been identified. Their correction leads to a
View Contingent Worker Basic Data 2 Customer Project Man SAP Fiori Launchpad The basic data of the contingent worker has been
viewed.
ager URL
View Supplier Information for Contingent Customer Project Man SAP Fiori Launchpad The supplier information created for the contingent
URL
Worker ager worker has been viewed.

Employee Photo Replication
Maintain Employee Upload of new photo for employee or contingent worker is HR Manager SFSF EC URL A new photo has been uploaded, or an existing photo has
Photo required.
been exchanged.
Trigger Employee Employee photo extraction is triggered by the SAP HCI Background The change in the employee's photo has been extracted
Photo Replication
Update Employee Background The photo record of the employee has been updated au
Photo Record in SAP
tomatically in SAP S/4HANA.
S/4HANA
View Employee Photo Customer SAP Fiori Launchpad URL The updated photo of the employee has been viewed.
Project Manager
Handle Replication Ex The photo of an employee or contingent worker is not re Administrator SFSF EC URL Errors have been corrected and the records of employees
ceptions (Optional) plicated to SAP S/4HANA. have been re-send to SAP S/4HANA.

4 Test Procedures
This section describes test procedures for each process step that belongs to this scope item.
In the following, we split this chapter into four main subchapters:
● the procedure for the cost center replication process

● the procedure for the employee data replication process
● the procedure for the contingent worker data replication process
● the procedure for the employee photo replication process.
4.1 Cost Center Replication
In the following chapters, the procedures for executing the cost center data replication from SAP S/4HANA to SuccessFactors Employee Central are described. The high-level
process is as follows: after executing the preliminary steps as described in chapter Preliminary Steps for Cost Center Replication [page 8], changes to the existing cost center
hierarchy are performed in SAP S/4HANA. The changes are then replicated automatically to SuccessFactors Employee Central, where they can be checked for correctness.
4.1.1 Maintain Cost Center
Test Administration

date.
Business Role(s)


22 © 2016 SAP SE or an SAP affiliate company. All rights reserved. Test Procedures
Context
The Controller maintains one or several cost centers. This may refer to:
● creating a new cost center in an already replicated cost center hierarchy,

● updating an already replicated cost center, including name and description maintenance in different languages,
● delimiting an already replicated cost center.
Note
In all these cases, a delta replication will be triggered: the newly created cost center within the hierarchy or the adaptions performed on the existing cost center will be
transferred to SuccessFactors Employee Central. Delimit of a cost center is mapped to an inactive cost center if previously replicated to SuccessFactors Employee Central.
Prerequisite
The SAP S/4HANA system must support multiple languages.
Procedure
Note
In this procedure, the assumption is that the new and the changed cost centers belong to the same controlling area. In other words, the controlling area selected in test step
# 3 below is considered throughout the entire process step.
Test Step # Test Step Name Instruction Expected Result Pass / Fail / Comment
1 Log on Log on via the SAP Fiori Launchpad to SAP The page containing the Fiori apps associ
S/4HANA as Controller. ated with your role is displayed.
2 Access SAP Fiori App Choose the Manage Cost Centers tile. The Master Data for Cost Center screen is
displayed.

Test Procedures © 2016 SAP SE or an SAP affiliate company. All rights reserved. 23
3 Enter Controlling Area From the drop-down next to your name in the
top right corner of the screen, choose Set
Controlling Area.
In the dialog box, in the Controlling Area field,

select A000 from value help and press the
OK button.
4 Search Existing Cost Centers On the Master Data for Cost Center screen,
enter appropriate selection criteria and
choose the Go button.
From the list of search results, mark a cost

center.
5 Add New Cost Center Choose the Add button located in the bottom A new screen, Cost Center: New, opens in ad
right corner of the screen. dition to the Master Data for Cost Center
screen.
6 Enter Basic Information of New Cost Cen In the New Cost Center section of the screen, You proceed to the next screen for the cost
ter make the following entries: center creation.
Controlling Area: defaults to A000; leave as

is
Cost Center: <cost center ID>
Valid From: <validity start date>
Valid To: defaults to system high date; adapt

if appropriate, else leave as is
In the Reference section of the screen,

choose a controlling area and/or cost center
as reference, if appropriate.
Choose the Continue button.

7 Enter Master Data of New Cost Center In the General Data section make the follow
ing entries:
Cost Center: Enter a cost center name.
Cost Center Description: Enter a cost center

description.
Person Responsible: Enter the cost center

manager.
Cost Center Category: Select from value help.
In the Organizational Units section, make the

following entries:
Hierarchy Area: Select from value help.
Company Code: 1710
Business Area: Select from value help
Currency: USD (by default, based on selected

company code selected), read-only field
Profit Center: Select from value help
8 Save New Cost Center Choose the Save button. The system confirms that data has been
saved.
9 Exit Cost Center Creation screen Close the browser window. You return to the Master Data for Cost Center
page.
10 Search Cost Center to be Changed On the Master Data for Cost Center screen, in The cost centers matching your search crite
the Standard section, enter search criteria ria are listed in the Search Results section of
and choose the Go button. the Master Data for Cost Center screen.
In case no search criterion is entered, all cost

centers existing in the controlling area are
listed.

11 Select Cost Center to be Changed In the Search Results list, mark the cost cen A new screen, Cost Center: <cost center ID,
ter you want to change and choose the Edit cost center name>, opens in addition to the
button located in the bottom right corner of Master Data for Cost Center screen.
the screen.
12 Update Cost Center Data On the Cost Center: <cost center ID, cost The system confirms that data has been
center name> screen, modify, for example, saved.
the description, and choose the Save icon.
13 Exit Cost Center Edit screen Close the browser window. You return to the Master Data for Cost Center
page.
14 Search Cost Center for Multiple Language On the Master Data for Cost Center screen, in The cost centers matching your search crite
Maintenance the Standard section, enter search criteria ria are listed in the Search Results section of

listed.
15 Select Cost Center for Multiple Language In the Search Results list, select the cost cen A new screen, Cost Center: <cost center ID,
Maintenance ter you want to change and choose the Edit cost center name>, opens in addition to the
the screen.
16 Expand Translation and Long Text section On the Cost Center: <cost center ID, cost A table is displayed containing the languages
center name> screen, expand the Translation in which the name, description, and possibly,
and Long Text section. long text description of the chosen cost cen
ter are listed.

17 Maintain Cost Center Name and Descrip Choose Insert and make the following entries: The system confirms that data has been
tion in Multiple Languages saved. The data maintained in multiple lan
Language: For example, German
guages is visible in the Translation and Long
Name: enter translated name as appropriate Text section.
Description: add as appropriate
Note
For adding a long text in the chosen lan
guage, mark the appropriate row in the ta
ble and select the Edit Long Text button.
Repeat this for other languages as required,

for example Chinese, French, Spanish,
and Portuguese. When done, choose the
Save button.
page.
19 Search Cost Center to be Delimited On the Master Data for Cost Center screen, in The cost centers matching your search crite
the Standard section, enter search criteria ria are listed in the Search Results section of

listed.
20 Select Cost Center to be Delimited In the Search Results list, select the cost cen A new screen, Cost Center: <cost center ID,
ter you want to delimit, and choose the Edit cost center name>, opens in addition to the
the screen.
21 Select Validity Period Choose the Validity Periods button and navi The Insert Validity Period dialog box opens.
gate from there to Insert Validity Period.

22 Enter Cost Center Validity End Date In the Valid To field, enter the last day the A success message is generated by the sys
tem about saving the data.
cost center should be active.
Choose the OK button. Then choose the Save

button.
page.
4.1.1.1 Trigger Cost Center Delta Replication
Test Administration

date.
Business Role(s)

Context
Every change in the cost center hierarchy is replicated as a delta load, meaning that only data that has changed since the last synchronization is replicated to SuccessFactors
Employee Central. The frequency of these replications depends on the schedule set for the batch job in the SAP HCI middleware.
The batch job, which has been scheduled in the SAP HCI middleware system on a regular basis, extracts and replicates the cost center data from the SAP S/4HANA system to
SuccessFactors Employee Central. The mapping of the SAP S/4HANA fields to the SuccessFactors Employee Central system is performed in the SAP HCI middleware.
This is an automated step, and no manual execution is required.

4.1.1.2 Update Cost Center Data in SFSF EC
Test Administration

date.
Business Role(s)

Context
The data values have been received by the SuccessFactors Employee Central system where the cost center hierarchy has been updated with the new cost center as well as
existing cost centers.
Note
In order to monitor in SFSF EC if the replication has been successful, you can proceed as follows:
1. Log on to SuccessFactors as Administrator.

2. From the Home drop-down in the left-top corner, choose Admin Center.
3. In the Company Processes & Cycles portlet, choose Company Settings OData API Audit Log .
4. In Filter Options, select all Status checkboxes and select all OData API Call checkboxes.
In the Entity Name section, keep only the FOCostCenter checkbox selected.
Choose the Search button.
5. In the result list displayed on the right side of the screen, select the appropriate entry and choose the REST button to view the request and response messages.

4.1.2 View Cost Center Data
Test Administration

date.
Business Role(s)

Context
The Administrator views if the cost center updates have been replicated correctly to SuccessFactors Employee Central. He or she verifies if the new cost center has been
replicated and if existing cost centers have been updated as expected.
Procedure
1 Log On Log on to SuccessFactors as Administrator. The Home page is displayed.
2 Go to Administration Center From the Home drop-down in the top-left The Admin Center screen is displayed.
corner, choose Admin Center.

3 Go to Manage Data On the Admin Center screen, go in the The Manage Data screen is displayed.
Company Processes & Cycles portlet to
Employee Files and there choose Manage
Data.
Note
You can add this link to your favorites if
you right-click it. You can then choose the
link from the My Admin Favorites portlet
on the Home page, or from the My
Favorites portlet on the Admin Center
screen.
4 Search New Cost Center On the Manage Data screen, in the Search The result is displayed below the Search
field, select Cost Center from the drop- portlet: on the right part of the screen, a port
down list. In the blank field next to the Search let with the current details of the chosen cost
field, search and select the new cost center center is displayed; on the left part of the
you have created in SAP S/4HANA and just screen, the History portlet for this cost center
replicated to SuccessFactors Employee Cen is displayed.
tral.
5 Check New Cost Center Data Check if the new cost center has been repli
cated correctly from SAP S/4HANA.
For details on the field mapping between SAP

S/4HANA and SFSF EC, refer to the table at
the end of chapter Preliminary Steps for Cost
Center Replication [page 8].
6 Search Updated Cost Center On the Manage Data screen, in the Search The result is displayed below the Search
field, select Cost Center from the drop- portlet: on the right part of the screen, a port
down list. From the blank field next to the let with the current details of the chosen cost
Search field, search and select the cost cen center is displayed; on the left part of the
ter you have changed in SAP S/4HANA and screen, the History portlet for this cost center
just replicated to SuccessFactors Employee is displayed.
Central.

7 Check Updated Cost Center Data Check if the changed data, for example, the
description, has been replicated correctly
from SAP S/4HANA.
8 Search Cost Center Updated with Multiple On the Manage Data screen, in the Search The result is displayed below the Search
Language Description field, select Cost Center from the drop- portlet: on the right part of the screen, a port
down list. From the blank field next to the let with the current details of the chosen cost
Search field, search and select the cost cen center is displayed, on the left part of the
ter for which you have maintained the de screen, the History portlet for this cost center
scription in multiple languages in SAP S/ is displayed.
4HANA and just replicated to SuccessFac
tors Employee Central.
9 Check Multiple Language Description of

Cost Center
Select the View Translations icon next
to the Description field.
In the dialog box, verify that the translations

of the cost center description you performed
in SAP S/4HANA have been replicated cor
rectly. When done, choose the Done button.
10 Search Delimited Cost Center On the Manage Data screen, in the Search The result is displayed below the Search
field, select Cost Center from the drop- portlet: on the right part of the screen a port
down list. In the blank field next to the Search let with the current details of the chosen cost
field, search and select the cost center that center is displayed; on the left part of the
you have delimited in SAP S/4HANA and just screen, the History portlet for this cost center
replicated to SuccessFactors Employee Cen is displayed.
tral.
11 Check Delimited Cost Center In case the newest record is not yet displayed
because its validity start is in the future, se
lect it from the History portlet. Verify that the
Start Date field has a date that is one day af
ter the validity end date maintained in SAP
S/4HANA and the Status field has value
InActive.

4.2 Employee Data Replication
In the following subchapters the procedures for executing the employee data replication from SuccessFactors Employee Central to SAP S/4HANA is described.
At high level, this process is as follows: after executing the preliminary steps as described in chapter Preliminary Steps for Employee Data Replication [page 10], hiring data of
new employees is entered into the SuccessFactors Employee Central system. This data is then replicated automatically to the SAP S/4HANA, where it can be checked for
correctness. Because the employee data needs to be always up-to-date, adaptions of the employee's master record can be performed in SuccessFactors Employee Central.
These adaptions are then replicated automatically as delta changes to SAP S/4HANA, where they can be checked for correctness.
During his or her life cycle at the company, the employee might be terminated. For this, termination-specific data is entered SuccessFactors Employee Central. This data is
then replicated automatically to SAP S/4HANA, where it can be checked for correctness.
In some situations, the terminated employee might return to the company. In this case, rehiring data of the rehired employee is entered into the SuccessFactors Employee
Central system. This data is then replicated automatically to SAP S/4HANA, where it can be checked for correctness. Because the employee data needs to be always up-to-
date, adaptions of the employee's master record can be performed in SuccessFactors Employee Central. These adaptions are then replicated automatically as delta changes
to SAP S/4HANA, where they can be checked for correctness.
4.2.1 Enter Hiring Data
Test Administration

date.
Business Role(s)

Context
The HR manager enters hiring data for a newly hired employee. This data includes legally mandated, company-specific, and personal data for the employee.
Note
Execute this step for several new employees in order to check that the master data replication from SuccessFactors Employee Central to SAP S/4HANA works correctly,
particularly if the number of employees exceeds the size of buffers for splitting the employees into batches for replication.
Prerequisites
In order to maintain successfully payment information for the new employee, banks must have been maintained in the system in order to be available in the drop-down.
Procedure
1 Log On Log on to SuccessFactors Employee Central The Home page is displayed.

as an HR manager.
2 Go to Admin Center Screen From the Home drop-down, select Admin The Admin Center screen is displayed.
Center.
3 Add New Employee In the Manage Employees portlet of the You are directed to the My Employee File -
Admin Center screen, choose Update User Add New Employee screen.
Information Add New Employee .
Note
You can add Add New Employee to My
Favorites and start the process from
there.

4 Enter Identity Information for New Em On the Identity section, make the following
ployee entries:
Hire Date: select from calendar help
Company: Company Code 1710 (1710)
Event Reason: New Hire (HIRNEW)
In the Name Information block, make the fol

lowing entries:
First Name: enter as appropriate
for example, Alan
Middle Name: enter as appropriate
Last Name: enter as appropriate
for example, Jon
Suffix: select from the drop-down list, if ap

propriate
Salutation: enter as appropriate
for example, Mr.
Display Name: enter as appropriate
Birth Name: enter as appropriate
In the Employee Information block, make the

following entries:
Person Id: it is recommended to use a num

ber range having as prefix EC in order to
easily find the employee after replication to
SAP S/4HANA. Enter, for example
EC000xxx, with x being a concrete number
Note
This is a (Person Id) External field, which
is used to identify the employee as a per

son. The internal Person Id field is used to

identify the employee in technical com
munication from SFSF EC to SAP S/
4HANA. Both the internal and external
Person ID are forwarded to SAP S/
4HANA. The PersonIDExternal is used as
the ID of the employee for display and
search in SAP S/4HANA.
5 Continue Choose the Continue button. The Personal Information section in the Add
New Employee screen is expanded.
6 Enter Personal Information for New Em In the Personal Information section, make
ployee the following entries:
Gender: select from drop-down, for example

Male
Native Preferred Language: select the Corre

spondence Language from drop-down
Title: select from drop-down if appropriate
Initials: enter if appropriate
Note
Only the information listed above is made
available in SAP S/4HANA, but not fur
ther information like marital status, na
tionality etc.
The resulting personal information stored

in SAP S/4HANA is not time dependent,
since relevant changes in the future are
not expected.

7 Enter Contact Information for New Em In the Email Information block, select the Add
ployee link. The editable fields show up and you can
enter following information:
Email Type: select Business from drop-

down
Email Address: enter as appropriate
Is Primary: defaults to Yes; adapt if appro

priate.
Note
The other available email types are not
relevant for integration with SAP S/
4HANA.
In the Phone Information block, select the

Add link. The editable fields show up and you
can enter following information:
Phone Type: select Business from drop-

down
Country Code: enter +1
Area Code: enter as appropriate, for exam

ple, 303
Phone Number: enter as appropriate
Extension: enter if appropriate
Is Primary: defaults to Yes; adapt if appro

priate.
Note
Phone information relevant for SAP S/
4HANA are Business and Cell. These
two phone types are replicated to SAP S/
4HANA and made there available as part

of the employee workplace address to

gether with the email of type Business.
The maintenance of phone type Cell is
described in chapter Maintain Employee
Contact Information [page 85] .
8 Enter Address Information for New Em In the Home Address block, make the follow
ployee ing entries:
Note
The home address is country-specific.
Depending on the country selected, dif
ferent fields are to be filled.
Address Type: value Home is defaulted, leave

as is
Country: the country where the company is

located, in which the employee is hired is de
faulted. In this case value United States
is defaulted, leave as is
Address Line 1: enter house number and

street name as appropriate, for example, 12
Main Street
Address Line 2: use if needed, for example,

enter an apartment number
City: enter as appropriate, for example,

Denver
County: enter as appropriate, for example,

Denver
State: select from drop-down, for example,

Colorado
ZIP: enter as appropriate, for example,

80204

9 Continue Choose the Continue button. The Job Information section in the Add New
Employee screen is expanded.
10 Enter Organizational Information for New In the Organizational Information block,

Employee make the following entries:
Company: value Company Code 1710

(1710) is defaulted; leave as is
Business Unit: select from drop-down list
Division: select from drop-down list
Department: select from drop-down list
Cost Center: select from drop-down list
Note
Location/Timezone are currently not re
plicated to SAP S/4HANA.

11 Enter Job Information for New Employee In the Job Information block, make the fol Depending on the propagation rule config
lowing entries: ured in your instance, the following fields will
be filled automatically based on the value
Supervisor: select name of supervisor of new
you have chosen for the Job Classification:
employee from drop-down list
Job Title, Pay Grade, and Regular/
Temporary.
Caution
Optional field, but if not filled, the em
ployee cannot be retrieved in the organi
zational structure!
Job Classification: select from drop-down list
Standard Weekly Hours: defaulted based on

value in field Job Classification; adapt if re
quired
FTE: defaulted based on value entered in

field Job Classification; adapt if required
Select the Show <#> more fields link and

make the following entries:
Employee Class: select, for example,

Employee from drop-down.
12 View Employment Details of New Em In the Employment Details block, note that
ployee original start, seniority start, and service
dates default to the hire date entered on the
Identity section.
Note
The Is Contingent Worker field is set to No
and is read-only.
13 Continue Choose the Continue button. The Compensation Information section in the
Add New Employee screen is expanded.

14 Enter Payment Information for new Em In the Payment Information block, the job
ployee country and effective end date of the record
are defaulted and read-only. Select the (+)
Add Details icon. The editable fields show up
and you can enter following information:
Pay Type: select Main Payment Method

from drop-down
Payment Method: select Bank Transfer

(05) from drop-down
Note
Dependent on the payment method
chosen, different editable fields will be
displayed for entering values.
Bank Country: select United States

(US) from drop-down if not already defaulted
Account Owner: enter employee’s name if

not already defaulted

Account Number: enter as appropriate
Routing Number: enter <unique bank

identifier> enter, for example,
10040000
Currency: select USD(USD) from drop-down

if not defaulted upon entering payment
method; currency and country should fit to
each other

15 Submit Data Choose the Submit button, or alternatively A success message is generated by the sys
the Continue button. tem informing you about the hire date of the
new employee. You may choose to view the
employee’s profile, add hiring data of an
other new employee, or simply return to the
home page. A Welcome to
SuccessFactors email is sent automati
cally by the system from your email account
to the new employee containing login infor
mation for the same.
16 View Employee Profile Choose the View profile of <new employee You are directed to My Employee File
name> button.
new <employee name> Personal
Information section.
17 Verify Data Verify the data displayed in the employee The new employee has Employee Status
profile. For example, in the Job Information Active, and data matches what was main
subsection check value of the Employee tained.
Status field.
4.2.1.1 Trigger Employee Master Data Replication 1
Test Administration

date.
Business Role(s)

Context
The batch job, which has been scheduled in the SAP HCI middleware system on a regular basis, extracts and replicates the employee master data from SuccessFactors
Employee Central to the SAP S/4HANA system.
4.2.1.2 Create Employee Master Data Record in SAP S/4HANA
Test Administration

date.
Business Role(s)

Context
Based on the employee information passed from SAP HCI, SAP S/4HANA recognizes that the employee does not exist in the system and creates automatically a business
partner with role Employee. A Vendor (Supplier) is automatically created with the same ID as the business partner for supporting financial processes in SAP S/4HANA, like
travel expense payouts. Basic employee information is made available in SAP S/4HANA in the employee factsheet, whereas the home address replicated to the SAP S/
4HANA system is made available in the vendor created for the business partner of role Employee.

4.2.1.3 Initiate Employee Master Data Replication Confirmation Message 1
Test Administration

date.
Business Role(s)

Context
After the employee master data replication has taken place, the SAP S/4HANA system sends a confirmation message to the middleware (SAP HCI), which processes this
message and sends it to SuccessFactors Employee Central.
4.2.1.4 Receive Employee Master Data Replication Confirmation Message 1
Test Administration

date.
Business Role(s)

Context
The confirmation of the employee master data replication is received by SuccessFactors Employee Centraland can be monitored there.
Note
The success or failure of the master data replication of the new employee can be monitored as described in Monitor Employee Master Data Replication [page 65] .
The master data of the new employee as replicated to the SAP S/4HANA can be viewed and checked for correctness. Refer to View Personnel Master Data [page 67] for
more details.
Note
Continue your testing with process steps Monitor Employee Master Data Replication [page 65] and View Personnel Master Data [page 67]. Afterwards you can maintain
employee information as described in process step Maintain Employee Information [page 83] and subsequent.
4.2.2 Enter Termination Data
Test Administration

date.
Business Role(s)

Context
The HR Manager enters the data of an employee regarding termination of employment.
The reasons for termination are clustered into voluntary and involuntary termination, voluntary separation program, early and normal retirement, or death.
Procedure
1 Log On Log on to SuccessFactors Employee The Home page is dis

Central as an HR manager. played.
2 Search Employee In the People: Search field in the top- The system proposes a
right corner of the page, enter the name list of employees match
(or name parts) of the employee you ing your search criteria.
want to terminate.
3 Select Employee Click in the list of employees the appro You are directed to the
priate employee. Employee Files page in
which the Personal
Information section of the
employee is displayed.
4 Start Termination Action for Employee Choose the Take Action button. From the The Terminate dialog box
value list that appears, choose is displayed.
Terminate.

5 Enter Termination Data for Employee In the Terminate part of the dialog box, All other date fields on
make the following entries: the screen are filled auto
matically with the termi
Termination Date: select employee’s last
nation date.
day at work from the calendar help
Termination Reason:select from drop-

down
OK to Rehire: select from drop-down
Caution
Pay attention to the value in case you
would like to rehire this employee in
the future. In this case, select Yes.
6 Transfer Direct Reports (Optional) In case the employee that is terminated Depending on the value
has direct reports, in the Transfer Direct chosen in the Who should
Reports part of the dialog box, select to the <#> direct report(s)
whom these direct reports should report of <terminated employee
after the supervisor’s termination: name> report to after the
termination? field, differ
Who should the <#> direct report(s) of
ent values than the one
<terminated employee name> report to
given in the example
after the termination?": select, for exam
might have to be entered
ple, Everyone to upper
into the Transfer Event
manager <upper manager
Reason field. In addition,
name> from drop-down.
additional fields to be fil
Transfer Event Reason: select, for exam led might show up; fill
ple, Data Change(DATACHG) from them as appropriate.
drop-down

7 Submit Data Choose the Save button. A system message con

firms that your changes
have been saved. You are
directed to the My
Employee File
<terminated employee
name> Employment
Information screen.
8 Verify Termination of Employee In the Job Information subsection of the The employee has been
Job Information section, verify that terminated and is no lon
Employee Status has value ger active in the system
Terminated. starting one day after the
termination date. This
In case the termination date is in the fu
particular employee is no
ture, you are advertised in the Job
longer available in the re
Information subsection that future
sult list starting one day
change in job information is pending. Se
after the termination date
lect this link and check that the
when searching for em
Employee Status value Terminated
ployees.
becomes effective one day after the en
tered termination date.
Test Administration

date.

Business Role(s)

Context
4.2.2.2 Update Employee Master Data Record in SAP S/4HANA 1
Test Administration

date.
Business Role(s)

Context
Based on the employee information passed from SAP HCI, SAP S/4HANA recognizes that the employee exists in the system and automatically updates the existing master
data record of the business partner with role Employee. The employee will not be available for any follow-up processes in SAP S/4HANA.

Test Administration

date.
Business Role(s)

Context
After the employee master data replication has taken place, the SAP S/4HANA system sends a confirmation message to the middleware (SAP HCI), which processes this
Test Administration

date.
Business Role(s)

Context
The confirmation of the employee master data replication is received by SuccessFactors Employee Central and can be monitored there.
Note
The success or failure of the master data replication of the terminated employee can be monitored as described in Monitor Employee Master Data Replication [page 65] .
The master data of the terminated employee as replicated to SAP S/4HANA can be viewed and checked for correctness. Refer to View Personnel Master Data [page 67]
for more details.
Note
Continue your testing with process steps Monitor Employee Master Data Replication [page 65] and View Personnel Master Data [page 67].
4.2.3 Enter Rehiring Data
Test Administration

date.
Business Role(s)


Context
The HR Manager enters master data of an employee who has previously left the company and was then rehired by the same. This data includes legally mandated, company-
specific, and personal data for the employee.
The employee‘s existing person ID in the system will be reactivated. By using the rehired employee’s old person ID, you will have a continuous history for the employee and
static data, such as the address, which was created as part of the original employee master data, can be re-used.
Prerequisite
The particular employee must exist in your system. He or she must have been already hired (have employment status Active) in the past in order to have a person ID in the
system.
The particular employee must have left previously the company in order to be rehired by the same. The Terminate action type must have been performed with value of field OK
to Rehire set to Yes.
Note
For details on executing the Terminate action type, refer to Enter Termination Data [page 45].
Banks must have been maintained in the system in order to be available in the drop-down in the Payment Information block.
Procedure
1 Log On Log on to SuccessFactors Employee Central as an HR manager. The Home page is dis
played.
2 Go to Admin Center Screen From the Home drop-down, select Admin Center. The Admin Center screen
is displayed.

3 Add New Employee In the Manage Employees portlet of the Admin Center screen, choose You are directed to My
Update User Information Add New Employee . Employee File Add New
Employee screen.
Note
Alternatively, you can choose Update User Information Rehire
Inactive Employee , and on the next screen, select the appropriate
inactive employee name link. Adapt the hiring date as appropriate and
then continue with test step #7

4 Enter Identity Information for New Em On the Identity section, make the following entries: The data entered here is
ployee used by the system to
Hire Date: select from the calendar help
search in the database for
Company: Company Code 1710 (1710) existing employees that
might match. Therefore, at
Event Reason: New Hire (HIRNEW)
least first and last name, or
In the Name Information block, make the following entries: combinations of first name,
last name, and person ID
entered here should be
Middle Name: enter as appropriate correct.
Suffix: select from drop-down if appropriate
Salutation: select from drop-down
In the Employee Information block, make the following entries:
Person Id: enter as appropriate
Note
This is a (Person Id) External field, which is used to identify the em
ployee as a person. The internal Person Id field is used to identify the
employee in technical communication from SFSF EC to SAP S/
4HANA. Both the internal and external Person ID are forwarded to
SAP S/4HANA. The PersonIDExternal is used as the ID of the em
ployee for display and search in SAP S/4HANA.
5 Continue Choose the Continue button. The Duplicate Check dialog

box is displayed listing the
employees matching any
of the data entered in the
Identity section.

6 Select Employee to be Rehired Mark the employee you want to rehire and choose the Accept Match but In the Identity section, the
ton. Name Information block
and the Employee
Caution Information block are pre
The employee you choose must have status Terminated. filled automatically with
data that has been main
tained during the previous
appointment of the em
ployee with the company.
The old person Id is reacti
vated and read-only.
7 Enter Identity Information of Rehired On the Identity section, make the following entry:
Employee
Event Reason: Rehire(REHREH)
In the Name Information block, check if the information is still valid and
adapt it if appropriate.
8 Continue Choose the Continue button. The Personal Information

section in the Add New
Employee screen is ex
panded.

9 Enter Personal Information for Rehired In the Personal Information section, you may decide to accept the data al
Employee ready existing in the system or adapt it as required:
Gender: adapt, if appropriate, by selecting value from drop-down.
Native Preferred Language: adapt the Correspondence Language if ap

propriate by selecting value from drop-down.
Title: adapt, if appropriate, by selecting value from drop-down.
Initials: enter if appropriate.
Note
Only the information listed above is made available in SAP S/4HANA,
but not further information like marital status, nationality etc.
The resulting personal information stored in SAP S/4HANA is not

time dependent, since relevant changes in the future are not ex
pected.
10 Enter Contact Information for Rehired In the Email Information block, review the already existing email of type
Business in the system and adapt if required.
Employee
In the Phone Information block, review the already existing phone type
Business (and possibly Cell) in the system and adapt if required.
Note
The phone types Business (and Cell) and the email of type
Business are made available as part of the employee workplace ad
dress in SAP S/4HANA.

11 Enter Address Information for Rehired In the Home block, review the data already existing in the system and
Employee adapt it if required.
Note
The home address is country-specific. Depending on the selected
country, different fields are to be filled.
Country: default value is the country where the company in which the em
ployee is rehired is located. In this case, default value is United
States, leave as is
Create entries as appropriate in the following fields: Address Line 1,

Address Line 2, City, County, State, ZIP
Note
In case there is also a Home Address block visible, delete it using the
Trash Bin icon.
12 Continue Choose the Continue pushbutton. The Job Information sec

tion in the Add New
Employee screen is ex
panded.

13 Enter Organizational Information for In the Organizational Information block, review the data as taken over
Rehired Employee from the existing master data record of the rehired employee and adapt
as appropriate:
Company: value Company Code 1710 (1710) is defaulted; leave as is
Business Unit: adapt, if appropriate, by selecting from drop-down
Division: select from drop-down
Department: select from drop-down
Cost Center: adapt, if appropriate, by selecting from drop-down
Note
Location/Timezone are currently not replicated to SAP S/4HANA.
14 Enter Job Information for Rehired Em In the Job Information block, review the data as taken over from the exist Dependent on the propa
ployee ing master data record of the rehired employee. and adapt as appropri gation rule configured in
ate: your instance, following
fields will be auto-popu
Supervisor: select name of supervisor of rehired employee from drop-
lated from the value you
down
have chosen for the Job
Classification: Job Title,
Caution
Pay Grade, and Regular/
Optional field, but if not filled, the employee cannot be retrieved in the Temporary.
organizational structure!
Job Classification: adapt if appropriate by selecting from drop-down
Standard Weekly Hours: defaulted based on value in field Job

Classification; adapt if required
FTE: defaulted based on value entered in field Job Classification; adapt if

required.
Select the Show <#> more fields link and make the following entries:
Employee Class: select, for example, Employee from drop-down

15 View Employment Details for Rehired In the Employment Details block, note that the seniority start date and
Employee service date are defaulted to the rehiring date, whereas the original start
date defaults to the date when the employee joined the company for the
first time.
Note
Field Is Contingent Worker is set to No and is read-only.
16 Continue Choose the Continue button. The Compensation

Information section in the
Add New Employee screen
is expanded.

17 Enter Payment Information for Rehired In the Payment Information block, , the job country and effective end date
Employee of the record are defaulted and read-only. Check if the data as taken over
from the master data record that was maintained during the employee’s
previous employment at the company is still valid. If not, adapt it accord
ingly.
Select the (+) Add Details icon. The editable fields show up and you can
enter following information:
Pay Type: select Main Payment Method from drop-down
Payment Method: select Bank Transfer (05) from drop-down
Note
Dependent on the payment method chosen, different editable fields
will be displayed for entering values.
Bank Country: select United States (US) from drop-down if not al
ready defaulted
Account Owner: enter employee’s name if not already defaulted
Select the Show <#> more fields link and make the following entries:
Routing Number: <unique identifier of the bank>; enter,

for example, 011000390
Account Number: enter as appropriate
Currency: select USD if not already defaulted upon entering payment

method; currency and country should fit to each other.
In case pay type Expenses has been maintained during the employee’s
previous employment at the company, verify if it is still valid, else adapt it
or delete it (for this choose the Trash Bin icon next to the record.

18 Submit Data Choose the Submit button, or alternatively the Continue button. A success message is gen
erated by the system, in
forming you about the hire
date of the rehired em
ployee. You may choose to
view the employee’s pro
file, add hiring data of an
other new employee, or
simply return to the home
page.
A Welcome to
SuccessFactors email
is sent automatically by the
system from your email ac
count to the new employee
containing login informa
tion for the same.
19 View Employee Profile Choose the View profile of <rehired employee name> button. You are directed to My
Employee File <rehired
employee name>
Personal Information
section.
20 Verify Data Verify the data displayed in the employee profile. For example, in the Job The rehired employee has
Employee Status Active,
Information subsection check value of field Employee Status.
and data matches what
In case the rehire date is in the future, you are advertised in the Job Infor was maintained.
mation subsection that future change in job information is pending. Se
lect this link and check that the Employee Status value Active becomes
effective on the rehire date entered.

Test Administration

date.
Business Role(s)

Context
4.2.3.2 Update Employee Master Data Record in SAP S/4HANA 2
Test Administration

date.
Business Role(s)

Context
Based on the employee information passed from SAP HCI, SAP S/4HANA recognizes that the employee exists in the system and updates automatically the existing master
data record of the business partner with role Employee. In addition, the available data of the vendor (supplier) created during initial replication for supporting financial
processes in SAP S/4HANA, like travel expense payouts, is updated accordingly.
Test Administration

date.
Business Role(s)

Context
After the replication of employee master data has taken place, the SAP S/4HANA system sends a confirmation message to the middleware (SAP HCI), which processes this

Test Administration

date.
Business Role(s)

Context
The confirmation of the employee master data replication is received by SuccessFactors Employee Central and can be monitored there.
Note
The success or failure of the master data replication of the rehired employee can be monitored as described in Monitor Employee Master Data Replication [page 65] .
The master data of the rehired employee as replicated to SAP S/4HANA can be viewed and checked for correctness. Refer to View Personnel Master Data [page 67] for
more details.
Note
Continue your testing with process steps Monitor Employee Master Data Replication [page 65] and View Personnel Master Data [page 67]. Afterwards you can
maintain employee information as described in process step Maintain Employee Information [page 83] and subsequent.

4.2.4 Monitor Employee Master Data Replication
Test Administration

date.
Business Role(s)

Context
The HR Manager monitors the success or failure of the creation of the master data record of the newly hired employee, as well as the update of the master data record of the
terminated and/or rehired employee in the SAP S/4HANA system. For this, he or she views the replication status for each employee to see if there are any failed jobs.
Procedure
1 Log On Log on to SuccessFactors Employee Central The Home page is dis

as an HR manager. played.
2 Go to Admin Center Screen From the Home drop-down, select Admin The Admin Center screen
Center. is displayed.
3 Go to Data Replication Monitor In the Company Processes & Cycles block of The Data Replication
the Admin Center screen, go to Employee Monitor screen is dis

played.
Files Monitor S/4HANA Master Data
Integration .

4 Select Display Options Select the following display options, and The replications from the
then, choose the Apply button: last hour are shown in
the Standard View part of
Replication Status: select all checkboxes
the Data Replication
Selection Criteria: leave all selection criteria Monitor screen.
as No Selection
Replication Time: select the Last Hour radio

button to view the log from the last hour
5 Check Status of Jobs Ensure that all jobs have the replication sta Possibly existing unsuc
tus Successful.
cessfully processed repli
If there are any jobs with replication status cation requests have
Failed, click the Replication Status to view been identified and are to
the error message. be solved as described in
process step Maintain
Fix these errors by correcting the employee
Employee Information
data in SFSF EC as described in chapter
[page 83]. The
Maintain Employee Information [page 83].
changed data will then be
Refer also to the note below this procedure
replicated automatically
table.
as delta information by
If the errors are due to the fact that for exam the batch job, which has
ple during bulk transfer of employees an em been scheduled in the
ployee with manger assignment is transfer SAP HCI middleware sys
red before the corresponding manager was tem on a regular basis.
transferred to SAP S/4HANA, continue with Process step Maintain
test step # 6. Employee Information
[page 83] needs to be
repeated until all jobs
have replication status
Successful.
6 Re-Send Employee Data (Optional) The data of employee does not need to be The employee is transfer
changed. Instead, in the Standard View part red again to SAP S/
of the Data Replication Monitor screen flag 4HANA; data of em
the checkbox(es) in the Select column on the ployee does not need to
left of the employee name(s) and press the be changed.
Send button.

Note
You can verify the status of each SOAP message sent between the applications and view them in detail. For this, proceed as follows:
1. On the Admin Center screen, navigate to Company Processes & Cycles Company Settings SFAPI Audit log
2. In Filter Options flag all Status checkboxes, SFAPI Call checkboxes, and Object checkboxes. Click the Search button.
3. In the result list displayed on the right side of the screen, select the appropriate entry related to compoundemployee, fo_businessunit, fo_division, and
fo_department (make sure the four entries mentioned have similar timestamps) and click on the SOAP button to view the request and response messages.
In case you want to view the detailed confirmation and/or confirmation error message, you can proceed as follows:
1. On the Admin Center screen, navigate to Company Processes & Cycles Company Settings OData API Audit log .
2. In Filter Options flag all Status checkboxes, flag all OData API Call checkboxes, and in the Entity Name section keep only the EmployeeDataReplicationConfirmation
and/or EmployeeDataReplicationConfirmationErrorMessage checkbox flagged. Click the Search button.
3. In the result list displayed on the right side of the screen select the appropriate entry and click on the REST button to view the request and response messages.
4.2.5 View Personnel Master Data
Test Administration

date.
Business Role(s)

Context
The Customer Project Manager validates the replicated data of the new, rehired, and terminated employees in SAP S/4HANA to make sure the employee data is in-sync
between SuccessFactors Employee Central and SAP S/4HANA.
In the following subchapters, we detail the procedure for each type of employee data maintained during hiring, termination or rehiring, and replicated to SAP S/4HANA.
4.2.5.1 View Employee Basic Data
Test Administration

date.
Business Role(s)

Context
The Customer Project Manager views the basic data of the employee as replicated from SuccessFactors Employee Central. This data includes name information,
organizational information, and communication information. In the following, the procedure is divided into three parts: for hired, terminated, and rehired employees.
Procedure for hired employees
1 Log On Log on via the SAP Fiori Launchpad to SAP The page containing the Fiori apps associ
S/4HANA as Customer Project Manager. ated with your role is displayed.

2 Search Employee On the top right-corner of the screen, next to On the Search Results screen, the system
your name, select the Search (magnifying proposes a list of employees matching your
glass) icon. In the two editable search fields, search criteria. For each employee a short
make the following entries: overview of organizational details is given,
like company code, cost center, and organi
All: select Employees from drop-down
zational unit to which they are assigned, as
Search In: Employee Search: enter <full well as the job title.
name> or <*full name parts*> or
<person ID> of the employee and press
Enter .
3 Select Employee On the Search Results screen, choose the You are directed to the employee's fact
<employee name> link of the employee sheet.
whose data you want to view, for example,
Alan Jon.
4 View Identity and Personal Information In the page header check that the identity
and personal information are correctly trans
ferred. For example, check the employee's
first name, last name, middle name, initials,
formal name, person ID as maintained in
SFSF EC.
5 View Communication Details In the Communications subsection of the

General Information section, verify the cor
rectness of the following replicated data:
● check that the phone information of type

Business has been correctly transfer
red; this is visible in the Phone field.
● check that email address of type
Business has been correctly transfer
red; this is visible in the Email field.

6 View Employment Details In the Employments section, verify the cor

rectness of the following replicated data:
● Company:
● From/To: hire date/system high date.
● Job Title:
● Manager: (value of this field should con
tain value of field Supervisor from Suc
cessFactors Employee Central).
● Organizational Unit: (value of this field
should contain value of the Department
field from SuccessFactors Employee
Central. In case Department is not main
tained in SuccessFactors Employee
Central, the value from Division is taken.
If Division is also not maintained, the
value from Business Unit is taken.).
● Cost Center: <enter cost
center>
● Verify that value of field Employment
Status is Active.
Note
This data, except From/To, is visible also
in the Basic Data subsection of the
General Information section.
Note
If required, you can also check in the
Employments section the fields
Employmentinternalid and/or
Personnelnumber, which contain the ap
propriate IDs of the employee as main
tained in the S/4HANA system. For this
choose on top of the Employments table
the Settings icon, flag the appropriate
checkboxes, and choose OK.

Note
The Technical Support in the SAP Service Center can check in the SAP S/4HANA backend system if additional basic data, like for example title or gender, has been
correctly replicated from SuccessFactors Employee Central. For this, he or she can proceed as follows:
● Log on to the SAP S/4HANA backend system/client and enter transaction code se16.
● On the Data Browser: Initial Screen, in the Table Name field enter value IEMPLOYEE and choose Enter .
● On the Data Browser: Table IEMPLOYEE: Selection Screen, enter selection criteria as appropriate: for example, enter in the Last Name field the <last name> or
<*last name parts*> of the employee who has been hired in SFSF EC.
● Choose the Execute icon, or alternatively F8 .
● Mark the record of the employee of interest and choose the Display icon, or alternatively F7 .
● View and check the correctness of the data of the hired employee as replicated from SFSF EC, for example academic title, correspondence language, gender.
● Check also the correctness of the business partner role: for a regular employee it should have value BUP003(Employee).
Note
As mentioned in test step #6 in the above table, the Organizational Unit visible on the employee's fact sheet is filled with the value of the lowest organizational unit
maintained in SuccessFactors Employee Central, most likely the Department. Nevertheless, the superordinate organizational units, like division and business unit, are also
replicated to the SAP S/4HANA system. The Technical Support in the SAP Service Center can also check in the SAP S/4HANA backend system if these have been
● On the Data Browser: Initial Screen, in the Table Name field enter value /SHCM/HRP5090 and choose Enter .
● On the Data Browser: Table /SHCM/HRP5090: Selection Screen enter in the Object ID field the value available in the Employmentinternalid field in the employee's fact
sheet. Choose the Execute icon, or alternatively F8 .
● Mark the record of the employee and choose the Display icon, or alternatively F7 .
● View and check the correctness of the data visible in the fields Department ID, Department Name, Division ID, Division Name, Bus. Unit ID, and Bus. Unit Name.
● Check also the value of field Employment Status; it should be 1 (Active).
Procedure for terminated employees

2 Search Employee On the top right-corner of the screen, next to On the Search Results screen, the system
your name, select the Search (magnifying proposes a list of employees matching your
glass) icon. In the two editable search fields, search criteria.
In case the employee has already status
All: select Employees from drop-down Terminated in SFSF EC on the date you
search for him or her, this employee should
Search In: Employee Search: enter <person
not show up in the search result list. In this
ID>, <full name> or <*full name
case, the technical support in the SAP serv
parts*> of the terminated employee and ice center can proceed as described in the
press Enter . note below this table.
In case the employee is terminated on a fu

ture date than the date you search for him or
her, continue with test step # 3 and subse
quent.
whose data you want to view.
4 View Employment Details In the Employments section, two records

should be visible: one for the employee's ac
tive period at the company, and one for the
period in which the employee is not anymore
with the company.
Verify that for the active period, the To date

coincides with the termination date as main
tained in SFSF EC and the Employment
Status has value Active.
Verify that for the inactive period, the From

date coincides with one day after the termi
nation date as maintained in SFSF EC, the To
date coincides with the system high date,
and the Employment Status has value
Inactive.

Note
The Technical Support in the SAP Service Center can check in the SAP S/4HANA backend system if termination-related data has been correctly replicated from
SuccessFactors Employee Central. For this, he or she can proceed as follows:
● On the Data Browser: Initial Screen, in the Table Name field enter value IEMPLOYEE and choose Enter .
● On the Data Browser: Table IEMPLOYEE: Selection Screen enter selection criteria as appropriate: for example, enter in the Last Name field the <last name> or <*last
name parts*> of the employee who has been terminated in SFSF EC. Choose the Execute icon, or alternatively F8 .
● Note down the value in field Int. Person No.
● Go back to the Data Browser: Initial Screen, enter in the Table Name field value IEMPLOYDETCUR and choose Enter . On the Data Browser: Table IEMPLOYDETCUR:
Selection Screen enter the Int. Person No. the value you have noted down in the previous step and choose F8 . Check that the Employment Status has value 0 (meaning
Inactive).
Alternatively, the Technical Support in the SAP Service Center can check the content of table /SHCM/HRP5090 for the terminated employee:
● On the Data Browser: Table /SHCM/HRP5090: Selection Screen enter in the Object ID field the employment internal ID of the terminated employee. Choose the
Execute icon, or alternatively F8 .
● Two records for the terminated employee should be available:
● one for the period in which the employee was active in the company: value of field Employment Status is 1 (Active)
● one for the period in which the employee is no longer with the company: value of field Employment Status is 0 (Inactive).
Procedure for rehired employees

2 Search Employee fieldOn the top right-corner of the screen, In the Search Results screen, the system pro
poses a list of employees matching your
next to your name, select the Search (magni
search criteria. For each employee a short
fying glass) icon. In the two editable search
overview of organizational details is given,
fields, make the following entries: like company code, cost center, and organi
well as the job title.
Search In: Employee Search: enter <full
name> or <*full name parts*> or
<person ID> of the employee and press
Enter .
whose data you want to view.
and personal information are correctly trans
ferred. For example, check the employee's
first name, last name, middle name, initials,
formal name, person ID as maintained in
SFSF EC.

General Information section verify the cor
rectness of following replicated data:
Check that the phone information of type

Business has been correctly transferred:
this is visible in the Phone field;
Check that email address of type Business

has been correctly transferred; this is visible
in the Email field.

6 View Employment Details In the Employments section, three records

should be visible: one for the employee's first
appointment at the company, one for the pe
riod in which the employee was not anymore
with the company, and one for the period in
which the employee is again with the com
pany.
Verify that for the inactive period, the To date

coincides with the last day before the rehire
date as maintained in SFSF EC and the
Employment Status has value Inactive.
Verify the correctness of following replicated

data for the period in which the employee is
again with the company:
● Company:
● From/To: rehire date/system high date.
● Job Title:
● Manager: (value of this field should con
tain value of field Supervisor from Suc
cessFactors Employee Central)
● Organizational Unit: (value of this field
should contain value of field Department
from SuccessFactors Employee Central.
In case Department is not maintained in
SuccessFactors Employee Central, the
value from Division is taken. If Division is
also not maintained, the value from
Business Unit is taken).
● Cost Center:
● Verify that value of field Employment
Status is Active.

Note
The current valid data, except From/To, is
visible also in the Basic Data subsection of
the General Information section.
Note
propriate IDs of the employee as main
tained in the S/4HANA system. For this
choose on top of the Employments table
the Settings icon, flag the appropriate
Note
● On the Data Browser: Initial Screen, in the Table Name field enter value IEMPLOYEE and choose the Enter .
● On the Data Browser: Table IEMPLOYEE: Selection Screen, enter selection criteria as appropriate: for example, enter in the Last Name field the <last name> or
<*last name parts*> of the employee who has been rehired in SFSF EC.
● Choose the Execute icon, or alternatively F8 .
● Mark the record of the employee of interest and choose the Display icon, or alternatively F7 .
● View and check the correctness of the data of the rehired employee as replicated from SFSF EC, for example academic title, correspondence language, gender.
● Check also the correctness of the business partner role: for a regular employee it should have value BUP003(Employee).
Note
As mentioned in test step #6 in the above table, the Organizational Unit visible on the employee's fact sheet is filled with the value of the lowest organizational unit
maintained in SuccessFactors Employee Central, most likely the Department. Nevertheless, the superordinate organizational units, like division and business unit, are also

replicated to the SAP S/4HANA system. The Technical Support in the SAP Service Center can also check in the SAP S/4HANA backend system if these have been
● On the Data Browser: Table /SHCM/HRP5090: Selection Screen enter in the Object ID field the value available in the Employmentinternalid field in the employee's fact
sheet. Choose the Execute icon, or alternatively F8 .
● Three records for the rehired employee should be available:
● one for the period in which the employee was previously active in the company: value of field Employment Status is 1 (Active)
● one for the period in which the employee is no longer with the company: value of field Employment Status is 0 (Inactive).
● one for the period in which the employee is again active in the company: value of field Employment Status is 1 (Active). Mark this record and choose the Display icon,
or alternatively F7 . View and check the correctness of the data visible in the fields. View and check the correctness of the data visible in the fields namedDepartment
ID, Department Name, Division ID, Division Name, Bus. Unit ID, and Bus. Unit Name.
Note
In the SAP S/4HANA backend, you can switch between the Field Name (meaning technical name) and the Field Label (meaning semantic name) as follows:
● in the menu on top of the Data Browser: Initial Screen navigate to Settings User Parameters … ;
● in the upcoming User-Specific Settings dialog box or Data Browser tab go to the Keyword section and check either the Field Name or Field Label radio-button as per your
needs;
● choose Enter .
4.2.5.2 View Employee Payment Information
Test Administration

date.
Business Role(s)

Context
Caution
This information is not relevant for terminated employees.
For each employee replicated from SuccessFactors Employee Central a business partner is created in SAP S/4HANA. The factsheet of the created business partner contains
among other information also data related to the employee's payment details and address. The Customer Project Manager views the payment information of the employee as
replicated from SuccessFactors Employee Central.
Procedure
ated with your role is displayed.
S/4HANA as Customer Project Manager.
2 Open Maintain Business Partner App In the Master Data - Business Partner section An additional page opens, containing the
click on the Maintain Business Partner tile. Maintain Business Partner screen.

3 Search Employee On the left part of the screen select the Find In the Description section below the search
tab and make following entries in the search fields, the system proposes a list of employ
fields: ees matching your search criteria.
Find: select Business Partner or

Persons from drop-down
By: select Name from drop-down
Make entries in one of the below fields:
Last name: enter <last name> of the em

ployee
First name: enter <first name> of the

employee
Select the Start button.
4 Select Employee In the Description section, double click on the The details of the selected employee are
<employee name> link of the employee shown in the right part of the screen. Per de
whose data you want to view, for example, fault, the data for the Business Partner
Alan Jon. (Gen.) role is displayed. The section of the
screen contains several tabs, like Address,
Address Overview, Identification, and
Payment Transactions.
5 Go to Payment Transactions Go to the Payment Transactions tab. The Payment Transactions tab is displayed,
containing two sections: Bank Details and
Payment Cards.
6 View Payment Information In the Bank Details section, the data main
tained in SFSF EC for pay type Main
Payment Method is displayed. It contains
bank key, account number, name of financial
institution, and validity period.
To view additional details of the record, mark

it and choose the Bank Data button. In the
upcoming Bank Data window, view the data.
When done, choose the X (Close) button.

4.2.5.3 View Employee Address Information
Test Administration

date.
Business Role(s)

Context
Caution
This information is not relevant for terminated employees.
among other information also data related to the employee's payment details and address.
The Customer Project Manager views the address information of the employee as replicated from SuccessFactors Employee Central.
Procedure
1 Log on Log on via the Fiori SAP Launchpad to SAP The page containing the Fiori apps associ


Person from drop-down
By: select Name from drop-down.

ployee.

employee.
5 Go to Address Go to the Address tab. The Address tab is displayed, containing sev
eral sections.
6 View Address Information In the Street Address section, the data main
tained in SFSF EC for the Home Address is
displayed. Check the correctness of the repli
cated data. The mapping between the ad
dress fields in SFSF EC and those in SAP S/
4HANA is given in the note below.

Note
Home address fields in SFSF EC and their mapping to the SAP S/4HANA fields are given in the table below:
United States SFSF EC Fields SAP S/4HANA Business Partner Factsheet SAP S/4HANA Backend Fields
Country Country COUNTRY
Address Line 1 Street/House number STREETNAME
Address Line 2 Street 4 STREETSUFFIXNAME
City City CITYNAME
County District DISTRICT
State Region REGION
ZIP Postal Code POSTALCODE
Note
The check of the SAP S/4HANA backend fields should be performed only by the Technical Support in the SAP Service Center. The procedure is as follows:
1. Log on to the SAP S/4HANA backend system/client and enter transaction code se16.
2. On the Data Browser: Initial Screen, in the Table Name field enter value IEMPLHOMEADDRSS and choose Enter .
3. On the Data Browser: Table IEMPLHOMEADDRSS: Selection Screen enter selection criteria as appropriate: for example, enter in the Full Name field the <full name> or
<*full name parts*> of the employee who has been just hired or rehired in SFSF EC. Choose the Execute icon, or alternatively F8 .
4. On the Data Browser: Table IEMPLHOMEADDRSS: Select Entries <#> screen mark the record of the employee of interest, for example, Alan Jon, and choose the
Display icon, or alternatively F7 .

4.2.6 Maintain Employee Information
Test Administration

date.
Business Role(s)

Context
The HR Manager maintains master data of the employee in the SuccessFactors Employee Central system. The information contained in the employee file needs to be up-to-
date, so the HR Manager creates new records and adapts existing ones as appropriate.
In the following subchapters, we detail the maintenance procedure for several types of employee data.
Caution
Maintenance of employee data is relevant only for active employees! For the employees, which have been terminated as described in chapter Enter Termination Data [page
45] , chapters Maintain Employee Information [page 83], Monitor Employee Master Data Delta Replication [page 96] and View Updated Personnel Master Data [page
98] are not relevant!
Note
Every change in the employee data is replicated as a delta load, that is, only employee data that has changed in SuccessFactors Employee Central since the last
synchronization is replicated to SAP S/4HANA. The frequency of these replications depends on the schedule that has been set for the batch job in the SAP HCI middleware
system. In the following, we describe these automated process steps only once, after the last maintenance process step described in this chapter.

Procedure
For maintaining employee information, the HR Manager needs to select the particular employee first. In order not to overload the procedure for each step with details to
searching and selecting the employee, we describe it in detail below:

as an HR manager.
2 Search for Employee In the People Search field on the top-right The system proposes a list of employees
corner of the screen, enter the name (or matching your search criteria.
name parts) of the employee whose data you
want to maintain.
3 Select Employee Choose the appropriate employee from the You are directed to the Employee Files page,
list, for example, Alan Jon. on which the employee's existing data record
is divided into several sections: Personal
Information, Employment Information, and
Payment Information. The default view is the
Personal Information section.
4 Continue Continue with the procedure as described in:
Maintain Employee Contact Information

[page 85]
Maintain Employee Supervisor [page 87]
Maintain Employee Payment Information

[page 88]
Maintain Employee Address Information

[page 91]

4.2.6.1 Maintain Employee Contact Information
Test Administration

date.
Business Role(s)

Context
The HR Manager maintains the contact information of the employee as necessary.
In this document, we consider, as example, the phone information of the employee. Phone information relevant for SAP S/4HANA are Business and Cell. These two phone
types are replicated to SAP S/4HANA and made available as part of the employee workplace address in SAP S/4HANA together with the email of type Business. During
entering hiring data for the employee, the phone type Business has been created. In this chapter, we will refer to creation of phone type Cell, as well as updating phone type
Business.
Procedure
1 Edit Contact Information In the Contact Information subsection of the The Contact Information dialog box is dis
Personal Information section, select the played.
Pencil icon next to the Contact Information
block.

2 Create New Phone Information Record In the Phone Information part of the dialog
box select the (+) Add link and make the fol
lowing entries:
Phone Type part of the dialog box select the

link and make the following: select Cell
from drop-down
Country Code: enter as appropriate
Area Code: enter as appropriate
Extension: enter as appropriate
Is Primary: defaults to Yes; adapt if appropri

ate
Note
Only one phone type maintained for the
employee is to be classified as primary.
3 Save Data Choose the Save button. A system message is generated about suc
cessful saving of the data. The data is visible
in the employee’s file. The primary phone
type is marked with a star. part of the dialog
box select the
4 Update Existing Phone Information Record Adapt the existing information of phone type A system message is generated about suc
(Optional) Business if needed. When done, choose
in the employee’s file.
the Save button.

4.2.6.2 Maintain Employee Supervisor
Test Administration

date.
Business Role(s)

Context
The HR Manager maintains in the employee's file a new supervisor.
Caution
We only consider the case that the employee's current supervisor is replaced by a new supervisor. Reasons for replacing the supervisor can be, for example, retirement,
termination, or transfer of the supervisor him- or herself. The employee does not experience any transfer or any other change in job information! This process step is for
testing purposes only to verify that the replication to SAP S/4HANA works properly.
Procedure
1 Edit Job Information Go to the Employment Information section The Job Information dialog box is displayed.
and in the Job Information subsection select
the Pencil icon next to the Job Information
block.

2 Enter Effective Date Enter effective date of change:
When do you want your changes to take

effect?: select using calendar icon.
3 Enter Event and Event Reason Event: select Data Change from drop-
down
Event Reason: select Data

Change(DATACHG) from drop-down.
4 Enter Employee's New Manager In the Job Information part of the dialog box
Supervisor: select from drop-down.
in the employee’s file. In case the change in
supervisor takes place at a future date, you
are advertised in the Job Information subsec
tion that future changes are pending.
6 View Future Dated Changes (Optional) Click on the Pending future change in Job
Information (<data>) link in the Job
Information subsection. In the upcoming Job
Information Changes dialog box, select the
History icon. In the Change History part of the
dialog box, select the appropriate record and
check if the new supervisor is displayed as
expected.
4.2.6.3 Maintain Employee Payment Information
Test Administration

date.
Business Role(s)

Context
The HR Manager maintains payment information of the employee. This data is then replicated to the SAP S/4HANA system where it is required for controlling payout of
expenses.
In the United States, it is common that a separate payment method is defined for payout of expenses (check or a bank account (typically a credit card account)). This can be
defined in the HR system.
In the following, the maintenance of pay type Expenses with payment method Check is described.
Procedure
1 Edit Payment Information Go to the Payment Information section and The Payment Information dialog box is dis
select the Pencil icon next to the Payment
played.
Information block.
2 Enter Effective Date Enter effective date of change:
When do you want your changes to take

effect?: select using calendar icon
3 Add New Record Select the Add link in the bottom left corner The fields for adding new data become edita
of the Payment Information dialog box. ble below the already existing record.

4 Create New Payment Information Record In the Details part of the Payment Information
dialog box, make the following entries:
Pay Type: select Expenses from drop-down
Payment Method: select Check(06) from

drop-down.
Note
Dependent on the payment method
chosen, different editable fields will be dis
played for entering values.

Currency: defaulted to USD(USD) upon en

tering Pay Type; adapt if appropriate
Note
For integration into SAP S/4HANA neither
Percentage nor Amount is supported. For
a given effective start date, only a single
record of type Expenses should be cre
ated. The integration picks up one, but
currently does not consider other entries.
cessful saving of the data.
6 View New Future Dated Payment Informa In case the newly added payment informa
tion Record (Optional) tion is effective on a future date, select in the
Payment Information block the Clock icon.
In the Change History part of the upcoming

Payment Information: Changes dialog box,
select the appropriate record and check if the
newly added payment information is dis
played as expected.

4.2.6.4 Maintain Employee Address Information
Test Administration

date.
Business Role(s)

Context
The HR Manager maintains the address information of the employee as necessary. He or she updates the existing home address data for a specified employee.
The home address is needed in the SAP S/4HANA system for supporting check payout to the employee, such as payout of travel expenses by check. For this purpose, the
employee home address is replicated to the SAP S/4HANA system and made available in the vendor created for the employee. The home address can be maintained time
dependently in SuccessFactors Employee Central, but only the current address is shown at the vendor. This is achieved through a scheduled job in SAP S/4HANA handling
maintenance of addresses into the future in SuccessFactors Employee Central.
Note
The home address is country-specific. Depending on the country selected, different fields are to be filled.

Procedure
1 Edit Address Information In the Address Information subsection of the The Home Address dialog box is displayed.
Personal Information section, select the
Pencil icon next to the Addresses block.
2 Enter Effective Change Date In the Home Address dialog box, enter an ef
fective date of change:
When would you like your changes to take

effect: select using the calendar icon
3 Create New Home Address Record In the Home part of the dialog box make the
following entries:
Country: United States , leave as is
Address Line 1: enter house number and

street name as appropriate, for example, 12
Main Street
Address Line 2: use if needed, for example,

enter an apartment number
City: enter as appropriate, for example, Los

Angeles
County: enter as appropriate, for example,

Los Angeles
State: select from drop-down, for example,

California
ZIP: enter as appropriate, for example,

90001
4 Save Data Choose the Save button. A system message confirms that the data
has been saved. The data is visible in the em
ployee’s file. In case the changes are effec
tive on a future date, select the Pending
future change in Home Address (mm/dd/yy)
link to view the changes.

Note
In case you need to correct an existing home address rather than entering a new effective dated home address, proceed as follows:
● In the Address Information subsection of the Personal Information section, select the Clock icon next to the Addresses block.
● In the Change History part of the upcoming dialog box, select the record you want to correct and choose the Edit button.
● In the Edit History of Home Address on <effective start date> dialog box leave the date as is and make the appropriate correction. When done, choose the Save button.
4.2.6.4.1 Trigger Employee Master Data Delta Replication
Test Administration

date.
Business Role(s)

Context
Every change in the employee master data is replicated as a delta load, meaning that only data that has changed since the last synchronization is replicated to SAP S/4HANA.
The frequency of these replications depends on the schedule set for the batch job in the SAP HCI middleware. The batch job replicates the changed employee master data
(like contact information, payment information, and address information) from SuccessFactors Employee Central to the SAP S/4HANA system.

4.2.6.4.2 Update Employee Master Data Record in SAP S/4HANA 3
Test Administration

date.
Business Role(s)

Context
Based on the employee information passed from SAP HCI, SAP S/4HANA recognizes that the employee exists in the system and automatically updates the existing master
data record of the business partner with role Employee. In addition, the available data of the supplier (vendor) created during initial replication for supporting financial
processes in SAP S/4HANA, like travel expense payouts, is updated accordingly.
4.2.6.4.3 Initiate Changed Employee Master Data Replication Confirmation Message
Test Administration

date.

Business Role(s)

Context
After the replication of changes in employee master data has taken place, the SAP S/4HANA system sends a confirmation message to the middleware (SAP HCI), which
processes this message and sends it to SuccessFactors Employee Central.
4.2.6.4.4 Receive Changed Employee Master Data Replication Confirmation Message
Test Administration

date.
Business Role(s)

Context
The confirmation of the replication of changed employee master data is received by SuccessFactors Employee Central and can be monitored there.

4.2.7 Monitor Employee Master Data Delta Replication
Test Administration

date.
Business Role(s)

Context
The HR Manager monitors the success or failure of the update of the employee’s master data record in the SAP S/4HANA system. For this, he or she checks the replication
status for each employee to see if there are any failed jobs.
Procedure

as an HR manager.
Center.
3 Go to Data Replication Monitor In the Company Processes & Cycles block of The Data Replication Monitor screen is dis
the Admin Center screen, go to Employee played.
Integration .

4 Select Display Options Select the following display options, and The replication jobs from the last hour are
then, choose the Apply button: shown in the Standard View part of the Data
Replication Monitor screen.
Replication Status: select all checkboxes
Selection Criteria: leave all selection criteria

as No Selection
Replication Time: check radio button Last

Hour to view the log from the last hour
5 Check Status of Jobs Ensure that all jobs have the replication sta Any existing replication requests that have
tus Successful. not been processed have been identified and
are to be solved as described in process step
If there are any jobs with replication status
Maintain Employee Information [page 83].
Failed, click the Replication Status to view
The changed data will then be replicated au
the error message.
tomatically as delta information by the batch
Fix these errors by correcting the employee job, which has been scheduled in the SAP
data in SFSF EC as described in chapter HCI middleware system on a regular basis.
Maintain Employee Information [page 83]. Process step Maintain Employee Information
Refer also to the note below this procedure [page 83] needs to be repeated until all jobs
table. have replication status Successful.
Note
You can verify the status of each SOAP message sent between the applications and view them in detail. For this, proceed as follows:
1. On the Admin Center screen, navigate to Company Processes & Cycles Company Settings SFAPI Audit Log .
2. In Filter Options, select all Status, all SFAPI Call and Object checkboxes.
3. In the result list displayed on the right side of the screen select the appropriate entry related to compoundemployee, fo_businessunit, fo_division, and
fo_department (make sure the four entries mentioned have similar timestamps) and click on the SOAP button to view the request and response messages.
In case you want to view the detailed confirmation and/or confirmation error message, you can proceed as follows:
1. On the Admin Center screen, navigate to Company Processes & Cycles Company Settings OData API Audit Log .
2. In Filter Options, select all Status checkboxes and select all OData API Call checkboxes.
In the Entity Name section, keep only the EmployeeDataReplicationConfirmation and/or EmployeeDataReplicationConfirmationErrorMessage checkboxes selected.

3. In the result list displayed on the right side of the screen, select the appropriate entry and choose the REST button to view the request and response messages.
4.2.8 View Updated Personnel Master Data
Test Administration

date.
Business Role(s)

Context
The Customer Project Manager views the updated master data of the employee as it has been replicated from SuccessFactors Employee Central to the SAP S/4HANA
system.
In the following subchapters, we detail the procedure for each type of employee data described in chapter Maintain Employee Information [page 83] .
4.2.8.1 View Employee Communication Information
Test Administration

date.
Business Role(s)

Context
The Customer Project Manager views the updated contact information of the employee: he or she views if the new phone type Cell has been created and the already existing
phone type Business has been updated as expected in the SAP S/4HANA system. The employee's contact information as maintained in SFSF EC is visible as communication
information in the employee's fact sheet in SAP S/4HANA.
Procedure
2 Search Employee On the top-right corner of the screen, next to In the Search Results screen, the system pro
your name, select the Search (magnifying poses a list of employees matching your
All: Employees
Search In: Employees: enter <full name>

or <*full name parts*> of the em
ployee and press Enter .
Alan Jon.

4 View New Phone Information In the Communications subsection of the

General Information section, check that the
phone information of type Cell has been re
plicated correctly.
5 View Updated Phone Information In the Communications subsection of the

General Information section, check that
phone type Business has been updated
correctly.
4.2.8.2 View Employee Manager Assignment
Test Administration

date.
Business Role(s)

Context
The Customer Project Manager views the employee's new supervisor information in order to check if the data has been updated as expected in the SAP S/4HANA system.
The employee's new supervisor as maintained in SFSF EC is visible as manager information in the employee's fact sheet in SAP S/4HANA.

Procedure
All: Employees
Search In: Employees: enter <full name>

or <*full name parts*> of the em
ployee and press Enter .
3 Select Employee In the Search Results screen, choose the You are directed to the employee's fact
Alan Jon.
4 View Employee's Manager In the Employments section, verify that the

Manager field contains the name of the em
ployee's new supervisor as maintained in
SuccessFactors Employee Central.
Note
This data is visible also in the Basic Data
subsection of the General Information sec
tion.

4.2.8.3 View Updated Employee Payment Information
Test Administration

date.
Business Role(s)

Context
The Customer Project Manager views the updated payment information of the employee as replicated from SuccessFactors Employee Central. He or she checks if the new
pay type has been created as expected in the SAP S/4HANA system.
Caution
The Pay Type from SuccessFactors Employee Central will be transferred as expenses to SAP S/4HANA. In case only pay type Main Payment Method has been
maintained in SuccessFactors Employee Central for the employee, this will be transferred to SAP S/4HANA (you have tested this already in chapter 4.2.5.2). In case for the
employee an additional pay type Expenses has been maintained in SuccessFactors Employee Central starting an effective date, the Main Payment Method will be
delimited in SAP S/4HANA.

Procedure
tab and make following entries in the search
fields, the system proposes a list of employ
fields:
ees matching your search criteria.
Persons from drop-down

ployee
First name: enter <first name> of the em

ployee
5 Go to Payment Transactions Go to the Payment Transactions tab. The Payment Transactions tab is displayed,
containing two sections: Bank Details and
Payment Cards.

6 View Delimited Bank Information In the Bank Details section, the data main
tained in SFSF EC for pay type Main
Payment Method is displayed. It contains
bank key, account number, name of financial
institution, and validity period.
Verify that this record is delimited one day

before the pay type Expenses starts to be
valid in SFSF EC: for this check the date visi
ble in the Valid To field of the record.
7 Check Payment Method Select in the Display in BP role field in the up
per part of the screen value FI Vendor
from drop-down. In the menu located in the
screen header an additional button,
Company Code, is displayed. Select this but
ton.
The screen content changes. Go to the

Vendor: Payment Transactions tab. In the
Automatic Payment Transactions section,
check that in field Payment methods value
CT is visible, meaning concatenation of
"check" and "bank transfer".
4.2.8.4 View Updated Employee Address Information
Test Administration

date.
Business Role(s)

Context
The Customer Project Manager views the updated home address information of the employee as replicated from SuccessFactors Employee Central. For this, he or she will use
the factsheet of the updated business partner.
Procedure
1 Log on Log on via the Fiori SAP Launchpad to SAP The page containing the Fiori apps associ


By: select Name from drop-down.

ployee.

employee.
5 Go to Address Overview Go to the Address Overview tab. The Address Overview tab is displayed, con
taining several sections.

6 View Address Information In case in SuccessFactors Employee Central

a new effective dated home address has
been maintained for the employee, the
Address Overview table contains at least two
records: the old and the new address. Check
the correctness of the replicated data. Verify
that the new home address has been created
starting a specific date and that the old home
address has been delimited accordingly.
In case in SuccessFactors Employee Central

possible errors in the existing home address
of the employee have been corrected, the
Address Overview table contains only one re
cord. Verify that the correction has been re
plicated as expected.
To view more details of each address record,

mark the record in the Address Overview ta
ble and choose the Magnifying Glass icon be
low the table. In the upcoming dialog box,
check the data visible in the Street Address
section.
Note
The mapping between the address fields
in SFSF EC and those in SAP S/4HANA is
given in the note below.
Note
Home address fields in SFSF EC and their mapping to the SAPIn case in SuccessFactors Employee Central a new effective dated home address has been S/4HANA fields
are given in the table below: maintained for the employee, the Home address fields in SFSF EC and their mapping to the SAP S/4HANA fields are given in the table below:
Country Country COUNTRY

Address Line 1 Street/House number STREETNAME
Address Line 2 Street 4 STREETSUFFIXNAME
City CITYNAME
County District DISTRICT
State Region REGION
ZIP Postal Code POSTALCODE
Note
Only the Technical Support in the SAP Service Center should perform the check of the SAP S/4HANA backend fields. The procedure is as follows:
1. Log on to the SAP S/4HANA backend system/client and enter transaction code se16.
2. On the Data Browser: Initial Screen, in the Table Name field enter value IEMPLHOMEADDRSS and choose Enter .
3. On the Data Browser: Table IEMPLHOMEADDRSS: Selection Screen enter selection criteria as appropriate: for example, enter in the Full Name field the <full name> or
<*full name parts*> of the employee whose home address has been maintained in SFSF EC and should now be verified. Choose the Execute icon, or alternatively F8 .
4. On the Data Browser: Table IEMPLHOMEADDRSS: Select Entries <#> screen mark the record of the employee of interest, for example Alan Jon, and choose the Display
icon, or alternatively F7 .
Note
In SAP S/4HANA you can switch between the Field Name (meaning technical name as given in the above table) and the Field Label (meaning semantic name) as
follows:
○ in the menu on top of the Data Browser: Initial Screen navigate to Settings User Parameters…;
○ in the upcoming User-Specific Settings dialog box / Data Browser tab go to the Keyword section and check either the Field Name or Field Label radio-button as
per your needs;
○ choose Enter .

4.3 Contingent Worker Data Replication
In the following subchapters the procedures for executing the contingent worker data replication from SuccessFactors Employee Central to SAP S/4HANA is described.
In addition to employees, the company can also hire contingent workers to deliver services on a non-permanent basis. The contingent workers are often known as
independent professionals, temporary contract workers, labor hires. For contingent workers only a limited amount of information is maintained in the SuccessFactors
Employee Central system and then replicated automatically to SAP S/4HANA. In addition, master data for the contingent worker can be updated in the SuccessFactors
Employee Central system and replicated automatically as delta changes to SAP S/4HANA.
At high level, this process is as follows: after executing the preliminary steps as described in chapter Preliminary Steps for Employee Data Replication [page 10], master data
of new contingent workers is entered into the SuccessFactors Employee Central system. This data is then replicated automatically to the SAP S/4HANA, where it can be
checked for correctness. Because the data needs to be always up-to-date, adaptions of the contingent worker's master data record can be performed in SuccessFactors
Employee Central as long as he or she is in status Active. These adaptions are then replicated automatically as delta changes to SAP S/4HANA, where they can be checked
for correctness. After the work order, to which the contingent worker is assigned, has ended, the status of the contingent worker turns inactive in the system. Nevertheless,
the contingent worker can be reactivated by assigning him or her to other work orders.
4.3.1 Enter Master Data of Contingent Worker
Test Administration

date.
Business Role(s)

Context
The HR manager enters master data for a new contingent worker. This data includes personal data, company-specific data, and work order related data for the contingent
worker.
Prerequisites
The Vendor (Supplier) created in SAP S/4HANA and relevant for the work order to be assigned to the contingent worker has been created manually in SuccessFactors
Employee Central.
Note
The vendor information can be created in SuccessFactors Employee Central as follows:
Log on to SuccessFactors Employee Central and navigate to Home Admin Center .
In the Company Processes & Cycles portlet of the Admin Center screen select Employee Files Manage Data .
From the Create New drop-down select VendorInfo. Fill the upcoming fields with exactly the same data as the vendor created in SAP S/4HANA has. Choose the Save
button.
Procedure
1 Log on Log on to SuccessFactors Employee Central as an HR manager. The Home page is displayed.
2 Go to Admin Center From the Home drop-down, select Admin Center. The Admin Center screen is dis
screen played.
3 Add Contingent In the Manage Employees block of the Admin Center screen, You are directed to the My
Employee choose Update User Information Add Contingent Employee File Add Contingent
Worker . Worker screen.
Note
You can add Add Contingent Worker to My Favorites and
start the process from there.

4 Enter Identity Infor In the Identity Information section, make the following entries:
mation for Contin
Start Date: select from calendar help
gent Employee
Company: Company Code 1710 (1710)
In the Name Information block, make entries as appropriate for

following fields:
Middle Name: enter as appropriate
Suffix: select from drop-down
Salutation: select from drop-down
5 Continue Choose the Continue button. The Personal Information section in

the Add Contingent Worker screen is
expanded.
6 Enter Contact Infor In the Email Information block of the Personal Information sec
mation for Contin tion, select the (+) Add link. The editable fields show up and you
gent Worker can enter following information:
Email Type: select Business from drop-down
Email Address: enter as appropriate
Is Primary: defaults to Yes; adapt if appropriate
Note
The other available email types are not relevant for integra
tion with SAP S/4HANA.
7 Continue Choose the Continue button. The Contingent Worker Assignment

Information section in the Add
Contingent Worker screen is ex
panded.

8 Enter Organiza In the Organizational Information block, make the following en
tional Information tries:
for Contingent Em
Company: value Company Code 1710 (1710) is defaulted;
ployee
leave as is
Make entries as appropriate for the following fields:
Business Unit: select from drop-down
Division: select from drop-down
Department: select from drop-down
Cost Center: select from drop-down
Note
Location/Timezone are currently not replicated to SAP S/
4HANA.
9 Enter Job Informa In the Job Information block, make the following entries: Depending on the propagation rule
tion for Contingent configured in your instance, the fol
Job Classification: select from drop-down
Employee lowing fields will be filled automati
Standard Weekly Hours: defaulted based on value in field Job cally based on the value you have
Classification; adapt if required chosen for the Job Classification: Job
Title, Pay Grade, and Regular/
FTE: defaulted based on value entered in field Job Classification;
Temporary.
adapt if required
Select the <#> more fields link and make following entry:
Employee Class: select Service Provider or

Freelancer from drop-down
Note
In case you leave Employee Class empty, value Service
Performer is created by default in SAP S/4HANA.
10 Continue Choose the Continue button. The Work Order Information section
in the Add Contingent Worker screen
is expanded.

11 Enter Work Order In the Work Order block make the following entries:
Information for Work Order ID: enter as appropriate.

Contingent Worker
Work Order Name: enter as appropriate
Owner ID: enter person ID parts and select the appropriate em
ployee from the value help.
Note
The individual responsible for work orders. This can be a pro
curement specialist, supervisor or a manager.
Supplier: select from drop-down, for example, Vendor 1.
Note
For the employee class Freelancer the value contained in
the Supplier field will not be transferred to SAP S/4HANA!
End Date: select from calendar help the date on which the en
gagement of the contingent worker ends in the work order.
Note
Starting one day after this date the work order turns inactive
and the contingent worker will no longer be active in the sys
tem.

12 Submit Data Choose the Submit button, or alternatively the Continue button. A success message is generated by
the system, informing you about the
hire date of the new contingent
worker. You may choose to view the
profile of the contingent worker, add
data of another new contingent
worker, or simply return to the home
page. A Welcome to
SuccessFactors email is sent au
tomatically by the system from your
email account to the new contingent
worker containing login information
for the same.
13 View Contingent Choose the View profile of <contingent worker name> button. You are directed to My Employee
Worker Profile
File new contingent worker
name> page, containing three sec

tions: Personal Information,
Employment Information, and
Contingent Worker. In the Header,
above the name the Contingent
Worker symbol is displayed.

14 Verify Data Verify the data displayed in the different sections: The contingent worker has Employee
Status Active, and data matches
In the Job Information subsection of the Employment
what was maintained.
Information section, check that value of field Employee Status is
Active.
In the Organizational Information subsection of the Employment

Information section, select the Pending future change in Job
Information (<Date>) link. In the upcoming Change History:
Organizational Information Changes dialog box view the details
of the two records created with appropriate events and event
reasons: Start Contingent Worker and End Contingent Worker.
In the record related to event End Contingent Worker record
check that value of field Employee Status is Terminated and
the effective date of that change is one day after the date main
tained in field End Date in the Work Order block.
4.3.1.1 Trigger Contingent Worker Master Data Replication
Test Administration

date.
Business Role(s)


Purpose
The batch job, which has been scheduled in the SAP HCI middleware system on a regular basis, extracts and replicates the contingent worker master data from
SuccessFactors Employee Central to the SAP S/4HANA system.
4.3.1.2 Create Contingent Worker Master Data Record in SAP S/4HANA
Test Administration

date.
Business Role(s)

Context
Based on the information passed from SAP HCI, SAP S/4HANA recognizes that the contingent worker does not exist in the system and creates automatically a business
partner with role Service Provider or Freelancer, depending on the value maintained for Employee Class in SFSF EC.
In addition, in case of Service Provider, a relationship between the contingent worker and the vendor maintained in the work order in SFSF EC is automatically created in
SAP S/4HANA.
Basic information is made available in SAP S/4HANA in the contingent worker's factsheet.

4.3.1.3 Initiate Contingent Worker Master Data Replication Confirmation Message
Test Administration

date.
Business Role(s)

Context
After the contingent worker master data replication has taken place the SAP S/4HANA system sends a confirmation message to the middleware (SAP HCI), which processes
this message and sends it to SuccessFactors Employee Central.
4.3.1.4 Receive Contingent Worker Master Data Replication Confirmation Message
Test Administration

date.
Business Role(s)

Context
The confirmation of the contingent worker master data replication is received by SuccessFactors Employee Central and can be monitored there.
Note
The success or failure of the master data replication of the new contingent worker can be monitored as described in Monitor Contingent Worker Master Data Replication 1
[page 118] .
The master data of the new contingent worker as replicated to the SAP S/4HANA can be viewed and checked for correctness. Refer to View Contingent Worker Master
Data [page 120] for more details.
4.3.2 Monitor Contingent Worker Master Data Replication 1
Test Administration

date.
Business Role(s)


Context
The HR Manager monitors the success or failure of the creation of the master data record of the new contingent worker in the SAP S/4HANA system. For this, he or she views
the replication status for each employee to see if there are any failed jobs.
Procedure
1 Log on Log on to SuccessFactors Employee Central The Home page is displayed.

as an HR manager.
Center.
3 Go to Data Replication Monitor In the Company Processes & Cycles portlet of The Data Replication Monitor screen is dis
Integration .
4 Select Display Options Select following display options and when The replication jobs from the last hour are
done press the Apply button: shown in the Standard View part of the Data
Replication Status: flag all checkboxes

as No Selection


5 Check Status of Jobs Ensure that all jobs have the replication sta Possibly existing unsuccessfully processed
tus Successful. If there are any jobs with replication requests have been identified and
replication status Failed click on the are to be solved as described in process step
Replication Status to view the error message. Maintain Contingent Worker Information
Fix these errors by correcting the employee [page 127]. The changed data will then be re
data in SFSF EC as described in chapter plicated automatically as delta information
Maintain Contingent Worker Information by the batch job, which has been scheduled
[page 127]. in the SAP HCI middleware system on a regu
lar basis. Process step Maintain Contingent
Worker Information [page 127] needs to be
repeated until all jobs have replication status
Successful.
4.3.3 View Contingent Worker Master Data
Context
The Customer Project Manager validates the replicated data of the contingent worker in SAP S/4HANA to make sure the data is in-sync between SuccessFactors Employee
Central and SAP S/4HANA.
In the following subchapters, we detail the procedure for several type of data maintained for the contingent worker in SuccessFactors Employee Central and replicated to SAP
S/4HANA.
4.3.3.1 View Contingent Worker Basic Data 1
Test Administration

date.
Business Role(s)

Context
The Customer Project Manager views the basic data of the contingent worker as replicated from SuccessFactors Employee Central. This data includes information related to
name, communication, and organization.
Procedure
2 Search Contingent Worker On the top right corner of the screen, next to In the Search Results screen, the system pro
glass) icon. In the two editable search fields search criteria. For each employee a short
on top of the screen make following entries: overview of organizational details is given,
Search In: Employees: enter <full name> well as the job title.
or <*full name parts*> of the contin
gent worker and press Enter .
3 Select Contingent Worker In the Search Results screen, click on the You are directed to the factsheet.
<employee name> link of the contingent
worker whose data you want to view.

and personal information attributes are cor
rectly transferred. For example, check the
contingent worker's first name and last
name.

General Information section check that email
address of type Business has been cor
rectly transferred; this is visible in the Email
field.

6 View Employment Details The Basic Data subsection of the General

Information section contains the current valid
data. Verify the correctness of following repli
cated data:
● Job Title
● Organizational Unit (value of this field
Business Unit is taken),
● Cost Center
● Company:
The table in the Employments section
contains two entries:
● one for the period in which the contin
gent worker is active in the system; this
record has in the To field the validity end
date of the work order to which the con
tingent worker is assigned
gent worker is inactive in the system;
this record has in the From field the date
of the first day after the work order to
which the contingent worker was as
signed has ended. The To field contains
the system high date.
Note
propriate IDs of the contingent worker as
maintained in the S/4HANA system. For

this choose on top of the Employments ta

ble the Settings icon, flag the appropriate
Note
● On the Data Browser: Initial Screen, in the Table Name field enter value IEMPLOYEE and choose Enter
● On the Data Browser: Table IEMPLOYEE: Selection Screen enter selection criteria as appropriate: for example, enter in the Last Name field the <last name> or <*last
name parts*> of the contingent worker recently added to SFSF EC. Choose the Execute icon, or alternatively F8 .
● Mark the record of the contingent worker of interest and choose the Display icon, or alternatively F7 .
● View and check the correctness of the data of the contingent worker as replicated from SFSF EC, for example academic title, and gender.
● Check also the correctness of the business partner role:
● ○ for a contingent worker it should have value BBP005 (Service Provider) or BBP010 (Freelancer), depending on the value maintained for Employee Class
in SFSF EC. In case no employee class has been maintained in SFSF EC for the contingent worker, value BBP005 (Service Provider) will be shown as default.
Note
As mentioned in test step #6 in the above table, the Organizational Unit visible on the fact sheet of the contingent worker is filled with the value of the lowest organizational
unit maintained in SuccessFactors Employee Central, most likely the Department. Nevertheless, the superordinate organizational units, like division and business unit, are
also replicated to the SAP S/4HANA system. The Technical Support in the SAP Service Center can also check in the SAP S/4HANA backend system if these have been
● On the Data Browser: Table /SHCM/HRP5090: Selection Screen enter in the Object ID field the value available in the Employmentinternalid field in the contingent
worker's fact sheet. Choose the Execute icon, or alternatively F8 . Two records should be visible, one for the active period of the contingent worker at the company and
one for the inactive period.
● View and check the correctness of the data visible in the fields Department ID, Department Name, Division ID, Division Name, Bus. Unit ID, and Bus. Unit Name.
● Check also the values of field Employment Status for each record: it should be 1 (Active) for the period in which the work order has effective status Active in
SuccessFactors Employee Central and 0 (Inactive) once the work order has effective status InActive in SuccessFactors Employee Central.

4.3.3.2 View Supplier Information for Contingent Worker
Test Administration

date.
Business Role(s)

Context
For each contingent worker replicated from SuccessFactors Employee Central a business partner of role Service Provider or FreelancerService Provider is created
in SAP S/4HANA. In addition, in case of a relationship between the contingent worker and the vendor maintained in the work order in SFSF EC is automatically created in SAP
S/4HANA.
Note
For a Freelancer no relationship between the contingent worker and vendor is created in SAP S/4HANA.
The Customer Project Manager views if the assignment between the contingent worker of role Service Provider and supplier has been replicated correctly to SAP S/
4HANA. For this, he or she checks in the business partner factsheet if a relationship exists between the supplier and the business partner role Service Provider.
Note
In SuccessFactors Employee Central, the supplier is maintained as vendor in the work order.

Procedure
1 Log on Log on via the SAP Fiori Launchpad to SAP S/ The page containing the Fiori apps associ
4HANA as Customer Project Manager. ated with your role is displayed.
2 Open Maintain Business Partner App In the Master Data – Business Partner section An additional page opens, containing the
3 Search Contingent Worker On the left part of the screen select the Find In the Description section below the search
Find: Select Business Partner or

By: Select Name from drop-down
Last name: Enter <last name> of the con

tingent worker
First name: Enter <first name> of the con

tingent worker
4 Select Contingent Worker In the Description is created in section, double The details of the selected contingent
click on the <name> link of the contingent worker are shown in the right part of the
worker whose data you want to view. screen. Per default, the data for the
Business Partner (Gen.) role is
displayed. The section of the screen con
tains several tabs, like Address, Address
Overview, Identification, and Payment
Transactions.
5 Go to Identification Go to the Identification tab. The Identification tab is displayed, contain

ing several sections.

6 View Identification Information In the Identification Numbers section check if

the contingent worker is of type Service
Performer. For this check in the External BP
Number table the values of fields IDType and
Description.
7 Select Relationship to Supplier In the menu on top of the screen select the In the Relationship to BP table, the existing
Relationships button. In the Relationship Cat. relationship is displayed.
field select value Is Service Provider
For from drop-down.
8 View Relationship Details In the Relationship to BP table do the following:
● check that in the Business Partner field

the ID of the vendor (supplier) as main
tained in the work order in SFSF EC is visi
ble;
● check that in the Description field the
name of the vendor (supplier) is visible;
● check that in the Valid From / Valid To
fields the validity period of the work order
as maintained in SFSF EC is visible.
4.3.4 Maintain Contingent Worker Information
Context
The HR Manager maintains master data of the contingent worker in the SuccessFactors Employee Central system. The information contained in the contingent worker's file
needs to be up-to-date, so the HR Manager creates new records and adapts existing ones as appropriate.
In the following subchapters, we detail the maintenance procedure for several types of data.
Note
Every change in the contingent worker data is replicated as a delta load, that is, only data that has changed in SuccessFactors Employee Central since the last
synchronization is replicated to SAP S/4HANA. The frequency of these replications depends on the schedule that has been set for the batch job in the SAP HCI middleware
system. In the following, we describe these automated process steps only once, after the last maintenance process step described in this chapter.
Procedure
For maintaining contingent worker information, the HR Manager needs to select the person first. In order not to overload the procedure for each step with details to searching
and selecting the contingent worker, we describe it in detail below:

as an HR manager.
2 Search for Contingent Worker In the People Search field on the top right The system proposes a list of persons
name parts) of the contingent worker whose
data you want to maintain.
3 Select Contingent Worker Click in the list of contingent workers the ap You are directed to the Employee Files page,
propriate contingent worker. in which the contingent worker's existing
data record is divided into several sections:
Personal Information, Employment
Information, and Contingent Worker. The de
fault view is the Personal Information section.
4 Continue Continue with the procedure as described in

the subsequent chapters Maintain Contin
gent Worker Contact Information [page 129]
and Maintain Contingent Worker Work Order
Information [page 130].

4.3.4.1 Maintain Contingent Worker Contact Information
Test Administration

date.
Business Role(s)

Context
The HR Manager maintains the contact information of the contingent worker as necessary.
In this document, we consider as example the phone information of the contingent worker.
During entering master data for the contingent worker, the email type Business has been created. In this chapter, we will refer to creation of phone type Business. The email
of type Business and phone type Businessare part of the contingent worker's workplace address in SAP S/4HANA.
Procedure
1 Edit Contact Information In the Contact Information subsection of the The Contact Information dialog box is dis
Personal Information section, select the played.
Pencil icon next to the Contact Information
block.

2 Create New Phone Information Record In the Phone Information part of the dialog
box select the (+) Add link and make the fol
lowing entries:
Phone Type: select Business from drop-

down
Country Code: enter as appropriate
Area Code: enter as appropriate
Extension: enter as appropriate
Is Primary: defaults to Yes; adapt if appropri

ate
in the contingent worker's file. The primary
phone type is marked with a star.
4.3.4.2 Maintain Contingent Worker Work Order Information
Context
The HR Manager maintains information related to the work order of the contingent worker. This data may be related to correcting an error in the existing work order.
This data is then replicated as delta change to the SAP S/4HANA system where it can be checked for correctness.

Procedure
1 Edit Work Order In the Contingent Worker subsection of the The Work Order: Changes dialog box is dis
Contingent Worker section, select the Clock played.
icon next to the Work Order block.
2 Select History Record Select from the Change History section on

the left of the dialog box the appropriate re
cord (most likely the one for which the effec
tive status is Active) and choose the Edit
button. In the Edit History of WorkOrder: on
<date> dialog box leave the date in the When
do you want your changes to take effect?: as
is.
3 Correct Work Order Info Make adjustments as required, for example

change the vendor and/or endDate.
in the contingent worker's file.
4.3.4.2.1 Trigger Contingent Worker Master Data Delta Replication
Test Administration

date.
Business Role(s)

Context
The batch job, which has been scheduled in the SAP HCI middleware system on a regular basis, extracts and replicates the changed contingent worker master data (like
contact information) from SuccessFactors Employee Central to the SAP S/4HANA system. This is an automated step, and no manual execution is required.
4.3.4.2.2 Update Contingent Worker Master Data Record in SAP S/4HANA
Test Administration

date.
Business Role(s)

Context
Based on the information passed from SAP HCI, SAP S/4HANA recognizes that the contingent worker exists in the system and updates automatically the existing master data
record of the business partner with role Service Provider or Freelancer. This is an automated step, and no manual execution is required.

4.3.4.2.3 Initiate Changed Contingent Worker Master Data Replication Confirmation
Test Administration

date.
Business Role(s)

Context
After the replication of changes in contingent worker master data has taken place, the SAP S/4HANA system sends a confirmation message to the middleware (SAP HCI),
which processes this message and sends it to SuccessFactors Employee Central. This is an automated step, and no manual execution is required.
4.3.4.2.4 Receive Changed Contingent Worker Master Data Replication Confirmation Message
Test Administration

date.
Business Role(s)

Context
The confirmation of the replication of changed contingent worker master data is received by SuccessFactors Employee Central and can be monitored there. This is an
automated step, and no manual execution is required.
Test Administration

date.
Business Role(s)

Context
The HR Manager monitors the success or failure of the update of the master data record of the contingent worker in the SAP S/4HANA system. For this, he or she views the
replication status of each employee to see if there are any failed jobs.

Procedure

as an HR manager.
Center.
the Admin Center screen go to Employee played.
Integration
4 Select Display Options Select following display options and when The replications from the last hour are shown
done press the Apply button: in the Standard View part of the Data

as No Selection

Successful.

4.3.6 View Updated Contingent Worker Master Data
In the following subchapters, we detail the procedure for each type of contingent worker data described in chapter Maintain Contingent Worker Information [page 127].
4.3.6.1 View Contingent Worker Communication Information
Test Administration

date.
Business Role(s)

Context
The Customer Project Manager views the updated contact information of the contingent worker: he or she views if the phone information type has been created as expected in
the SAP S/4HANA system.

Procedure
All: select Employeesfrom drop-down

General Information section check that
phone information of type Businesshas
been correctly transferred; this is visible in
the Phone field.
4.3.6.2 View Updated Supplier Information for Contingent Worker
Test Administration

date.
Business Role(s)

Context
The Customer Project Manager views if the correction in the supplier data has been replicated as expected to the SAP S/4HANA system.
Procedure


Last name: enter last name of the contin

gent worker
First name: enter first name of the con

tingent worker
4 Select Contingent Worker In the Description section, double click on the The details of the selected contingent worker
name link of the contingent worker whose are shown in the right part of the screen. Per
data you want to view. default, the data for the Business
Partner (Gen.) role is displayed. The
section of the screen contains several tabs,
like Address, Address Overview,
Identification, and Payment Transactions.
5 Go to Identification Go to the Identification tab. The Identification tab is displayed, containing

several sections.

Performer. For this check in the External
BP Number table the values of fields IDType
and Description.
For from drop-down.

8 View Relationship Details In the Relationship to BP table, check that in

the Business Partner and Description fields
the corrected vendor (supplier) ID and name
are visible.
4.3.7 Re-Activate Contingent Worker
Context
After the work order, to which the contingent worker is assigned, has ended, the status of the contingent worker turns also inactive in the system. Nevertheless, you can
assign this contingent worker again to other work orders, which your company needs to execute.
For this, the HR Manager needs to create via the contingent worker file the new work order in the system and then reactivate the contingent worker by assigning him or her to
this work order.
When reactivating the contingent worker, the data maintained during his or her first assignment at the company is taken over and can be reused.
Prerequisite
The Vendor (Supplier) created in SAP S/4HANA and relevant for the work order to be assigned to the contingent worker has been created manually in SuccessFactors
Employee Central.
Procedure

as an HR manager.

2 Search for Contingent Worker In the People Search field on the top right The system proposes a list of persons
name parts) of the contingent worker whose
data you want to maintain.
3 Select Contingent Worker Click in the list of contingent workers the ap You are directed to the Employee Files page,
propriate contingent worker. in which the contingent worker's existing
data record is divided into several sections:
Personal Information, Employment
Information, and Contingent Worker. The de
fault view is the Personal Information section.
4 Go to Work Order Go to the Contingent Worker section.
5 Go to Work Order History In the Contingent Worker subsection of the The Work Order: Changes dialog box is dis
Contingent Worker section, select the Clock played.
icon next to the Work Order block.
6 View Start Date of Inactive Work Order Select from the Change History section on
the left of the dialog box the record in which
the work order has status InActive. Note
down the start date of this record.
Note
The new work order you are going to cre
ate should have a start date after this
start date.
7 Insert New Work Order Record Select the Insert New Record button in the The Insert History Record for Work Order dia
bottom left of the dialog box. log box is displayed.

8 Enter New Work Order Details In the Insert History Record for Work Order
dialog box make following entries:

effect?: select from calendar help a date,
which is after the start date of the inactive
work order record
workOrderId: enter as appropriate
workOrderName: enter as appropriate
workOrderOwnerId: enter as appropriate
vendor: select from drop-down
endDate: select from calendar help
startDate: select from calendar help the

same date you have entered into the When
would you like your changes to take effect?
field
9 Save New Work Order Choose the Save button.
10 View Work Order History Note that in the Change History section on
the left of the dialog box two new records are
shown: the record you just created for the
new work order having status Active, and a
record created automatically for the period in
which this work order is InActive.
11 Go to Organizational Information History Refresh the page. The Organizational Information Changes dia
log box is displayed.
In the Organizational Information subsection
of the Employment Information section, se
lect the Clock icon next to the Organizational
Information block.
12 Insert New Organizational Information Re Select the Insert New Record button in the The Insert History Record for Organizational
cord bottom left of the dialog box. Information dialog box is displayed.

13 Enter New Organizational Information De In the Insert History Record for Organizational
tails Information dialog box make following en
tries:

effect?: select from calendar help the start
date you have previously entered for the new
work order (test step # 8)
Event: select Start Contingent

Worker from drop-down
Event Reason: select Start Contingent

Worker from drop-down.
In the Organizational Information and Job

Information sections of the dialog box the
data that already exists in the system for the
contingent worker is displayed. You may de
cide to accept it as is or to adapt it as appro
priate.
14 Save New Organizational Information Choose the Save button. A message is generated by the system about
the successful saving of the data. An addi
tional event End Contingent Worker
with event reason End Contingent
Worker is triggered, having as start date
one day after the work order, to which the
contingent worker is assigned, becomes in
active. It is visible in the Change History sec
tion on the left of the Organizational
Information Changes dialog box.
15 Close Dialog Box Choose the X (Close) icon.

16 Verify Data Check that in the Job Information subsection

of the Employment Information section a
Pending future change in Job Information
(<Date>) link is also available. Click on it and
verify that the same event End Contingent
Worker record is visible as the one mentioned
in the result column of test step # 14.
4.3.7.1 Trigger Contingent Worker Master Data Delta Replication
Test Administration

date.
Business Role(s)

Context
The batch job, which has been scheduled in the SAP HCI middleware system on a regular basis, extracts and replicates the changed contingent worker master data from
SuccessFactors Employee Central to the SAP S/4HANA system.

4.3.7.2 Update Contingent Worker Master Data Record in SAP S/4HANA
Test Administration

date.
Business Role(s)

Context
Based on the information passed from SAP HCI, SAP S/4HANA recognizes that the contingent worker exists in the system and updates automatically the existing master data
record of the business partner with role Service Provider or Freelancer.
4.3.7.3 Initiate Changed Contingent Worker Master Data Replication Confirmation Message
Test Administration

date.
Business Role(s)

Context
After the replication of changes in contingent worker master data has taken place, the SAP S/4HANA system sends a confirmation message to the middleware (SAP HCI),
which processes this message and sends it to SuccessFactors Employee Central.
4.3.7.4 Receive Changed Contingent Worker Master Data Replication Confirmation Message
Test Administration

date.
Business Role(s)

Context
The confirmation of the replication of changed contingent worker master data is received by SuccessFactors Employee Central and can be monitored there.

Test Administration

date.
Business Role(s)

Context
The HR Manager monitors the success or failure of the update of the master data record of the contingent worker in the SAP S/4HANA system. For this, he or she views the
replication status of each employee to see if there are any failed jobs.
Procedure

as an HR manager.
Center.
Integration .

4 Select Display Options Select following display options and when The replication jobs from the last hour are
done press the Apply button: shown in the Standard View part of the Data

as No Selection

Successful.
4.3.9 View Contingent Worker Master Data
Context
In the following subchapters, we detail the procedure for several type of data maintained for the contingent worker in SuccessFactors Employee Central and replicated to SAP
S/4HANA.
4.3.9.1 View Contingent Worker Basic Data 2
Test Administration

date.
Business Role(s)

Context
The Customer Project Manager views the basic data of the reactivated contingent worker as replicated from SuccessFactors Employee Central. This data includes information
related to name, communication, and organization.
Procedure

and personal information attributes are cor
rectly transferred. For example, check the
contingent worker's first name and last
name.

General Information section check that email
address of type Business has been cor
rectly transferred; this is visible in the Email
field.

6 View Employment Details The Basic Data subsection of the General

Information section contains the current valid
data. Verify the correctness of following repli
cated data:
● Job Title
● Organizational Unit (value of this field
Business Unit is taken),
● Cost Center
● Company:
The table in the Employments section
contains two new entries:
gent worker is active again in the sys
tem; this record has in the To field the
validity end date of the new work order
to which the contingent worker is as
signed
gent worker is inactive again in the sys
tem; this record has in the From field the
date of the first day after the new work
order to which the contingent worker
was assigned has ended. The To field
contains the system high date.
The inactive record from the previous assign

ment of the contingent worker to a work or
der has been delimited one day before the
assignment to a new work order becomes ac
tive.

The values of field Employment Status reflect

accordingly the assignment of the contingent
worker to a work order.
Note
propriate IDs of the contingent worker as
maintained in the S/4HANA system. For
this choose on top of the Employments ta
ble the Settings icon, flag the appropriate
Note
As mentioned in test step #6 in the above table, the Organizational Unit visible on the fact sheet of the contingent worker is filled with the value of the lowest organizational
unit maintained in SuccessFactors Employee Central, most likely the Department. Nevertheless, the superordinate organizational units, like division and business unit, are
also replicated to the SAP S/4HANA system. The Technical Support in the SAP Service Center can also check in the SAP S/4HANA backend system if these have been
● On the Data Browser: Table /SHCM/HRP5090: Selection Screen enter in the Object ID field the value available in the Employmentinternalid field in the contingent
worker's fact sheet. Choose the Execute icon, or alternatively F8 . Four records should be visible, two for the previous, and two for the current engagement with the
company.
● View and check the correctness of the data visible in the fields Department ID, Department Name, Division ID, Division Name, Bus. Unit ID, and Bus. Unit Name of the
newest active record.
● Check also the values of field Employment Status for each record.

4.3.9.2 View Supplier Information for Contingent Worker
Test Administration

date.
Business Role(s)

Context
For each contingent worker replicated from SuccessFactors Employee Central a business partner of role Service Provider or FreelancerService Provider is created
in SAP S/4HANA. In addition, in case of a relationship between the contingent worker and the vendor maintained in the work order in SFSF EC is automatically created in SAP
S/4HANA.
Note
For a Freelancer no relationship between the contingent worker and vendor is created in SAP S/4HANA.
The Customer Project Manager views if the assignment between the contingent worker of role Service Provider and supplier has been replicated correctly to SAP S/
4HANA. For this, he or she checks in the business partner factsheet if a relationship exists between the supplier and the business partner role Service Provider.
Note
In SuccessFactors Employee Central, the supplier is maintained as vendor in the work order.

Procedure
1 Log on Log on via the SAP Fiori Launchpad to SAP S/ The page containing the Fiori apps associ
4HANA as Customer Project Manager. ated with your role is displayed.
Find: Select Business Partner or

By: Select Name from drop-down
Last name: Enter <last name> of the con

tingent worker
First name: Enter <first name> of the con

tingent worker
4 Select Contingent Worker In the Description is created in section, double The details of the selected contingent
click on the <name> link of the contingent worker are shown in the right part of the
worker whose data you want to view. screen. Per default, the data for the
Business Partner (Gen.) role is
displayed. The section of the screen con
tains several tabs, like Address, Address
Overview, Identification, and Payment
Transactions.
5 Go to Identification Go to the Identification tab. The Identification tab is displayed, contain

ing several sections.


Performer. For this check in the External BP
Number table the values of fields IDType and
Description.
For from drop-down.
8 View Relationship Details In the Relationship to BP table do the following:
● check that in the Business Partner field

the ID of the vendor (supplier) as main
tained in the work order in SFSF EC is visi
ble;
● check that in the Description field the
name of the vendor (supplier) is visible;
● check that in the Valid From / Valid To
fields the validity period of the work order
as maintained in SFSF EC is visible.
4.4 Employee Photo Replication
In the following subchapters the procedures for executing the employee (or contingent worker) photo replication from SuccessFactors Employee Central to SAP S/4HANA is
described. At high level this process is as follows: after executing the preliminary steps as described in chapter Preliminary Steps for Employee Photo Replication [page 12] ,
changes to the existing photos are performed in SuccessFactors Employee Central. The changes are then replicated automatically to SAP S/4HANA, where they can be
checked for correctness.
Caution
The process steps described in this chapter are also relevant for contingent workers!
The process steps described in this chapter are not relevant for terminated employees!

4.4.1 Maintain Employee Photo
Context
The HR Manager maintains photos of employee and contingent workers. This may refer to:
● adding a photo for an employee or contingent worker who does not have any photo yet
● exchanging an already replicated photo
Note
In all these cases, a delta replication will be triggered.
Procedure
Note
Even though in the following only "employee" is mentioned, the procedure is valid for contingent workers, too!
1 Log on Log on to SuccessFactors Employee Cen The Home page is displayed.

tral as an HR manager.
2 Search Employee without Photo In the People: Search field in the top right The system proposes a list of employees matching
corner of the page, enter the name (or your search criteria.
name parts) of the employee for whom you
want to add a photo.
3 Select Employee Choose an employee from the list, for ex You are directed to the Employee Files page in the
ample, Alan Jon. employee's existing data record is divided into sev
eral sections. The default view is the Personal
Information section.

4 Go to Header Edit Mode Select the Header button (Pencil icon) in A callout containing the Edit Photo Picture button
the right top corner of the screen. is displayed.
5 Edit Photo Choose the Edit Profile Picture button. The Edit Profile Picture dialog box is displayed,
where you have the options to upload or drop a
photo in the pictogram.
6 Add Photo Continue with one of the two options below: The uploaded photo is visible in the Select
imageProfile Header of the employee or contingent
Option 1: Select the link, select the file with
worker.
the appropriate photo and upload it.
Option 2: Open the folder containing the

photo you want to upload, and move the
photo from the folder into the pictogram.
For both options, use the Zoom In or Select

image fileZoom Out icons to adjust the
photo into the pictogram. When done,
choose the Save button.
7 Search Employee with Photo In the People: Search field in the top right The system proposes a list of employees matching
corner of the page, enter the name (or your search criteria.
name parts) of the employee for whom you
want to exchange a photo.
8 Select Employee Choose an employee from the list. You are directed to the Employee Files page, in
which the employee's existing data record is div
ided into several sections. The default view is the
Personal Information section.
9 Go to Photo Edit Mode Select the Header button (Pencil icon) in A callout containing the Edit Profile Picture button
the right top corner of the screen. is displayed.

10 Edit Photo Choose the Edit Profile Picture button. The Edit Profile Picture dialog box is displayed,
where you have the options to upload a new pic
ture or delete the existing one.
Note
Deletion of a photo is not supported by the mid
dleware. Therefore, if you remove the employ
ee's photo in SFSF EC, his or her last photo
transferred to SAP S/4HANA will be still visible
in the factsheet.
11 Exchange Photo Select the Upload New Picture button, se The new photo is visible in the Profile Header of the
lect the file with the appropriate photo and employee or contingent worker.
upload it.
Use the Zoom In or Zoom Out icons to ad

just the photo into the pictogram. When
done, choose the Save button.
4.4.1.1 Trigger Employee Photo Replication
Test Administration

date.
Business Role(s)


Context
The batch job, which has been scheduled in the SAP HCI middleware system on a regular basis, extracts and replicates the employee photo from SuccessFactors Employee
Central to SAP S/4HANA.
4.4.1.2 Update Employee Photo Record in SAP S/4HANA
Test Administration

date.
Business Role(s)

Context
Based on the employee information passed from SAP HCI, SAP S/4HANA recognizes that the employee exists in the system and updates his or her record automatically with
the photo.
Note
The Image server must be up and running in SAP S/4HANA.

4.4.2 View Employee Photo
Test Administration

date.
Business Role(s)

Context
The Customer Project Manager views the employee (or contingent worker) photo as replicated from SuccessFactors Employee Central.
Procedure
Note
Even though in the following only "employee" is mentioned, the procedure is valid for contingent workers, too!

For employees with a photo, this photo is visi
All: Employees ble as small icon in the search result list.
Search In: Employee Search: enter <full

name> or <*full name parts*> of the
employee and press Enter .
3 Select Employee with New Photo In the Search Results screen, choose the You are directed to the employee's fact
whose initial photo has been uploaded, for
example, Alan Jon.
4 View Newly Uploaded Photo Check that the photo is displayed below the
employee's name in the page header.
5 Select Employee with Updated Photo Search and select the employee whose photo You are directed to the employee's fact
has been updated in SFSF EC. sheet.
6 View Exchanged Photo Check that the photo is displayed below the
employee's name in the page header.
4.4.3 Handle Replication Exceptions (Optional)
Test Administration

date.

Business Role(s)

Context
Situations can occur in which the photo of an employee or contingent worker is not replicated to SAP S/4HANA. Such a situation occur if the employee, whose photo should
be replicated, is not yet replicated successfully to SAP S/4HANA. If the employee is not transferred successfully, the system will try to transfer his or her record on the next
run.
Note
Deletion of an employee's photo in SFSF EC is not supported by the middleware. Therefore, if you remove the employee's photo in SFSF EC, his or her last photo
transferred to SAP S/4HANA will be still visible in the factsheet.
Procedure
The Administrator receives an email with the list of all employees /contingent workers for which the photo replication did not work. He or she can then remove the photo of
those employees which should anyway not be replicated, like for example the superuser. Otherwise, the system will always try to transfer this photo, which will enhance the
workload of the system. Then the Administrator checks in the data replication monitor the status of the employee, and re-sends this record if necessary.

Important Disclaimers and Legal Information
Coding Samples
Any software coding and/or code lines / strings ("Code") included in this documentation are only examples and are not intended to be used in a productive system environment. The Code is only intended to better explain and visualize the syntax and phrasing
rules of certain coding. SAP does not warrant the correctness and completeness of the Code given herein, and SAP shall not be liable for errors or damages caused by the usage of the Code, unless damages were caused by SAP intentionally or by SAP's gross
negligence.
Accessibility
The information contained in the SAP documentation represents SAP's current view of accessibility criteria as of the date of publication; it is in no way intended to be a binding guideline on how to ensure accessibility of software products. SAP in particular
disclaims any liability in relation to this document. This disclaimer, however, does not apply in cases of wilful misconduct or gross negligence of SAP. Furthermore, this document does not result in any direct or indirect contractual obligations of SAP.
Gender-Neutral Language
As far as possible, SAP documentation is gender neutral. Depending on the context, the reader is addressed directly with "you", or a gender-neutral noun (such as "sales person" or "working days") is used. If when referring to members of both sexes, however, the
third-person singular cannot be avoided or a gender-neutral noun does not exist, SAP reserves the right to use the masculine form of the noun and pronoun. This is to ensure that the documentation remains comprehensible.
Internet Hyperlinks
The SAP documentation may contain hyperlinks to the Internet. These hyperlinks are intended to serve as a hint about where to find related information. SAP does not warrant the availability and correctness of this related information or the ability of this
information to serve a particular purpose. SAP shall not be liable for any damages caused by the use of related information unless damages have been caused by SAP's gross negligence or willful misconduct. All links are categorized for transparency (see: http://
help.sap.com/disclaimer).

Important Disclaimers and Legal Information © 2016 SAP SE or an SAP affiliate company. All rights reserved. 163
go.sap.com/registration/
contact.html
© 2016 SAP SE or an SAP affiliate company. All rights reserved.

No part of this publication may be reproduced or transmitted in any
form or for any purpose without the express permission of SAP SE
or an SAP affiliate company. The information contained herein may
be changed without prior notice.
Some software products marketed by SAP SE and its distributors
contain proprietary software components of other software
vendors. National product specifications may vary.
These materials are provided by SAP SE or an SAP affiliate company
for informational purposes only, without representation or warranty
of any kind, and SAP or its affiliated companies shall not be liable for
errors or omissions with respect to the materials. The only
warranties for SAP or SAP affiliate company products and services
are those that are set forth in the express warranty statements
accompanying such products and services, if any. Nothing herein
should be construed as constituting an additional warranty.
SAP and other SAP products and services mentioned herein as well
as their respective logos are trademarks or registered trademarks
of SAP SE (or an SAP affiliate company) in Germany and other
countries. All other product and service names mentioned are the
trademarks of their respective companies.
Please see http://www.sap.com/corporate-en/legal/copyright/
index.epx for additional trademark information and notices.

Script Integración Con EC - EN - US

Uploaded by

Document Information

Original Title

Copyright

Available Formats

Share this document

Share or Embed Document

Sharing Options

Did you find this document useful?

Is this content inappropriate?

Copyright:

Available Formats

Script Integración Con EC - EN - US

Uploaded by

Copyright:

Available Formats

Test Script PUBLIC

Employee Central Integration (JB1_US)

Employee Central Integration (JB1_US) PUBLIC

1.1 Purpose of the Document

1.2 Purpose of Employee Central Integration

PUBLIC Employee Central Integration (JB1_US)

2.1 System Access and Roles

The test is conducted in the following systems:

SuccessFactors Employee Central SuccessFactors instance URL

SAP S/4HANA SAP Fiori Launchpad URL

● SuccessFactors Employee Central will be shortened SFSF EC

In SAP S/4HANA, cloud edition

Business Catalog Role Name Business Catalog Role ID Log On

In SuccessFactors Employee Central

In addition, some activities need to be executed by the SAP Service Center

Business Role Business Role Description

Middleware Administrator An employee of the SAP Service Center responsible for:

2.2 Master Data, Organizational Data, and Other Data

PUBLIC Employee Central Integration (JB1_US)

Data Sample Value Details Comments

2.3 Business Conditions

Business Condition Comment

1 The legal entities have been setup in SuccessFactors Employee

2 Cost centers have been defined in the SAP S/4HANA system.

Employee Central Integration (JB1_US) PUBLIC

2.4.1 Preliminary Steps for Cost Center Replication

Customer project: Fill in the project-specific parts.

Test Case ID <X.XX> Tester Name Testing Date Enter a test

Responsibility <State Service Provider, Customer or Joint Service Duration Enter a

PUBLIC Employee Central Integration (JB1_US)

1. Log on to the SAP Fiori Launchpad with the Controller role.

Fields in SAP S/4HANA Fields in SuccessFactors Employee Cen­ Description/Comment

Cost Center (Name) Name

Cost Center Description Description

Employee Central Integration (JB1_US) PUBLIC

Company Code Company Company Code of Cost Center

2.4.2 Preliminary Steps for Employee Data Replication

Customer project: Fill in the project-specific parts.

Test Case ID <X.XX> Tester Name Testing Date Enter a test

Responsibility <State Service Provider, Customer or Joint Service Duration Enter a

Uploading Employee Data to SuccessFactors Employee Central Master Instance

PUBLIC Employee Central Integration (JB1_US)

Validating Replicated Employee Data in SAP S/4HANA

2.4.3 Preliminary Steps for Employee Photo Replication

Customer project: Fill in the project-specific parts.

Test Case ID <X.XX> Tester Name Testing Date Enter a test

Responsibility <State Service Provider, Customer or Joint Service Duration Enter a

Uploading Employee Photo to SuccessFactors Employee Central Master Instance

Validating Replicated Employee Photo Data in SAP S/4HANA

Employee Central Integration (JB1_US) PUBLIC

Cost Center Replication

Process Step Business Condition Business Role Transaction Expected Results

Employee Data Replication

Process Step Business Condition Business Role Transaction Expected Results

PUBLIC Employee Central Integration (JB1_US)

Initiate Employee Background A confirmation message about the replication of em­

Initiate Employee Background A confirmation message about the replication of em­

Employee Central Integration (JB1_US) PUBLIC

In addition, the available data of the vendor created dur­

Initiate Employee Background A confirmation message about the replication of em­

PUBLIC Employee Central Integration (JB1_US)

In addition, the available data of the vendor created dur­

Employee Central Integration (JB1_US) PUBLIC

Fields in SAP S/4HANA Fields in SuccessFactors Employee Cen Description/Comment

Initiate Employee Background A confirmation message about the replication of em

Initiate Employee Background A confirmation message about the replication of em

In addition, the available data of the vendor created dur

Initiate Employee Background A confirmation message about the replication of em

In addition, the available data of the vendor created dur