How To Fix MDG_BS_CC002 - Relation to change request &1 has been successfully severed

SAP Error Message - Details

• Message type: E = Error

• Message class: MDG_BS_CC - Cleansing Case Messages specific to MDG

• Message number: 002

• Message text: 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 messages in the SAP system have a message text, however this is frequently insufficient to comprehend or resolve the problem.

To make things easier, more detailed information is frequently added to describe the issue, how to fix it, and the necessary steps or configuration modifications.

Unfortunately, there isn't any extra information in this error notice.

What else can you do?

First, use our AnswerBot below to get a possible cause and solution (requires a premium subscription).

Also, review the in-depth Common Questions & Answers listed below; you could discover a solution there or be able to connect with others who have faced similar challenges.

You can also try searching the SAP support portal (support.sap.com) but you need a special user ID to access it. It is possible that an SAP support note exists that provides additional details about the mistake or even steps for fixing it.

Smart SAP Assistant

• What is the cause and solution for SAP error message MDG_BS_CC002 - Relation to change request &1 has been successfully severed ?

  The SAP error message MDG_BS_CC002 indicates that a relationship to a change request has been successfully severed. This message typically occurs in the context of SAP Master Data Governance (MDG) when a change request is being processed, and a relationship to that change request is being removed or disconnected.
  Cause:
  The error message MDG_BS_CC002 is not necessarily an error in the traditional sense; rather, it is an informational message indicating that a relationship to a change request has been severed. This can happen for several reasons, including:
  
  Manual Severing: A user may have manually severed the relationship to the change request.
  Change Request Processing: During the processing of a change request, certain relationships may be automatically severed based on the logic defined in the MDG configuration.
  Data Model Changes: Changes in the data model or the underlying master data may lead to the severing of relationships.
  
  Solution:
  Since this message is informational, there may not be a need for a specific solution unless it is causing issues in your workflow. However, if you want to address the situation, consider the following steps:
  
  Review Change Request: Check the change request associated with the message to understand why the relationship was severed. Look for any changes made to the master data that might have triggered this action.
  Check Configuration: Review the MDG configuration settings to ensure that the severing of relationships is intended behavior. If it is not, you may need to adjust the configuration.
  Consult Documentation: Refer to SAP documentation or notes related to MDG to understand the context of this message better.
  User Training: If users are manually severing relationships, consider providing training or guidelines on when and how to do this appropriately.
  
  Related Information:
  
  SAP Notes: Check for any relevant SAP Notes that might provide additional context or solutions related to this message.
  MDG Documentation: Review the official SAP MDG documentation for insights into change request processing and relationship management.
  Community Forums: Engage with SAP community forums or user groups to see if others have encountered similar messages and how they resolved them.
  
  If the message is causing issues in your workflow or if you need further assistance, consider reaching out to your SAP support team or consulting with an SAP expert.