How To Fix FTCM216 - No payment requests (PAYRQ) were found for selection

SAP Error Message - Details

• Message type: E = Error

• Message class: FTCM - Electronic Banking and Treasury for US Cash Management

• Message number: 216

• Message text: No payment requests (PAYRQ) were found for selection

What causes this issue?

Payment requests were identified as being created, however a search for
them has failed.

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?

Review the existence of payment requests for the selection of advices.
Post them directly if they are found or restart the generation if not.

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 FTCM216 - No payment requests (PAYRQ) were found for selection ?

  The SAP error message FTCM216 "No payment requests (PAYRQ) were found for selection" typically occurs in the context of the SAP Financial Supply Chain Management (FSCM) module, particularly when dealing with payment requests in the context of the payment processing or payment run.
  Cause:
  
  
  No Payment Requests Created: The most common cause of this error is that there are no payment requests available for the selection criteria you have specified. This could be due to:
  
  No payment requests have been created for the specified date range or selection criteria.
  Payment requests have already been processed or cleared.
  
  
  
  Incorrect Selection Criteria: The selection criteria you are using to filter payment requests may not match any existing records. This could include:
  
  Incorrect company code.
  Incorrect payment method.
  Date range that does not include any existing payment requests.
  
  
  
  Authorization Issues: In some cases, the user may not have the necessary authorizations to view or process the payment requests.
  
  
  Data Issues: There may be data inconsistencies or issues in the underlying tables that store payment request information.
  
  
  Solution:
  
  
  Check Payment Requests: Verify if there are any payment requests created in the system that meet your selection criteria. You can do this by:
  
  Navigating to the relevant transaction (e.g., F110 for automatic payment transactions) and checking the payment request logs.
  Using transaction codes like FBL1N (Vendor Line Item Display) or FBL3N (G/L Account Line Item Display) to see if there are any relevant entries.
  
  
  
  Review Selection Criteria: Ensure that the selection criteria you are using are correct. Double-check:
  
  Company code
  Payment method
  Date range
  Any other filters applied
  
  
  
  Check Authorizations: Ensure that you have the necessary authorizations to view and process payment requests. You may need to contact your SAP security team to verify your access rights.
  
  
  Consult with Technical Support: If you suspect data issues or if the problem persists after checking the above points, it may be necessary to consult with your SAP technical support team or basis team to investigate further.
  
  
  Review Configuration: If you are responsible for system configuration, ensure that the payment request settings are correctly configured in the system.
  
  
  Related Information:
  
  Transaction Codes: Familiarize yourself with relevant transaction codes such as F110 (Automatic Payment Transactions), FBL1N (Vendor Line Item Display), and FBL3N (G/L Account Line Item Display).
  SAP Notes: Check for any relevant SAP Notes that may address known issues or provide additional guidance related to payment requests and the FTCM216 error.
  Documentation: Review SAP documentation related to payment processing in FSCM for best practices and troubleshooting steps.
  
  By following these steps, you should be able to identify the cause of the FTCM216 error and take appropriate action to resolve it.