Entering content frame

Background documentation Transport Organizer - Concept Locate the document in its SAP Library structure

The Transport Organizer is fully integrated into the ABAP Workbench and Customizing tools. You can navigate between them in both directions. This enables you to:

Recording Changes

The Transport Organizer records and documents all changes to objects in the Repository and Customizing:

The Transport Organizer helps you when you organize development projects by allowing you to distribute project work for individual developers or teams between different change requests. These change requests record all changes made to development objects and Customizing settings. Objects from the areas of Customizing and the ABAP Workbench are managed and recorded in separate requests. Special checks have been implemented for each of these applications.

This graphic is explained in the accompanying text

You access the Transport Organizer from a request overview that clearly shows all change requests and allows you to display several levels of detail, right down to the object list itself.

Developments, corrections, and repairs are recorded in tasks and transported using change requests.

The target system and type of transport are assigned automatically and no longer need to be maintained by the user.

Several users can work together on a project by organizing their development work in tasks. These tasks belong to a common change request.

You can control access to Transport Organizer functions for different user groups by assigning appropriate authorizations.

Once you have included Repository objects in a change request, you can edit them in this request only. This means that until the change request has been released, they are locked against development work or maintenance by other developers not working on this change request. These developers are only allowed to display the objects.

This is how the Transport Organizer prevents uncoordinated, parallel changes from being made to objects. Only make changes to the original objects. A warning appears if you try and change a non-original object.

The Transport Organizer is activated automatically every time you edit a Repository object. An object has to be in a change request before a user can create or change it. Entering objects in requests ensures that all changes made in the ABAP Workbench are registered.

Changes to Customizing data are also registered by the Transport Organizer.

A package and the developer who is responsible for it are assigned to each Repository object. This development class indicates which area the object belongs to. This enables you to quickly contact a person in connection with any object. The structure of the entire ABAP Workbench is based on packages which can assist you in starting your work.

The Transport Organizer provides version management for all Repository objects, enabling you to compare or retrieve previous versions of objects. This lets you document or restore versions released before or after a particular change request or development project.

All developers working on a change request are required to write structured documentation when releasing their tasks. This states the aims of the project, its status, and any special features it includes. In addition, all changed objects are automatically recorded in the object list of the change request. This information, together with the documentation and version management, ensures that you have complete control over all revisions made in a single or multiple computer configuration.

Development projects are not worked on in a production system, but in one or more development systems depending on their size. To ensure that objects remain consistent, each Repository object has a defined original location. Changes are generally made at the original location to prevent unintentional, parallel work on the same object. The original location of Repository objects can be changed with relocation transports.

If several development systems are being used, it may be necessary to transport objects specifically to SAP Systems that are not supplied with regular change transports. If necessary, you can also change the transport attributes of the object (original system, package, transport layer). The transport types required for this are managed by the extended view of the Transport Organizer.

To transport Repository and Customizing objects from the development system to other SAP Systems in the system group, transport routes are used, which are defined when the system group is configured in the Transport Management System. The transport involves exporting objects from the source system in which the objects were changed and importing them into one or more target systems.

A transport log is created automatically for each change request. If errors occur in the production system after an import has taken place from a quality assurance system, the log enables you to immediately find out the following:

There are Transport Organizer tools available for searching for, displaying, editing, and analyzing change requests and transports.

Leaving content frame