KEMBAR78
SAP Transport Requests Guide | PDF | Information Technology Management | Areas Of Computer Science
Scribd
Upload
60 views6 pages

SAP Transport Requests Guide

Transport requests (TRs) contain change tasks that modify objects in the development system. Each TR can have multiple change tasks assigned to different users, but a single user is assigned to each task. The project manager creates the TR and assigns tasks to project members. When all tasks are complete, the manager can release the full TR to the target system.

Uploaded by

supriya
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
60 views6 pages

SAP Transport Requests Guide

Transport requests (TRs) contain change tasks that modify objects in the development system. Each TR can have multiple change tasks assigned to different users, but a single user is assigned to each task. The project manager creates the TR and assigns tasks to project members. When all tasks are complete, the manager can release the full TR to the target system.

Uploaded by

supriya
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/ 6

 Transport Requests (TRs) – 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, the purpose of transport,
request category and the target system. It is also known as Change
Requests.
 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 …
 The project manager or designated lead is responsible to create a TR
and assign the project members to the TR by creating task/s for each
project member.
 Hence, she/he is the owner with control of all the changes that are
recorded in that TR and therefore, she/he can only release that TR.
 However, assigned project members can release their respective
change tasks, once completed.
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).

SE01 – Transport Organizer – Extended View


Create a Change Request

 Change Request can be created in two ways:


o Automatic – Whenever creating or modifying an object, or when
performing customizing settings, the system itself displays the
'Dialog box' for creating a change request or mention name of an
already created request, if available.
o Manually – Create the change request from the Transport
Organizer, and then enter required attributes and insert objects.

You might also like