How To Fix FTVV_MESSAGES117 - Payment block was set

SAP Error Message - Details

• Message type: E = Error

• Message class: FTVV_MESSAGES - Reporting Financial Assets Management

• Message number: 117

• Message text: Payment block was set

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 FTVV_MESSAGES117 - Payment block was set ?

  The SAP error message FTVV_MESSAGES117 indicates that a payment block has been set on a vendor or invoice, preventing the payment from being processed. This is a common issue in SAP systems, particularly in the Accounts Payable module.
  Cause:
  The payment block can be set for various reasons, including but not limited to:
  
  Vendor Master Data: The vendor may have a payment block set in their master data.
  Invoice Verification: The invoice may have been flagged for a payment block during the invoice verification process.
  Payment Terms: Specific payment terms may impose restrictions that lead to a payment block.
  Approval Processes: The invoice may require approval before payment can be processed, leading to a temporary block.
  Discrepancies: There may be discrepancies between the invoice and the purchase order or goods receipt, leading to a payment block.
  
  Solution:
  To resolve the issue, you can take the following steps:
  
  
  Check Vendor Master Data:
  
  Go to the vendor master record (transaction code XK03 or MK03) and check if a payment block is set. If it is, you may need to remove it (transaction code XK02 or MK02) if you have the necessary permissions.
  
  
  
  Review Invoice Details:
  
  Check the invoice in the system (transaction code MIRO for invoice verification) to see if there are any flags or blocks set. Look for any discrepancies that need to be resolved.
  
  
  
  Examine Payment Terms:
  
  Review the payment terms associated with the invoice to ensure they are correct and do not impose unnecessary restrictions.
  
  
  
  Approval Workflow:
  
  If the invoice is pending approval, follow up with the relevant personnel to expedite the approval process.
  
  
  
  Consult with Finance Team:
  
  If you are unsure about the reason for the payment block, consult with your finance or accounts payable team for further insights.
  
  
  
  Transaction Codes:
  
  Use transaction codes like FBL1N (Vendor Line Item Display) to check the status of the vendor's open items and see if there are any payment blocks.
  
  
  
  Related Information:
  
  Payment Block Types: SAP allows different types of payment blocks (e.g., manual, automatic) that can be set based on business rules.
  Configuration: Payment blocks can be configured in the SAP system, and understanding the configuration settings may help in troubleshooting.
  Documentation: Refer to SAP Help documentation or your organization's internal documentation for specific guidelines on handling payment blocks.
  
  By following these steps, you should be able to identify the cause of the payment block and take appropriate action to resolve the issue.