The following authorization objects exist in the CTS:
Used to secure the functions that change transport requests and tasks
Used to secure the administration functions in the CTS
If you have just installed the system, use the role maintenance transaction to maintain authorizations. If you want to set up your own authorizations, use the authorization trace. For more information, see Analyzing Authorizations Using the System Trace.
You can also assign the authorizations in the CTS for individual systems. This is particularly relevant for non-ABAP transports, since many non-ABAP systems can have the same ABAP communication system and this allows you to control the authorizations separately for the individual systems. For more information, see System-Specific Authorizations.
The authorization object S_TRANSPRT consists of the fields Activity and Request Type. The following values are used:
|01||Add or generate|
|23||Change/edit object list manually|
|50||Change source client
This is only possible if the request does not contain any client-dependent objects.
|75||Release other user's requests|
|78||Edit transport proposal|
|87||Assign your own request to another user|
|DTRA||Transportable change requests|
|TASK||Task (repair or correction)|
|TRAN||Transports of copies|
The authorization object S_CTS_ADMI, which is used to safeguard the administration functions, only has the field CTS_ADMFCT, whose values describe the various administration activities. Use the following values to assign the user authorization for particular administration functions.
|INIT||Initialize the Transport Organizer, for example, after a system copy|
|SYSC||Setting the System Change Option|
|PROJ||Manage projects in the Change and Transport System|
|INBX||Edit the TMS worklist|
|IMPA||Import all requests in an import queue|
|IMPS||Import individual requests into the target system (obsolete)|
|TDEL||Delete transport requests from the import queue|
|TADD||Add transport requests to the import queue|
|IMPT||Import requests into the target system using the Transport Management System (obsolete)|
|EPS1||Transfer files using the Electronic Parcel Service (EPS) to any directory|
|EPSW||Write files to the transport directory using the Electronic Parcel Service. This is a subpart of EPS1.|
|EPS2||Manage files in the Electronic Parcel Service (EPS)|
|QTEA||Process QA approval step and distribute approved requests|
|TQAS||Activate inactive requests. This can, for example, overwrite a QA approval.|
|TADM||Special transport functions in TMS, for example, granting QA approval|
|WHIT||Only for use of central CTS: Edit Transport Whitelist entries|