SAP ABAP IMG Activity SIMG_CFMENUORFCDLOG (Define a logical filename)
Hierarchy
☛ BBPCRM (Software Component) BBPCRM
   ⤷ CRM (Application Component) Customer Relationship Management
     ⤷ CRM_APPLICATION (Package) All CRM Components Without Special Structure Packages
       ⤷ FK (Package) FI-LC Consolidation
IMG Activity
ID SIMG_CFMENUORFCDLOG Define a logical filename  
Transaction Code S_ALR_87002799   IMG Activity: SIMG_CFMENUORFCDLOG 
Created on 19981222    
Customizing Attributes SIMG_CFMENUORFCDLOG   Define a logical filename 
Customizing Activity SIMG_CFMENUORFCDLOG   Define a logical filename 
Document
Document Class SIMG   Hypertext: Object Class - Class to which a document belongs.
Document Name SIMG_CFMENUORFCDLOG    

Logical file names need to be defined for importing individual financial statement data from PC or UNIX systems into the Consolidation system.

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 the import 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.

  2. 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.

Requirements

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

Activities

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.

Further notes

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 1   Mandatory 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_CFMENUORFCDLOG 0 HLA0001251 Data Entry with dBase 
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 0000000006 Define Cross-Client Logical File Name 
V_FILENAME V - View SM30 0000000007 Define Client-Specific Logical File Names 
History
Last changed by/on SAP  19981222 
SAP Release Created in