Infotype 0302 - How to get it working?

[Deon_van_Zyl]

Hi,

I have read through all the threads I could find, but somehow I cannot manage to do a Hire and a Transfer action on the same day.

1) We have set the config in T77S0 -> ADMIN -> EVSUP to 1.

2) In table T529A the U0000 and the U0302 columns are both checked for the hiring as well as the Transfer action.

3) When you hire someone, the entries are created in both IT0000 and IT0302. Perfect.

HOWEVER

When I try and do a transfer action through PA for the same date as the hiring action (status stays active obviously), I get a message "Do not enter a personnel action for the date of hiring/transfer ".

But whyyyyyy??? B-)

Any help would be immensely appreciated!

Kind Regards

Deon

[antoine_foucault]

Hi Gideon:

The reason why you get an error message is explained here:

2469647 - IT0302 Additional Action is not created and system raise error message PG021

[Former Member]

Hi Gideon,

I assume this is standard behavior: second action should verwrite the existing one, disregarding the fact that you activated IT 0302. This is general time contraining for IT 0000. Obviously system cannot overwrite hiring action in this case. and generate error message.

[Deon_van_Zyl]

Hi Vladimir,

Please read what infotype 0302 is supposed to do before commenting that is should be disregarded. The whole purpose of the infotype is to move 1 action to infotype 0302 and keep the other one in Infotype 0000.

http://saphr.iexpertify.com/2008/12/additional-actions-infotype-it0302.html

[Former Member]

This is exactly what I have written. You cannot simply move Hiring action to IT 0302 and replace it with the other one.

[Former Member]

Please check the table T77S0.

Make sure it is set up to: ADMIN EVSUP 1 Additional Actions

Regards,

[Deon_van_Zyl]

Hi Luciano,

Did you read my very first point?

1) We have set the config in T77S0 -> ADMIN -> EVSUP to 1.

[antoine_foucault]

Hi Gideon,

Well, well, nice surprise... kind of strange because If if follow the standard abap coding that should not happen then.

I see your error message is error number 021 of message class PG... maybe you could go to SE93 tcode view this message and do a "where used" search see if it help.... it should report CL_HRPA_INFTY_0000 and MP000040.

Obviously I am guessing you are using the legacy system so the "interesting one" is the one in MP00040.

In my case, the message only occur in action infotype module pool... the condition is clear T529A-STAT2 IS INITIAL.

Are you trying to do the transfer on the same date as the hiring? maybe go see view V_529A_B to assign priorities for actions....

Antoine

[antoine_foucault]

Gideon,

I noticed I referred to a search in SE93 tcode but actually it's wrong, an error I made, the correct tcode for message class is SE91. Sorry for my mistake... the point there is to check on the where-used ref to find out if maybe a wrongful custom check in the HRPADINFTY BADi or XPAD customer exit could be throwing PG021 error.

Could you find a solution to your issue? did you check view V_529A_B to define priority list for Personnel Action types?

Best,

Antoine

[Deon_van_Zyl]

Hi Antoine,

Thanks for you detailed feedback and help in tracking the problem!! Currently I don't have anything defined in V_529A_B. I am not sure how the priority list is used or what it is for?

In the meantime I will check if the error message is called somewhere else and also try and debug MP000040 as I am currently first trying to just get it working via PA40.

-d

[antoine_foucault]

Hello:

Priority list is used to determine which action is going to stay in P0000 and which one is going to P0302 when you are running two actions for the same day. Setup to least priority action in V_529A_B to push that to P0302.

Best,

Antoine

[Deon_van_Zyl]

Hi Antoine,

It keeps getting weirder.. I cannot seem to maintain V_529A_B. When i go into table maintenance it does not give me the option to add new rows? Bizar.. I did try to toggle the edit button etc and I have SAP ALL on our dev system.

The other thing that does not make sense, is if I debug MP000040, it basically check the action does not have a function code of '1789' (with my action being a transfer, it has a function code of 0) and then the second check is to see if EVSUP is yes (which it should be) and t5290-stat2 is not is not initial, which is correct because it should stay 3. What am I missing here?

        IF t529a-funch NA '1789'.                           "QNUCE

          IF ( evsup IS INITIAL OR                          "XFYK008016

             ( evsup EQ yes AND NOT t529a-stat2 IS INITIAL ) OR

* PA41 can be used to move a non-entry/non-leaving action...

* Therefore during PA41 (PSPAR-AKTYP = 'U') avoid that this action is

* moved as a first hiring action (S0000 is initial)

             ( s0000 IS INITIAL AND t529a-stat2 IS INITIAL    "N1668793

                    AND pspar-aktyp = 'U' ) ) .               "N1668793

            MESSAGE e021.      "Keine Maßn. zum Datum des Eintritts

          ENDIF.                                            "XFYK008016

        ENDIF.

[antoine_foucault]

Bonjour Gideon;

1/Can you confirm the date of hire and the date of transfer?

2/ V_529A_B view... let see this one in details; as I review the system I see in V_529A_B you can't add entries simply because this view already should give you all relevant entries from T529A. The relevant entries are status field (STAT1, STAT2 and STAT3) with blank value and update IT0000 (U0000) with X value.

So in the light of the above and given your issue, could you try to setup this transfer action (in T529A view) so that all status (STAT1, STAT2 and STAT3) field are set to blank (meaning no change from previous actions), add MSN20 feature to check that it should only be processed for employee with status (STAT2) other than inactive. Clear all following flag for input field and update infotype (U0000, U0302), save, and then flag them again and save (to make sure they are flagged in the DB).

Then you should have it available in V_529A_B.

Yes, it seems if STAT2 value is cleared in T529A to go against my first answer to you but I think this field might get assigned a value at runtime.

Put a break-point at line MESSAGE e021 and then go do perform what is you perform to make SAP throw this issue for you.

Best,

[antoine_foucault]

Hi Gideon,

Could you make sure that employment status (STAT2) is set to active (3) in view T529A for this action and test again? Would that solve your issue?

best,

Antoine

[Deon_van_Zyl]

Hi Antoine,

100% sure. I checked that right in the beginning. Everything is checked correctly.

Any other thoughts?

Kind Regards

Deon

[antoine_foucault]

see my comment below...