3415719 - Integration Center job does not import all the records with Full Purge

You configure an Integration Center job with Full Purge, and import the data from a CSV file.

In the import file, there are multiple records for an externalCode (e.g. with different Start Date).

When the job completed successfully, you found one or more records of this externalCode were not imported.

SAP SuccessFactors HXM Suite

• Integration Center

1. Put all the records in the CSV file, which includes multiple records of an externalCode
2. Import the CSV file with a Full Purge Integration Center job
3. You find one or more records are not imported

Integration Center is based on OData API, and OData API can upsert at most 1000 records at a time.

When Integration Center reads the import file, it will read first 1000 records as a page and import them. Then it will read next 1000 records, and so forth.

Note: the page size can be controlled by "Source Page Size". It can be at most 1000 records per page.

This issue will occur if you put the records of an externalCode in different pages in the import file.

For example, a user has 2 records A and B. You put record A in the first 1000 records, and put record B in the next 1000 records.

When the job reads the first page, record A is imported.

When the job reads the next page, record A is deleted and record B is imported (due to Full Purge). As a result, only record B remains.

For Full Purge, you need to ensure all the records of an externalCode to be within the same page read by the job.

Or you can use Incremental Purge instead, which can also prevent such issue.

Integration Center Guide - OData Operations and Purge Types For Inbound Integrations

SF, SuccessFactors, Success Factors, configuration, Purge Type, fullpurge, External Code, missing, overwrite , KBA , LOD-SF-INT-INC-ODATA , ODATA API In Integration Center , Problem