Ansicht
Dokumentation

EHS_SRE_IMP_100 - Platform-Independent File Names

PERFORM Short Reference   ABAP Short Reference  
This documentation is copyright by SAP AG.

Application data often needs to be stored in files outside the database. These files are stored in different directories and must meet different syntax requirements for file names and paths, depending on the operating system used. For this reason, many SAP applications use platform-independent logical file names and call the FILE_GET_NAME function module when saving files, which returns the corresponding platform-specific file name, including the path, for a logical file name.

The function module, which can also be used in customer-specific applications, reads definitions stored in tables for the objects described below. These definitions and the system values read at runtime determine how the logical file names are converted.

• Operating system

• Syntax group

Name for a group of operating systems that use the same syntax for file names and paths (for example, UNIX).

• Logical file name

A mnemonic name, valid across all platforms, for a file to be saved (for example, MONTHLY_SALE).

• Physical file name

The physical file name that is assigned to a logical file name and that is also valid across all platforms. It can contain placeholders that can be replaced with actual system values at runtime (for example, sale_<MONTH>).

• Logical path

A mnemonic file name, valid across all platforms, under which files are to be saved (for example, SALE_ARCHIVE).

• Physical path

The physical path assigned to a logical path for a specific syntax group. It contains the reserved placeholder <FILENAME> for the file name and, if necessary, other placeholders that are replaced at runtime (for example, /usr/<SYSID>/sale/<FILENAME>). As a rule, physical paths are assigned to a logical path for multiple syntax groups.

• Variables

Variables can be defined and assigned any character strings as values, which can then be included in file names and paths by means of the placeholder <V=variable name>.

All definitions for the platform-independent file names are valid across all clients. For logical file names, however, you can also create client-specific definitions.

For more information about converting logical file names into platform-specific file names, see also the documentation for the FILE_GET_NAME function module.

The standard SAP system contains all definitions required for SAP applications. (For details on which application uses which logical file names, see the application-specific documentation.)

Check whether the physical paths used in these definitions are consistent with the structure of your file system. If necessary, adjust the paths to meet your requirements. Note that although you can change the conversion of logical file names used by SAP applications, you cannot change the logical file names themselves.

You only need to make new entries if you call the FILE_GET_NAME function module in your own applications and require new file names and paths as a result. You can also choose any logical file names in this case.

• You can use transaction FILE to maintain the definitions of the logical file names and paths that are valid for all clients.

• You can use transaction SF01 to maintain the logical file names also for specific clients if necessary.

• You can use transaction SF07 to start a report that generates an overview of the logical file names and paths defined.

BAL_S_LOG - Application Log: Log header data   PERFORM Short Reference  
This documentation is copyright by SAP AG.

Length: 4109 Date: 20240523 Time: 185304     sap01-206 ( 76 ms )