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

SAP Error Message - Details

• Message type: E = Error

• Message class: FVD_COND_VERIFIER - Condition Verifier

• Message number: 065

• Message text: Condition item is not a payment condition but contains a payment 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_VERIFIER065 - Condition item is not a payment condition but contains a payment lock ?

  The SAP error message FVD_COND_VERIFIER065 indicates that there is a condition item in your pricing or condition records that is not classified as a payment condition, yet it has a payment lock applied to it. This situation typically arises in the context of financial transactions, particularly in the SAP Financial Services module.
  Cause:
  
  Incorrect Condition Type: The condition type associated with the item may not be set up to handle payment conditions, but it has been inadvertently marked with a payment lock.
  Configuration Issues: There may be configuration issues in the pricing procedure or condition records that lead to this inconsistency.
  Data Entry Errors: Manual data entry errors when creating or modifying condition records can lead to this situation.
  
  Solution:
  
  
  Review Condition Records: Check the condition records for the item in question. Ensure that the condition type is appropriate for payment conditions. If it is not, you may need to change the condition type or remove the payment lock.
  
  
  Adjust Payment Lock: If the condition type is correct, consider removing the payment lock from the condition item. This can usually be done in the condition record maintenance transaction (e.g., using transaction code VK11 or VK12).
  
  
  Check Configuration: Review the configuration of the pricing procedure in the SAP system. Ensure that the condition types are correctly defined and that the payment conditions are set up properly.
  
  
  Consult Documentation: Refer to SAP documentation or help resources for specific guidance on the condition types and their configurations.
  
  
  Testing: After making changes, perform tests to ensure that the error does not reoccur and that the pricing behaves as expected.
  
  
  Related Information:
  
  Transaction Codes: Familiarize yourself with relevant transaction codes such as VK11 (Create Condition), VK12 (Change Condition), and VK13 (Display Condition) for managing condition records.
  SAP Notes: Check SAP Notes for any known issues or patches related to this error message. SAP Notes can provide insights into specific bugs or configuration recommendations.
  User Roles and Authorizations: Ensure that the user has the necessary authorizations to make changes to condition records and pricing procedures.
  
  If the issue persists after following these steps, it may be beneficial to consult with your SAP support team or a functional consultant who specializes in SAP Financial Services for further assistance.