Transport Request

Transport Request
Transport Request acts as carrier of the configuration settings from one system to another
system on same landscape
EG: Development to Quality Or Golden Client to Testing Client under development system
Each TR contains one or more change jobs, also known as change Tasks. Which contains the
details of complte configuration setting
Task:
Tasks are stored inside a TR, just like multiple files are stored in some folder. Before releasing
the TR ensure all task are under the must release first. Only when TR is released from
development system then only can basis team will move the TR into quality system. Task is a
space reserved for one user & only that user on whose name the task is created only that user
load the data into TR.
TR format : SID K9 5 Digit Request Number
ECC K9 900030
Table For TR : E070 &E071
Create or Release the TR = SE09 / SE10
TR IS 2 Type:
Customizing Request (W) – contains objects that belong to 'client-specific' customizing.

The configuration setting which will be applicable to only the client where we do the
configuration.
Eg: Creation of Plant, S.Loc, Enterprise structure
IN SPRO WHAT EVER WE DO CHANGE ARE SAVED IN THIS TR.
Position the cursor on the TR name or a Task name & choose the Release icon (Truck), a record
of the TR is automatically added to the appropriate import queues of the systems defined in the
TMS.
Workbench Request (K) – contains repository objects and also 'cross-client' customizing
objects. The configuration changes which affects the other client under the development
landscape are saved automatically in workbench transport requests.
EG:
Maximum Changes related to ABAP
Changes related to Access Sequences
The Import Process
After the request owner releases the Transport Requests from Source system, changes should
appear in quality and production system; however, this is not an automatic process.
As soon as the export process completes (releasing of TRs), relevant files (Co files and Data files)
are created in the common transport directory at OS level and the entry is made in the Import
Buffer (OS View) / Import Queue (SAP App. View) of the QAS and PRD.
Now to perform the import, we need to access the import queue and for that, we need to
execute transaction code STMS -> Import Button OR select Overview -> Imports
It will show the list of systems in the current domain, description, and a number of requests
available in Import Queue and the status.
Import Queue -> is the list of TRs available in the common directory and are ready to be
imported into the target system, this is the SAP Application View, at the OS level it is also
known as Import Buffer.

The Import Status
Import Queue shows some standard 'status icons' in the last column, here are the icons with
their meanings, as defined by SAP:
In case, a request is not added automatically in the import queue/buffer, even though the OS
level files are present, then we can add such requests by the following method, however, we
should know the name of intended TR:

Import History
We can also check the previous imports that happened in the system as follows:

Transport logs and return codes
After the transport has been performed, the system administrator must check whether it was
performed properly or not, for that SAP has provided us with the following type of logs (SE01 ->
GOTO -> Transport Logs)
Action Log – which displays actions that have taken place: exports, test import, import and so
forth. Transport Logs – which keep a record of the transport log files.
One of the important information provided by logs are the return codes:
0: The export was successful.

4: Warning was issued but all objects were transported successfully.
8: A warning was issued and at least one object could not be transported successfully.
12 or higher: A critical error had occurred, generally not caused by the objects in the request.
2PLANT
To change the status of a released TR to unreleased we have to run program “RDDIT076”
 Go to SE38
 Enter Program name as “RDDIT076”
 Click execute
 Enter the TR number
 Click execute
 Double click on the request
 Edit the Request type
 Change R (Released) to D (modifiable)
Following Tables contains information about Change Requests

E070 – Change request headers
E071 – Change request Object lists
TRBAT — To check if a Transport entry is in the Process of being imported use table

Transport Request

Uploaded by

Copyright:

Available Formats

Transport Request

Uploaded by

Document Information

Original Title

Copyright

Available Formats

Share this document

Share or Embed Document

Sharing Options

Did you find this document useful?

Is this content inappropriate?

Copyright:

Available Formats

Transport Request

Uploaded by

Copyright:

Available Formats

Transport Request

Table For TR : E070 &E071

Create or Release the TR = SE09 / SE10

Customizing Request (W) – contains objects that belong to 'client-specific' customizing.

The Import Process

The Import Status

0: The export was successful.

To change the status of a released TR to unreleased we have to run program “RDDIT076”

Following Tables contains information about Change Requests

You might also like