How To Fix FKKCOLL124 - No dunning notices exist for business partner &1

SAP Error Message - Details

• Message type: E = Error

• Message class: FKKCOLL - Submission to Ext.Collection Agency/Legal Dunning Procedure

• Message number: 124

• Message text: No dunning notices exist for business partner &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 FKKCOLL124 - No dunning notices exist for business partner &1 ?

  The SAP error message FKKCOLL124 indicates that there are no dunning notices available for the specified business partner (indicated by &1). This error typically occurs in the context of the dunning process in SAP, which is used to manage overdue receivables and send reminders to customers.
  Cause:
  
  No Dunning Procedure Assigned: The business partner may not have a dunning procedure assigned, which is necessary for generating dunning notices.
  No Open Items: There may be no open items or overdue invoices for the business partner that would trigger a dunning notice.
  Dunning Run Not Executed: The dunning run may not have been executed for the specified period, meaning no dunning notices have been generated.
  Dunning Block: The business partner may have a dunning block set, preventing any dunning notices from being created.
  Incorrect Selection Criteria: The selection criteria used to retrieve dunning notices may be incorrect, leading to no results being found.
  
  Solution:
  
  Check Dunning Procedure: Ensure that the business partner has a dunning procedure assigned. You can do this by checking the business partner's master data.
  Verify Open Items: Check if there are any open items or overdue invoices for the business partner. If there are none, no dunning notices will be generated.
  Execute Dunning Run: If the dunning run has not been executed, run the dunning process for the relevant period. This can be done through transaction code F150.
  Review Dunning Block: Check if there is a dunning block on the business partner. If so, you may need to remove it to allow dunning notices to be generated.
  Adjust Selection Criteria: Review the selection criteria used when trying to retrieve dunning notices to ensure they are correct and appropriate for the business partner in question.
  
  Related Information:
  
  Transaction Codes:
  
  F150: Execute Dunning Run
  BP: Business Partner Master Data
  
  
  Dunning Configuration: Review the configuration settings for dunning procedures in the SAP system to ensure they are set up correctly.
  Documentation: Refer to SAP Help documentation for detailed information on dunning processes and configurations.
  
  By following these steps, you should be able to identify the cause of the error and implement the necessary solutions to resolve it.