10-17-2011 5:58 PM
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
10-17-2011 7:25 PM
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?
10-17-2011 10:00 PM
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
10-18-2011 10:01 AM
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
06-01-2012 9:52 AM
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