PA40 - BDC- Action Type Problem

[Former Member]

Hi all,

Iam doing BDC for Tcode PA40 , To Terminate the employees. in PA40 screen i have only 6 action types in which " leave " is one of them.

The sequence of the action types on the 1st screen of PA40 are :

1. change of job

2. change in pay.

3. Leaving

4. Early Retirement

so in BDC

PERFORM DYNPRO USING:

'X' 'SAPMP50A' '2000',

' ' 'RP50G-PERNR' ZREC-EMPNUM,

' ' 'BDC_OKCODE' '/00',

'X' 'SAPMP50A' '2000',

' ' 'RP50G-SELEC(03)' 'X',

' ' 'BDC_OKCODE' '=PICK',

and it is working properly.

Now the problem is , my onsite guy who has to run the BDC for termination has 16 action types including "leaving" in different positions Eg.

1. Early Retirement

2. change in pay.

3. change of job

4. hire

5. ...

6 ...

7 Leaving

So The BDC is not working properly , I checked with BAsis , and he is not able to figure it out , because if it was configuration problem then all the users will have the same problem. Now this is for a particular user it is changed , might be the other new user who uses will have a different screen.

If this is the case then how to go about with the action type field ' ' 'RP50G-SELEC(03)' 'X'.

INstead of this field can we use some other field which has a value leaving or is there any other alternative plz do let me know.

waiting for your valuable replies.

Regards

Dan

.

[Former Member]

Hi daniel,

1. Yes you are right.

2. The SEQUENCE of actions (which is displayed)

will vary from user to user

based upon his authorisation rights.

3. So one can never be sure,

where the LEAVING

action will appear on which row.

regards,

amit m.

[Former Member]

Hi Amit,

Thx for the reply, If this is the problem then how to go about with the termination of employees.

If you have any idea abt this please do let me know

Dan

[Former Member]

Hi again,

1. we can use HR_INFOTYPE_OPERATION

2. for leaving probably we will have to update

infotype 0000 (leaving action)

and probably others, which may be required.

regards,

amit m.

[Former Member]

Try the this, it works to me.

TABLES: t588b.

DATA: usergroup LIKE t588b-userg.

DATA: w_screen_field(15) TYPE c.

DATA: it588b LIKE t588b OCCURS 0 WITH HEADER LINE.

DATA: w_index TYPE n.

REFRESH it588b.

CLEAR t588b.

GET PARAMETER ID 'UGR' FIELD usergroup.

SELECT * FROM t588b INTO TABLE it588b

WHERE mntyp = 'M'

AND menue = '01'

AND userg = usergroup.

READ TABLE it588b WITH KEY massn = 'ZB'.

IF sy-subrc = 0.

w_index = sy-tabix.

CONCATENATE 'RP50G-SELEC(' w_index ')' INTO w_screen_field.

REFRESH bdc_tab.

PERFORM process_screen USING:

'X' 'SAPMP50A' '2000',

' ' 'RP50G-PERNR' t_inrec-pernr,

' ' w_screen_field 'X',

Best regards,

Bing

[Former Member]

You can even do Action from PA30. The DTT tool for HCM Best Practices is designed around PA30 recording. Don;t user Pa40 for actions. Most of the batch loads in our company happen via PA30.

-Aman