SAP ABAP IMG Activity SIMG_CFMENUCX01_MD43 (Define a Logical File Name)
Hierarchy
☛ SAP_FIN (Software Component) SAP_FIN
   ⤷ EC-CS (Application Component) Consolidation
     ⤷ FC00 (Package) Cons: General consolidation (cannot be assign.to FC01-FC09)
IMG Activity
ID SIMG_CFMENUCX01_MD43 Define a Logical File Name  
Transaction Code S_ALR_87003076   IMG Activity: SIMG_CFMENUCX01_MD43 
Created on 19981222    
Customizing Attributes SIMG_CFMENUCX01_MD43   Define a logical file name 
Customizing Activity SIMG_CFMENUCX01_MD43   Define a Logical File Name 
Document
Document Class SIMG   Hypertext: Object Class - Class to which a document belongs.
Document Name SIMG_CFMENUCX01_MD43    

You need to define logical file names in order to transfer data using data transfer method 'flexible upload' or 'offline data entry'.

Logical file names are used to determine the physical file path in which data is stored. Logical file names and physical file names have the following relationship: You assign a logical file path to a logical file name. Depending on the individual operating system, a physical file path can be assigned to this logical file path.

In this step you make the following assignments:

  1. Definition of logical file names and paths that are cross-client

    This involves the following steps:

    • Define logical file paths.
      • Here you define logical file paths that are 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 exist.
    • Define logical file names that are cross-client.

  • When defining a logical file name, you enter the name of the logical file, a short description, the physical file name, data format "ASC", and the logical path name. You may also want to specify the application area. This allows a more precise determination of the use of the file name, but is not an extra function in itself.
    • In general, you specify a variable for the physical file name. The variable can consist of several reserved words, which are replaced with current values during the upload. See the field documentation. Here a sampling of a few reserved words:

,<DATE>    Date reflected by SY-DATUM

,<CLIENT>    Client reflected by SY-MANDT

,<PARAM_1>    Dimension and cons unit

,<PARAM_2>    Fiscal year and period

For example, you might specify the filename "<PARAM_1><PARAM_2>.txt". When creating the upload files, you must ensure that the reserved words will produce the predefined naming conventions. For example, if you want to upload a file that represents dimension 01, cons unit A01, fiscal year 1998 and period 003, the name of the file must be "01A011998003".
If you always upload files into SAP from only one operating system, e.g. MS-DOS, you do not need to use a logical file path. Instead, when defining the logical file name, enter the entire physical file path for the physical file name, for example, "c:\temp\<PARAM_1><PARAM_2>.txt". You do not enter a logical file path. Then the system determines the physical file path via the logical file name.

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

  1. Definition of logical file names that are client-specific

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

    As with the logical file name, in client-specific maintenance you enter a short description, the physical file name, data format "ASC" and the logical path name.

    See also the documentation concerning step Additional client-dependent filename maintenance in the Basis Implementation Guide.

Requirements

Syntax groups must already exist for the applicable operating systems.

Standard settings

The logical file path ECCS_PATH and the logical file name ECCS_FILE are preset in the standard system.

Activities

First, do the activities described in "Definition of logical file names that are cross-client", including each of the sub-activities. Then, do the activities described in "Definition of logical file names that are client-specific".

Further notes

  • In the master data of consolidation units, assign a logical file name to each unit, which collects data using flexible upload or offline data entry. Also, determine if the upload file resides on the application server or the presentation server. If any of this information is not defined in master data, it must be entered each time the data transfer is executed.
  • 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.

Business Attributes
ASAP Roadmap ID 255   Create Interfaces 
Mandatory / Optional 2   Optional activity 
Critical / Non-Critical 2   Non-critical 
Country-Dependency A   Valid for all countries 
Assigned Application Components
Documentation Object Class Documentation Object Name Current line number Application Component Application Component Name
SIMG SIMG_CFMENUCX01_MD43 0 HLA0100202 Data Collection 
Maintenance Objects
Maintenance object type C   Customizing Object 
Assigned objects
Customizing Object Object Type Transaction Code Sub-object Do not Summarize Skip Subset Dialog Box Description for multiple selections
FILENAME C - View cluster FILE 00000001LR Define Cross-Client Logical File Name 
V_FILENAME V - View SM30 00000012LR Define Client-Specific Logical File Names 
History
Last changed by/on SAP  20040604 
SAP Release Created in