How To Fix >W070 - Items with payment specification for payment run are not dunned

SAP Error Message - Details

• Message type: E = Error

• Message class: >W -

• Message number: 070

• Message text: Items with payment specification for payment run are 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 >W070 - Items with payment specification for payment run are not dunned ?

  The SAP error message W070: Items with payment specification for payment run are not dunned typically occurs in the context of accounts receivable and dunning processes. This message indicates that there are items in the system that have been specified for payment but are not eligible for dunning. Here’s a breakdown of the cause, potential solutions, and related information:
  Cause:
  
  Payment Specification: The items in question have been marked for payment, which means they are in a state where they are expected to be paid, and thus, they are excluded from the dunning process.
  Dunning Configuration: The dunning procedure may be configured in such a way that it does not include items that are already specified for payment.
  Dunning Block: The items may have a dunning block set, which prevents them from being included in the dunning run.
  Payment Terms: The payment terms associated with the items may indicate that they are not yet overdue, which would also exclude them from dunning.
  Document Status: The status of the document (e.g., cleared, paid, etc.) may also affect whether it can be dunned.
  
  Solution:
  
  Review Payment Specifications: Check the items that are specified for payment and determine if they should be included in the dunning process. If they should be dunned, you may need to remove the payment specification.
  Check Dunning Configuration: Review the dunning procedure settings in the SAP system to ensure that it is configured to include items that are specified for payment if that is the desired behavior.
  Remove Dunning Block: If there is a dunning block on the items, consider removing it if appropriate.
  Adjust Payment Terms: Ensure that the payment terms are set correctly and that the items are indeed overdue for dunning.
  Consult Documentation: Refer to SAP documentation or consult with your SAP support team to understand the specific configurations and settings that may be affecting the dunning process.
  
  Related Information:
  
  Dunning Process: Understand how the dunning process works in SAP, including the different dunning levels and how items are selected for dunning.
  Transaction Codes: Familiarize yourself with relevant transaction codes such as F150 (Dunning) and FBL5N (Customer Line Item Display) to analyze customer accounts and dunning items.
  SAP Notes: Check for any SAP Notes related to this error message for additional insights or patches that may address specific issues.
  User Exits and Enhancements: If your organization has custom enhancements or user exits related to the dunning process, review those to ensure they are not affecting the standard behavior.
  
  By following these steps, you should be able to identify the cause of the error message and take appropriate action to resolve it.