FKK_RTP070 - Payment document &1 not found for branch/cash desk &2/&3

SAP Error Message - Details

• Message type: E = Error

• Message class: FKK_RTP -

• Message number: 070

• Message text: Payment document &1 not found for branch/cash desk &2/&3

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_RTP070 - Payment document &1 not found for branch/cash desk &2/&3 ?

  The SAP error message FKK_RTP070 indicates that a payment document could not be found for a specific branch and cash desk combination. This error typically occurs in the context of the SAP Convergent Charging or SAP Contract Accounts Receivable and Payable (FI-CA) modules, where payment processing is involved.
  Cause:
  
  
  Missing Payment Document: The payment document referenced in the error message does not exist in the system. This could be due to:
  
  The document was never created.
  The document was deleted or archived.
  The document was created in a different branch or cash desk.
  
  
  
  Incorrect Configuration: There may be configuration issues related to the branch or cash desk settings in the system.
  
  
  Data Entry Errors: The branch or cash desk identifiers may have been entered incorrectly, leading to a mismatch.
  
  
  Authorization Issues: The user may not have the necessary permissions to view the payment document.
  
  
  Solution:
  
  
  Verify Document Existence:
  
  Check if the payment document exists in the system. You can do this by using transaction codes like FBL5N (Customer Line Item Display) or FBL1N (Vendor Line Item Display) to search for the document.
  
  
  
  Check Branch and Cash Desk Configuration:
  
  Ensure that the branch and cash desk settings are correctly configured in the system. You can review the configuration in the relevant customizing settings (transaction code SPRO).
  
  
  
  Correct Data Entry:
  
  Double-check the input values for the branch and cash desk to ensure they are correct. Make sure there are no typos or incorrect codes.
  
  
  
  Review User Authorizations:
  
  Ensure that the user has the necessary authorizations to access the payment document. This may involve checking roles and permissions in the user profile.
  
  
  
  Consult Logs and Traces:
  
  If the issue persists, check the application logs (transaction code SLG1) for any additional error messages or information that could provide more context.
  
  
  
  Contact Support:
  
  If you are unable to resolve the issue, consider reaching out to your SAP support team or consulting SAP Notes for any known issues related to this error message.
  
  
  
  Related Information:
  
  Transaction Codes: Familiarize yourself with relevant transaction codes such as FBL5N, FBL1N, SPRO, and SLG1 for troubleshooting.
  SAP Notes: Search for SAP Notes related to the error message FKK_RTP070 in the SAP Support Portal for any patches or updates that may address the issue.
  Documentation: Review the SAP documentation for the FI-CA module to understand the payment processing workflow and related configurations.
  
  By following these steps, you should be able to identify the cause of the error and implement a solution.