Hi all,
Before explaining my problem let me tell this. My client has not implemented HR and they are not ready to maintain the org. structure (since it takes hug time).
My problem:
when ever a PR is created it has to go for a approval process, because of the above to two reasons, i asked my client to create a ztable with these fields INITIATOR, Release strategy, release_code1....release_code8, user_id1....user_id8, this table is maintained by passing the userid who are authorized to create the PR and the corresponding release strategy by which the userid for the corresponding release code will also be maintained.
At this point, if the PR is created, based upon the user login id and based upon the release strategy I am finding the approver, and sending the workitem and everything is going fine.
For example if there are 4 approvers and first three has already approved the PR and it is pending with the 4th approver (userid--xx). At this time if anyone of the approvers goes to ME54n and releases the PR the system allows to do it since they are authorized to approve the PR.
I dont know how to check the login id with the corresponding release strategy to the corresponding approver which is maintained in the ztable.
Please help!!!
Regards
Balaji E.
Request clarification before answering.
Hi BK,
you need to restrict your users through roles.
The Basis can create a role through PFCG, where they can assign the transaction ME55 (or whatever) and can give the release codes like L1. L2 etc in the From and To section .
So what happens is that the 3 Approvers who had already released, though the have authorization to ME54N (or ME55) since they do not have Releasecode L4, they wont be able to release that PR.
and to Shweta's query, I think the name appears if we using the userexit (not sure though).
Hope it helps.
Aditya
Message was edited by:
Aditya Varrier
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
| User | Count |
|---|---|
| 5 | |
| 4 | |
| 4 | |
| 3 | |
| 2 | |
| 2 | |
| 2 | |
| 2 | |
| 2 | |
| 2 |
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.