Skip to Content

Archived discussions are read-only. Learn more about SAP Q&A

PA30 - Maintain HR Master Data - ITAB_DUPLICATE_KEY shoprt dump


when I run PA30 transaction I immediately receive short dump ITAB_DUPLICATE_KEY with info as follows:

What happened?

Error in ABAP application program.

The current ABAP program "SAPLHRBAS00GENERICSELECTION" had to be terminated

because one of the

statements could not be executed.

This is probably due to an error in the ABAP program.

Error analysis

You wanted to add an entry to table


with a UNIQUE KEY. However, there was already an entry with the

same key.

This may have been in an INSERT or MOVE statement, or within a

SELECT ... INTO statement.

In particular, you cannot insert more than one initial line into a

table with a unique key using the INSERT INITIAL LINE... statement.

User and Transaction

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

Transaction......... "PA30 "


Screen.............. "SAPMP50A 1100"

Screen line......... 3

Information on where terminated

The termination occurred in the ABAP program "SAPLHRBAS00GENERICSELECTION" in


The main program was "SAPMP50A ".

The termination occurred in line 65 of the source code of the (Include)


of the source code of program "LHRBAS00GENERICSELECTIONU17" (when calling the

editor 650).



60     IF begda > endda.
61       RAISE wrong_dates.
62     ENDIF.
64     IF NOT pernr_tab[] IS INITIAL.
65       SELECT pernr ename AS name begda endda FROM pa0001
66         INTO CORRESPONDING FIELDS OF TABLE l_pernr_date_tab
67           FOR ALL ENTRIES IN pernr_tab
68             WHERE pernr = pernr_tab-pernr AND
69                   sprps EQ space.
70       CLEAR pernr_tab[].
71 *     ENAME contains allways the latest name, so we don't have to care
72 *     about the dates
73       LOOP AT l_pernr_date_tab INTO l_pernr_date_wa.


This happens for a specific employee.

There are two records in PA0001 table, but they are on a different date ranges, so this should be OK.

PA0001 table content:


10001228 31.12.2008 01.09.2008 000 03.10.2008 MARTISB

10001228 31.12.9999 01.01.2009 000 03.10.2008 MARTISB

I suppose this happens when PA30 before showing screen to a user tries to read info of users used in last usage of PA30.

Maybe clear of SAP GUI cache should help? (Do you know how to cleare GUI cache on user's desktop?)

Maybe field SPRPS ("Lock Indicator for HR Master Data Record") should not be empty for the second record of PA0001 table?

Anyone know any solution for that or OSS note?

Kind regards


Not what you were looking for? View more on this topic or Ask a question