Do you have any question about this error?
Message type: E = Error
Message class: MDG_BS_CC - Cleansing Case Messages specific to MDG
Message number: 001
Message text: Change request &1 still exists; severing not allowed
As long as a change request is available, you cannot delete the
cleansing case assigned to it.
The system issues an error message and will not allow you to continue with this transaction until the error is resolved.
You have to delete the change request before removing it from the
cleansing case.
Error message extract from SAP system. Copyright SAP SE.
MDG_BS_CC001
- Change request &1 still exists; severing not allowed ?The SAP error message MDG_BS_CC001 indicates that a change request (CR) is still active or exists in the system, and therefore, the action you are trying to perform (such as severing a relationship or deleting an object) is not allowed. This is a common issue in SAP Master Data Governance (MDG) when dealing with change requests.
Cause:
- Active Change Request: The primary cause of this error is that there is an active change request associated with the object you are trying to modify or delete. The system prevents severing or deleting objects that are linked to ongoing change requests to maintain data integrity.
- Pending Approvals: The change request may be pending approval or still in process, which means it cannot be severed until it is completed or rejected.
- Incorrect Status: The object may be in a status that does not allow for severing or deletion.
Solution:
Check Active Change Requests:
- Use transaction code MDG_CRP or MDG_MAINT to check for any active change requests related to the object in question.
- Identify the change request number and its status.
Complete or Reject the Change Request:
- If the change request is still in process, you may need to complete it or reject it, depending on your business process.
- If you have the necessary authorizations, you can approve or reject the change request.
Change Request Status:
- Ensure that the change request is in a status that allows for severing or deletion. If it is in a status that does not permit these actions, you will need to change its status accordingly.
Consult with Your Team:
- If you are unsure about how to proceed with the change request, consult with your team or the person responsible for managing change requests in your organization.
System Logs:
- Check system logs for any additional information or related errors that might provide more context about the issue.
Related Information:
By following these steps, you should be able to resolve the error and proceed with your intended actions in SAP MDG.
Get instant SAP help. Start your 7-day free trial now.
MDG_BS_CC000
No cleansing case exists in relation to change request &1
What causes this issue? A query was triggered to find the cleansing case related to a change request.System Response Either the cleansing case does ...
MDG_BS_BP_UNIT_TEST052
Read Char Value does not know entity &1
Self-Explanatory Message Since SAP believes that this specific error message is 'self-explanatory,' no more information has been given.The majority of...
MDG_BS_CC002
Relation to change request &1 has been successfully severed
Self-Explanatory Message Since SAP believes that this specific error message is 'self-explanatory,' no more information has been given.The majority of...
MDG_BS_CC003
Relation to change request &1 could not be deleted (check CR number)
Self-Explanatory Message Since SAP believes that this specific error message is 'self-explanatory,' no more information has been given.The majority of...
Click on this link to search all SAP messages.