3393967 - Employee fails with ERROR: Data for employee have been purged. Replication not possible.

You are triggering the replication for and employee from SuccessFactors to HCM and in Data Replication Monitor (DRM) and SLG1 you can see the error message saying that:

Data for employee have been purged. Replication not possible.

• SuccessFactors - Employee Central
• BIB Replication

1. go run the program ECPAO_EE_ORG_REPL_QUERY
2. select the employee whom you can reproduce the issue
3. observe the logs in SLG1
4. notice the error

In SuccessFactors you have implemented Data Retention Time Management DRTM and selected a purge period that happens after the FTSD that you have configured in HCM.

As a result, when the query to fetch the data hits SFSF, the parameter validateEffectiveEndDateFilter will return an error if for the given employee you already have a purged entity not allowing the replication to happen.

This behavior is explained in the below session of the implementation guide:

Enabling Validation Against Effective End Date Filter

To resolve this issue, you need to check the option Use Purge Status Overview for Data Purge in your query configuration.

This can be done following the implementation guide session below:

Configuring the Parameters for the Employee Master Data and Organizational Assignment Query

Once you enable this option, the ERP system will use the DRTMPurgeStatusOverview segment of the Compound Employee API.

This segment provides detailed purge dates and Using the purge status overview enables the ERP system to replicate employees whose data was partially purged, even if the purge date is after the full transmission start date (FTSD).

NOTE: In order to view this parameter to select your PA_SE_IN must be at least in version 31.

074(ECPAO_IN_PROCESSING), fail to replicate employee due to retention period , KBA , LOD-EC-INT-EE , Employee Integration EC to ERP On Premise , LOD-SF-INT-CE , Compound Employee API , Problem