SAP ABAP IMG Activity SIMG_CFMENUORFF1207 (Define and Assign Logical File Name)
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_CFMENUORFF1207 Define and Assign Logical File Name  
Transaction Code S_ALR_87002633   IMG Activity: SIMG_CFMENUORFF1207 
Created on 19981222    
Customizing Attributes SIMG_CFMENUORFF1207   Define a logical filename 
Customizing Activity SIMG_CFMENUORFF1207   Define a logical filename 
Document
Document Class SIMG   Hypertext: Object Class - Class to which a document belongs.
Document Name SIMG_CFMENUORFF1207    

Periodic extracts transfer the data via a PC or UNIX. Therefore, you need to define a logical file name and assign it to the company.

Since the sender and receiver systems reside on two separate physical systems, the logical file name and its assignment must be known in both the sender and the receiver systems.

Logical file names are used to determine 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.

You have two options to disclose logical file names and their assignments in the sender system:

  • Option 1: First, you define the logical file names in the sender system (for details, see section "Activities" below). However, you maintain the assignments centrally in the Consolidation system and then transport them to the sender system.
  • Option 2: You maintain both the logical file names and their company assignments in the Consolidation system and then transport them to the sender system.

Requirements

You have created syntax groups and assigned their relevant operating systems.

Activities

Option 1:

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

    To do this, complete the following steps:

    • Define logical path names
      • The definition of logical path names is always cross-client.
    • Assign physical path names to logical path names
      • 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 to be valid in all clients
      • 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 periodic extract since this would cause the physical file path to be incorrectly determined.

      For more information, see the documentation for the step

Maintain Additional Client-Specific File Names 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 to be valid in 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 Maintain Additional Client-Specific File Names in the Basis Implementation Guide.

  2. Transport the assignments of the logical file names to companies to the sender system.

Option 2:

Transport the logical file names and their company assignments from the Consolidation system to the sender system.

Further notes

You can use an analysis to find out more about definitions already created in the system. For this you need to complete 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 1   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_CFMENUORFF1207 0 HLA0001214 A N HLA0009482  
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 0000000008 Define Cross-Client Logical File Name 
V_FILENAME V - View SM30 0000000011 Define Client-Specific Logical File Names 
History
Last changed by/on SAP  20020508 
SAP Release Created in