on 09-05-2012 10:31 AM
Hi experts,
Just a short question, which will be the correct using for make some dates validation on infotype 2001? A new implementation badi for HRPAD00INFTY or it will be better to use ZXPADU02? Which are the differences between them?
I've already created a new implementation badi for HRPAD00INFTY but when I execute PA30 transaction I find that there's a first awart validation in ZXPADU02....
Which is the correct way to do this?
Thanks in advance,
Best Regards,
Rebeca
Hi Rebeca,
Actually, when I faced a similar issue, I've decided to use the User Exit. It does the work very well.
However, it is also possible to use the BAdI, as you mentioned, by creating a custom implementation.
Both enhancements may do the work perfectly.
Regards,
Liran
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Hi Liran,
Thanks for your answer. At first, I created a new badi for this issue in order to check that a user (checked by an authorization object) could save absences data without dates validation (begda,endda) done by the infotype.
Once this was done, I checked with absence 0002 (that couldn't be save on dates 13.04.2012 )and then realised that the oppositte validation was done in the User Exit ZXPADU02 that is trigger before the badi implementation.... Then I realised that the implmentation should be done in ZXPADU02 and not in the badi, but the problem is what you told me, this user exit contains a lot of code for all standard infotypes created in the client and the code is too long and not to much maintenable. So, that was why I put this entry, to organice my ideas....
So, for sum up, if you have idea to check a lot of infotypes validation inside the user exit it will be better (and cleaner) to create a new badi for each infotype, doesn't it?
For solve my issue I will make the corresponding changes in the user exit....
Thanks a lot
Regards,
Rebeca
User | Count |
---|---|
104 | |
12 | |
11 | |
6 | |
6 | |
4 | |
3 | |
3 | |
3 | |
3 |
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.