As of Release 3.0A, detailed authorization checks are carried out in transaction SE01 (Correction System) and SE09 (Workbench Organizer).
Release 3.0 has introduced extensive structural changes to the R/3 Correction and Transport System that integrate the SAP Workbench and the Correction and Transport System. The functionality of the Correction and Transport System (transaction SE01) has almost completely been included in the Workbench Organizer (transaction SE09). To ensure compatibility, transaction SE01 still exists with its entire functionality and will only be replaced in a subsequent Release. One of many new functions which the Workbench Organizer offers, is an authorization concept which is adapted to the structure of the Workbench Organizer. With the help of authorizations you can determine, for example, which user may create, change, release or export change requests (previously K transports). It lets you control whether or not a user may edit tasks (previously corrections or repairs). Samples of the corresponding authorizations are available in the profiles delivered by SAP. Users can be classified into five different groups. These are:
in S_A.SYSTEM : S_CTS_ALL
in S_A.ADMIN : S_CTS_ADMIN
in S_A.CUSTOMIZ: S_CTS_PROJEC
in S_A.DEVELOP : S_CTS_DEVELO
in S_A.USER : S_CTS_APPLIC
The individual authorizations are described below:
1. S_CTS_ALL
Includes all authorizations within the Workbench Organizer and the Correction
and Transport System. If a user has this authorization, he can execute special
functions in the Workbench Organizer and Correction System which were
previously reserved for the special user DDIC. This includes, for example, the
transaction STME as well as the maintenance of the control tables for the
Correction System. Furthermore, a user who has this authorization is able to
initialize the Correction System and the Workbench Organizer (transaction
SE06). Unlike the user DDIC, a user with the authorization S_CTS_ALL can make
changes to objects of the ABAP/4 Development Workbench. These are managed by
the Workbench Organizer. The user DDIC has no change authorization in customer
systems.
2. S_CTS_ADMIN
A user with this authorization may only obtain information on change requests
and tasks and display corresponding logs.
3. S_CTS_PROJEC
This authorization allows a user to perform all the actions in the Correction
and Transport System and the Workbench Organizer, which were also previously
allowed. A correspondingly authorized user can create, edit, lock, unlock and
release/export a change request. The same operations are allowed for tasks,
Customizing requests and object lists.
4. S_CTS_DEVELO
If a user has the authorization S_CTS_DEVELO, he/she can only cooperate in
developments at task level. This means that the independent creation of change
requests or tasks is not permitted. Furthermore, there is no authorization to
change the user ID in a task. If such a user has finished development work,
he/she can release the task to the higher-level change request, but may not
release the change request itself.
5. S_CTS_APPLIC
This authorization only allows change requests, tasks, Customizing requests
and object lists to be displayed. The authorization corresponds to the
S_CTS_ADMIN authorization.
Please note that the authorization S_CTS_ALL allows you to use special functions, such as setting the system change option.
If you do not want to use the authorization concept which is provided with
Release 3.0A, you should give the authorization S_CTS_PROJEC to all users.
This ensures that development work runs smoothly.
The present authorization concept allows users to be grouped in the following
ways:
A person in charge of a project (S_CTS_PROJEC) defines the development work
that is to be carried out. A change request for the development work is
created in transaction SE09. The project manager then assigns users
(S_CTS_DEVELO) who are responsible for tasks to the change request. When the
individual developers have completed their work, they release their tasks to
the change request. When all tasks have been released, the responsible project
manager can release and export the change request. Only users who have the
authorization S_CTS_PROJEC or S_CTS_DEVELO can participate in project
work.
The user ID, or name of the person responsible for a task, can only be changed
by the person in charge (S_CTS_PROJEC). The users involved in the project
(S_CTS_DEVELO) may not create or change Workbench objects, since they have no
authorization to create or change requests and tasks. They must always be
assigned to an existing change request. Persons in charge of a project
(S_CTS_PROJEC) can become responsible for requests of others by changing the
name in the request. Please refer to the relevant release notes for a detailed
explanation of the Workbench Organizer functions.