Obsolete authorization objects in APO

[former_member230681]

Hi Experts,

I have to create one role in APO in which I have to manually insert authorization objects.When I try to do so, for some authorization objects I get error message "Authorization object is obsolete" and the authorization object does not get inserted.This might have happened because of upgrade.

Is there anyway to determine how to find authorization object corresponding to obsolete authorization objects in upgraded system?

Edited by: AnikaGupta on Dec 20, 2011 1:41 PM

[former_member204634]

Hi

I don't have much experience with APO security specifically or with regards to do what do with obsolete objects; but in general - I would say that obsolete auth object's description/documentation would provide hints to the object which should replace the object in context (for example object S_XMB_DSP). I would like to ask as to why are you trying to add this object manually - accepting if its an exception/necessary but see if you can resolve it by t-code addition in menu and checking what all auth objects are pulled - and building a solution based on SU24 proposals (depends if the obsolete object is called for this transaction in SU24 - maybe it does not) - if its an obsolete object you might want to edit its status in SU24 as do not check (apart from basis/hr objects)

Best Regards

Prashant

[Bernhard_SAP]

Hello Anika,

have a look at SU21->class AAAA (Obsolete authorization objects).

Normally objects contained in that class are really obsolete, so trying to insert them into a profile does not make too much sense.

If you use such objects for instance in own coding, either

a)change your coding to a still valid object

b)change your coding to a Z-object (won't get affected at upgrades)

c)worst option: change (modify) the obsolete object and chagne its class assignement

b.rgds, Bernhard