Home » Tables » Usobt_C And Usobx_C Tables

Usobt_C And Usobx_C Tables

We discussed about the basics of SU24 tcode in our previous discussion.

In this discussion, we will be discussing about the SU24 custom tables USOBT_C and USOBX_C.

In our last discussion, we saw that SU24 tcode is used to maintain all those authorization objects that are checked during the execution of a particular transaction.

We also saw that for every authorization object that is in SU24.

The customer tables USOBX_C and USOBT_C are initially filled with the contents of these tables and can synchronized at each further upgrade.

These tables can be evaluated in the Data Browser (transaction SE16).

Share; Alert Moderator.

You already have an active moderator alert for this content.

tables are filled with default values and are used for the initial fill of the customer tables USOBX_C and USOBT_C.

(3)Difference between usobt and usobt_c ?

Answer: USOBT is SAP delivered table where as USOBT_C is customer table.

After the initial fill, you can modify the customer tables , and therefore the behavior of the Profile Generator, if.

SU24, USOBT_C & USOBX_C are customer Tables.

Customer Tables are filled with SAP standard tables at the start of SAP installation.

Later as per the need, we could change the check indicator/proposal status of transactions for authorizations in SU24 which directly after saving reflects inn USOBT_C & USOBX_C.

26/10/2010 The check indicators as maintained in SU24 are stored in two customer specific tables USOBT_C and USOBX_C.

The customer specific tables ensure that the values modified by a customer are not over-written by the SAP proposed values during a future upgrade.

We can have a look at the SAP proposed values through the transaction SU22.

1) SU24 will refer back to table USOBT and USOBX.

When we add customize transaction object, you can find it under USOBT_C and USOBX_C.

So you can use SU24 to see what object will be used when you add a particular transaction into a role.

10/10/2013 What is the difference between USOBX_C and USOBT_C ?

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 is a standard SAP Table which is used to store Relation Transaction > Auth.

Object (Customer) data and is available within R/3 SAP systems depending on the version and release level.

Below is the standard documentation available and a few details of the fields which make up this Table.

USOBX_C is a standard SAP Table which is used to store Check Table for Table USOBT_C data and is available within R/3 SAP systems depending on the version and release level.

Below is the standard documentation available and a few details of the fields which make up this Table.

26/10/2010 The check indicators as maintained in SU24 are stored in two customer specific tables USOBT_C and USOBX_C.

The customer specific tables ensure that the values modified by a customer are not over-written by the SAP proposed values during a future upgrade.

We can have a look at the SAP proposed values through the transaction SU22.

usobt_c and usobx_c tables