New Functions in the Correction and Transport System (SE01)


In the long-term, transaction SE01 will be replaced by the Workbench Organizer (transaction SE09). The Workbench Organizer should be used whenever possible. Release 3.0 still includes the full functionality of transaction SE01. For detailed documentation, please refer to the online manual for the Workbench Organizer. For an initial overview, consult the separately provided Release Notes.

In Release 3.0, transaction SE01 is accessed by selecting:
Tools -> ABAP/4 Workbench -> Environment -> Maintenance -> Corrections

Corrections and repairs are managed in the Workbench Organizer under the generic term 'tasks'. A 'change request' is allocated to every task. When changes have been made, the task is released to its allocated change request. A change request can include several tasks that may belong to different users.

Change requests can be transportable or local. Transportable change requests correspond to the consolidation requests in transaction SE01. Local requests are new. They can be edited in transaction SE01, but not created there. This ensures that transactions SE01 and SE09 are fully compatible.

When you modify ABAP/4 Workbench objects, a standard request query window appears instead of the previous correction or repair window. The Own requests option displays a hierarchical list of requests and tasks that may be used. It also shows tasks/requests created in SE01. The request or task you require can be chosen from the list.
The Create request option lets you create a new request with a task. The system automatically assigns the correct attributes
(transportable or local; correction or repair).

Modifications to SAP objects can be entered in transportable change requests (consolidation transports) together with your own development work. They can then be transported, provided that the transport route is set correctly in the new table TWSYS.
If this functionality is not used, no settings are required in TWSYS.

All development classes are controlled by the Correction System. Exceptions are local development classes (starting with '$', no connection to the correction system) and test development classes (starting with 'T', optional connection to the correction system).

A new authorization object regulates access to the functions provided by transaction SE01 and SE09. This is described in a separate Release Note.

The status of a task or request called "DOCUMENT" in SE01, is called Modifiable in the Workbench Organizer. "LOCKED" is now correspondingly called Protected.

All change requests and tasks have received a new attribute Source client . The logon client is stored during creation. If a request or a task is edited in another client, the client is changed, providing no client-specific object is contained in the request or one of the tasks. All tasks of a request must have the same source client.

A transportable change request can only be released and exported from its source client. In Release 3.0, ADO objects (e.g. layout sets and other SAPscript objects) can also be exported from the source client. To do this, the program RDDIMPDP has to be started as a background job in client 000 and be scheduled in the source client. Scheduling can be carried out in any client, if you run program RDDNEWPP as user DDIC. Scheduling has to take place once in each existing client after an upgrade. For further information see the documentation on the ABAP report RDDIMPDP.
Every object is allocated to exactly one category that identifies it as client-specific or client-independent. The category and client- dependency can be viewed in the object list with Display attributes -> Object.

All requests and tasks have been assigned a new attribute, namely Category . Two categories are distinguished:
"CUST" client-specific Customizing
"SYST" SAP Repository, objects for all clients
Requests or tasks of the category "CUST" can only include objects of the category "CUST" (client-specific Customizing objects).

Customizing requests can be created and edited. Customizing requests exclusively contain client-specific Customizing objects.

In Release 3.0A, the automatic recording of changes to Customizing settings in Customizing requests has become an attribute of the client. You can set the recording option for a client in table T000. Please refer to the Release Note Client control via table T000 for more details.

Generic object names may no longer be used in corrections or transport requests. They are only allowed in general object lists (object lists for transport).

The Include template function can no longer be selected for tasks since the objects are not to be edited and no versions are created.

The transport of table entries is no longer controlled by the object function. The same applies to all SAP objects; the existence of an object in the source system determines whether it is deleted in the target system or not. After transporting table contents, the status in the target system is identical to the status in the source system for the specified area or the specified keys. Tables belonging to class "C" are an exception to this: Customizing table, maintenance only by the customer, no SAP import.

The Object function field in the editor is no longer available for input. Maintenance is only necessary in exceptions and is then performed with Extras -> Change object func. .

The function Unlock is no longer allowed for a request or a task. Please remove locked lines individually with the function Delete line in the editor (consider the consequences: version administration incorrect, logically dependent objects become overtakers...).

The table for development classes TDEVC, no longer contains data relevant for system administration. Entries made for the integration and consolidation systems related to transports are now stored in a separate table.
Development classes are treated as objects of the ABAP/4 Workbench. Changes to development classes are no longer reserved for the system administrator. When a development class is created or changed this is entered in a task (object type R3TR DEVC). Maintenance is carried out in transaction SM31 or from the ABAP/4 Workbench (transaction SE80).

System administration changes

There are separate Release Notes on configuring the Workbench Organizer or the Correction and Transport System:
Configurations for SE01 and SE09

Further notes

Workbench Organizer
Authorization object for SE01 and SE09