Application Development Discussions
Join the discussions or start your own on all things application development, including tools and APIs, programming models, and keeping your skills sharp.
cancel
Showing results for 
Search instead for 
Did you mean: 

usobx_c,usobt_c

Former Member
0 Kudos

hi guys,

may i know wats the use of the tables usobx_c,usobt_c??

2 REPLIES 2

Former Member
0 Kudos

The table USOBT_C defines for each transaction and for each authorization object which default values an authorization created from the authorization object should have in the Profile Generator.

The table USOBX_C defines which authorization checks are to be performed within a transaction and which not (despite authority-check command programmed ). This table also determines which authorization checks are maintained in the Profile Generator.

USOBT_C gives Relation between Transaction to Auth. Object (Customer)

USOBX_C is Check Table for Table USOBT_C

- Award points if this helps you-

- Danny D'sa

null

null

Former Member
0 Kudos

Hi Kevin,

The original source of Danny's answer is here:

http://www.sapsecurityonline.com/sap_security_interview_questions/sap_security_interview_questions.h...

Unfortunately this part of it is incorrect:

"The table USOBX_C defines which authorization checks are to be performed within a transaction and which not (despite authority-check command programmed )"

What this should say is that it is possible to switch off certain auth checks that are performed in the code.

It won't allow you to switch off kernel level checks such as S_TCODE, S_TABU_DIS and a few other S_ and P_ checks.

Is is a common mistake made by many newbies and experienced security folk that it is possible to define what auth checks are being performed solely by the modification of the above tables via SU22 and SU24