How To Fix GI222 - Verbuchungsproblem in der Summentabelle & durch Feldüberlauf

SAP Error Message - Details

• Message type: E = Error

• Message class: GI - FI-SL update

• Message number: 222

• Message text: Verbuchungsproblem in der Summentabelle & durch Feldüberlauf

Was verursacht dieses Problem?

Table &V1& can only store values up to a defined maximum value for each
period in its currency and quantity fields. This value depends on the
length of the respective field in the totals table. Depending on the
totals table and component, the length of these fields normally varies
between 15, 17, and 23 characters.
Program termination was triggered because the maximum value for the
field was exceeded by the last posting transaction. The system attempted
to enter a value into one of the currency or quantity fields of totals
table &V1&.
This attempt failed because the calculation result exceeded the value
range of the target field in table &V1&.
The following arithmetic operation was performed for table &V1& with
account assignment
(ledger / record type / company code / year / period (RPMAX) / account
number):
&V2& :
*
* &V3& field
* Name of target field = current content of target field in the database
+ value to be updated
*
<ZH>Additional Helpful Information for Analyzing Runtime Errors:</>
*
* &V4&
*
Explanation
ACC = 'BAL': The account is a balance sheet account but not a retained
earnings account.
ACC = 'PRO': The account is a P<(>&<)>L account.
ACC = 'RET': The account is a retained earnings account.
ACC = 'NONE': The standard field for the account number (RACCT) does not
exist in the totals table.
ACC = 'MAST': The account number is available in the master data.
FLD = Field length of target field
LDR = 'X': The ledger in question is a standard ledger.
LDR = '_': The ledger in question is not a standard ledger. The ledger
was created in Customizing.
NewGL = 'X': The table is a table from new General Ledger Accounting.
NewGL = '_': The table is not a table from new General Ledger
Accounting.

Das System gibt eine Fehlermeldung aus und erlaubt Ihnen nicht, mit dieser Transaktion fortzufahren, bis der Fehler behoben ist.

Systemantwort

The update was terminated with a runtime error.

Wie behebe ich diesen Fehler?

Because the totals tables belong to different applications and
components, the solution to the problem will also be application-spec
ific.
Therefore, the approach to the solution must be discussed with the
relevant department. The following points must be clarified first:
Which component uses the totals table?
Which processes update the totals table?
The component can be identified using the totals table &V1& and the
assigned ledger. The processes that update this ledger must be clarified
with the department that uses the ledger.
The currency and quantity fields can only be extended to a maximum of 23
characters without problems in customer-defined tables of component
FI-SL using transaction GCIN. Even here, the fields must not be extended
under time pressure and only by an experienced SAP consultant.
Otherwise, data may be lost.
For all other components, the currency or quantity fields cannot be
extended or can only be extended as a modification.
Therefore, alternative solutions should be sought first. The following
procedure is helpful for the analysis:
<ZH>* Further analysis:</>
You can display the amounts for the account assignment ledger / record
type / company code / year / period / account number using transaction
SE16 (for all tables), transaction GD12 (for tables from new General
Ledger Accounting), or transaction GD13 (for FI-SL tables) &V2&.
Multiple data records may be displayed. It is likely that at least one
record contains a high value in the field specified above.
Analyze the causes of very high values within an account. You may be
able to discover what is contributing to this high amount by drilling
down to the line items (if they exist).
Check whether it is necessary from a business perspective to combine
these values in one or a few accounts.
Check whether the problem can be solved by splitting the account in
question into multiple accounts. Also check whether the account can be
split by other key values because different account assignment fields
(profit center, business area, and so on) are available for different
table groups.
Check whether it is possible to solve the problem by generating negative
postings (see BSEG-XNEGP). A negative posting enables the transaction
figures for the account to be reset on the original side of the account
(debit or credit) when a reversal is carried out.
If the runtime error was caused by a posting to period zero, this
posting was probably generated by a balance carryforward routine.
In this case, you need to check whether the account is a normal balance
sheet account or a retained earnings account (see "Additional Helpful
Information for Analyzing Runtime Errors").
Because several P<(>&<)>L accounts can be carried forward in one
retained earnings account, you need to check whether another retained
earnings account can be assigned for particular P<(>&<)>L accounts.
For more application-specific information, see SAP Note 1814914.

Fehlermeldungsextrakt aus SAP-System. Copyright SAP SE