The Common Transport Directory 

To store the data files between transports, we recommend you use the common transport directory as shown in The SAP System Landscape. The three systems use this directory for all exports and imports. All transports should run over this directory.

To protect the integrity, validity, and consistency of the data being transported, consider the following points:

·        The common transport directory is generally mounted using NFS mount (UNIX) or Windows NT share. To prevent misuse, place those systems that share the transport directory in a separate secure LAN (see Network Infrastructure).

·        Only the system administrator should be able to execute imports (using tp or TMS).

·        Archive the data in the transport directories so that you can review the transport activities if necessary. This is especially important for the transport logs and the TPPARAM configuration file (prior to Release 4.5). See also SAP Note 41732 for information about deleting information in transport directories.

As of Release 4.5, the transport profile is generated and maintained by TMS. Therefore, maintaining the TPPARAM file at the operating system level is no longer necessary.

·        If you have several SAP Systems, separate them into logically differentiated system landscapes.

·        If you use TMS, you can use a separate transport directory for the productive system instead of the common transport directory.

If you consider this option, then take the following points into account:

¡        You increase security by making it harder for unauthorized persons to import data into the productive system.

¡        You must explicitly start the transport into the productive system. The user who starts the transport must have system administration authorizations (transport super user).

¡        You no longer receive the return values or logs in the export system.

¡        In addition, you also have to copy any transport files from Hot Packages into both transport directories.