Copy Transport Request Manually
In the most case, we transport the request CTS (Change and Transport System) between the system landscape. But in some rare case, we need to copy the request to the local file or import the request into another system if the source and target system has no transport route between them.
This blog will show you how to operate the transport request manually.
Step 1. Know the transport request
SAP uses the transport request to record your modification in the dev system. All the modified objects are stored in the transport request file. The naming conversion of transport request is like XXXKYYYYYY. XXX stands for the system id and YYYYYY stands for the request number. Releasing a transport request forces the SAP system to store the request in two files on the server: one is header (also known as co-files) and one body files (also known as data-file).
Step 2. Find the directory of request files
Go to transaction AL11 and find directory parameter DIR_TRANS. Actual path of DIR_TRANS is something like /usr/sap/trans.
The header file of transport request is saved in the path /usr/sap/trans/cofiles and the file name is KYYYYYY.XXX.
The body file locates in the path /usr/sap/trans/data with naming syntax: RYYYYYY.XXX.
Step 3. Download/upload transport request file
There are two transaction codes allow you to download and upload the file from the server.
Upload File – CG3Z
Download File – CG3Y
After the transport files are uploaded to the server, you can import it into the system using transaction STMS.
From here you can find more information about SAP CTS (Change and Transport System).