SuccessFactors to SuccessFactors Integration - Batch

[PB2]

SAP SuccessFactors is a HCM system cloud-based application, which contains employee records.

• New Hire records
• Data change/Modified
• Termination records

Every Organizations use SAP SuccessFactors to manage various aspects.

• HR operations
• Recruitment
• payroll
• Learning activities and performances
  

CPI Can connect to SuccessFactors through OData Adapter and SF Adapter.

Connectivity:

• OData Adapter – OData V2, OData V4
• SuccessFactors Adapter - OData V2, OData V4, REST, SOAP

OData V2 Configuration:

SuccessFactors OData V2 Configuration

SuccessFactors SOAP Configuration

Querying the SF: We can use the Compound Employee and Employee Central. 
Compound employee Query to fetch all the details from SF and below is the query as an example for specific country.
Query compound employee - (PersonInfo, AddressInfo, employment_information etc).

Employee central – Sepcific fields from each entity(PerPersonal, EmpJob, EmpEmployment, EmpComp, PayComprecurring)

Integration Modes :

• Full load – To fetch complete historical employee records and process to SF system.
• Delta load – Based on daily changes . Integration will process the change/modified records.

                          -  Lastmodified date field.
                          - Lastmodified date field & resultOptions=allJobChangesPerDay.

Employee record types in SF :

• Backed dated Records
  - Expression – Fromdate = 1900-01-01

• Current dated Records
  - Based on the Lastmodified date field / Write variable (which stores the LSRD)

• Future dated Records
  - Expression  - todate = 9999-01-01
  
  

SF to SF - Batch integration
----------------------------------------
Usually, an employee can be created in SF with only Personal information or only Job information etc. as a minimal number of fields. This can be achieved to process with individual APIs. This looks as a partial profile crated in SF.

To avoid this, we have new feature which helps to create the employees at a time with multiple portlets. 

We need to follow specific format to achieve this and Employee profile only creates when batch process is success. 

Processing data as a batch to SF:

• User details
• Biographical info
• Per personal Info
• Job info
• Employment Info

Request Payload:

Employee records to be followed in the below specific format to as a request payload to SF Receiver adapter. 

Batch Process configuration:

Resource path – Any resource path can be selected but SF will check only the fields which are processing when we enable the batch processing. Please follow as below. 

Response Payload:
Success: Response payload looks as below when its success.

Error: Response payload looks as below when its fails.

Advantages
----------------
1. Employee profile will only create when batch process is success. So, no partial employee profile will be created.

2. It reduces the performance issues and manual efforts.

Helpful Links:
https://community.sap.com/t5/technology-blogs-by-sap/batch-operation-in-odata-v2-adapter-in-sap-clou...

2649826 - Query Parameters for the CompoundEmployee API Entity

2649816 - CompoundEmployee API Delta Transmission - SAP for Me

Let me know if you see any issues.

All the Best!