How To Fix MDG_BS_ECC_SUPPLIER036 - No CR type available for business activity &1

SAP Error Message - Details

• Message type: E = Error

• Message class: MDG_BS_ECC_SUPPLIER - Master Data Processes ECC Supplier

• Message number: 036

• Message text: No CR type available for business activity &1

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_ECC_SUPPLIER036 - No CR type available for business activity &1 ?

  The SAP error message MDG_BS_ECC_SUPPLIER036 indicates that there is no Change Request (CR) type available for the specified business activity in the Master Data Governance (MDG) system, particularly in the context of supplier data management.
  Cause:
  This error typically arises due to one of the following reasons:
  
  Missing Configuration: The Change Request type for the specific business activity (e.g., creating, changing, or deleting a supplier) has not been configured in the MDG system.
  Incorrect Business Activity: The business activity specified in the error message may not be correctly defined or may not correspond to any existing Change Request type.
  Authorization Issues: There may be authorization issues preventing the system from accessing the Change Request type.
  System Settings: The system settings may not be properly aligned with the business processes, leading to the absence of a valid Change Request type.
  
  Solution:
  To resolve this error, you can take the following steps:
  
  
  Check Configuration:
  
  Go to the MDG configuration settings in the SAP system.
  Navigate to the Change Request Management settings and verify that the Change Request type for the specific business activity is defined and active.
  Ensure that the Change Request type is correctly assigned to the relevant business activity.
  
  
  
  Define Change Request Type:
  
  If the Change Request type is missing, you may need to create a new Change Request type that corresponds to the business activity in question.
  Use transaction code MDGIMG to access the configuration and define the necessary Change Request types.
  
  
  
  Review Business Activity:
  
  Ensure that the business activity specified in the error message is valid and corresponds to a defined Change Request type.
  Check for any typos or discrepancies in the business activity name.
  
  
  
  Authorization Check:
  
  Verify that the user has the necessary authorizations to create or process Change Requests for the specified business activity.
  Check the roles and authorizations assigned to the user in the SAP system.
  
  
  
  Consult Documentation:
  
  Review the SAP documentation or help resources related to MDG and Change Request Management for additional guidance on configuration and troubleshooting.
  
  
  
  Testing:
  
  After making the necessary changes, test the process again to ensure that the error no longer occurs.
  
  
  
  Related Information:
  
  Transaction Codes: MDGIMG (to access MDG configuration), SE11 (to check data dictionary), SE80 (to check repository objects).
  SAP Notes: Check for any relevant SAP Notes that may address known issues or provide additional guidance related to this error message.
  MDG Community: Engage with the SAP community forums or support channels for insights from other users who may have encountered similar issues.
  
  By following these steps, you should be able to identify and resolve the cause of the error message MDG_BS_ECC_SUPPLIER036 in your SAP MDG system.