cancel
Showing results for 
Search instead for 
Did you mean: 

Runtime Errors - ITAB_DUPLICATE_KEY when loading data to DSO with an IPAK

Former Member
0 Kudos

Hi All,

We are facing the below error whwn we are loading the data to DSO with an IPAK.

Below is the dump :

_______________________________________________________________________________________________________

Runtime Errors ITAB_DUPLICATE_KEY

Date and Time 10/13/2009 03:12:39

-


-


Short text

A row with the same key already exists.

-


-


What happened?

Error in the ABAP Application Program

The current ABAP program "/1BCDWB/SAPLIQG000000000001" 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

An entry was to be entered into the table

"\PROGRAM=/1BCDWB/SAPLIQG000000000001\DATA=SLSRQRMNT_NEW_ITAB[]" (which should

have

had a unique table key (UNIQUE KEY)).

However, there already existed a line with an identical key.

The insert-operation could have ocurred as a result of an INSERT- or

MOVE command, or in conjunction with a SELECT ... INTO.

The statement "INSERT INITIAL LINE ..." cannot be used to insert several

initial lines into a table with a unique 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" " "

"/1BCDWB/SAPLIQG000000000001" or "/1BCDWB/LIQG000000000001U02"

"/1BCDWB/IQG000000000001EXTR"

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.

-


-


System environment

SAP-Release 700

Application server... "bwapp1"

Network address...... "161.228.215.45"

Operating system..... "AIX"

Release.............. "5.3"

Hardware type........ "00C8A9B24C00"

Character length.... 8 Bits

Pointer length....... 64 Bits

Work process number.. 4

Shortdump setting.... "full"

Database server... "bwdbp1"

Database type..... "ORACLE"

Database name..... "BWP"

Database user ID.. "SAPBWP"

Terminal................. " "

Char.set.... "en_US.ISO8859-1"

SAP kernel....... 700

created (date)... "May 5 2008 21:10:58"

create on........ "AIX 2 5 005DD9CD4C00"

Database version. "OCI_102 (10.2.0.2.0) "

Patch level. 159

Patch text.. " "

Database............. "ORACLE 9.2.0.., ORACLE 10.1.0.., ORACLE 10.2.0.."

SAP database version. 700

Operating system..... "AIX 1 5, AIX 2 5, AIX 3 5, AIX 1 6"

Memory consumption

Roll.... 5099600

EM...... 0

Heap.... 3146592

Page.... 32768

MM Used. 7888432

MM Free. 327904

-


-


User and Transaction

Client.............. 010

User................ "NEX32JJ"

Language key........ "E"

Transaction......... " "

Transactions ID..... "4AD423A622220141E1008000A1E4D72D"

Program............. "/1BCDWB/SAPLIQG000000000001"

Screen.............. "SAPMSSY0 1000"

Screen line......... 6

-


Accepted Solutions (0)

Answers (2)

Answers (2)

Former Member
0 Kudos

hello anil;

check if the key of the tables is equal to the key of the DSO.

They should be equall to avoit duplicate data.

Regards;

Ricardo

Former Member
0 Kudos

Please do help me to solve above error.

Thanks in advance,

Anil

Pravender
Active Contributor
0 Kudos

execute RSAR_RSISOSMAP_REPAIR by checking repair mode.

For more details refer OSS note 613449.

Former Member
0 Kudos

Tried this one Its giving the below message:

No Incorrect Entries Found

Former Member
0 Kudos

Hello Anil

Looks like you are trying to populate the internal table with records that have the same key values. You might want to redefine the internal table or check the data that is being populated into the table.

Regards,

Former Member
0 Kudos

Hi,

After running the program RSAR_RSISOSMAP_REPAIR with repair mode have you tried loading the data again with the infopackage.

Hope you have checked the repair mode.

Try activating the datasource or infosource again and try the data load if the infosource is inactive.

Running this program will correct inconsistencies and loading again may help you.

If it is really an duplicate issue check whether unique entries checkbox done in the DSO if yes remove or change the key fields as required.

Thanks,

Arun