How To Fix CM_MDG_BS_CLF_GEN035 - Classification data not saved. Errors occured

CM_MDG_BS_CLF_GEN035 - Overview

• Message type: E = Error

• Message class: CM_MDG_BS_CLF_GEN - Classification Message Class

• Message number: 035

• Message text: Classification data not saved. Errors occured

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 CM_MDG_BS_CLF_GEN035 - Classification data not saved. Errors occured ?

  The SAP error message CM_MDG_BS_CLF_GEN035 indicates that there was an issue when trying to save classification data in the Master Data Governance (MDG) system. This error typically arises during the classification of master data objects, such as materials or business partners, and can be caused by various factors.
  Possible Causes:
  
  Validation Errors: There may be validation rules that are not met. For example, mandatory fields might be missing or contain invalid data.
  Authorization Issues: The user may not have the necessary authorizations to save classification data.
  Data Consistency Issues: There could be inconsistencies in the data being saved, such as duplicate entries or references to non-existent objects.
  Technical Issues: There may be underlying technical issues, such as database constraints or system performance problems.
  Custom Code: If there are custom enhancements or modifications in the classification process, they might be causing the error.
  
  Solutions:
  
  Check Validation Messages: Review the detailed error messages or logs to identify specific validation issues.