Responsibility maintenance in Prod?

[Michael Pokraka]

Hmmm, the pressing enter trick doesn't work on my current 4.6c system (Su=
pp.Pack 44).
As to your second point, it's blocked but open. I.e. the transaction sayt=
 'System has status not modifiable' but the fields are then available for=
 input... I don't know if it's something flaky in SAP or a problem with o=
ur auths. I think we'll be able to lock that down again once we get the r=
est sorted out.=20
 
Thanks for the input.
Cheers
Mike
 
On Tue, Aug 19, 2003 at 03:16:29PM +0200, Menne de Jong wrote:
> One remark and one question:
> 1)
> I noticed that when using transaction PFAC_DIS (4.6c) on pressing enter=
 you
> get all options.
>=20
> 2)=20
> The container and type of a role are part of the workbench object role,=
=20
> whereas responsibilities are customizing within a role. Is the maintena=
ce of
> the role type and container not blocked on your productive system as op=
posed
> to the responsibility?
>=20
> Menne
>=20
> -----Original Message-----
>> From: Vineet Mehta
> To: SAP-WUG at MITVMA.MIT.EDU
> Sent: 8/19/2003 2:48 AM
> Subject: Re: Responsibility maintenance in Prod?
>=20
> Hi!=20
> If I understand this correctly, you want a display mode for PFAC.=20
>=20
> You can restrict the authorization to PFAC_DIS.=20
> You should take PFAC_CHG, PFAC_CHG, PFAC_DEL, PFAC taken away from=20
> authorization.=20
>=20
> I hope this helps.=20
> Cheers,=20
> Vineet=20
>=20
>=20
>=20
>=20
>=20
>         workflow at quirky.me.uk=20
>         Sent by: Owner-SAP-WUG at MITVMA.MIT.EDU=20
> =09
>         18/08/2003 09:37 AM=20
>         Please respond to SAP-WUG=20
>                 =A0 =A0 =A0 =A0=20
>                 =A0 =A0 =A0 =A0 To: =A0 =A0 =A0 =A0SAP-WUG at MITVMA.MIT.E=
DU=20
>                 =A0 =A0 =A0 =A0 cc: =A0 =A0 =A0 =A0=20
>                 =A0 =A0 =A0 =A0 Subject: =A0 =A0 =A0 =A0Responsibility =
maintenance in
> Prod?
>=20
> Greetings workflowers,
> Question concerning responsibilities: Should they be maintained in a
> production=20
> environment?
> In the past, I've come across two scenarios, based on the type of key
> used to=20
> determine responsibilities:
> 1. fairly constant data which can be maintained in DEV and transported
> (e.g.=20
> plant, country)
> 2. master data which doesn't necessarily exist in dev (e.g. customer).
> PFAC was=20
> opened in producton and the WF admin would maintain the
> responsibilities.
> =20
> Now I have a high-maintenance situation on a 4.6c system where things
> change=20
> frequently and people outside of IT are to maintain the responsibilitie=
s
> and=20
> agent assignments. I notice PFAC has an all-or-nothing attitude, thus i=
f
> we=20
> give someone access, they can maintain all workflow roles and even
> change the=20
> role/rule type. Is there any way to restrict this nicely - Ideally a
> display=20
> mode for PFAC with edit facilities for the individual responsibilities
> would be=20
> nice....
> =20
> Any thoughts and opiniions appreciated,
> Cheers
> Mike
> =20