How To Fix FVD_COND_VERIFIER_D068 - Condition item & for payment to 3rd party but contains alt. dunning lock

SAP Error Message - Details

• Message type: E = Error

• Message class: FVD_COND_VERIFIER_D - Condition Verifier

• Message number: 068

• Message text: Condition item & for payment to 3rd party but contains alt. dunning lock

What causes this issue?

The condition item with condition type &V1& and condition type key &V2&,
effective from &V3&, is specified as a third party payment. However, a
dunning lock has been entered, which is contrary to the settings in
Customizing.

System Response

The loan conditions contain errors and therefore cannot be saved.

How to fix this error?

Remove the condition item in question from the loan conditions, or set
the correct dunning lock in Customizing for Loans Management in the
activity <DS:SIMG.PROD_PRO_BUKRS>Company Code-Dependent Settings for
Product Type</>.
If this is not possible in your user interface, contact your system
administrator.

Procedure for System Administrators

The complete key for the condition item is &V4&.

Error message extract from SAP system. Copyright SAP SE.

Smart SAP Assistant

• What is the cause and solution for SAP error message FVD_COND_VERIFIER_D068 - Condition item & for payment to 3rd party but contains alt. dunning lock ?

  The SAP error message FVD_COND_VERIFIER_D068 typically indicates an issue related to the condition item for a payment to a third party, specifically when there is an alternative dunning lock in place. This error can arise in the context of financial transactions, particularly in accounts receivable or accounts payable processes.
  Cause:
  The error message suggests that there is a conflict due to an alternative dunning lock on the condition item. This can occur for several reasons:
  
  Dunning Lock: The customer or vendor has a dunning lock that prevents further processing of payments or invoices.
  Condition Item Configuration: The condition item may not be properly configured to allow for payments to third parties when a dunning lock is present.
  Data Inconsistency: There may be inconsistencies in the master data or transaction data that are causing the system to reject the payment.
  
  Solution:
  To resolve the error, you can take the following steps:
  
  
  Check Dunning Lock:
  
  Review the customer or vendor master data to see if there is a dunning lock in place. You can do this by navigating to the customer or vendor account in SAP and checking the dunning information.
  If a dunning lock exists and is not necessary, consider removing it if it aligns with your business processes.
  
  
  
  Review Condition Item Configuration:
  
  Check the configuration of the condition item in the pricing procedure. Ensure that it is set up correctly to allow payments to third parties even when a dunning lock is present.
  Consult with your SAP configuration team to verify that the condition types and pricing procedures are correctly defined.
  
  
  
  Data Consistency Check:
  
  Perform a consistency check on the relevant master data and transaction data. Look for any discrepancies that might be causing the error.
  Use transaction codes like SE16 or SE11 to analyze the relevant tables for any inconsistencies.
  
  
  
  Consult SAP Notes:
  
  Search for relevant SAP Notes that may address this specific error message. SAP frequently updates its knowledge base with solutions for known issues.
  
  
  
  Testing:
  
  After making any changes, conduct tests to ensure that the error no longer occurs and that payments can be processed as expected.
  
  
  
  Related Information:
  
  
  Transaction Codes: Familiarize yourself with relevant transaction codes such as:
  
  FD32: Change Customer Credit Management
  FK02: Change Vendor
  FBL1N: Vendor Line Item Display
  FBL5N: Customer Line Item Display
  
  
  
  Documentation: Review SAP documentation related to dunning procedures and condition items to better understand how they interact.
  
  
  Support: If the issue persists after following the above steps, consider reaching out to your SAP support team or consulting with SAP experts for further assistance.
  
  
  By following these steps, you should be able to identify the root cause of the error and implement a solution to resolve it.