SAP ABAP IMG Activity SIMG_CFMENUORFF1206 (Determine the Scope of Consolidation)
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
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_CFMENUORFF1206 | Determine the Scope of Consolidation |
| Transaction Code | S_ALR_87002710 | IMG Activity: SIMG_CFMENUORFF1206 |
| Created on | 19981222 | |
| Customizing Attributes | SIMG_CFMENUORFF1206 | Determine the scope of consolidation |
| Customizing Activity |
Document
| Document Class | SIMG | Hypertext: Object Class - Class to which a document belongs. |
| Document Name | SIMG_CFMENUORFF1206 |
In this step you can determine the scope of consolidation and the group characteristics. The following consolidation types featuring an integration to transactional SAP applications are available depending on which SAP Consolidation component you implement at your group's headquarters:
- The R/3 FI-LC component supports the following types of consolidation:
- The R/3 EC-CS component supports the following types of consolidation:
This Implementation Guide describes the configuration for consolidation using the FI-LC component.
Activities
- Specify the group to which the companies of your SAP system will report.
- Establish the fiscal year variant to be used as the basis for the consolidated financial statements.
- Establish for which consolidation types data should be transferred.
- Establish which consolidation system is used by the data-receiver.
- Read the documentation on data transfer procedures in the following steps in order to decide which procedure you want to use.
Further notes
- Make configurations in one of the following steps (depending on which transfer procedure you choose):
- Please note the following concerning the Consolidation fiscal year (FY) variant:
- Specification of the FY variant when setting up periodic extract:
- The Consolidation FY variant is specified for information purposes only. This variant must be the same as the company code FY variant. When posting to the general ledger and in parallel to the consolidation staging ledger, the system uses the FY variant of the company code and converts the periods if the fiscal year is non-calender. When a periodic extract is created from the consolidation staging ledger and imported into the consolidation processing ledger, the system copies the periods 1:1. This is why the FY variants must agree.
- Specification of the FY variant when setting up rollup:
- The Consolidation FY variant can be different from the company code FY variant. When you save your settings, the FY variant is automatically generated in the master records of the companies involved in the update and rollup. The FY variant of the companies is therefore derived from the Consolidation FY variant which you specified.
- You can also manually change the FY variant in Company Maintenance after it has been generated. However, please note that any change to the FY variant within the current fiscal year is extremely problematic if period closing is involved.
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_CFMENUORFF1206 | 0 | HLA0001211 A N HLA0009482 |
Maintenance Objects
| Maintenance object type |
History
| Last changed by/on | SAP | 19981222 |
| SAP Release Created in |
