Symptom
After the 2H 2025 Release you have notices some issues or errors in the DRM or errors on related the replication confirmation process.
For example, you see an issue or error like one of the following:
- Reprocess and / or Delete buttons missing:
- [COE0020]Reprocess permission is required
- You may that no employees are displayed in the Data Replication Monitor when you access it
(i.e. for all Replication Statuses & All Until Now)
- You see errors like below error on the confirmation process:
<?xml version='1.0' encoding='utf-8'?>
<UpsertResponses>
<EmployeeDataReplicationConfirmationUpsertResponse>
<key>EmployeeDataReplicationConfirmation/externalCode=********************************</key>
<status>ERROR</status>
<editStatus null="true"/>
<message>No permission to delete object!</message>
<index type="Edm.Int32">0</index>
<httpCode type="Edm.Int32">500</httpCode>
<inlineResults type="Bag(SFOData.UpsertResult)"/>
</EmployeeDataReplicationConfirmationUpsertResponse>
Please note: these should only be considered symptoms in the event of this happening directly after the 2H release
- Any further symptoms will be added here will be added once identified
Image/data in this KBA is from SAP internal systems, sample data, or demo systems. Any resemblance to real data is purely coincidental.
Environment
SAP SuccessFactors Integrations 2H 2025
Resolution
As of this release we have introduced a change making the below replication objects secured by default:
- EmployeeDataReplicationElement (Employee Data Replication Status)
- EmployeeDataReplicationConfirmation
- EmployeeDataReplicationNotification
- ReplicationTargetSystem
- DataReplicationMonitorConfiguration
As a result of this change, users who previously had "Access to non-secured objects" permission or the "Admin access to MDF OData APIs" permission should be defaulted to have read and write permissions to the above objects under User Permissions > Data Replication Monitor section in the relevant role in Manage Permission Roles.
- During the 2H Preview release we observed that some customers did not have these permissions granted automatically as part of the release & according to the above logic
- DRM engineering team have advised that this should be addressed for the 2H Production release & the permissions should be granted automatically users who previously had "Access to non-secured objects" permission or the "Admin access to MDF OData APIs"
- Important note: before the release, users with the permissions "Access to non-secured objects" or "Admin access to MDF OData APIs" already had access to the replication objects mentioned above. After the release, these users will receive the new specific permissions for replication objects under User Permissions > Data Replication Monitor. This does not mean they have gained additional access - they already had it through the admin permissions mentioned previously (this change would also not provide them access to the Data Replication Monitor tool).
The access to the Data Replication Monitor tool is controlled via Manage Integration Tools > Access to Data Replication Monitor
WORKAROUND:
If you face any of the above symptoms (or similar) following the 2H Production release (that were not occurring before the release)
Please try manually adding the View / Edit permissions under User Permissions > Data Replication Monitor section in the relevant role in Manage Permission Roles.
Granting these permissions has addressed all reported situations occurring in the Data Replication Monitor as a result of this change.
See Also
- SAP SuccessFactors Product Release & Road Map Information
- SAP SuccessFactors Patches Knowledge Base
- KB Article 2171560 - How to be notified of new or updated SAP Notes or KBAs
Keywords
SAP Knowledge Base Article - Public