How To Fix GI373 - The next or previous data record cannot be displayed

GI373 - Overview

• Message type: E = Error

• Message class: GI - FI-SL update

• Message number: 373

• Message text: The next or previous data record cannot be displayed

What causes this issue?

You cannot display the next or previous data record, since the
organizational unit cannot be uniquely determined. In the overview
list, the organizational unit (company code or global company) is
suppressed and a derivation is not possible, since the selection for
the organizational unit is not unique.

System Response

The desired action cannot be executed.

How to fix this error?

Display the organizational unit in the overview list or select one
organizational unit in the selection screen.

Procedure for System Administrators

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

Error message extract from SAP system. Copyright SAP SE.

Smart SAP Assistant

• What is the cause and solution for SAP error message GI373 - The next or previous data record cannot be displayed ?

  The SAP error message GI373, which states "The next or previous data record cannot be displayed," typically occurs when a user attempts to navigate through records in a transaction or report, but the system cannot find the next or previous record to display. This can happen for several reasons:
  Causes:
  
  Data Record Deletion: The record you are trying to access may have been deleted or is no longer available in the database.
  Authorization Issues: The user may not have the necessary authorizations to view certain records.
  Filters or Selection Criteria: The current selection criteria or filters applied may not match any existing records, leading to an inability to navigate.
  Transaction State: The transaction may be in a state where it cannot navigate to the next or previous record, such as being in a modal dialog or an incomplete transaction.
  Buffer Issues: Sometimes, the buffer may not be updated correctly, leading to inconsistencies in record navigation.
  
  Solutions:
  
  Check Record