How To Fix MDC_HDB_MTC060 - Match configuration &1 is not in generated state

MDC_HDB_MTC060 - Overview

• Message type: E = Error

• Message class: MDC_HDB_MTC - Message class for master data consolidation matching

• Message number: 060

• Message text: Match configuration &1 is not in generated state

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 MDC_HDB_MTC060 - Match configuration &1 is not in generated state ?

  The SAP error message MDC_HDB_MTC060, which states "Match configuration &1 is not in generated state," typically occurs in the context of SAP HANA and the Multi-tenant Database Container (MDC) environment. This error indicates that a specific match configuration (identified by &1) has not been properly generated or activated, which is necessary for the system to function correctly.
  
  Cause:
  
  Configuration Not Generated: The match configuration has been created but not yet generated. This means that the necessary artifacts or structures that the configuration relies on have not been created in the database.
  Incomplete Setup: There may be an incomplete setup or configuration process that has not been finalized.
  System State: The system may be in a state where it cannot process the match configuration due to prior errors or issues.
  
  
  Solution:
  
  
  Generate the Match Configuration:
  
  Navigate to the relevant transaction or application where the match configuration is defined.
  Look for an option to generate or activate the match configuration.