How To Fix >4670 - | Dunning level not executed, percentage limit not reached

SAP Error Message - Details

• Message type: E = Error

• Message class: >4 - SAP File Transfer Protocol

• Message number: 670

• Message text: | Dunning level not executed, percentage limit not reached

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 >4670 - | Dunning level not executed, percentage limit not reached ?

  The SAP error message 4670 indicates that a dunning level was not executed because the percentage limit for dunning has not been reached. This typically occurs in the context of the dunning process, which is used to manage overdue customer invoices and accounts receivable.
  Cause:
  The error message is triggered when the system checks the dunning parameters and finds that the percentage of the total amount due does not meet the threshold set for the dunning level. This means that the amount overdue is not significant enough to warrant the next level of dunning.
  Solution:
  To resolve this issue, you can consider the following steps:
  
  
  Check Dunning Configuration:
  
  Review the dunning procedure settings in the SAP system. Ensure that the percentage limits for each dunning level are set correctly according to your business requirements.
  You can access the dunning configuration through the transaction code OBD2 (Dunning Procedure) or FBMP (Dunning Configuration).
  
  
  
  Review Customer Account:
  
  Check the specific customer account to see the outstanding amounts and their due dates. Ensure that there are overdue invoices that should trigger the dunning process.
  Use transaction code FD10N to display the customer balance and verify the amounts.
  
  
  
  Adjust Dunning Levels:
  
  If necessary, adjust the dunning levels or the percentage limits to ensure that they align with your business practices. You may want to lower the percentage limit if you want to trigger dunning at lower overdue amounts.
  
  
  
  Run Dunning Program:
  
  After making any necessary adjustments, run the dunning program again using transaction code F150. Ensure that you select the correct parameters for the dunning run.
  
  
  
  Check for Other Errors:
  
  If the issue persists, check for any other error messages or logs that might provide additional context. You can use transaction code SLG1 to view application logs.
  
  
  
  Related Information:
  
  Dunning Procedure: A dunning procedure in SAP defines how overdue invoices are managed, including the frequency and severity of reminders sent to customers.
  Dunning Levels: Each dunning level can have different parameters, such as the number of days overdue and the percentage of the total amount due that must be reached before the dunning notice is sent.
  Transaction Codes:
  
  F150: Dunning Run
  OBD2: Dunning Procedure Configuration
  FD10N: Display Customer Balance
  SLG1: Application Log
  
  
  
  By following these steps, you should be able to address the error message and ensure that the dunning process functions as intended.