S_DEVELOP

Definition

This is the general authorization object for ABAP/4 Development Workbench objects.

You use it to grant access authorizations for all ABAP/4 Development Workbench components. These include:

Associated objects: To use the Workbench, users must also have authorization for the object Correction/transport system and request management (S_TRANSPRT). An authorization for the object ABAP: Program flow checks is also required to execute programs.

Defined fields

The object consists of five fields. The first four identify an object or function in the R/3 System. The fifth field lists the operations that the user can perform on the objects.

The fields are as follows:

For a list of development classes, press F4 and then choose one from the list or display Table DEVC.
You can display a list of valid values and then choose one by pressing F4. Possible values for ABAP/4 Development Workbench object types are:
Values for ABAP/4 Dictionary object types:
Values for Data Modeler object types:
Value for Workflow:
Possible values:

Example

Developer: In general, developers should have all S_DEVELOP authorizations apart from the database utility ( development object ID value TABT). The authorization would then be as follows:

Field Value
Dev. class for transport system *
Development object ID A to TABS, TABU to Z*
Node name *
ABAP/4 program auth. group *
Activity *

With this authorization, the user has unrestricted access to Workbench objects, but is not allowed to execute any of the database utility functions.

Authorized for the database utility: A user with the following authorization has access to the ABAP/4 Dictionary database utility.

Field Value
Dev. class for transport system *
Development object ID TABT TABL INDX MACO MCID VIEW SQLT
Node name *
ABAP/4 program auth. group *
Activity *

With this authorization, the user has unrestricted access to the database utility for the objects listed. Only these object types are relevant for the database utility.

Fine classification: You can assign different authorizations for different object types or object names to a user by assigning several authorizations.

Example: Suppose a user is meant to have unrestricted access to programs and ABAP/4 Dictionary objects, but should only be able to display data models. You can define these different authorizations in the following way:

Authorization 1: Programming without restriction

Field Value
Dev. class for transport system *
Development object ID A to U, V to Z
Node name *
ABAP/4 program auth. group *
Activity *

Authorization 2: Display data models

Field Value
Dev. class for transport system *
Development object ID U*
Node name *
ABAP/4 program auth. group *
Activity 03

Conversion of authorizations on upgrade to Release 3.0

From Release 3.0, this authorization object replaces the following objects:

During the Release upgrade, existing authorizations and profiles for S_ADMI_FCD, S_DDIC_OBJ and S_EDITOR are automatically converted to the appropriate authorization for S_DEVELOP.

Further notes

In production systems, only the system administrator and the EarlyWatch user should have an authorization for this object. The EarlyWatch user should only have an authorization with the values SYST and PROG for the field development object ID, and 03 for the field Activity.