How To Fix FKKEXC009 - Unable to save payments of cash desk &1/&2 in system

SAP Error Message - Details

• Message type: E = Error

• Message class: FKKEXC - Message Class for External Payments

• Message number: 009

• Message text: Unable to save payments of cash desk &1/&2 in system

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 FKKEXC009 - Unable to save payments of cash desk &1/&2 in system ?

  The SAP error message FKKEXC009 ("Unable to save payments of cash desk &1/&2 in system") typically occurs in the context of the SAP Contract Accounts Receivable and Payable (FI-CA) module. This error indicates that there is an issue preventing the system from saving payment transactions related to a specific cash desk.
  Possible Causes:
  
  Configuration Issues: There may be incorrect or incomplete configuration settings for the cash desk in the system.
  Authorization Problems: The user may not have the necessary authorizations to perform the payment transaction.
  Data Inconsistencies: There could be inconsistencies or missing data in the payment documents or related master data.
  System Errors: Temporary system issues or bugs may also lead to this error.
  Open Items: There may be open items that need to be cleared before the payment can be processed.
  
  Solutions:
  
  
  Check Configuration:
  
  Verify the configuration settings for the cash desk in the SAP system. Ensure that all necessary parameters are correctly set up.
  Check the cash desk settings in transaction code OBY6 or OBA7.
  
  
  
  Review Authorizations:
  
  Ensure that the user has the appropriate authorizations to execute payment transactions. This can be checked using transaction code SU53 after the error occurs.
  
  
  
  Validate Data:
  
  Check the payment document for any missing or incorrect data. Ensure that all required fields are filled out correctly.
  Review related master data (e.g., customer accounts) for any inconsistencies.
  
  
  
  Check for System Issues:
  
  Look for any system messages or logs that might indicate a temporary issue. You can check transaction SM21 for system logs or ST22 for dumps.
  If the issue persists, consider restarting the session or checking with your SAP Basis team for any ongoing system issues.
  
  
  
  Clear Open Items:
  
  If there are open items that need to be cleared, address those first. You can use transaction FBL1N or FBL5N to review open items for vendors or customers.
  
  
  
  Consult SAP Notes:
  
  Search for relevant SAP Notes in the SAP Support Portal that may address this specific error message. There may be patches or updates available that resolve known issues.
  
  
  
  Related Information:
  
  Transaction Codes: Familiarize yourself with relevant transaction codes such as F-28 (Post Incoming Payments), F-32 (Clear Customer), and F-53 (Post Outgoing Payments).
  Documentation: Review SAP documentation related to FI-CA and cash desk management for best practices and troubleshooting steps.
  Support: If the issue cannot be resolved internally, consider reaching out to SAP Support for further assistance.
  
  By following these steps, you should be able to identify the root cause of the error and implement a solution to resolve it.