Solution : https://service.sap.com/sap/support/notes/626915 (SAP Service marketplace login required)
Summary :
SAP Note discusses errors that occur when transporting table entries with unique indexes in SAP systems. Errors such as "2EETW000 duplicate key error during insert" reflect conflicts between unique indexes during data transportation. To resolve these errors, SAP offers solutions including not transporting such table entries, ensuring global uniqueness of entries across systems, or removing unique constraints from indexes not meant for uniqueness enforcement. The note advises against the transport of non-unique transaction data across systems with delivery class 'L'. Alternatively, global uniqueness can be ensured via RFC-based comparisons, or indexes may be redefined as non-unique.
Key words :
insert sequence failed due, 2eetw000 duplicate key error, duplicate key error due, error simply involves, terms sap_dext reason, rfc-based comparison, efficient data access, older r3trans versions, globally unique identifiers, internal return code 128
Related Notes :
| 1414583 | Error when importing WebClient UI configurations |
| 1074030 | R3trans: "Duplicate key" composite SAP note (as of Rel 6.10) |
| 689574 | Add. info. on upgrading to SAP ERP Central Component 5.00 |
| 88656 | R3trans: Duplicate key composite SAP note (Release 4.0-4.6) |
| 28324 | R3trans: Composite note "duplicate key" array insert |