on 09-01-2009 7:56 AM
Dear colleague,
We want to define authorization on POs list in a way that every user will see only his own POs and also will be able to change only his own PO.
As far as I know the authrization on POs list can be defined in PFCG in the role but only by Purchasing Organization or Purchasing group.
We have a lot of users under the same Purch. group so using the Purch. group authorization is not good enough for us.
Does anyone know how can we define the Requester as the POs list authorizations?
Thanks in advance,
Keren
you cannot in SAP standard. you either have to align the persons with the purchasing group or face major developments. adjusting the PO lists as well as all the main transactions, like ME2, MASS, BAPI_PO and the dozens i have not found until today will keep a horde of abappers busy for some time. plus: you lose visibility ... transparancy. if you'll ever face an audit, such wide action needs explaining.
facing all this it seems a small effort to assign every person her/his purchasing group ...
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
keren, no.
this cannot be done using a single BADI (which will only enhance ... what?? ME2*N?). you have not only the lists to check for authorization, but also all transactions called from that list ... which can be even a BAPI.
please write the specs of what you will need and consult one of your abappers for detailled analysis.
that list allows for editing PO's. if you implement your authoritiy-check there and only there, what happens when some of the users think of editing the PO's another way, say by using ME22N ... surely you would want for the same algorithm to apply there = everyone only her/his own POs. should not the same algorithm apply to changes done via MASS also?
of course, it is your decision ... i'm just trying to write that securing the one list only is not foolproof ...
User | Count |
---|---|
1 | |
1 | |
1 | |
1 |
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.