runtime error - duplicate key found

[Former Member]

Dear Techies,

i have a strange issue here.

I am writing a stadard internal table to sorted table.

Though there are no duplicate entries,

my itab_s[] = itab[] gives a dump saying ITAB_DUPLICATE_KEY

What could be the reason.

how to check which record gives the dump from ST22.

regards

Imran.

[Former Member]

Hi

Set a break point on statement where it is generating the dump and check.

Shiva

[Former Member]

Dear Techies,
> Though there are no duplicate entries,
>  my itab_s[] = itab[]          gives a dump saying ITAB_DUPLICATE_KEY
>   What could be the reason.

Just a thought - maybe you're wrong and there are duplicate entries??

Rob

[Former Member]

There are no duplicates. Just checked for the data in the dump. For the objects it is returning the dump, i tried deleting those in the source internal table through debugging, but i dint fetch me any result

00101D 701069961021 1 2010052199991231 00020100521I039246 00000000#####

3333342333333333333222232233333333333333332222222222333333333334333333222222223333333300000222

001014070106996102100001002010052199991231000000000000020100521903924600000000000000000000C000

0000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000

0000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000

3000300031003000310044002000370030003100300036003900390036003100300032003100200020002000200031

00101D 701069971021 1 2010052199991231 00020100521C5137023 00000000#####BGN

3333342333333333333222232233333333333333332222222222333333333334333333322222223333333300000444

001014070106997102100001002010052199991231000000000000020100521351370230000000000000000000C27E

0000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000

0000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000

3000300031003000310044002000370030003100300036003900390037003100300032003100200020002000200031

00101D 701069981021 1 2010052199991231 00020100521C5137023 00000000#####BGN

3333342333333333333222232233333333333333332222222222333333333334333333322222223333333300000444

001014070106998102100001002010052199991231000000000000020100521351370230000000000000000000C27E

0000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000

0000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000

3000300031003000310044002000370030003100300036003900390038003100300032003100200020002000200031

I have deleted the above entries from the internal table.

Regards

Imran.

[Former Member]

There are no duplicates.

So you've found a bug in the ABAP kernel.

Rob

[Former Member]

Hello,

As replied by Rob there can be duplicate entries, then focus on part of statement use...

are using append statement?

Try to use

INSERT <FROM> INTO TABLE <ITAB>

...

Thanks

[Former Member]

Thanks for the replies.

This is production system, apart from debugging, i dont have a solution. And i need to find the error data which is if any.

But i dont think there is. Can there be any kernal level error.

Regards

Imran.

[Former Member]

Have you looked for notes?

Rob

[sjeevan]

Imran,

A quick search on the internet led me to this program to identify the duplicates

RSAR_RSISOSMAP_REPAIR using SE38 without checking the repair mode.

to correct it go to RSISOSMAP table through SE16n.

I hope this is applicable to your problem.

You may want to look at the following notes also

[Note 1130891 - ITAB_DUPLICATE_KEY after SORT of itab with UNIQUE keys|https://service.sap.com/sap/support/notes/1130891]

[1080997|https://service.sap.com/sap/support/notes/1080997]

Edited by: Jeevan Sagar on Sep 20, 2011 6:36 PM

[Former Member]

Check for blank records in the database/Internal table.

-Veeru