How To Fix G00602 - No journal entry records were read

SAP Error Message - Details

• Message type: E = Error

• Message class: G00 - SAP Consolidation

• Message number: 602

• Message text: No journal entry records were read

What causes this issue?

You did not specify a valie file name for the journal entry file. No
journal entries were read.

System Response

The system issues an error message and will not allow you to continue with this transaction until the error is resolved.

How to fix this error?

Procedure for System Administrators

Error message extract from SAP system. Copyright SAP SE.

Smart SAP Assistant

• What is the cause and solution for SAP error message G00602 - No journal entry records were read ?

  The SAP error message G00602, which states "No journal entry records were read," typically occurs when a user attempts to access or process journal entries in the General Ledger (G/L) but the system does not find any relevant records to display or process. This can happen for several reasons. Below are some common causes, potential solutions, and related information:
  Causes:
  
  No Data Available: There may simply be no journal entries recorded for the specified criteria (e.g., date range, company code, etc.).
  Selection Criteria: The selection criteria used in the report or transaction may be too restrictive, leading to no records being found.
  Authorization Issues: The user may not have the necessary authorizations to view the journal entries.
  Data Posting Issues: Journal entries may not have been posted correctly or may have been deleted.
  System Configuration: There may be configuration issues in the G/L settings that prevent journal entries from being displayed.
  
  Solutions:
  
  Check Data Availability: Verify that there are indeed journal entries posted for the specified criteria. You can do this by checking the relevant tables (e.g., BKPF for document headers and BSEG for document line items).
  Adjust Selection Criteria: Review and adjust the selection criteria in the report or transaction to ensure it is not too restrictive. For example, broaden the date range or remove filters.
  Review Authorizations: Ensure that the user has the necessary authorizations to access the journal entries. This can be checked in the user roles and profiles.
  Verify Posting: Check if the journal entries were posted correctly. You can look for any error messages during the posting process or check the status of the entries.
  Consult Configuration: If the issue persists, consult with your SAP Basis or configuration team to review the G/L settings and ensure everything is configured correctly.
  
  Related Information:
  
  Transaction Codes: Common transaction codes related to journal entries include:
  
  FB03: Display Document
  FBL3N: G/L Account Line Item Display
  FBL1N: Vendor 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: Refer to SAP documentation for detailed information on G/L accounting and journal entries.
  
  If the problem persists after trying the above solutions, it may be beneficial to consult with your SAP support team or reach out to SAP support for further assistance.