SAP System Directories on UNIX

Here you can find information about the directory structure of an SAP system. An SAP system contains the following types of directories: Physically shared directories, which reside on the global host and are shared by Network File System (NFS) Logically shared directories, which reside on the local host with symbolic links to the global host Local directories, which reside on the local host

The figures below assume that you have set up one file system for the SAP system mount directory /<sapmnt> and one file system for the /usr/sap directory.

Standard SAP Directories for an ABAP System (Unicode or Non-Unicode)

Standard SAP Directories for a Dual-Stack (ABAP+Java) System

Standard SAP Directories for a Java System (Unicode)

SAP System Directories in Detail

Directory Description

/<sapmnt>/<SAPSID> Software and data for one SAP system This directory and its subdirectories need to be physically shared using Network File System (NFS) and mounted for all hosts belonging to the same SAP system. It contains the following subdirectories: exe This directory contains executable kernel programs. In an SAP system with distributed instances, this directory must be shared for all hosts with the same operating system. Note

Dual-stack (ABAP+Java) system only:

exe contains a folder uc and a folder nuc, each with a platformspecific sub folder: o <sapmnt>/<SAPSID>/exe/uc/<platform> is used in Unicode systems. Executable kernel programs are replicated from this directory to the exe directories of each Unicode system instance. o <sapmnt>/<SAPSID>/exe/nuc/<platform> is used in nonUnicode systems (see below). Executable kernel programs are replicated from this directory to the exe directories of each non-Unicode system instance (see below). End of the note. global This directory contains log files. In an SAP system with distributed instances, this directory must be shared for all hosts with the same operating system.

Directory profile

Description

This directory contains the start and operations profiles of all instances. In an SAP system with distributed instances, this directory must be shared for all hosts with the same operating system. /usr/sap/<SAPSID> Instance-specific data, symbolic links to the data for one system This directory contains files for the operation of a local instance. There is a subdirectory for each instance. Each instance directory has the name of the related instance. o The instance name (instance ID) of the ABAP primary application server instance is DVEBMGS<Instance_Number>, and the instance name of an ABAP additional application server instance is D<Instance_Number>. In a high-availability system, there is also an ABAP central services instance called ASCS<Instance_Number> and an enqueue replication server instance called ERS<Instance_Number> Example The file system structure might look as follows: On a primary application server instance with SAP system ID C11 and instance name DVEBMGS00, the ABAP additional application server instance has the instance name D01. End of the example. o The instance name (instance ID) of the ABAP+Java primary application server instance is DVEBMGS<Instance_Number>, the instance name of the Java central services instance is SCS<Instance_Number>, and the instance name of an ABAP+Java additional application server instance is D<Instance_Number>. In a high-availability system, there is also an ABAP central services instance called ASCS<Instance_Number> and an enqueue replication server instance called ERS<Instance_Number>

Directory Example

Description

The file system structure might look as follows: On a primary application server instance with SAP system ID C11 and instance name DVEBMGS00, the Java EE Engine is installed in /usr/sap/C11/DVEBMGS00/j2ee. On an additional application server instance with instance name D01, the Java EE Engine is installed in/usr/sap/C11/D01/j2ee. End of the example. o The instance name (instance ID) of the Java primary application server instance is J<Instance_Number>, the instance name of a Java additional application server instance is J<Instance_Number>, and the instance name of the Java central services instance is SCS<Instance_Number>. In a high-availability system, there is also an enqueue replication server instance called ERS<Instance_Number> Example The file system structure might look as follows: On a primary application server instance with SAP system ID C11 and instance name J00, the Java EE Engine is installed in /usr/sap/C11/J00/j2ee. On a additional application server instance with instance name J01, the Java EE Engine is installed in /usr/sap/C11/J01/j2ee. End of the example. The directory /usr/sap/<SAPSID>/SYS contains soft links to appropriate directories in /<sapmnt>/<SAPSID>/ for storing data used by several instances. SYS is logically shared and available on each host of the SAP

Directory

Description system. Its subdirectories contain symbolic links to the corresponding subdirectories of /<sapmnt>/<SAPSID> on the SAP global host, as shown in the figures above. Whenever a local instance is started, the sapcpe program checks the executables against those in the logically shared directories and, if necessary, replicates them to the local instance. For more information about sapcpe, see Program sapcpe. Executables located in/usr/sap/<SAPSID>/SYS/exe/run are replicated by sapcpe to the exe subdirectory of the instance directories.

Global transport directory for all SAP systems

The global transport directory is used by the Change and Transport System (CTS). The CTS helps you to organize development projects in the ABAP Workbench and in Customizing, and then transport the changes between the SAP systems in your system landscape. For more information, see Change and Transport System.

/usr/sap/trans

Download file from SAP unix system to your desktop using transaction SXDA
Step 1 - Use DX tools from within sap tranasction SXDA (data transfer work bench) Select menu option Goto->DX Tools

Step 2 - Fill in mandatory fields Put an entry into 'Object type', 'Program type', and 'Program'. The values can be anything as these fields are not used for the functionality we are going to be using, but if they are

not entered the transaction will not run. You can also enter the details of the file you want to copy here as well, this will be pulled through to the next screen or you can simply enter it on the next screen.

Step 3 - Enter file to be copied details Next click on the copy button in the application tool bar and enter the details of the file you want to copy in the source section and where you want it to be copied too in the target section. (If you entered you source file details on the previous screen they will have been brought through to this screen).

Step 4 - Copy file Now press the green tick button and your file will be transfered to you selected location. There are instances where copying a file this way will cause a CONVT_CODEPAGE ABAP Runtime Error (conversion of a text from codepage '4110' to codepage '4102'). This just means that while converting from the source file codepage to the target file codepage it was unable to convert a particular character in the file and the stanard SAP code just falls over:-(. I have not really found a solution to this other than removing the particualar character from the file. If anyone has a solution to this i would be very gratfull to here it. Also contact your Basis team as they will be able to FTP the file from the SAP system for

you.