1)After releasing my change request, I can't find the transport files in the tra

nsport directory.
Solution:Make sure you released the request, as well as the tasks under it (the request i
s the part of the tree directly under the word "Transportable"). Check the actio
n logs using SE09 for errors. If there were no errors, try re-transporting an ob
ject by changing it and creating a new request. Before releasing the task or req
uest, go to SE09 and list the request. If the request is listed under "Local", i
t can NOT be transported to another system.
2)My change request is always local, but I want it to be transportable
Solution:The problem lies in either the workbench setup, the development class assigned t
o the objects you wish to transport, or both. Check the workbench setup with SE0
6->Display. Is your system set as a productive system? If so, change requests us
ually are not transportable. Try creating a new development class Z000, and choo
se any transport layer that the system allows you to choose (if your system does
not allow you to choose any transport layers, then the workbench is not set up
to allow any changes to be transportable). If it allows you to choose several la
yers, create on new class for each layer, and a new change request for each clas
s. Then go to SE09 and check if your requests are transportable. If they are tra
nsportable, try to release one of the development classes (release the task and
the request) and check that the files are created.
3)The system won't let me release a request because the the "target system is th
e same as the source system."
Solution:Click on the request, hit Shift+F6 (Change), and change the target system to a S
ID other than the source system. If your system won't let you change it to a SID
that works, you are either trying to transport from the wrong system, or you ne
ed to redo your system landscape.
4)How do I redo the system landscape?
Solution:This should be done by a consultant during installation, and should not be chang
ed after installation. If you really want to do it yourself, release all locked
objects, log onto client 000 with DDIC, go to SE06, choose the landscape you wan
t (usually 2- or 3-system group, and press Create. Tell the system which SIDs do
which roles, and the rest is set up automatically.
5)I want to import objects into a system other than the one for which the transp
ort files are targeted.
Solution:Use the override options
6)After using the override options, tp won't let me delete the request from the
buffer.
Solution:-

Re-import the request, and then delete it from the buffer. If you cannot re-impo
rt (because, for instance, it is a very old request, and you do not know if re-i
mporting will overwrite newer object), you can delete the entries directly from
the file /usr/sap/trans/buffer/SID. This of course is not a "real" solution, but
it does work (the "real" solution maybe would involve further editing of the E0
70, E071, or E070C tables, but I don't know).
7)I have created local objects in both the target system and the source system.
Now I want to organize development and create objects only in the DEV system, an
d allow no direct changes to the target system. What do I do about the objects a
lready created?
Solution:They need to be reassigned to a development class before they can be transported
. Create a development class (or use an existing one) and test to make sure its
objects can be exported and imported successfully.
8)How do I delete all the old change request/task clutter from my system.
Solution:If none of the tasks in the request have been released, the entire task/request
can be deleted. Before deletion, however, you should check to make sure that the
related objects are either changed back to the state they were in before the ch
ange that resulted in their being linked to the change request.
9)The system says that I have to release all locked objects before I can perform
a certain task. How do I find out what objects are locked?
Solution:Look in the tables TLOCK, E070, E071, and E070C. Sometimes, data in these tables
can become orphaned, and may need to be processed manually (this is rarely nece
ssary).
10)What do I do with all these transport files?
Solution:You can backup and delete old transport files every once in a while. Directories
to be backed up and deleted in the /usr/sap/trans directory include: data, cofi
les, log, olddata, EPS/out, EPS/log, and put/*. Note that SAP-delivered files ca
n be deleted without backup; this includes directories such as put/exe, put/tool
s, and EPS/in.