Checking Critical Objects in Requests
Use
When you release requests, you can check whether they contain any critical objects. These objects can include user authorizations, or other table entries or objects critical for security. If a request contains objects that are classified as critical, an error message or warning appears (depending on the parameter setting), and the request is not released.
Prerequisites
The Transport Management System is configured accordingly and the
critical transport objects have been maintained.Procedure
To activate the check when releasing and exporting requests, insert the parameter
CHK_CRIOBJ_AT_EXPORT into your transport profile. The following table contains the possible values for this parameter, and their effects:Value of CHK_CRIOBJ_AT_EXPORT |
Effect |
0 (zero) |
No check is made (as if the parameter was not inserted in the transport profile) |
W |
A warning appears when a request including critical objects is released. You can still release the request. |
E |
An error message appears when a request including critical objects is released. You cannot release the request. |
Result
An error message or warning appears when you export a request including critical objects, depending on how you set the parameter.