How To Fix FVD_COND_VERIFIER066 - Condition item is not a payment condition but contains a dunning lock

SAP Error Message - Details

• Message type: E = Error

• Message class: FVD_COND_VERIFIER - Condition Verifier

• Message number: 066

• Message text: Condition item is not a payment condition but contains a dunning lock

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 FVD_COND_VERIFIER066 - Condition item is not a payment condition but contains a dunning lock ?

  The SAP error message FVD_COND_VERIFIER066 indicates that there is an issue with a condition item in the context of dunning (the process of communicating with customers to ensure the collection of accounts receivable). Specifically, the error states that the condition item is not recognized as a payment condition but has a dunning lock applied to it.
  Cause:
  
  Condition Type Misconfiguration: The condition item in question may not be set up correctly in the system. It might be classified incorrectly, leading the system to treat it as a non-payment condition.
  Dunning Lock: The condition item has a dunning lock applied, which prevents it from being processed further in the dunning run. This could be due to previous settings or manual interventions.
  Data Inconsistency: There may be inconsistencies in the master data or transaction data that are causing the system to misinterpret the condition item.
  
  Solution:
  
  
  Check Condition Type Configuration:
  
  Go to the condition type configuration in the SAP system (Transaction code: V/06 for pricing conditions).
  Verify that the condition type is correctly defined as a payment condition and does not have any dunning-related settings that conflict with its intended use.
  
  
  
  Review Dunning Settings:
  
  Check the dunning settings for the customer account in question. Ensure that the dunning lock is appropriate and that it is not applied to conditions that should be processed.
  You can check the dunning information in the customer master data (Transaction code: FD03).
  
  
  
  Remove Dunning Lock:
  
  If the dunning lock is not necessary, you can remove it. This can typically be done in the customer account settings or through the dunning run configuration.
  
  
  
  Data Consistency Check:
  
  Run a consistency check on the relevant data to ensure that there are no discrepancies. This may involve checking the related documents, customer accounts, and condition records.
  
  
  
  Consult Documentation:
  
  Refer to SAP documentation or help notes related to dunning and condition types for further insights and best practices.
  
  
  
  Contact SAP Support:
  
  If the issue persists after checking the above points, consider reaching out to SAP support for assistance. They may provide specific notes or patches that address this error.
  
  
  
  Related Information:
  
  Dunning Process: Understand how the dunning process works in SAP, including the configuration of dunning levels and the impact of dunning locks on payment conditions.
  Condition Types: Familiarize yourself with the different condition types in SAP and their purposes, especially in the context of pricing and payment processing.
  Transaction Codes: Useful transaction codes include:
  
  V/06 for condition type configuration.
  FD03 for viewing customer master data.
  F150 for running the dunning program.
  
  
  
  By following these steps, you should be able to identify the root cause of the error and implement a solution to resolve it.