It was quite tedious when the requirement was slated to concatenate Personal Area (WERKS) and Cost Center (KOSTL) to be come an Organizational Key (VDSK1). I make one mistake in this issue while performing scoping. I was not careful enough when activating a BADI (Business Add-Ins).
In this issue, I have tried a different user exit that is made available by the main program in PA40 and include a question put forth to SDN forum.
In this issue, I have tried a different user exit that is made available by the main program in PA40 and include a question put forth to SDN forum.
There is one incident during my submission to ABAP Forum, a certain ABAPer told me that this (HRPAD00INFY) would not be call but just HRPAD00MGEACTIVATE. He was quite persistent on that matter that HRPAD00INFY would not be called up by PA40. So I had proof him wrong. Anyway, there is not much to argue in sdn.sap.com/forum on this issue as I have marked it as “Solve It On My Own”. Not to say that I underestimate him but one should get their facts right before one confidently point out to others.
-wilstroth, sdn.sap.com/forum/abap development-
Back to the lead, the concatenation was made possible in PA40 with the use of HRPAD00INFTY with one method called
Finally, I have solve this problem. I found that searching for a BADI is not that difficult at all. A little pinch of patience and a little pinch of time is all you need in order to look for a suitable one. Not to mention a little pinch of carefulness in the work done.
27 July 2006, Correction:
Actually, the method that should solve the problem is "Before Output" in HRPAD00INFY
Is sky the limit… who says HRPAD00INFY cannot work for PA40?!
Is sky the limit… who says HRPAD00INFY cannot work for PA40?!
No comments:
Post a Comment