SAP Note

556734 - FAQ Transport: Setup and further information

Symptom
1. Are there general recommendations for importing transports?

2. What do I need to consider when setting up the transport?

3. Can I use the transport directory between NT and UNIX?

4. How can I tidy up my transport directory?

5. Are transports possible between systems with different Support Package versions?

6. Are transports possible between different R/3 releases?

7. Are there any general points to note on switching tp and R3trans?

8. Where can I find more information on the transport?

Other Terms
FAQ, Q+A

Reason and Prerequisites

Solution
1. Are there general recommendations for importing transports?

If possible, the TMS should be used and not direct tp calls.If possible, you should import
transports if nothing else is running in the system (online/Batch/Batch Input/Direct
input/...)or at least nothing that affects the objects contained in these transport
requests.There should be at least two free background work processes in the system (note
26966), that can also be scheduled with high priority as of Release 4.6. All application
servers must access the same transport directory which is set via the profile parameter
DIR_TRANS.This is possible by attempting the call by double-clicking via the AL11. There are
also test options from the TMS via OVERVIEW -> SYSTEMS and there R/3SYSTEM -> CHECK ->
TRANSPORT DIRECTORY.Furthermore the programs tp and R3trans should be current.The versions
can be checked with tp -V and R3trans -V.A function test of the tools can be checked from
the TMS (OVERVIEW -> SYSTEMS and there R/3SYSTEM -> CHECK -> CONNECTION TEST or TRANSPORT
TOOL).

2. What do I need to consider when setting up the transport?

All systems that create the same transport group in the TMS must use the same transport
directory while systems from different transport groups must use different transport
directories.The following notes are helpful when you set up the required directory accesses
via share or mount: 28781, 62739, 45516, 117395, 201199, 538268.
Up to R/3 Release 4.0, the file TPPARAM must be edited directly in the DIR_TRANS/bin
directory.As of R/3 Release 4.5, the parameters can then be maintained from R/3 in the TMS
under SYSTEM OVERVIEW after you double-click on the corresponding system.The parameter
TRANSDIR is automatically global (checkmark in column global) in the TMS.This global
TRANSDIR can be different than the transport directory used by the group (if there are
different groups).With the TPPARAM, TRANSDIR must correspond with DIR_TRANS.Furthermore the
batch jobs RDDIMDP (for client 000) or RDDIMPDP_CLIENTnnn (for the respective client nnn)
must be scheduled for every client.These jobs must also be released event-dependently and
with sufficient authorizations (for example as user DDIC).This can be checked using
transaction SM37.

3. Can I use the transport directory between NT and UNIX?

When you refer to note 28781 it is also possible to use a common transport directory between
NT and UNIX systems.

4. How can I tidy up my transport directory?

If necessary, before the clean-up the files should be saved first because the logs provide
information about system changes and may be needed for the revision.After that the older log
files can be deleted via the commands "tp check all" and "tp clearold".You will find more
detailed descriptions in notes 41732, 168175, 312843, and in the online documentation.

5. Are transports possible between systems with different Support Package versions?

Such transports are technically possible, but inconsistencies can occur between the versions
of the transported objects.For example if you first import the Support Packages in the
development system and then change an object with a transport request, the version of the
transport request is valid there.If you first import the transport request in the subsequent
system and then the Support Packages, the version of the Support Packages is active there.

6. Are transports possible between different R/3 releases?

Technically, such transports are often possible.However, the inconsistencies described above
can occur between the object versions.Further technical and logical problems for the various
releases are outlined in notes 60928, 120151, 126776 and 330267.

7. Are there any general points to note on switching tp and R3trans?

The versions of the tp and R3trans must always match the respective kernel release of the
system and should be in the directory /usr/sap/<SID>/SYS/exe/run.You can check the version
and patch level with the commands tp -V or R3trans -V.See note 19466 for the update of both
the R/3 kernel and the tools tp and R3trans.For the release upgrade via an upgrade,
additional updates of these tools may be required in other directories.You must then read
the information in the corresponding upgrade note or guide.

8. Where can I find more information on the transport?

- Course BC 325
- SAP Online Library -> Basis -> Change and Transport System (BC-CTS)
- SAP Service Marketplace, Alias /SWCHANGEMANAGEMENT

Manual Activities

Attributes
Key Value

Other Components BC-CTS-TMS (Transport Management System)

62739 Configuring a central transport host

60928 Transports between Release 3.0 or 3.1 and Release 4.0

556972 FAQ OCS: Recommendations for error scenarios

556946 Transport FAQ: TMS

556941 Transport FAQ: Error scenarios

538268 Log files with transport directory of length 0

536068 tp clearold: Termination with long transport request names

45516 tp error: no temporary protocol ...

41732 Deletion of data in transport directory

330267 Transports between Basis Releases 4.6* and 6.*

312843 tp CHECK/CLEAROLD latest News

28781 Central transport directory NT/UNIX

26966 Background jobs do not start when transporting

201199 Cannot access file &

19466 Downloading SAP kernel patches

168175 tp check/clearold problems

126776 Transports between Releases 4.5 and 4.6

120151 Transports between Release 4.0 and 4.5

117395 Authorization problems for file I/O on Microsoft Windows

This document is referenced by

201199 Cannot access file &

70547 CC-TOPIC: Client transport

330267 Transports between Basis Releases 4.6* and 6.*

538268 Log files with transport directory of length 0

536068 tp clearold: Termination with long transport request names

28781 Central transport directory NT/UNIX

126776 Transports between Releases 4.5 and 4.6

60928 Transports between Release 3.0 or 3.1 and Release 4.0

120151 Transports between Release 4.0 and 4.5

814639 Transport requests disappear from the buffer

312843 tp CHECK/CLEAROLD latest News

26966 Background jobs do not start when transporting

556972 FAQ OCS: Recommendations for error scenarios

556946 Transport FAQ: TMS

117395 Authorization problems for file I/O on Microsoft Windows

168175 tp check/clearold problems

45516 tp error: no temporary protocol ...

556941 Transport FAQ: Error scenarios

62739 Configuring a central transport host