How To Fix FDM_COLLECTION059 - There are no promises to pay to be confirmed

SAP Error Message - Details

• Message type: E = Error

• Message class: FDM_COLLECTION - SAP Collections Management

• Message number: 059

• Message text: There are no promises to pay to be confirmed

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 FDM_COLLECTION059 - There are no promises to pay to be confirmed ?

  The SAP error message FDM_COLLECTION059 indicates that there are no promises to pay that need to be confirmed in the context of the Collections Management module. This typically occurs when a user attempts to confirm a payment promise in the system, but there are no existing payment promises available for confirmation.
  Causes:
  
  No Payment Promises Created: There may not be any payment promises entered in the system for the customer or account in question.
  Incorrect Selection Criteria: The user may be looking in the wrong area or using incorrect filters that do not match any existing payment promises.
  Data Synchronization Issues: There could be a delay or issue in data synchronization between different modules or systems, leading to the absence of expected payment promises.
  User Authorization: The user may not have the necessary permissions to view or confirm payment promises.
  
  Solutions:
  
  Check for Existing Payment Promises: Verify if there are any payment promises created for the customer or account. This can be done by navigating to the relevant transaction or report that lists payment promises.
  Review Selection Criteria: Ensure that the correct filters and selection criteria are being used when searching for payment promises. Adjust the parameters to broaden the search if necessary.
  Create Payment Promises: If there are no payment promises, consider creating them as needed. This can be done through the appropriate transaction in the Collections Management module.
  Check User Permissions: Ensure that the user has the necessary authorizations to view and confirm payment promises. If not, contact your system administrator to adjust permissions.
  Data Refresh: If there are known synchronization issues, it may be necessary to refresh the data or check for any background jobs that need to be completed.
  
  Related Information:
  
  Transaction Codes: Familiarize yourself with relevant transaction codes in SAP for managing payment promises, such as FDM_COLL for collections management.
  Documentation: Refer to SAP Help documentation for Collections Management for detailed guidance on managing payment promises.
  Support: If the issue persists, consider reaching out to your SAP support team or consulting the SAP community forums for additional assistance.
  
  By following these steps, you should be able to identify the cause of the error and take appropriate action to resolve it.