Symptom
- This article covers information on how to manage Imports and API upserts when HRIS Sync is involved
- We import/upsert EC data, and when we do, this triggers the HRIS Sync job to run against the data in the import/upsert, but if we run the import/upsert back to back, sometimes the HRIS Sync job has not finished running from the first import/upsert, which causes the HRIS Sync job to fail for the other imports/upserts (as only 1 HRIS Sync job can run at a time). What do we do to avoid this?
- We carry out a "Delete" operation to remove an EC record, but the removal of the record, does not trigger a sync of the new active record (Import & API).
Image/data in this KBA is from SAP internal systems, sample data, or demo systems. Any resemblance to real data is purely coincidental.
Read more...
Environment
- SAP SuccessFactors Employee Central, SAP SuccessFactors HCM Suite
Product
SAP SuccessFactors HCM Core all versions
Keywords
ECT-74662, API, Import, Delete Operation, HRIS Sync , KBA , sf employee central , LOD-SF-EC-HRS , HRIS Sync , LOD-SF-EC-EDP-BIO , Biographical Information Import , How To
About this page
This is a preview of a SAP Knowledge Base Article. Click more to access the full version on SAP for Me (Login required).Search for additional results
Visit SAP Support Portal's SAP Notes and KBA Search.