Hello colleagues,
I'm getting this dump at our SOLMAN. Any help?
Category ABAP Programming Error
Runtime Errors ITAB_DUPLICATE_KEY
ABAP Program CL_SPR_MASTERDATA_REPOSITORY==CP
Application Component SV-SMG
Date and Time 17.02.2014 13:39:41
| Short text |
| There is already a line with the same key. |
| What happened? |
| Error in the ABAP Application Program |
| The current ABAP program "CL_SPR_MASTERDATA_REPOSITORY==CP" had to be |
| terminated because it has |
| come across a statement that unfortunately cannot be executed. |
| What can you do? |
| Note down which actions and inputs caused the error. |
| To process the problem further, contact you SAP system |
| administrator. |
| Using Transaction ST22 for ABAP Dump Analysis, you can look |
| at and manage termination messages, and you can also |
| keep them for a long time. |
| Error analysis |
| You tried to insert an entry into table |
| "{O:1715*\CLASS=CL_SPR_MASTERDATA_REPOSITORY}\DATA=MERGE_MASTERDATA[19]-MTEXTS |
| ". However, updating |
| the unique table key "PRIMARY_KEY" resulted in a duplicate entry. The key |
| concerned may be either the primary key or a secondary key. |
| The key components of the duplicate entry have the values "{2147483648-}" |
| " " " " " ". |
| With primary keys, the system may terminate while processing |
| block insert operations. The statements concerned are |
| (1) MOVE |
| (2) INSERT/APPEND ... LINES OF ... INTO/TO |
| (3) SELECT ... INTO/APPENDING ... |
| With secondary keys, the system may also terminate while processing |
| a single record insert operation. In particular, the following |
| modifying statements may cause the system to terminate due to |
| duplicate key values: |
| (1) "<fs> = ..." or "<fs>-comp = ...", if the assignment to |
| a field symbol or to a component of a field symbol modifies a |
| component of a unique secondary key. |
| (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 <fs> ...[TRANSPORTING comp_1 ... comp_n] ...", |
| if the field symbol points to a row of a table with unique secondary |
| keys and transporting the values read modifies a component of a unique |
| secondary key. |
| How to correct the error |
| Probably the only way to eliminate the error is to correct the program. |
| If the error occures in a non-modified SAP program, you may be able to |
| find an interim solution in an SAP Note. |
| If you have access to SAP Notes, carry out a search with the following |
| keywords: |
| "ITAB_DUPLICATE_KEY" " " |
| "CL_SPR_MASTERDATA_REPOSITORY==CP" or "CL_SPR_MASTERDATA_REPOSITORY==CM004" |
| "COMPARE_MASTERDATA" |
| If you cannot solve the problem yourself and want to send an error |
| notification to SAP, include the following information: |
| 1. The description of the current problem (short dump) |
| To save the description, choose "System->List->Save->Local File |
| (Unconverted)". |
| 2. Corresponding system log |
| Display the system log by calling transaction SM21. |
| Restrict the time interval to 10 minutes before and five minutes |
| after the short dump. Then choose "System->List->Save->Local File |
| (Unconverted)". |
| 3. If the problem occurs in a problem of your own or a modified SAP |
| program: The source code of the program |
| In the editor, choose "Utilities->More |
| Utilities->Upload/Download->Download". |
| 4. Details about the conditions under which the error occurred or which |
| actions and input led to the error. |