topic Re: manually added Authorization object in Application Development and Automation Discussions

manually added Authorization object

Former Member — Mon, 25 Feb 2008 17:54:01 GMT

All ,

What is the impact for manually added authorization objects in the roles after the system upgrade??

Re: manually added Authorization object

Former Member — Mon, 25 Feb 2008 19:01:36 GMT

My 2 cents, since I don't see any replies.

I try to avoid manual auth objects on a role as much as possible. One problem with manually auth object is in PFCG, it will not give a reference to what transaction the auth object came from. Unless thoroughly documented this can be an audit issue.

In regards to upgrades, I don't this it will have any affect. It is usually the tcodes that are affected.

Re: manually added Authorization object

Bernhard_SAP — Tue, 26 Feb 2008 15:42:31 GMT

Hi,

the reference comes from the values maintained in SU24. So if you maintain SU24 and assign the self created object to a transaction, you will have this reference then visible in pfcg too. An upgrade will not delete own created objects (naming convention has to be recognized, Z***** is preferable as object name).

b.rgds, Bernhard