Skip to Content
author's profile photo Former Member
Former Member

How to insert IT0001for exist employee

Hi All,

We have any issue like, when we enter particular employee in PA20 or PA30, it is taking to dump. We had applied OSS notes like 1839621, 1834536 but no luck. How to insert or maintain IT0001 to resolve this issue.

We ran these report RPUPBVG0 and RPUPAV00

When i run report RPUPAV00, i got the below message and noticed IT0001 does not exist.

2 ERP016X"Start of Infotype Regeneration in Client:" "500" " " " "

2 ERP016X" New Personnel Number:" "00000010" " " " "

2EERP016 "*" "00000010" "Infotype 0001 Does Not Exist" " "

2 ERP016X"Statistics" " " " " " "

Please find dump:-

hat happened?
The exception 'CX_HRPA_INVALID_INFOTYPE_DB' was raised, but it was not caught
anywhere along
the call hierarchy.

Since exceptions represent error situations and this error was not
adequately responded to, the running ABAP program

rror analysis
An exception occurred that is explained in detail below.
The exception, which is assigned to class 'CX_HRPA_INVALID_INFOTYPE_DB', was
not caught in
procedure "READ" "(METHOD)", nor was it propagated by a RAISING clause.
Since the caller of the procedure could not have anticipated that the
exception would occur, the current program is terminated.
The reason for the exception is:
Inconsistent data exists in the database for infotype 0002 A for 00000010

issing RAISING Clause in Interface
Row 1
Module type (METHOD)
Module Name READ

rigger Location of Exception
Row 140

Module type (METHOD)


110 ASSIGN pnnnn2_ref->* TO <pnnnn2>.

111 ASSIGN db_table_ref->* TO <db_nnnn2>.

112 ASSIGN <pnnnn2> TO <pshdr2> CASTING.


114 * read data from secondary database table

115 SELECT SINGLE * FROM (dbname) INTO <db_nnnn2>


117 pernr = <pshdr>-pernr AND

118 subty = <pshdr>-subty AND

119 objps = <pshdr>-objps AND

120 sprps = <pshdr>-sprps AND

121 endda = <pshdr>-endda AND

122 begda = <pshdr>-begda AND

123 seqnr = <pshdr>-seqnr.

124 IF sy-subrc IS INITIAL.

125 MOVE-CORRESPONDING <db_nnnn2> TO <pnnnn2>.

126 <pshdr2>-infty = secondary_infty.

127 ELSE.

128 IF 1 = 0.

129 * 049 Fehlender Sekundärsatz zu Infotyp &1 Schlüssel &3


131 ENDIF.

132 CONCATENATE <pshdr>-pernr <pshdr>-subty <pshdr>-objps <pshdr>-sprps <pshdr>-endda <p

133 INTO invalid_key.

134 msg-msgty = 'E'.

135 msg-msgid = 'PBAS_SERVICE'.

136 msg-msgno = '049'.

137 msg-msgv1 = infty.

138 msg-msgv2 = secondary_infty.

139 msg-msgv3 = invalid_key.

>>>>> RAISE EXCEPTION TYPE cx_hrpa_invalid_infotype_db


142 tclas = tclas

143 infty = infty

144 pernr = pernr

145 table = dbname

146 key = invalid_key

147 msg = msg.

148 ENDIF.

149 ENDIF.


151 * read cost assignment data if necessary

152 CASE <pshdr>-refex.

153 WHEN false.

154 CLEAR pref.

155 WHEN true.

156 SELECT * FROM assob_hr INTO assob_hr

157 UP TO 1 ROWS


159 pernr = <pshdr>-pernr AND



Add a comment
10|10000 characters needed characters exceeded

Related questions

3 Answers

  • Best Answer
    author's profile photo Former Member
    Former Member
    Posted on Dec 22, 2013 at 04:30 PM

    Hi Ram,

    I am sure the above programs mentioned by fellow experts are helpful. However, I suspect if the solution will help. If it does, let me know.

    What Jonathan mentioned above is correct, this issue is related to decoupling and Shared infotype framework....Added to this, i would say, this issue, potentially, is because of Multiple assignments.

    1. Go to Program RPUFIXDS and try to enter the Erroneous employee number.

    2. You will notice two employees linked to each other... One of them is correct, the other one is where the issue is....

    What would have happened?

    What possibly the case is that the employee was being hired and mid-way the hiring was stopped...

    Therefore the primary infotype was filled, automatic maintenance of secondary infotype was not successful. When you try to now search for the second PERNR using PA20/30/40, a database check is being conducted to verify if it can produce the data on screen...unfortunately not..and the dump occurs....

    What can be done now?

    Difficult to answer.

    1. If the above was the case, then recommendation is delete the PERNR using PU00. My gut feel, mostly PU00 will also result in dump when you select the erroenous PERNR.

    2. Second alternative is, in the debug mode, maintain secondary infotype. Once this is done, you can maintain IT0001. Will definitely work.

    3. Third alternative could be, remove the reference infotypes, possibly IT0709/IT0031 which could relate to the main PERNR and then try to see if you something can be done (Not sure on this one though).

    Hope this helps.



    Add a comment
    10|10000 characters needed characters exceeded

    • Former Member

      Hi All,

      It is not for all users. It is only for one user which we need to insert. I have taken ABAPer help to insert the record.

      We can insert record via debug mode.

      Thanks for all your support.



  • Posted on Dec 18, 2013 at 05:05 PM


    You have an issue on a secondary infotype. Maybe you can see it in the variable (dbname) in your dump (transaction ST22).

    Please also check the infotype config via this program:


    When I see which class is dumping, it tells me, this has something to do with shared infotypes or Decoupled infotypes.

    Best regards,


    Add a comment
    10|10000 characters needed characters exceeded

    • Former Member

      Hi Have a look at

      1. Program RPU_CHECK_TIMECONSTRAINT_S1 (no selection parameters required).
      2. Output produces list of inconsistencies with time constraints for infotypes and incomplete personnel numbers.
      3. Correct date gaps using program RPUSCNTC.

      Thx PAW

  • Posted on Dec 20, 2013 at 03:06 PM

    Are you in country GB? A recent implementation of a note introducing a new secondary infotype for sexual orientation information, may cause this issue. Please look up oss, if this turns up any helpful notes.

    Add a comment
    10|10000 characters needed characters exceeded

Before answering

You should only submit an answer when you are proposing a solution to the poster's problem. If you want the poster to clarify the question or provide more information, please leave a comment instead, requesting additional details. When answering, please include specifics, such as step-by-step instructions, context for the solution, and links to useful resources. Also, please make sure that you answer complies with our Rules of Engagement.
You must be Logged in to submit an answer.

Up to 10 attachments (including images) can be used with a maximum of 1.0 MB each and 10.5 MB total.