3573422 - Creating and Updating Contingent Workers via OData API or Integration Center

You need to automate the process of creating and updating Contingent Workers using OData API or Integration Center.

SAP SuccessFactors HCM Suite

Prerequisite

Ensure Contingent Workers are properly set up in your instance (refer to Implementing Support for Contingent Workers in Employee Central chapter).

Instructions

First of all is important to understand that Integration Center runs based on OData API engine that, when creating/updating records, calls the Import engine, the same engine behind "Import Employee Data" and "Import and Export Data" pages. For example, when updating emails for Contingent Workers using OData API directly or Integration Center, a simple import is happening in the background.

With that understood, these are the relevant chapters when creating or updating Continent Workers:

1. Importing Contingent Worker Data;
2. Importing Work Order Data;
3. Importing Vendor Info Records;

The main differences when using OData API directly or Integration Center are:

1. Have basic understanding of the tools. The Integration Center guide (more specifically Creating Inbound Integrations chapter) and the OData API guide (more specifically Adding a New Employee chapter) provide helpful guidance.
2. Consider the technical names of entities and fields, rather than labels. They can be found in the OData API guide or OData API Data Dictionary feature.

For example, based on the Importing Contingent Worker Data chapter, in order to hire a contingent worker using OData API directly, you will need to (in order):

1. Upsert in the User entity (known as Basic User Information);
2. Upsert in the PerPersonal entity (known as Biographical Information);
3. Upsert in the EmpEmployment entity (known as Employment Details);
4. Upsert in the PerPerson entity (known as Personal Information);
5. Upsert in the WorkOrder entity (known as Work Order Information);
6. Upsert in the EmpJob entity (known as Job History);
7. Upsert in the PerEmail entity (known as Email Information);
   OBS.: Links from OData API guide included;

Using Integration Center for the example above would be tough, as due to several data validations, a job per entity may be required. In any case, there is a feature to include multiple entities in inbound integrations that consultants can try to use:

Specifics of Rehire scenarios

In order to rehire a full-time employee as a contingent worker, consider the Rehiring a Regular Employee as a Contingent Worker chapter. It is important to ensure that the User ID chosen for the new Employment record does not already exist in the system.

In order to rehire a contingent worker as a full-time employee, consider the Rehiring a Contingent Worker as a Regular Employee chapter. It is important to upsert the EmpEmployment entity with the same Person ID but with a different User ID.

Note that upserts in the User entity are not necessary, as this is created automatically after upserting the EmpEmployment entity.

Important note

For how-to, configuration or implementation issues (consulting matters), the appropriate approach is to contact your CSM/CEE (instructions in the KBA 2671448) to get informed about Professional Services or Authorized Partners (instructions in the KBA 2149831).

Integration Center, Contingent Workers, SFTP, user provisioning, SAP SuccessFactors Platform, LOD-SF-INT-INC, automate process, daily files. , KBA , LOD-SF-INT-ODATA , OData API Framework , LOD-SF-INT-INC , Integration Center , How To