How To Fix GG518 - (Texte desc.) Seule entrée du compteur enreg.collecté prise en compte !

SAP Error Message - Details

• Message type: E = Error

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

• Message number: 518

• Message text: (Texte desc.) Seule entrée du compteur enreg.collecté prise en compte !

Quelle est la cause de ce problème?

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.

Réponse du système

Le système émet un message d'erreur et ne vous permettra pas de poursuivre cette transaction tant que l'erreur n'est pas résolue.

Comment corriger cette erreur?

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.

Extrait du message d'erreur du système SAP. Copyright SAP SE.