Authorisation Check Steps Work Flow—->

  1. User Logon to the system using ID & Passowrd successfully.
  2. User Executes a Transaction.
  3. System checks whether transaction code is locked in SM01
  4. If transactions are not locked then it checks for authoirsation object S_Tcode
  5. It is allowed then it checks for minimal authorisation in table TSTCA
  6. If it is allowed then it checks for authorisation objects in SU24
  7. The authorisations are checked in the programs using command Authority-Check command
  8. SAP maintains the allowable transactions and allowable authorization objects in SU56 and missing authorizations in SU53
  9. Each time a tcode is executed it checks in SU56 [UserContext] it is available then allows, if not writes into SU53

The above steps are important to understand the work flow of Authorization Check whenever an User log-on and run a Transaction Code.

Authorisation Check

  1. The minimal authorisation that are required to execute a transaction are maintained in table “TSTCA”
  2. The maximum authorisations that are required to execute a transaction are maintained in table “USOBT”
  3. The objects that are required to execute a transaction are checked using check indicator in table “USOBX”

These two are standard tables and any customer changes are over written, so these tables are copied to customer tables USOBT_C and USOBX_C using the option in SU25

Reagrds

Samar

To report this post you need to login first.

Be the first to leave a comment

You must be Logged on to comment or reply to a post.

Leave a Reply