What are the types of transport requests?

There are four types of transport requests:

1. customizing request (Contains client specific changes recorded in a single client)
2. Workbench request (Contains changes made to the repository objects of ABAP work
bench)
3. transport of copies (Allows to transport any sub objects into object list to any other
SAP system)
4. relocation (Use this when development system of a complete package is to be changed
on permanent basis)
Transports of Copies and Relocations
Transports of copies
You can use this request type to transport objects to a specified SAP System.
The objects are transported with the version they have in the current SAP System. The original
location of the objects remains unchanged. There is no delivery to another SAP System.

Relocations without package change

You can use this request type if you want to develop objects in another SAP System on a
temporary basis. For example, you may want to make special developments in a separate
SAP System so as not to interfere with the development process.
A relocation without package change basically offers the same functions as a transport of
copies. This request type allows you to move the original location of objects to the target
system.

Relocations with package change

You can use this request type when you want to change the development system of individual
objects on a permanent basis.
This request type allows you to change the original location of objects to the target system and
change the package of the objects at the same time.
The package is changed automatically. If you choose a suitable package, the objects have the
right transport attributes immediately after you import them into the target system of the
request. Here you can edit them in transportable change requests without needing to make
any further settings.

Relocations of complete packages (with change of transport layer)

You can use this request type when the development system of a complete package is to be
changed on a permanent basis.
This request type allows you to automatically change the transport layer of the package.
To do this, you only need to specify the package and transport layer to which you want to
assign the package. The object list of the request is set up automatically and contains all
objects in the package.
The transport layer is changed automatically. If you choose a suitable transport layer the
objects have the right transport attributes immediately after you import them into the target
system of the request. Here you can edit them in transportable change requests without
needing to make any further settings.
You have to set up the object list yourself for the first three request types. For information on
this, see
Including Objects in a Request Manually.
You can only enter complete objects in the object list of relocations. If there are sub-objects
(for example, from other requests), you can let the system convert them to the
corresponding parent objects. To do this, go to the Transport Organizer request overview
and choose Request/task Object list Sub-objects Complete objects.

Introduction about transports in SAP BW

How to create transport request:

We can create transport request using T-Code SE01 or SE10. I am giving SE01
screen shots.
Open SE01 click on transports tab.
Now you will get the below screen.

i)
ii)

By default you will get your username in User field. If you want to create
transport request for another user, then specify the name.
We will have 4 different types of transport requests in BI system. We will discuss
this in next step.
Once you give the username, just click on create (marked in red on top in the
above screen.)
Note: if you want see the transport request created by any person, give the
username, select type of transport request and status of request. We have two
statuses for transport request i) Modifiable and ii) Released.
Then click on display, you will get the list.
Once you click on create, you will get the below screen.

The system will ask you to select which type of transport you want to create.
Mainly we have two types of transport requests, they are
i)
ii)

Customizing Request.
Workbench Request.
Customizing Request: Changes to Customizing settings are recorded in
Customizing requests. Customizing request records client dependent objects

like table entries, SPRO configurations. Client dependent objects are only
available to particular client.
When you create Customizing requests, the transport target is automatically
assigned the standard transport layer by the SAP system.

Workbench Request: Workbench requests record changes made to ABAP

Workbench objects. Workbench request records client independent objects like
reports, Functions, tables. Client independent objects are available across the
system irrespective of client.
We have local and transportable Workbench requests. (Local Workbench requests
have the target system as <space>).
The package of the object and the transport route settings in the Transport
Management System determine whether changes are recorded in a local or a
transportable Workbench request.

Now we will discuss about the other 4 options in the above screen.
Transport of Copies: If you want to create the new transport with the same
objects in some other transport, then you have to select this option.

Relocation of Objects without (W/O) Package Change: Using this you can
move the original location of the objects entered in the object list to the target
system. The objects still exist after these transports, and you can change them
(in repairs). If objects were transportable before the transport, they remain so,
because the objects are still assigned to the same packages and transport
layers.
1)

We can use this if we want to create object into another SAP system for

temporary basis
2)

It is having same functions as transport of copies

3)

It allows you to move original location of object.

Relocation of Objects with Package Change: using this you can change the
original location of the objects entered and reassign the objects to an
appropriate new package.
The package change means that you can automatically adjust the transport
attributes of the objects to the new development system. This means that you
edit the objects immediately after they have been imported into the target
system.
1)

Select this type if you want to change the development system for an

object permanently.
2)

Allows you to change the original location of an object.

Relocation of Complete Package: Using this you can simultaneously move the
original location of all objects in a package to the target system and
simultaneously assign the package to another transport layer.
1)

Select this when development system of a complete package is to be

changed.
2)

It allows you to change the transport layer of the package

Once you select the type of transport request you want to create, click on
continue to move further.
Now you will get the below screen.

1)

Give the short description for the transport request. Transport number is

system generated.
2)

Give the project code for this transport or you can use F4 selection for

search.
3)

Specify the target name for the transport request.

4)

In Tasks tab, by default system will assign your user name and will create

one child transport (task) under your main transport. If you want to create child
transport for any other user, then give the username under tasks.
5)

Once you enter the required information click on Save, system will

generate the transport request.

You can see in the below screen.

Once you create the transport request, the status of the request will be
modifiable.
As we discussed earlier, we have 2 transports in the above screen. One is main
transport and other one is child request.

We can see the properties and the objects included in particular requests using
Tcode SE01.
Goto SE01 click on Display tab give the transport number and click on
display.
See the below screen.

In the next screen select the transport and click on display to see all the details
about the transport request.

Now we will get the below screen, which consist of 3 tabs, they are
I)
Properties
II) Objects
III) Documentation
As shown in the below screen.

Properties: This tab contains the general information about the transport request
like project code, target system, status and last changed date.

Objects: This tab will contains all the objects which are included in this transport
request.

Documentation: This tab will contain the documentation about the transport if
we maintain.

How to release transport request:

Once we check the transport request in SE01 and confirms transport is Ok, we can
release the same to move further.
In menu bar, click on request/task Click on Release.

Once you release the transport request, you can find the same in transport queue
(STMS) in the next system based on transport connection maintained in your
system.

What is the difference between TP and

R3TRANS
TP is a transport tool used to control the import and export of program and table changes made
within the SAP system in order to transport them and R3TRANS does them using scripts, that
were generated from TP. In short R3TRANS is the tool, that does the main work for TP by
initiating it to transport file from OS to DB and vice versa.
TP controls the process and calls several tools, like R3TRANS but also e.g. DDIC-Activation.

TP commands:
tp export <change request>: The complete objects in the request from the source
system will be transported. This command also Used by
SAP System when it releases a request.
tp r3e <change request>:
R3trans export of one transport request.
tp sde <change request>:
Application defined objects in one transport request can
be exported.
tp tst <change request><SAP system >: The test import for transport request can be
done using this command.
tp createinfo <change request>:
This command creates a information file that is
automatically done during the export.
tp verse <request>:
This command creates version creates versions of the
objects in the specified request.
tp showbuffer <sid>:
Shows all the change requests ready to be imported to the
target system.
tp count <sid>:
Using this command users can find out the number of
requests in the buffer waiting for import.
tp go <sid>:
This command shows the environment variables needed for
the connection to the database
of the <sid> or target system.
tp showparams <sid>:
All the values of modifiable tp parameters in the global
parameter file. The default value is shown for parameters
that
Tp showbuffer<sID> :
show all change requests ready to be imported to the
target system
Tp count<SID>
number of requests in the buffer waiting for import
Tp importall<SID>:
Imports all the request from buffer to the target system
Tp put<SID>
imports all the request from buffer to the target system
and locks the system
tp sapstart <sid>:
To start the R/3 system.
tp stopsap <sid>:
To stop the R/3 system.
tp dbstart <sid>:
To start the database.
tp dbstop <sid>:
To stop the database
tp locksys <sid>:
This command locks the system for all the users
except SAP* and DDIC. The users that have already logged
on are not affected by the call.
tp unlocksys <sid>:
This command unlocks the system for all the users.
tp lock_eu <sid>:
This command sets the system change option to
"system can not be changed" tmporarily.
tp unlock_eu <sid>:
This command unlocks the system for all the
changes.
tp backupall <sid>:
This command starts a complete backup using
R3trans command. It uses /usr/sap/trans/backup directory
for the backup

R3trans commands:
R3trans -d :
This command is used to check the database connection .
R3trans -u <int>:
Unconditional mode can be used as we have seen in the
above example.
R3trans -v :
This is used for verbose mode. It writes additional details to
the log file
R3trans -i <file>:
This command directly imports data from data file
without a control file.
R3trans -l <file>:
This provides output of a table of contents to the log file.
R3trans -n :
This option provides a brief information about new
features of R3trans.
R3trans t:
This option is used for the test mode. All modifications in
the database are rolled back
R3trans ba:
This command is used for a complete backup. we will see in
the next paragraph how to use the Control file for the
backup.
R3trans bd:
This command is used for a delta backup if the user does
not want a complete backup.
R3trans bi:
This option will display backup information
Manual Import process of a transport at Os level with TP program
This article answers following queries :

How to import a transport manually with TP program?

How to import a transport without using STMS in SAP?

How to import a transport at Os level in SAP ?

How to insert a request into the import queue of an SAP R/3 system manually?

When performing a request import manually, what will happen if client is not
mentioned?

Can we manually import all the requests that are present in the import queue of an
SAP system? If so, how ?

What is the parameter file name which was similar to TP_<domain>.PFL file which
was used in older SAP versions?

What will happen in the background if a transport request is added to the import
queue of an SAP system ?

What will happen if the client in which you want to import does not exist in the target
system?

-----------------------------------------------------------------------------------------

Sometimes, there will be situations like you have to process transport imports
manually. This can be done by TP program from the operating system level.
Transport
control
program
TP
is
controlled
by
a
parameter
file
TP_<domain>.PFL which is present under bin subdirectory of the transport
directory.
Please note in older releases of SAP R/3, the file is termed as TPPARAM.
Before using TP for the first time, it is suggested to test the connection to the
desired target system.
To perform this test, following command can be used.
tp connect

<target system> pf=<complete path of the parameter file>

If this test results are fine you can proceed further otherwise you need to
troubleshoot the same and identify the reason for the same.
In order to insert a request into the import queue of an SAP R/3 system, use the
following command:
tp addtobuffer <request>
parameter file>

<target system> pf=<complete path of the

If the above command is successful then, datafile and cofile of the request will get
copied under respective data subdirectory and cofiles subdirectory of the
transport directory.
As the request is inserted to the import queue, it can now be imported using the
following command.
tp

import <request>
parameter file>

<target system>

pf=<complete path of the

In case you would like to import all the requests that are present in the import
queue of an SAP system in the current sequence then provide the following
command at oslevel.
tp

import all
file>

<target system>

pf=<complete path of the parameter

You can add the following to specify a specific client for import:
client = <number of the client>
If the client is not mentioned, the data is copied to the client with the same
number as the client from which the data was exported.
If the client into which you would like to import a request does not exist in the
target system, the import terminates with an error message.