1. Objective
As a functional consultant having information about ABAP and BASIS issues might be helpful sometimes for you. In this document I would make a small note of steps you need to download / upload transport request from / to a server. You can use this method to make a backup of your customizing in order to transfer them into another system which in not connected to your customizing system for example.
2. Name conversion
If you have a look your request names thru SE01 you will see the names are in AAABCCCCCC format which AAA is System ID, B is K and CCCCCC is a number which increase sequential.
System keeps the request in format XCCCCCC.AAA that X can be K for header of request and R for body of your request. The rest are the same as above.
3. How to download a request
To download a request go thru AL11.Find "DIR_TRANS" and double click on it. Here you will find "cofiles" and "data" in column "File Name" which system keep hear of requests and body into them respectively.
Double click on cofiles row and go into. Find a request of yours which starts with K(as a header) by Ctrl+F and double click on it. Take the name of directory. You will need this path as source of request to download.
Open a new session and run CG3Y tcode to download your request. In opened window put you source path which you took above + "\" + your request name as "source of file on application server". In target section put a directory path on your computer and the same name as your request's name for file name.
If you have lots of requests this procedure can be time consume so I recommend to make a list of your requests' name and do it one by one as quick as possible. Meanwhile there is function module you can develop your own program to speed up procedure in case you need. The function module is ARCHIVFILE_SERVER_TO_CLIENT.
Up to now you have downloaded the header files of request and you must do the name for body files. The difference here is just going into "data" row of "DIR_TRANS" and the prefix of the name is "R". You can follow the same method to download body of requests also.
4. How to upload a request in a new system
To upload the request into target system you will use CG3Z tcode. in the same method simply upload the requests into new system. I mean specify your local path as source of upload and to take a exact path of target file on application server you can use al11 on new system to see in.
4.1 Import uploaded request into transport request queue on new system
Yes by uploading the request into new system the task is not finished. You must add the requests into queue also. For this issue run STMS and go into your transport request queue. Select "Extras > Other requests > Add".
Specify "transport request" from list which shows your uploaded requests and select your client as "Target Client".
Just this
Omid
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
User | Count |
---|---|
5 | |
4 | |
4 | |
3 | |
2 | |
2 | |
1 | |
1 | |
1 |