SAP ABAP IMG Activity SIMG_CFMENUCX01_IT26 (Subsequent Integration of Organizational Units)
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_IT26 Subsequent Integration of Organizational Units  
Transaction Code S_PL0_09000370   (empty) 
Created on 20020502    
Customizing Attributes SIMG_CFMENUCX01_IT26   Subsequent Integration of Organizational Units 
Customizing Activity SIMG_CFMENUCX01_IT26   Subsequent Integration of Organizational Units 
Document
Document Class SIMG   Hypertext: Object Class - Class to which a document belongs.
Document Name SIMG_CFMENUCX01_IT26    

Use

Consolidation units and groups that are created manually in integrated dimensions are not automatically integrated -- that is, the system does not know which operational organizational units lie behind the consolidation units or groups.

Therefore, integrated data collection is only possible once you have subsequently integrated the manually created units and groups. For this, you need to specify and save the valid operational organizational units for each manually created unit or group.

Requirements

Standard settings

Activities

  1. In the selection screen, you specify the integrated dimension, to which you want to subsequently integrate consolidation units and groups. You can select certain consolidation units and groups, and you can choose whether to also select rollup consolidation units for processing.
  2. Specify the integrated consolidation type for which you want to integrate the consolidation units and groups.
  3. If the system in which the units and groups are assigned has a logical system ID, specify that as well.
  4. If you are performing profit center consolidation, you also need to specify the controlling area.
  5. In general, the system creates a list with four sections:
    • The first two sections (consolidation units and consolidation groups) contain organizational units that have yet to be integrated.
    • The last two sections show the consolidation units and groups that are already integrated. No more processing is necessary for these organizational units.
  6. If an operational organizational unit exists in the local system, the system performs the following checks:
    • When creating the list, the system attempts to derive the names of the operational organizational units by using the the rules for ID combination with the IDs of the consolidation units and groups. The result is shown in the fields of the list next to the consolidation units and groups to be integrated, and in the status display. The latter shows whether all of the operational organizational units derived by the system already exist and whether they were uniquely identified.
    • When dealing with the integrated consolidation types "business area consolidation" and "profit center consolidation", the system can interpret the ID of each consolidation group twofold -- that is, according to the ID combination rules of each grouping category. Therefore, the system lists the results from the analysis of the consolidation group ID for both of these possibilities, even though only one of them can be applicable.
  7. Using update mode, check the IDs of the operational organizational units in the list, and make any corrections if necessary.
  8. Before saving, select the consolidation units and groups that are to be integrated. If one of the selected units shows an error, it cannot be saved and thus is also not integrated.
  9. Before saving, you can run the check function. This checks all of the entreis in the leading sections of the list. Look out for any errors in the consolidation units and groups that are to be integrated.
  10. Save the data.

Note

As an alternative, you can work step by step through all of the consolidation units and groups to be integrated, which means that you can save the data on a step by step basis. When a check is successful, the system transfers the integrated units and groups of the current session to the lower sections of the list. You can then continue processing the remaining entries without the need for rerunning the customizing step.

Example

Business Attributes
ASAP Roadmap ID 254   Transfer Data 
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_IT26 0 HLA0100204 Data Collection from R/3 Systems 
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
CXNT T - Individual transaction object CXNT  
History
Last changed by/on SAP  20020502 
SAP Release Created in 470