on 07-26-2007 7:03 PM
Gurus,
I desperately need help
On each SAVE of IT0001, we need to create IT0017.
We did dynamic action and it is working fine.
But we are having lot of custom mass upload programs where we will be updating data in IT001. As dynamic action is not going to work in background, we need to change all these programs to update IT0017. This is lot of program change and testing.
I am looking for some approach to update IT0017 even during background run of these mass upload programs. We tried BADI HRPAD00INFTY to update IT0017 on save of IT0001, but we were unable to crt IT0017 because of some unknown errors.
Please help please please .
Manali,
Did you try with user exit EXIT_SAPFP50M_002? I had to do an update of infotype 0041 everytime I saved other infotype, and it worked ok.
Regards
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Manali,
I have just read your other and I think that the problem is that you are trying to lock the employee when it is already locked by SAP, becaue you are in PA30 or the like processing Infotype 0001 for that employee. So I think you could do one of the following ideas:
1) Try not to use HR_EMPLOYEE_ENQUEUE? May be that way it works
2) Access straigthly to table PA0017 with INSERT sql (ok, it is not very standard and may cause inconsistencies)
3) Create a Batch Input with the data to update IT0017 (in the bady or user exit), and schedule it to run at the night so that you make sure the emploeyee wont be locked by anyone.
4) In the other thread you said you had a standalone program to do the update... you could create a job to run it, and like 3 schedule it to run at night
Hope some of those works for you!
Regards
Thanks !!
Pl. see my opinion regarding options you provided...
1)If I am not using HR_EMPLOYEE_ENQUEUE .. FM HR_INFOTYPE_OPERATION ( which I am using to crt IT0017) give me error that employee is not enqueued.
2)I am not very much in favor of direct table update.
3) I am unable to understand this approach
4) This approach is not acceptable to team. They will like to have immediate data update
Let me know what you think
thanks
Manali,
Taking into account that:
.- You need inmediate update
.- You cant use dynamic actions
.- You cant use standar programming to do the update, because HR_INFOTYPE_OPERATION wont work with the employee already locked
The only I think will achieve what you need is direct update to the table, and I think like you it is far from the best way to resolve a problem, but as far as I know it is the only way with that scenario
User | Count |
---|---|
91 | |
7 | |
7 | |
4 | |
3 | |
3 | |
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.