on 12-06-2011 5:39 AM
Hello All,
In our scenario we are using release procedure without classification.
Let say in a Startegy S1 created there are three level of approvals L1, L2 and L3.
It goes in a way that if L1 created PR it should be released from L2 level from ME55 then L3 from same ME55 transaction which is fine.
But problem comes when L2 or L3 Person raises requisition. Let say L3 level person has raised requisition then he himself can released that from L1 and L2 level from ME55 transaction as he is on last level and has authority to release the requisition.
Ideally this is should not be fair practice.
We need to know how we can control this so that person who raised requisition should not release himself/herself.
Is there any configuration setting or any other way to do. Or we need to change the strategy.
Regards
Himanshu Nijhawan
Any Suggestions from experts ?
Regards
Himanshu
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Hi,
Do not design release process of PR as you explained. PR releaser always a PR releaser only and he should not create any PR. Also PR creator always used to create PR and PR creator should not release PR.
You can easily restrict and control PR release process by having well designed user authorization matrix and release matrix. As per release u201CVALUESu201D, release matrix designed and based on authorization, control can be established for transaction codes.
Lets example: User 1 will create PR, user 2 will change PR and you have 3 release codes for releasing PR such as like L1, L2, L3 for three user respectively user 3,user4 and user5..Now you can allow (authorized to) user to do following transaction
Transaction Code----
> User
ME51N----
> user 1
ME52N----
> user 2
ME53N -
>(All users ie..user1.user2,user3,user4 & user5)
ME54N or ME55 with release codeL1----
> user3
ME54N or ME55 with release codeL2----
> user4
ME54N or ME55 with release codeL3----
> user5
If business needs, you can give authorization user3, user4 and user5 to change PR(ME52N) by eliminating user2.
NOTE: For more details contact basis team and control all these by authorization object.
Regards,
Biju K
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Hello,
Thanks for explaination.
You mean to say there must be seperate person who will create PR and separte for approval.
But there can be case when PR approver also need to raise a PR for some requirement. Then he should not be able to release PR himself. This should go to some other person for approval process. There must be some mechanism to restrict that either by configuration change or authorization. Is this possible.
Regards
Himanshu
Release of a document is subject the business has to decide.
There might be as many levels as you can(max 😎 but there is set of procedure to be followed that is decided by the business.
Your question, the one who raises can also release which you seem is unfair. But in the organisation for example GM can raise a requisition and release it as an emergency but not always.So generally the higher or final level can raise and release the PR/PO.
Control at creation level might be possible, you can only control the access to release.
The levels L1L2L3 you decide who has to release and when and in which order.
L3 is the last, then the pre-requisite is L1,L2 levels must be released.
You can give authorization access to the L1,L2,L3 through workflow.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Hi,
There seems to be a conflict of interest in the requirement.
The person who creates the PR cannot also release/approve it.
There has to be atleast one more person(s) besides him who will release it.
Hence, please relook the requirements.
Otherwise, if you still want to configure the requirement, then you can try adjusting the Release pre-requisite settings in Release procedure configuration. In the release prerequisite, you can set that for L3, there is no prerequisite release from L1/L2. i.e L3 alone can release the request.
Regards
Prabhu
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Hi Himanshu...
System doesnt know who creates the document and who should release. All is controlled thru the authorizations you give in the role matrix. If a particular person is allowed and assigned a release code then he can always do it in his login no matter whether the creator is himself or someone else. If you have set your strategy like that then you cannot surpass the same. Or else you control the doc release with value limits to each of the levels. For example 25000-50000 to L1 only 50000-100000 to L2 only so on...
Shiva
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Hello
Thanks for reply. Correct me if i am wrong
I have mentioned that in e.g current scenario there are three codes L1 L2 and L3.
L3 has got access for L2 and L1 as its a last approval level. Is this setting came automatically to L3 person that L3 possesss L2 and L1 automatically or this can be changed fromour end?
Regards
Himanshu Nijhawan
Hi Himanshu
Pls refer this link
http://help.sap.com/saphelp_45b/helpdata/en/a7/2d547bb435d1118b3f0060b03ca329/content.htm
Regards
Shiva
Hi Himanshu,
Please correct yourself, if a person(L2 Level) is creating the document then he can only approve the L2 level of release code.
please dont assign him the L1 code in from the roles as the object is given.
this is done by the Help of the security consultant, ask him to remove the Release codes L1 and L3 from the
object M_EINK_FRG
Field FRGCO.
Hope it helps you.
Regards,
yawar Khan
Edited by: 1234_abcd on Dec 6, 2011 11:16 AM
This you can control thru Authorizations . Pl contact your basis team..
M_BANF_FRG >> T-DV86065801 >> FRGCD (PR Release Code)
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
hi,
Please use the work flow for this and concern your basis person.
Thanking you.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
User | Count |
---|---|
89 | |
7 | |
6 | |
3 | |
3 | |
3 | |
3 | |
3 | |
3 | |
2 |
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.