3199038 - DRM: successful and pending status showing for the same employee

Image/data in this KBA is from SAP internal systems, sample data, or demo systems. Any resemblance to real data is purelycoincidental.


You wish to find out why the Data Replication Monitor is not overwriting a Pending status after a successful replication, leading to both successful and pending statuses to show for the same employee

SAP SuccessFactors Data Replication Monitor

Known Issue. This can happen in rare cases if parallel processing is performed with the same business key. In these scenarios it is safe to delete the Pending records manually from the tool. 

2891972 - Data Replication Monitor: Delete Behavior
2167526 - How to delete an entry or many entries from Data Replication Monitor in SuccessFactors system
2515724 - How to delete multiple records from Data Replication Monitor UI [1708 release feature]

delete, duplicate, pending status was not overwritten after a successful replication, both successful and pending is showing for an employee, successful and pending, successful, pending, different externalCodes, identical, replication target system, content type, parallel processing, same business key, business key, DRM, Data Replication Monitor, replication , KBA , LOD-SF-INT-DRM , Data Replication Monitor , LOD-SF-INT , Integrations , LOD-SF-INT-CE , Compound Employee API , Problem