Auhtorizations Issue

[Former Member]

Hello experts,

I am implementing a project on Authorizations from scratch. All users had SAP_ALL profile, but after an audit they were told to restrict access to information. So, i am implementing their specs. In this first phase in order to please the next audit, the implementation is very simple.

I have 4 roles, 3 to distribute by the users, and another one for the Administrators.

So i have based my approach in this first phase in transaction level. The users filled the Excel with the transactions they use and the Roles are based on them. I inserted the transactions and generated automaticaly the authorizations. I accepted all SAP recomendations for the Authorizations and authorization object values and gave full access to the authorizations that SAP didn't knew what activities to put.

Now i am testing the processes users will do, and i realized the following:

Some transactions have inside them, shortcuts masked of buttons, go tos, etc that leads to other transactions users didn't mapped. Is there any table that gives me wich transactions can be called inside the transactions, so i can map every transaction users will use? Wich is the best way to get all transactions mapped?

Another question regarding the implementation proccess:

Am i procceeding correctly? Please be aware that, in the short term all authorizations will be much more restricted after the more detailed specs of the client.

Thank you very much

Regards

John

[jurjen_heeck]

Well, at least you're making progress

For starters, please choose a more descriptive subject line the next time. Quite a few posts here are about authorization issues.

As far as the hidden transactions are concerned, a lot of transactions will propose these additional transactions to be entered into S_TCODE by the profile generator. Another possibility is that the couples are registered in SE97 so the S_TCODE check for the called transaction is skipped anyway.

I do not think there is a short way to find these. Testing will reveal them anyway. To avoid working through tons of error messages you can consider having your key-users go through their processes with SAP_ALL and a system trace sunning. That'll reveal all transactions started.

Cheers

Jurjen