How To Fix G01164 - Selected volume of data (&1 records) is too big - make packets

G01164 - Overview

• Message type: E = Error

• Message class: G01 - SAP Consolidation

• Message number: 164

• Message text: Selected volume of data (&1 records) is too big - make packets

What causes this issue?

Using the current selection conditions, &V1& data records were read for
processing from table &V2&. This volume of data is too great.
Internally, the system can only process &V3& records per table.

System Response

This processing request cannot be carried out.

How to fix this error?

If necessary, make further restrictions in your data selection to
reduce the volume of data. If this is not possible (for example,
because the check is run automatically), it is recommended to
temporarily <DS:TRAN.CXB3>Deactivate the Consistency Check</>. If this
is done, run a <DS:TRAN.CX1B4>Consistency Check</> and, if necessary, a
database conversion in regular intervals, but always after a critical
breakdown change to a data-carrying FS item. Remember to reactivate
consistency checking beforehand.

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.

G01164 - Details

• The SAP error message G01164 indicates that the volume of data selected for processing is too large, and the system is unable to handle it in a single operation. This typically occurs in scenarios where a large dataset is being processed, such as during data exports, reports, or data transfers.
  
  Cause:
  
  Large Data Volume: The primary cause of this error is that the number of records being processed exceeds the system's limits for a single operation.
  System Configuration: The system may have specific configurations or limitations set for data processing that restrict the number of records that can be handled at once.
  Performance Issues: Attempting to process a large volume of data in one go can lead to performance degradation, which may trigger this error.
  
  
  Solution:
  
  
  Break Down the Data: Instead of processing all records at once, break the data into smaller packets or batches. This can often be done by applying filters or limits to