Symptom
- When refreshing SuccessFactors instance, the OIDs are changed for workforce persons in SuccessFactors. If you don't reset data in MDI, it would contain the same employee twice in the future (OID1 and OID2 for same person).
- This would lead to data issues in S/4 most likely.
- Therefore resetting data in MDI is the preferred solution.
Environment
- SAP SuccessFactors HXM Suite
Reproducing the Issue
- You have completed SuccessFactors Instance refresh
- You would like to know the best approach to reset MDI data replication
Cause
- You need to stop MDI data replication during SuccessFactors instance refresh to prevent unintended data flow.
Resolution
-
Independently refresh each provider and consumer system (for example, Production to Quality) using the appropriate system tools, such as the S/4HANA Public Cloud refresh tool.
-
Re-enable integrations once the refresh is complete.
-
Resend data from each provider to MDI in the recommended sequence (for example, cost centers, company codes, then workforce data).
-
Perform an initial load and migration to MDI on both SAP SuccessFactors and S/4HANA to ensure all references are updated using Object IDs (OIDs).
See Also
You can find more information in our MDI guide on this link
Keywords
MDI, post refresh, activities, steps after refresh, recommended approach post refresh, successfactors instance refresh, data replication , KBA , LOD-SF-INT-MDI , OneMDI Business Scenarios , LOD-SF-INT , Integrations , LOD-SF-INT-CE , Compound Employee API , Problem
SAP Knowledge Base Article - Public