How To Fix MDG_BS_BP_CHECK090 - Additional Information Criterium &1 & Type &2 does not exist

SAP Error Message - Details

• Message type: E = Error

• Message class: MDG_BS_BP_CHECK - Messages for check of BP data

• Message number: 090

• Message text: Additional Information Criterium &1 & Type &2 does not exist

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_BP_CHECK090 - Additional Information Criterium &1 & Type &2 does not exist ?

  The SAP error message MDG_BS_BP_CHECK090 typically occurs in the context of Master Data Governance (MDG) for Business Partners (BP). This error indicates that a specific criterion (Criterium &1) of a certain type (&2) does not exist in the system. This can happen during the validation or activation of business partner data.
  Cause:
  
  Missing Configuration: The error often arises when the system is unable to find the specified validation or check criteria in the configuration settings. This could be due to missing entries in the relevant customizing tables.
  Incorrect Data Entry: If the data being processed does not match the expected format or values defined in the system, it can lead to this error.
  Transport Issues: If the configuration or data was recently transported from another system and the necessary settings were not included, this error may occur.
  Versioning Issues: If there are discrepancies between the versions of the MDG components or if the system is not updated, it may lead to missing criteria.
  
  Solution:
  
  
  Check Configuration:
  
  Go to the relevant customizing transaction (e.g., SPRO) and verify that the criteria for business partner checks are correctly defined.
  Ensure that the criteria specified in the error message exist in the system.
  
  
  
  Review Data:
  
  Check the data being processed to ensure it adheres to the expected formats and values.
  Validate that all required fields are filled out correctly.
  
  
  
  Transport Management:
  
  If the issue arose after a transport, check the transport logs to ensure that all necessary objects were included in the transport request.
  If needed, re-transport the missing configuration.
  
  
  
  System Updates:
  
  Ensure that your SAP system is up to date with the latest support packages and notes, as some issues may be resolved in newer versions.
  
  
  
  Debugging:
  
  If you have access to debugging tools, you can analyze the program logic to identify where the error is being triggered and why the criteria are not found.
  
  
  
  Consult Documentation:
  
  Review SAP Notes and documentation related to MDG and business partner checks for any specific guidance or known issues.
  
  
  
  Related Information:
  
  SAP Notes: Search for relevant SAP Notes that might address this specific error or provide additional context.
  MDG Documentation: Review the official SAP documentation for Master Data Governance to understand the configuration and validation processes better.
  Community Forums: Check SAP Community or other forums for similar issues reported by other users, as they may provide insights or solutions.
  
  If the issue persists after following these steps, consider reaching out to SAP support for further assistance.