How To Fix G00636 - Neither journal entries nor totals data were selected; please check

SAP Error Message - Details

• Message type: E = Error

• Message class: G00 - SAP Consolidation

• Message number: 636

• Message text: Neither journal entries nor totals data were selected; please check

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 G00636 - Neither journal entries nor totals data were selected; please check ?

  The SAP error message G00636, which states "Neither journal entries nor totals data were selected; please check," typically occurs when you are trying to execute a report or transaction that requires financial data, but the system cannot find any relevant entries to display. This can happen for several reasons. Here’s a breakdown of potential causes, solutions, and related information:
  Causes:
  
  No Data Available: The most straightforward reason is that there are no journal entries or totals data available for the specified selection criteria (e.g., date range, company code, account, etc.).
  Incorrect Selection Criteria: The parameters you entered in the selection screen may not match any existing data. This could include incorrect date ranges, account numbers, or other filters.
  Data Not Posted: If the financial transactions have not been posted yet, there will be no data to retrieve.
  Authorization Issues: Lack of proper authorization to view certain data can also lead to this error.
  Data Archiving: If the data has been archived, it may not be available for reporting unless the archive is accessed.
  
  Solutions:
  
  Check Selection Criteria: Review the selection criteria you have entered. Ensure that the date range, company code, and other filters are correct and that they correspond to the data you expect to see.
  Verify Data Posting: Ensure that the relevant journal entries have been posted in the system. You can check this in the relevant transaction (e.g., FB03 for viewing documents).
  Expand Date Range: If you are using a narrow date range, try expanding it to see if any data appears.
  Check Authorizations: Ensure that you have the necessary authorizations to view the data. You may need to consult with your SAP security team.
  Review Archived Data: If you suspect that the data might have been archived, check with your SAP Basis team to see if the data can be retrieved from the archive.
  Use Different Reports: If the report you are using is not yielding results, consider using alternative reports or transactions that might provide the information you need.
  
  Related Information:
  
  Transaction Codes: Familiarize yourself with relevant transaction codes such as:
  
  FB03: Display Document
  FBL1N: Vendor Line Item Display
  FBL3N: G/L Account Line Item Display
  FBL5N: Customer Line Item Display
  
  
  SAP Notes: Check SAP Notes for any known issues or patches related to this error message.
  Documentation: Review SAP documentation or help files for the specific report or transaction you are using to understand its requirements better.
  
  If the issue persists after trying the above solutions, it may be beneficial to consult with your SAP support team or a functional consultant who can provide more tailored assistance based on your specific SAP environment and configuration.