2885190 - Error 'Confirmation is outdated: processingTime is less than or equal to processingTime of existing element.'

At CPI or Boomi, the standard packages below fail and throw the exception "Confirmation is outdated: processingTime is less than or equal to processingTime of existing element."

On CPI:
ERP to SAP SuccessFactors Employee Central Confirmation v2

On Boomi:
Packaged Integration: EC Payroll to EC - Employee Confirmation v5.0

This will possibly corelate with "Pending" status in the Data Replication Monitor for the records affected.

Example:

1. The ERP program trigger user ABC (replication 1) replication now, and it trigger user ABC (replication 2) replication again after 1 minute.
2. The ERP receive 2 times user ABC payload in SRTUTIL and process according ERP queue/load.
3. The ERP picks first user ABC (replication2) and completes the infotypes writing, creating the confirmation in SLG1 and sent back to SF.
4. Next ERP picks user ABC (replication1) and completes the infotypes writing, creating the confirmation in SLG1 and sent back to SF.
5. SF is expecting to always receive the latest confirmation (replication2), but SF received in the opposite sequence/order (replication2) and later (replication1).
6. This will cause the error mentioned.

• SAP Cloud Platform Integration
• Dell Boomi
• SAP SuccessFactors

This error message occurs if the latest replication has already been finalized, and the status of an earlier replication is reported afterwards. One possible reason for this is that the replication is scheduled too often.

This situation is just for technical reasons defined as error but can be treated like a warning: The logic behind ensures that the Data Replication Monitor is only updated with the status of the latest replication which is the desired behaviour.

If it occurs rarely, you can ignore the occurrences. If it occurs more frequently, it indicates there are general issues in the setup of your integration.

Reduce the scheduling frequency of the replication process to a minimum every 15 minutes or less.

• Standard Employee Master Data / Master Data & Org Assignment (i.e. Bundle / BiB) replication processes should not be scheduled any more frequently than every 15 minutes
• Scheduling any more frequently than this (e.g. every 5 minutes / every 10 minutes) is known to cause issues

If you perform a full load, the scheduled integration should be stopped to not possibly replicate the same persons in parallel.

Don’t manually reprocess persons via Data Replication Monitor if they have been modified in EC. This may cause the person is integrated twice in parallel. The next scheduled integration run will pick them up already due to the data change.

2731712 - ERP to EC Confirmation V2 error : Header/Property value not found for the parameter XXXX error : CPI com.sap.gateway.core.ip.component.odata.exception.OsciException

Cloud Platform Integration, ERP to SAP SuccessFactors Employee Central Confirmation v2, Confirmation is outdated, processingTime, cpi, hci, confirmation, EC Payroll to EC, Employee Confirmation , KBA , LOD-SF-INT-CPI , Standard SF to 3rd Party CPI (HCI) Content , LOD-SF-INT-BPI , Dell & Boomi Infrastructure , LOD-SF-INT-CPI-ERP , Standard SF to SAP ERP or S/4HANA Integration using CPI , LOD-SF-INT-DRM , Data Replication Monitor , Problem