Transport Between UNIX and Windows Systems 

When you use the Change and Transport System (CTS), various files described by the kernel, tp.exe, and R3trans.exe are created in the transport directory. The files of the subdirectories log, buffer, and cofiles are opened in default mode (=text mode), while the files of the transport subdirectory data are described in binary mode.

When the files are written in text mode, there are the following differences between the two operating systems:

·        UNIX writes a line feed at the end of each line.

·        Windows writes a carriage return/line feed at the end of each line.

When the files are written in binary mode, a line feed is written under UNIX and under Windows at the end of each line. The files that are written in text mode under Windows cannot therefore be read under UNIX, and vice versa.

To set up a common transport directory for Windows and UNIX, you must choose the binary mode as the default mode to describe the files. You can set this using profile parameters or environment variables. These parameters are not required for transports between pure Windows systems performed in the conventional text mode.

Adjusting Modes to Open a File

To use a common transport directory for both operating systems, you must adjust the mode to open a file under Windows in the UNIX text mode.

·        For the transport tools, you can set this using the transport profile parameter ABAPNTFMODE or the environment variable abap/NTfmode.

·        For the SAP kernel, set the mode to open a file using the profile parameter abap/NTfmode.