How To Fix FKKEXC110 - No data was selected for the cash desk closing

SAP Error Message - Details

• Message type: E = Error

• Message class: FKKEXC - Message Class for External Payments

• Message number: 110

• Message text: No data was selected for the cash desk closing

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 FKKEXC110 - No data was selected for the cash desk closing ?

  The SAP error message FKKEXC110 ("No data was selected for the cash desk closing") typically occurs in the context of the SAP Contract Accounts Receivable and Payable (FI-CA) module when attempting to perform a cash desk closing operation. This error indicates that the system did not find any relevant data to process for the cash desk closing.
  Causes:
  
  No Transactions Recorded: There may be no transactions recorded in the cash desk for the period you are trying to close.
  Incorrect Selection Criteria: The selection criteria used for the cash desk closing might be too restrictive or incorrect, leading to no data being selected.
  Cash Desk Not Opened: The cash desk may not have been opened for the period in question, or it may have already been closed.
  Data Posting Issues: There could be issues with data posting, such as missing or incomplete entries that prevent the system from recognizing any transactions.
  Configuration Issues: There may be configuration issues in the cash desk settings or in the FI-CA module that prevent data from being selected.
  
  Solutions:
  
  Check Transactions: Verify that there are transactions recorded in the cash desk for the period you are trying to close. You can do this by reviewing the cash desk entries.
  Review Selection Criteria: Ensure that the selection criteria you are using for the cash desk closing are correct and not overly restrictive. Adjust the criteria if necessary.
  Open Cash Desk: Confirm that the cash desk is open for the period you are trying to close. If it is closed, you may need to reopen it or check the closing status.
  Data Integrity: Check for any data integrity issues. Ensure that all necessary postings have been completed and that there are no missing entries.
  Configuration Review: Review the configuration settings for the cash desk and the FI-CA module to ensure everything is set up correctly. Consult with your SAP administrator or functional consultant if needed.
  Consult Documentation: Refer to SAP documentation or help resources for additional guidance on cash desk closing procedures and troubleshooting.
  
  Related Information:
  
  Transaction Codes: Familiarize yourself with relevant transaction codes such as FPAYH (for cash desk closing) and FPL9 (for cash desk overview).
  SAP Notes: Check SAP Notes for any known issues or patches related to this error message.
  User Authorization: Ensure that you have the necessary authorizations to perform cash desk closing operations.
  Support: If the issue persists, consider reaching out to SAP support or your internal IT support team 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.