All About Transport Request
All About Transport Request
- What is Transport Request?
- What is Data File Cofile?
- What are the types of Transport Requests?
- What is Transport Domain Controller?
- How to Configure Transport Domain Controller?
- Transport Route?
- What are the types of Transport Route Editors?
- What is R3 Trans?
- STMS Configuration?
- How to import a Transport Request?
- Transport Request Options?
- What are the Transport Return Codes?
- What are the Transport Logs?
- Transport Status?
- How to change the status of Releases TR?
- How to Deactivate Fully Loaded (Import all) Truck?
- Transport Tables?
This is my first attempt to add info on SCN.
I hope it helps the one in need and will help me as well with your feedback.
Thanks and Regards,
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
- Number – can be anything from a range starting with 90001
- 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.
Types of transport change request:
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 SCC1. You can see the client number next to this type of request.
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.
Domain Controller configuration:
- First decide which system you would like to define domain controller
- Go to SE06
- Click the post installation activity
- Go to STMS
- It will ask for the Domain controller name
- Enter system ID of the Domain controller
- Enter domain_<Sid> as Domain controller name and enter the description
- Click save button
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.
Types of editors (For transport routes):
- 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).
Command : R3 trans –d is used to check the R3 trans connecting to the DB or not.
Trans directory path is – usr\sap\trans
Types of Transport Request:
Transport request types are 3 and they are
1) K type – with change in integrated system to consolidated system
2) C type – without change in integrated system to consolidated system
3) T type – move the one system to another system
Login to the system with DDIC in client 000
Go to the T-Code STMS configured––>standard configured ––> single system, development system, three systems in group
Go to the T-Code STMS ––>overview ––>systems ––> sap systems ––>external system ––>then we have to give the system name, <Sid>
Steps for Importing Transport Request:
- Check if we have an approval on mail to Transport.
- Check where we need to Transport (Quality or Production)
- Check if STMS is configured
- 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
- Select the Queue from the list (Quality of Production accordingly)
- Refresh the list
- Check your Request number to be imported.
- 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.
- Select type of request Immediate ,at start time or after an Event
In the Execution Tab select Type of Import Synchronous or Asynchronous
Synchronous : Dialog or batch process is blocked until import has ended in synchronous transport
Asynchronous : 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
Transport performed without errors
Warnings were issued. All objects were transported successfully.
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)
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)
Indicates import cancelled due to system down while import, due to user expired during import, due to insufficient roles and authorization.
1) ALOG – It Specifies the Application Log
2) SLOG – It specifies the Job steps
3) ULOG – Tp commands
D : Modifiable
L : Modifiable Protected
O : Release started
R : Released
N : Released (with import protection for repaired objects)
Note: 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)
How to Deactivate Fully Loaded Truck:
Never click on the Fully loaded Truck during transport
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
3. Click on System Overview (3 boxes button)
4. Double click on the system you want to disable Import All button
5. Goto Transport Tool Tab in edit mode.
6. Click on ADD button & add NO_IMPORT_ALL with value 1
7. Save & exit
8. Repeat above steps for all the systems in which you want to disable import all button
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
Disclaimer and Liability Notice:
We will not be held liable for any damages caused by using or misusing the
Information shared in this document, and anyone using these methods
does so at his/her own risk.
Nice document 🙂
Nice document 🙂
Good document... Especially(To change the status of a released TR to unreleased we have to run program “RDDIT076”)
This is a good information and a must to know.
Very nice info thank you....
Thank you for the document.
thank you for this document. I have a question about transport sequentiality.
Let's say I have an object (ex. a Report), which I edit, include in CR DEVK000001 and release the CR (but not transport). Then I change the Report again, include it in DEVK000002 and release.
These is my understanding, please correct me if I'm wrong:
1) If I transport DEVK000001 and DEVK000002 together to a Q environment, Transport Manager will follow the sequence DEVK000001 -> DEVK000002, thus only DEVK000002 will be considered for the Report, since it is the last version;
2) If I transport DEVK000001 first and DEVK000002 secondly, I will obtain the same result as before, but both versions will be present in the target environment;
3) If I transport DEVK000002 first and DEVK000001 secondly, anyway, I will have the first version in the target environment, and the last version will be then considered as an old one.
4) If point 3 is correct -> what happens when I transport from this Q environment to P? Will I have the same possibilities as in the 3 points above?
I hope I was clear.
This was very helpful. Thank you
My config customisation is not auto generating transports.How best should i activate tht
Thank yu 🙂 learned new one today regarding reverting of TR from released to unreleased.
In some systems, the RDDIT076 trick works well, but in others, during the second release of TR it seems that the cofile / datafile keeps the first release data and are not overwritten with the second, despite no error occurs during both releases…
Anyone has face this behavior and has an explanation / solution for it?