How To Fix FTVV_MESSAGES427 - Partner blocked by dunning run; relevant dunning data cannot be changed

SAP Error Message - Details

• Message type: E = Error

• Message class: FTVV_MESSAGES - Reporting Financial Assets Management

• Message number: 427

• Message text: Partner blocked by dunning run; relevant dunning data cannot be changed

What causes this issue?

The partner is due to be included in a dunning run.

System Response

The system issues an error message and will not allow you to continue with this transaction until the error is resolved.

How to fix this error?

You can only make a change if the dunning selection is reset or if the
dunning print job has been completed.

Procedure for System Administrators

Error message extract from SAP system. Copyright SAP SE.

Smart SAP Assistant

• What is the cause and solution for SAP error message FTVV_MESSAGES427 - Partner blocked by dunning run; relevant dunning data cannot be changed ?

  The SAP error message FTVV_MESSAGES427 indicates that a partner (usually a customer or vendor) is blocked due to a dunning run, which means that the system has processed a dunning run for that partner, and as a result, certain dunning-related data cannot be changed until the block is lifted.
  Cause:
  
  Dunning Run Processed: The primary cause of this error is that a dunning run has been executed for the partner in question. During this process, the system locks the dunning data to prevent changes that could lead to inconsistencies.
  Blocked Status: The partner may have been set to a blocked status due to overdue payments or other reasons, which is often a part of the dunning process.
  
  Solution:
  To resolve this error, you can take the following steps:
  
  
  Check Dunning Run Status:
  
  Verify if a dunning run has indeed been executed for the partner. You can check the dunning run logs or reports to confirm this.
  
  
  
  Unblock the Partner:
  
  If the partner is blocked due to dunning, you may need to unblock them. This can typically be done in the customer or vendor master data by changing the status.
  Navigate to the relevant transaction (e.g., FD02 for customers or FK02 for vendors) and check the dunning information.
  
  
  
  Wait for Dunning Process Completion:
  
  If the dunning run is still in process or has just been completed, you may need to wait until the system releases the lock on the dunning data.
  
  
  
  Adjust Dunning Parameters:
  
  If you need to change dunning data, consider adjusting the dunning parameters or settings in the dunning configuration (transaction OBD2 for dunning areas).
  
  
  
  Consult with SAP Support:
  
  If the issue persists or if you are unsure about the steps to take, it may be beneficial to consult with your SAP support team or refer to SAP Notes for specific guidance related to your version of SAP.
  
  
  
  Related Information:
  
  Dunning Process: Understand how the dunning process works in SAP, including the configuration of dunning levels, dunning notices, and how they affect customer/vendor accounts.
  Transaction Codes: Familiarize yourself with relevant transaction codes such as F150 (Dunning) and FD02/FK02 (Change Customer/Vendor).
  SAP Documentation: Refer to SAP Help documentation for detailed information on dunning management and error handling.
  
  By following these steps, you should be able to resolve the error and manage the dunning data for the affected partner effectively.