How To Fix MDG_DT_DATA_MODEL124 - Switch BC set &1 does not exist; recheck switch BC set name

SAP Error Message - Details

• Message type: E = Error

• Message class: MDG_DT_DATA_MODEL - Messages for the Configuration Workbench Model Access API

• Message number: 124

• Message text: Switch BC set &1 does not exist; recheck switch BC set name

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_DT_DATA_MODEL124 - Switch BC set &1 does not exist; recheck switch BC set name ?

  The SAP error message "MDG_DT_DATA_MODEL124: Switch BC set &1 does not exist; recheck switch BC set name" typically occurs in the context of SAP Master Data Governance (MDG) when there is an issue with the Business Configuration (BC) set that is being referenced. Here’s a breakdown of the cause, potential solutions, and related information:
  Cause:
  
  Non-Existent BC Set: The error indicates that the Business Configuration (BC) set specified in the error message does not exist in the system. This could be due to a typo in the name or the BC set not being created or activated.
  Incorrect Configuration: The configuration settings for the MDG data model may not be correctly set up, leading to references to BC sets that are not valid.
  Transport Issues: If the BC set was supposed to be transported from another system (e.g., from development to production), it may not have been transported correctly.
  
  Solution:
  
  Verify BC Set Name: Check the name of the BC set mentioned in the error message. Ensure that it is spelled correctly and matches the naming conventions used in your system.
  Check BC Set Existence: Use transaction code SIMG or SPRO to navigate to the relevant configuration area and verify if the BC set exists. If it does not exist, you may need to create it or activate it.
  Create/Activate BC Set: If the BC set is missing, you may need to create it or activate it if it is in a deactivated state. This can typically be done through the configuration settings in the MDG area.
  Transport BC Set: If the BC set is supposed to be in the system but is missing, check the transport logs to ensure that it was transported correctly. If not, you may need to re-transport it.
  Consult Documentation: Refer to the SAP documentation for MDG to understand the specific requirements and configurations for the BC sets related to your data model.
  
  Related Information:
  
  SAP Notes: Check SAP Notes related to MDG and BC sets for any known issues or additional guidance.
  MDG Configuration Guide: Review the MDG configuration guide for detailed steps on setting up and managing BC sets.
  Community Forums: Consider checking SAP Community forums or other user groups for similar issues and solutions shared by other users.
  
  If the issue persists after following these steps, it may be beneficial to consult with your SAP Basis or MDG support team for further assistance.