Symptom
- Purge request is not shown on "Requests Awaiting Approval" tab, but instead appear directly on "Approved Request" tab with status "failed".
- Approval status show as "Reviewing..." for the failed purge request.
- Purge request fails without preview report.
- SAP Support may see server logs in the backend showing an error with "SFLearningObjectType".
- Purge shows "0 of 1 approved"
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 HCM Suite
- SAP SuccessFactors Learning
Reproducing the Issue
- Create a user purge request >
- Go to Purge Request Monitor >
- The request just created will not be shown on "Requests Pending Initial Approval" tab >
- Go to "Purge Progress & Results" tab >
- You will see the purge request with status "Failed" >
- If you click the approved below the "Failed", you will see as if the purge is on reviewing by the approvers:
Cause
- Cause #1: Learning is enabled in Provisioning > Company Settings > But no Learning URL is configured (there is a misconfiguration).
- Cause #2: The user submitting the purge does not have Learning admin permissions and/or does not have a matching user in Learning.
Resolution
Resolution for cause #1:
Ensure that the BizX - Learning integration is properly configured.
In some cases, Learning is enabled in Provisioning > Company Settings > However there's no Learning URL configured.
This will result in the purge automatically failing. Please refer to KBA 2318325 for further details on BizX - Learning integration.
Resolution for cause #2:
The user in BizX scheduling the DRTM Master Data Purge/Purge Inactive should have the following permissions in Learning:
- View User - to view the report.
- Delete User - to delete the user.
Additionally, the user who submits the purge request must have an admin user in Learning, as referenced in Assigning Roles to SAP SuccessFactors Learning Administrators | SAP Help Portal
The user who submits the purge request must have a matching admin ID and user ID in Learning, which also must match the user ID in SAP SuccessFactors platform.
The expected is: Platform user ID = Learning user ID = Learning admin ID
- The SAP SuccessFactors platform user_sysid must match the admin ID and the user (learner) ID exactly. For example, if your SAP SuccessFactors platform user is jdoe, then you must have an admin id jdoe (exact match) and a user ID jdoe in Learning. This is because the master data purge calls an API for both the get report and the delete (purge) user APIs. Learning takes the user_sysid from the SAP SuccessFactors platform and plugs it into the permissions to call the API in Learning. So a jdoe in SAP SuccessFactors platform calls the API as a jdoe in Learning.
See Also
Keywords
Data Management, Purge user, failure, LMS, sf, sf, sfsf, sf sf, SuccessFactors, SuccessFactor, Success, Factor, bizx, plt, failed, purge reviewing, Exception is caught when getting person type by user ids, Splunk, server logs, job failed, 2005, release, issues, new error, error message is The user is not permitted to perform the requested operation, INC0074434, DRMAccessException, EAS-16067, purge, request, Requests Awaiting Approval, Approved Request, failed, status , KBA , LOD-SF-PLT-DRM , Data Retention Management , LOD-SF-LMS-ADM , System Admin, Global Variables, References , LOD-SF-PLT , Platform Foundational Capabilities , LOD-SF-LMS , Learning Management System , How To