How To Fix G00602 - No journal entry records were read

G00602 - Overview

• 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