ITAB_DUPLICATE_KEY is an ABAP runtime error which you may come across when using or developing within an SAP system. See below for the standard details explaining what it means and how you can avoid or fix this runtime error.
Short Dump Classification: A - ABAP Programming Error
You can view further information about a runtme error by using transaction code ST22 which will show you this and all runtime erros that have happen in your SAP system.
Also check out the Comments section below to view or add related contributions and example screen shots.
Please see program correction for more details about the possible cause of this runtime error and how it could be avoided.
Please see search hints for more details about the possible cause of this runtime error and how it could be avoided.
Please see send to sap for more details about the possible cause of this runtime error and how it could be avoided.
A row already exists with this key
Please see abap error for more details about the possible cause of this runtime error and how it could be avoided.
An attempt was made to insert an entry into table <runtime parameter>-NAME. Updating
unique table key <runtime parameter> resulted in a duplicate entry however. The key in
question could be either the primary key or a secondary key.
The key components of the duplicate entry have the values <runtime parameter> <runtime parameter> <runtime parameter>
<runtime parameter>.
With primary keys, termination can occur during block insert
operations. The can affect numerious statements, for example
(1) MOVE
(2) INSERT/APPEND ... LINES OF ... INTO/TO
(3) SELECT ... INTO/APPENDING ...
With secondary keys, termination can also occur due to a single record
insert operation. In particular, the following modifying statements can
cause the system to terminate due to duplicate key values as soon as
the key is used again (delayed update):
(1) "
(2) "ref->* = ..." or "ref->comp = ...", if the assignment to a field
symbol or to a component of a field symbol modifies a component of a
unique secondary key.
(3) "MODIFY ... [TRANSPORTING comp_1 ... comp_n] ...", if transporting
the components to be changed modifies a component of a unique secondary
key.
(4) "COLLECT ... INTO ...", if adding up the columns of a numeric type
modifies a component of a unique secondary key.
(5) "READ TABLE ... INTO