All About Transport Request
All About Transport Request
All About Transport Request
Transport Route?
What is R3 Trans?
STMS Configuration?
Transport Status?
Transport Tables?
Transport request:
An SAP Transport is a package which is used to transfer data from one SAP installation to another. This change can be
from a small change to major change. It can be considered as an “update”, with the only difference being that SAP
transports are made by the SAP users themselves. Each TR contains one or more change jobs, also known as change
Tasks. All the Tasks are stored inside a TR for eg: multiple files stored in some folder.
TR can be released only once, all the tasks inside a TR are completed, released or deleted. Change requests are
named in a standard format as: <SID>K<Number>
SID – System ID
Once the Transport request is released, it creates a Data file and Co-file.
Cofile : having the attributes of data file. Co-file is created “K”, Co Files contains the controlling data
Data file: having the data file is created “R”, Data files contain the database details.
1) Workbench Request: Workbench requests are cross-client. Changes done in one client are automatically reflected
in all other clients.
2) Customizing Request: Customizing requests are client specific. The changes will not be reflected in other clients.
For e. g a change done in ECC Dev system will not be reflected in other clients in the same ECC Dev system. We have
to do a client copy using T-code SCCL. You can see the client number next to this type of request.
3) Transport of copies:
A transport of copies will move the latest version of an object included to the system of your choice, but will not
assume that you want to move it to production. Therefore, it transports a “copy” of the object but assumes that its
final destination is only the system that you are moving it to. A normal transport on the other hand would assume it’s
going to the system that you’re moving it to (QA) and all other systems downstream from it. (Production)
Also for this reason, we can move all the transports of copies we want and we won’t see them affect the downstream
system. (Production) They will only affect the system that we move them into. You will still be opening a single
Customizing or Workbench request to move your changes to production, but you will only be releasing these requests
when you know you are ready to move. For unit testing in QA you will be moving Transport of Copies until you are
satisfied with what you have. At this time, you will release your original change request and move it into QA for final
User Acceptance testing. By doing this, you will be using a single transport for your change that will ultimately go to
production.
Transport Domain Controller: There will be only one Transport Domain controller in the Landscape. It is used to
maintain the information of all the systems in the Landscape. Initially The DEV system is configured as TP Domain,
but later we can move it to other systems .Mostly it remains in the DEV system only. It is a post installation activity.
First decide which system you would like to define domain controller
Go to SE06
Go to STMS
Example for customizing changes are - Changes in SAP Script or Standard Text creation etc..
Transport Route:
STMS-–>Overview––>Transport route––>change button ––> click the DEV, QAS & PRO––>click the add transport
route tab ––>then we have to give the <Sid>, transport layer, system name.
Graphical editor
Hierarchical editor
R3 Trans: R3trans is used to transport data between SAP Systems and for the migration between different SAP
releases. However, note that R3trans is usually called from other programs, in particular from TP (Transport Control
Program) and R3 (upgrade control program).
STMS configuration:
Go to the T-Code STMS configured––>standard configured ––> single system, development system, three systems in
group
(Or)
Go to the T-Code STMS ––>overview ––>systems ––> sap systems ––>external system ––>then we have to give the
system name, <Sid>
For eg. if we need to move to production go to Production System then T-code STMS in Production
system and if quality then login to quality system
Click on the request number and Adjust the queue using symbol
Once queue is adjusted click on the Request number and click on Half Loaded Truck
Never click on the Full loaded Truck. (if we do so system will be down completely) .To disable the Truck go to topic no
1.11
Once you click on the Truck you will get below options and fill the information accordingly.
Synchronous : If we select Synchronous that’s means request update in same table which is already in target
system. Dialog or batch process is blocked until import has ended in synchronous transport
Asynchronous: If we select Asynchronous that’s means request created in new component as on existing
component. Dialog or batch process is released after import is started in asynchronous transport.
1. Leave Transport request in queue for later Import: This check box causes the requests to be imported again in
correct order with the next import of all requests.
2. Import Transport requests again: This also imports the transport request if it has already been imported.
3. Overwrite originals: It imports objects if the objects are the originals in the target system. The object directory
entry determines the SAP system where the original version of an object is located.
4. Overwrite objects in unconfirmed repairs: It also imports objects, if they were repaired in the target system and
the repair is not yet confirmed.
5. Ignore Non-permitted transport type: It imports the transport request if this transport type was excluded by
particular settings in the transport profile.
6. Ignore Non-permitted Table Class: It imports data records of a table even if the delivery class of the table does
not permit the data records to be imported
7. Ignore predecessor relations: If you want to import all the requests for one or several projects, but additional
requests from other projects exist for which there are dependencies .This option is switched off by default, which
means the predecessor’s relationships will not be damaged.
8. Ignore Invalid Component Version: This option is used to avoid component mismatch issue
Return Codes
Return code Meaning
0008 Individual objects could not be transported successfully. You must analyze and correct the errors.
Examples of import errors: Original object was not overwritten, Repaired object was not
overwritten(This can be syntax error, program generation error, dictionary activation error or
method execution error)
0012 A critical error has occurred, probably not caused by the contents of the request. You must
inform your system administrator. (indicates import cancelled, program cancelled due to job,
Import cancelled due to object missing, import cancelled due to object not active)
0018 Indicates import cancelled due to system down while import, due to user expired during import,
due to insufficient roles and authorization.
Transport Logs:
3) ULOG – Tp commands
Transport status:
D : Modifiable
L : Modifiable Protected
O : Release started
R : Released
Note: To change the status of a released TR to unreleased we have to run program “RDDIT076”
Go to SE38
Click execute
Click execute
We can deactivate the full Truck option by setting a parameter No_Import_all = 1 using below steps:
1. Log on to your TMS Domain Controller.
2. Tcode – STMS
4. Double click on the system you want to disable Import All button
8. Repeat above steps for all the systems in which you want to disable import all button
TRBAT — To check if a Transport entry is in the Process of being imported use table