0% found this document useful (0 votes)
73 views6 pages

SAP Transport Requests

Copyright
© © All Rights Reserved
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as PDF, TXT or read online on Scribd
0% found this document useful (0 votes)
73 views6 pages

SAP Transport Requests

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

2024

Transport Requests in SAP


SAP PP/QM LEARNINGS
VENKATA SAI NASINA
Transport Request (TR) in SAP
Transport Request is container of changes which is made in SAP Development system as per
Customer requirement.

Using TR we can transport or move all changes/ Customize setting from DEV to QA to Production
System.

To transfer or copy the changes that have been performed in the development system to
subsequent systems or from lower systems to any higher system, SAP Software Logistics use transport
requests which act as a container for objects that semantically belong together. Roughly speaking, a
transport request contains objects that form a testable unit. Transport requests can be divided into the
following:

Workbench requests that are transport requests for transporting cross-client Customizing and
repository objects.

Customizing requests that are transport requests for transporting from client-specific
Customizing.

Software logistics provides tools and processes with which you can manage your system
landscape in all lifecycle phases. For the developing of changes in the development system and
transporting them into the subsequent systems, the following roles are involved:

Naming Convention for Transport Request:


System Name < Co file created in Data base > Number can be anything from starting with 9xxxx

Ex: If TR RD1ERP90003 generated in development system then as per naming convention Here SID is RD1
and Co file created in Data base ERP.

Types of Transport Request


There are two standard types of transport requests, and they are:

1. Workbench Request : Workbench requests are cross-client. Changes done in one client are
automatically reflected in all other clients. If we use ABAP Logic during changes then use
Workbench Request.

2. Customizing Request : Customizing requests are client specific. The changes will not be
reflected in other clients. for Example if we made changes in Dev server-010 system then this will
not reflected in Dev server -015 system we need to do copy client by TR (T code ; SCC1) we use
this customizing request only when we are not using ABAP Logic during changes in system.
Releasing TR :
T code: SE01

If you know the TR number then go to SE01->Display tab -> Put TR No. -> Click on Display Push
Button.

1. Select Sub TR EH7K900456 --> Click on truck Icon Button so that Sub TR will be release.

2. Again Select Main EH7K900455 --> TR Click on Truck Icon Button so that Main TR will be
release

Note: System doesn’t allow you to release TR without releasing Sub TR.

3. Once you Release TR then Right Check mark will be visible next to TR
Reverting SAP Released Transport Request To Unreleased Status
If You want to revert the changes of TR from Released to Unreleased then refer below mentioned Process.

1. Run T code SE38 /SA38

2. Enter Program RDDIT076 in SE38/SA38 & Execute

3. In the Selection screen Enter Main TR number which you want to change status.

4. Select TR and Click on binoculars

5. Click on Pencil Button for Change Mode.


System Allow you change status From “Released” to “Modifiable” which is "R to D'" & SAVE it

Now TR status Changed as D- Modifiable

For Information Purpose ;

Types of TR Status Request

Type of Request

You might also like