Authorization objects : Changed, maintained, standard ? / deriving roles

[Former Member]

Hi all,

We've noticed that the organisational values are not always inherited when deriving roles in the authorizations objects.

Actually, it kind of depends of the status of the auth. obj.: changed, maintened or satandard. It is not inherited when the auth.object is on "changed".

We don't understand how we can fix this. How to pass the auth. object from "changed" to "maintened" and therefore deriving the roles in the right way ??

Thanks a lot for your help

[Former Member]

>

> Hi all,
> We've noticed that the organisational values are not always inherited when deriving roles in the authorizations objects.
> Actually, it kind of depends of the status of the auth. obj.: changed, maintened or satandard. It is not inherited when the auth.object is on "changed".
> We don't understand how we can fix this. How to pass the auth. object from "changed" to "maintened" and therefore deriving the roles in the right way ??
> Thanks a lot for your help

The symptoms you are getting aren't necessarily due to the object being in changed status, rather someone has gone into the roles and updated the org level directly in the object rather than using the org level popup. You can have an object in changed status where you have changed an activity for example & it will still get the org level from the org level popup.

From memory there is an icon by the field value where you can reset the field. I don't have SAP in front of me so I may be wrong. There are other options like deleting and re-adding the object via expert mode of auth maintenance but if someone has been maintaining org levels directly then this could potentially cause you big problems with the rest of the objects in the role depending on how they have been maintained.

It's also worth considering that objects in changed status have lost their link with the transaction which pulled them in originally. For this reason it is wise to avoid having objects in changed mode & maintain SU24 correctly.

[jurjen_heeck]

>

> From memory there is an icon by the field value where you can reset the field.  

It's the trashcan on the row where the field value was manually modified.

If that's there for an org field it's also an indicator that a value was eneterd in the wrong fiels (not in orglevels). Properly maintained orgfields will not show the trashcan.

If you see no trashcans at all in the rofile, go to 'utitlities' 'settings' and check the box for 'icons in tree structure' -> 'for deleting field contents'.

hth

Jurjen

[Former Member]

Thanks Jurjen, I knew there was something there, just couldn't remember what it was!

[Former Member]

I agree with Alex.

Additionally, if you have many of these "changed" and "manually" authorizations in the roles and have a release upgrade planned in the foreseeable future; then this might be your opportunity not to upload the roles into your new release, but rather redesign your concept to eliminate these authorizations which have lost their relationship to the transactions in the menus of the roles, and the master roles if you use them.

Cheers,

Julius

[Former Member]

Thank you for you answers, but we still don't find how to pass it from "changed" to "maintained". We don't even know how they turned to "changed" because we didn't touch it : we just added some objects trought SU24 and readded the transactions in the roles.

We discovered then that the objects were on "changed" and we want to fix that.

Thank you !

[Former Member]

>

> Thank you for you answers, but we still don't find how to pass it from "changed" to "maintained". We don't even know how they turned to "changed" because we didn't touch it : we just added some objects trought SU24 and readded the transactions in the roles.
> We discovered then that the objects were on "changed" and we want to fix that.
> Thank you !

Hi,

You can't change it from Changed to Maintained

You would have to delete the auth object which is changed, exit the auth tab. Go back in in Expert mode & select read old & merge with new. This will pull through the value you have maintained in SU24. You will lose the values which you were changed from standard & will only get what is in SU24.

The only way the objects would have gone to changed mode is if someone changed the contents of the field directly in the auth object. There is no other way it would happen. If a field is blank & you put values in then this will give you Maintained status, otherwise it will be Standard status.

Cheers

Alex