How To Fix >1680 - | Dunning by collection strategy for co. code &1: Line item &2 not dunned

SAP Error Message - Details

• Message type: E = Error

• Message class: >1 - Shockwave SAPGUI message handling

• Message number: 680

• Message text: | Dunning by collection strategy for co. code &1: Line item &2 not dunned

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 >1680 - | Dunning by collection strategy for co. code &1: Line item &2 not dunned ?

  The SAP error message 1680 indicates that a line item has not been dunned due to the collection strategy defined for the company code. This message typically arises in the context of accounts receivable and dunning processes, where the system is trying to apply a dunning procedure to a specific line item but encounters an issue based on the collection strategy.
  Cause:
  
  Collection Strategy Configuration: The collection strategy for the company code may not be set up correctly, or it may not include the specific criteria needed to dunning the line item.
  Dunning Block: The line item may have a dunning block set, which prevents it from being dunned.
  Dunning Procedure: The dunning procedure assigned to the customer may not be appropriate for the line item in question.
  Payment Terms: The payment terms associated with the line item may not meet the criteria for dunning.
  Dunning Levels: The line item may have already reached the maximum dunning level, or it may not have reached the threshold for dunning.
  
  Solution:
  
  Check Collection Strategy: Review the collection strategy settings for the company code in the SAP configuration. Ensure that the strategy is correctly defined and includes the necessary criteria for dunning the line item.
  Review Dunning Block: Check if the line item has a dunning block. If it does, you may need to remove the block if it is appropriate to do so.
  Verify Dunning Procedure: Ensure that the dunning procedure assigned to the customer is appropriate for the line item. You may need to adjust the dunning procedure settings.
  Examine Payment Terms: Review the payment terms associated with the line item to ensure they align with the dunning criteria.
  Check Dunning Levels: Verify the dunning levels for the line item. If it has already been dunned to the maximum level, it may not be eligible for further dunning.
  Run Dunning Program Again: After making the necessary adjustments, run the dunning program again to see if the line item can now be dunned.
  
  Related Information:
  
  Transaction Codes: You may use transaction codes like F150 (Dunning) to run the dunning program and OBD2 (Dunning Procedure) to check the dunning procedure settings.
  SAP Notes: Check for any relevant SAP Notes that may address specific issues related to dunning and collection strategies.
  Documentation: Review SAP documentation on dunning processes and collection strategies for more detailed guidance on configuration and troubleshooting.
  
  By following these steps, you should be able to identify the cause of the error message and implement the necessary solutions to resolve it.