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 tables

Former Member
0 Kudos

Hi,

Can I body explain me clearly the role of USOBX_C and USOBT_C tables in SAP authorization

mechanism?

Thank you in Advance.

1 ACCEPTED SOLUTION

Former Member
0 Kudos

Hi Rama,

Tables USOBT & USOBX are standard tables delivered by SAP.

USOBT defines for each transaction and authorisation object, which default values should be used in the profile generator for the transaction(s) entered in a Role Menu.

USOBX defines (a) which authorisation checks should occur within a transaction and (b) which authorisation checks should be maintained in the profile generator.

In each case the set up and values are SAP's standard ones which may not be appropriate for how a business wants to run its operations on SAP.

At implementation a copy is made of these tables (via SU25) and these copies are called USOBT_C and USOBX_C.

Hope it helps.

Please award points if it is useful.

Thanks & Regards,

Santosh

3 REPLIES 3

Former Member
0 Kudos

Rama,

[Removed by the moderator.]

Search this site as well as there much info available.

Cheers,

Ben

Former Member
0 Kudos

Hi Rama,

Tables USOBT & USOBX are standard tables delivered by SAP.

USOBT defines for each transaction and authorisation object, which default values should be used in the profile generator for the transaction(s) entered in a Role Menu.

USOBX defines (a) which authorisation checks should occur within a transaction and (b) which authorisation checks should be maintained in the profile generator.

In each case the set up and values are SAP's standard ones which may not be appropriate for how a business wants to run its operations on SAP.

At implementation a copy is made of these tables (via SU25) and these copies are called USOBT_C and USOBX_C.

Hope it helps.

Please award points if it is useful.

Thanks & Regards,

Santosh

0 Kudos

> USOBX defines (a) which authorisation checks should

> occur within a transaction and (b) which

> authorisation checks should be maintained in the

> profile generator.

That's not strictly correct, only the code & in some cases the kernel define the check that occur, though USOBX settings will have some control over those.