SF EC CWM Impl
SF EC CWM Impl
5 Additional Configurations. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 45
5.1 Business Rules In Contingent Workforce Management. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 45
Setting a Business Rule for Work Order . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 46
Synchronizing Data Between Work Order and Job Information of Contingent Workers. . . . . . . . . . . . 47
Setting Up Validations for Employment Details of Contingent Workers. . . . . . . . . . . . . . . . . . . . . . . 49
5.2 Renaming the Standard Label for Contingent Workers. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 50
5.3 Check Tool for Contingent Workforce Management. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 51
8 Appendix A. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .86
8.1 Standard Reporting. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 86
Learn about changes to the documentation for Contingent Workforce Management in recent releases.
1H 2021
Added Added more information about entering Importing Contingent Worker Data [page
the correct sequence number while up 72]
dating Job History of contingent workers.
Changed Updated information regarding deleting a Deleting a Work Order [page 70]
Work Order.
1H 2021
Added Added a recommendation about creating Creating Event Reasons for Standard
only one event reason for the ECWK (End Events in Contingent Workforce Manage
Contingent Worker) event. ment [page 25]
Added Added more information about entering Importing Contingent Worker Data [page
the correct sequence number while up 72]
dating Job History of contingent workers.
Added Added more information regarding per Role-Based Permissions for Contingent
missions required to configure contingent Workforce Management [page 9]
worker event reasons.
Added Added more information about granting Adding Standard Contingent Workforce
the required permissions after importing Management Events [page 23]
the standard events and before configur
ing the event reasons.
Added Added information to highlight that a Synchronizing Data Between Work Order
business rule is not triggered when un and Job Information of Contingent Work
supported fields are modified in a Work ers [page 47]
order.
Added Added a new topic for more information Adding the Contingent Worker Type Pick
about associating the contingent worker list to the Work Order Data Object [page
picklist with the standard Work order data 36]
object.
Added Added a new topic for more information Adding the Contingent Worker Type Pick
about associating the contingent worker list to the UI [page 37]
picklist with the Work order UI.
Added Added a new topic about Centralized serv Centralized Services with Contingent
ices enabled with Job Information imports Worker Data Imports [page 78]
for contingent workers.
Added Added a note about how contingent work Rehiring as a Contingent Worker [page
ers can be rehired in instances where con 63]
current employment is enabled, and in
stances where concurrent employment is
not yet enabled.
2H 2020
November 6
We've brought several improvements to the guide this release. We've grouped related topics together, and streamlined the
structure to give you a better implementation and administration experience.
Updated the topic about hiring contin Updated the task context to highlight Hiring a Contingent Worker [page 54]
gent workers that Employment Information is now a
mandatory part of the hiring process.
October 9
Added a topic about configuring Live Pro A custom data block is now available on Adding Live Profile User Information for
file User Information for contingent work the People Profile to manage changes to Contingent Workers [page 51]
ers basic information of contingent workers.
Added a topic about configuring Work Or Customize the standard Work Order ob Configuring the Work Order Data Object
der object for contingent workers ject definition to suit your requirement. [page 32]
Added a topic about configuring a Vendor Customize the standard Vendor Info ob Configuring the Vendor Info Object [page
Info object for contingent workers. ject definition to suit your requirement. 29]
Updated the topic about importing con Added a recommended import sequence Importing Contingent Worker Data [page
tingent worker data. for rehiring contingent workers as full- 72]
time employees. Also added a note to
provide an event reason with Job Infor
mation imports while hiring or rehiring
contingent workers.
Updated the topics about hiring and re Event reason can be entered on the UI • Hiring a Contingent Worker [page
hiring contingent workers while hirring or rehiring contingent work
54]
ers.
• Rehiring a Full-Time Employee as a
Contingent Worker [page 65]
Contingent Workforce Management is one of the important features in Employee Central that's designed to give a
complete view of your contingent workforce.
Managing contingent workers is a challenging task, especially when the headcount is large. With the usual practice
of maintaining contingent worker data outside of your core HRIS system, getting your arms around this elusive
workforce to know that about their work location, assignments, trainings, supervisor details, and other related
information can be daunting.
Employee Central helps you address these concerns by enabling you to manage your contingent workforce just like
the regular employees in your company.
Contingent workers are a part of the workforce that is externally sourced, and therefore not a part of your company.
They can be freelancers or independent contractors. Contingent Workers are generally outsourced through
vendors in partnership with your company, on a contract basis.
While Employee Central helps you manage your full-time employees, Contingent Workforce Management provides
some key capabilities that enable you to perform a myriad of tasks to effectively manage contingent workers at
your company. Using Contingent Workforce Management with Employee Central enables you to:
• Create a common place for information about all employees (regular and contingent), in your company.
• Create workforce metrics and reporting, identify labor-related trends in your organization, and provide a
holistic view of labor for Executives and HR professionals.
• Extend select HR processes to contingent workers.
• Create open contingent requisitions using Position Management.
• Convert a contingent worker to a permanent employee.
• Convert an employee to a contingent worker.
• Create customized reports with or without contingent worker information, as required.
You can integrate Contingent Workforce Management with external labor and service procurement applications like
SAP Fieldglass to:
Related Information
Result/Additional In
Permission Type Permission Category Permission Name Applies To formation
Administrator Admin Center Manage Upgrade Center Administrators/Manag Enables you to access
Permissions ers the Upgrade Center
page to perform various
system upgrades.
Administrator Manage System Employee Central Administrators/Manag Allows you to enable the
Properties Feature Settings ers Contingent Workers fea
ture in Employee Cen
tral.
Administrator Manage Hires Add Contingent Worker Administrators/Manag Enables you to access
ers Admin Center Add
Contingent Worker
page to create a contin
gent worker profile as
part of the hiring proc
ess.
User Employee Data Select from the list of Administrators/Manag Allows you to View or
available fields grouped ers Edit different fields on
under different headers. the Employee Profile
page.
User Employee Central Select from the list of Administrators/Manag The selected fields are
Effective Dated Entities available fields grouped ers available on the UI when
under different headers. you hire or rehire con
tingent workers. These
fields are also required
for SAP Fieldglass inte
gration to Employee
Central.
User Employee Views Select all the options. Administrators/Manag Grants access to all the
ers data blocks on the Peo
ple Profile.
User General User • User Login Contingent Workers Enables access to the
Permission application, People Pro
• Live Profile Access
file, and Company Info.
• Company Info
Access User
Search
User Learning Select from the list of Contingent Workers Enables access to SAP
options available. Learning Management
System.
User Homepage v3 Tile Homepagev3 ToDo tile Contingent Workers Enables access to the
Group Permission group To-Do tile group on the
Home page.
• HR Information
Business Email
Address
User Employee Central • Personal Contingent Workers Grant View Current level
Effective Dated Entities Information access to these attrib
Actions utes in the Personal
Information entity.
• First Name
• Last Name
• Middle Name
User Employee Views Personal Information Contingent Workers Enables access to the
Personal Information
block on the People
Profile.
Related Information
Before beginning to implement Contingent Workforce Management, you can try out the solution in your test
instance by enabling the SAP Best Practices service.
Context
SAP Best Practices provide a set of recommended HR business configurations, designed to help customers get the
most out of their SAP SuccessFactors footprint. As an Implementation partner, you can help customers find the
configuration blocks as per their requirements. These best practices are useful when implementing the solution for
new customers. The instruction set includes an interactive process simulation, test scripts, a process flow to guide
you how the software works as standard and so on.
• Automated, free-of-cost preconfiguration that shortens time-to-value for customers, and allows a quick move
to the cloud.
• Ability to run the business process instantly for customer showcases.
• Leading Practices content based on experience and learnings from customer projects.
• Modular and flexible deployment of configuration data where you can select only the configurations required
by customers.
• Regularly updated content with new features, localization, and modules released with the SAP SuccessFactors
releases.
Procedure
1. Go to 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.
SAP Best Practices are now enabled and available as recommended upgrades in the Upgrade Center.
Next Steps
Note
To access Upgrade Center, you must have the Manage Upgrade Center permission.
Related Information
SAP Best Practices for SuccessFactors Employee Central: Administer Contingent Workforce
To configure Contingent Workforce Management in your Employee Central instance, you must perform a series of
steps in the recommended sequence.
Prerequisites
Procedure
Related Information
Set up your Employee Central instance to manage contingent workers by enabling the feature in Admin Center.
Prerequisites
Context
To enable Contingent Workforce Management and the related processes in Employee Central, you must activate
the feature.
Procedure
Next Steps
Related Information
Classify information specific to contingent workers by creating a person type in supported HRIS elements.
Context
You can configure the following HRIS elements to create a person type for contingent workers. By doing so, you can
manage the information to be made available for contingent workers in different areas of the application such as
the People Profile.
emailInfo No
emergencyContactPrimary No
employmentInfo Yes
homeAddress Yes
jobInfo Yes
jobRelationsInfo No
nationalIdCard No
personalInfo No
personInfo No
phoneInfo No
Note
• You can include countryspecific fields (standard and custom) added to an HRIS element in your
contingent worker person type configuration. You an also create a contingent worker person type
configuration for each country. However, ensure that you manage the visibility of such fields properly using
permissions. To see the most common use cases, see the Related Information section.
• By creating a contingent worker person type in homeAddress and emergencyContactPrimary HRIS
elements, you include contingent workers in employee related searches in the application.
Procedure
For more information about configuring a person type, refer to the Related Information section.
Next Steps
Related Information
Common use cases for creating a person type for contingent workers.
Go to Admin Center Manage Business Configuration page to check and verify any of the following use cases.
Enabling a Field for Employees and Disabling the Field for Contingent Workers
Prerequisite: A person type configuration for contingent workers is created in the respective HRIS element.
Example
If you want the <FTE> field in Job Information enabled for employees and disabled for contingent workers,
Disabling a Field for Employees and Enabling the Field for Contingent Workers
Prerequisite: A basic business rule is created with 'Job Information' as the base object, with logic about disabling
specific fields for employees and enabling them for contingent workers.
If you want the <cost-center> field in Job Information disabled for employees and enabled for contingent
workers,
Example
If you want to add a custom field <custom-string6> to the person type configuration for contingent workers
in Job Information.
Note
It's important that you follow the steps as mentioned, to avoid validation errors.
Enabling a Field for Employees and Disabling for Contingent Workers for One
Country/Region, but Enabling the Field for Another Country/Region
Prerequisite: Country/regionspecific configuration and person type configuration for contingent workers is
created in the respective HRIS element.
Example
If you want the <custom-date1> field in Job Information enabled for employees and disabled for contingent
workers in the USA, but enabled for all users in Germany,
1. Go to the country/regionspecific configuration for USA under Job Information HRIS element, enable the
<custom-date1> field, and save the setting.
2. Go to the person type configuration for contingent workers in USA under Job Information HRIS element,
disable the <custom-date1> field, and save the setting.
Prerequisite: Country/regionspecific configuration and person type configuration for contingent workers is
created in the respective HRIS element.
Example
If you want the <custom-string14> field in Job Information enabled for all users in the USA, but disabled only
for contingent workers in Germany,
1. Go to the country/regionspecific configuration for USA under Job Information HRIS element, enable the
<custom-string14> field, and save the setting.
2. Go to the person type configuration for contingent workers in USA under Job Information HRIS element,
enable the <custom-string14> field, and save the setting.
3. Go to the country/regionspecific configuration for Germany under Job Information HRIS element, enable
the <custom-string14> field, and save the setting.
4. Go to the person type configuration for contingent workers in Germany under Job Information HRIS
element, disable the <custom-string14> field, and save the setting.
Disabling a Field for Employees and Enabling the Field for Contingent Workers
in One Country/Region, but Disabling the Field for All Users in Another
Country/Region
Prerequisite: Country/regionspecific configuration and person type configuration for contingent workers is
created in the respective HRIS element.
Example
If you want the <custom-double8> field in Job Information disabled for employees and enabled for contingent
workers in the USA, but disabled for all users in Germany.
1. Go to the country/regionspecific configuration for USA under Job Information HRIS element, enable the
<custom-double8> field, and save the setting.
2. Go to the person type configuration for contingent workers in USA under Job Information HRIS element,
enable the <custom-double8> field, and save the setting.
3. Go to the country/regionspecific configuration for USA under Job Information HRIS element, disable the
<custom-double8> field, and save the setting.
4. Go to the country/regionspecific configuration for Germany under Job Information HRIS element, disable
the <custom-double8> field, and save the setting.
Note
It's important that you follow the steps as mentioned, to avoid validation errors.
Adding and Enabling a Custom Field Only for All Users in One Country/Region
Example
If you want the <custom-string2> field in Job Information enabled for all users in USA.
After configuring a person type for contingent workers in the required HRIS elements, the next step is to configure
the employmentInfo HRIS element to identify contingent workers.
Context
In Employee Central, different processes identify contingent workers by referring to a standard field
<IsContingentWorker>. You can add, enable, and configure the field's attributes in employmentInfo HRIS
element.
Procedure
Attribute Value
Results
You've successfully configured the Employment Information for Contingent Workers. You can use this standard field
to define business rules, create permission groups, roles, and so on, for contingent workers.
Next Steps
Ensure that this field value is set to Yes for contingent workers and No for employees in their respective profiles for
compliance purposes.
Setup permission groups specific to contingent workers in your company by creating a dynamic user group.
Context
A dynamic user group allows you to filter a group of users from the rest. Dynamic user groups are generated
automatically when the attributes of employees match the selection criteria. You can define a dynamic user group
for contingent workers from the Business Configuration UI.
Results
You have successfully created a dynamic user group for contingent workers.
Next Steps
1. Create a dynamic permission group for contingent workers from Employee Central, and SAP Fieldglass
respectively.
Note
Use the <isContingentWorker> and <Source of Record> fields to define inclusion or exclusion
criteria for contingent workers.
Related Information
Before you configure event reasons for hiring, rehiring, and terminating contingent workers, you must first add the
standard events to the source picklist by importing the required data.
Prerequisites
Your picklists are migrated to the Metadata Framework (MDF). For more information about migrating picklists,
refer to the Related Information section.
Context
1. Start Contingent Worker (SCWK), associated with hire and rehire activities.
2. End Contingent Worker (ECWK), associated with termination activities.
These events must be added as picklist values to the source Events picklist, so that you can create event reasons
out of them.
Procedure
A job is initiated.
Note
To download the exported data, go to Admin Center Monitor Job page. If your job is completed, the
Download Status link is available.
Picklist.Code event
Note
Add the event label in different languages as required.
Status A
Option ID 30766
Note
For ECWK event, enter 30765.
Min value -1
Max value -1
R Value 0
Value -1
9. Save your changes. Compress the file along with the other files into a zip file.
Results
The standard Contingent Workforce Management events are now added to the source Events picklist. To manage
picklists and their values, go to Admin Center Picklist Center .
Grant the Event Reasons permission for the standard events, before configuring event reasons.
Related Information
Event reason is a required attribute when you hire, rehire, or terminate contingent workers.
Context
After you import the standard events SCWK (Start Contingent Worker) and ECWK (End Contingent Worker) and
their translations, you must create an event reason belonging to each of these events respectively. Once created,
you can modify the configuration anytime.
Recommendation
We recommend that you create only one event reason configuration for the ECWK (End Contingent Worker)
event.
Procedure
To add a translation to the event reason name and description, select the icon next to the respective field.
5. Select an event corresponding to the event reason you’re creating.
For event reason belonging to start contingent worker event, select SCWK. For event reason belonging to end
contingent worker event, select ECWK.
Results
Configure different types of actions to take place for different contingent worker events.
Prerequisites
Context
Business rules help you set up dynamic actions such as setting visibility of fields, initializing field values, and so on,
for different contingent worker events.
Procedure
Example
If
Then
Next Steps
Assign the rule to the Job Information HRIS element from the Business Configuration UI.
Related Information
Creating Event Reasons for Standard Events in Contingent Workforce Management [page 25]
Creating Business Rules
Assigning Business Rules to HRIS Elements and Fields
Legacy Employee Central picklists have been migrated to MDF picklists. All picklists are now managed in the
Picklist Center.
For more information, refer to the Implementing Picklists guide on the SAP Help Portal.
If you’re looking for information about... See this KBA... This applies to...
Please check this KBA to keep up to date with any related issues to
picklists.
Blank error while adding new employee KBA 2197679 Employee Central
Contingent Workforce: Events with externalCode are missing in the picklist KBA 2400351 Employee Central
event
Cascading picklists not working on Job Information KBA 2458906 Employee Central
Unable to create Leave of Absence Time Types after migrating picklists to KBA 2518461 Employee Central
MDF
HRIS Sync stops working for certain mappings after MDF picklist KBA 2464855 HRIS Sync
migration
Legacy picklist externalCode is blank for Boomi integrations KBA 2116077 Integration
Fields are not mapping between Onboarding and Employee Central in KBA 2432866 Onboarding 1.0/
Emergency Contact Information Employee Central
You get the following error when accessing the Picklist Management page: KBA 2211499 Permissions
"You do not have permission to perform any Administrative or Human
Resources functions"
Mapping picklist fields in Employee Central Position Management to RCM KBA 2361220 Recruiting
Integration with OData API Management/
Employee Central
Error encountered when selecting any Recruiting or Onboarding hire in the KBA 2478250 Recruiting
Manage Pending Hires page Management/
Employee Central
Disabling the sync of non-unique external codes KBA 2824572 Employee Central
Country/region not filled out in the Job Information section when adding a KBA 2798662 Employee Central
new employee
An error occurred while the changes were being synchronized. The KBA 2800724 Employee Central
position and incumbents have not been updated
Picklist Issues: xxx is an invalid option ID for the field KBA 2997095 Employee Central
Vendors are workforce distributors entrusted with the staffing responsibilities in your company.
Each contingent worker in your company belongs to a Vendor. As part of your Contingent Workforce Program to
source and secure talent, you may have contracts established with a single vendor or multiple vendors. While
having a right team of staffing vendors is important, structuring them accordingly has equal significance.
The contingent worker hiring process regards vendor information as a mandatory requirement. You can create
vendor data manually or through data imports.
Vendor data is stored in a Metadata Framework object. You can use the data object in its default configuration or
customize it according to your requirements within the confines of the Metadata Framework.
Modify the standard data object as per your company's standards and requirements.
Context
Vendor Info is a standard data object available by default with Contingent Workforce Management. It's
preconfigured to collect only the basic and necessary vendor information. However, you can customize it just like
any other data object on Metadata Framework.
Procedure
Related Information
Context
You can create a Vendor Info record from the UI, one at a time. If you want to add multiple records, you can import
the data instead.
Procedure
Note
To add translations, select the icon next to this field.
Next Steps
Context
When you have multiple vendor info records to add, the recommended method is to import the data.
Procedure
7. On the Admin Center Import and Export Data page, select Import Data as the action to perform.
8. Select the VendorInfo generic object.
9. Attach the file prepared with data to import.
10. Import the data.
Results
A job is initiated. To monitor the job status and download a status report, go to Admin Center Monitor Job
page.
A Work Order is basically a stipulated contract established between the vendor providing the contingent workforce,
and your company.
Work order creation is an integral part of the contingent worker hiring process. When you hire contingent worker,
you also create a Work Order record. The Work Order record has start and end dates, which indicate the duration of
the contract. If the end date of the contract is reached, the contingent worker record is automatically terminated
unless the end date is extended.
You can use the Work Order object in its default configuration or customize it according to your requirement.
Modify the standard data object as per your company's standards and requirements.
Context
Work order is a standard data object available by default with Contingent Workforce Management. It's
preconfigured to collect only the basic and necessary Work order related information. However, you can customize
it just like any other data object on Metadata Framework.
Procedure
Related Information
Following is a list of fields available with the standard Work order data object.
Manage how the Work Order block appears on the contingent worker hiring wizard and the People Profile.
Context
As an Administrator, you can create and configure a UI to define the Work order block to collect and display
information as per your requirement.
Procedure
The following fields are set as required by default and this property can’t be changed.
• Start Date
• Work Order Name
• Work Order ID
• User ID
• Effective Status
• Vendor
• Effective Start Date
• End Date
5. Edit the User ID and Effective Start Date fields by hovering over the respective fields and selecting the 'pencil'
icon. Ensure that these fields are marked as not visible.
6. Save your changes.
Related Information
Define a list of values to select the type of contingent worker as part of the hiring process.
Context
If there are different types of contingent workers in your company like Profile Worker, Statement of Work (SOW),
and so on, you can create a picklist and add it to your Work order object definition. Thereafter, you can also make it
available for selection on the UI during the hiring process.
Note
If you use SAP Fieldglass integration, you must create external codes for the different contingent worker types
using SAP Fieldglass values. For more information, refer to the Related Information section.
Procedure
Adding the Contingent Worker Type Picklist to the Work Order Data Object [page 36]
Associate the contingent worker type picklist with the corresponding standard field in the Work order data
object.
Related Information
Associate the contingent worker type picklist with the corresponding standard field in the Work order data object.
Context
After creating a worker type picklist for contingent workers, you must associate it with the respective field in your
Work order data object to take effect.
Procedure
Related Information
Associate the contingent worker type picklist with the corresponding field in your Work order UI configuration.
Context
After creating a worker type picklist for contingent workers, you must associate it with the respective field in your
Work order UI configuration to take effect.
Procedure
Related Information
Adding the Contingent Worker Type Picklist to the Work Order Data Object [page 36]
Add a custom block to your People Profile configuration to display Work Order Information of contingent workers.
Context
After you’ve configured the Work Order data object and created a configurable UI, the next step is to add the UI as a
custom block to the People Profile.
Next Steps
Manage the information that can be viewed and edited by contingent workers by granting the necessary
permissions.
Related Information
Set up notifications to be sent to contingent workers for different events during the hiring or rehiring process.
Context
• When a contingent worker is hired using Add contingent worker/ Imports/ APIs.
• When a contingent worker is rehired as a contingent worker.
• When a regular employee is rehired as a contingent worker.
Procedure
Under Email Notification Templates, there are two templates available for contingent workers:
• Welcome message for contingent workers
• Contingent Workers Recruit Notification
Tip
2. Click on any template to see the standard configuration and make modifications. You can configure details to
include in email notifications sent to different users like contingent workers, supervisors, Work order owners,
and so on.
For information about the different tags available for use in the email templates, refer to the Related
Information section.
3. Save your changes.
Next Steps
Go to Admin Center Manage Data , and create a new Contingent Workers Email Notification Configuration.
Related Information
Procedure
1. In the Admin Center, go to Configure Business Rules and create a basic rule with Work Order as the base object.
2. Configure the business rule so that there is no precondition, and it always executes the Trigger Work Order
Expiration Event.
Example
4. Create and schedule a batch job of type BizX Daily Rules Processing Batch in Provisioning.
If you already have a BizX Daily Rules Processing Batch job configured, you need not do anything.
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.
Results
Note
If you've homepage V3 enabled in Provisioning, you'll see the notifications in the Notification section (under the
bell icon) instead.
Related Information
Standard tags available for use in email templates for contingent workers.
In case the tags supplied in the email template doesn't find any corresponding value for it, then the email simply
shows the tag.
PERSON_ID
SET_PASSWORD_URL
NAME
Example
External worker [[FIRST_NAME]] [[LAST_NAME]] with User ID [[USER_ID]] is added in SAP SF Employee
Central.
This user will report to [[SUPERVISOR]] and will belong to [[DEPARTMENT]] Department.
Example
Username: [[USER_NAME]]
[[SET_PASSWORD_URL]]
Currently you can only create contingent workers in Employee Central (EC). However, in non-EC systems like
Learning (LMS) and Talent there are other ways you can mark someone as a contingent worker in order to
distinguish them from regular employees.
1. In Provisoning, create an employee export job and select the checkbox Required for SuccessFactors Learning
sync and SAP Jam manual sync.
Remember
As a customer, you don't have access to Provisioning. To complete tasks in Provisioning, contact your
implementation partner. If you're no longer working with an implementation partner, contact Product
Support.
In the resulting employee export CSV file, you'll see a new column called EXTERNAL_WORKER in which contingent
workers are marked with Y.
Check whether a user record already exists while rehiring contingent workers.
Context
A default configuration to check for duplicate users is available in Employee Central. But you can create a custom
configuration by modifying the standard generic object.
By configuring a duplicate user check while rehiring contingent workers, you can:
• Review existing data from previous employment such as Personal Information, Job Information, and
Compensation Information while rehiring contingent users.
• Define an event reason used for end-dated payments feature in the Compensation block.
• Search users using national ID.
• Automatically generate user ID using rules.
Note
There can be only one configuration to check for duplicate users. If your delete or deactivate your custom
configuration, the default configuration is considered.
Procedure
Related Information
After performing the required tasks to implement Contingent Workforce Management, you can perform the
following optional configurations depending on your requirement.
Adding Live Profile User Information for Contingent Workers [page 51]
Display information typically not available on contingent workers profiles by adding a custom block to the
People Profile.
Business rules contain logic for instructing the system to carry out various operations when data is viewed,
changed or saved.
There can be many scenarios where you must manually perform certain tasks as a result of changes brought about
by a certain process. Such scenarios can include but not limited to:
Business rules bring a certain level of automation and help you manage contingent worker data in your system
much more effectively. You can customize the application the way you want, and create an instance unique to your
organization.
If you are planning to restrict the contract duration of the contingent workers, you must set up the business rule for
the work order correctly.
Context
While configuring a business rule for a work order period, you must remember to add a condition that defines the
work order period as Active.
Procedure
Select Work Order as the Base Object, and briefly describe the purpose of the rule in the Description field and
click Continue.
3. Set the If condition for the work order and define a nested If condition with the and operator where you set the
WorkOrder.Effective status as Active.
Define a Then condition to throw a warning message if the work order period exceeds the given period. For
example, when you create a work order and restrict the work order period to three months based on the
company's legal agreement, the rule cannot determine the active work order period unless you set the work
order status to active as shown in the sample screenshot:
If you do not set the condition for the work order as Active, the following error message appears when you
try to save the rule: The rule is unable to determine the active work order period. If this rule restricts the
active work order period, modify the rule to additionally set the WorkOrder.Effective Status to Active.
4. Save your changes and exit the Configure Business Rules page.
Keep common data between Work order and Job Information of contingent workers in sync using business rules.
Prerequisites
You’ve upgraded your system to support concurrent employment for contingent workers.
Context
Lets suppose you have some data that's common between the Work order and Job Information of contingent
workers. Work order updates that result in changes to common data requires to be monitored manually to update
the corresponding Job Information record so that contingent worker data is in sync. With business rules, you can
automate this process to ensure that data shared between Work order and Job Information is always consistent.
Currently, data sync between Work order and Job Information is automatically initiated when:
• You add a new Work order from the Admin Center Add Contingent Worker page.
• You modify an existing work order from the People Profile, Manager Self-Service UI, or Data Imports (from UI or
API).
Procedure
1. On the Admin Center Configure Business Rules page, click (Create New Rule) to create a business
rule.
2. Under Contingent Workforce rule scenario category, select Synchronize Work Order Changes to Job Information
rule scenario.
3. Configure the business rule as per your requirement.
Keep the If condition in the rule to be always true, and use input parameters from Work Order and Job
Information data objects only. The following fields are not available for sync in Job Information data object.
Sample Code
Note
Ensure that Job Information is the target object and Work Order is the source object in your rule.
Results
You’ve successfully created a business rule to sync data between work order to job information, whenever you add
a new work order or edit an existing work order.
Note
• Editing Work orders already existing in the system before upgrading your system to support concurrent
employment for contingent workers.
• Editing Work orders to modify field values that are not available for sync.
Next Steps
Go to Admin Center Company System and Logo Settings , select the business rule from the Rule for
Synchronizing Work Order to Job Information dropdown, and save the changes.
Related Information
Using business rules, you can set up validations to help prevent you from creating incorrect employment details
while hiring contingent workers in your company.
Prerequisites
Create a custom field in the EmploymentInfo HRIS element from the Business Configuration UI to store and display
the alert message. It's because the business rule is executed onView where the 'Raise Message' feature isn’t
supported.
Context
While creating a new contingent worker profile, you enter a hire date, a Work order start date, a termination date
and a Work Order end date. Since it's required that the termination date and the Work order end date of contingent
workers must be the same, you can create a business rule configuration to alert whenever there’s a date mismatch.
Procedure
Next Steps
Go to the Manage Business Configuration page and attach the business rule in the EmploymentInfo Triggers
section with the following details:
Change the default label that appears on the Org Chart and People Profile to something suitable for contingent
workers in your company.
Prerequisites
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.
Procedure
The custom language pack gets appended to the selected language pack.
5. Select Action Download default labels against the original language pack.
Note
You don't need to copy the entire original file, only the keys and labels you want to customize. In this case,
the Contingent Workers label.
7. Enter the new label in the ECT_CONTINGENT_WORKER key and save the CSV file.
Note
The new label appears in the People Profile and Org Chart. If you want to change the name in the People
Search as well, ensure to rename the COMMON_Contingent_Worker key in the CSV file too.
Results
The standard contingent worker label is updated and will reflect in the respective pages the next time you log in to
the application.
Check tool is a feature that identifies and highlights potential issues with your application along with viable
solutions to help you resolve them by yourself.
As an Administrator, you can use the check tool to identify configuration or data issues and take corrective actions
to rectify them by yourself, thereby eliminating the need to create a support ticket and save the time and effort
involved. For more information about how to use the check tool, refer to the Related Information section.
Related Information
Display information typically not available on contingent workers profiles by adding a custom block to the People
Profile.
Context
In Employee Central, there's limited information shown for contingent workers on the People Profile, which implies
that you can only view and edit information that's available. To modify other details, you must import the required
data using different methods such as OData APIs or Employee Central Imports.
For quick and efficient data management, you can now customize the People Profile to display information that is
otherwise not visible on contingent worker profiles.
Procedure
The fields appear in the order of your selection. To reorder, drag the field with the corresponding (Sort) icon
selected.
5. Save the changes.
Results
People Profile UI is now configured with the Live Profile User Information custom block. You can view and modify
information in the custom block directly from the contingent workers profile.
• You can modify details associated with active, inactive, or terminated contingent workers. Ensure that the
information is unique.
• For contingent workers with concurrent employment, you can modify details associated with each
employment. Ensure that the information is unique for each employment.
Next Steps
Manage who can view and/or edit the different fields added to the custom block by granting Employee Data
permission.
Related Information
Prerequisites
Procedure
Note
If contingent workers are hidden on the Company Organization Chart, the total number of direct reports of
a manager doesn’t include the contingent workers.
Results
You have successfully hidden contingent workers from the Company Organization Chart.
Learn about how you can configure different processes to manage contingent workers in your company.
Some of the important processes involved in contingent workforce management include, but not limited to:
Add contingent worker details in Employee Central by creating a new profile as a part of the hiring process.
Context
Hiring contingent workers is simplified with the help of a guided step-by-step approach, similar to the hiring
process for regular employees. To create a contingent worker profile, you must provide necessary details like
Identity Information, Work Order information, and so on. Adding Employment Information is also a mandatory.
Employee Central provides a standard UI for hiring contingent workers, which is currently not customizable.
This topic covers the process of hiring contingent workers, one at a time. If you want to hire many contingent
workers, you can opt to import the data instead. For more information about importing contingent worker data,
refer to the Related Information section.
Procedure
The Identity Information of contingent workers includes details such as the Recruit Date, Company, Event
Reason, Name Information, Employee Information, and so on.
Note
The Personal Information of contingent workers includes details such as the Email Information, Phone
Information, Addresses, Primary Emergency Contact, and so on.
The Contingent Worker Assignment Information includes details such as the Target Position, Organizational
Information, Job Information, Employment Details, and so on.
Billing Amount The total billing amount based on currency and billing rate
type.
Example
Billing Amount: 15.00
Currency: US Dollar
Worker Type Select one of three worker types from the dropdown:
• Contingent Worker
• SOW Worker
• Profile Worker
Caution
If you haven't integrated your Employee Central in
stance with SAP Fieldglass, these values may not ap
pear. If such cases, you can create a picklist to maintain
worker type options. For more information about creat
ing picklists, refer to the Related Information section.
Work Order Owner Enter the person responsible for the Work orders. This per
son can be a Procurement Specialist, Supervisor, or a Man
ager.
Note
The start date of the Work order is propagated from the start date entered in the Identity Information
section.
Related Information
You can flexibly configure the hiring process to cater to different needs for your workforce. You can create effective
dated templates for specific hiring scenarios, for example, for seasonal workers, interns, or full-time employees.
To simplify the hiring process, you can create templates with only the blocks needed for the type of employment
you are hiring for. The template allows you to add standard and custom MDF objects to the configuration. Custom
MDF objects allow you to customize the template by adding fields, for example, to record uniform or shoe sizes.
The template is a collection of pages, where each page is a collection of HRIS elements and/or userdefined
configuration UIs. The configuration UIs are not pre-delivered - you need to define them yourself.
You can define the order of the objects and even remove some entities that aren't required for the template. The
template can hold only a maximum of 30 standard and custom MDF objects and Employee Central HRIS elements
- in total - contained between 2 and 10 pages. One-page templates are not allowed by the system.
Once a template is created, you can have set the status to active or inactive, as needed. You can also delete
templates if they are no longer necessary. However, a template cannot be deleted if the hiring process, saved
drafts, or workflow associated to it is not complete.
Configure the hire template to have a flexible configuration that meets your specific hiring needs.
Prerequisites
• You have all permissions for the Hire Template MDF object found in Manage Permission Roles
Administrator Permissions Manage Business Configuration Hire Template .
• You have standard MDF permissions as well as edit permissions for all custom MDF objects used in the
template.
If you’ve configured the MDF object in the template and the user who accesses the template doesn’t have
permission to that MDF object, they won’t see that MDF object when using the template.
• You've created the custom Hire Template MDF objects.
• The template allows you to add standard and custom MDF objects to the configuration. You can define the
order of the objects and even remove some entities that aren't required for the template. The template can
hold only a maximum of 30 MDF objects and Employee Central HRIS elements - in total - in between 2 through
10 pages. You can only select HRIS elements that are configured in the data model.
Note
If you use the Payment Information object, you must also have configured the Personal Information Screen
Lookup object.
• You have the Admin Center Manage Permission Roles Manage Hires Manage Hire Configuration
Templates permission either for all templates or a selection of them.
Once templates are created in the Admin Center Manage Data Create New Hire Template page,
they’re automatically added to a list, where access to those templates must be granted. If access is granted for
all templates, the permission applies to all existing templates as well as for any templates created in the future.
If the Manage Hire Configuration Templates permission is granted, then by default, you have permission for the
Permission for Standard Hire Template, which is the existing hire configuration in the instance.
This is a view permission, only for the existing hiring configuration in the instance. There is no physical
template and hence this standard template is not editable.
We recommend that super admins have permission for all templates, whereas HR admins and hiring
managers only have access/permission to specific templates.
Note
Context
The template allows you to add standard and custom MDF objects to the configuration. The template only supports
user-based MDF objects that have Configuration UIs assigned to them. A user-based MDF object means that the
external code of the MDF object is set to Data Type = User. Examples of user-based MDF objects include Payment
Information, Deductions, as well as custom MDF objects.
The template must include Name Information, Personal Information, Biographical Information, Job Information,
and Employment Information. Add MDF objects as needed in new sections.
Identity always remains the first section, but MDF object sections can be arranged to follow. Personal Information
and Global Information are shown together. Similarly, in Employment Information, Compensation Information,
Recurring Pay Component, and Non-Recurring Pay Component Information are shown together.
You can add, remove, and reorder the new hire standard blocks, such as to exclude Dependents or Global
Information.
You can add, remove, and reorder standard MDF objects, such as Payment Information.
Procedure
We do not recommend that you add custom fields to this object. Custom fields should only be added in custom
MDF objects.
Note
Each HRIS element can only be used once in each template. For example, you can't add Pay
Component Non-Recurring twice.
Note
When configuring a hire template for contingent workers, only the Employee Central HRIS elements
applicable for person type Contingent Worker and the WorkOrder MDF object are supported.
Note
Remember that each step can contain a maximum of 10 blocks. The total number of blocks for the entire
template is 30.
Since each template has a name and an ID, it makes it easier to find later in the list.
Note
For saved drafts of templates where you receive an error message that it’s invalid, you can correct the
template configuration to make the template valid again. This happens when an object definition or config
UI is removed from the configuration pages used.
Once the template is created, it appears in the Manage Data list of Hire Templates. By default, the templates are
displayed alphabetically by template name. You can edit and delete templates from this list. A template can’t be
deleted if the hiring process or workflow associated to it isn't complete. It’s also possible to set a template to
inactive, although it stills appear in the list of templates shown in Admin Center Manage Permission Roles
Manage Hires Manage Hire Configuration Templates .
Next Steps
Once the template is created, the list of templates in the Manage Hires is updated so that you can assign
permissions for that specific template to a person or group to use it. If cases where that list isn’t automatically
updated, ask the system admin to check the RBP Refresh background job for the RBP list.
Context
You can change contingent worker details such as the Personal Information, Work Order information, and so on,
directly from the UI by accessing their file. If there are multiple contingent worker records to modify, you can import
the data instead. For more information about importing contingent worker data, refer to the Related Information
section.
Procedure
1. Log in to the application and search for the respective contingent worker profile.
2. Select the icon corresponding to a data block to make the required changes.
Alternatively, you can select the Actions menu to edit specific details such as Work Order Information,
Organization Information and so on. There’s another method to edit Work Order information by selecting the
(Work Order History).
If you edit the Work Order dates (Start Date or End Date), the system automatically synchronizes
corresponding Job and Employment Information.
3. Save the changes.
End the stipulated contract between the contingent worker and your company.
Context
Although the Work order end date to terminate a contingent worker is automatically calculated during the hiring
process, you can choose a different date as necessary. This topic covers the process of changing the Work order
end date from the People Profile.
However, if there are multiple Work orders to process, you can import the data in bulk. For more information about
importing Work order data, refer to the Related Information section.
Procedure
1. Log in to the application and search for the respective contingent worker profile.
2. Go to the Work Order section, and select (Edit Work Order)
You can also edit the Work order information by selecting the respective option from the Actions menu.
3. Choose an End Date.
4. Save the changes.
Results
Next Steps
Check if the contingent worker has any direct reporters, and plan to reassign them to a different user.
Create a configuration to check if a terminated contingent worker has any direct reports, and reassign them
accordingly.
Prerequisites
You have created a job request type BizX Daily Rules Processing Batch 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.
Context
The process of reassigning users directly reporting to an inactive contingent worker is governed by a batch
processing job. During its first run, it looks for contingent worker records inactive from the day before the current
date. The job can fetch data from a maximum of 30 days prior to the current date.
If there are backdated terminations of contingent workers within a period of 30 days, the job gathers this data and
reassigns the managers of the direct reports.
Example
Lets suppose the job runs successfully on January 1. If it runs again on March 1, it will fetch the records of any
contingent workers that have been inactive since January 30 (that is, 30 days prior to March 1). Any inactive
records from between January 1 to January 29 aren’t fetched, since these fall outside of the 30 day period.
As such, you must ensure the BizX Daily Rules Processing Batch job is properly scheduled.
Note
If you've configured a workflow on Work Orders or Job Information objects to update the work order's end date
to a past date, such records aren't fetched. Contingent worker records with work order end dates in the future
are also not fetched.
Results
The BizX Daily Rules Processing Batch is now configured to monitor inactive contingent workers, and automatically
reassign their direct reports to a new manager. Direct reports of an inactive contingent worker who doesn’t have a
manager are updated with the status NO_MANAGER.
Related Information
Rehire a person who has previously worked at your company, as a contingent worker.
Context
If a person who worked as a contingent worker at your company qualifies for a new contingent worker role, you can
rehire them in Employee Central. A contingent worker whose Work Order is expired is considerable for rehiring as
well.
To rehire a contingent worker whose Work Order is expired, you must add a new Work Order.
Note
If concurrent employment is supported for contingent workers, you can rehire a contingent worker on a new
employment only.
If concurrent employment isn’t supported for contingent workers, you can rehire a contingent worker on their
existing employment only.
You also have the option to import contingent worker data if there are many contingent workers to rehire. For more
information, refer to the Related Information section.
Note
A popup dialog box appears notifying that an employee record matching the Identity Information already exists
in the system, along with an option to accept the match.
4. Select Accept Match and continue.
Results
If successful, the contingent worker is rehired on a new Work Order. You can verify the new Work Order details on
the contingent worker's profile.
Related Information
Rehire a person who was a contingent worker at your company, as a full-time employee.
Context
If a person who worked as a contingent worker at your company applies for the role of a full-time employee, you can
rehire them provided the required criteria is met.
Note
A popup dialog box appears notifying that an employee record matching the Identity Information already exists
in the system, along with an option to accept the match.
4. Select Accept Match and continue.
Another popup dialog box appears notifying that the existing record belongs to a contingent worker, along with
an option to hire as a regular employee.
5. Select Yes to hire the applicant as a regular employee.
6. Complete the hiring process by adding Personal Information, Job Information, and Compensation Information.
Results
Related Information
Rehire a person who was a full-time employee at your company, as a contingent worker.
Context
If a person who worked as a regular employee at your company is to be staffed as a contingent worker, you can
rehire them provided the required criteria is met.
This topic covers the process of rehiring a regular employee as a contingent worker, one request at a time. If there
are multiple persons to rehire, you can bulk import the data. For more information, refer to the Related Information
section.
Note
A popup dialog box appears notifying that an employee record matching the Identity Information already exists
in the system, along with an option to accept the match.
4. Select Accept Match and continue.
Another popup dialog box appears notifying that the existing record belongs to a regular employee, along with
an option to hire as a contingent worker.
5. Select Yes to hire the applicant as a contingent worker.
6. Complete the hiring process by adding Personal Information, Contingent Worker Assignment Information, and
Work Order Information.
Results
Related Information
Rehire an inactive contingent worker or assign an effective dated contract to an active contingent worker by adding
a new Work Order.
Prerequisites
You have not yet upgraded your system to support concurrent employment for contingent workers.
Context
The process of adding a new Work Order varies depending on whether concurrent employment for contingent
workers is supported in your system or not. This topic covers the process of adding a new Work Order when
concurrent employment for contingent workers isn’t supported. For information about adding a new Work Order
(Assignment) when concurrent employment for contingent workers is supported, refer to the Related Information
section.
When concurrent employment for contingent workers isn’t supported, a contingent worker can’t have multiple
active Work Orders. But you can still add a new Work Order that is effectivedated (a start date in the future), which
means it will become active after the currently active Work Order ends.
There are three methods to add a new Work Order in Employee Central.
Recommendation
We recommend using the Add Contingent Worker wizard to add a new Work order and avoid manual adjustment
of Job Information. You can also import data to add multiple Work orders. For more information, refer to the
Related Information section.
But if you want to add a new Work Order from the People Profile instead, follow the guidelines mentioned in this
topic.
Procedure
The status must be Active if you’re rehiring an inactive contingent worker. But if you’re adding an effective
dated Work order, the status must be Inactive.
5. Select a Vendor from the dropdown.
If the desired vendor isn’t available in the dropdown, you can add a vendor by selecting (Add Vendor) and
providing the required vendor information.
6. Enter the End Date.
7. Save your changes.
Results
You’ve successfully added a new Work Order to the selected contingent worker profile.
Next Steps
Add Job Information associated with the new Work Order. You can either import the Job Information or add it on
the contingent worker profile manually.
Related Information
Prerequisites
You’ve upgraded your system to support concurrent employment for contingent workers.
Adding a new assignment implies creating concurrent employment for contingent workers where they can have
multiple active Work Orders each of which is a separate employment. Adding a new assignment to a contingent
worker having an active Work Order also qualifies as a case of rehiring a contingent worker.
Recommendation
We recommend adding a new Work order using the Add Contingent Worker page.
For adding multiple Work orders, you can choose to import the data. For more information, refer to the Related
Information section.
Procedure
Results
You’ve successfully added a new assignment and created a concurrent employment for a contingent worker.
Related Information
Permanently remove Work Order related information of contingent workers from the system.
Context
You can delete a Work Order in an upgraded instance that supports Concurrent Employment for contingent
workers, then the contingent worker isn't soft deleted from the system and only the following data is deleted, after
you delete the Work Order:
• Work Order
• Job History
• Job Relationships
To reuse the existing employment after Work Order deletion for a new Work Order, you can use CSV Imports for the
new Work Order against the existing User ID.
Caution
• In case you want to purge a contingent worker from your system then you don’t need to delete the Work
Order. It’s recommended that you use DRTM Master Data Purge tool to purge the contingent worker's data
and, then manually delete the records in any integrated downstream systems.
• In case you want to update any of the attributes of an existing Work Order including the start and end dates,
then you do not require to delete the current Work Order and create a new one. You should edit the existing
Work Order from Take Action Edit Work Order .
There are two methods to delete Work Order related information of contingent workers.
This topic covers the process of deleting Work Order related information from the Manage Data page. For
information about deleting Work Order information from the People Profile, refer to the Related Information
section.
Procedure
Results
Related Information
Permanently remove Work Order related information of contingent workers from the system.
Context
You can delete Work Order related information of a contingent worker directly from their profile.
Procedure
1. Log into the application and search for the contingent worker whose Work Order you want to delete.
2. In the Employee Profile, go to the Work Order section and select (Work Order: History)
3. Select the required timeslice from the list shown on the left side of the popup window.
4. Select Delete and confirm your action.
Results
Hire, Rehire, or create concurrent employments for multiple contingent workers by importing data.
Prerequisites
You've reviewed the configuration of the different HRIS entities involved in the data import process, 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
Data Import is a convenient and recommended approach for hiring or rehiring a large number of contingent
workers. This method is also applicable for adding or updating contingent worker data.
Update Contingent Worker Details. <The required entity> • If you update the Work Order dates,
the corresponding Job History and
Employment Information records
are automatically synchronized.
• If you’re updating Job History in
Incremental Load mode, ensure that
you provide the correct sequence
number of the record you want to
update. This check prevents any val
idation errors during imports.
Example
Importing Job History for a con
tingent worker with an SCWK
event reason, with an incorrect
sequence number or without a
sequence number, results in a
validation error.
Rehire a contingent worker as a full-time 1. Employment Details • Enter the same Person ID but a dif
employee. 2. Job History ferent user ID in the Employment
Update contingent worker Details. <The required entity> • If you update the Work Order dates,
the corresponding Job History and
Employment Information records
are automatically synchronized.
• If you’re updating Job History in
Incremental Load mode, ensure that
you provide the correct sequence
number of the record you want to
update. This check prevents any val
idation errors during imports.
Example
Importing Job History for a con
tingent worker with an SCWK
event reason, with an incorrect
sequence number or without a
sequence number, results in a
validation error.
Rehire as a contingent worker. 1. Work order Information • Enter an event reason belonging to
2. Job History the SCWK event in the Job History
Rehire full-time employee as a contingent • Employment details • Enter an event reason belonging to
worker. the SCWK event in the Job History
• Work order Information
import template.
• Job History
• Enter the same Person ID but a dif
• (Optional) Other Information as nec ferent user ID in the Employment
essary Details import template.
• Verify that the value in the
isContingentWorker column is set to
Yes in the Employment Details im
port template.
Add a new Work Order. • Work order Information • Enter an event reason belonging to
the SCWK event in the Job History
• Job History
import template.
• (Optional) Other Information as nec
essary
• Ensure to import Employment De
tails with the same Person ID, and
user ID.
Rehire a contingent worker as a full-time 1. Employment Details • Enter the same Person ID but a dif
employee. 2. Job History ferent user ID in the Employment
Procedure
Recommendation
It's recommended that you download the latest version of the import file template from the server.
Tip
Related Information
Context
When you want to add or update a large number of Work Orders, importing the data is the recommended approach
to save time and effort.
Note
Procedure
1. To download the import template, go to Admin Center Import and Export Data .
2. Select Download Template as the action to perform.
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.
Hide External Code - visible only when Key Preference is set Select one of the following:
to Business Key. • Yes
• No (default value)
• CSV File, if you’ve downloaded the template excluding dependencies. Fill the form by referring to the
following table:
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.
• ZIP File, if you’ve downloaded the template including related dependencies. Attach the file to upload.
To check the import status, go to Admin Center Monitor Job . If the job is completed, a clickable link
Download Status is available against your job request.
Note
After the import is successful, data changes reflect in Employee Central immediately, but will appear in
user profiles only after the HRIS sync job is executed.
Next Steps
Related Information
Centralized services bring process and security-related enhancements to contingent worker data imports.
With 1H 2021, Centralized services are enabled by default with Job Information data imports for contingent
workers. They’re applicable irrespective of whether you’ve upgraded to support concurrent employment for
contingent workers or not.
Given the requirement, you can choose to opt out using Centralized services by deselecting the Enable Centralized
Services for Job Information switch on the Company System and Logo Settings page. For more information about
Centralized services, refer to the Related Information section.
Set up and manage concurrent employments for contingent workers at your company.
Context
Concurrent employment is when a person in your company has multiple employments at the same time.
Concurrent employment for contingent workers is available as an optional upgrade in Employee Central.
Note
S/4HANA doesn’t support overlapping (concurrent) employments for contingent workers. So, if you’re an
existing customer requiring contingent worker data within your S/4HANA instance, you must not create
overlapping Work orders.
Procedure
2. Select Learn More & Upgrade Now under Important Upgrades Concurrent Employment for Contingent
Workers .
3. Select Upgrade Now.
Remember
Results
Note
Related Information
Forward propagation implies that changes in field values of an object are cascaded or “propagated” to future dated
records of the same object.
Your system can automatically calculate and update effective dated employee records when you add a new record.
This tendency of forward propagation of data continues until the system finds a future dated record with a value
different than the value being propagated.
Currently, forward propagation of data happens only when you modify the following data:
• Work order
• Job Information
Note
Business rules aren’t triggered when data is changed as a result of forward propagation.
Prerequisites
Ensure that your system supports concurrent employment for contingent workers.
Forward data propagation takes place when you modify the active Work order of contingent workers from their
Employee Profiles or data imports (from UI or API). Data is propagated to the corresponding inactive Work order.
Forward propagation of data works only when you modify the following fields in the Work order data object.
• Billing Amount
• Billing Rate
• Currency
• Worker Type
• Work order Name
• Work order Owner
• Vendor
Forward Propagation with Concurrent employment not supported for contingent workers
Example
Example
Scenario 1: Lets suppose a contingent worker has two active Work orders and two inactive Work orders in the
following sequence.
In this case, if you modify any active Work order record, changes are propagated to the subsequent inactive
Work order record.
Scenario 2: Lets suppose a contingent worker has two active Work orders and one inactive Work order.
In this case, if you modify the active record for Work order 2, changes are propagated to the subsequent
inactive record for Work order 2.
Data changes, including date values, made on the UI or via data imports (from UI and API) are propagated until the
next End Contingent Worker (ECWK) event record in Job Info. The changes do not propagate to the next set of Start
Contingent Worker (SCWK) or ECWK event records in Job Info when there are multiple work orders.
Example
Example
1. If you add a new Job Information record through the Employee Profile by selecting the (Edit Job
Information), forward propagation works like it does for regular employees in Employee Central. For
information about how forward propagation works for regular employees, refer to the Related Information
section.
2. Suppose that a contingent worker has three records in their Job History like 'Start Contingent Worker
(SCWK)', 'Data Change', and 'End Contingent Worker (ECWK)'. Forward propagation works only when you
modify the Data Change record, where changes are propagated to the ECWK record.
3. Suppose that a contingent worker has four records in their Job History like 'Start Contingent Worker
(SCWK)', 'Data Change 1', 'Data Change 2', and 'End Contingent Worker (ECWK)'. Forward propagation
works only when you modify the 'Data Change 2' record, where changes are propagated to the 'End
Contingent Worker (ECWK)' record.
Related Information
Context
The contingent worker data that is created and maintained in the system by your existing process will be
incompatible with the new contingent workforce management feature in Employee Central. To ensure compatibility,
you must:
Note
After rehiring, you must create a new work order, add the job information with their new employment, and
update their employment information.
Results
Next Steps
Rehire the terminated contingent workers with a new employment and create a new work order accordingly.
Related Information
Learn how you can keep the personal data of your employees secure and private with SAP SuccessFactors.
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 HXM 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 customer’s responsibility to
evaluate legal requirements and implement, configure and use the features provided by SAP SuccessFactors in
compliance with all applicable regulations.
Related Information
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 its limitations.
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 HXM 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.
Related Information
You can use the Contingent Worker Register advanced report to analyze your total workforce in Employee Central.
For more information on reporting, see the Advanced Reporting guides on the SAP Help Portal, SAP
SuccessFactors Employee Central Reference .
Hyperlinks
Some links are classified by an icon and/or a mouseover text. These links provide additional information.
About the icons:
• Links with the icon : You are entering a Web site that is not hosted by SAP. By using such links, you agree (unless expressly stated otherwise in your agreements
with SAP) to this:
• The content of the linked-to site is not SAP documentation. You may not infer any product claims against SAP based on this information.
• SAP does not agree or disagree with the content on the linked-to site, nor does SAP warrant the availability and correctness. SAP shall not be liable for any
damages caused by the use of such content unless damages have been caused by SAP's gross negligence or willful misconduct.
• Links with the icon : You are leaving the documentation for that particular SAP product or service and are entering a SAP-hosted Web site. By using such links, you
agree that (unless expressly stated otherwise in your agreements with SAP) you may not infer any product claims against SAP based on this information.
Example Code
Any software coding and/or code snippets are examples. They are not for productive use. The example code is only intended to better explain and visualize the syntax and
phrasing rules. SAP does not warrant the correctness and completeness of the example code. SAP shall not be liable for errors or damages caused by the use of example
code unless damages have been caused by SAP's gross negligence or willful misconduct.
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.
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.