Community
Application Development and Automation Discussions
Join the discussions or start your own on all things application development, including tools and APIs, programming models, and keeping your skills sharp.
cancel
Turn on suggestions
Auto-suggest helps you quickly narrow down your search results by suggesting possible matches as you type.
Showing results for 
Search instead for 
Did you mean: 
Read only

manually added Authorization object

Former Member

‎2008 Feb 25 5:54 PM

0 Likes
1,657

All ,

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

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

Reply
2 REPLIES 2
Read only

Former Member

‎2008 Feb 25 7:01 PM

0 Likes
887

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.

Read only

Bernhard_SAP
Product and Topic Expert
Product and Topic Expert
In response to Former Member

‎2008 Feb 26 3:42 PM

0 Likes
887

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