FKK_RTP046 - 20: Payment posted, bank was not yet informed

SAP Error Message - Details

• Message type: E = Error

• Message class: FKK_RTP -

• Message number: 046

• Message text: 20: Payment posted, bank was not yet informed

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 FKK_RTP046 - 20: Payment posted, bank was not yet informed ?

  The SAP error message FKK_RTP046 ("Payment posted, bank was not yet informed") typically occurs in the context of the SAP Contract Accounts Receivable and Payable (FI-CA) module. This error indicates that a payment has been posted in the system, but the corresponding notification to the bank regarding this payment has not yet been sent.
  Cause:
  
  Timing Issue: The payment might have been posted in the system, but the process to inform the bank (e.g., through a payment file or direct communication) has not been executed yet.
  Configuration Issues: There may be configuration settings in the payment processing that are not set up correctly, preventing the system from sending the notification to the bank.
  Batch Job Not Executed: If the system relies on batch jobs to send payment notifications, the relevant job may not have been executed or may have failed.
  Manual Intervention Required: Sometimes, manual steps are required to trigger the notification to the bank, and these may have been overlooked.
  
  Solution:
  
  Check Payment Processing: Verify that the payment has been correctly processed and that all necessary steps have been completed.
  Run Batch Jobs: If applicable, check if there are any batch jobs that need to be executed to inform the bank. Ensure that these jobs are scheduled and running as expected.
  Review Configuration: Check the configuration settings related to payment processing and bank communication in the SAP system. Ensure that all necessary parameters are correctly set.
  Manual Notification: If the system does not automatically notify the bank, you may need to manually send the payment notification or file to the bank.
  Consult Documentation: Refer to SAP documentation or your organization's internal guidelines for handling payment notifications to banks.
  
  Related Information:
  
  Transaction Codes: You may want to use transaction codes like FBL1N (Vendor Line Item Display) or FBL5N (Customer Line Item Display) to check the status of the payment.
  Logs and Monitoring: Check the application logs (transaction code SLG1) for any errors or warnings related to payment processing and bank notifications.
  SAP Notes: Look for relevant SAP Notes that may address this specific error or provide additional troubleshooting steps.
  Support: If the issue persists, consider reaching out to your SAP support team or consulting with SAP support for further assistance.
  
  By following these steps, you should be able to identify the cause of the error and implement a solution to resolve it.