SAP ABAP IMG Activity SIMG_CFMENUCX01_MD4A (Collect Consolidation Group Hierarchy from File)
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_MD4A Collect Consolidation Group Hierarchy from File  
Transaction Code S_PL0_86000155   (empty) 
Created on 20040308    
Customizing Attributes SIMG_CFMENUCX01_MD4A   Collect Consolidation Group Hierarchy from File 
Customizing Activity SIMG_CFMENUCX01_MD4A   Collect Consolidation Group Hierarchy from File 
Document
Document Class SIMG   Hypertext: Object Class - Class to which a document belongs.
Document Name CFMENUCX01_MD4A    

Use

After transferring the consolidation groups and consolidation units into the SAP System using flexible uploads, you still need to set up consolidation group hierarchies. As an alternative to manually maintaining hierarchies or to transfers with flexible uploads, you can collect hierarchy information from a data file into the SAP System. Note that this interface is not a flexible upload, instead this interface requires a predefined fixed file structure.

Building a File for Uploading Consolidation Group Hierarchies

The file must use the following format in order to transfer consolidation group hierarchies into the SAP system:

  • The fields of the file must be separated by one of the following separators:
    • Semicolons (;)
    • Tabs (ASCII code 9)
  • The first row (header row) must contain the fields Dimension, Consolidation Version, Year, and Period.
  • The remaining rows (data rows) represent the hierarchies from top to bottom. Here we distinguish between a row that declares a new hierarchy and the subsequent rows that reflect the entries in that hierarchy. A row that declares a new (partial) hierarchy must contain the fields Hierarchy and Top Consolidation Group. The rows for hierarchy entries must contain the following fields in the order listed here:
    • Consolidation group
    • Consolidation group or unit
    • Year of first consolidation
    • Period of first consolidation
    • First consolidation at end of period
    • Organizational change at first consolidation (indicator) - see remark 1
    • Organizational change at first consolidation - see remark 1
    • Year of intention of sale - see remark 3
    • Period of intention of sale - see remark 3
    • Year of discontinued operations - see remark 3
    • Period of discontinued operations - see remark 3
    • Year of divestiture accounting
    • Period of divestiture accounting
    • Divestiture accounting at beginning of period
    • Organizational change at divestiture accounting (indicator) - see remark 1
    • Divestiture accounting due to merger - see remark 2
    • Parent indicator

      Remark 1: The file may contain the fields for an organizational change only if the "Organizational Change" function is activated in system utilization for consolidation of investments.

      Remark 2: The file may contain the "Divestiture Accounting Due to Merger" field only if the "Merger Activities" function is activated in system utilization for consolidation of investments.

      Remark 3: The file may contain the "Year of Intention of Sale", "Period of Intention of Sale", "Year of Discontinued Operations", and "Period of Discontinued Operations" fields only if the "Assets Held for Sale" function is activated in the dimension being used.

      The rows must be arranged in the same way as they would appear in the fully expanded hierarchy display of manual creation. Hence, each group is always exploded in the subsequent rows down to the units before the next group is listed. A new hierarchy can be started only once the preceding hierarchy is complete.

      A hierarchy is recognized as such only if there is no consolidation group in the SAP System that has the same name.

  • Blank rows are ignored, but also permitted.
  • All hierarchies, consolidation groups and units that occur in the file must already exist in the system. However, it is not required that the top consolidation group already be assigned to the hierarchies being loaded. This can be done by the upload itself.
  • The date of first consolidation is optional. If this field is blank, the corresponding year and period values are taken from the header row.
  • Indicator-like fields in the data record can be set to ' ' (space character) or 'X'. The parent indicator is optional.

Example of the Structure of a Text File

Abbreviations used:

Hn: Hierarchy

CGn: Consolidation group

Cnnnn: Consolidation unit

01;100;1999;012

H1;CG1

CG1;C9000;2000;003; ;X;12345;9999;999; ;X;X
CG1;CG2; 2000;003; ; ; ;9999;999; ; ;
CG2;C1000;2000;003; ; ; ;9999;999; ;X;
CG2;C2000;2000;003; ; ; ;2002;006; ; ;
CG2;C2200;2000;006; ; ; ;2002;009; ; ;

Requirements

You have created the consolidation units and consolidation groups in the SAP System.

Standard settings

Activities

  1. Create a file that contains the hierarchy information according to the structure mentioned earlier.
  2. Choose Collect Consolidation Group Hierarchies.

    The file information can be written only if it is fully consistent. If errors are found in update mode, the system automatically switches into test mode.

    The system only uploads complete hierarchy information for a given combination of dimension, version, year, and period. The upload replaces any hierarchy data that already exists in the SAP System. However, the upload does not affect hierarchy data that belongs to time periods that precede the date specified in the header row.

Example

Business Attributes
ASAP Roadmap ID 152   Design data acquisition 
Mandatory / Optional 2   Optional activity 
Critical / Non-Critical 2   Non-critical 
Country-Dependency A   Valid for all countries 
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
CX1P T - Individual transaction object CX1C3  
History
Last changed by/on SAP  20040308 
SAP Release Created in 500