How To Fix GLE_MCA424 - No documents were selected for company code &1 and fiscal year &2

SAP Error Message - Details

• Message type: E = Error

• Message class: GLE_MCA - Multicurrency Accounting

• Message number: 424

• Message text: No documents were selected for company code &1 and fiscal year &2

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 GLE_MCA424 - No documents were selected for company code &1 and fiscal year &2 ?

  The SAP error message GLE_MCA424 indicates that no documents were selected for a specific company code and fiscal year during a financial operation, such as a closing process or report generation. This error typically arises in the context of financial accounting and controlling modules.
  Cause:
  
  No Transactions: There may be no financial transactions recorded for the specified company code and fiscal year. This could happen if the company code is newly created or if no postings have been made.
  Incorrect Selection Criteria: The selection criteria used in the report or transaction may not match any existing documents. This could include incorrect fiscal year, company code, or other parameters.
  Document Status: The documents may be in a status that excludes them from being selected (e.g., they may be archived or marked for deletion).
  Authorization Issues: The user may not have the necessary authorizations to view the documents for the specified company code and fiscal year.
  Configuration Issues: There may be configuration issues in the financial settings that prevent documents from being selected.
  
  Solution:
  
  Check Transactions: Verify that there are indeed transactions recorded for the specified company code and fiscal year. You can do this by checking the relevant financial documents in the system.
  Review Selection Criteria: Ensure that the selection criteria used in the report or transaction are correct. Double-check the company code, fiscal year, and any other filters applied.
  Document Status: Check the status of the documents. If they are archived or marked for deletion, you may need to restore them or adjust your selection criteria.
  Authorization Check: Ensure that the user has the necessary authorizations to access the documents for the specified company code and fiscal year. This may involve checking user roles and permissions.
  Configuration Review: If the issue persists, review the configuration settings in the financial module to ensure that everything is set up correctly for the company code and fiscal year in question.
  
  Related Information:
  
  Transaction Codes: You can use transaction codes like FB03 (Display Document) or FBL1N (Vendor Line Item Display) to check for existing documents.
  SAP Notes: Check SAP Notes for any known issues or patches related to this error message.
  Documentation: Refer to SAP documentation for financial accounting to understand the implications of the error and the correct setup for company codes and fiscal years.
  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 cause of the error and implement a solution.