7734ba068ecd4762a48d33e91a4e0c27

PUBLIC
Document Version: 1H 2024 – 2024-05-16
Managing Mass Changes in Employee Central

© 2024 SAP SE or an SAP affiliate company. All rights reserved.
THE BEST RUN

Content
1 Overview of Mass Changes in Employee Central. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4
2 Mass Data Management. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5

2.1 Permissions for Mass Data Management. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5
2.2 Configuring the MassChangeJobConfiguration from Manage Data. . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6
2.3 Creating Mass Change Requests. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8
2.4 After Submitting a Mass Change Request. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 11
2.5 Deleting Mass Change Requests. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 12
3 Managing Mass Changes. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 14

3.1 Mass Changes to Job Information and Job Relationship. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 14
3.2 Mass Changes to Positions. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .15
4 Foundation Data. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 23
4.1 Importing Foundation Data. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 23
4.2 Foundation Data Translation. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 26
Importing Data Translations for Legacy Foundation Objects. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 27
Importing Data Translations for Metadata Framework Foundation Objects. . . . . . . . . . . . . . . . . . . . 33
5 Employee Data Imports. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 39

5.1 Centralized Services for Employee Data Imports. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 39
5.2 Prerequisites for Importing Employee Data. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 41
Configuring Data Import Settings. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 42
Role-Based Permissions for Employee Data Import. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .45
Working with View-only Fields. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 47
Enabling Security Scan of User Inputs. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 47
Performance Benchmarks. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 48
5.3 Employee Data Import Process. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .51
Downloading Import File Templates. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 54
Preparing Data to Import. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 58
Uploading Import Files. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 99
Uploading Multiple Import Files Together. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 108
Scheduled Job Manager for Monitoring Jobs using Imports. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 110
Troubleshooting. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 111
5.4 Assignment ID Definition with Data Imports. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 116
Setting Up a Process for Auto-Generating Assignment ID. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 117
5.5 Data Validation and Error Management with Data Imports. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 118
5.6 End Date Correction with Data Imports. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 119

2 PUBLIC Content
5.7 Employee Data Deletion with Imports. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 124
Deleting Employee Data with a Single Entity. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 125
Deleting Employee Data with Multiple Entities. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 127
Use Cases: Employee Data Deletion. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 128
5.8 Identical Record Suppression with Data Imports. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .132
Use Cases: Identical Record Suppression. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 133
5.9 Forward Propagation of Data with Imports. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 137
5.10 Sequence Number Generation and Correction with Data Imports. . . . . . . . . . . . . . . . . . . . . . . . . . . . 149
5.11 Rehire Employees with Data Imports. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 157
Rehiring Former Employees with an Existing User ID. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 157
Rehiring Former Employees with an Existing User ID (New Employment). . . . . . . . . . . . . . . . . . . . . 158
5.12 Attaching Documents with Data Imports. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 160
5.13 Configuring Business Rules for Data Imports. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 162
Assigning a Business Rule to an Employee Central Entity. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 165
Use Cases: Business Rules. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 166
5.14 Configuring Workflows for Data Imports. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 175
5.15 Managing Access to Basic User Imports . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 177
5.16 Restricting Legal Entity Changes to an Employee Profile. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 178
5.17 Scheduling Data Import Jobs. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 179
5.18 Automatic Interruption and Cancellation of Import Jobs. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 181
6 Data Protection and Privacy. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 182

6.1 Centralized Data Protection and Privacy. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 182
6.2 Data Retention Management. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 183
7 Implementation of Off Cycle Event Batch. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 184

7.1 Off Cycle Event Batch. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 184
7.2 Creating an Off Cycle Event Batch Object. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 186
7.3 Creating a Business Rule for an Off Cycle Event Batch. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 190
7.4 Creating a User or Group of Users for an Off Cycle Event Batch Job. . . . . . . . . . . . . . . . . . . . . . . . . . . 192
7.5 Setting Up an Off Cycle Event Batch Job. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 193
7.6 Adding Off Cycle Event Batch Object to a Transport Bundle . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 194
7.7 Additional Configurations. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .195
Optimize Offcycle Event Batch Object Configuration. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 196
Monitoring Jobs. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 197
Use Cases. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 197
8 Change History. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 205

Content PUBLIC 3
1 Overview of Mass Changes in Employee
Central
Everything about the different methods in Employee Central to perform mass transactions on employee and/or
company data.
There can be many scenarios for performing mass changes can be many, ranging from a system-wide data
migration to ad-hoc data updates.
SAP SuccessFactors provides dedicated solutions to help achieve your objective. This guide elaborates on the
different options available in Employee Central for mass data changes.
Supported Entities/Data Ob-

Solution Description jects Suitable User Roles
Mass Data Management [page Use this solution to perform Position data objects. System Administrators, HR
5] bulk updates to data objects Representatives
from the UI.
Foundation Data [page 23] Use this solution to import Foundation data objects, in- System Administrators
foundation data, and perform cluding MDF (Generic) data
mass changes to foundation objects.
data.
Employee Data Imports [page Use this solution to import All HRIS entities. System Administrators
39] employee data, and perform
mass changes to employee
data.
Mass Changes to Job Infor- Use this solution to perform Job Information and Job Rela- System Administrators
mation and Job Relationship mass changes to Job Infor- tionship entities.
[page 14] mation and Job Relationship
data. This solution performs
mass changes on the basis of
business rules.
Mass Changes to Positions Use this solution to perform Position data objects. System Administrators
[page 15] mass changes to Position
data. This solution performs
mass changes on the basis of
business rules.

4 PUBLIC Overview of Mass Changes in Employee Central
2 Mass Data Management
Mass Data Management is a UI based solution to perform bulk changes to data in Employee Central.
Mass Data Management is simple and effective solution for performing data modifications in bulk. It moves away
from the traditional approach of configuring rules and a backend job for performing mass changes, to a UI based
approach where you can exercise much better control over the data you want to modify.
Whether you are an administrator with a strong technical background or an HR representative with a functional
(non-technical) background, you can use this solution to address your mass change requirements. Currently, Mass
Data Management supports changes to Position data objects only.
Salient features of Mass Data Management:
• A Fiori based UI, providing a simple, adaptive, and intuitive user experience.
• Comparatively flat learning curve, requires little to no prior technical knowledge.
• Readily extensible to support a wide range of data objects in Employee Central.
Using Mass Data Management, you can:
• Flexibly build a list of positions to modify using extensive filtering capabilities.

• Modify multiple positions with one change job.
• Review changes (highlighted on UI), and save change requests as drafts.
• Share drafts with colleagues for a review before finalizing the changes.
• Download logs to report on all mass changes performed in the system.
• Configure additional fields in the Position data object that can be modified as part of a mass change request, or
used as filters.
• Able to edit the Custom Date field through Mass Data Management
2.1 Permissions for Mass Data Management
To perform mass changes and related tasks, you must have the following permissions.
Permission Type Permission Category Permission Name Result
Administrator Manage Mass Data Enable Mass Data Provides access to the
Management Management Admin Center Mass Data
Management page.
User Miscellaneous Permissions MassChangesJob Grants access to create and

manage mass change job con-
MassChangesJobConfiguratio
figuration and create mass
n
change requests.

Mass Data Management PUBLIC 5
2.2 Configuring the MassChangeJobConfiguration from
Manage Data
Before you create your first mass change request, you must configure the UI to include data object fields that can
be filterable, editable, and visible.
Context
The mass change UI configuration acts as a canvas for all your mass data transactions. The different sections of
the mass change UI aren't preconfigured by default. As the administrator, you can configure these sections by
adding fields from the target data object to:
• Search data
• Display data, and
• Modify data.
Therefore, creating a mass change UI configuration is necessary to be able to create change requests.
 Note
You can only have one mass change UI configuration for each instance.
Procedure
1. Go to Admin Center Manage Data .

2. Create a new MassChangesJobConfiguration.
3. Enter an externalId, name, and select the targetGOType as Position.
4. Optional: Modify the default value set on the minRecordLimitToTriggerJob field.
Based on this value, your mass change request is processed synchronously (instantly) or asynchronously (in
the background). If the number of records you’ve modified exceeds this value, the mass change request
is processed asynchronously. The data to process includes your changes, and changes resulting out of
associated business rule execution. Changes resulting out of business rule execution are always processed
asynchronously.
 Note
The user-defined value must be less than or equal to 50.
5. Add fields from the position data object to the configuration, by selecting from the fieldName dropdown.
 Note
• The <effectiveStatusStr> field is added to the configuration by default, and can’t be removed.

6 PUBLIC Mass Data Management
• Fields of data type User aren’t supported currently.
• Standard position associations such as Right to Return, and Parent Position aren’t supported currently.
• If you have fields set to Not Visible in position object, the fields won’t be displayed in Manage Data
under MassChangesJobConfiguration.
6. To configure a field to be filterable by default on the mass change UI, select the corresponding defaultFilter
value to Yes.
7. To configure a field as a filter, select Details and set it as filterable.
 Note
If the field has a parent, ensure to add the parent field to the configuration and set it as filterable.
8. To configure a field to be editable as part of a mass change request, select Details and set it as editable.
 Note
• If the field has a parent, ensure to add the parent field to the configuration and set it as editable.
• Except <externalCode>, all other fields can be configured as editable.
9. Optional: Add matrix relationship to the configuration by selecting from the associationName dropdown.
 Note
By default, matrix relationship is editable as part of a mass change request. You can’t configure the
association to be filterable as it isn't supported.
10. Save the configuration.
Results
You’ve created a request job. You can perform either of the following actions from Take Action:
• Modify a configuration.
 Note
You can't modify a configuration if there are mass change requests in the Processing Draft status. You can
edit once the requests are moved to the Draft status.
• Delete an existing configuration.
 Caution
All drafts associated with a mass change configuration are deleted if you:
• Modify or delete fields from the job configuration.
• Delete the MassChangesJobConfiguration object.

Next Steps
Create a mass change request from Mass Data Management.
Related Information
Permissions for Mass Data Management [page 5]

Creating Mass Change Requests [page 8]
2.3 Creating Mass Change Requests
Modify multiple records simultaneously by creating a mass change request.
Prerequisites
• You’ve the Enable Mass Data Management permission.

• You've the permissions to view and/or edit different fields of the data object instances you intend to modify,
specifically fields that are Generic Objects.
• You’ve created a mass change UI configuration.
Context
You can create a mass change request to update position records only.
Procedure
1. Go to Admin Center Mass Data Management to view the overview page.

2. Initiate a search by mass change title or code in the search box to view the existing mass change requests.
3. To create a new mass change request, choose Create.
4. You can modify the title of your mass change request by selecting the (Edit)icon.
5. Enter a search criteria using the available filters.
 Note
Effective Date is the only filter criteria that's mandatory. Though it's initially preselected to show the current
date, you can select any other date in the past or future, as applicable.

Filters allowing multiple values selection appear with a  icon.
6. To change the default group of filters, select Adapt Filters. All filterable fields in your mass change UI
configuration are displayed here.
 Note
You can retain filter values while viewing the Draft screen in Mass Data Management. By hovering over
Other Filters you can also view the list of filter values applicable for that search result. Currently, a filter
group can contain a maximum 8 filters (excluding Effective Date).
To filter based on the matrix relationship for position, you can select a new filter Matrix Position in Adapt
Filters. You’re required to configure this field in Manage Data and Configure Object Definition for it to be
available in the New Position Mass Change Adapt Filters Matrix Position . This helps you update
positions in bulk with Matrix Position as a filter category.
7. Choose Go to initiate a search.
Records matching the filter criteria are fetched. Position and Start Date columns are added to the table
configuration by default.
 Note
If you initiate a search with no criteria in the search box, an empty page appears with no data. You need to
refresh the page to load the data again.
To change the table configuration, select  (Columns). All fields added to your mass change UI configuration
are displayed here.
 Recommendation
For a better user experience, we recommend adding not more than 15 columns.
8. Optional: Select  (Sort)to apply a sort criteria.
 Note
• You cannot sort by Foundation Objects and Matrix Relationship fields.

• In the Create New Position Mass Change the Reset option is available for the Sort By fields in the Sort
dialog box.
9. Select the records to modify, and choose Edit.
You can select a maximum of 1000 records at a time.

10. Modify the records as necessary.
• All editable fields in your mass change UI configuration are displayed here. The effective date you selected
as part of the filter criteria appears in read-only mode indicating that the changes take effect on the
respective date.
• If you've configured matrix relatonship in your mass change UI configuration, you can see Matrix
Relationships on the edit page. Only the matching matrix relationships for the selected positions are
available for you to edit. Whenever you add a new matrix relationship, or edit the existing relationship, the
change is applicable to all the selected positions.

 Note
• In the Matrix Relationship for Position section, you should select the values in a sequential order to
ensure the values are editable, if not the values will be in read-only mode.
For example, you configure 5 fields for Matrix Relationship For Position such as, Type, Related
Position, Custom Field 1, Custom Field 2, and Custom Field 3. Type and Related Position values are
required to be provided in order to make Customer Field 1 editable. If the Custom Field 1 value is
provided the system would enable Custom Field 2 and so on.
• When you modify a matrix relationship for a position, you can view the changes in the Matrix
Relationship for Position dialog box. The old matrix relationship record is crossed out and the new
value is displayed.
• You can't add a new matrix relationship by selecting a relationship type that already exists for any
of the selected positions.
• You can't delete existing matrix relationships.
• On incremental changes to the draft for Matrix Relationships, the edit page defaults to the
position's original value rather than to the last updated value. All other fields on the edit page
defaults to the last updated values.
Modified records are shown with a clickable link Modified. Select the link to see your edits, and the changes
resulting out of business rule execution.
11. Choose Apply and then OK to apply the changes to the selected records.
The Modified page appears. You can view a list of all modified records on this page.
 Note
The onChange rules configured on the modified fields are triggered on applying the changes. All changes
are applied to the selected records, and your mass change request is saved as draft. Depending on
the number of records you’ve modified, your mass change request is processed synchronously or
asynchronously. During asynchronous processing, your changes are being processed and the results will be
available. The status of your mass change request is momentarily set to DRAFT PROCESSING. You cannot
perform any changes to the mass change request until the status changes back to DRAFT. You can have at
most 10 drafts active at a given point in time. Drafts that remain unchanged for 30 days from the date of
creation are automatically deleted.
12. Optional: If you want to edit other records from the list, choose the All tab and make the necessary changes.
13. If you want to review records containing error, choose the Containing Errors tab.
A list of all records with errors appears.

14. Choose a record to resolve the errors, or discard the modifications.
15. Optional: To discard changes made to a single record or multiple records, select the respective records from
the list, and choose Discard Modifications.
You can also cancel the mass change request anytime as long as the request is in the draft status.
 Note
Cancellation of a mass change request leads to its automatic deletion.
16. Optional: At this point, you can share the mass change request with other users. To do so, go to the Mass
Actions Overview page and select the checkbox against your mass change request. Then select Share.

You can also add a custom message before sharing. An email notification is sent to all the recipients.
 Note
• You can share multiple mass change requests.

• Mass change requests can be shared with a maximum of 5 users.
• The shared users can see the mass change requests in read-only mode. They can’t modify or submit
the mass change request.
17. Submit the mass change request for further processing.
A mass change request is successfully created, and you’re redirected to the Mass Actions Overview page. The
change request is saved in the PROCESSING status.
Results
You’ve successfully initiated a mass change request. You'll receive an email notification after the request is
processed successfully. A log file is also created for reference purposes, which is available for 6 months from
its creation date.
Mass change requests failing to complete successfully or containing any errors are classified with the status
ERROR. You can review the change request or notify someone to resolve the errors.
Related Information
Configuring the MassChangeJobConfiguration from Manage Data [page 6]

Permissions for Mass Data Management [page 5]
2.4 After Submitting a Mass Change Request
After creating and submitting a mass change request the following changes take effect:
A mass change request is successfully created, and you’re redirected to the Mass Actions Overview page. The
change request is saved in the PROCESSING status.
 Note
• The changes take effect on the effective date selected.

• onSave rules configured with the data object are triggered.
• Workflows configured, if any, are triggered.
• The standard Position to Job Information sync process is also initiated.
• The text input in the search field is no longer case sensitive. Previously, the search was restricted, you
would get results only for the exact text input you added in the search field.

 Example
While searching a mass change request, the upper and lowercase letters are considered as the same
string values. For example, ABC, Abc, or aBc is considered as the same string value.
• In the Mass Actions Overview page, by default you can view the associated number of requests on All
Requests, My Requests and Requests Shared With Me tabs.
After submitting the mass change request, you can also view the updates to the position data from Manage Data.
Go to Manage Data and select Position in the search drop-down list. Then, search and choose the position which
has the updates from the submitted job, under the search drop-down list next to Position. You can view all the
details of the position here.
2.5 Deleting Mass Change Requests
You can delete mass change requests that are in the draft status from Mass Data Management.
Context
Deleting mass change requests will permanently delete all the draft data associated with it.
Procedure
1. Go to Admin Center Mass Data Management .

2. From the Status dropdown, choose Draft.
All mass change requests in the draft status appears on the All Requests tab.
3. If you want to delete a single mass change request or multiple requests, perform the following steps.
Otherwise, skip the step.
a. Choose requests that you want to discard.
b. Choose Delete.
 Remember
You can use the Delete option only for draft records. It is disabled if records of different statuses are
chosen for deletion.
c. Choose Ok.
The record is permanently deleted, and cannot be retrieved.

4. If you want to delete a single mass change request, perform the following steps. Otherwise, skip the step.
a. Open a mass change request that you want to discard.

b. Choose Cancel Discard .
The record is permanently deleted, and cannot be retrieved.

5. If you want to discard any modifications to position records of a mass change request, perfrom the following
steps.
a. Open a mass change request.
b. Go to the Modified tab, and choose a single or multiple records from the existing list of changes.
c. Choose Discard Modification.

3 Managing Mass Changes
Mass Changes allows HR Admins to create and run Mass Changes for the employees. HR Admins can manage
changes to employees’ job information and job relationships based on an Employee Group. Additionally, with this
feature, the HR Admins can efficiently execute changes to employees’ data such as; manager reassignments, or
reorganizations affecting a large number of employees.
Furthermore, HR Admins can manage the mass changes to Position objects using business rules. However, we
recommend using the Mass Data Management tool which provides good user experience such as, filter capabilities,
table view of results, draft option and multiple other features hence, providing better control to HR Admins in
managing the data
Related Information
Mass Data Management [page 5]
3.1 Mass Changes to Job Information and Job Relationship
Simultaneously make changes to a lot of job information and job relationship records.
Prerequisites
You have view and edit permissions for mass changes: Administrator Permissions Manage Mass Changes
Context
You can make effective-dated changes to employee records in 1 batch job. Common example for creating a mass
change is to move a lot of employees to a new manager, a new building, or a new project.
Procedure
1. Go to Admin Center Manage Mass Changes .

14 PUBLIC Managing Mass Changes
2. Create a new mass change.
3. Enter the required information.
For this field... ...do the following
Mass Change Name Enter a name
Employee Group Select a group from the list or create a new group. If you
select an existing group, you can select View to review the
members of that group.
Effective Date Select the date the change comes into effect.
Mass Change Area Select Job Information or Job Relationship or fields in those
areas
Field Select the affected field
New Value Enter the new value
Event Reason Select the relevant event reason, for example, Data Change.
4. Select Save to save this as a draft version. Select Save and Initiate to run the batch the immediately.
In the Mass Changes list, you can see all mass changes created in the system or filter to see those created by
you. For mass changes with the status Draft, select the mass change to open it again.
Results
Once the batch is run, the status changes to Completed Successfully or Completed with Errors. For batches with
errors, you cannot reinitiate them. However, you can copy them using Actions to create a new batch.
For successful batches, new records are created in the Job History for the affected employees.
You can see the results of the batch job in a CSV where necessary.
To view all the jobs created in Manage Mass Change, go to Manage Data and choose MassChangeDefinition in
the search field. All the created jobs are available under the search drop-down list, next to MassChangeDefinition.
3.2 Mass Changes to Positions
There is a mass change feature you can use to make changes simultaneously to a large number of positions.
Overview
• You can use a single rule to define the position target population and the change attributes.
• Changes are effective dated.

Managing Mass Changes PUBLIC 15
• Changes to positions can be synced to incumbents.
• The default is for the Mass Change Run object to be secured by a role-based permission (RBP). Only users with
the relevant permission can make mass changes.
 Note
For more information about Mass Data Management, please refer to the Related Information section.
Prerequisites
• The Mass Change Run object is RBP-secured by default. You grant access to it by going to the Admin Center
and choosing Manage Permission Roles . You can find the permission under Miscellaneous Permissions.
• You grant access to Manage Mass Changes for Metadata Objects also in Manage Permission Roles, this time
under Metadata Framework.
Restrictions
• If a pending position is valid for the change, but the effective start date is before the change date, the relevant
record can't be updated.
• No role-based permissions are applied to selecting and changing the positions.
• Only Set statements are allowed in the Select And Update Rule THEN condition.
• If any records in the mass change run contain an optimistic locking exception, then the whole batch will be
rolled back. For more information, see the Related Links section below.
Creating A New Mass Change Run
You create a mass change run by going to the Admin Center and choosing Manage Mass Changes for Metadata
Objects. Here's an example, showing the sort of entries you can make:

Here's what the fields you see here mean:
• Code
Unique code for the new mass change run.
• Name
Translatable name for the new mass change run.
• Object Type To Be Changed
Indicates whether the object is a position or a time object.
• Change Date
This is the date on which the changes take effect. All records (active, inactive, pending) valid from this date that
match the IF condition of the Select And Update Rule are included.
• Synchronize To Incumbents
This indicates whether the changes in the position objects should be synchronized to the incumbents.
• Select And Update Rule
Enter a rule that defines which objects are selected and what is updated. Use IF conditions to restrict the
number of objects to be changed by this mass change run. Use SET statements in the THEN condition to
define the new values of objects.
 Note
Only rules created with the Update Rule for Mass Change Run rule scenario can be selected. Only SET
statements are supported in the THEN condition.
• Execution Mode
You can choose Run or Simulate. When you choose Simulate, the mass changes aren't saved, but you can see
the result in the log. When you choose Run, the mass changes are executed and saved. You can monitor the
progress and check results of the job in the Scheduled Job Manager page.
 Note
The status of these jobs will continue to be available in the legacy Monitor Jobs page.
• Execution Status
This field shows the status of the mass change run:
• Scheduled means that the mass change run is scheduled and will run soon
• In Progress means that the mass change run is still running.
• Executed means that the mass change run was successful.
• Failed means that there were errors in the last mass change run.
• Log
The log shows information about the executed mass change run. The information includes the number of
updated and failed objects/records and CSV field with detailed information about each record.
 Note
The log is purged after six months.
If you select Simulate or Run as the execution mode and then save the mass change run, the system triggers
a QUARTZ Job (Name MassChangeRun_<Code><UniqueNumber>) that processes the change. So, it may take
a while before the run starts. You can review the status of the QUARTZ Job if you reload the mass change run in
Execution Status.
After the mass change run has finished, the user who started the mass change run receives an email. The
details can be found in the Log section of the mass change run.

 Note
In order to ensure that the mass change runs execute as smoothly as possible, we recommend that you enable
the rule cache.
1. In the Admin Center, go to Configure Object Definitions.

2. For the relevant mass change run, set the Use Rule Cache field to Yes.
The result is that the mass change run is much quicker than before, and you're significantly less likely to
encounter a timeout.
Once the Mass Change request is created, you can check the log in Scheduled Job Manager in Admin Centre and
when the Mass Change is completed then, the Execution status changes to Executed and the logs are generate.
To view the submitted jobs for position object inManage Data, go to Manage Data and choose Mass Change Run. All
the submitted jobs are available under the search drop-down list, next to Mass Change Run. You can also view the
execution status of the job here.
Processing Details
Let's assume the mass change run discussed above is executed. The assigned rule "PosJobTitleChange" would
look like this:
Before the run, the positions data in the system looks like this:

You set the change date of the mass change run to 12/31/2016. This means that not all position records are
relevant for this mass change run. Only records that are valid as of the change date or records that are valid after
the change date are relevant for the run. In the chart below, you can see 2 records that are only valid before the
change date. These are not valid for the mass change run.

Once the relevant records are found, they are passed to the rule defined in Select And Update Rule. Only those
matching the IF condition are changed. In the chart below, you can see that Position 2 is not changed at all because
it does not satisfy the IF condition.

Mass Changes to Composite Objects
It is also possible to modify the data of a composite object, such as Matrix Relationship. The rule shown in the
picture below is an example of such a rule.
The IF condition returns all positions that are assigned to company = SAP and that already have a matrix
relationship with Type = HR Manager Position and Related Positions is not equal to Expert Developer. The SET
statement updates this existing matrix relationship and sets the related positions to Expert Developer.

 Note
The SET statement on a composite object creates a new record if no record specified by the Select-Statement
in the SET-Condition was found. So, it's important to restrict this in the IF condition as shown in the screenshot
above.
Related Information
Optimistic Locking

4 Foundation Data
Foundation Data consists of information that defines your company, and everything else related to it such as the
organization, pay, job structures, and so on.
Foundation Data is commonly shared across the company. Therefore, it’s important to import foundation data
before importing employee data. You can import foundation data and also translate it to ensure that your
proprietary information of your company is available in different languages.
There are preconfigured templates available in Employee Cental to import Foundation Data. Each template
corresponds to a data object, also known as a Foundation Object (FO). Each Foundation Object stores a specific
type of foundation data.
Foundation Objects can be broadly classified into the following types, which include legacy Foundation Objects as
well as Metadata Framework Foundation Objects (Generic Objects):
1. Foundation Objects for structuring your business.

2. Foundation Objects for handling job-related areas.
3. Foundation Objects for handling pay-related areas.
4. Other Foundation Objects.
 Remember
Ensure you have the Administrator Permission Manage Foundation Objects Import Transaltions
permission to import data and perform translations for selected foundation objects
Related Information
Foundation Objects for Structuring your Business

Foundation Objects for Handling Job-Related Areas
Foundation Objects for Handling Pay-Related Areas
Other Foundation Objects
4.1 Importing Foundation Data

Create a database of information proprietary to your company by importing Foundation Data.
Prerequisites
Corporate Data Model must be configured with the required Foundation Object definitions.

Foundation Data PUBLIC 23
Context
Importing Foundation Data is one of the first steps in the data import process. You can import Foundation Data
using preconfigured file templates available in Employee Central for each Foundation Object.
 Tip
To ensure you’re using the up-to-date version of CSV template, always download a copy from the system.
This topic covers the process of importing Foundation Data with legacy Foundation Objects. For information about
importing Foundation Data and Translations with MDF Objects (also known as Generic Objects), refer to the
Related Information section.
In Employee Central, following objects are classified as MDF Objects:
• Legal Entity
• Local Legal Entity
• Pay Group
• Department
• Business Unit
• Job Function
• Job Classification
• Local Job Classification
• Cost Center
• Pay Calendar
• Division
Procedure
1. Go to Admin Center Import Foundation Data .

2. Select Download a blank CSV template.
3. Select a Foundation Object from the list.
A popup window appears prompting you to choose a location on your computer to save the template.
4. Save a copy of the template on your computer.
5. Update the template with required information.
Ensure that the template contains all the required columns. The order of columns in the template doesn’t
matter but it’s important that all columns exist.
6. To import the Foundation Data, select the Foundation Object from the Type field on the Import Foundation Data
page.
Before importing Foundation Data, it’s important that you keep note of the associations established between
Foundation Objects while setting up the Corporate Data Model. To ensure that the import is successful, you
must import data of dependent and referenced objects before importing the Corporate Data Model.
 Example
Let's suppose that you’ve created an association between Legal Entity and Department Foundation Objects,
where Legal Entity is associated with Department Foundation Object. As a result, the import file template

24 PUBLIC Foundation Data
of the Legal Entity Foundation Object has a dedicated column for Department. Therefore, to import Legal
Entity data, the Department data must exist in the system.
For more information about associations between different Foundation Objects, refer to the Related
Information section.
7. Choose a method of data import.
• Select Full Purge, if you’re importing the data for the first time, or you want to completely overwrite
existing data with information included in the template. Existing records not included in your import file are
unaffected.
 Example
Lets suppose there are existing Cost Center records as follows:
Sample Database Output

Cost Center ID Start Date Name Parent Cost Center
A January 1, 1900 Industries R & D Industries
B January 1, 1900 Corporate IT Corporate
A January 1, 2018 Research and Develop- Industries

ment
B May 1, 2019 Corporate IT IT
You add a new record for Cost Center B by importing data in Full Purge mode.
Sample Import File Data

RESULT:
• Existing records with Cost Center ID as A remain unchanged.
• There is a single record for Cost Center ID as B.

A January 1, 1900 Industries R & D Industries
A January 1, 2018 Research and Develop- Industries

ment
• Select Incremental Load, to update existing data.
 Note
This option is selectable for all Foundation Objects except Dynamic Role and Position Dynamic Role, which
support data imports in Full Purge mode only.

8. Specify the number of records present in your import file template in the Real-Time Threshold field.
 Note
• If the number of records is greater than 10, the data is imported in the background.
9. Select Choose File to select the file to upload.

10. (Optional) If you want the template to be encoded in a format other than Unicode (UTF-8) (default value),
select an encoding format from the File encoding dropdown.
11. (Optional) To check if there are any data discrepancies, select Validate Import File Data.
12. Select Import.
Next Steps
Repeat the process to import data with other Foundation Objects as required.
Related Information
Setting up Corporate Data Model

Importing Data Translations for Metadata Framework Foundation Objects [page 33]
4.2 Foundation Data Translation
By translating Foundation Data, you can ensure that proprietary information of your company is available in
different languages.
Since foundation data includes fundamental information about your organization, pay, and job structure, which is
reflected globally, you can create multilingual versions to facilitate users across the globe to view this information
in their preferred language. Foundation data is translatable only if the user's preferred language is supported by the
system. To find the list of supported languages, go to Options Change Language .
 Note
Foundation data isn’t translated in the People Profile. The People Profile shows basic foundation data such as
organizational information, such as division, department, location, and so on.
Related Information
Importing Data Translations for Legacy Foundation Objects [page 27]

Importing Data Translations for Metadata Framework Foundation Objects [page 33]
4.2.1 Importing Data Translations for Legacy Foundation

Objects
Create multilingual versions of data imported with legacy Foundation Objects.
Prerequisites
• Verify that foundation data is imported in your system.

• Verify that Provisioning is configured to:
• Activate the required language packs.
• Set the default language.
• Enable translation of Foundation Objects.
 Remember
As a customer, you don't have access to Provisioning. To complete tasks in Provisioning, contact
your implementation partner or Account Executive. For any non-implementation tasks, contact Product
Support.
These configurations are a part of a basic setup of Employee Central.
Context
In terms of classification, the following data objects are identified as legacy Foundation Objects.
• Location Group
• Geo Zone
• Location
• Pay Range
• Pay Grade
• Pay Component
• Pay Component Group
• Frequency
• Dynamic Role
• Workflow Config
• Event Reason
You can translate the name and decription attributes in all these Foundation Objects.

 Note
You can also translate custom fields in the Foundation Objects, provided they are of type translatable.
Translating foundation data in legacy Foundation Objects is a 3-step process:
1. Download the import template of the Foundation Object.

2. Update the template with the translations.
3. Upload the template into the system.
 Note
The following procedure shows how you can perform a mass translation of Foundation Object data. If you
want to add or update translations to specific instances of legacy Foundation Objects, refer to the Related
Procedure
1. Go to Admin Center Import and Export Data .

2. Select Download Template from the Select an action to perform dropdown.
Field Value
Select Generic Object Select FOTranslation.
Include dependencies Select:

• Yes (default value), to download a zip file containing
all templates corresponding to the parent object and
related child objects in CSV format. The zip file also
contains an additional file Import_Sequence.csv, con-
taining information about the import sequence that you
must follow.
• No, to download the template for the selected data ob-
ject only.
Include immutable IDs Select:

• Yes, to include the entity ID and the record ID in the
template.
• No (default value), to exclude the entity ID and the re-
cord ID in the template.
Exclude reference objects - visible when Include Select:

Dependencies is set to Yes. • Yes, to exclude the reference objects in the zip file.
• No (default value), tp include reference objects in the
zip file.
Key Preference Select one of the following:

• External Code.

Field Value
• Business Key (default value)
 Note
A business key for an MDF object is a set of fields of
the MDF object that can be used as a unique key.
Hide External Code - visible only when Key Preference is set Select one of the following:
to Business Key. • Yes
• No (default value)
Identity Type Select one of the following:

• User ID(default value)
• Assignment ID
3. Select Download.
A popup window appears prompting you to select a location on your computer to download the zip file. Select
an appropriate location and save the zip file on your computer.
4. Prepare the import file template with data to import.
The template is typically labeled as FoTranslation.csv.
The template is formatted to include the following columns:
Title Description
externalCode This column must contain the external code assigned to

all the existing legacy Foundation Objects by the system.
This value doesn’t correspond to any external code that
you’ve created or imported as an Administrator. It’s the
FoTranslation-specific external code that's created when
you configure your system to enable Foundation Object
translation.
foObjectID This column must contain the identifier assigned to

all existing instances of legacy Foundation Objects by
the system respectively. This identifier is created when
you configure the system to enable Foundation Object
translation.
foType This column must contain the type of the legacy Foundation
Object.
 Example
businessUnit, jobFunction, company, to name a few.
foField This column must contain the HRIS-field ID of all

translatable fields of a legacy Foundation Object. Typically,
the name and description fields of a given legacy
Foundation Object are translatable. However, you can also
translate custom fields in the Foundation Objects, provided
they are of type translatable.

Title Description
value.<locale ID> There's one column for each language pack selected in
Provisioning. These columns must contain translations of
the data that you’ve entered for the foField of a given foType
respectively.
 Remember
Support.
Following is an example of a translated file, the translations are highlighted:
 Example
5. To upload the template, select Import Data from the Select an action to perform dropdown on the Import and
Export Data page.
6. Select one of the following options:
• CSV File, if you’ve downloaded the template excluding any related dependencies. On select, a form appears
with the following fields:
Field Value
Select Generic Object Select FOTranslation.
File Select the file that you want to upload.
File Encoding Choose the correct file encoding for your data.
Purge Type Select Full Purge.
Suppress Redundant Date-Effective Records Select one of the following:

• Yes (default value)
• No

• External Code

Field Value
 Note
A business key for an MDF object is a set of
fields of the MDF object that can be used as a
unique key.
Use Locale Format Select one of the following:

• Yes - If selected, you must also select a locale.

Assignment ID
Date Format This field is hard-coded as MM/DD/YYYY.
• ZIP File, if you’ve downloaded the template including related dependencies. On select, a form appears with
the following fields:
Field Value
File Select the file to upload.
7. (Optional) Select Validate to perform a check before importing data.

8. Click Import.
If successful, data translations for legacy Foundation Objects are imported into the system.
Results
After the import, the system determines the language in which foundation data is shown to users based on the
following order of precedence:
1. Log on language of the user: The user's preferred language as selected in the Options Change Language
section.
2. Default company language: When there’s no translation is available in the logon language of the user. Default
company language is based on the configuration setting made in Provisioning.
 Remember
Support.
3. US English: When there’s no translation available in the default company language.

Related Information
Employee Central Configuration: Setting Basic Options

Importing Foundation Data [page 23]
4.2.1.1 Translating Data in Legacy Foundation Object

Instances
Add or change translations in existing instances of legacy foundation objects.
Prerequisites
Data translations for legacy foundation objects are imported in the system.
Context
After importing data translations for legacy foundation objects through the mass import method, you can modify
translations in an existing instance of a legacy foundation object if required. To do so, you must edit the respective
foundation object instance and modify the translations by adding or updating data as necessary.
 Recommendation
Follow this method only you want to add or change only a few terms in the legacy foundation object instance.
Example: Revising terms that have not been translated appropriately.
For information about mass importing translations for legacy foundation objects, refer to the Related Information
section.
Procedure
1. Go to Admin Center Manage Organization, Pay and Job Structures .

2. Select a legacy foundation object type from the first Search dropdown.
 Example
Location Group
3. Select a corresponding instance of legacy foundation object type from the second Search dropdown.
The selected data object instance is displayed on screen.

4. Go to Take Action Make Correction .
The data object is available in edit mode.
5. Click  (View Translations) against a given field in the data object.
 Note
Translatable fields of the data object are associated with the  icon.
A popup window appears with a list of supported languages and free text fields for entering translations. The
list of languages correspond to the language packs activated in Provisioning.
 Remember
Support.
6. Click Finished.
7. Enter the translations for other fields in a similar manner.
8. Click Save.
The foundation object instance is updated with the new translations.
Related Information
Importing Data Translations for Legacy Foundation Objects [page 27]
4.2.2 Importing Data Translations for Metadata Framework

Foundation Objects
Create multilingual versions of data imported with Metadata Framework foundation objects.
Prerequisites
• Verify that the following settings are made in Provisioning:

• Activate the required language packs.
• Set the default language.
 Remember
Support.

These configurations are a part of a basic setup of Employee Central.
• Verify that the following permission is granted: Import Translations.
Context
You can import data as well as translations for Metadata Framework Objects at the same time. In Employee
Centrall, the following data objects are identified as Metadata Framework foundation objects (also known as
Generic Objects).
• Legal Entity
• Business Unit
• Cost Center
• Division
• Department
• Job Classification
• Job Function
• Pay Group
• Pay Calendar
You can translate the name and decription attributes in all these foundation objects.
 Note
You can also translate custom fields in the foundation objects only if they are of type translatable.
Importing data and translations for a Generic Object is a 3-step process:
1. Download the import template of the Generic Object.

2. Prepare the import data as well as translations.
3. Upload the template into the system.
 Note
The following procedure shows how you can perform a mass import of Generic Object data and translations. If
you want to add or update translations in specific Generic Object instances, refer to the Related Information
section.
Procedure
1. Go to Admin Center Import and Export Data .

2. Select Download Template from the Select an action to perform dropdown.
Field Value
Select Generic Object Select a data object from the list

Field Value
 Example
Legal Entity
Include dependencies Select:

• Yes (default value), to download a zip file containing
all templates corresponding to the parent object and
related child objects in CSV format. The zip file also
contains an additional file Import_Sequence.csv, con-
taining information about the import sequence that you
must follow.
• No, to download the template for the selected data ob-
ject only.
Include immutable IDs Select:

• Yes, to include the entity ID and the record ID in the
template.
• No (default value), to exclude the entity ID and the re-
cord ID in the template.
Exclude reference objects - visible when Include Select:

Dependencies is set to Yes. • Yes, to exclude the reference objects in the zip file.
• No (default value), tp include reference objects in the
zip file.

• External Code.
 Note
A business key for an MDF object is a set of fields of
the MDF object that can be used as a unique key.
Hide External Code - visible only when Key Preference is set Select one of the following:
to Business Key. • Yes

• Assignment ID
3. Select Download.
A popup window appears prompting you to select a location on your computer to download the zip file. Select
an appropriate location and save the zip file on your computer.
4. Prepare the import file template with the required data.

In the template, there's one column for each language pack that you’ve selected in Provisioning. These
columns must contain translations of data corresponding to the translatable fields of the respective foundation
object.
 Remember
Support.
5. To upload the template, select Import Data from the Select an action to perform dropdown on the Import and
Export Data page.
6. Select one of the following options:
• CSV File, if you’ve downloaded the template excluding any related dependencies. On select, a form appears
with the following fields:
Field Value
Select Generic Object Select the respective foundation object for which you
want to import translations.
File Select the file to upload.
File Encoding Choose the correct file encoding for your data.
Purge Type Select Full Purge.
Supress Redundant Date-Effective Records Select one of the following:

• Yes (default value)
• No

• External Code
 Note
A business key for an MDF object is a set of
fields of the MDF object that can be used as a
unique key.
Use Locale Format Select one of the following:

• Yes - If selected, you must also select a locale.

Assignment ID
• ZIP File, if you’ve downloaded the template including related dependencies. On select, a form appears with
the following fields:

Field Value
File Select the file that you want to upload.
7. (Optional) Select Validate to perform a check before importing data.

8. Select Import.
Results
Foundation Data is viible to users in a language that is determined as follows::
1. Log on language of the user: The user's preferred language as selected in the Options Change Language
section.
2. Default company language: When there’s no translation is available in the logon language of the user. Default
company language is based on the configuration setting made in Provisioning.
 Remember
Support.
3. US English: When there’s no translation available in the default company language.
Related Information
Assigning Permissions to a Role
4.2.2.1 Translating Data in Metadata Framework Foundation

Object Instances
Add or change translations in existing instances of Metadata Framework foundation objects.
Prerequisites
Data translations for Metadata Framework foundation objects (also known as generic objects) are imported in the
system.

Context
After importing data translations for generic foundation objects through the mass import method, you can modify
translations in an existing instance of a generic foundation object if required. To do so, you must edit the respective
foundation object instance and modify the translations by adding or updating data as necessary.
 Recommendation
Follow this method only you want to add or change only a few terms in the generic foundation object instance.
Example: Revising terms that have not been translated appropriately.
For information about mass importing translations for generic foundation objects, refer to the Related Information
section.
Procedure
1. Go to Admin Center Configure Object Definitions .

2. Select a generic foundation object type from the first Search dropdown.
 Example
Legal Entity
3. Select a corresponding instance of generic foundation object type from the second Search dropdown.
The selected data object instance is displayed on screen.
4. Go to Take Action Make Correction .

The data object is available in edit mode.
5. Click  (View Translations) against a given field in the data object.
 Note
Translatable fields of the data object are associated with the  icon.
A popup window appears with a list of supported languages and free text fields for entering translations.
There is also an entry that shows the default value currently set for the selected field. The list of languages
correspond to the language packs activated in Provisioning.
 Remember
Support.
6. Click Finished.
7. Enter the translations for other fields in a similar manner.
8. Click Save.
The foundation object instance is updated with the new translations.

5 Employee Data Imports
A solution part of SAP SuccessFactors Employee Central to perform mass changes to employee data.
Employee Data Imports features as a dedicated method to help you execute changes to employee data in bulk.
Using CSV templates corresponding to each HRIS element in Employee Central, Employee Data Imports enables
you to manage changes to employee data efficiently.
Employee Data Imports can be used to manage data for different types of users in your company such as
employees, contingent workers, and so on.
Following are some of the prominent scenarios where mass data transactions can be administrated using
Employee Data Imports:
• Migrating user data from a third-party HRIS system to Employee Central.

• Adding new user data, or hiring users.
• Updating existing user data.
• Deleting user data.
• Terminating users.
• Rehiring users.
Currently, Centralized services support several participating entities to bring data consistency and a host of
performance-related improvements to the data import process. To know more about Centralized services, refer to
the Related Information section.
Related Information
Centralized Services for Employee Data Imports [page 39]

Prerequisites for Importing Employee Data [page 41]
5.1 Centralized Services for Employee Data Imports
Centralized services is an umbrella term for a collection of specialized services governing different processes in
Employee Central.
Centralized services is basically a framework that acts as a common platform supporting various features in
Employee Central, with the aim to bring consistency without compromising on quality.

Employee Data Imports PUBLIC 39
With Employee Data Imports, Centralized services work together to enable different HRIS entities to support
functions like business rules, identical record suppression, forward data propagation, and so on.
Centralized services are enabled by default, and are applicable to data imports initiated from the Import Employee
Data page or OData APIs.
Entities supported by Centralized services are either Universal or Admin Opt-out:
 Note
You have the option to deselect settings that are Admin Opt-out, in which case the respective entity exhibits
legacy behavior without Centralized services.
Centralized Services: Supported and Unsupported Entities on Imports
The following HRIS entities are currently supported by Centralized services on Imports:
HRIS Entities Configuration Type Dependency
Biographical Information Universal
Employment Details Universal
Job History Universal
Job Relationships Universal
Job Information Universal
Personal Information Universal
Global Information Universal

40 PUBLIC Employee Data Imports
HRIS Entities Configuration Type Dependency
Phone Information Universal
Email Information Universal
Social Account Information Universal
National ID Information Universal
Address Universal
Personal Document Information (Work Universal

Permit)
Global Assignment Universal
Emergency Contacts Universal
Recurring Pay Component Universal
Non-Recurring Pay Component Universal
Compensation Information Universal
Person Relationship Universal
Termination Details Universal
The following HRIS entities are currently not supported by Centralized services on Imports:
Unsupported Entities
Basic Import
Background Import
Composite (Zip) Data Upload
Consolidated Dependents
Extended Import
5.2 Prerequisites for Importing Employee Data
Before beginning the data import process, you must prepare your system to meet certain prerequisites.
Key Considerations
• To ensure that data is imported successfully, it’s imperative that you have a thorough knowledge of the HR data
to be migrated as well as the data models across both the applications.
• You must account for dependencies or constraints that can impact the data import process, if any. If there’s
Personally Identifiable Information or confidential data present, you must be aware of the parties who can
review and validate the data.

• Employee Central is set up and data models, rules, and foundation objects are configured in accordance with
the configuration work book.
• Role-based permission model is implemented in your system.
• Configuring the system for optimal import performance.
• Implementing input validation check on import data.
• To perform uploads in preferred languages supported by the system, ensure data translations are added to
FO's, GO's and Picklists.
 Note
At any given time, you can execute a maximum of three Employee Data Import jobs, simultaneously. If a new
job is submitted during this time, the new job is added to the queue until one of the ongoing jobs has completed
its execution.
Related Information
Implementing Employee Central

Implementing Role-Based Permissions
Foundation Data Translation [page 26]
5.2.1 Configuring Data Import Settings
Review the existing system settings to ensure an optimal performance during the data import process.
Context
Before you begin the data import process, be it foundation data or employee data, there are a few important
system settings you must review. Depending on the volume of data to be imported, you can configure these
settings accordingly. Based on established performance benchmarks, we also provide recommended values for
your convenience.
Procedure
1. Go to Admin Center Company System and Logo Settings .

2. Enter a value in the Maximum threadpool size for Employee Central and Foundation data imports field.
The thread pool size is an important factor in determining the time that the system takes to process data. With
a thread pool size of 'X', the system imports 'X' batches of data at a time.

 Recommendation
We recommend a thread pool size of 5.
3. Enter a value in the Set a batch size for employee and foundation data imports. (Enter a value between 1-100)
field.
The system divides and groups the records in your import file into smaller units called 'batches'. The batch size
is the number of records that the system processes in each batch. It's recommended that you set the batch
size value as 100.
 Note
A value greater than 100 is not considered, and is automatically truncated to the maximum value of 100.
4. Enter a value in the Scheduled Jobs Retention Period in days field.
This value corresponds to the number of days to retain details of the scheduled import jobs, for monitoring and
reporting purposes.
 Note
The recommended retention period for scheduled jobs is 180 days.
5. Save the settings.
The maximum number of records supported by Employee Central Imports is 30,000. If your import file has
more than 30,000 records, we recommend that you distribute the data into multiple files and upload each file
separately.
 Note
• For Employment based entities, the maximum number of records supported by Employee Central
Imports is 30,000 without rules execution. If there are large number of rules configured or if there are
cross-entity rules, then we recommend that you distribute the data into multiple files with a maximum
of 20,000 records and upload each file separately.
• For Person based entities, the maximum number of records supported by Employee Central Imports is
30,000. If your import file has more than 30,000 records, we recommend that you distribute the data
into multiple files and upload each file separately.
• At any given time, you can execute a maximum of three Employee Data Import jobs, simultaneously. If
a new job is submitted during this time, the new job is added to the queue until one of the ongoing jobs
has completed its execution.
• If an upload of an import file takes more than 2 hours, resulting in interruption, we recommended
that you split the file into two. Splitting your file ensures that you use system resources optimally. For
example, in the below table for Job Information import with rules, we recommend a maximum upload
of 20000 records. If the time taken to complete this upload is more than 2 hours, then in the next job
split the upload into two files of 10000 records each.
Recommended number of records allowed in a single file

Employee Data Import Entity upload
Basic Import 30000

Recommended number of records allowed in a single file
Employee Data Import Entity upload
Biographical Information, also referred to as Person Informa- 30000

tion Import.
Personal Information 30000
Addresses 30000
Person Relationship 30000
Phone Information 30000
Email Information 30000
National ID Information 30000
Personal Documents Information 30000
Emergency Contact 30000
Global Information 30000
Employment Details 20000 (with rules involved)
30000 (without rules involved)
Compensation Information 20000 (with rules involved)
Pay Component Recurring 20000 (with rules involved)
Pay Component Non-Recurring 20000 (with rules involved)
Job History 20000 (with rules involved)
Termination Details 20000 (with rules involved)
Results
You’re now all set to begin the data import process.
Related Information
Automatic Interruption and Cancellation of Import Jobs [page 181]

5.2.2 Role-Based Permissions for Employee Data Import
To import employee data and perform related tasks, you must have the required permissions.
You can define permissions for different roles before assigning them to users, so that they can perform tasks
permitted by their role. It’s useful when there are many users who can access the Import Employee Data page, and
you want to define the level of access for each user.
Administrator Permissions Employee Central Import Enable Workflows for selected Workflows attached with the
Settings entities selected Employee Central Im-
port entities are triggered
when you’re importing em-
ployee data.
Enable Business Rules for Business rules attached with

selected entities the selected Employee Cen-
tral Import entities are trig-
gered when you’re importing
employee data.
Enable execution of rules Business rules attached with

against NO_OVERWRITE the selected Employee Central
Import entities will also up-
date fields that are marked as
'NO_OVERWRITE' in your im-
port file template.
Enable Forward Propagation Data is propagated to effective

during Incremental Import dated records when you’re im-
porting data with the selected
Employee Central Import enti-
ties.
Support cumulative update of Country/region-specific data

country-specific data for global existing in the Employee Pro-
information import in full purge files is retained when you’re
importing Global Information
in full purge mode.
Enable RBP Access Validation Allows you to import em-

for EC Elements during ployee data with the selected
Imports Employee Central Import enti-
ties under User Permission
Employee Central Import
Entities . Additionally, it al-
lows you to import Job His-
tory and Compensation Infor-
mation for users belonging to
your target population only.
Import Employee Data Allows you to import new em-

ployee data and update data
for existing employe data.

Manage Foundation Objects Import Translations Import data and translations

for the selected Foundation
Objects to ensure that your
proprietary information of
your company is available in
different languages.
Manage Hires Rehire Inactive Employee You can rehire employees who
have previously worked at
your company.
Manage User Allow users to view all the jobs You can monitor jobs submit-
ted by all users.
Allow Retroactive Employee You can add changes before

Data Changes the earliest start date of a re-
cord.
Admin Center Permissions Monitor Scheduled Jobs Allows you to monitor your im-
port jobs using the Scheduled
Job Monitor tool.
User Permissions Employee Central Import Employee Central Import Allows you to import em-
Entities ployee data with the selected
Entities
Employee Central Import enti-
Supported Import Entities: ties.
• Biographical Information  Note

• Personal Information
Import permission for
• National ID Information Compensation Info also
• Addresses controls the import of
• Phone Information Recurring Pay Component

for all import permissions
• Email Information
• Social Accounts
Information
• Emergency Contacts
• Job History
• Personal Documents
Information
• Compensation Info
• Pay Component Non
Recurring
• Employment Details
• Job Relationships
• Global Assignment Details
• Person Relationship
• Termination Details

Related Information
Using Role-Based Permissions
5.2.3 Working with View-only Fields
For HRIS fields that are configured with Visibility as View in combination with Allow Imports status in the Manage
Business Configuration page, you can choose to allow or disallow data uploads.
HRIS Field Configuration Behavior
Visibility = View With imports, you can upload field values for this configuration.
If you have these fields as part of the template, values from the
Allow Imports = Yes
template are imported.
If you do not have these fields as part of the template, values

from the previous record are copied over to the record being
imported.
Visibility = View With imports, you cannot upload field values for this configura-
tion. These fields are not part of the template.
Allow Imports = No
However, values from the previous record are copied over to
the record being imported.
5.2.4 Enabling Security Scan of User Inputs
Configure the system to scan the data in the import files and take appropriate actions.
Context
As a security measure, you can setup your system to scan the data included in your import file and reject malicious
content, if any.
Procedure
1. Go to Admin Center Platform Feature Settings .
The Platform Feature Settings page appears where you can enable or disable platform features.
2. Select Security Scan of User Inputs.

3. Click Save.
Your system is now configured to perform a validation on import data.
5.2.5 Performance Benchmarks
Performance benchmarks are standards established with respect to the amount of time taken to import a set of
records with each employee data import entity.
 Note
If you encounter issues when performing mass uploads of more than 10k records, you may choose to
• Disable rule processing by disabling execution of rules from Employee Central Import Settings Enable
Business Rules for selected entities
• Trigger rules selectively by applying rule context when configuring them in the Manage Business
Configuration page.
These options are also available to APIs.
The benchmarks for each entity have been established in a test environment under the following conditions:
• The maximum number of records in the import file template for each entity applied was 10,000, unless
specified otherwise.
• Business rules are not applied while importing these records. If you have business rules applicable, there can
be a difference in the reported benchmark data and the actual data.
• Centralized services for Employee Central Imports is enabled, unless specified otherwise.
 Note
The time required to import is proportional to the number of records in your import file.
Performance Benchmarks for Employees

This table lists the latest optimization values for Employee Data Imports using Centralized services.
Approximate Time Taken (in

Employee Data Import Entity Purge Type minutes) Additional Information
Basic Import - 18 -
Biographical Information, also - 1 Parallel imports using multiple

referred to as Person Info Im- import files is supported.
port.
Employment Details - 1 -
Personal Information Full Purge 2 Parallel imports using multiple

import files is supported.
Incremental Load 2

Addresses Full Purge 2 Parallel imports using multiple

Incremental Load 3
Phone Information Full Purge 1 Parallel imports using multiple

Incremental Load 1
Email Information Full Purge 1 Parallel imports using multiple

Incremental Load 1
National ID Information Full Purge 2 Parallel imports using multiple

2
Incremental Load 2
Personal Documents - 1 -
Information
Emergency Contact - 1 -
Global Information Full Purge 5 Parallel imports using multiple

Incremental Load 4
Compensation Info Full Purge 2 -
Incremental Load 2 -
Pay Component Recurring Full Purge 3 -
-
 Note Incremental Load 2
The <Start Date> value

in the import file should
be the same as the
<Start Date> value
mentioned while import-
ing Compensation Info.
Pay Component Non- - 3 -
Recurring
Job History Full Purge 6 -
Incremental Load 6 -

Termination Details - 4` -
Performance Benchmarks for Dependents

Biographical Information for a - 50 Generate a unique PersonID-

batch of 20k records. External for each dependent.
 Tip
Suffix the ID with a “d” to
distinguish between em-
ployees and their corre-
sponding dependents.
Person Relationship for a - 50 -
batch of 20k records.
Personal Information for a - 50 -
batch of 20k records.
National ID for a batch of 20k - 50 National ID validations are

records. performed on Employee and
Dependents information alike.
For more information on how

the validations are performed,
refer to the Related Informa-
tion section.
 Note
The duration for import remains unchanged as these dependent entities are not yet available on Centralized
services.
Related Information
Validation Rules of National ID

5.3 Employee Data Import Process
A standard process to follow for performing various transactions on employee data through imports.
The Employee Data Import process involves 3 main steps. Following is a clickable diagram highlighting the different
stages in the process.
• Downloading Import File Templates [page 54]

• Preparing Data to Import [page 58]
• Uploading Import Files [page 99]
You must execute these 3 steps to perform any kind of bulk transactions on employee data.
To get started, go to Admin Center Import Employee Data .
Employee Data Import Use Cases and Import Sequence
The following use cases describe the data import sequence for regular or full-time employees.
 Note
To know about the data import sequence for contingent workers, refer to the Related Information section.
Adding New Employee Data/Hiring New Users

To add new employee data, hire users (permanent/internal or non-permanent/external ), or migrate data to
Employee Central, follow the recommended import sequence.
 Note
Entities marked with '*' are required. Others are optional.

Recommended Data Import Sequence
Entities to Import Additional Information
1. Basic User Information This step involves the following data imports:
• Basic Import*: Information such as the first name, last

name, email ID, and so on, is populated in the system.
User accounts are created.
• Extended Import: Information about each employee such
as the date of birth, citizenship, nationality, and so on, are
added to user accounts.
• Background Import: Information such as educational qual-
ification, certifications, work experience(internal and ex-
ternal), active community memberships, and so on, are
2. Biographical Information With Biographical Information* import, information that consti-

tutes the bio data of users such as the country/region of birth,
region of birth, person ID, and so on, is added to user accounts.
'Persons' are created.
3. Employment Information This step involves the following data imports:
• Employment Details*: Information such as the employ-

ment start date, hire date, stock grants, option grants, and
so on, are added to user accounts.
• Global Assignments: Information such as the assignment
type, assignment duration, and so on, are added to user
accounts.
4. Job Information This step involves the following data imports:
• Job History*: Information related to the current job assign-

ment is added to user accounts.
• Job Relationships: Information related to associations with
the current job assignment is added to user accounts.
5. Compensation Information This step involves the following data imports:
• Compensation Information*: Information such as the ap-

plicable pay group, pay type, payroll ID, and so on, is
• Pay Component Recurring: Information such as the fre-
quency of the recurring payments, the number of units,
the end date, and so on, is added to user accounts.
• Pay Component Non Recurring: Information such as the
component type, alternative cost center details (if any),
pay date, and so on, is added to user accounts.

Entities to Import Additional Information
6. Personal Information This step involves the following data imports:
• Personal Information*: Information such as the first name,

last name, gender, nationality, native language, marital
status, and so on, is added to user accounts.
• Global Information: Country/region-specific information is
added to the user accounts.
• Phone Information: Information such as the phone num-
bers, area code, country/region code, extension, and so
on, is added to user accounts.
• Email Information: Information such as the email type,
email address, and so on, is added to user accounts.
• Social Accounts Information: Information such as the do-
main, account ID, and so on, is added to user accounts.
• National ID Information: Information about national iden-
tity of employees as applicable to their respective coun-
try/region, is added to user accounts.
 Example
The social security number (SSN) in the United
States, the Permanent Account Number (PAN) in In-
dia.
• Addresses: Information such as the current address, al-

ternative address, address type, corresponding ZIP code,
and so on, is added to user accounts. Address information
can vary according to country/region.
• Emergency Contact: Information such as primary emer-
gency contact, back up emergency contact, and so on, is
Modify User Data
To modify existing user data, follow the data import process to import the corresponding entity data. There’s no
recommended import sequence in this case.
 Example
To modify employment information of users, import data for Employment Details entity.
Delete User Data
Deleting user data is a sensitive case as it can cause downstream implications, and must be carried out carefully.
You can import data to delete information associated with a single entity or multiple entities together. For more
information, see Employee Data Deletion with Imports [page 124]
 Note
Data deletion through Imports is not supported for non-effective dated entities like Biographical Information,
Employment Information, and so on.

Terminate Users
To terminate users, follow the data import process to import Termination Details.
Rehire Users
Rehire Users with new User ID
To rehire users with a new user ID, the recommended import sequence is as follows,
1. Employment Details
2. Job History
Rehire Users with existing User ID
To rehire users with an existing user ID, follow the data import process to import Job History details.
For more information, see Rehire Employees with Data Imports [page 157].
Related Information
Importing Contingent Worker Data

Importing Dependent Information
5.3.1 Downloading Import File Templates
Begin the data import process by downloading an up-to-date version of the preconfigured import file template.
Prerequisites
• The HRIS elements corresponding to the data you want to import must be configured to include the required
data fields.
• The HRIS elements that support country/region-specific templates must be configured, to download country/
region-specific import templates.
• If Centralized services is not enabled for Person Relationship imports, to include country/region-specific
address information in Person Relationship imports, enable the Enable Country/Region-Specific support for
Address Information in Personal Relationships Imports (Not applicable for Centralized Services) setting on the
Company System and Logo Settings page.
 Note
By enabling this setting, fields and country/region-specific fields configured for the homeAddress HRIS
element will be available for selection while downloading import templates for Person Relationship. If the
setting isn't enabled and the field is-address-same-as-person is enabled, 9 hard-coded address fields
are available for you to include in the template, no matter whether the fields are configured in any data
model.

Context
Downloading the import file template from the server is recommended to ensure that you have the latest and up-
to-date version of the template. You can also choose to download a country/region-specific template, or customize
your template by selecting from the list of available fields.
Procedure
1. Go to Admin Center Import Employee Data .

2. Select Download Template as the action to perform.
3. Select an entity from the dropdown.
Based on your selection, additional options appear on the page.
4. Select at least one country/region from the Select Country dropdown.
Choose this option to download the template for the required country/region. This option appears only if the
entity you've selected supports country/region-specific information under the Available Data Fields column.
You can select multiple countries/regions if required.
 Note
For country/region-specific entities, you have an option to download the base model fields by deselecting
all the countries in the Select country/region.
5. (Optional) If you want to encode the template in a format other than Unicode (UTF-8), select an encoding
format from the File encoding dropdown.
6. Select the data fields to include in the import template from Available Data Fields.
This option appears only if the entity you've selected supports data field selection.
The selected fields appear under the Selected Data Fields column.
 Note
To remove a selected data field, choose  (Delete) against the respective field.
Mandatory fields or 'Business Keys', are automatically included under the Selected Data Fields, and can't
be removed. In SAP SuccessFactors, each record is identified by a set of unique identifiers known as
Business Keys. Based on the business keys, employee records created or updated respectively.
 Note
If you have selected multiple countries/regions, ensure that you select only the required fields as
custom data fields configured for other countries/regions that you haven’t selected can also appear in
the list.
Example: While downloading a Job Information template for Canada, custom fields configured for USA
also appear in the list of Available Data Fields.
7. Select Generate Template.

Next Steps
Prepare the template with data to import.
Related Information
Preparing Data to Import [page 58]

Configuring Country/Region-specific Elements
5.3.1.1 Import File Templates
SAP SuccessFactors provides preconfigured templates for importing different types of employee data.
An import file template is a CSV file intended to serve the purpose of importing a specific type of employee data.
Since Employee Central identifies and stores employee data in what are known as HRIS elements, there is an
import file template corresponding to every HRIS element involved in the data import process.
Import File Templates
Following are the import file templates available.
Corresponding HRIS
Element as Present in Supports Country/ Requires Role-based
Business Configuration Region-Specific Supports Manual Data Permissions: Employee
Import Template UI (BCUI) Templates? Field Selection? Central Import Entities
Basic Import No No Yes
Extended Import No No No
Background Import No No No
Biographical personInfo No Yes Yes

Information
Person Relationship personRelationsh No Yes Yes

ipInfo
Employment Details employmentInfo Yes Yes No
Global Assignments globalAssignment No Yes No

Info

Corresponding HRIS
Element as Present in Supports Country/ Requires Role-based
Business Configuration Region-Specific Supports Manual Data Permissions: Employee
Import Template UI (BCUI) Templates? Field Selection? Central Import Entities
Personal Information personalInfo No Yes Yes
Global Information globalInfo Yes Yes Yes
Recruit Information No Yes No
Termination Details employmentInfo Yes Yes Yes
Job History jobInfo Yes Yes Yes
Compensation Info compInfo Yes Yes Yes
Phone Information phoneInfo No Yes Yes
Email Information emailInfo No Yes Yes
Social Accounts imInfo No Yes Yes

Information
National ID Information nationalIdCard No Yes Yes
Addresses homeAddress Yes Yes Yes
Emergency Contact emergencyContact Yes Yes Yes

Primary
Personal Documents No Yes Yes

Information
Pay Component payComponentRecu No Yes No

Recurring rring
Pay Component Non payComponentNonR No Yes Yes

Recurring ecurring
Job Relationships jobRelationsInfo Yes Yes Yes
Compound Delete No No No
Using this template, you can import:
• Biographical Information
• National ID Information
• Phone Information

 Note
This template supports the import of multiple national IDs, phone numbers, and email IDs.
Related Information
Role-Based Permissions for Employee Data Import [page 45]
5.3.2 Preparing Data to Import
After downloading the import file template, the next step in the data import process is to prepare the data to import
in the required format.
Procedure
1. Ensure that all the required fields are present in the import file template.
2. Understand the format, the permitted values, and other attributes of each field in your import file template.
Refer to the corresponding subtopic of the entity for which you're importing data to for more information about
the business keys, Data Object tables, additional supported configurations, and related use cases.
3. Ensure that your spreadsheet management application supports the file encoding format you selected while
downloading the import file template.
Unsupported file encoding formats can cause special characters in your import file to get corrupt. If the field
labels or data contains a comma (,), ensure that the corresponding labels have quotes around them.
 Note
• Special characters supported: ~ ` ! @ # $ % & * ( ) _ - + = { } [ ] / : ; " ' . ? /.

• Special characters supported but require special consideration:
• Pipe (|): It acts as delimiter in imports for one-to-many association between two foundation
objects. So, it’s supported, but if used in externalCode of a foundation object, causes issues
when such an object is used in one-to-many association for another foundation object.
• Backward Slash (\) or Double Quote (“): If picklist labels contain the Backward Slash (\) or Double
Quote (“), these characters aren’t displayed on UI.
• Unsupported special characters: Caret (^).
• Picklist labels must be unique.
4. To retain leading zeros in your import file template, change the format of the required cell. To do so:
a. Right-click the cell, and select Format Cells.
b. On the Number tab, select the Text option.
c. Save your changes.

 Note
We've described the process in reference to the Microsoft Excel application, but the same logic can be
applied to other popular spreadsheet management applications.
5. Pay special attention while mapping data with fields of the following data types:
Expected input in
Data Type Description Sample Field import file Sample Value
STRING Custom (user defined) <custom-string1> Text/Alphanumeric/ ABC, 123ABC, 123

String fields number
STRING Preconfigured <company>, External code of the <1710>, <1710–

(systemic) String <location> corresponding MDF 2715>
fields Foundation Object
TextArea Preconfigured <notes> Text/Alphanumeric/ <12345ABCdef>

(systemic) String number
fields
HRIS_FINDUSER User-type fields <manager-id> Person ID <342152>
STRING Reference objects of <employee-class> Label of the picklist <Employee>,

type Picklist <Contractor>
 Remember
• Provide a
value
correspondin
g to your
locale.
• The system
always
considers
active picklist
values.
BOOLEAN <is-fulltime- Yes, No or an <Y>, <Yes>, <T>,

employee> equivalent value <True>, <1>, <N>,
<No>, <F>, <False>,
<0>
DATE <probation- Dependent on the • English US:

period-end-date> logged in user's 04/20/2019
language settings
• English UK:
20/04/2019
 Example
• Format for US
English:
MM/DD/
YYYY
• Format for UK
English:

Expected input in
Data Type Description Sample Field import file Sample Value
DD/MM/
YYYY
6. If your import file contains data of new employees, ensure that the <start-date> value in the initial records of
Job Information, Personal Information, and Compensation Information (with the Hire event) matches with
the Hire Date in their Employment Details.
With Centralized services enabled, the Employment Information <start-date> is updated with the effective
start date of the most recently processed Hire/Rehire record. This sync happens whenever a Hire/Rehire
record is modified or inserted.
Since Employee Central is an effective-dated system, any mismatch in the date values leads to data
inconsistencies.
7. If you're importing data for an entity other than Addresses and Job Relationship (Work Permit) imports, you
don't need to enter the <end-date> value in the import files.
Even if you specify a value, the end dates are calculated automatically based on the corresponding start dates.
8. Follow the recommended sequence for importing data for different roles.
Before you import employee data, the employee's manager and the HR representative data must be imported.
Related Information
Different IDs in SAP SuccessFactors HCM Suite

Field Requirements for the User Data File
Downloading Import File Templates [page 54]
5.3.2.1 Basic User Information Imports
Notable points to help you prepare data for importing Basic User Information.
General Information
Business Keys Data Field Definitions Additional Information
• STATUS Basic User Information: Data Field Basic User entity is currently not
Definitions supported by Centralized services.
• USERID
• USERNAME
• FIRSTNAME

• LASTNAME
• GENDER
• EMAIL
• MANAGER
• HR
• DEPARTMENT
• TIMEZONE
Configurations/Processes Supported with Basic User Information Imports
Basic User entity supports the following configurations/processes by default:
• Assignment ID Definition
For more information about each configuration/process, refer to the Related Information section.
Managing Passwords of Users Migrated to Single Sign On (SSO) Authentication

Protocol
New passwords generated with basic user imports will serve for basic authentication and token-based SSO only.
No emails are generated for resetting passwords. To reset passwords, go to your identity provider's administrator
panel.
Related Information
Assignment ID Definition with Data Imports [page 116]

5.3.2.2 Biographical Information Imports
Notable points to help you prepare data for importing Biographical Information.
General Information
User ID Biographical Information: Data Field Biographical Information entity is

Definitions universally supported by Centralized
services.
 Note
User ID is a case sensitive field. Ensure that you enter the correct value to avoid validation errors.
Configurations/Processes Supported with Biographical Information Imports
Biographical Information entity supports the following configurations/processes:
• Business Rule Configuration

• Document Attachment
• Identical Record Suppression
Related Information
Attaching Documents with Data Imports [page 160]

Identical Record Suppression with Data Imports [page 132]
Configuring Business Rules for Data Imports [page 162]

5.3.2.3 Employment Details Imports
Notable points to help you prepare data for importing Employment Details.
General Information
• User ID Employment Details: Data Fields Employment Details entity is

Definition universally supported by Centralized
• Hire Date
services.
 Note
User ID is a case sensitive field. Ensure that you enter the correct value to avoid validation errors.
 Remember
You cannot hire a user and set the new hire as a manager in the same import. You must first hire the user and
then update the manager in a second import.
Configurations/Processes Supported with Employment Details Imports
Employment Details entity supports the following configurations/processes:
• Rehire Former Employees (with a new User ID)
Rehire Users with a New Employment (New User ID)
You can rehire previous employees either with their old user ID or give them a new ID to start a new employment
record. While rehiring inactive employees with a new employment, the <Original Start Date> field located
under the Employment Information section of the Employee Profile highlights the effective start date of the
employee. Since the <Original Start Date> of the new employment is different as compared to the old
employment, when you import the rehire data, the system automatically updates the <Original Start Date>
field with the value provided in your import file.
You can configure your system to keep the Original Start Date of employees unaffected by data imports. To do so,
you must:

1. Add a custom date field to the employmentInfo HRIS element through the Business Configuration UI (BCUI).
For more information about using BCUI, refer to the Related Information section.
2. Download the import file template for Employment Information. Ensure that you’ve included the custom date
field in the list of selected fields.
3. While preparing import data, enter the <Original Start Date> of the old employment in the custom date
field.
4. Upload the import file template.
As a result, when the data is imported, even if the <Original Start Date> is updated, the custom date field will
always show the start date of the old employment.
 Note
To rehire a user with their old employment information and existing user ID, use the Job History import.
Related Information

Rehiring Former Employees with an Existing User ID (New Employment) [page 158]
Using Business Configuration UI
5.3.2.4 Global Assignment Imports
Notable points to help you prepare data for importing Global Assignment information.
General Information
• User ID Global Assignment: Data Fields Definition Global assignment is universally

supported by Centralized services.
• Assignment Start Date
As part of the data preparation process, review the following:
• Global Assignment configuration settings to match your requirement.

• Permissions for Global Assignment
• Event Reasons for Global Assignment
• Business Configuration for Global Assignment

Configurations/Processes Supported with Global Assignment Imports
Global Assignment entity supports the following configurations/processes by default:
With Centralized services enabled, several supported configurations/processes are enhanced and a few new
configurations/processes are supported, which are as follows:
• End Date Correction

Data Validation
Centralized services introduce several validations to ensure data consistency.
• When importing the Global Assignment record, the system checks whether there is an active job information
record, as of the global assignment start date and either successfully imports the global assignment record or
throws a validation, meaning that the import fails.
The status of the Job Information record, as of the global assignment start date, cannot contain any of the
following statuses: Termination, Retired, or No Show.
 Example
Job Information Record Import Date Import Result
Future termination record for Septem- Import a global assignment with start Successful
ber 30th date on September 15th
Future termination record for Septem- Import a global assignment with start Successful
ber 30th date on Oct 10th
Future rehire record for Oct 1st
Future termination record for Septem- Import a global assignment with start Failed with Validations
ber 30th date on Oct 10th
No future rehire record
Related Information

Configuring Global Assignment Settings
Permissions for Global Assignments
Creating Event Reasons for Global Assignments

Business Configuration for Global Assignments
Right to Return (Position Management)
5.3.2.5 Job History Imports
Notable points to help you prepare data for importing Job History.
General Information
• User ID Job History: Data Fields Definition Job (Information) History imports is
universally supported by Centralized
• Event Date
services.
• Sequence Number
Configurations/Processes Supported with Job History Imports
Job History entity supports the following configurations/processes by default:
• Business Rules
• Employee Data Deletion
• Forward Propagation of Data
• Workflow Configuration
Points to note for workflow configuration:
• Workflows are triggered only if your import file contains 1 record for each user. If there are multiple records
for the same user with at least 1 record requiring approval, the data for this user isn’t imported.
• Workflows are triggered only by the entity used in the import, for example, Job History. If no workflow is
triggered by the entity in the import, all changes are immediately saved to the database, including derived
entities, such as cross-entity rule results.
• Workflows are triggered only when a new Job History record is inserted in the import.
• Workflows aren't supported for the Update and Delete operations. This means that a workflow isn't
triggered when a Job History record with a configured workflow is updated, with or without derived entities
involved, such as Compensation Information.
• Workflows aren't triggered for a new hire record, with an exception for internal hires.
• Carbon copy (Cc) role notifications are supported.
• Cross-entity rules are supported.
For more information, refer to the linked topics listed in the Related Information section.
With Centralized services, several supported configurations/processes are enhanced and a few new
configurations/processes are supported, which are as follows:

• Sequence Number Generation and Correction
Sequence Number is not required if you have only 1 record to be imported for a user on a given event date.
However if you want to import multiple records for a user with same event dates, it’s essential to provide a
proper sequence number if you want to:
• Add multiple records for a user on the same date, or,
• Update one of multiple records existing for the user on a same date.
In such cases Sequence Number is an important factor to consider while preparing import data. The sequence
number generation and correction process helps handle scenarios where a sequence number is not provided
with import data.
Standard Events for Job History Imports
For a list of events supported, please refer to Events.
 Note
You must import Employment Details before importing Job History for Hire, Rehire, or Termination events,
because the start and/or end dates of the employment are always adjusted with these events.
Data Validation
Centralized services introduce several validations to ensure data consistency. Job History imports are validated for
the following scenarios:
• To ensure that active employees don't have inactive managers on the start date of the newly imported Job
Information record. To ensure that active employees don't have inactive managers during the validity of the
newly imported Job Information record, a warning message is raised. The validation runs for active employees
only.
• To ensure that exactly 1 hire record exists for each user, which is also the first record.
• To ensure the employment status doesn't change when the event or event reason is changed.
The validation checks whether your changes are compatible when you edit an existing record. You can change
a Location Change record and make it a Department Change by selecting another event reason, or you can
change 'New Hire' into 'Hire from Affiliate' - meaning it can be the same event or a different event, so long as
neither the old nor the new event introduces a status change.
It is possible that termination information changes the employment status, however, follow-on processes, such
as for Position Management, are not triggered.
• To ensure that working days for each week is greater than or equal to 0, or less than or equal to 7.
• To ensure that only the Set action is used in rules where Job Information or Job Information Model is the target
object.
• To ensure that the user can’t be their own manager, or the user can’t be their manager’s manager.
• To ensure that duplicate records are not created from cross-entity rules, the system checks onSave rules for
Job Information. The existing hire record is updated, however, forward propagation is stopped for the record.
If the rule result contains a 'special event', you can use a fallback event reason. This fallback event reason and

event in the cross-entity rule result to create an new Job Information record. (A special event is any event that
changes the employment status of the user. )
Position to Job Sync Validation: If you've Position Management enabled, you can execute position-specific
processes with Job History imports to validate the modified data. For more information, refer to the Related
Higher Duty: During the Job History import of higher duty or temporary assignment records, the validations
related to higher duty or temporary assignment are executed and the reference salaries and higher duty allowance
are calculated and updated, where required.
Employments Information: Derivation to ensure that the start and/or end date of Employment Information will
always be adjusted whenever a Job Information Hire/Termination/Rehire record is modified.
Global Assignment: Derivation to ensure that the start Global Assignment and end Global Assignment dates
on Global Assignment records are always adjusted when the corresponding records are imported using the Job
History import.
Pension Payouts: Derivation to ensure that the obsolete pension payout dates are always adjusted when the
corresponding records are imported using the Job History import.
Time Off: With Centralized services, it's possible to:
• Update fields other than the event reason field for a leave of absence.
 Note
A leave of absence can only be added in Time Off. The system does not allow Job Information events to be
created in the import.
• Update the expected return date field when a enabled in Time Management.
Related Information

Deleting Employee Data with a Single Entity [page 125]
Restricting Legal Entity Changes to an Employee Profile [page 178]
Configuring Workflows for Data Imports [page 175]
Forward Propagation of Data with Imports [page 137]
Rehiring Former Employees with an Existing User ID [page 157]
Sequence Number Generation and Correction with Data Imports [page 149]
End Date Correction with Data Imports [page 119]
Execute Position Processes During Job History Imports
Creating a Leave of Absence (LOA) Time Type
Creating a Fallback Event Reason Configuration
Follow-Up Processes After Job History Import

5.3.2.6 Job Relationships Imports
Notable points to help you prepare data for importing Job Relationships information
General Information
• User ID Job Relationships: Data Fields Definition Job Relationships entity is universally
• Event Date
• Relationship Type
Configurations/Processes Supported with Job Relationships Imports
Job Relationships entity supports the following configurations/processes by default:

When a field is changed in an existing job relationship, fields are changed in the import using a Modify
operation. However, for changes to the <Relationship Type> field, the changes are done in the import using
a Delete and Insert operation.
Job Relationships entity is universally supported by Centralized services. Several supported configurations/
processes are enhanced and a few new configurations/processes are supported, which are as follows:
• Business Rules
Data Validation
Centralized services introduce several validations to ensure data consistency. Job Relationships imports are
validated for the following scenarios:
• To ensure that the start date is not before the first Job Information Hire record.
• To ensure that active employees don't have inactive related users on the start date of the newly imported Job
Relationships record, an error message is raised. To ensure that active employees don't have inactive related
users during the validity of the newly imported Job Relationships record, a warning message is raised.

Related Information

5.3.2.7 Compensation Information Imports
Notable points to help you prepare data for importing Compensation Information.
General Information
• User ID Compensation Information: Data Fields Definition The compensation information

import is universally supported
• Event
by Centralized services.
Date
• Sequenc
e
Number
Configurations/Processes Supported with Compensation Information Imports
Compensation Information entity supports the following configurations/processes by default:

OnSave rules are executed for both records of the recurring pay component and Compensation Information.
However, the import will be prevented if there is no Compensation Information record for the user or if the
event reason was not set using the rules.
If identical records are included with the import, the system executes rules for compensation information to
see if there are any changes to compensation and recurring pay component data. If there are changes, then
they are saved in the system.
When you import data for a recurring pay component record that does not have a corresponding
Compensation Information record, the system creates a new Compensation Information to match the pay
component record.
Sequence Number is an important factor to consider while preparing import data. Since Job History supports
importing multiple records for a user with same event dates, it’s essential to provide a proper sequence
number if you want to:

The sequence number generation and correction process helps handle scenarios where a sequence number
isn’t provided with import data.
Data Validation
Centralized services introduce several validations to ensure data consistency. Compensation Information imports
are validated for the following scenarios:
• When Compensation Information is imported, the system checks that the associated Pay Component
Recurring is imported and validated.
• If the Allow Retroactive Employee Data Changes permission setting is activated, the system validates changes
prior to the earliest retroactive date but only shows a warning message. If the Allow Retroactive Employee Data
Changes permission setting is deactivated, an error message is shown.
Related Information

5.3.2.8 Recurring Pay Component Imports
Notable points to help you prepare data for importing Recurring Pay Component Information.
General Information
• Event Date Recurring Pay Component: Data Fields The Recurring Pay Component import
Definition is universally supported by Centralized
• User ID
services.
• Event Date
• Sequence Number

Configurations/Processes Supported with Recurring Pay Component Imports
Recurring Pay Component entity supports the following configurations/processes by default:

OnSave rules are executed for both records of the recurring pay component and Compensation Information.
However, the import will be prevented if there is no Compensation Information record for the user or if
the event reason was not set using the rules. The rule for setting the event reason can either be based
on Compensation Information or it can be a cross-entity rule between the Recurring Pay Component and
Compensation Information.
Only changes to the pay component data being imported are checked (whereas the Compensation Information
import checks the data for both compensation information and pay components).
When you import data for a recurring pay component record that does not have a corresponding
Compensation Information record, the system creates a new Compensation Information to match the pay
component record.
Sequence Number is an important factor to consider while preparing import data. Since Job History supports
importing multiple records for a user with same event dates, it’s essential to provide a proper sequence
number if you want to:
The sequence number generation and correction process helps handle scenarios where a sequence number
isn’t provided with import data.
• Calculated amount
The calculated amount of a bonus pay component (or any percentage pay component as Base Salary) is
automatically recalculated in the import.
Data Validation
Centralized services introduce several validations to ensure data consistency. Recurring Pay Component imports
are validated for the following scenarios:
• To ensure that the Recurring Pay Component is validated along with the corresponding Compensation
Information when the import is executed.
• To ensure that a business rule with recurring pay components as the base object can't create or delete other
recurring pay components.
• To ensure that only pay components defined as recurring can be created or updated for Compensation
Information.
Pay Component Value: For pay components of type Amount and Percentage, the system ensures that a null value
is not accepted. However, a value of 0.0 is accepted. For pay components of type Number, usually the value is not
provided by the user since it is calculated and set by the system. Any value is accepted, including null.

Frequency: Frequency is only checked if the canOverride field is set to False. An error is raised when the frequency
provided in the import does not match the value provided in the object definition. Both values can be null.
Related Information

Employee Data Deletion with Imports [page 124]
5.3.2.9 Non-Recurring Pay Component Imports
Notable points to help you prepare data for importing non-recurring pay component information.
General Information
• Issue Date Non-Recurring Pay Component Data The non-recurring pay component
Fields import is universally supported by
• Sequence Number (if enabled)
Centralized services.
• Type
• User ID
 Note
In the Incremental Load mode, if the
sequence number field,
<allow-import>=false: user_id +
pay_date + pay_comp_code is the
business key.
<allow-import>=true: user_id
+ sequence_number (when the
sequence number is enabled) is the
business key.
Sequence Number
For the non-recurring pay component data import process, the <sequence-number> field is a required field, but
not a business key, if it is disabled. This field accepts an alphanumeric value with the maximum of 38 characters.
With a unique sequence number, you can import multiple records having the same pay component on the same
day, without the risk of existing data being overwritten.

For the autogeneration of a sequence number, we store the sequence number as an alphanumeric value only if it
is autogenerated. If it's user input, the maximum amount is set to 38 characters (numeric or alphanumeric). If it's
autogenerated, the maximum amount is set to 36 alphanumeric characters.
This is applicable to the UI and imports:
• On the Edit UI and Take Action menu.

• For Odata APIs and imports in the Full and Incremental Load purge mode:
• If allow-import = no, then the sequence number is autogenerated.
• If allow-import = yes, then you need to provide the sequence number in the import file for all the
records in an Incremental Load. In the Full Purge mode, the sequence number is autogenerated for records
that do not have a sequence number. If required, there's a provision for you to provide sequence numbers
for the records as well.
Scenarios for Sequence Number Generation

Record 1 Record 2 Record 3 Record 4 Record 5
Mode of Input User input or sys- System generated User input User input System generated
tem generated
Sequence number A342S784GHYU78 Alphanumeric 57656 FH675GH7T5 Alphanumeric

KJ value value
Based on your business requirements, there are two cases related to sequence number configuration. To check
your existing configuration, go to Admin Center Manage Business Configuration Employee Central HRIS
Elements payComponentNonRecurring .
CASE 1: <sequence-number> isn’t configured or is disabled
The system automatically generates a sequence number for each user record. However, the value isn’t displayed on
the UI.
CASE 2: <sequence-number> is enabled
• In the Full Purge mode, the sequence number is automatically generated if it doesn't exist in the import record.
• In the Incremental Load mode, ensure that there are unique values in the <sequence-number> field for each
user record.
Configurations/Processes Supported with Non-Recurring Pay Component

Imports
Non-Recurring Pay Component entity supports the following configurations/processes by default:

A workflow is created for each record resulting in multiple records being processed for a user. Earlier, a
workflow was created for only one user record. The remaining records for the user weren't processed

Data Validations
Centralized services introduce several validations to ensure data consistency. Non-Recurring Pay Component
imports are validated for these scenarios:
• A non-recurring pay component record that refers to a time account payout record, can't be deleted.
• The payment date can't be changed for a non-recurring pay component record that refers to a time account
payout record.
• A non-recurring pay component record is imported only if a user's Job Information record exists.
• The pay component associated with a non-recurring pay component record is active and non-recurring.
• An import file doesn't have a non-recurring pay component record with multiple data operations for the same
business key. For example, an import record doesn't have an entry for a Create operation and then a Delete
operation with the same business key.
• Duplicate sequence numbers do not exist in an import record for a user.
Related Information

5.3.2.9.1 Use Cases: Non-Recurring Pay Component Imports
Notable scenarios related to non-recurring pay component imports on Centralized services.
Prerequisites
You've enabled Admin Center Company System and Logo Settings Enable Centralized Services for Non-
Recurring Pay Component Information (Applicable only for data imports from UI and API)
Full Purge Mode with Sequence Number Enabled
For this scenario, the sequence number field is enabled with the attribute allow-import=true.

Sample User Data
Issue Date (dd/mm/
yyyy) User ID Pay Component Amount Sequence Number
01/08/2022 User123 Bonus 100 1
14/09/2022 User123 Bonus 120 2
14/09/2022 User123 Bonus 125 3
You add these records by importing data in the Full Purge mode.
Sample Import Data

Issue Date (dd/mm/
14/09/2022 User123 Bonus 140 1
14/09/2022 User123 Bonus 150 2
Result
The user record that's effective on August 1st is deleted from the database and the two records with the sequence
number and amount provided for each are imported.

Issue Date (dd/mm/
14/09/2022 User123 Bonus 140 1
14/09/2022 User123 Bonus 150 2
Full Purge Mode with Sequence Number Disabled
For this scenario, the sequence number field is either enabled with the attribute allow-import=false or the
sequence number field is disabled.
Sample User Data

Issue Date (dd/mm/yyyy) User ID Pay Component Amount
01/08/2022 User123 Bonus 100
14/09/2022 User123 Bonus 120
14/09/2022 User123 Bonus 125
You add these records by importing data in the Full Purge mode.
Sample Import Data

14/09/2022 User123 Bonus 140
14/09/2022 User123 Bonus 150

Result
The user record that's effective on August 1st is deleted from the database and the two records with the amount
provided for each are added.

14/09/2022 User123 Bonus 140
14/09/2022 User123 Bonus 150
 Note
In the Full Purge mode, the sequence number is automatically generated if it doesn't exist in the import record.
However, we recommend that you provide the sequence number in the import file.
Incremental Load with Sequence Number Enabled
For this scenario, the sequence number field is enabled with the attribute allow-import=true.
Use case 1
Sample User Data

Issue Date (dd/mm/
01/01/2022 User123 Bonus 200 1
01/01/2022 User123 Bonus 400 2
You add a record by importing data in the Incremental mode.
Sample Import Data

Issue Date (dd/mm/
01/02/2022 User123 Meal Allowance 800 1
Result
With the new issue date and pay component but with the same sequence number, the user record that matches
the business key (User ID + Sequence Number) is automatically updated, keeping the second record as is.

Issue Date (dd/mm/
01/01/2022 User123 Bonus 400 2

Use case 2
Sample User Data
Issue Date (dd/mm/
01/01/2022 User123 Bonus 200 1
01/01/2022 User123 Bonus 400 2
Sample Import Data

Issue Date (dd/mm/
Result
With the new issue date, pay component, and sequence number, a new user record is added to the existing records
as there isn't a record that matches the business key (User ID + Sequence Number).

Issue Date (dd/mm/
01/01/2022 User123 Bonus 200 1
01/01/2022 User123 Bonus 400 2
Incremental Load with Sequence Number Disabled
For this scenario, the sequence number field is either enabled with the attribute allow-import=false or the
sequence number field is disabled.
Use case 1
Sample User Data
01/01/2022 User123 Bonus 200
01/01/2022 User123 Bonus 400
Sample Import Data

01/01/2022 User123 Bonus 800
Result

With the same issue date and a different amount, the first user record that matches the business key (User ID +
Issue Date + Pay Component) is updated automatically and the other record is deleted.

01/01/2022 User123 Bonus 800
Use case 2
Sample User Data
01/01/2022 User123 Bonus 200
01/01/2022 User123 Bonus 400
Sample Import Data

01/01/2022 User123 Meal Allowance 800
Result
With the same issue date and a different pay component, a new record is created in addition to the existing records
as there isn't a record that matches the business key (User ID + Issue Date + Pay Component).

01/01/2022 User123 Bonus 200
01/01/2022 User123 Bonus 400
Use case 3
Sample User Data
01/01/2022 User123 Bonus 200
01/01/2022 User123 Bonus 400
Sample Import Data

01/02/2022 User123 Bonus 800
Result
With a different issue date and same pay component, a new record is created in addition to the existing records as
there isn't a record that matches the business key (User ID + Issue Date + Pay Component).

01/01/2022 User123 Bonus 200
01/01/2022 User123 Bonus 400
01/02/2022 User123 Bonus 800
Use case 4
Sample User Data
01/01/2022 User123 Bonus 200
01/01/2022 User123 Bonus 400
Sample Import Data

Result
With a different issue date and pay component, a new record is created in addition to the existing records as there
isn't a record that matches the business key (User ID + Issue Date + Pay Component).

01/01/2022 User123 Bonus 200
01/01/2022 User123 Bonus 400
5.3.2.10 Personal Information Imports
Notable points to help you prepare data for importing Personal Information.
General Information
Business Keys Data Field Definitions Additional Supported Configurations
• Person ID External Personal Information: Data Fields Personal Information entity is

• Event Date
services.

Configurations/Processes Supported with Personal Information Imports
Personal Information entity supports the following configurations/processes:

Related Information

5.3.2.11 Global Information Imports
Notable points to help you prepare data for importing Global Information.
General Information
• Country Global Information: Data Fields Definition Global Information entity is universally
• Event Date
• Person ID External
Configurations/Processes Supported with Global Information Imports
Global Information entity supports the following configurations/processes:


Cumulative Update of Country/Region-Specific Information
Global Information supports updating existing country/region-specific information, even when you're importing
data in Full Purge mode.
To do so, you must have the Support cumulative update of country-specific data for global information import in full
purge mode permission.
 Example
Let's suppose a user has Global Information as follows:
Sample Global Information

Event Date (dd/mm/
yyyy) Person ID External Country/Region Custom String 1 Custom String 2
01/01/2021 mhoff USA Sample_Data_1 Sample_Data_2
01/01/2021 mhoff DEU Sample_Data_3 Sample_Data_4
You add new records by importing Global Information in Full Purge mode.
Sample Import Data

Event Date (dd/mm/
If you've the Support cumulative update of country-specific data for global information import in full purge mode
permission, the existing country/region-specific record of the user is updated.

Event Date (dd/mm/
01/01/2021 mhoff DEU Sample_Data_3 Sample_Data_4
If you don't have Support cumulative update of country-specific data for global information import in full purge
mode permission, the first record is updated with the new import data since the business keys match and the
second record is deleted.

Event Date (dd/mm/

Related Information

5.3.2.12 Phone Information Imports
Notable points to help you prepare data for importing Phone Information.
General Information
• Person ID External Phone Information: Data Fields Definition Phone Information entity is universally
• Phone Type
Configurations/Processes Supported with Phone Information Imports
Phone Information entity supports the following configurations/processes:

Related Information


5.3.2.13 Email Information Imports
Notable points to help you prepare data for importing Email Information.
General Information
• Person ID External Email Information: Data Fields Definition Email Information entity is universally
• Email Type
Configurations/Processes Supported with Email Information Imports
Email Information entity supports the following configurations/processes:

Related Information


5.3.2.14 Social Account Information Imports
Notable points to help you prepare data for importing Social Account Information.
General Information
• Person ID External Social Account Information: Data Fields Social Accounts Information is
• Domain
services.
Configurations/Processes Supported with Social Account Information Imports
With Centralized services enabled, Social Accounts Information entity supports the following configurations/
processes:

Related Information

Employee Data Deletion with Imports [page 124]

5.3.2.15 National ID Information Imports
Notable points to help you prepare data for importing National ID Information.
General Information
• Person ID External National ID Information: Data Fields National ID Information entity is

• National ID Card Type
services.
• Country
Configurations and Processes
National ID Information entity supports the following configurations/processes:

• National ID Assignment
Related Information

Using Temporary National ID While Hiring an Employee [page 87]

5.3.2.15.1 Using Temporary National ID While Hiring an
Employee
Provide a temporary national ID in the import template for employees who don't have a valid national ID during the
hiring process.
Prerequisites
• Verify if the required user accounts exist in the system.

• Verify if the fields, isTemporary and temporary-id are enabled in the nationalIdCard HRIS element. To check
the existing configuration, go to Admin Center Manage Business Configuration Employee Central HRIS
Elements nationalIdCard .
 Note
Ensure that the national-id field is not configured as a mandatory field.
For information about a complete list of fields available for nationalIdCard element, refer to the Related
Procedure
1. Go to the Admin Center.

2. In the Tools Search field, type Import Employee Data.
This brings up the Import Employee Data page.

3. From the Select the action you want to perform drodown, choose Download Template.
4. From the Select an entity dropdown, choose National ID Information template.
5. Generate the template.
To know more about downloading templates, refer to Download Templates.

6. In the downloaded template, enter Yes in the Temporary ID Available column.
7. Provide the temporary ID of the employee in the Temporary ID column.
 Note
That this is optional. You can also leave this column blank.
8. Now, upload the import file.
To know more about uploading employee data, refer to Importing Files.

Results
On a successful import, the employee's temporary national ID is stored in the system. You can view the national ID
information on the Employee Profile page.
5.3.2.16 Address Imports
Notable points to help you prepare data for importing Address information.
General Information
• Person ID External Address Information: Data Fields Addresses entity is universally

Definition supported by Centralized services.
• Event Date
• Address Type
Addresses entity supports the following configurations or processes:

• Documents Attachment
End Dates for Addresses
Providing an end date in the address record for an employee isn't a mandatory requirement as it is automatically
calculated based on the respective start date. But if you intend to provide an end date, note the following.
For multiple records with same Person ID External, it's recommended that you provide End Date values in all such
records, or don't provide any value at all. Providing End Date value in some records and not in others results in
validation errors.

 Note
End dates explicitly provided in the import template will be considered only with Full Purge imports. If you are
importing data in Incremental Load mode, end dates are calculated automatically.
End Date Correction
End date correction is a method by which the system determines whether or not there can be gaps (time frame
between the end date of one record and the start date of the next record) between different address records of an
employee. While preparing import data, you can choose to specify an end date value along with other information
in your import file template. Based on whether you import the data in Incremental Load or Full Purge mode, the end
dates are adjusted automatically.
 Example
Let's suppose you import the following records in Incremental Load mode.
Sample Import Data

Person ID External Address Type Start Date Country/Region
104003 Home January 4, 2020 USA
104003 Home May 4, 2020 USA
104003 Home October 4, 2020 USA
After the data is imported, the output will be as follows:

Person ID External Address Type Start Date End Date Country/Region
104003 Home January 4, 2020 May 3, 2020 USA
104003 Home May 4, 2020 October 3, 2020 USA
104003 Home October 4, 2020 December 31, 9999 USA
Any date gaps between the address records are automatically adjusted. The end date of the last record is also
adjusted.
Now, if you add a new record that is active anywhere between the start date of the first record and the end date
of the last record.
Sample Import Data

Person ID External Address Type Start Date Country/Region
104003 Home February 4, 2020 USA

104003 Home January 4, 2020 February 3, 2020 USA
104003 Home February 4, 2020 May 3, 2020 USA
104003 Home May 4, 2020 October 3, 2020 USA
104003 Home October 4, 2020 December 31, 9999 USA
The end date of the first record is corrected in accordance with the start date of the newly added record. Also,
the end date of the new record is corrected in accordance with the start date of the third record. The reason
being, the end of any record can't be greater than the start date of the subsequent record. This process of end
date calculation holds true even if you don't provide an end date value in your import file template.
If you're importing data in Full Purge mode for the same address type with end dates provided, gaps in between
records are considered and end dates aren't corrected.
Let' suppose your import file template has the following records ready to be imported in Full Purge mode.
Sample Import Data

104003 Home May 4, 2020 June 4, 2020 USA
104003 Home October 4, 2020 November 4, 2020 USA
After the data is imported, the database output will be as follows:

104003 Home May 4, 2020 June 4, 2020 USA
104003 Home October 4, 2020 November 4, 2020 USA
Related Information


5.3.2.17 Emergency Contact Information Imports
Notable points to help you prepare data for importing Emergency Contact Information.
General Information
• Person ID External Emergency Contact Information: Data Emergency Contact Information entity
Fields Definition is universally supported by Centralized
• Name
services.
• Relationship
Several configurations and processes are supported as follows:
• Identical record suppression

• Business rule configuration
• Data deletion
You can delete all emergency contacts for an employee through import.
• Same relationship type
You can import emergency contact records with the same relationship type as the existing emergency contacts
of the employee in Incremental Load mode.
Data Validation
Data validations on Emergency Contact Import are introduced for the following:
• To ensure that the business key is unique.

• To ensure that the field country is filled for the address information of emergency contacts.
Deleting Primary Emergency Contact
You can't delete the record of a primary emergency contact for employees through data import. You must either
update an existing record as the primary record or import a new record (that will act as the primary record) before
deleting the existing primary record. However, to delete the primary record only, you can do it manually in People
Profile.

Related Information

5.3.2.18 Person Relationship Imports
Notable points to help you prepare data for importing Person Relationship Information.
General Information
• Person ID External Person Relationship: Data Fields Definition Person Relationship entity is supported
by Centralized services by default
• Event Date
through the setting Admin Center
Company System and Logo Settings
Enable Centralized Services for
Dependents (Applicable for data
imports from UI and API and saving
changes on Editing UI) .
With Centralized services enabled, several configurations and processes are supported as follows:
• Identical record suppression

• Forward propagation of data in fields
• Address fields are no longer available for you to include in the template for Person Relationship imports.
 Tip
To edit address information of dependents by import, set the is-address-same-as-person field to Yes
or import another template of address information for dependents.
• After you update the person relationship information for a dependent, the dependent's data, for example,
personal information and address information, is aligned automatically. This also applies to the employee's
other dependents.

 Note
If the dependent is also an employee in the same company, you can't delete the dependent's data expect
for the person relationship through a DELIMIT operation because the data is shared by the employee
records.
Data Validation
With Centralized services enabled, the following data validation is supported:
• A data validation process is introduced to ensure that the person ID external of employees is not reused in the
related-person-id-external field for dependents.
For separate data management of employees and dependents, employees and dependents must have different
person ID external even if in reality they are the same person.
• The setting Company System and Logo Settings Enable Address Validations applies to addresses of
dependents as well.
• Employee addresses aren't copied for dependents if any incorrect or invalid address information is found.
• When you import person relationship information, the dependents' other data will be validated.
Assigning Dependent as the Employee's Beneficiary
You can assign a dependent as a beneficiary only for Australian employees. To do so, you must enter the details of
the dependent beneficiary in the Is-Beneficiary column of your import file template.
 Note
There can only be one dependent beneficiary for each employee.
If you've assigned a dependent beneficiary for non-Australian employees, the system skips importing such
data. However, if the non-Australian employees have a pension payout, you can assign as many dependent
beneficiaries as required.

5.3.2.19 Personal Documents Information (Work Permit)
Imports
When preparing to import work permit data on the Centralized services, understand and comply with the following
requirements.
General Information
• Country Personal Documents Information: Data Social Accounts Information entity is

Fields Definition universally supported by Centralized
• Document Type
services.
• Document Number
• Issue Date
• User ID
 Note
• Importing work permits on the Centralized services is now based on user ID; previously, it's based on
person ID. Because one person can have multiple user accounts, so you could end up purging work permit
information of multiple users when you chose to purge data of one person. With a user ID-based importing
process, you only purge work permit information for the particular user ID you specified.
• Personal Documents Information supports data imports in Full Purge and Incremental Load modes.
Configurations/Processes Supported with Personal Documents Information

Imports
Personal Documents Information entity supports the following configurations/processes by default:
Use Cases
 Example
Data imports are validated differently before and after Issue Date is included in business keys.

Sample Work Permit Records - 1 Existing and 1 to Be Imported
Document Num-
Record User ID Country Document Type ber Issue Date
Record existing in Logged-in user's United States Work Permit 2283D2FBC2021 2021-10-01
system ID
Record in import Logged-in user's United States Work Permit 2283D2FBC2021 2022-04-09
file ID
If it's an Incremental mode
Before: Business keys consisted of User ID, Country, Document Type, and Document Number, but not Issue
Date. So, as the two records have identical business keys and they're considered as the same record, the
existing record would be simply updated to have a new issue date.
After: Business keys consist of all the five fields. So, as the two records don't have identical business keys, the
record in the import file will be added to the system as a new record.
There's no difference in Full Purge mode for this example.
Sample Work Permit Records - 2 to Be Imported

Document Num-
Record User ID Country Document Type ber Issue Date
Record 1 in import Logged-in user's United States Work Permit 2283D2FBC2021 2021-10-01
file ID
Record 2 in import Logged-in user's United States Work Permit 2283D2FBC2021 2022-04-09
file ID
Let's assume that, at the time of importing, no other work permit record existing in the system has a business
key identical to that of record 1 or record 2, whether the business key is a combination of the four or the five
fields.
Before: Business keys consisted of User ID, Country, Document Type, and Document Number, but not Issue
Date. So, as the two records have identical business keys, neither would be imported.
After: Business keys consist of all the five fields. So, as the two records don't have identical business keys,
they'll both be added to the system as new records.
Related Information


5.3.2.20 Termination Details Imports
Notable points to help you prepare data for importing employee termination details.
General Information
User ID Termination Details: Data Fields Definition Termination Details imports is

universally supported by Centralized
services.
When you import Termination Details data, the system creates both Termination Details and the corresponding Job
Information record with the termination date +1 day and the same event reason as was used in the Termination
Details import. You can terminate no-show new hires using the termination import as well.
Import Termination Details first and if needed, you can import Job Information to update any other details.
If data is imported in the wrong order (meaning, Job Information before Termination Details), the system still
creates a new Job Information termination record corresponding with the data in the Termination Details import.
It does it with sequence number = null, which results in the system determining the next sequence number and
using that. For example, if you import Job Information termination record first, it gets the sequence number "1".
Then when you import Termination Details, the system creates the Job Information record to correspond with the
Termination Details import, but since a Job Information record already exists on that date, the system will create
the new Job Information record with the sequence number "2".
 Note
Do not terminate managers and their direct reports in the same import. This leads to data issues and errors.
When a manager with direct reports is terminated, the system processes the termination of the manager
immediately, Then the system initiates two scheduled jobs, one to process the changes to direct reports and
another to process the changes to Job Relationships. A notification is sent to the user who performed the
action once the job is run successfully.
Configurations/Processes Supported with Termination Details Imports
Termination Details entity supports the following configurations/processes by default:
• Business Rules
• onSave rules with Job Information as source element and Job Information as the target element are
supported with the Trigger onSave Rules for HRIS Elements rule scenario.
• onChange rules for Job Information as source element are supported only with the Trigger onChange Rules
for HRIS Elements rule scenario.

• onPostSave rules are supported with Job Information as the source element.
• We do not recommend making any changes to the hire date or employment end date using rules. It is
technically possible, but may cause data inconsistencies.
• Cross-entity rules with Job Information or Employment Details as the source element have several
changes. Please refer to the Cross-Entity Rules with Centralized Services topic linked in the Related
• Forward Propagation
Forward propagation is supported only for the employee status field from Job Information.
• If there is no workflow configured for Employment Details but there is a workflow configured for Job
Information, then the workflow is not triggered.
• If there is no workflow configured for Employment Details or Job Information, then no workflow is
triggered.
• If workflows are configured for both Employment Details and Job Information, then the workflow for
Employment Information is triggered.
• For termination imports with workflows, only the Employment Details workflow rules are triggered.
• Preference is always given to an Employment Information workflow configuration. For users on a global
assignment or with standard employment, if no Employment Information workflow configuration is
found, then the system checks whether a Job Information workflow configuration exists and uses that
configuration to trigger the workflow.
However, when terminating a user on a global assignment, the system now uses the End Global
Assignment workflow rather than the Termination workflow as was previously done.
• Workflow approvals are only supported when terminating the employment of a user on global
assignment (meaning, final save for termination of an employment for a user with standard
employment or concurrent employment is saved in the legacy process).
• Workflow resubmit is only supported when terminating the employment of user on a global
assignment employment.
• Workflow updates are only supported when terminating the employment of user on a standard or
concurrent employment.
• When Termination Details are imported, it is possible to trigger an automatic recalculation of Time
Management processes, such as Termination End Handling and Accrual Recalculation.
Managing Termination Details for Employees with Concurrent Employment
The system allows for the termination of multiple employments for an employee in same import file.
For terminating the main employment of employees with concurrent employment, you must ensure that you also
set one of their active employments as their new main employment.

 Example
User ID of Concurrent User ID of Concurrent

Employee Name User ID of Main Employment Employment 1 Employment 2
John Doe jdoe jdoe_1 jdoe_2
The effective start date of concurrent employment 1 is July 1, 2019 whereas the effective start date of
concurrent employment 2 is December 1, 2019.
You can terminate the main employment of John only if you assign him new main employment. In this case,
you must assign concurrent employment 1 as the new main employment as its effective start date is before
concurrent employment 2.
To assign a new main employment, you must enter the user ID of an active concurrent employment under the <New
Main Employment> column in your import file template.
Position Management
For customers using Position Management, there are further considerations:
• For cases where transferring direct reports or the to-be-hired adaptation is required, we recommend using the
Termination Details import instead of the Job Information import since event reasons that change employment
status are not triggered in Job Information imports.
• For some events such as Furlough and Suspension, no transferring of direct reports or to-be-hired adaptation
is triggered when used in imports or the Job History UI.
Data Validation
Ther are several validations to ensure data consistency. Termination Details imports are validated for the following
scenarios:
• To ensure that there is only one termination date.

If changes are made, then the record is updated rather than a second termination record created.
• To ensure that there is no rehire record without a termination record in between the hire and rehire records.
• To ensure that an end date is included and not blank.
• To ensure that the end date is after the hire or start date.
• To ensure that the termination date and resignation date are in the correct format for the locale.
• To ensure that an event reason is included and not blank, and includes a valid event reason.
If the event reason is valid, then the external code is also valid.
• To ensure that the <person-id-external> field is included and not blank.
• To ensure that the <user-sys-id> field is included and not blank.
• To ensure that the external code for a foundation object is valid.
• To ensure that the external code for a generic object is valid.
• To ensure that values entered in picklist fields are valid.

• To ensure that values entered in worker fields are valid.
• To ensure that the mandatory fields for No Shows such as "Event Reason", "Ok to Rehire", "End Date" are
included rather than the fields mandatory for Termination if the event reason is 'No Show'..
• To ensure that an additional termination workflow is not created if a user has a pending workflow.
• To ensure that if the &&NO_OVERWRITE&& value is provided in the template for <User ID>, <Event
Reason>, <Person ID External>, and <Termination Date> fields, the system reminds the user that
this value is not supported for these fields.
Related Information

Cross-Entity Rules with Centralized Services
Follow-Up Processes After Termination Details Import
5.3.3 Uploading Import Files

Create new records or update existing records by uploading import files prepared with the required information.
Context
After you’ve downloaded the import file template and prepared the import data, you must upload the file to
Employee Central for creating or updating employee records as applicable. Once the file is successfully uploaded,
data is added or updated in the system accordingly.
 Note
Association validation for effective-dated entities and non effective-dated enties are performed during
employee data import.
Depending on the selected entity, you can configure how the data must be imported based on your requirement.
Employee Central provides two options:
Employee Data Import Types

Import Type Suitable for
Full Purge Adding new data, or replacing existing data with new data.
Incremental Load Updating existing data.
 Note
These options are also available while importing data using OData APIs.

Related Information
Uploading Import Files in Full Purge Mode [page 100]

Uploading Import Files in Incremental Load Mode [page 103]
5.3.3.1 Uploading Import Files in Full Purge Mode
Overwrite existing employee data with information in your import file by uploading data in full purge mode.
Prerequisites
• You've updated the import file with the required data to upload.
• There are no dependencies on the import data. For instance, before importing data for an employee, data for
the employee's manager and HR representative must be existing in the system.
• The data import settings are properly configured.
• You've reviewed the configuration of the respective HRIS element on the Business Configuration UI.
 Note
During data imports, the base configuration of the HRIS element takes precedence over its country/region-
specific and person type configurations. For instance, if <custom-string 1> is not a mandatory field
in the jobInfo HRIS element but mandatory in its contingent worker person type configuration, it is a
non-mandatory field for Job History data imports. If such fields are present in your import file without a
value, or not present in your import file at all, a null value is automatically added to them.
Context
Full purge imports are recommended when you’re importing data for the first time, or want to completely overwrite
existing information in the employee data files. You also have the option to upload multiple files together. For more
details, refer to the Related Information section.
Procedure

2. Select Import Data as the action to perform.
3. Select the entity corresponding to the data you want to import.

Based on your selection, additional options appear on the page. If you’ve selected Basic Import, select More
Options to further customize your import. For information about configuring advanced options with basic
imports, refer to the Related Information section.
4. If the entity you've selected supports a Purge Type, select Full Purge.
5. Select Browse to attach the import file from your computer.
6. (Optional) Depending on the selected entity, the Import Description field appears. Enter a brief job description.
7. (Optional) To select a data encoding format other than Unicode (UTF-8), choose from the File encoding
dropdown.
By selecting a proper file encoding format, you can represent data in different languages as necessary.
8. (Optional) To select the file locale other than English (United States), choose from the File Locale dropdown.
The options appearing in the dropdown correspond to the language packs selected during Employee Central
configuration. File Locale allows you to choose the language and locale for the data you’re importing, which
is especially important for date, number, and picklist fields, as the format can change based on the locale.
Selecting a file locale wouldn’t affect your default logon language or the language of your UI components.
9. (Optional) Depending on the selected entity, the Real-Time Threshold field is shown. Enter an appropriate
value.
You can change the Real-Time Threshold to specify a value lower than the default value shown. The user-
defined threshold value can’t exceed the default value. A default value is automatically displayed for the
selected entity.s If the number of records in your import file is greater than the Real-Time Threshold value, data
imports happens asynchronously. Otherwise, data is synchronously imported.
 Note
The mode of importing data (synchronous or asynchronous) is automatically determined depending on the
number of records in your import file.
10. (Optional) Select Validate Import File Data to check if there are any discrepancies in the data provided in the
template.
Run this check to ensure that there are matching import headers, and the CSV file you're uploading contains
valid data. If the entity for which you’re importing data supports Centralized services, and has a parent or child
entity, then data associated with the parent or child entity is also validated.
 Example
When importing Personal Information, the associated Global Information is also validated and vice versa.
When importing Compensation Information, the associated Pay Component Recurring information is also
validated and vice versa.
11. Select Import.
Results
The data is validated and the import process is initiated. After the import process is complete, email notifications
are generated. The email notifications also include details about any errors encountered during the process.
If you are importing data for an entity that has related entities, the related entity records are implicitly copied
over. For instance, Personal Information entity is related to Global Information, and they share a parent-child

relationship. When you're importing Personal Information on a future date, the Global Information associated with
the existing Personal Information is implicitly copied over and vice-versa.
 Note
Business rules are not executed on the copied over records.
Next Steps
After uploading the import file, you can:
• Select Monitor Job to:

• Track the progress of your import job. To monitor import jobs submitted by other users, you must have the
Allow users to view all the jobs permission.
• (For batch imports) Download failed records after a batch is completed, while the main batch job
continues.
 Tip
If some batches fail because of picklist unavailability, reimport the failed records.
If a job isn’t showing any progress, it can be because the UI isn’t displaying updated results. In such cases,
note the time stamp and report a case.
• Repeat the procedure to upload another import file.
 Recommendation
At any given time, you can execute a maximum of three Employee Data Import jobs, simultaneously. If a
new job is submitted during this time, the new job is added to the queue until one of the ongoing jobs has
completed its execution.
Related Information

Configuring Data Import Settings [page 42]
Configuring Additional Options with Basic Imports [page 106]
Uploading Multiple Import Files Together [page 108]

5.3.3.2 Uploading Import Files in Incremental Load Mode
Selectively update existing employee data by uploading data in incremental load mode.
Prerequisites
 Note
Context
Importing data in the Incremental Load mode is beneficial when you want to update specific information while
retaining a majority of existing employee data. You can also perform what is known as a Partial Import.
To perform a partial import, you must enter &&NO_OVERWRITE&& against fields in your import file, whose value you
want to retain.
 Note
• You cannot enter &&NO_OVERWRITE&& against fields that are business keys.
• Business rules consider updating fields marked as not to be overwritten, if you’ve the Enable execution of
rules against NO_OVERWRITE permission.
Procedure

Based on your selection, additional options appear on the page. If you’ve selected Basic Import, select More
Options to further customize your import. For information about configuring advanced options with basic
imports, refer to the Related Information section.

3. If the entity you've selected supports a Purge Type, select Incremental Load.
4. Select Browse to attach the import file from your computer.
5. (Optional) Depending on the selected entity, the Import Description field appears. Enter a brief job description.
dropdown.
By selecting a proper file encoding format, you can represent data in different languages as necessary.
The options appearing in the dropdown correspond to the language packs selected during Employee Central
configuration. File Locale allows you to choose the language and locale for the data you’re importing, which
is especially important for date, number, and picklist fields, as the format can change based on the locale.
Selecting a file locale wouldn’t affect your default logon language or the language of your UI components.
8. (Conditional) Define the Real-Time Threshold value.
defined threshold value can’t exceed the default value. A default value is automatically displayed when you
select an entity. If the number of records in your import file is greater than the Real-Time Threshold value,
the system imports the data asynchronously. Otherwise, data is imported synchronously. Partial imports are
always asynchronous.
 Note
The mode of importing data (synchronous or asynchronous) is automatically determined depending on the
number of records in your import file.
template.
Run this check to ensure that there are matching import headers, and the CSV file you're uploading contains
valid data. If the entity for which you’re importing data supports Centralized services, and has a parent entity,
then data associated with the parent entity is also validated.
Example: Global Information supports Centralized services, and is the child of Personal Information. Hence,
when data is validated as part of Global Information imports, the corresponding Personal Information is also
validated.
10. Select Import.
Results
The data is validated, and the import process is initiated.
Fields not having any values in your import file are substituted with default values. The default value can be:
• &&NO_OVERWRITE&&, for fields supporting partial imports.

• Null value, for all other fields.
If you are importing data for an entity that has related entities, the related entity records are implicitly copied
over. For instance, Personal Information entity is related to Global Information, and they share a parent-child
relationship. When you're importing Personal Information on a future date, the Global Information associated with
the existing Personal Information is implicitly copied over and vice-versa.

 Note
Business rules are not executed on the copied over records.
After the import process is complete, email notifications are generated. The email notifications also include details
about any errors encountered during the process.
Next Steps
After uploading the import file, you can:
• Select Monitor Job to:

• Track the progress of your import job. To monitor import jobs submitted by other users, you must have the
Allow users to view all the jobs permission.
• (For batch imports) Download failed records as soon as a batch is completed, while the main batch job
continues.
 Tip
If some batches fail because of picklist unavailability, reimporting the failed records resolve the problem. If
a job is taking unusually long time to complete, it’s possible that the UI isn’t displaying updated results. In
such cases, capture the time stamp and report the case.
• Repeat the procedure to upload another import file. Generally, you upload a single file to import data
corresponding to a respective entity. However, you also have the option to upload multiple files together. For
more details, refer to the Related Information section.
 Recommendation
At any given time, you can execute a maximum of three Employee Data Import jobs, simultaneously. If a
new job is submitted during this time, the new job is added to the queue until one of the ongoing jobs has
completed its execution.
Related Information
Partial Imports: Unsupported Fields [page 106]

Configuring Additional Options with Basic Imports [page 106]
Uploading Multiple Import Files Together [page 108]

5.3.3.2.1 Partial Imports: Unsupported Fields
Only certain fields in your import file template support Partial Imports.
If you want to perform a Partial Import while importing data in Incremental Load mode, you cannot update
information for:
• ADDRESS
• The default Address entity does not support Partial Import.
• Location and Emergency Contact Foundation Objects also refer to this address. Therefore these two
columns will not support Partial Import as well.
• WORK_PERMIT_INFO
• PAY_CALENDAR
• JOB_RELATIONSHIPS
• JOB_FAMILY
• DYNAMIC_ROLE*
• WF_CONFIG*
• WF_CONFIG_CONTRIBUTOR*
• WF_CONFIG_CC*
 Note
*: These fields are Foundation Objects.
5.3.3.3 Configuring Additional Options with Basic Imports
Select additional actions to be performed with basic employee data imports.
Prerequisites
You have selected More Options while importing basic employee data.
Context
You can configure specific tasks to be performed with basic user imports such as manager transfer, document
removal, and so on.

Procedure
1. Select the applicable options from the Basic Options tab.
Automatic Manager Transfer
Select this option... To...
Automatic Completed Document Copy to New Manager Move all the documents from the old manager's Completed
folder to the new manager's Completed folder.
Automatic Inbox Document Transfer To New Manager Move all the documents from the old manager's Inbox to the
new manager's Inbox.
Automatic En Route Document Transfer To New Manager Move all the documents from the old manager's En-Route
folder to the new manager's En-Route folder.
Automatic insertion of new manager as next document Make the new manager a part of the review process and
recipient if not already remove the old manager from accountability henceforth.
Automatic Document Removal
Select this option... To...
Remove Inactive Employees' In-Progress Documents Remove all in progress documents of inactive employees.
Remove Inactive Employees' Completed Documents Remove all completed documents of inactive employees.
 Note
To find options related to Automatic Manager Transfer and Automatic Document Removal, the Effective
Dated fields in Basic Import setting must be enabled in Provisioning.
 Remember
As a customer, you don't have access to Provisioning. To complete tasks in Provisioning, contact your
implementation partner or Account Executive. For any non-implementation tasks, contact Product
Support.
2. Select applicable options from the Compensation Options tab.

3. Save the settings.
Next Steps
Complete the basic data import process.

5.3.4 Uploading Multiple Import Files Together
Compress multiple import files together and upload them simultaneously as a Zip file.
Prerequisites
 Note
Context
Generally, you upload a single file to import data corresponding to a respective entity. However, if you have multiple
files to upload, you can compress them together into a Zip file and upload the single compressed file. The order in
which data is imported is as follows:
• Basic Import
• Personal Information Import
• Job History
Other data, if any, is imported without any particular order.
If you’re creating new employee records, ensure that your Zip file contains the following import files:
• Basic Import

Procedure

3. Select Composite (Zip) Data Upload.
4. Select a method of importing data from the Purge Type field.
• Full Purge, if you’re importing data for the first time or you want to completely overwrite existing data with
information included in the import file.
 Caution
With this option, all existing employee data (historic data included) corresponding to the selected
entity is removed. To keep existing information, you must include the same in the import file or create a
data backup, as required.
While importing data, if the system encounters fields without any value, null values are added to them.
• Incremental Load, to update employee data already existing in the system.
You can also use this option to perform a Partial Import, when only the required employee data is updated
and all the other details remain unchanged. To partially import data, you to enter &&NO_OVERWRITE&&
under those fields in your import file, whose value you don't want to modify. As a result, after you upload
the file in the system, except business keys, and fields having a value &&NO_OVERWRITE&&, all other
values will be updated with values provided in your import file.
While importing data, if the system encounters a field without any value, &&NO_OVERWRITE&&, or null
value is added to it depending on whether it supports partial import or not.
5. Select Browse to attach the Zip file from your computer.
6. (Conditional) Depending on the entity you’ve selected, the Import Description field appears. Enter a brief job
description.
dropdown.
By selecting a proper file encoding format, you can represent data in different language as necessary.
Selecting a file locale wouldn’t affect your default logon language or the language of your UI components. It
corresponds to the locale for which data is being imported. The options appearing in the dropdown are based
on the language packs selected during Employee Central configuration.
9. (Conditional) Define the Real-Time Threshold value.
defined threshold value can’t exceed the default value. A default value is automatically displayed when you
select an entity. If the number of records in your import file is greater than the Real-Time Threshold value,
the system imports the data asynchronously. Otherwise, data is imported synchronously. Partial imports are
always asynchronous.
 Note
The mode of importing data (synchronous or asynchronous) is automatically determined by the system
depending on the number of records in your import file. During an asynchronous import, the system
validates the first 10 records. Discrepancies, if any, results in errors. After you rectify the errors and upload
the file again, the import process will continue.

template.
 Tip
When importing data for new employees, validations like 'Person-ID-External' is invalid can appear. You can
ignore these validations and proceed with the import.
11. Select Import.
Results
The data is validated, and the import process is initiated. After the import process is complete, email notifications
are generated. The email notifications also include details about any errors encountered during the process.
Next Steps
After uploading the Zip file, you can monitor the import job by selecting Monitor Job.
Related Information

5.3.5 Scheduled Job Manager for Monitoring Jobs using

Imports
Monitor execution details and other statistics of each submitted job associated with employee data import.
Prerequisites
To monitor jobs submitted by you, you need the Administrator Permissions Admin Center Permissions
Monitor Scheduled Jobs
To monitor jobs submitted by others, you need the Administrator Permissions Manage User Allow users to
view all the jobs permission to use this feature.

 Note
With this permission enabled, in addition to viewing the jobs, you are able to access the Download Report link
from View Details in the Scheduled Job Manager.
Context
If the number of records in your import file is greater than the specified real-time threshold value, data imports
happen asynchronously. A job is submitted for further processing.
Procedure

2. Choose Scheduled Job Manager
The Scheduled Job Manager page opens in a tab in the browser, This page lists all the jobs (of type Employee
Data Import) that you have submitted.
3. Identify the job that you want to monitor.
4. Choose Actions View Details Download Status corresponding to your job, if you want to download a
copy of the job execution report.
The status file in a CSV format is automatically downloaded to your local system.
5. Choose Close to return to the Scheduled Job Manager page.
Related Information
Managing Scheduled Jobs in Admin Center
5.3.6 Troubleshooting
Information about typical error or warning messages that you may encounter during the data import process along
with their cause and resolution.
Error/Warning Message While Importing... What's the Cause? What's the Resolution?
- Required information was not Fill out all required

Missing required
field provided. information and upload the
file again.

- There's a duplicate record in Delete the duplicate record

Username already
exists your import file. and upload the file again.
- There's an inconsistent entry Ensure that the employee's

Manager Cycle
detected with this in the hierarchy field. own USERID is not listed.
manager ID — This field should show the
<manager id> manager's USERID. Also, the

employee must not appear
both above and below the
manager in the file.
The correct sequence is:
1. Manager’s data
2. HR Representative data
3. Employee data
- The manager's <USERID> Make sure that the manager's

Manager ID invalid
assigned for the employee <USERID> exists in the
doesn't exist in the database database.
If you're adding both the

employee and manager, make
sure that the manager is
added before the employee.
- The data in your import file Verify they the data you're
Internal system
error encountered is invalid/incorrect, or the importing is correct/valid.
while importing existing data is invalid.
record.
- There could be an invalid Verify the import data, make

The record you
value in the import file or the
entered is invalid. corrections as necessary and
record may no longer exist.
Please check the import the data again.
information and try

again.
The Date of Birth Biographical Information For some countries, the Verify the import data, make
does not correspond National ID information corrections as necessary and
to the National ID includes date of birth record import the data again.
associated with this of a user. This message

most likely appears when
user
you're updating the date of
birth, and the data does not
match the National ID record
associated with the user.

The Gender does Personal Information For some countries, the Verify the import data, make
not correspond to National ID information corrections as necessary and
the National ID includes gender data of a import the data again.
associated with this user. This message most

likely appears when you're
user
updating the gender data, and
the data does not match the
National ID record associated
with the user.
Personal information Personal Information This message most likely • When <person-id-
does not exist appears when a user's external> record for
<person-id-external> or a dependent does
a dependent's <person-id- not exist, import
external> is invalid. This biographical information
can happen due when: to define a new
person in the system.
• <person-id-
Thereafter, import
external> record
person relationship
for a dependent
information to associate
does not exist.
the dependent with the
• <person-id-
respective employee.
external> for a
dependent exists,
• To import personal
information of a
but not associated
user whose <person-
with an employee.
id-external> does
• You’re importing
not exist, you must
personal information for
import their basic
a user whose <person-
user information to
id-external> does not
create a <person-
exist.
id-external>, and
then import personal
information.
Failed to perform Job History This error message most Depending on the cause of
country specific likely appears when: the error, you can change
the file locale or associate a
validation. Please • You’re importing job
ensure this record country with the legal entity
history of employees,
and try importing the data
is associated with a and the dates do not
again.
valid Company record match the date format
for given dates associated with the file
locale selected during
import.

 Example
If your file locale is
set to English (United
States) and you’d like
to import job history
for employees from
Germany. While
Germany supports
the date format
DD.MM.YYYY, the
data you upload
is in the format
MM/DD/YYYY
(corresponding to
the English (United
States)) file locale.
If you specify dates
in the German date
format, the system
will generate an
error.
• A country has not been

associated with the Legal
Entity or, a country has
been defined but the
effective start date of the
country is in future (when
compared to the record
being imported).
Country is a • Emergency Contact This error message most Update the import file
required field and • Consolidated likely appears when you template with an appropriate
cannot be blank Dependents leave the <Country> field value in the <Country> field
blank while filling out and try importing the data
the <Address> field while again.
importing emergency contact
or dependents information.
<Country> is now a
mandatory field when the
visibility of the is-address-
same-as-person HRIS field is
set to No

This error message most

You cannot create Global Assignment • Create a Home
likely appears when:
Host employment Employment before
record for Person ID • You’re importing a Host importing Host
Employment record for Employment for an
External without a
an inactive employee
Home Employment inactive employee.
without associating a
Home Employment. • Specify the start date
• You’re importing the Host of the Host Employment
Employment record, on or after the Home
where the start date is Employment start date
earlier than the start and import the data
date of the Home
again.
Employment.
User has already Termination Details This error message most • You must terminate the
likely appears when: active employee before
been rehired. You
can delete the • You’re importing a rehire initiating the rehire
record for an active process.
existing rehire
employee. • You must delete the
record or terminate
• A rehire record already existing rehire record
the employee to exists for the user. before importing the new
proceed with this rehire record.
rehire record
Additional Points to Note
• While investigating the failed records in your import file, check if any records have the <End Date> field. If
the <End Date> in your import file does not correspond to the <End Date> value present in the system, the
import process will not be successful. While the system calculates the end dates based on the hierarchy of
event start dates, you can remove this field value, and try importing the file again.
• Ensure all the effective-dated records are in a single CSV file, when importing multiple batches in parallel.
• After a Basic Import, if you are unable to find users in your system, it is most likely that the list of users in the
“Everyone” group isn't refreshed. To fix this, re-import basic user information for a few users (not all). This will
refresh the list and you should be able to find the users now.
• After a Biographical Information import, if you face an error after clicking on Employee Information in an
employee profile to review the Biographical information, it is most likely that the import hasn't been completed.
Ensure that the import process is complete before reviewing the data in employee profiles.
• After importing dependents information, if you find that:
• A single dependent is shared by two employees, it might be due to an incorrect <Person-ID-External>
association. To resolve this, create one <Person-ID-External> for each dependent respectively.
Thereafter, associate this information with the corresponding employees using the Person Relationship
template.
• Dependents are converted to employees, remove the National ID of the dependent and re-import data with
a new <Person-ID-External>. This will avoid the validation check on the National ID.

5.4 Assignment ID Definition with Data Imports
Assignment ID can be used to define a relationship between the personnel (temporary or permanent) and your
company.
Objectively, assignment ID (<assignment_id_external>) is similar to the user ID assigned to all personnel

in your company. However, assignment ID is flexible and can be changed whenever required, unlike the user ID.
Modifications to the user ID of employees require assistance from your designated Implementation Partner or SAP
Product Support.
With Employee Central imports, there are 2 ways to define assignment ID for new employees who have multiple
employment records:
Prerequisite: The required HRIS elements must be configured to add the <assignment_id_external> field.
To check the existing configuration, go to Admin Center Manage Business Configuration Employee Central
HRIS Elements .
1. Manually define assignment ID in your import file template.

• For new employees, import data using the Basic Import template.
• For new employees with Concurrent Employment, import data using the Employment Details template.
• For new employees having a Global Assignment, import data using the Global Assignment template.
 Note
While importing data, if the system finds records where you haven’t entered an Assignment ID, a value is
automatically assigned from the corresponding <users_sys_id> field.
2. Configuring the system to auto-generate an assignment ID: Create an employee setting configuration to
generate assignment ID during the data import process.
Setting Up a Process for Auto-Generating Assignment ID [page 117]

Auto-generate assignment IDs while importing data by creating an employee setting configuration.
Related Information
Managing User Information: Assignment ID

Basic User Information Imports [page 60]
Employment Details Imports [page 63]
Global Assignment Imports [page 64]

5.4.1 Setting Up a Process for Auto-Generating Assignment ID
Auto-generate assignment IDs while importing data by creating an employee setting configuration.
Context
To automate the process of generating the Assignment IDs for new employees, you must create an employee
settings configuration and attach a business rule to auto-generate assignment IDs. The business rule is executed
during the data import process.
Procedure

2. Select Employment Settings Configuration from the Create New dropdown.
A form to create an employment setting configuration appears.
3. Specify a code for the employment settings configuration.
4. (Optional) Enter the name of the configuration in the Name field.
5. Set the Status as Active.
6. Select Yes from the Activate “Generate Assignment ID External” by Using a Business Rule dropdown.
7. Select  (Add Rule) to create a business rule.
The Configure Business Rules page appears in a popup window. For information about how to create a business
rule, refer to the Related Information section.
 Note
Ensure that you create a business rule instance belonging to the Generate Assignment ID External scenario
in Employee Central Core rule scenario category.
8. After creating the business rule, select the new rule from the Rule to generate Assignment ID External
dropdown.
9. Save the changes.
Results
Your employee settings configuration is activated. With this configuration in place, the system generates an
assignment ID while importing Employment Details or Global Assignment information of employees.
 Note
• The assignment ID generated by the system can be different from the user ID of employees.
• Assignment ID from the import file takes precedence over the assignment ID generated by the system.

Task overview: Assignment ID Definition with Data Imports [page 116]
Related Information
Creating a Business Rule
5.5 Data Validation and Error Management with Data Imports
Data validation and error management are part of Centralized services to help ensure data imports and the
resultant changes are accurate and consistent.
General Validations
Data imports for all entities supported by Centralized services are validated. The validations include:
• Association validation: To check the associations between the various Foundation Objects (FOs) and Generic
Objects (GOs), and verify if the data you’ve entered in the import file is correct.
 Note
Inactive FOs and GOs are not considered during imports. During an import, if an event reason status is
specified as Inactive in the import file, then the Event Reason is considered for the import. However, if the
Event Reason status is configured as Inactive in Manage Organization, Pay and Job Structures, then the
event reason is not considered for import.
• Derived entity validation: To check if there are any issues arising as a result of cross-entity transactions with
data imports. Cross-entity transactions can arise out of cases such as rule execution, forward propagation, and
so on.
 Example
While importing Job Information, if a cross-entity rule is executed to update Compensation Information,
the corresponding record is validated. Compensation Information is the derived entity in this case.
 Note
The Job History import fails in Initial Load Mode if there is a cross-entity rule from Job Information to
Recurring Pay Component if there is no corresponding Compensation Information record.
• Duplicate record validation: To check if there are multiple records in your import file with same data.
• Forward data propagation validation: To validate existing data in all the target records qualifying for forward
propagation.

• Related entity validation: To check the existing data of an entity that is related to the entity for which you are
importing data.
 Example
Personal Information and Global Information share a parent-child relationship. When you're importing
Personal Information on a future date, the Global Information associated with the existing Personal
Information is implicitly copied over. If the existing Global Information has inconsistencies, they must be
resolved before importing Personal Information.
Similarly, with Global Information imports, the associated Personal Information record is validated for
consistency.
 Example
When a new record for Compensation Information is imported, the recurring pay component is also copied
over from the previous record. During the copy, validation is completed for both Compensation Information
and the recurring pay component. To reduce data inconsistency.
• Sequence number validation: To check if a sequence number is entered for all the records having same
business keys. Applicable for data imports with entities that support addition or modification of multiple
records (having same business keys) on the basis of a sequence number, such as Job Information.
• Earliest date validation: To check if the effective date of changes is before the earliest date of the record and
that the logged in user has permission to make those changes. This validation is for all effective-dated entities
supported on Centralized services.
Error Management
Raise Message: While configuring business rules, you can add conditions to handle exceptional scenarios with a
warning or an error message using the Raise Message action. For more information about creating a rule that raises
a message, refer to the Related Information section.
Related Information
Creation of a Rule That Raises a Message
5.6 End Date Correction with Data Imports
End date correction is a part of Centralized services to manage end dates of effective-dated employee records.
When you’re importing data for effective-dated entities, end date correction is required to keep data consistent in
the following scenarios:
• Addition or deletion of a record for employees who have multiple records.

• Updating an existing record with a new start date.
For employees who have multiple records, end date correction is a method to determine whether there can be date
gaps between different records or not.
 Note
A 'date gap' is the time frame between the end date of one record and the start date of the next record.
Based on whether you import the data in Incremental Load or Full Purge mode, the end dates are adjusted
automatically.
End date correction is supported for the following entities:
HRIS Entities Supporting End Date Correction

HRIS Entity Supports User-Defined End Dates? Additional Information
Job History No • If an entity supports user-defined

Compensation Information No end dates, end dates specified in
your import file template are consid-
Recurring Pay Component No
ered, and not calculated automati-
Personal Information No cally.
Global Information No • If an entity doesn't support user-de-

fined end dates, end dates specified
Addresses Yes
in your import file template are ig-
 Note nored, and calculated automatically.
Only for data imports in Full Purge

mode.
Job Relationships Yes
 Note
Only for data imports in Full Purge
mode.
Use Cases for End Date Correction and Calculation
Adding new records without providing end date values in the import file
Prerequisites: You’re importing data in Incremental Load mode.
 Example
Sample Import Data

Person ID External Address Type Start Date (dd/mm/yyyy) Country/Region
104003 Home 04/01/2020 USA

104003 Home 04/05/2020 USA
104003 Home 04/10/2020 USA

Start Date (dd/mm/ End Date (dd/mm/
Person ID External Address Type yyyy) yyyy) Country/Region
104003 Home 4/1/2020 03/05/2020 USA
104003 Home 4/5/2020 03/10/2020 USA
104003 Home 4/10/2020 31/12/9999 USA
Result: End dates are automatically calculated. Date gaps, if any, between records are adjusted accordingly.
The end date of the last record is also adjusted.
Adding new records with end date values provided in the import file
Prerequisites: You’re importing data in Full Purge mode.
 Example
Let' suppose you’re importing address information of an employee, with end dates provided for all records.
Sample Import Data

104003 Home 04/01/2020 04/02/2020 USA
104003 Home 04/05/2020 04/06/2020 USA
104003 Home 04/10/2020 04/11/2020 USA
Result: Existing address information of employees is deleted and replaced with data from your import file. If
there are any date gaps between records, they are not corrected.

104003 Home 04/01/2020 04/02/2020 USA
104003 Home 04/05/2020 04/06/2020 USA
104003 Home 04/10/2020 04/11/2020 USA

Adding new records with start dates coming after the start date of the most recent existing
record
 Example
Let's suppose a user has one Job Information record as follows:
The start date here means before the start date of an existing record.
Sample User Data

yyyy) yyyy) Country/Region Supervisor Job Title
01/01/2021 31/12/9999 USA John Doe Analyst
You add two new records without providing an end date in the import file:
Sample Import Data

01/01/2022 IND Jane Doe Senior Analyst
01/01/2023 AUS John Smith Manager

01/01/2022 31/12/2022 IND Jane Doe Senior Analyst
01/01/2023 31/12/9999 AUS John Smith Manager
Result: The end date of the existing record is corrected in accordance to the new records added. The end dates of
the new records are also calculated.
Adding new records with start dates coming before the start date of the initial record
 Example
Let's suppose a user has one Job Information record as follows:
Sample User Data

You add a new record without providing an end date in the import file:

Sample Import Data
01/01/2020 IND Jane Doe Analyst Intern

01/01/2020 31/12/2020 IND Jane Doe Analyst Intern
Result: The end date of the new record is corrected in accordance to the existing record.
Adding a new record with start date between the start dates of existing records
 Example
Lets suppose the following data exists for a user:
Sample User Data

104003 Home 04/01/2020 3/5/2020 USA
104003 Home 04/05/2020 3/10/2020 USA
104003 Home 04/10/2020 31/12/9999 USA
Now, you add a new record between the start date of the first record and the end date of the last record.
Sample Import Data

104003 Home 04/02/2020 USA

104003 Home 04/01/2020 03/02/2020 USA
104003 Home 04/02/2020 03/05/2020 USA
104003 Home 04/05/2020 03/10/2020 USA

104003 Home 04/10/2020 31/12/9999 USA
Result: The end date of the first record is corrected according to the start date of the new record. Also, the end
date of the new record (second record) is corrected according to the start date of the third record. The reason
being, the end of any record can’t be greater than the start date of the subsequent record. This process of end date
calculation holds true even if you don’t provide an end date value in your import file template.
The principles of end date correction as demonstrated in the these use cases are also applicable to other effective-
dated entities.
5.7 Employee Data Deletion with Imports
Remove employee data associated with different entities.
Deleting employee data is a consequential process, and must be dealt with utmost importance. Data once deleted
can be difficult or impossible to recover.
Using data imports, you can choose to delete employee data associated with a single entity, or multiple entities as
applicable.
We can also create a DRTM purge request to purge a specific type of data and not the entire set of user accounts
with all their records. However, if you want to do a full purge of inactive users, use the DRTM Master Data purge
instead. For more information, refer Related Information

Import employee data to be removed with a single entity.
Deleting Employee Data with Multiple Entities [page 127]

Consolidate and import employee data with multiple entities for deletion.
Use Cases: Employee Data Deletion [page 128]

Notable scenarios related to employee data deletion with imports.
Related Information
Purging Specific Types of Data with DRTM

DRTM Master Data Purge

5.7.1 Deleting Employee Data with a Single Entity
Import employee data to be removed with a single entity.
Prerequisites
• To delete country/region-specific information, the corresponding HRIS elements must be properly configured.
To review your existing configuration, go to the Admin Center Manage Business Configuration page.
• To delete Job History, ensure that the Company field is available in your import file template.
• To delete a leave of absence Job History record, you have Enable Leave of Absence Editing enabled in the Time
Management Configuration MDF object.
Context
Employee data can be deleted in Incremental Load mode, by choosing an operation type between DELETE and
DELIMIT. The operation type depends on the entity you select for importing data.
You cannot delete and add data at the same time. To do so, you must create two separate jobs.
 Note
This criteria doesn't apply to entities supported by Centralized services.
Business key changes are considered as a 'Delete' of existing business keys and 'Insert' of new business keys.
This applies whether the business key is changed or if the same business key is deleted and re-added.
Key considerations with Job Information, Recurring Pay Component and Compensation
Information deletion:
• You must provide the sequence number with the records in your import file template.
• You can delete data associated with multiple employee records.
• For a given employee, if your import file contains data to be deleted and added at the same time, Recurring Pay
Component associated with the Compensation Information (to be deleted) is automatically linked with the new
Compensation Information (to be added).
• Deleting Compensation Information results in the deletion of the corresponding Recurring Pay Component
information also.
Procedure
1. Download the import file template of the required entity.

2. Prepare the template with data to delete.

While preparing import data, enter DELIMIT or DELETE (depending on the selected entity) in the Operation
column.
For deleting.. Enter...in the Operation Column
Addresses DELIMIT
Compensation Information DELETE
Email Information DELETE
Emergency Contact Information DELETE
Global Information DELIMIT
Job History DELETE
Job Relationships DELIMIT
National ID Information DELETE
Non Recurring Pay Component Information DELETE
Person Relationship DELIMIT
Personal Information DELETE
Phone Information DELETE
Recurring Pay Component Information DELIMIT
Social Accounts Information DELETE
3. Upload the file to import the data.
Results
If successful, the employee data corresponding to the selected entity is deleted.
Related Information
Configuring Country-Specific Fields through Business Configuration UI

Uploading Import Files [page 99]
Deleting Employee Data with Multiple Entities [page 127]

5.7.2 Deleting Employee Data with Multiple Entities
Consolidate and import employee data with multiple entities for deletion.
Prerequisites
The Admin Center Manage Employee Central Settings Enable Compound Deletion setting is enabled. This
setting is required to download the required import file template.
Multiple entry deletion is supported for these entities:
• Addresses
 Note
You can only delete the Biographical Information of employees if there is no existing Employment
Information and/or Dependent information for them.
• Pay Component Non-Recurring
Context
You can use a dedicated import template to group together employee data belonging to different entities for
deletion.
 Note
Data deletion with multiple entities always happens in Full Purge mode.
Procedure
1. Download the Compound Delete import file template.

2. Prepare data to import.
The import file template contains two columns.
• In the externalCode column, enter the employee identifier such as the User ID or the Person ID External.
• In the hris-element-id column, enter the identifier of the HRIS element whose associated data you want to
delete.

 Note
To find the HRIS element identifier, go to Admin Center Manage Business Configuration page.
Results
If successful, the corresponding employee data is deleted.
Related Information

5.7.3 Use Cases: Employee Data Deletion
Notable scenarios related to employee data deletion with imports.
Forward propagation is supported for data deletion of all effective-dated entities. If forward propagation is
applicable, data changes are cascaded to subsequent records of the employee.
Data Deletion for Addresses
 Note
When you delete data with imports, make sure that the start date falls within the date range of records existing
in the system.
Examples
 Example
The following example shows how data changes are forward propagated when you delete data.
Existing Records of Addresses for an Employee

Person ID External Address Type Country/Region Start Date End Date
104003 Home USA January 1, 2012 December 31, 2012

104003 Billing USA January 1, 2013 December 31, 2014
104003 Billing USA January 1, 2015 December 31, 9999
You delete a record by importing the following data:
Person ID External Address Type Start Date Country/Region Operation
104003 Billing January 1, 2013 USA DELIMIT
Result: The Billing records with the start date on January 1, 2013 and January 1, 2015 are deleted.

 Example
The following example shows how data changes are forward propagated until there's a data gap when you
delete address information.
Existing Address information of an employee:
Sample Address Information

Person ID Ex- Country/
ternal Address Type Start Date End Date Address 1 Region Attachment ID
104003 Home January 4, April 4, 2020 - USA -
2020
104003 Home May 5, 2020 September 4, 278 Shadow USA 924

2020 Brook Street
Ada, OK 74820
104003 Mailing May 5, 2020 September 4, 278 Shadow USA 924

2020 Brook Street
Ada, OK 74820

104003 Home October 4, December 31, 278 Shadow USA 924

2020 9999 Brook Street
Ada, OK 74820
104003 Mailing October 4, December 31, 278 Shadow USA 924

Ada, OK 74820
104003 Home May 5, 2020 USA DELIMIT
After the import, the home address record effective from May 5, 2020 is deleted. The home address record
effective from Oct 4, 2020 is not deleted because of a data gap before it. The forward propagation stops when
there's a gap.
Sample Database Output - with Forward Propagation

104003 Home January 4, April 4, 2020 - USA -
2020
104003 Mailing May 5, 2020 September 4, 278 Shadow USA 924

2020 Brook Street
Ada, OK 74820
104003 Home October 4, December 31, 278 Shadow USA 924

Ada, OK 74820
104003 Mailing October 4, December 31, 278 Shadow USA 924

Ada, OK 74820
 Example
The following example shows how the data change is forward propagated until the data in a future record is
different from the original value of the previous record.

104003 Home January 1, 2020 April 30, 2020 278 Shadow USA 924
Brook Street
Ada, OK 74820
104003 Home May 1, 2020 September 30, 278 Shadow USA 924
2020 Brook Street
Ada, OK 74820
104003 Home October 1, 2020 December 31, 111 Brook Street USA 333
2020
104003 Home January 1, 2021 December 31, 111 Brook Street USA 333
9999
104003 Home January 1, 2020 USA DELIMIT
After the import, the home address record effective from January 1, 2020 is deleted. The home address record
effective from October 1, 2020 is not deleted because the address record is different from the original data of
the previous record.

104003 Home October 1, 2020 December 31, 111 Brook Street USA 333
2020
104003 Home January 1, 2021 December 31, 111 Brook Street USA 333
9999
Related Information

5.8 Identical Record Suppression with Data Imports
A method to exclude duplicate records and redundant information while importing data.
Multiple records with same data for a person indicate inaccurate or stale data. It can cause issues with reporting,
analyzing metrics leading to performance inefficiency. Identical record suppression enables you to keep data
consistent and avoid duplicate records from getting imported.
Identical record suppression is enabled by default with employee data imports.
Entities that support identical record suppression with data imports are:
• Addresses
• Emergency Contacts
• Global Information
• Social Account Information
• Job History
• Compensation Information
• Personal Documents Information
• Entities supported only with Centralized Services
• Recurring Pay Component
• Person Relationship Information
 Example
For effective-dated entities, if you're importing data that matches existing data for an employee on a given date,
the record isn’t imported. However, if you're importing data that matches existing data but on a different date,
the record is imported.
For non-effective dated entities, if you're importing data that matches existing data for an employee, the record
isn’t imported.
If you import Job History and Compensation Information with or without providing a seq-number in the import file,
the import data is validated against the existing employee data on the same effective date. If there’s no information
available as of that effective date, the system validates the data you’re importing with the previous effective dated
record. If there are still no changes, the data isn't updated.

 Note
Identification of records to suppress isn’t a part of the validation process. However when you do an import, the
business rules are executed to see if there are any changes to the import data. If there are changes then the
record is saved. If the records are still identical even after rule execution then the record is suppressed.
Related Information

Use Cases: Identical Record Suppression [page 133]
5.8.1 Use Cases: Identical Record Suppression
Notable scenarios related to identical record suppression with employee data imports.
Identical Record Suppression with Job Information Imports
Importing Job Information with Identical record suppression not enabled

Let's suppose an employee has existing Job Information as follows:
Sample Employee Data

Start Date (dd/mm/yyyy) Country/Region Supervisor Job Title
01/01/2021 USA John Doe Analyst
01/03/2021 USA John Doe Senior Analyst
Case 1: You add a new record by importing data in Full Purge mode.
Sample Import Data

Result: All existing records are deleted and replaced with the new record. The audit details are updated.

Start Date (dd/mm/
yyyy) Country/Region Supervisor Job Title Last Modified Date
01/02/2021 USA John Doe Senior Analyst <Date of Import>
Case 2: You add a new record identical to one of the existing records by importing data in Full Purge mode.

Sample Import Data
Result: The first record is not imported as the data is identical to an existing record, however, the audit details are
updated. The second record is deleted.

Start Date (dd/mm/
01/01/2021 USA John Doe Analyst <Date of Import>
Case 3: You add a new record by importing the data in Incremental Load mode.
Sample Import Data

01/04/2021 USA John Doe Manager
Result: The new record is added to the existing set of employee records. The audit details are updated.

Start Date (dd/mm/
01/04/2021 USA John Doe Manager <Date of Import>
Case 4: You add a new record identical to an existing record by importing the data in Incremental Load mode.
Sample Import Data

Result: The record is not imported. However, the audit logs are updated.

Start Date (dd/mm/
Importing Job Information with Identical record suppression enabled

Let's suppose an employee has existing Job Information as follows:

Sample Employee Data
Case 1: You add a new record by importing data in Full Purge mode.
Sample Import Data

Result: The first record is imported as there is a change to Job Title. However, second record is deleted and the
audit details are updated..

Start Date (dd/mm/
Case 2: You add a new record identical to an existing record by importing data in Full Purge mode.
Sample Import Data

Result: The first record is not imported as the data is identical to an existing record (suppressed) and the audit
details are not updated. However, the second record is deleted.
Sample Output Data

Case 3: You add a new record identical to an existing record by importing the data in Incremental Load mode.
Sample Import Data

Result: The record is not imported ('suppressed'). The audit details are not updated.


Identical Record Suppression with Compensation Information, Recurring Pay
Component Imports
The following use cases are from the perspective of Compensation Information imports, but the behavior is the
same with Recurring Pay Component imports.
 Note
For Compensation Information imports, if identical records are included with the import, the system executes
rules for Compensation Information to check if there are any changes to both Compensation Information and
Recurring Pay Component data. If there are changes to the data, the updated data is saved in the system.
However, for Recurring Pay Component imports, the system checks for changes only specific to Recurring Pay
Component data to Recurring Pay Component data included in the import file.
Importing Compensation Information with Centralized services enabled and Identical record
suppression not enabled
Let's suppose an employee has existing Compensation Information as follows:
Sample User Data

Start Date (dd/mm/
yyyy) Event Reason Sequence Number User ID Benefits Rate
10/10/2020 DATACHG 1 sdesikan1 5
You add the following records by importing data in Incremental Load mode.
Sample Import Data

Start Date (dd/mm/
Result:
• The first record is not imported ('suppressed') as the data is identical to an existing record. The audit details
are updated.
• The second record is imported successfully. But its sequence number is corrected to match the order.

Start Date
(dd/mm/yyyy) Event Reason Sequence Number User ID Benefits Rate Last Modified Date
10/10/2020 DATACHG 1 sdesikan1 5 <Date of

Import>

Import>

Import>

Importing Compensation Information with Centralized services and Identical record
suppression enabled
Let's suppose an employee has existing Compensation Information as follows:
Sample User Data

Start Date (dd/mm/
You add a new record by importing data in Incremental Load mode.
Sample Import Data

Start Date (dd/mm/
Result: The record is not imported ('suppressed') as the data is identical to an existing record, and a warning
message is displayed on the UI. The audit details are not updated.

Start Date (dd/mm/
5.9 Forward Propagation of Data with Imports
Forward propagation is a process by which data changes are cascaded or "propagated" to future dated records.
Forward propagation is supported only in Incremental Load mode.
Forward propagation of data is useful when modifications to employee data are applicable to corresponding
effective dated records in the future.
For records where forward propagation of data occurs, the system runs the validation checks against all the fields.
Currently, forward propagation of data is supported with the following data imports on Centralized services:
• Addresses
• Global Information
• Job History
• Recurring Pay Component
• Termination Details (Job Information)

• Person Relationship Information
The following sections describe the behavior of these supported entities on Centralized services.
 Note
• Rules aren't triggered on forward propagated data.

• Forward propagation is supported only on incremental mode.
• Forward propagation is supported only for insert, meaning when inserting and modifying a value or adding
a new record for an entity.
• Forward propagation of data happens with Compensation Information (including Recurring Pay
Component) imports only if you've the Enable Forward Propagation during Incremental Import permission.
Forward Propagation of Data with Job History, Compensation Information, and

Personal Information Imports
Forward propagation of data when field values in the records subsequent to the newly added record match with the
values in the first record.
Example
These examples of forward propagation apply to Job History and Personal Information imports as well.
 Example
Existing Compensation Information records of an employee:
Sample Compensation Information
Start Date Custom String 1 Custom String 2 Custom String 3 Custom String 4
April 1, 2019 X A O -
June 1, 2019 X B O -
September 1, 2019 Y C O -
You add a new record by importing the following data:
Sample Import Data
May 1, 2019 Z B Q E
Compensation Information of the employee after importing data:

April 1, 2019 X A O -
May 1, 2019 Z B Q E
June 1, 2019 Z B Q E
September 1, 2019 Y C Q E
For the record with <Start Date> as June 1, 2019, the values in the Custom String 1, Custom String 3 and
Custom String 4 match with the values in the record with <Start Date> as April 1, 2019, but the value in
Custom String 2 doesn't match. Hence, data is propagated only to Custom String 1, Custom String 3, and
Custom String 4. Also for the record with <Start Date> as September 1, 2019, forward propagation happens
on Custom String 3 and Custom String 4 as the value was same as previous record. However, for Custom
String 1 the propagation stops as the value is different from previous record.
Forward Propagation of Data with Recurring Pay Component and Global

Information Imports
 Restriction
Forward propagation of calculated fields such as <Annualized Salary>, <Calculated Amount> is

currently not supported.
Example
These examples of forward data propagation apply to both Recurring Pay Component and Global Information
imports.
 Note
When you add records of child entity to a record without existing child entity records, forward propagation of
data happens if the field value in the futures is empty.
 Example
Existing Compensation Information records of an employee:

User ID Start Date Event Reason
Mhoff January 1, 2000 DATACOST

User ID Start Date Event Reason
Existing Recurring Pay Component records of the same employee:

User ID Start Date Pay Component Currency
Mhoff January 1, 2000 Base Salary USD
Sample Import Data

Mhoff January 1, 2001 Travel Allowance INR
Mhoff January 1, 2001 Base Salary INR
Recurring Pay Component information of the employee after importing data:

Base Salary INR
Base Salary USD
Base Salary USD
In continuation with the above sample database output, if you delete an existing record by importing the
following data:

Sample Import Data
User ID Start Date Pay Component Currency Operation
Mhoff January 1, 2001 Travel Allowance INR DELIMIT
Recurring Pay Component information of the employee after importing data:

Mhoff January 1, 2001 Base Salary INR
In this case, only the pay component data is deleted while all the other data remains intact.
 Example
Existing Records of Personal Information for an Employee

Person ID External First Name Last Name Start Date End Date
104003 Julie Armstrong January 1, 2015 December 31, 2015
Existing Records of Global Information for an Employee

Person ID External Country/Region Number of Children Start Date End Date
104003 Australia 0 January 1, 2015 December 31, 2015
You add new record by importing the following data:
Sample Import Data

Person ID External Country/Region Number of Children Start Date
104003 Australia 1 January 1, 2016
Result:
No forward propagation happens, because the number of children starting from January 1, 2017 is "0" and is
different from the original value of the previous record, which is empty.

Records of Global Information for an Employee After Import
 Example

Existing Records of Global Information for an Employee

104003 Australia January 1, 2017 December 31, 2018
Sample Import Data

Result:
The updated field value "1" is forward propagated and stops on December 31, 2018, because there's no record
of global information from January 1, 2016 to December 31, 2016 and the value of <Number of Children> in
the future record is empty.


 Example

There's no records of global information for this employee.
Sample Import Data

Result:
The global information record is forward propagated.

Forward Propagation of Data with Address and Job Relationship Imports
Forward propagation works when you add or modify (update or delete) data. The following examples apply to Job
Relationship imports as well.
For use cases about forward propagation in data deletion, see related information.
Forward Propagation with Data Addition
The following examples show how data change is propagated when you add address information.
 Example

Person ID External Address Type Postal Code Start Date End Date
104003 Billing 10000 January 1, 1999 December 31, 2019
104003 Billing January 1, 2021 December 31, 9999

Person ID External Address Type Postal Code Start Date
104003 Billing 20000 May 1, 2020

104003 Billing 10000 January 1, 2020 April 30, 2020
104003 Billing 20000 May 1, 2020 December 31, 2020
104003 Billing January 1, 2021 December 31, 9999
 Example

104003 Billing 30000 May 1, 2020

The updated field value "30000" is forward propagated to the future record that starts from January 1, 2021
because before import, the future record has the same postal code as that of the previous record.

 Example

104003 Billing 30000 May 1, 2020
Sample Database Output with Forward Propagation

The updated field value "30000" is forward propagated and stops on December 31, 2020 because there's no
record from January 1, 2021 to April 30, 2021.
Forward Propagation with Same and Different Entity Type
Currently, if you insert a same entity type within an existing record, the data isn't propagated forward. Insertion of
only a different entity type within an existing record is propagated forward.
 Example
Forward propagation happens and gaps are filled.
Existing Address Information of an Employee

Person ID Exter-
nal Address Type Start Date End Date Address 1 Country/Region
104003 Home January 4, 2020 April 4, 2020 Home address 1 USA
104003 Mailing May 5, 2020 September 4, Mailing address 1 USA

2020
104003 Mailing October 4, 2020 December 31, Mailing address 2 USA

9999

Person ID External Address Type Start Date Address 1 Country/Region Attachment ID
104003 Home May 5, 2020 Home address 2 USA 924
Sample Database Output with Forward Propagation

104003 Home January 4, April 4, 2020 Home address 1 USA

2020
104003 Home May 5, 2020 September 4, Home address USA 924

2020 2
104003 Mailing May 5, 2020 September 4, Mailing address USA

1
2020
104003 Home September 5, October 3, Home address USA 924

2020 2020 2
104003 Home October 4, December 31, Home address USA 924

2020 9999 2
104003 Mailing October 4, December 31, Mailing address USA

2
2020 9999
The newly added home address information is propagated to future dated records with other details in the
import file template like Address 1 and Attachment ID.
 Example

Person ID Exter-
123412 Home January 1, 2020 December 31, Homeaddress1 USA

2029

2030
123412 Mailing January 1, 2031 December 31, Mailingaddress USA

9999
Now, import data with Address Type as Home.
Person ID External Address Type Start Date End Date Address 1 Country/Region
123412 Home January 1, 2025 updateHomeAddr USA

ess
Address information of the employee after importing data:

Person ID Exter-

2024
123412 Home January 1, 2025 December 31, updateHomeAd- USA

2029 dress

2030

9999
Here, when a same entity type (in this example, entity Address Type is Home), within an existing record is
imported, forward propagation of data doesn't take place.
 Example
For the same Sample Address Information mentioned in the previous example, import data with Address Type
as Others.
Person ID External Address Type Start Date End Date Address 1 Country/Region
123412 Others January 1, 2025 OtherAddress USA
Address information of the employee after importing data:

Person ID Exter-

2024

2029
123412 Others January 1, 2025 December 31, OtherAddress USA

2029

2030

2030

9999

Person ID Exter-

9999
Here, when a different entity type (in this example, entity Address Type is Others), within an existing record is
imported, forward propagation of data takes place.
 Example
Forward propagation is supported only when a new type of import is inserted between the records. See the
following example for Job Relationship imports.
Record Start Date Job Position
1 1.1.2000 HR Manager
2 1.5.2000 Custom Manager
Now, insert a record with 1.3.2000 and Custom Manager between record 1 and 2. The result is that forward
propagation doesn't take place because Custom Manager exists in the future records already.
Now, in the following example, insert a record with 1.3.2000 and Matrix Manager between record 1 and 2.
Forward propagation takes place as the inserted record is of a new type.
2 1.3.2000 Matrix Manager

Related Information

Use Cases: Employee Data Deletion [page 128]
5.10 Sequence Number Generation and Correction with Data

Imports
Sequence number generation and correction is a part of Centralized services to differentiate between employee
records having identical information.
What's a Sequence number?

Sequence number is an attribute of the employee data stored in Employee Central that's purely meant for
reference purposes, and not visible on the UI. It's a numeric field available in HRIS entities which permit multiple
changes to data on a daily basis for entities such as Job Information, Compensation Information, Recurring Pay
Component information, and so on.
Why is Sequence number required?

A sequence number is required to keep employee records in a prescribed order to ensure data consistency. When
you import multiple records on the same Start Date, or add new records with start dates matching with existing
records, a sequence number helps distinguish one record from another. Here are a few examples illustrating the
significance of the sequence number.
Example 1
 Example
Let's suppose you’re importing four new records for a user without providing a sequence number in your import
file.
Sample Import Data

Event Date (dd/mm/
yyyy) User ID Country/Region Job Title Sequence Number
01/01/2021 jdoe USA Analyst Intern

Event Date (dd/mm/
yyyy) User ID Country/Region Job Title Sequence Number
01/01/2021 jdoe USA Junior Analyst
01/01/2021 jdoe USA Senior Analyst
01/01/2021 jdoe USA Manager
These records are not imported because the system is unable to determine the first record of the sequence.
Example 2
 Example
Lets suppose there are three records existing for a user as follows:
Sample Employee Records

Event Date Sequence Num-
(dd/mm/yyyy) User ID Country/Region Supervisor Job Title ber
01/01/2021 jdoe USA Carla Grant Analyst Intern 1
01/01/2021 jdoe USA Carla Grant Junior Analyst 2
01/01/2021 jdoe USA Carla Grant Senior Analyst 3
You add a new record by importing data in Incremental Load mode, without providing a sequence number in
your import file.
Sample Import Data

01/01/2021 jdoe USA Carla Grant Manager
After the data is imported, the new record is assigned a sequence number to match the order of the existing
records.

01/01/2021 jdoe USA Carla Grant Manager 4
Let's suppose you import another record on the same date in Incremental Load mode. This time you provide a
sequence number in your import file.

Sample Import Data
01/01/2021 jdoe USA Carla Grant Business Analyst 2
Since the business keys (Event Date, User ID, and Sequence Number) match with an existing record, the
corresponding record is updated.
Database Output
01/01/2021 jdoe USA Carla Grant Business Analyst 2
 Remember
Sequence number is a part of the key that identifies an employee record. Therefore, to update an existing
record and not add a new one, you must ensure to provide the sequence number of the respective record.
Notable Use Cases
Sequence number correction with data deletion
 Example
Lets suppose an employee has existing Job Information as follows:
Sample Employee Records

Event Date (dd/mm/
yyyy) User ID Supervisor Sequence Number Notes
01/01/2021 jdoe Carla Grant 1 Note 1
You delete the record with sequence number 2.
Sample Import Data

(dd/mm/yyyy) User ID Supervisor ber Notes Operation
01/01/2021 jdoe Carla Grant 2 Note 2 Delete
Result: The sequence number of the subsequent records are automatically corrected to keep the order.

Database Output
Event Date (dd/mm/
yyyy) User ID Supervisor Sequence Number Notes
Sequence number generation and correction for records created by business rules
 Example
Lets suppose an employee has the following Job Information, Compensation Information, and Recurring Pay
Component Information:
Sample Job Information

01/01/2021 jdoe USA Carla Grant Analyst 1

Event Date User ID Pay Group Benefits Rate Sequence Number
01/01/2021 jdoe USA Semi-Monthly 0 1

(US)
Sample Recurring Pay Component Information

Event Date (dd/mm/
yyyy) User ID Pay Component Currency Sequence Number
01/01/2021 jdoe Base Salary USD 1
You add a new record by importing data in Incremental Load mode. You also have a business rule associated
with the Job Information entity to create new Compensation and Recurring Pay Component records.
Sample Import Data

01/01/2021 jdoe IND Carla Grant Senior Analyst 2
Result: When the new records created by the rule are associated with the Compensation Information and the
Recurring Pay Component Information of the user, a sequence number is automatically adjusted.
Sample Database Output for Job Information

01/01/2021 jdoe USA Carla Grant Analyst 1
01/01/2021 jdoe IND Carla Grant Senior Analyst 2

Sample Database Output for Compensation Information
Event Date (dd/mm/
yyyy) User ID Pay Group Benefits Rate Sequence Number
01/01/2021 jdoe USA Semi-Monthly 0 1

(US)
01/01/2021 jdoe IND Monthly (IN) 2 2
Sample Database Output for Recurring Payment Information

Event Date (dd/mm/
01/01/2021 jdoe Base Salary INR 2
Sequence number correction with identical record suppression
 Example

You add three new records by importing Job Information in Incremental Load mode, without providing a
sequence number:
Sample Import Data

Event Date (dd/mm/
yyyy) User ID Country/Region Supervisor Job Title
01/01/2021 jdoe USA Carla Grant Manager
01/01/2021 jdoe USA Carla Grant Business Analyst
01/01/2021 jdoe USA Carla Grant System Analyst
Result: These records are not imported because the system is unable to determine the first record of the
sequence.
Importing data without providing a sequence number
•  Example

Case 1: You add a new record by importing data in Full Purge mode, without providing a sequence number.
Sample Import Data

01/02/2021 jdoe USA Marcus Hoff Analyst
Result: During the import process, a sequence number "1" is generated and assigned to the new record.
Data in the new record is matched against existing data. Since the business keys (Event Date, User ID,
Sequence Number) don't match with the existing record, the existing record is updated. The audit logs are
updated as well.

01/02/2021 jdoe USA Marcus Hoff Analyst 1
Case 2: You add a new record identical to the existing record by importing data in Full Purge mode, without
providing a sequence number.
Sample Import Data

01/02/2021 jdoe USA Marcus Hoff Analyst
Sequence Number) match with the existing record, the data is not imported ('suppressed'). The audit logs
are not updated.

01/01/2021 jdoe USA Marcus Hoff Analyst 1
•  Example

Case 1: You add a new record by importing data in Full Purge mode, without providing a sequence number.
Sample Import Data


Case 2: You add a new record by importing data in Incremental Load mode, without providing a sequence
number.
Sample Import Data

01/01/2021 jdoe USA Carla Grant Junior Analyst
Sequence Number) match with an existing record, the existing record is updated.

Case 3: You add multiple records by importing data in Full Purge mode, without providing a sequence
number.

Sample Import Data
Result: The records are not imported as the system is unable to determine the first record of the sequence.
•  Example
Lets suppose an employee has existing Compensation Information as follows:

Event Date (dd/mm/
yyyy) User ID Payroll ID Payroll System ID Sequence Number
01/01/2021 jdoe 1 4 1
01/01/2021 jdoe 2 4 2
You add recurring pay component information by importing data in Incremental Load mode, without
providing a sequence number.
Sample Import Data

Event Date (dd/mm/
01/01/2021 jdoe Base Salary USD
01/01/2021 jdoe Meal Allowance USD
Result: The Compensation Information record with sequence number 1 doesn't have any recurring pay
component records linked to it, whereas, the Compensation Information record with sequence number 2
has two recurring pay component records linked.
Sample Database Output - Compensation Information

Event Date (dd/mm/
01/01/2021 jdoe 1 4 1
Linked Recurrring Pay Component records: None
Sample Database Output - Compensation Information

Event Date (dd/mm/
01/01/2021 jdoe 2 4 2
Linked Recurrring Pay Component records:

Sample Database Output - Recurring Pay Component Information
Event Date (dd/mm/
01/01/2021 jdoe Meal Allowance USD 2
5.11 Rehire Employees with Data Imports
Persons who have previously worked at your company can be rehired if the required qualifications are met.
If a terminated employee is eligible to be rehired in your company, you can initiate the rehire process in Employee
Central. However, if a significant number of persons are to be rehired, you can use Employee Central Imports to
save time and manual effort.
There are two ways of rehiring former employees using employee data imports:
1. Rehire with the existing user ID of their previous employment. In this case, the previous employment data is
visible in the system.
2. Rehire with a new user ID. In this case, the previous employment data isn’t visible in the system. For more
information about rehiring users with a new user ID, refer to the Related Information section.
Rehiring Former Employees with an Existing User ID [page 157]

Retain and refer the old employment data by rehiring former employees using their existing user ID.
Create a fresh employment record by rehiring former employees with new user ID.
5.11.1 Rehiring Former Employees with an Existing User ID
Retain and refer the old employment data by rehiring former employees using their existing user ID.
Prerequisites
You must have the Rehire Inactive Employee permission.
Context
When you rehire former employees using their existing user ID, their old employment data is visible in the system,
and referred directly wherever possible. It is also possible to rehire former no-shows.

Procedure
1. To rehire users with the same user ID, download a copy of the Job History import file template.
Along with other information, enter the user ID of their previous employment under <User ID> column and
the event reason for rehiring users (as configured for your company) under <Event Reason> column. For
information about other notable points with Job History imports, refer to the Related Information section.
Results
If successful, users are rehired on a new employment with their existing user ID.
During the import, most of the termination-specific fields are removed. Fields such as Benefits End Date as well as
custom strings are deleted. Only the Ok to Rehire, Eligible for Salary Continuation, and Regret Termination fields are
kept.
If the user had a global assignment, then all specific fields for global assignment details such as Payroll End Date
and custom fields are also removed.
Related Information

Job History Imports [page 66]
Termination Information
5.11.2 Rehiring Former Employees with an Existing User ID (New

Employment)
Create a fresh employment record by rehiring former employees with new user ID.
Prerequisites
• The People Profile is active and set up.

 Remember
Support.
• You must have the Manage Hires Rehire Inactive Employee with New Employment permission.
Context
When you rehire former employees by assigning a new user ID with their new employment, their old employment
data isn’t visible in the system. It is also possible to rehire former no-shows.
 Note
If a user being rehired already has an active employment, a concurrent employment is created. This means
that concurrent employment must be enabled in your system, since the rehire process would fail if concurrent
employment isn’t enabled.
Procedure
1. Download a copy of the Employment Details import file template.

Along with other information, enter the person ID of the user in the <Person ID External> column, and the
new user ID in the <User ID> column. The <Is Rehire> field must have a value relative to Yes.
 Note
<Is Rehire> is a boolean field. It accepts a set of values for Yes.
The <isRehire> field is a transient field used during import when a user is created for the Rehire with New
Employment scenario. This value is not saved to the database, it is only needed for the import.
To set the value as Yes, you can enter: Y, Yes, T, True, 1. By default, the system considers the field value as
1.
For information about other notable points with Employment Details imports, refer to the Related Information
section.
If successful, new user accounts are created.

4. To activate the newly created user accounts, download a copy of the Job History import file template.
Along with other information, enter the new employment's user ID under <User ID> column and the event
reason for rehiring users (as configured for your company) under <Event Reason> column. For information
about other notable points with Job History imports, refer to the Related Information section.

If successful, the HRIS sync job is scheduled. After the job is completed, the new user accounts are activated.
Related Information

Employment Details Imports [page 63]
Job History Imports [page 66]
5.12 Attaching Documents with Data Imports
Update employee records with supporting information by attaching a digital copy of documents with import file
templates.
Prerequisites
• The <attachment-id> field must be enabled and configured as visible in the HRIS elements of Emergency
Contact and Person Relationship entities.
 Note
The <attachment-id> field appears by default in the import templates of all other supported entities.
• To download country/region-specific import file templates, the corresponding HRIS element must be
configured.
To check the existing configuration, go to Admin Center Manage Business Configuration page.
Context
You can attach various types of documents such as Address Proof, Job Info Letter, and so on, with employee
records as a source of verification to claims made by employees. Document attachment is supported with the
following data imports:
• Personal Documents Information (Work Permit)

• Job History

• Consolidated Dependents
• Person Relationship
• Emergency Contact
• Addresses
Documents in the following formats are supported: *.doc, *.docx, *.pdf, *.txt, *.htm, *.ppt, *.pptx, *.xls, *.xlsx, *.gif,
*.png, *.jpg, *.jpeg, *.html, *.rtf, *.bmp, and *.msg.
Procedure

2. Download the import file template of the required entity.
3. While preparing the import data, enter the name of the document (along with extension) in the <attachment-
id> column.
Example: mhoff_visa.pdf
4. Create a new file in a text editor program and save the file as import.properties.
5. Edit the import.properties file, and add the parameter <importFileName> to hold the name of your import
file template.
Example: Let's suppose that you’ve downloaded the template to import Job History. Then the value for
<importFileName> must be the same as the actual file name of the CSV import file.
6. Compress the import file, the required documents, and the import.properties file into a zip file.
Results
If successful, the documents included in your zip file are linked with corresponding employee records.
Related Information
Setting Up Country-Specific Data Model


5.13 Configuring Business Rules for Data Imports
Use business rules to perform predefined tasks with different events during data imports.
Prerequisites
• You have set the Permission Settings Administrator Permissions Employee Central Import Settings
Enable Business Rules for selected entities permission.
• You have set the Permission Settings Administrator Permissions Employee Central Import Settings
Enable execution of rules against NO_OVERWRITE permission.
Context
You can apply business rules with data imports to execute supplementary tasks when data is changed or saved .All
HRIS entities are supported.
Business rules can be linked to an HRIS element or any of its fields. Rules are triggered based on the event type
selected. For imports, HRIS elements support onSave, onPostSave event types, whereas HRIS fields support only
onChange event type.
 Note
onPostSave event is applicable to the Job Information entity only.
When deleting records, business rules are not triggered except for onSave rules for workflows. For those workflow
rules to be triggered, only the SET operation on the same type or record for deletion is supported.
Special Cases to Note While Configuring Rules
 Restriction
onChange business rules attached to fields of an HRIS entity are triggered during the import process,
irrespective of whether there are any changes or not. However, this restriction isn't applicable to HRIS entities
supported by Centralized Services as onChange rules attached with such entities are triggered only when there
are changes to the corresponding field values.
• Non-Recurring Pay Component Imports

This import doesn't trigger onSave and onChange business rules configured for Job History information.
• Job History Imports
You cannot use event reasons in business rules to trigger changes in employment status. For example, you
cannot terminate an employment using a business rule.
• Import Personal Information for Dependents
It doesn't trigger the onSave or onChange business rules attached to thepersonalInfo HRIS element having
base objects as Dependents or Personal Information.

• Recurring Pay Component Imports
The DELETE operation is not supported. The SET operation is supported only when you set values in the
same record; setting values in other recurring pay components is not possible. When used to set values in the
same record, the CREATE operation works like a set. When used to set values in or create another record, the
CREATE operation is supported only for Centralized services imports.
Behavior with Cross-Entity Rules
Employment-related entities support cross-entity business rules, under specific conditions.
Cross entity-rules are supported for workflows.
In cross-entity rules, forward propagation on a target entity (for example, Compensation Information) is applied if
the source entity (for example, Job Information) has permission for forward propagation.
Behavior with Event Reason Derivation
• Manual Event Reason Derivation

If the event reason value is provided in the import template, then this event reason is used.
The data is validated by the system to ensure that an event reason is given. Since it is a required field, it cannot
be empty.
If the event reason is removed from the template or if &&NO_OVERWRITE&& value is provided in the template
for Event Reason field, the system reminds the user that an event reason is a required field.
• Using Event Reason Derivation with Business Rules
To have the event reason derived using business rules, you must enable the Enable Business Rules for selected
entities permission for imports. We also recommend activating the Enable the Execution of Rules Against
NO_OVERWRITE setting.
If the event reason value is provided in the import template, then the event reason provided in template is taken
into account rather than the event reason derivation by onSave business rules.
When you create records using imports, if an event reason is provided but is empty in the template, then
the event reason is derived using the onSave business rules. If the event reason is removed from the import
template or if the &&NO_OVERWRITE&& value is provided in the template for the Event Reason field, then the
event reason derivation by onSave business rules is used.
When you update records using imports, if the event reason is removed from the template or if the
&&NO_OVERWRITE&& value is provided in the template for the Event Reason field, then the event reason
used before the update will be used.
Procedure
1. Go to Admin Center Configure Business Rules .

2. Create a business rule by selecting  (Create New Rule) .
3. Select the rule scenario that best fits your requirements.
4. Enter the Rule Name, Rule ID, and select a Start Date.
The Rule ID automatically picks up the value entered in the Rule Name field. However, it can be changed.
5. Select a Base Object.
The base object must correspond to the name of the HRIS element. Here are a few suggestions:

Select Base Object... With rules for HRIS element...
Spot Award or Spot Award Model payComponentNonRecurring
Job Information or Job Information Model jobInfo
Personal Information or Personal Information Model personalInfo
Compensation Information or Compensation Information compInfo

Model
Recurring or Recurring Model payComponentRecurring
Employment Details or Employment Details Model employmentInfo
6. Continue and set up the business rule as required.
You can handle exceptional conditions with the Raise Message action. However, this feature is supported
only for specific entities supporting Centralized Services. For all other entities, you can handle exceptional
conditions by:
1. Assigning the error or warning message to a custom string in the corresponding HRIS element.
2. Monitoring the custom string to catch any exceptions.
A business rule is created with the specified conditions.
Next Steps
Assign the business rule to the desired HRIS element or field. You can do this either from the Configure Business
Rules UI or navigate to the Business Configuration UI to assign it to the HRIS element.
Related Information

Assigning a Business Rule to an Employee Central Entity [page 165]
Use Cases: Business Rules [page 166]
Cross-Entity Rules with Centralized Services

5.13.1 Assigning a Business Rule to an Employee Central Entity
Apply the business rule by assigning it to the corresponding Employee Central entity.
Prerequisites
If you’re assigning a business rule to an Employee Central entity optionally supported by Centralized services,
and you want to apply a rule context criteria with the rule, ensure that the Centralized services settings for the
optionally supported entities are enabled from Company System and Logo Settings page.
Context
You can apply a business rule to an HRIS entity or one of its fields. You can also define a rule context to prevent
unnecessary rule triggers.
 Note
Rule contexts are applicable for onChange and onSave business rules only.
Procedure
1. Go to Admin Center Manage Business Configuration .
2. In the left pane, expand Employee Central HRIS Elements .

3. Select the respective HRIS element from the list.
4. To apply a business rule to an HRIS element:
a. In the Trigger Rules section, select the Base Object corresponding to the base object selected in the
business rule.
b. Select a value for Event Type.
c. Select the business rule from the Rules dropdown.
d. Set the value for the Enabled field to Yes.
e. If you want to set a rule context, select Details.
f. Under the Rule Contexts section, modify the settings to meet your requirements.
 Note
If you have Centralized services enabled, onSave business rules are executed with data imports only if
Imports setting is enabled.
g. Save your changes.

5. To apply a business rule to a localized HRIS field in the selected HRIS element:

a. Select Details associated with the HRIS field.
A pop-up window appears.
b. In the Trigger Rules section, select the Base Object corresponding to the base object selected in the
business rule.
c. Select a value for Event Type.
 Note
Only onChange is supported for HRIS fields.
d. Select the business rule from the Rules dropdown.

e. Set the value for the Enabled field to Yes.
f. If you want to set a rule context, Select Details.
g. Under the Rule Contexts section, make selections to meet your requirements.
 Note
If you have Centralized services enabled, onChange business rules are executed with data imports only
if Imports setting is enabled.
h. Save your changes.
Results
You’ve successfully assigned a business rule to the selected HRIS entity.
5.13.2 Use Cases: Business Rules
Notable scenarios related to business rule execution with different data imports.
Cross-Entity Rules with Centralized services
Cross-entity rules configured to create new records are now regulated by Centralized services. Newly created
records are added only if they’re unique and don't match with existing records. Otherwise, the existing record is
updated.
The following example explains the behavior from the perspective of Job Information, but the logic is applicable to
cross-entity rules between Compensation Information and Recurring Pay Component entities.

 Example
Let's suppose a user has existing Job Relationships as follows:
Sample Job Relationship Data

Event Date End Date
User ID Relationship Type (dd/mm/yyyy) (dd/mm/yyyy) Related User ID Notes
JDoe Second Manager 01/01/2021 31/12/2021 JSmith Note 1
JDoe HR Manager 01/01/2021 31/12/2021 CGrant Note 2
You add a new Job Information record by importing data in Incremental Load mode.
Sample Import Data

Event Date (dd/mm/ End Date (dd/mm/
User ID yyyy) yyyy) Job Title Event Reason
JDoe 11/01/2021 Manager DATACHG
An onSave rule is attached to the Job Information entity that creates a new Job Relationship record.
Rule-Created Data
Event Date (dd/mm/
User ID Relationship Type yyyy) Related User ID Notes
JDoe Second Manager 01/01/2021 JSmith Note 3
Result: This record is not added as the business keys (User ID, Start Date, Relationship Type) match with an
existing Job Relationship record.
Add a new Job Information record by importing data in Incremental Load mode.
Sample Import Data

Event Date (dd/mm/ End Date (dd/mm/
User ID yyyy) yyyy) Job Title Event Reason
JDoe 11/02/2021 Manager DATACHG
The following record is created as a result of business rule execution:
Rule-Created Data
Event Date (dd/mm/
User ID Relationship Type yyyy) Related User ID Notes
JDoe Second Manager 01/01/2021 JSmith Note 3
Since the business keys of the new record match with an existing record, the existing record is updated with
new information instead.

Event Date End Date
JDoe Second Manager 01/01/2021 31/12/2021 JSmith Note 3

Event Date End Date
JDoe HR Manager 01/01/2021 31/12/2021 CGrant Note 2
onChange Rules with Centralized Services: Updating Value of a Field Present in

the Import File
onChange rules configured at the field level of an HRIS entity can update the value of other fields in your import file
only if the field value is null or empty.
 Example
Let's suppose a user has the following Personal Information.
Sample Personal Information

Person ID External Custom String 1 Custom String 2 Custom String 3
ecsl Personal Information Type A Personal Information Type B
You add new Personal Information by importing data in Incremental Load mode.
Sample Import Data

Personal ID External Custom String 1 Custom String 2 Custom String 3
ecsl Personal Information Type C Personal Information Type D
Now, if there are onChange rules configured on <Custom String 1>, <Custom String 2> such that,
 Sample Code
//Rule 1
if(Personal Information.custom-string1 == Personal Information Type C) THEN
SET Personal Information.custom-string2 == Personal Information Type E
//Rule 2
if(Personal Information.custom-string2 == Personal Information Type E) THEN
SET Personal Information.custom-string3 == Personal Information Type F
During the data import process, Rule 1 is evaluated as true. But since <Custom String 2> has a value in the
import file, it takes precedence over the rule evaluation. As a result, Rule 2 is evaluated as false.
Result:

ecsl Personal Information Type C Personal Information Type D
 Example
Let's suppose a user has the following Personal Information.

Sample Import Data

Personal ID External Custom String 1 Custom String 2 Custom String 3
ecsl Personal Information Type C
Now, if there are onChange rules configured on <Custom String 1>, <Custom String 2> such that,
 Sample Code
//Rule 1
if(Personal Information.custom-string1 == Personal Information Type C) THEN
//Rule 2
if(Personal Information.custom-string2 == Personal Information Type E) THEN
SET Personal Information.custom-string3 == Personal Information Type F
//Rule 3
if(Personal Information.custom-string3 == Personal Information Type F) THEN
SET Personal Information.custom-string1 == Personal Information Type G
During the data import process, Rule 1 and Rule 2 are evaluated as true. Therefore, the values of <Custom
String 2> and <Custom String 3> are updated accordingly. But since <Custom String 1> has a value in
the import file, it takes precedence over the rule evaluation. As a result, Rule 3 is evaluated as false.
Result:

ecsl Personal Information Type C Personal Information Type E Personal Information Type F
onChange Rule Behavior with Centralized Services: Updating Value of a Field

Not Present in the Import File
onChange rules configured on the field level of an HRIS entity don't update fields excluded in your import file or
marked as not to be overwritten. But if you’ve the Enable execution of rules against NO_OVERWRITE permission,
the rules are able to update fields not present in your import file, or fields marked as not to be overwritten.
 Example
Prerequisites: You don't have the Enable execution of rules against NO_OVERWRITE permission.
Case 1: Let's suppose a user has existing Personal Information as follows:

Sample Import Data

Personal ID External Custom String 1 Custom String 3
The following onChange rule is configured on <Custom String 1>:
 Sample Code
IF (Personal Information.custom-string1 == Personal Information Type C) THEN

Result: When the data import job is in progress, Rule 1 is evaluated to be true. But <Custom String 2> is not
present in the import file, and has a definite value in the existing record. Therefore, its value isn’t updated.

ecsl Personal Information Type C Personal Information Type B

Person ID External Custom String 1 Custom String 2
ecsl Personal Information Type A
Sample Import Data

Personal ID External Custom String 1
 Sample Code

Result: When the data import job is in progress, Rule 1 is evaluated to be true. But <Custom String 2> is
not present in the import file, and doesn’t have a definite value in the existing record. Therefore, its value is
updated.

ecsl Personal Information Type C Personal Information Type E
 Example
Prerequisites: You have the Enable execution of rules against NO_OVERWRITE permission.

Sample Import Data

Personal ID External Custom String 1 Custom String 3
 Sample Code

Result: When the data import job is in progress, Rule 1 is evaluated to be true. <Custom String 2> is not
present in the import file, and has a definite value in the existing record. But since you've the Enable execution
of rules against NO_OVERWRITE permission, its value is updated.


ecsl Personal Information Type A
Sample Import Data

Personal ID External Custom String 1

 Sample Code

Result: When the data import job is in progress, Rule 1 is evaluated to be true. <Custom String 2> is
not present in the import file, and doesn’t have a definite value in the existing record. Therefore, its value is
updated.

Derivation of the 'Previous Value' in onSave Rules
When you're adding multiple records for a user in a chronological order, rules configured to evaluate based on the
previous value of a field (in correspondence with a given date) will refer to the existing records of the user, and not
the records in your import file. If there are no existing records present, the rule will evaluate against a null value.
 Example
Let's suppose a user has the following Job Information:

Event Date (dd/mm/yyyy) User ID Event Reason Business Unit
01/01/2020 JDoe HIRE Business Unit DB
You add new Job Information for the same user by importing data in Full Purge mode.
Sample Import Data

Event Date (dd/mm/yyyy) User ID Event Reason Business Unit
01/01/2020 JDoe HIRE Business Unit Import
01/02/2020 JDoe DATACHG New Business Unit
You have the following rule configured with the Job Information entity for an onSave event.
 Sample Code
IF (Job Information Mode.Business Unit.Value != Job Information Mode.Business

Unit.Previous Value) THEN
SET Job Information Mode.Job Title.Value == Job Information Mode.Local Job
Title.Value
When this rule is triggered for the record with event date (01/02/2020), the previous value of the <Business
Unit> is obtained as Business Unit DB, and not Business Unit Import.

 Example
Insert Use Case for Compensation Information:
For example, we have a onSave rule that calculates the ratio between the previous value of a salary Salary
Amount and the current value of it, and it copies it into Salary Change % custom field.

“Salary Amount” Custom Field in
Event Date Sequence Number Compensation Information
01/01/2022 1 A
01/02/2022 1 B
You insert a new Compensation Information record for the same user on an existing date by importing data in
Incremental mode. Without a sequence number specified, the import is considered as an insert, the same way
as if we specify it to be the second one.
This new Compensation Information record contains C as the Salary Amount value on the 01/02/2022 with
sequence number 2.
Sample Import Data

01/02/2022 2 C
When the rule is triggered for the record with event date (01/02/2022), the previous value of the Salary
Amount is obtained as B. As a result, the value of Salary Change % is a ratio between B and C.
Sample Compensation Information After Import

Current Value of “Salary Previous Value of “Salary
Event Date Sequence Number Amount” Custom Field Amount” Custom Field
01/01/2022 1 A -
01/02/2022 1 B -
01/02/2022 2 C B
 Example
Update Use Case for Compensation Information:
For example, we have a onSave rule that calculates the ratio between the previous value of a salary Salary
Amount and the current value of it, and it copies it into Salary Change % custom field.

01/01/2022 1 A
01/02/2022 1 B

You update a Compensation Information record for the same user on an existing date by importing data in
Incremental mode.
This new Compensation Information contains C as the Salary Amount value on the 01/02/2022.
Sample Import Data

01/02/2022 1 C
When the rule is triggered for the record with event date (01/02/2022), the previous value of the Salary
Amount is obtained as B, and not A. As a result, the value of Salary Change % is a ratio between B and C.
Sample Compensation Information After Import

Current Value of “Salary Previous Value of “Salary
Event Date Sequence Number Amount” Custom Field Amount” Custom Field
01/01/2022 1 A -
01/02/2022 1 C B
Compensation Rule Behavior Change for Recurring Pay Components
A rule which uses the CREATE command to update an existing PCR causes the PCR to be updated with the rule
result. The values of any fields which are not filled explicitly by the rule, are taken from the existing record. The audit
fields (creation date and user) show that the PCR was updated.
 Example
Let's suppose a user has the following Recurring Pay Component saved in the system:
Sample Recurring Pay Component

Start Date
(dd/mm/ Pay Compo- Custom
yyyy) nent Amount Currency Frequency String Created By Created On
01/09/2022 Base Salary 1000 USD Monthly existingValue adminUser1 2022-09-01

12:00:00

When another user performs an edit using the createPCR rule to the exisiting Compensation Information, the
following result is seen:
Sample Output
Start
Date
(dd/mm/ Pay Com- Fre- Custom Created Created Changed Changed
yyyy) ponent Amount Currency quency String By On By On
01/09/20 Base Sal- 1000 USD Monthly existing- admi- 2022-09- admi- <time at
22 ary Value nUser1 01 nUser2 execu-
12:00:00 tion>
When another user inserts a new Compensation Information using the createPCR rule, the following result is
seen:
Sample Output
Start
Date
(dd/mm/ Pay Com- Fre- Custom Created Created Changed Changed
yyyy) ponent Amount Currency quency String By On By On
01/09/20 Base Sal- 1000 USD Monthly existing- admi- <time at admi- <time at
22 ary Value nUser2 execu- nUser2 execu-
tion> tion>
5.14 Configuring Workflows for Data Imports
Create an approval process by configuring workflows to review data being imported.
Prerequisites
• You've enabled Enable Business Rules for Workflow Derivation setting in Provisioning.
 Remember
Support.
• You've the Enable Workflows for selected areas permission.

Context
A workflow is a sequence of connected steps that allows you to notify and seek approval from the concerned
stakeholders before importing data. You can configure a workflow with the following data imports:
• Job History
 Remember
Workflows configured with Job History:

• Are triggered only if your import file contains one record for each user. If there are multiple records for
the same user with at least one record requiring approval, the data for this user isn’t imported.
• Are triggered only by the entity used in the import, for example, Job History. If no workflow is triggered
by the entity in the import, all changes are immediately saved to the database, including derived
entities, such as cross entity rule results.
• Are triggered only when a new Job History record is inserted in the import.
• Are not supported for the Update operation. This means that a workflow isn't triggered when a Job
History record with a configured workflow is updated, with or without derived entities involved, such as
Compensation Information.
• Aren't triggered for a new hire record. They are triggered for internal hire though.
• Support Carbon copy (Cc) role notifications.
All workflows are triggered when data is imported in Incremental Load mode only.
• Non-Recurring Pay Component Information
 Remember
Workflow configured with Non-Recurring Pay Component:
A workflow is created for each record resulting in multiple records being processed for a user. Without
Centralized services setting enabled, a workflow would be created for only one user record. The remaining
records for the user will not be processed.
When terminating the employment a user on a global assignment, the system now uses the End Global
Assignment workflow rather than the Termination workflow as was previously done.
Procedure
1. Configure a workflow to set up an approval process.

2. Configure a basic business rule with conditions to trigger the workflow.
 Tip
Ensure that the base object of your business rule corresponds to the Employee Central entity with which
you want to attach the workflow.
3. Assign the business rule to the respective Employee Central entity.

Results
You've successfully configured and assigned a workflow. When the workflow is triggered, a task to review the import
data is created and assigned to each recipient defined in the workflow. Email notifications are generated to inform
the recipients about the actions. Based on their approval, data is imported.
Related Information
Employee Central Workflows: Creating a Workflow

Assigning a Business Rule to an Employee Central Entity [page 165]
5.15 Managing Access to Basic User Imports
Govern who can, and who can't import basic user information by managing access to basic user import.
Context
Previously, admins having access to the Import Employee Data page could import all sorts of employee data,
including basic user information. With Q4 2019, you have the option to restrict access to basic user information
imports with the help of role-based permissions. You can configure your system so that admins having the Basic
User Import permission can import basic user information.
 Note
If you choose not to configure role-based access to basic user information imports, admins can import basic
user information as long as they can access the Import Employee Data page.
Procedure
1. Go to Admin Center Manage Employee Central Settings .

2. Select Enable Control on Basic User Import in Role-Based Permissions.
3. Save your changes.

Results
The Basic User Import permission is now available for assignment.
Next Steps
Grant the Basic User Import permission to the required user roles.
Related Information
5.16 Restricting Legal Entity Changes to an Employee Profile
Prevent complications arising out of legal entity-related changes with Job Information imports.
Context
While importing Job Information of employees rehired on a new employment, you must ensure that the legal
entity associated with their new employment doesn’t match with the legal entity associated with their previous
employment. Because employees can only be associated with one legal entity, a new employment must be
associated with a new legal entity.
Procedure

2. Select Employment Settings Configuration from the Create New dropdown.
3. Enter a unique identifier of the configuration in the Code field.
4. (Optional) Enter the name of the configuration in the Name field.
5. Select the status as Active.
6. Select the condition to enforce new employment as On Change of Legal Entity.

Results
The employee settings configuration is created and activated.
5.17 Scheduling Data Import Jobs
Create a recurring job to import a specific type of employee data to your Employee Central instance.
Prerequisites
You have an SFTP account. For security reasons, we recommend that you use SAP SuccessFactors hosted SFTP
server. In case you don't have an SFTP account, contact your Partner or SAP Product Support.
Context
If you want to automate the employee data import process through an SFTP/FTP Job Scheduler, you can create a
recurring job request in Admin Center Scheduled Job Manager Job Scheduler Create Job Request .
For import jobs that contain any sensitive data, if you download the file from the Scheduled Job Manager log, then
this is added to the Read Audit log. For more information, refer to the Scenarios Supporting Entering Download
Reasons topic.
Procedure
1. In the Admin Center, go to Scheduled Job Manager Job Scheduler Create Job Request .
2. Create a job definition by providing a Job Name and assigning a Job Owner.
3. From the Job Type dropdown, select Employee Data Import (For Employee Central Only).
4. Define the job parameters by selecting the type of data you want to import
If you don’t have the up-to-date import template, select Download a blank CSV template.
For Basic Import, there are additional options available. Select the options as applicable.
Some import types provide the option of choosing how you want to import data. Select:
• Full Purge, if you want to delete or overwrite existing employee data with the data in your import template.
• Incremental Load, if you want to retain existing employee data and update only the required data present in
your import template.
If you want to encode the template in a format other than Unicode (UTF-8), select an encoding format from
the File encoding dropdown.

To select the file locale other than English (United States), choose from the File Locale dropdown.
 Note
The options appearing in the dropdown correspond to the language packs selected during Employee
Central configuration. File Locale allows you to choose the language and locale for the data you’re
importing, which is especially important for date, number, and picklist fields, as the format can change
based on the locale. Selecting a file locale wouldn’t affect your default logon language or the language of
your UI components.
5. Configure the server access parameters by entering the Host Address

6. Enter the FTP Login and FTP Password values.
 Tip
These values can be obtained from the Operations team.
7. Select FTP Passive Mode if applicable, only after confirming with the Operations team.
8. Keep the SFTP Protocol checkbox selected and test the connection. Also test whether the file put permission is
working as required.
9. Provide the file path where your import file can be located by the job scheduler.
10. Enter the name of your import file template, and select a date format and the file encryption method of your
choice.
If the job scheduler is unable to find your import file on the server, your scheduled job is not executed and
marked with status as "Skipped".
11. Set the job recurrence criteria as applicable.
12. Enter the date and time when you would like the job to start.
13. Enter the email addresses of users who must be kept notified about events related to the job execution.
14. Select the checkbox to send an email notification when the job starts, if necessary.
15. Complete the job request creation by selecting Submit.
Results
If successful, your job request is created and listed under the Manage Scheduled Jobs page.
Next Steps
As a next step, you can:
• Manually initiate the job for the first time. To do so, select Actions Run It Now against your job on the
Manage Scheduled Jobs page.
• Create a new job request for importing another type of employee data.

5.18 Automatic Interruption and Cancellation of Import Jobs
From the performance standpoint and resource utilization perspective, actively running data import jobs are
interrupted or canceled upon failing to meet the required criteria.
Data import jobs are now internally monitored in reference to metrics such as time taken since inception, memory
consumption and so on. If a job fails to meet a certain pre-defined threshold, it’s interrupted or cancelled as
applicable. The intention is to help reduce the overhead cost of scheduling and running jobs with errors, and enable
job owners to manage failed jobs more effectively.
This process of automatic interruption or cancellation applies to import jobs initiated from the UI or API, as well as
scheduled jobs in Provisioning.
Criteria for Auto-Cancellation of Jobs

A data import job qualifies to be canceled if:
• It's failing repeatedly, and

• There are at least 100 failures reported within a span of 90 days.
If a job is canceled, the respective job owners are notified accordingly with the help of email notifications.
Criteria for Auto-Interruption of Jobs

A data import job qualifies to be interrupted if its running for a long time, or is memory intensive. The following
conditions help evaluate if a data import job should be interrupted:
• Its been running for more that 2 hours, or

• Is consistently utilizing significant system memory (~90%) for over 30 minutes.
All interrupted jobs are recovered after some time with the same job request ID, and their status is set to
"Recovered".
A data import job is interrupted and recovered only twice. Thereafter, the job runs uninterrupted till its completion.
You can monitor the progress of your jobs at Admin Center Monitor Jobs page.

6 Data Protection and Privacy
Learn how you can keep the personal data of your employees secure and private with SAP SuccessFactors.
Centralized Data Protection and Privacy [page 182]

Data protection and privacy features work best when implemented suite-wide, and not product-by-product.
For this reason, they’re documented centrally.
Data Retention Management [page 183]

Identify which data purge function in the Data Retention Management tool meets your data protection and
privacy requirements.
6.1 Centralized Data Protection and Privacy
Data protection and privacy features work best when implemented suite-wide, and not product-by-product. For this
reason, they’re documented centrally.
The Implementing and Managing Data Protection and Privacy guide provides instructions for setting up and using
data protection and privacy features throughout the SAP SuccessFactors HCM suite. Please refer to the central
guide for details.
 Note
SAP SuccessFactors values data protection as essential and is fully committed to help customers complying
with applicable regulations – including the requirements imposed by the General Data Protection Regulation
(GDPR).
By delivering features and functionalities that are designed to strengthen data protection and security,
customers get valuable support in their compliance efforts. However, it remains each customer’s responsibility
to evaluate legal requirements and implement, configure, and use the features provided by SAP SuccessFactors
in compliance with all applicable regulations.
Parent topic: Data Protection and Privacy [page 182]
Related Information
Data Retention Management [page 183]

Implementing and Managing Data Protection and Privacy

182 PUBLIC Data Protection and Privacy
6.2 Data Retention Management
Identify which data purge function in the Data Retention Management tool meets your data protection and privacy
requirements.
The Data Retention Management tool supports two different data purge functions: the newer data retention time
management (DRTM) function and legacy non-DRTM function.
 Remember
We encourage all customers to stop using the legacy purge function and start using data retention time
management (DRTM) instead. To get started using this and other data protection and privacy features, refer to
the Data Protection and Privacy guide.
If you already use the legacy data purge function as part of your current business process and you are sure that it
meets your company's data protection and privacy requirements, you can continue to use it, as long as you aware
of the differences between the two.
 Note
If you are using the legacy data purge function, you can only purge a calibration session when there is at least
one facilitator assigned to the session.
 Restriction
Be aware that the legacy data purge function may not meet your data protection and privacy requirements. It
doesn't cover the entire HCM suite and it doesn't permit you to configure retention times for different countries
or legal entities.
In the longer term, we recommend that you also consider adopting the newer solution. In the meantime, to use
legacy data purge, please refer to the guide here.
Parent topic: Data Protection and Privacy [page 182]
Related Information
Centralized Data Protection and Privacy [page 182]

Data Protection and Privacy PUBLIC 183
7 Implementation of Off Cycle Event Batch
Understand the basic implementation sequence of an Off Cycle Event Batch.
To get an Off Cycle Event Batch up and running is a three step process.
Off Cycle Event Batch [page 184]

Off Cycle Event Batch is a native Employee Central feature that offers key automation capabilities to help
you manage your employee data better.
Creating an Off Cycle Event Batch Object [page 186]

Before you schedule a job to execute on a periodic basis, you must have an instance of Off Cycle Event
Batch configured in place.
Creating a Business Rule for an Off Cycle Event Batch [page 190]
Identify the employee records to be processed by the Off Cycle Event Batch by creating a business rule.
Creating a User or Group of Users for an Off Cycle Event Batch Job [page 192]
You can create user groups for an off cycle event batch job. This allows you to run the rule in off cycle event
batch, only for the users of that off cycle event batch user group.
Setting Up an Off Cycle Event Batch Job [page 193]

After creating a business rule and an off cycle event batch object, setting up a scheduled job is the final step
in the process.
Adding Off Cycle Event Batch Object to a Transport Bundle [page 194]
Adding Off Cycle Event Batch Object to a transport bundle.
Additional Configurations [page 195]

Here are some important actions and settings that you can perform based on your requirement.
7.1 Off Cycle Event Batch
Off Cycle Event Batch is a native Employee Central feature that offers key automation capabilities to help you
manage your employee data better.
An Off Cycle Event Batch is a Metadata Framework (MDF) object that you can use to create an automated process
for modifying the following employee data:
• Job Information

184 PUBLIC Implementation of Off Cycle Event Batch
• Employee Time
• Work Order Information (for Contingent Workers)
With the help of an Off Cycle Event Batch, you can configure your system to execute a customized set of
instructions in the background for transactions that are recurring. As a result, the periodic requirement for
manually updating the employee records is practically eliminated.
What are these "recurring transactions" an Off Cycle Event Batch can handle?
Recurring transactions are events that periodically occur in your company, and therefore can vary accordingly.
Some of them include, but not limited to:
• Processing probation periods of employees

• Processing changes in pay scale level of employees eligible to the next pay scale level on a specified effective
date
• Processing seniority-based compensation updates to employee master data
• Generating Intelligent Services
How does an Off Cycle Event Batch work?
A fully configured Off Cycle Event Batch typically performs the following set of tasks:
1. Generate a list of employee records.
 Note
This task is executed only if you've configured your Off Cycle Event Batch to generate a list of employee
records to update. Otherwise, all the employee records in the system are considered.
2. Apply filter criteria as defined in your Off Cycle Event Batch object.
3. Execute the attached business rule to update the corresponding user records.
4. Import the data into the system.
 Note
Job Information data is forward propagated to future effective dated records with Off Cycle Event Batch
Job if the Enable Forward Propagation during Incremental Import permission is enabled.
Parent topic: Implementation of Off Cycle Event Batch [page 184]
Related Information

Forward Propagation in Job Information and Job Relationships

Implementation of Off Cycle Event Batch PUBLIC 185
7.2 Creating an Off Cycle Event Batch Object
Before you schedule a job to execute on a periodic basis, you must have an instance of Off Cycle Event Batch
configured in place.
Prerequisites
A business rule applicable to the process is created. For more information about creating a business rule, refer to
the Related Information section.
Context
The primary requirement to schedule a rule processing job in Provisioning is to have an Off Cycle Event Batch
object. This helps the system to identify the batch and execute it according to schedule. It will pick all the records
that match the filter criteria defined in the Off Cycle object.
 Remember
implementation partner or Account Executive. For any non-implementation tasks, contact Product Support.
Procedure

2. Select Off Cycle Event Batch from the Create New dropdown.
3. Fill out the form with details as appropriate.
Field Action
Code Enter a label to identify your Off Cycle Event Batch job.
Associated Rule Select the business rule from the dropdown.
Base Object Select a target base object or HRIS element from the drop-
down.
 Note
If you create an Off Cycle job for the base object Job
Information, the job considers only the current active

Field Action
records of employees to prevent creation of duplicate

records.
• To execute batch rules, either choose Job Information

and Employment Details.
 Note
For executing rules on job information or employ-
ment information, you are required to enable
Administrator Permissions Employee Central
Import Settings Enable Business Rules for
selected entities .
Off Cycle Event Batch User Group (Applicable for Job Select a user group from the dropdown to specify a target
Information and Employment Details base objects.) population.
 Remember
Select a user group only if you want to run the off cycle
batch for a particular group of employees. To include all
employees, skip this field.
Include All Matched Records in Every Run (Applicable for Select Yes if you want to update user records with recurring
Job Information, Employment Details, and Work Order base event information. To update non recurring event informa-
objects.) tion, select No.
 Example
• Events like changes to an employee's pay scale
are recurring and happen periodically. Select Yes in
such cases.
• Events like employee eligibility for company assets
like a car are non recurring and happen only once.
Select No in such cases.
Include Inactive Records (Applicable for Job Information and Select Yes, if you want to process inactive user records.
Employment Details base objects.)
Status Select Active from the dropdown.
Frequency Select a value from the dropdown to define the frequency of

the batch.
• No Selection
• Daily (default selection)
• Weekly
• Monthly

Field Action
 Note
This schedule will take precedence over the schedule
defined in Provisioning.
Day of Execution (Appears when Frequency is selected as Select the preferred day of the week or month, as applicable,
Weekly or Monthly) for executing the job.
4. OPTIONAL: Set a filter criteria to further streamline the list of user records to process.
If you create multiple filters, the system will filter records matching each filter criteria, and add them to the final
list of matching records.
Field Description
Filter Field Select the field from the dropdown. Example: Start Date.
 Note
Applicable for Job Information and Employment Details
base objects.
Operator Select an operator.
Offset Enter a number appropriate for the offset unit. This means,
how much time after the begin date should the batch run.
Offset Unit Depending on the selected base object, the offset may differ
or may not be supported at all.
For the Filter field, you can filter all the configured date fields for both standard and custom fields in Business
Configuration for the selected base object in the Off Cycle Event Batch.
The filter lists all the active date fields for jobInfo (Job Information base object) and employmentInfo
(Employment Detail base object). The type of HRIS Field should be Date and enabled Yes in the Business
Configuration. Additionally the filter also lists fields that are preconfigured for jobInfo (Job Information base
object) and employmentInfo (EmploymentDetail base object) that don’t need to be configured in Business
Configuration.
The preconfigured fields for jobInfo and employmentInfo are:
Job Information Employment Detail
startDate startDate
positionEntryDate serviceDate
jobEntryDate seniorityDate
companyEntryDate benefitsEligibilityStartDate

Job Information Employment Detail
locationEntryDate
departmentEntryDate
payScaleLevelEntryDate
hireDate
terinationDatem
leaveOfAbsenceStartDate
leaveOfAbsenceReturnDate
 Note
If the date field isn’t part of the Business Configuration and the additional filters list, you can’t save
the Off Cycle Object. We’ve included a validation message to notify you to either update the Business
Configuration or delete the filter fields in Off Cycle Event Batch.
 Example
Result when batch runs

Filter Field Operator Offset Offset Unit on 01/01/2019
hireDate is equal to 1 Year(s) The batch will pick up

all records which have
a hireDate equal to
01/01/2018.
hireDate is before 1 Year(s) The batch will pick up

a hireDate before
01/01/2018.
hireDate is on or before 1 Year(s) The batch will pick

up all records which
have a hireDate on or
before 01/01/2018.
hireDate is after 1 Year(s) The batch will pick

up all records which
have a hireDate after
01/01/2018.
hireDate is on or after 1 Year(s) The batch will pick up

a hireDate on or after
01/01/2018.
The Off Cycle Event Batch also filters records by Last successful run date, which is configured in job details
and is recommended for jobs meant for daily execution. The Off Cycle Event batch will only filter records whose
[last successful run date minus offset]< date field. The last successful run date could be the last successful job
run date or a specified date.

Results
You have successfully created an Off Cycle Event Batch object.
To check the progress of the job, go to Admin Center Monitor Jobs page.
Next Steps
Set up a schedule job in Provisioning.
 Remember
implementation partner or Account Executive. For any non-implementation tasks, contact Product Support.
Task overview: Implementation of Off Cycle Event Batch [page 184]
Related Information

Optimize Offcycle Event Batch Object Configuration
7.3 Creating a Business Rule for an Off Cycle Event Batch
Identify the employee records to be processed by the Off Cycle Event Batch by creating a business rule.
Prerequisites
In case you have an existing Basic business rules in place for Off Cycle Event Batch, use the Check Tool checks
under Application Employee Central Core to identify, and in some cases migrate your existing Basic rules to
Off Cycle rule scenario specific rules.

Context
With business rules, you can implement comprehensive sets of instructions to identify and process the exact
employee records.
Procedure
1. Go to Admin Center Configure Business Rules .

2. Create a business rule by selecting  (Create New Rule)
 Note
• New rules created for Off Cycle Event Batch Processing Job, should use the new rule scenario Trigger
Rule for Off Cycle Event Batch rule scenario.
• New rules created for Work Order Off Cycle job, should use the new rule scenario Trigger Notification for
Work Order Expiration.
3. Under Employee Central Core, select Trigger Rules for Off Cycle Event Batch.
The Trigger Rule for Off Cycle Event Batch rule scenario is preconfigured..
4. Enter the Rule Name, Rule ID, and select a Start Date.
The Rule ID automatically picks up the value entered in the Rule Name field. However, it can be changed.
5. Select a Base Object.
A Base Object corresponds to the data objects available in the system, and provides you with inputs for
defining the rule. You must select the same Base Object while creating an Off Cycle Event Batch event
definition.
6. Click Continue.
7. Set up the business rule according to your requirement.
 Note
• The SET action is supported only for the HRIS employee entities (and not MDF entities) and the rule
will modify only a single type of employee entity. Note that updating multiple types of entities in a single
rule is not supported. The effective date of the modified record will be set to the date on which the Off
Cycle Event Batch processed this record. Providing effective date as user input is not supported.
• Ensure that you don't add 'CREATE' conditions of your rule, as Offcycle Event Batch doesn't support
rules with 'CREATE' conditions.
 Note
The rules created with the Basic rule scenarios will continue to work. We recommend that you move your
rules to the off cycle scenario which has more guardrails and helps avoid manual configuration errors.

Results
You’ve successfully created a business rule to work with your Off Cycle Event Batch.
Next Steps
Create an instance of the Off Cycle Event Batch object.
Related Information

Forward Propagation in Job Information and Job Relationships
7.4 Creating a User or Group of Users for an Off Cycle Event

Batch Job
You can create user groups for an off cycle event batch job. This allows you to run the rule in off cycle event batch,
only for the users of that off cycle event batch user group.
Prerequisites
You have the Administrator Permissions Manage Workflow Manage Workflow Groups
Procedure
1. Go to Admin Center Manage Off Cycle Event Batch Group .

2. Create a new group by selecting  Create New Group.
3. Type a name for your group. Then choose who you want to include in the group.
4. Choose Done to create a new group.
Related Information

7.5 Setting Up an Off Cycle Event Batch Job
After creating a business rule and an off cycle event batch object, setting up a scheduled job is the final step in the
process.
Prerequisites
You’ve created and configured an off cycle event batch object.
Context
By setting up a job schedule, you can configure your system to process the off cycle event batch object on
a periodic basis. Off Cycle Event Batch Processing Job is a primary handler for all the jobs scheduled in your
application. It picks up all active off cycle event batch records and executes them. However, you can’t preferentially
select which offcycle events batches be picked up by the job.
You can use Scheduled Job Manager in Admin Center to create, manage, and monitor Off Cycle Event Batch
Processing job type.
 Note
The BizX Daily Rule Processing Batch job is now renamed to Off Cycle Event Batch Processing Job.

Related Information

Managing Scheduled Jobs in Admin Center
7.6 Adding Off Cycle Event Batch Object to a Transport

Bundle
Adding Off Cycle Event Batch Object to a transport bundle.
Prerequisites
You have the Administrator Configuration Transport Center Access to Transport Configurations .
Context
Bundles are artifacts in the Configuration Transport Center that contain configurations of your system. You can
use bundles to transport the configuration of a source system to a paired target system so that you don't need to
manually configure it.
Procedure
1. Go to Manage Data page and select Off Cycle Event Batch in the Search dropdown.
2. Choose Take Action Add to Transport Bundle to add the current object instance to the bundle. A list of
available transport bundles are displayed.

 Note
• Cannot exclude references: The entire Off Cycle Event Batch object will be transported. You cannot
exclude references (like filters) during transport.
• Only allowed in Full Purge mode: If you are transporting an Off Cycle Event Batch object named
oceb_obj from one instance to another, and the destination already has an Off Cycle object with the
same name oceb_obj, then the existing Off Cycle Event Batch in the destination will be replaced by the
one from the source. The existing object in the destination instance will be overwritten with the new
object during the transport process, ensuring that the destination instance has the source version of
the Off Cycle Event Batch object.
3. Select the bundle you want to add the configuration to and choose Save.
Your configuration is successfully added to the transport bundle. A success message is displayed.
4. Choose Close.
Results
The object instance is added to the transport bundle.
Related Information

Exporting SAP SuccessFactors Application Configurations Using Configuration Transport Center
7.7 Additional Configurations
Here are some important actions and settings that you can perform based on your requirement.
Optimize Offcycle Event Batch Object Configuration [page 196]

Improve the performance and reduce the job execution time by modifying your off cycle event batch object
settings.
Monitoring Jobs [page 197]

Check the execution details and other statistics of each job associated with your primary batch.

Use Cases [page 197]
Here are some possible use cases for Off Cycle Event Batch processing.
Parent topic: Implementation of Off Cycle Event Batch [page 184]
Related Information

7.7.1 Optimize Offcycle Event Batch Object Configuration
Improve the performance and reduce the job execution time by modifying your off cycle event batch object
settings.
Your off cycle event batch taking a long time to complete may be most likely due to your existing configuration.
Here are a few checks and configuration settings that you can make to improve performance.
• User Record Filtering: Verify that your off cycle event batch is properly filtering user records. If user records
are not filtering appropriately, its possible that the batch is executing business rules against all the records in
the system.
• Dynamic User Group: If your requirement is to process a specific group of user records, you can create a
dynamic user group. A dynamic user group ensures that only the required user records are process and invalid
user records are are filtered out accordingly.
• Include all matched records in every run: Use this option very carefully. Enable this option while configuring
your off cycle event batch object only if you want to process all the records in every run. If not, the disable this
option so that only newly matched records are processed during each run.
• Add inactive records: Set this option to No, while configuring your off cycle event batch object unless you want
to process inactive user records for a specific use case.
• Business Rules: Business rules can be a major contributing factor when a job is reporting a longer execution
time. Please consider the volume of rules and the complexity of the rule configuration while configuring your off
cycle event batch.
 Tip
Setup your business rule so that If condition has the most possible matching criteria first followed by the
least possible matching criteria. This reduces the rule iteration time on each user record.
• Scheduling Off Cycle Event Batch Processing Job: Find a suitable time slot to schedule your job when the
server load is less. For an optimum performance, avoid scheduling all the jobs in that instance at same time,
unless it is specifically required.

7.7.2 Monitoring Jobs
Check the execution details and other statistics of each job associated with your primary batch.
Context
After you have created and initialized your primary batch, you can monitor each job to track its status and
download the job execution report if required.
Procedure
1. Go to Admin Center Scheduled Job Manager .
The Scheduled Job Manager page appears, which list all the jobs (of type Off Cycle Event Batch Processing
Job) that you have submitted. For each product in your SAP SuccessFactors HCM suite, there will be a job
available.
 Example
Off Cycle Event Batch will have a job called BizXDailyRuleBatch:Processor:OFFCYCLE_EVENT
This job will pick all active Off Cycle Event Batch records and execute them. You cannot select which off cycle
events batches should be picked up by the job as they are all collectively picked up and executed in the order of
creation. The system will trigger the rule for each Off Cycle Event Batch record, and log the last successful run
for each rule triggered.
2. Identify the job that you want to monitor.
3. Click Download Status corresponding to your job, if you want to download a copy of the job execution report.
A popup window appears prompting you to save the status file in a CSV format.
4. Save the file on your computer.
Related Information
Scheduled Job Statuses
7.7.3 Use Cases
Here are some possible use cases for Off Cycle Event Batch processing.
Following examples illustrate how you can configure your Off Cycle Event batch to address some of the most
common business scenarios.

Absence
Configuring a rule to execute changes related to employee absences.
 Example
Configuring your Off Cycle Event batch.
 Example
Anniversary
Configuring a rule to generate notification on the event of an employee's work anniversary.

 Example
 Example
Annual Fixed Salary Increase
Configuring a rule to execute changes related to Compensation Information of employees.

 Example
 Example
Manager Change
Configuring a rule to execute changes related to Job Information of employees. In this case, we are considering a
change of an employee's manager.

 Example
 Example
New Hire
Configuring a rule to execute changes in the Job Information for new hires.

 Example
 Example
Wage Progression
Configuring a rule to execute changes related to the automatic transition of employees to the next higher pay level.

 Example
 Example
Managing Employee Termination Details
 Restriction
As of Q3 2019, updating termination details of employees using Offcycle Event batch is not supported.

As a work around, you can update termination details of employees by:
1. Creating an business rule. The business rule has to be created using the Job Information element, and in the
If condition you can check for termination event reason and set the fields accordingly. For more information
about creating business rules, refer to the Implementing Business Rules in SAP SuccessFactors guide on the
SAP Help Portal.
2. Associating the rule with the Job Information HRIS element with an onSave event. For more information about
configuring HRIS elements, refer to the Setting Up and Using Business Configuration UI (BCUI) guide on the
SAP Help Portal.
As a result, when the Off Cycle batch is in progress and Job Information entity is accessed, the business rule is
executed.

8 Change History
Learn about changes to the documentation for Mass Changes in Employee Central in recent releases.
1H 2024
Type of Change Description More Info
Changed Dependents Import is universally sup- Centralized Services for Employee Data
ported by Centralized services. Imports [page 39]
Changed We have deleted the topic (Deprecated)

Consolidated Dependents Imports, be-
cause Consolidated Dependents import is
not supported by Centralized services as
of 1H 2024.
Changed We have changed the text "Consolidated Centralized Services for Employee Data
Dependents (to be deprecated)" to "Con- Imports [page 39]
solidated Dependents" in the Unsup-
ported Entities list in the related topic.
Changed Created a new topic about adding Off Adding Off Cycle Event Batch Object to a
Cycle Event Batch Object to a Transport Transport Bundle [page 194]
Bundle.
2H 2023
October 13, 2023
New Dependents import now supports busi- Configuring Business Rules for Data Im-
ness rules. ports [page 162]
Changed We moved the Change History to the end Overview of Mass Changes in Employee
of the guide. Central [page 4]
Changed Updated the topic about Off Cycle Event Creating a Business Rule for an Off Cycle
Batch Processing Job. Event Batch [page 190]
New Created a new topic about creating a user Creating a User or Group of Users for an
or group of users for an Off Cycle Event Off Cycle Event Batch Job [page 192]
Batch Job.

Change History PUBLIC 205
Changed Updated the topic about the new job Setting Up an Off Cycle Event Batch Job
name. The BizX Daily Rule Processing [page 193]
Batch job is now renamed to Off Cycle
Event Batch Processing Job.
Changed Updated the note about the new rule Creating a Business Rule for an Off Cycle
scenario Trigger Rule for Off Cycle Event Event Batch [page 190]
Batch

206 PUBLIC Change History
Important Disclaimers and Legal Information
Hyperlinks
Some links are classified by an icon and/or a mouseover text. These links provide additional information.
About the icons:
• Links with the icon : You are entering a Web site that is not hosted by SAP. By using such links, you agree (unless expressly stated otherwise in your agreements
with SAP) to this:
• The content of the linked-to site is not SAP documentation. You may not infer any product claims against SAP based on this information.
• SAP does not agree or disagree with the content on the linked-to site, nor does SAP warrant the availability and correctness. SAP shall not be liable for any
damages caused by the use of such content unless damages have been caused by SAP's gross negligence or willful misconduct.
• Links with the icon : You are leaving the documentation for that particular SAP product or service and are entering an SAP-hosted Web site. By using such links,
you agree that (unless expressly stated otherwise in your agreements with SAP) you may not infer any product claims against SAP based on this information.
Videos Hosted on External Platforms

Some videos may point to third-party video hosting platforms. SAP cannot guarantee the future availability of videos stored on these platforms. Furthermore, any
advertisements or other content hosted on these platforms (for example, suggested videos or by navigating to other videos hosted on the same site), are not within the
control or responsibility of SAP.
Beta and Other Experimental Features

Experimental features are not part of the officially delivered scope that SAP guarantees for future releases. This means that experimental features may be changed by
SAP at any time for any reason without notice. Experimental features are not for productive use. You may not demonstrate, test, examine, evaluate or otherwise use the
experimental features in a live operating environment or with data that has not been sufficiently backed up.
The purpose of experimental features is to get feedback early on, allowing customers and partners to influence the future product accordingly. By providing your feedback
(e.g. in the SAP Community), you accept that intellectual property rights of the contributions or derivative works shall remain the exclusive property of SAP.
Example Code
Any software coding and/or code snippets are examples. They are not for productive use. The example code is only intended to better explain and visualize the syntax and
phrasing rules. SAP does not warrant the correctness and completeness of the example code. SAP shall not be liable for errors or damages caused by the use of example
code unless damages have been caused by SAP's gross negligence or willful misconduct.
Bias-Free Language
SAP supports a culture of diversity and inclusion. Whenever possible, we use unbiased language in our documentation to refer to people of all cultures, ethnicities, genders,
and abilities.

Important Disclaimers and Legal Information PUBLIC 207
www.sap.com/contactsap
© 2024 SAP SE or an SAP affiliate company. All rights reserved.
No part of this publication may be reproduced or transmitted in any form

or for any purpose without the express permission of SAP SE or an SAP
affiliate company. The information contained herein may be changed
without prior notice.
Some software products marketed by SAP SE and its distributors

contain proprietary software components of other software vendors.
National product specifications may vary.
These materials are provided by SAP SE or an SAP affiliate company for

informational purposes only, without representation or warranty of any
kind, and SAP or its affiliated companies shall not be liable for errors or
omissions with respect to the materials. The only warranties for SAP or
SAP affiliate company products and services are those that are set forth
in the express warranty statements accompanying such products and
services, if any. Nothing herein should be construed as constituting an
additional warranty.
SAP and other SAP products and services mentioned herein as well as
their respective logos are trademarks or registered trademarks of SAP
SE (or an SAP affiliate company) in Germany and other countries. All
other product and service names mentioned are the trademarks of their
respective companies.
Please see https://www.sap.com/about/legal/trademark.html for

additional trademark information and notices.
THE BEST RUN

7734ba068ecd4762a48d33e91a4e0c27

Uploaded by

Copyright:

Available Formats

You might also like

7734ba068ecd4762a48d33e91a4e0c27

Uploaded by

Document Information

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

7734ba068ecd4762a48d33e91a4e0c27

Uploaded by

Copyright:

Available Formats

PUBLIC

Document Version: 1H 2024 – 2024-05-16

Managing Mass Changes in Employee Central

THE BEST RUN

1 Overview of Mass Changes in Employee Central. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4

2 Mass Data Management. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5

3 Managing Mass Changes. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 14

5 Employee Data Imports. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 39

Managing Mass Changes in Employee Central

6 Data Protection and Privacy. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 182

7 Implementation of Off Cycle Event Batch. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 184

8 Change History. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 205

Managing Mass Changes in Employee Central

Supported Entities/Data Ob-

Managing Mass Changes in Employee Central

Salient features of Mass Data Management:

Using Mass Data Management, you can:

• Flexibly build a list of positions to modify using extensive filtering capabilities.

2.1 Permissions for Mass Data Management

Permission Type Permission Category Permission Name Result

User Miscellaneous Permissions MassChangesJob Grants access to create and

Managing Mass Changes in Employee Central

1. Go to Admin Center Manage Data .

The user-defined value must be less than or equal to 50.

Managing Mass Changes in Employee Central

10. Save the configuration.

• Delete an existing configuration.

Managing Mass Changes in Employee Central

Create a mass change request from Mass Data Management.

Permissions for Mass Data Management [page 5]

2.3 Creating Mass Change Requests

Modify multiple records simultaneously by creating a mass change request.

• You’ve the Enable Mass Data Management permission.

1. Go to Admin Center Mass Data Management to view the overview page.

Managing Mass Changes in Employee Central

7. Choose Go to initiate a search.

8. Optional: Select  (Sort)to apply a sort criteria.

• You cannot sort by Foundation Objects and Matrix Relationship fields.

9. Select the records to modify, and choose Edit.

You can select a maximum of 1000 records at a time.

Managing Mass Changes in Employee Central

A list of all records with errors appears.

Cancellation of a mass change request leads to its automatic deletion.

Managing Mass Changes in Employee Central

• You can share multiple mass change requests.

17. Submit the mass change request for further processing.

Configuring the MassChangeJobConfiguration from Manage Data [page 6]

2.4 After Submitting a Mass Change Request

• The changes take effect on the effective date selected.

Managing Mass Changes in Employee Central

2.5 Deleting Mass Change Requests

1. Go to Admin Center Mass Data Management .

The record is permanently deleted, and cannot be retrieved.

Managing Mass Changes in Employee Central

The record is permanently deleted, and cannot be retrieved.

Managing Mass Changes in Employee Central

Mass Data Management [page 5]

3.1 Mass Changes to Job Information and Job Relationship

1. Go to Admin Center Manage Mass Changes .