How To Fix FTCM215 - No payment request were generated from the advice selection

SAP Error Message - Details

• Message type: E = Error

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

• Message number: 215

• Message text: No payment request were generated from the advice selection

What causes this issue?

No payment requests could be created from the selection of payment
advice.

System Response

Please restart the selection after reviewing the selection criterion
and the selection requirements.

How to fix this error?

Selection might be set to execute in test mode to confirm the selection
problem. Review that the targeted advice can be selected with the
payment advice display transaction FF6A. Addtionally, the targeted
advice must be marked as authorized with transaction FFW1.

Procedure for System Administrators

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

Error message extract from SAP system. Copyright SAP SE.

Smart SAP Assistant

• What is the cause and solution for SAP error message FTCM215 - No payment request were generated from the advice selection ?

  The SAP error message FTCM215, which states "No payment request were generated from the advice selection," typically occurs in the context of the SAP Treasury and Risk Management module, particularly when dealing with payment advice processing. This error indicates that the system was unable to generate any payment requests based on the selected payment advice.
  Causes:
  
  Selection Criteria Issues: The criteria used to select payment advices may not match any existing records. This could be due to incorrect date ranges, company codes, or other filters.
  Missing Payment Advice: There may be no payment advices available for the selected parameters, meaning there are no records to process.
  
  Configuration Issues: The configuration settings for payment advice processing may not be set up correctly, leading to issues in generating payment requests.
  Data Inconsistencies: There may be inconsistencies or missing data in the underlying financial documents that prevent the generation of payment requests.
  Authorization Issues: The user may not have