Show TOC

Platform-Independent File Name Allocation

When executing the external data transfer, you can enter a cross-platform, logical file name for for the input and output file.

Read the following information describing the concept of the logical file names.

Concept

Application data often has to be held in files outside the database. Such files are held in different directories, depending on the operating system used. Filenames and paths have to meet varying syntax requirements. For this reason, many R/3 applications use logical filenames that are not specific to one platform. When files are saved the system uses the FILE_GET_NAME function module to supply a filename (with path) appropriate to the platform, based on the logical filename.

This function module (which you can use in custom applications) accesses definitions, held in tables, of the objects defined below. These definitions, and system values that are read at runtime, determine the conversion of logical filenames.

Name of a group of operating systems with identical filename and path syntax (for example, UNIX).
Cross-platform descriptive name for a file to be stored (for example MONTHS_SALES).
Physical filename assigned to a logical filename. It may contain a placeholder that is replaced by a current system value at runtime (for example, sales_<MONTH>).
Cross-platform descriptive name for a path where files can be stored (for example, SALES_ARCHIVE)
Physical path assigned to a logical path for a particular syntax group. A physical path contains the reserved word <FILENAME> as a placeholder for the filename, and may contain other placeholders (for example, /usr/<SYSID>/sales/<FILENAME>). They are replaced at runtime. Generally, several physical paths are assigned to the same logical path, each one applying to a different syntax group.
You can define variables and assign any character string values to them. You can include them in filenames and paths using the (= variable name) placeholder.

The definitions concerning platform-independent filenames apply to all clients. For logical filenames, you can additionally create client-specific definitions.

There is more information about the conversion of logical filenames to platform-specific names in the FILE_GET_NAME function module documentation.

Standard settings

The standard R/3 delivery system includes definitions for all R/3 application components. (See the documentation for particular components to find out which components use which logical filenames.)

Verify that the physical paths used in these definitions are compatible with your file structure. Amend them to meet your requirements if necessary. Note that you can change how the logical filenames used by the R/3 application components are converted, but that the logical filenames themselves must be retained.

You only require new entries if you utilize the FILE_GET_NAME function module in applications of your own and need new filenames or paths. In such cases you can define any logical filenames for your own use.

Additional information