3543784 - Confirmation fails with "OData Upsert failed :<500>No permission to create object!" - SF employee replication to ECP

No replication entries are being shown in DRM (Data Replication Monitor).

When looking at replication logs in SLG1, the Confirmation logs are failing with the error below:

"OData Upsert failed :<500>No permission to create object! with the index 0
OData Upsert response HTTP Status: 500..."

• SuccessFactors
  • Data Replication Monitor
• ECP

The issue arises due to the lack of necessary permissions for the technical user involved in the replication process. The user does not have the required permission to edit the "Employee Data Replication Status" object, which contains the data for DRM.

If this object is set as secured, then the "Admin access to MDF OData API" will not be enough.

1. Identify the technical user involved in the replication process.
   • If you are using basic authentication, the user will be shown in SE38 > RP_HRSFEC_PTP_CONFIGURATION transaction in ECP.
   • If you are using certificate-based authentication, follow these steps to identify the user:
     
     1. In SF, go to Security Center.
     2. Select "X.509 Public Certificate Mapping" tile.
     3. Search for the certificate entry which refers to your ECP system.
     4. The user will be shown in "Login Name" field.
2. Grant the user the necessary permission to edit the "Employee Data Replication Status" object.
   • The required permission is "Miscellaneous Permissions > Employee Data Replication Status (View and Edit)".

Data Replication Monitor, DRM, fields not updating, ECP, Employee Data Replication Status, permissions, technical user, replication process,  RP_HRSFEC_PTP_CONFIGURATION, X.509, X509, certificate authentication, , KBA , LOD-SF-INT-DRM , Data Replication Monitor , LOD-EC-GCP-PY-EDR , Employee Data Replication , Problem