KEMBAR78
What Is A Transport Request | PDF
Scribd
Upload
7 views2 pages

What Is A Transport Request

Transport Requests (TRs), also known as Change Requests, are containers for changes made in a development system, recording details such as change type and target system. Each TR can contain multiple change tasks, which are lists of modified objects assigned to users, and can only be released when all tasks are completed. There are two types of requests: Workbench Requests for repository and cross-client customizing objects, and Customizing Requests for client-specific settings.

Uploaded by

Sangita Sen
Copyright
© © All Rights Reserved
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as DOCX, PDF, TXT or read online on Scribd
7 views2 pages

What Is A Transport Request

Transport Requests (TRs), also known as Change Requests, are containers for changes made in a development system, recording details such as change type and target system. Each TR can contain multiple change tasks, which are lists of modified objects assigned to users, and can only be released when all tasks are completed. There are two types of requests: Workbench Requests for repository and cross-client customizing objects, and Customizing Requests for client-specific settings.

Uploaded by

Sangita Sen
Copyright
© © All Rights Reserved
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as DOCX, PDF, TXT or read online on Scribd
You are on page 1/ 2

What is a Transport Request?

Transport Requests (TRs) – are also known as Change Requests. It is a


kind of 'Container / Collection' of

changes that are made in the development system . It also records the
information regarding the type of

change, purpose of transport, request category and the target system.

Each TR contains one or more change jobs, also known as change Tasks
(minimum unit of transportable

change) . Tasks are stored inside a TR, just like multiple files are stored in
some folder. TR can be released

only once all the tasks inside a TR are completed, released or deleted.

Change Task is actually a list of objects that are modified by a particular


user. Each task can be assigned to

(and released by) only one user, however multiple users can be assigned
to each Transport Request (as it

can contain multiple tasks). Tasks are not transportable by themselves,


but only as a part of TR.

Change requests are named in a standard format as: <SID>K<Number>


[Not modifiable by system

administrators]

SID – System ID

K – Is fixed keyword/alphabet

Number – can be anything from a range starting with 900001

Example: DEVK900030

Tasks also use the same naming convention, with 'numbers' consecutive
to the number used in TR

containing them.

For Example, Tasks in the above mentioned TR Example can be named as:
DEVK900031, DEVK900032 …

Workbench Request – contains repository objects and also 'cross-client'


customizing objects. These
requests are responsible for making changes in the ABAP workbench
objects.

Customizing Request – contains objects that belong to 'client-specific'


customizing. As per client

settings these requests are automatically recorded as per when users


perform customizing settings

and a target system is automatically assigned as per the transport layer


(if defined).

You might also like