Symptom
- Unexpected data is replicated in ECP due to the following situations:
- 'Rehire with Old Employment' feature has been enabled.
- If the rehire date is in the past, the employee is already active even before the MPH is completed.
- The same is also available through API even before the completion of MPH.
Environment
SAP SuccessFactors Onboarding
Cause
- Whether onboarding data is replicated to ECP is determined by the “Hiring Not Completed” flag in Table_EMP_EMPLOYMENT_INFO; if the flag is False, the record is fetched for replication.
- For Rehire with Old Employment (ROOE), once hiring is complete, the “Hiring Not Completed” flag is never reset to True; this is standard system logic.
Resolution
- Check the “Hiring Not Completed” flag in Table_EMP_EMPLOYMENT_INFO for the rehire record.
- If the flag value is False, the employment is considered complete for replication and the record will be fetched by replication.
- For rehire with old employment (ROOE), note that this flag will not be set back to True after completion of the rehire step; this behavior is by design. So, it is impossible to stop the replication. Refer to KBA: 3426482 - HiringNotCompleted flag for rehire with old employment (ROOE) - Onboarding
- There is no API to distinguish whether MPH is complete when rehired.
See Also
Keywords
rehire with old employment, ROOE, hiring not completed flag, EMP_EMPLOYMENT_INFO, MPH, manage pending hires, Rehire, payroll replication, replication before mph, identify rehire without mph, ECP, API availability, data replication control, employment info flag, integration , KBA , LOD-SF-OBX-EC , Integration EC - MPH, Hire , Problem
Product
SAP SuccessFactors Onboarding all versions
SAP Knowledge Base Article - Public