How To Fix MDG_BS_SUPPL_CHECK073 - No dunning data exists for the company code &1

SAP Error Message - Details

• Message type: E = Error

• Message class: MDG_BS_SUPPL_CHECK - MDG: messages for check of supplier data

• Message number: 073

• Message text: No dunning data exists for the company code &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_SUPPL_CHECK073 - No dunning data exists for the company code &1 ?

  The SAP error message MDG_BS_SUPPL_CHECK073 indicates that there is no dunning data available for the specified company code. This error typically arises in the context of Master Data Governance (MDG) when trying to process supplier data, and it suggests that the system is unable to find any dunning information related to the company code you are working with.
  Cause:
  
  Missing Dunning Data: The primary cause of this error is that the dunning data for the specified company code has not been maintained in the system. This could happen if the dunning procedure has not been set up for the supplier or if the supplier has not been assigned to the company code correctly.
  Configuration Issues: There may be configuration issues in the dunning settings for the company code, which could prevent the system from retrieving the necessary dunning data.
  Data Inconsistencies: There might be inconsistencies or missing entries in the vendor master data that prevent the system from accessing the dunning information.
  
  Solution:
  
  
  Check Dunning Data: 
  
  Go to the vendor master data (transaction code XK03 or MK03) and check if the dunning data is maintained for the supplier in the relevant company code.
  Ensure that the dunning procedure is assigned to the vendor.
  
  
  
  Maintain Dunning Data:
  
  If the dunning data is missing, you can maintain it by using transaction code FK02 (Change Vendor) or XK02 (Change Vendor - Centrally) to enter the necessary dunning information for the supplier.
  
  
  
  Review Configuration:
  
  Check the dunning configuration in the system (transaction code OBD2 for dunning procedures) to ensure that the dunning procedure is correctly set up for the company code in question.
  
  
  
  Data Consistency Check:
  
  Run consistency checks on the vendor master data to identify any discrepancies or missing information that could be causing the issue.
  
  
  
  Consult Documentation: 
  
  Review SAP documentation or help notes related to dunning procedures and vendor master data to ensure that all necessary steps have been followed.
  
  
  
  Related Information:
  
  Dunning Procedure: A dunning procedure is a set of rules that defines how overdue payments are handled, including the frequency and content of dunning letters.
  Vendor Master Data: This includes all the information related to suppliers, such as payment terms, dunning information, and company code assignments.
  Transaction Codes: Familiarize yourself with relevant transaction codes such as XK03, XK02, FK02, and OBD2 for managing vendor data and dunning configurations.
  
  If the issue persists after following these steps, it may be beneficial to consult with your SAP support team or refer to SAP Notes for further troubleshooting.