How To Fix 0D290 - Dunning grouping not defined for company code &1 and product group &2

SAP Error Message - Details

• Message type: E = Error

• Message class: 0D - FS-CD General Messages

• Message number: 290

• Message text: Dunning grouping not defined for company code &1 and product group &2

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 0D290 - Dunning grouping not defined for company code &1 and product group &2 ?

  The SAP error message 0D290 indicates that there is a missing configuration for the dunning process in relation to a specific company code and product group. This error typically arises when the system attempts to execute a dunning run but cannot find the necessary settings for the specified parameters.
  Cause:
  The error occurs due to the following reasons:
  
  Dunning Grouping Not Defined: The dunning grouping for the specified company code and product group has not been defined in the system.
  Configuration Issues: There may be incomplete or incorrect configuration settings in the dunning procedure.
  Missing Master Data: The relevant master data (like customer/vendor master records) may not have the appropriate dunning grouping assigned.
  
  Solution:
  To resolve the error, you can follow these steps:
  
  
  Define Dunning Grouping:
  
  Go to the SAP transaction code OBD2 (or navigate through the menu: Financial Accounting > Accounts Receivable > Dunning > Define Dunning Areas).
  Check if the dunning grouping for the specified company code and product group is defined. If not, create a new entry.
  Ensure that the dunning area is correctly assigned to the relevant company code and product group.
  
  
  
  Check Dunning Procedure:
  
  Use transaction code OBD3 to review the dunning procedure settings.
  Ensure that the dunning procedure is correctly assigned to the company code and that it includes the necessary dunning levels and parameters.
  
  
  
  Review Master Data:
  
  Check the customer or vendor master records to ensure that the dunning grouping is assigned correctly.
  Use transaction codes FD03 (for customers) or FK03 (for vendors) to view the master data and verify the dunning grouping.
  
  
  
  Test the Configuration:
  
  After making the necessary changes, perform a test dunning run to ensure that the error no longer occurs.
  
  
  
  Related Information:
  
  Dunning Process: The dunning process in SAP is used to manage overdue receivables and send reminders to customers regarding outstanding payments.
  Dunning Areas: Dunning areas are used to group customers or vendors for the purpose of dunning. Each dunning area can have its own dunning procedure.
  Transaction Codes:
  
  OBD2: Define Dunning Areas
  OBD3: Dunning Procedure
  FD03: Display Customer Master
  FK03: Display Vendor Master
  
  
  
  By following these steps, you should be able to resolve the error message 0D290 and ensure that the dunning process functions correctly for the specified company code and product group.