Google Search - Blog...........

SAP - Transport System, Transport Request & Version Management.

Transport System

• Developers are in charge of creating or correcting data objects and will create change request, which can be for individual object or common request for a project. When the change request is released the system performs transport
• R/3 administrator is the person who sets up the transport system. This group works both at the R/3 application level and at the operating system level, using transport control (tp) program.

Change Request:

A Change request is a list in the system, which mainly contains the object to be transported. It also contains the transport type, the request category and the target system.

When the change request is created either manually or automatically, the system assigns a number to it automatically. This number is known as change request number.

The format of this number is normally

E.g., DD1K<900002>
Where DD1 is System Identification Number (SID)
K is keyword
The number is automatically generated by system and starts with 900001.

The change request records all modifications made to development object.

When the changes are made and the change task (will be discussed) has been released, the change request can be released.

SEO9 transaction
Tools -> ABAP/4 W.B -> overview -> W.B. organizer

Will display and check all the change requests.


A task in the workbench organizer is an activity in which user either creates an object or modifies the same. In workbench organizer, task can be either development or repair task.

A task is related to single user while change request contains tasks belonging to different users. You cannot transport task as such, but as a part of request. Each task is associated with task number, which is similar to change request number.

Usually, when a development work starts, a system administrator or project manager creates a change request to define tasks for all users involved in the project. Later, user starts modifying objects or create new object. Once user finishes his task, they must release them. A change request can be released for transporting, only when all tasks under the same change request are released.

Objects included in task become locked against other development work on the same object.

Version Management:

ABAP/4 workbench and the organizer provide a version management for all the objects in the system. With version management user can compare current version object and object with the previous version.

To display the version for a object,

Locate your object through the change request number of workbench organizer. Click on the object and from menu.
Utilities  display version.

It displays what has been modified and who did it.

Version management is important for developers also as it allows user to compare previous programs with the current one.


A transport means the process of moving something from one place to another. In R/3 system this ‘something’ means change request. To transport the objects you need to create the change request. It can be done with the help of workbench organizer. Transport System and workbench organizer are closely linked to each other.

An object original is a development object that has been created in the system in which you are working.

Suppose you transport object Zsus001 to another system, Zsus001 is object original for system DD1. If anyone tries to modify the program, he will be making repair to it, provided he has access key for the same. R/3 system offers this security measure to ensure that development object remain consistent for all system, thus preventing parallel work on the same objects. Correction of objects and development of objects can be only in original system.

The difference between Repair and Correction is as follows:

• If you modify an object in a system in which it is created, you are making Correction to it.
• If you modify an object in a system in which it was not created, then you are making Repair task.

Releasing Tasks and Request:

When new development or correction is complete, developer must release their task and request.
To release a task:
• Find a task from the Workbench initial screen.
• Position the cursor over the task.
• Click on the release button
A request is released by either system Administrator or Project Managers, once all the tasks are released

No comments:

Post a Comment