Application Development Discussions
Join the discussions or start your own on all things application development, including tools and APIs, programming models, and keeping your skills sharp.
cancel
Showing results for 
Search instead for 
Did you mean: 

Problem with IN_UPDATE method of BADI HRPAD00infty implementaion for infoty

Former Member
0 Kudos

Hello Experts,

IN_UPDATE method of badi HRPAD00INFTY's implementation is not triggering while saving the particular custom infotype .The same method in_update of the same implementaion is triggering while saving the other custom infotypes .Please let us know when you come across this situation.

Thanks and Regards,

Venkat

4 REPLIES 4

former_member209703
Active Contributor
0 Kudos

It should be fired for your custom infotype too.

Do you have any checks in the IN_UPDATE code? Have you modify any of the standard logic generated for the dynpro? Is that a PA infotype?

0 Kudos

Hello,

Thanks for your reply.

Yes,it is a PA infotype.There are ano any checks ,even badi implemenation method itself not triggering.Nothing was modified in the screens or generated ones.

Thanks,

venkat

former_member209703
Active Contributor
0 Kudos

Hi

There's one thing you can do to check why the BADI is not been triggered

This is the secuence of calls from your infotype code to the BADI method. (Bottom-Up)

You can follow them from your custom infotype and see why is not triggering.


ZCL_IM_JOSE===================CP	METHOD	IF_EX_HRPAD00INFTY~IN_UPDATE ==> Your custom BADI
CL_EX_HRPAD00INFTY============CP	METHOD	IF_EX_HRPAD00INFTY~IN_UPDATE ==> Your custom BADI
SAPUP50R				FORM	BADI_IN_UPDATE
SAPUP50R				FORM	UPDATE
SAPFP50P				FORM	PUT_INFOTYP_BUFFER
SAPFP50M				FORM	SAVE
SAPFP50M				FORM	FCODE
MP998000				FORM	FCODE_EDYNR        => Your custom infotype
MP998000				MODULE (PAI)	POST_INPUT_CHECKS  => Your custom Infotype

0 Kudos

 

Hi,

When you create a custom infotype with transaction PM01. He creates automaticaly a entry in table V_T582ITVCLAS. Without this entry, the infotype cannot run in the decoupled infotype framework and with this entry, the in_update method of the BADI HRPAD00INFTY are not triggered.

To trigger the in_update method of the BADI HRPAD00INFTY, you must change the permissibility of the infotype to "Not permitted" or delete the custom infotype entry in table V_T582ITVCLAS.

Rg,

Rachid