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

SAP Error Message - Details

• Message type: E = Error

• Message class: MDG_BS_ECC_BP_CHECK - MDG: messages for check on vendor and customer 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_ECC_BP_CHECK073 - No dunning data exists for the company code &1 ?

  The SAP error message MDG_BS_ECC_BP_CHECK073 indicates that there is no dunning data available for the specified company code in the context of Business Partner (BP) data management. This error typically arises when you are trying to perform operations related to business partners, such as creating or updating a business partner, and the system checks for dunning information that is expected to exist for the specified company code.
  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 business partner or if the business partner has not been assigned to the relevant company code.
  
  
  Incorrect Configuration: There may be issues with the configuration of the dunning process in the SAP system, such as missing settings in the dunning area or incorrect assignment of the business partner to the company code.
  
  
  Data Inconsistency: There could be inconsistencies in the data related to the business partner or the company code, leading to the absence of expected dunning information.
  
  
  Solution:
  
  
  Maintain Dunning Data:
  
  Go to the transaction code BP (Business Partner) and check the dunning data for the business partner in question.
  Ensure that the dunning procedure is assigned to the business partner for the relevant company code.
  
  
  
  Check Configuration:
  
  Verify the dunning configuration in the SAP system. You can do this by navigating to the dunning settings in the Financial Accounting (FI) module.
  Ensure that the dunning area is correctly configured and that the business partner is assigned to the appropriate company code.
  
  
  
  Assign Business Partner to Company Code:
  
  If the business partner is not assigned to the company code, you need to assign it. This can be done in the Business Partner transaction (BP) by editing the business partner and adding the necessary company code information.
  
  
  
  Review Data Consistency:
  
  Check for any inconsistencies in the data related to the business partner and the company code. You may need to run data consistency checks or use transaction codes like SE16 to view the relevant tables.
  
  
  
  Consult Documentation:
  
  Refer to SAP documentation or help resources for more detailed guidance on managing dunning data and business partner settings.
  
  
  
  Related Information:
  
  Dunning Process: The dunning process in SAP is used to manage overdue receivables and involves sending reminders to customers for outstanding payments.
  Business Partner Role: Ensure that the business partner has the correct roles assigned that pertain to financial transactions and dunning.
  Transaction Codes: Familiarize yourself with relevant transaction codes such as BP (Business Partner), FD32 (Customer Master), and OBD2 (Dunning Configuration) for managing business partner and dunning settings.
  
  If the issue persists after following these steps, it may be beneficial to consult with your SAP support team or a functional consultant who specializes in Financial Accounting and Business Partner management.