ALO1 Security

[Former Member]

We are working on archiving, and have an environment where normal document display transactions are securied by organization unitl. ( Sales Org, Plant, Company Code etc.) in the standard SAP transactions.

I'm trying to determine if we can give ALO1 to all users, depending on the underlaying secuirty of a standard transaction (or standard security they have included) to limit what documents a user can actually see.

Will ALO1 check standard organization authorization elements when viewing the data.

[Former Member]

We are working on archiving, and have an environment where normal document display transactions are securied by organization unitl. ( Sales Org, Plant, Company Code etc.) in the standard SAP transactions.

I'm trying to determine if we can give ALO1 to all users, depending on the underlaying secuirty of a standard transaction (or standard security they have included) to limit what documents a user can actually see.

Will ALO1 check standard organization authorization elements when viewing the data.

[Former Member]

Hi Ruth Jones,

I am not sure whether we can allow all user to ALO1, but the authority check will be done whenever user executes.

for example, when user try to execute Sales Document, it will execute the program RASHSD11, which will check authorisation objects like.... V_VBAK_AAT, V_VBAK_VKO .....

it means, whatever user have access for Sales Orgranisation it will gives that data only.

Thanks

Firoz.

[Former Member]

Hi,

ALO1 should not be assigned to all the users as a part of the common transaction codes. It is used to access Determine ASH/DOREX Relationships as a part of archiving and should be assigned only to the specific users.

Hope this helps!!

Regards,

Raghu