How To Fix FVD_COND_VERIFIER050 - Condition item is not a payment condition but contains bank details

SAP Error Message - Details

• Message type: E = Error

• Message class: FVD_COND_VERIFIER - Condition Verifier

• Message number: 050

• Message text: Condition item is not a payment condition but contains bank details

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_VERIFIER050 - Condition item is not a payment condition but contains bank details ?

  The SAP error message FVD_COND_VERIFIER050 indicates that there is an issue with a condition item in a financial transaction. Specifically, the error states that the condition item is not recognized as a payment condition, yet it contains bank details. This can occur in various scenarios, such as during the processing of payment conditions in financial documents or when configuring payment terms.
  Cause:
  
  Incorrect Configuration: The condition item may be incorrectly configured in the system. It might be set up as a non-payment condition but still has bank details associated with it.
  Data Entry Error: There could be a mistake in the data entry where bank details were inadvertently linked to a condition item that should not have them.
  Custom Development: If there are custom developments or enhancements in the SAP system, they might be causing this inconsistency.
  Master Data Issues: The master data for the vendor or customer might not be correctly set up, leading to this error when processing transactions.
  
  Solution:
  
  
  Review Condition Configuration:
  
  Go to the condition configuration in the SAP system (transaction code: V/06 for pricing conditions).
  Check the settings for the condition type in question and ensure that it is correctly defined as a payment condition if it is intended to be one.
  
  
  
  Remove Bank Details:
  
  If the condition item is not supposed to have bank details, remove any associated bank details from the condition item.
  This can typically be done in the transaction where the condition is being processed.
  
  
  
  Check Master Data:
  
  Review the master data for the relevant vendor or customer to ensure that payment terms and conditions are correctly set up.
  Ensure that the payment methods and bank details are correctly assigned.
  
  
  
  Consult Documentation:
  
  Refer to SAP documentation or help resources for specific guidance on the condition types and their configurations.
  
  
  
  Debugging:
  
  If the issue persists, consider debugging the transaction to identify where the error is being triggered. This may require assistance from a technical consultant.
  
  
  
  Contact SAP Support:
  
  If you are unable to resolve the issue, consider reaching out to SAP support for further assistance, especially if this is a recurring problem.
  
  
  
  Related Information:
  
  Transaction Codes: Familiarize yourself with relevant transaction codes such as V/06 (Condition Types), VK11 (Create Condition), and VK12 (Change Condition).
  SAP Notes: Check for any SAP Notes related to this error message, as they may provide specific fixes or patches.
  User Forums: Engage with SAP community forums or user groups where similar issues may have been discussed.
  
  By following these steps, you should be able to identify the root cause of the error and implement a solution to resolve it.