How To Fix GG518 - (Longtext) Only the collect counter entry will be included.

SAP Error Message - Details

• Message type: E = Error

• Message class: GG - Messages for FI-SL customizing

• Message number: 518

• Message text: (Longtext) Only the collect counter entry will be included.

What causes this issue?

A field name (most selective field) as well as a maximum number of line
items processed together per collect ("package size") were specified.
According to the current parameters, the uncritical program variant is
generated (see below). That is to say, the program proceeds according
to the collect counter.

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?

The logic of the repair program that is generated and called up is
decisively influenced by an (adequate) choice of parameters:
Entry of a selective field that is a key field (in the transparent
case, "logical") for the line item table as well as the summary table
(default is "RACCT"):
Important:
This logic requires sufficiently large "tablespaces" ("temporary
database spaces"- see Note 2425 for an overview), because each table
access to the line items is "sorted".
In other words, the generated program reads (in the transparent case,
according to the named field) line items sorted. During a value change
in this field, the program adds an internal table to another internal
table which is then inserted in the summary table.
The advantage of this version is that all line items can be processed
in a single program run (provided that the most selective field does
not represent more than approximately 200000 line items per value).
If you have smaller table spaces, take the second, memory-oriented
entry option:
Entry of a number of line items per collect (a good entry would be
about "10000", but bear in mind that an entry in this field causes a
field name entry in 1) to be ignored): The generated repair program
does NOT read sorted and performs a "collect" using an internal table
instead. This logic is generally somewhat faster and gives you the
advantage of being able to choose smaller table spaces than in the
first case.
Disadvantages:
In this version, no more than 100000 summary records from line items to
be processed should be created in each program run. In other words, you
may have to restart the program several times. In light of this, please
keep the following in mind:
To start multiple parallel runs for one table, execute main program
RGUREP01 as the first run. For all further runs, GENERATED program
RGUREP02 must be started. Also remember that the datasets are disjunct.

Error message extract from SAP system. Copyright SAP SE.

Smart SAP Assistant

• What is the cause and solution for SAP error message GG518 - (Longtext) Only the collect counter entry will be included. ?

  The SAP error message GG518 ("Only the collect counter entry will be included.") typically occurs in the context of the SAP system's handling of collective processing, particularly in the area of financial accounting or controlling. This message indicates that during a collective processing operation, only the collect counter entry is being considered, and other entries may not be included in the processing.
  Cause:
  The error can arise due to several reasons, including:
  
  Data Inconsistency: There may be inconsistencies in the data being processed, leading the system to disregard certain entries.
  Configuration Issues: Incorrect configuration settings in the collective processing parameters may lead to this message.
  Selection Criteria: The selection criteria used for the collective processing may be too restrictive, causing only certain entries to be included.
  Status of Entries: The status of the entries being processed may not meet the criteria for inclusion in the collective processing.
  
  Solution:
  To resolve the GG518 error, consider the following steps:
  
  Check Data Consistency: Review the data entries being processed to ensure there are no inconsistencies or errors. Correct any issues found.
  Review Configuration: Check the configuration settings related to collective processing in the relevant module (e.g., Financial Accounting, Controlling) to ensure they are set up correctly.
  Adjust Selection Criteria: Modify the selection criteria used for the collective processing to ensure that it is not too restrictive. This may involve broadening the date range or including additional criteria.
  Verify Entry Status: Ensure that the status of the entries being processed is appropriate for inclusion in the collective processing. For example, entries may need to be in a specific status (e.g., "open") to be included.
  Consult Documentation: Refer to SAP documentation or help resources for specific guidance related to the collective processing function you are using.
  
  Related Information:
  
  Transaction Codes: Depending on the context, you may be using transaction codes like F-02 (Post Document), F-03 (Clear Document), or others related to collective processing.
  SAP Notes: Check for any relevant SAP Notes that may address this specific error message or provide additional troubleshooting steps.
  Support: If the issue persists after trying the above solutions, consider reaching out to SAP support or your internal SAP support team for further assistance.
  
  By following these steps, you should be able to identify the cause of the GG518 error and implement a solution to resolve it.