Background: When defining authorizations using Profile GENERATOR, the table USOBX_C defines which authorization checks should occur WITHIN a TRANSACTION and which authorization checks should be maintained in the PG. You determine the authorization checks that can be maintained in the PG using Check Indicators. It is a Check Table for Table USOBT_C.

In USOBX_C there are 4 Check Indicators.

1. CM (Check/Maintain)

1. An authority check is carried out against this object.
2. The PG creates an authorization for this object and field values are displayed for changing.
3. Default values for this authorization can be maintained.

2. C (Check)

1. An authority check is carried out against this object.
2. The PG does not create an authorization for this object, so field values are not displayed.
3. No default values can be maintained for this authorization.

3. N (No check)

1. The authority check against this object is disabled.
2. The PG does not create an authorization for this object, so field values are not displayed.
3. No default values can be maintained for this authorization.

4. U (Unmaintained)

1. No check indicator is set.
2. An authority check is ALWAYS carried out against this object.
3. The PG does not create an authorization for this object, so field values are not displayed.
4. No default values can be maintained for this authorization.

Background: When defining authorizations using Profile Generator, the table USOBX_C defines which authorization checks should occur within a transaction and which authorization checks should be maintained in the PG. You determine the authorization checks that can be maintained in the PG using Check Indicators. It is a Check Table for Table USOBT_C.

In USOBX_C there are 4 Check Indicators.

1. CM (Check/Maintain)

2. C (Check)

3. N (No check)

4. U (Unmaintained)