Ansicht
Dokumentation

SIMG_CFMENUORFCANSY - Define a logical filename

General Data in Customer Master   rdisp/max_wprun_time - Maximum work process run time  
This documentation is copyright by SAP AG.

Logical file names must be defined for "periodic extract" procedures if the individual financial statement data is imported via UNIX systems.

Logical file names are used to detemine the physical file path in which data is stored. A logical file name is assigned to a logical file path. Depending on the individual operating system, a physical file path may be assigned to this logical file path.

In this step you make the following assignments:

1. Cross-client definition of file names and logical file paths

For this, complete the following steps:

• Define logical file paths

The definition of logical file paths is always cross-client.

• Assign physical file paths to logical file paths

You make assignments using syntax groups, to which individual operating systems are assigned. These syntax groups must already have been created.

• Define logical file names independently of the client

When defining a logical file name, you should enter the name of the logical file, a short description, the data format "ASC" and the logical path. You may also want to specify the application area. This would allow a more precise determination of the use of the file name, but has no functional significance. Please note that you should not specify a physical file name for periodic extract since this would cause the physical file path to be incorrectly determined.

For further information, see the documentation for the step Cross-client maintenance of filenames and paths in the Basis Implementation Guide.

1. Client-specific definition of file names

Before you maintain a file name for a specific client, you should first have completed the steps listed in point 1. The file name must be created for all clients before client-specific maintenance can take place.

To perform client-specific maintenance, you then have to enter the logical file name, a short description, the data format "ASC" and the logical file path, as above. You should not specify a physical file name.

See also the documentation for the step Additional client-specific filename maintenance in the Basis Implementation Guide.

You should have created syntax groups to which the operating systems which you use are assigned.

First perform the activities described in "Cross-client definition of file names and logical file paths" and then those described in "Client-specific definition of logical file names".

When defining the logical file name, do not enter a physical file name.

You can use an analysis to find out more about definitions already created in the system. To do this, run the step Run analyses in the Basis Implementation Guide.

Vendor Master (General Section)   SUBST_MERGE_LIST - merge external lists to one complete list with #if... logic for R3up  
This documentation is copyright by SAP AG.

Length: 3305 Date: 20240523 Time: 213529     sap01-206 ( 56 ms )