
In Release 3.0, the Workbench Organizer and the Correction and Transport System can be configured with transaction SE06. In the initial screen you have to specify whether the system is newly installed, whether it has been set up as a copy of another system, or whether it has already been configured for the Correction and Transport System.
You have the option of generating a standard configuration using a simple procedure or you can branch to the maintenance of system tables and generate more complex configurations.
An option is also provided to check the consistency of an existing configuration. Possible inconsistencies are noted in a log and can be eliminated afterwards.
The system tables for setting the configuration are:
TSYST Table of the SAP Systems within a system group
TASYS Table of the SAP Systems for distribution of
transports
DEVL Table of transport layers for distributed
developments (new)
TWSYS Table of target systems of transport requests
with objects of a consolidation system (new)
The table for development classes, TDEVC, no longer contains data for
system administration. The previous transport-relevant specifications
for the integration and the consolidation systems are stored in the new
table DEVL for transport layers. During the 3.0 Release upgrade, an
entry is generated in table DEVL for every combination of integration
and consolidation system which existed up to now. An appropriate
transport layer from table DEVL is allocated to every entry in table TDEVC.
Development classes are now 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).
Please refer to the online manual for the Workbench Organizer to get detailed information on the correct configuration of the Workbench Organizer and the Correction and Transport System.
To change the system configuration, you need a special administration authorization. For example, user DDIC has this authorization. In Release3.0, this authorization can also be assigned to other users. For further information see the additional release notes available for this topic.
Table DEVL for transport layers:
You can branch to the display or maintenance of table DEVL from
transaction SE06. Alternatively, you can start tansaction SM31 and enter the table name DEVL.
An entry is needed for every combination of integration system and consolidation system.
Table TSYST for a system group:
You can branch to the display or maintenance of table TSYST from
transaction SE06. Alternatively, you can start SM31 and enter the table name TSYST.
This table has one new field, the transport layer. Every system in the
group has an entry specifying the transport layer from table DEVL. This
names the integration and consolidation system for objects that have
their originals in this system. When a new development class is created
(see above) in a system, the transport layer which is entered in table TSYST is assigned to it.
Table TWSYS for the target systems of transport requests:
You can branch to the display or maintenance of table TWSYS from
transaction SE06. Alternatively, you can start transaction SM31 and enter the table name TWSYS.
When you work on objects in your integration system, these are entered
in a change request which can be transported and whose target system is
the respective consolidation system. All other changes are entered in a local request which is not transported.
Entries in table TWSYS enable you to deviate from this standard rule.
Enter the required target system for a source and a consolidation
system. When changes are made to objects with this consolidation system
and in the corresponding source system, the objects are entered in a
transportable change request with the required target system. In particular, this enables you to transport own developments and
modifications to SAP objects in the same change request.
Example:
System constellation with one development system DEV and one production
system LIF. If the table TWSYS contains the following entries:
Source system Consolidation system Target system
DEV LIF LIF
DEV SAP LIF ,
then objects with integration system DEV and consolidation system LIF can be edited together with SAP originals in the system DEV and then transported to LIF.