How To Fix GI219 - Problema de actualización en tabla de partidas individuales &

SAP Error Message - Details

• Message type: E = Error

• Message class: GI - FI-SL update

• Message number: 219

• Message text: Problema de actualización en tabla de partidas individuales &

¿Qué causa este problema?

The system attempted to update one or more documents in table &V1&. This
attempt failed due to a problem when inserting line items.
It is highly likely that this runtime error was caused by a DUPREC
problem. The system attempted to insert a line into line item table &V1&
for which a line with the same unique key already exists (duplicate
record).
Normally, the ledger-based line item tables of the general ledger must
have unique keys for the following combinations:
Key 1:
RCLNT
DOCNR
RBUKRS
RYEAR
DOCLN
RLDNR

El sistema emite un mensaje de error y no le permitirá continuar con esta transacción hasta que se resuelva el error.

Key 2:
RCLNT
BELNR
RBUKRS
GJAHR
BUZEI
DOCLN
RLDNR
<ZH>The following causes for a DUPREC error are possible in this case:
</>
If a direct (online) posting is to be carried out:
Problems caused by the number range object
Due to incomplete test sets in client copies, the tables in new General
Ledger Accounting still contain old data. Test systems are affected in
most cases.
Problems caused by a software error
If documents were subsequently being transferred from Financial
Accounting, the "Check Duplicate Transfer" indicator may not have been
set or the table contained unexpected documents.

Respuesta del sistema

The update was terminated with a runtime error.

¿Cómo arreglar este error?

The exact cause for the runtime error must first be examined. For this,
the following checks are helpful:
If documents were subsequently being transferred from Financial
Accounting, check whether the "Check Duplicate Transfer" indicator was
set.
If the error occurred during a migration, documents with the same
document numbers existed in the line item table &V1&.
In the case of a direct (online) posting, there can be multiple causes.
For this reason, the following steps should be carried out first:
Search for the cause in the standard SAP Notes using the terms
"SAPSQL_ARRAY_INSERT_DUPREC" and "SAPLGLIU".
If the document in question was being reversed, ensure that all the
relevant SAP Notes for the negative posting have been implemented. The
search terms in this case are "Reverse" and " G_RWIN_REVERSE".
Check the number range status of the number range objects in question
based on the document type used (see transaction FAGL_DOCNR_LD,
FAGL_DOCNR, FAGL_BELNR_LD).
A runtime error due to a duplicate document number can also result, for
example, when document number ranges are copied to another fiscal year,
although a document number from a more valid fiscal year (for example,
9999) was already used for this fiscal year.
Note that the document number for differing fiscal year variants can
differ between entry view and general ledger view.
<ZH>Analysis information:</>
The system attempted to update the following documents in line item
table &V1& (ledger/company code/fiscal year/DOCNR/BELNR):
&V2&
&V3&
&V4&
If the analysis shows that the problem is not a duplicate record,
further causes for the runtime error (such as problems in the database
system) must be analyzed.

Extracto de mensaje de error del sistema SAP. Copyright SAP SE.