Explaining Consolidation Units

Objective

After completing this lesson, you will be able to explain the flexible derivation of consolidation units

Consolidation Units

Consolidation Units

A consolidation unit in group reporting is the smallest element in a consolidation group structure that can be used as a basis of complete consolidation. Consolidation units represent legal subsidiaries.

Consolidation Units can be created manually using the Define Consolidation Units app or can be uploaded using the Import Consolidation Master Data app.

If the Consolidation Unit is an integrated Company (S/4HANA company) their reported financial data resides in the same SAP S/4HANA system as group reporting, e. i. in table ACDOCA, you can use the Release Universal Journals task in the data monitor to copy the data to table ACDOCU of group reporting.

Note

If you create a consolidation unit as an SAP S/4HANA company you can - instead of executing the Release Universal Journal task - also use the Data Collection task in the data monitor or use the data transfer from SAP Group Reporting Data Collection for this consolidation unit.

If the Consolidation Unit is a non-integrated Company (spreadsheet company), their reported financial data resides in an external system and you have to execute the Data Collection task in the data monitor or use the data transfer from SAP S/4HANA Finance for group reporting Data Collection to store the data in table ACDOCU of group reporting.

Consolidation Units and the Local Currency as Source for Currency Translation

This figure gives an example of how to set up an integrated consolidation unit when the Preparation Ledger is active. Focus are the settings for the source currency which is needed for a currency translation into group currency.

Note

For simplification and focussing on the currency topic, company and Consolidation unit have the same technical name in the figure above.

In the on public cloud system landscape the Preparation ledger is active per default. As a consequence the Local Currency Source which represents the currency related measure (keyfigure) in table ACDOCA is set in the definition of the consolidation version and not in the definition of a consolidation unit. As a consequence all consolidation units created for this consolidation version have the same Local Currency Source. In the figure above Amount in Company Code Currency is the currency-related measure for consolidation unit TA000 and BA000.

When the consolidation unit master data is set up you have to assign the Unit of the Local Currency Source measure of your company as Local Currency in the consolidation unit master data.

In the figure above, USD was assigned as Local Currency (Unit) of consolidation unit TA000 and CHF was assigned as Local Currency (Unit) of consolidation unit BA000.

As a consequence, the combination of Local Currency in the consolidation unit master data and the Local Currency Source set in the consolidation version describe the source data for a currency translation.

Note

If no Local Currency Source is selected in the consolidation version, Amount in Functional Currency is used per default.

Consolidation Unit: Time and Version-Dependent Attributes

Time and Version Dependent Attributes – Key Points

  • Consolidation unit attributes can be used as a selection mechanism.

  • Some consolidation unit attributes are time-dependent, others are time and version-dependent. This increases flexibility.

  • Version-dependent attribute values can be shared across versions.

Flexible Derivation of Consolidation Units - Key Points

  • Derivation of consolidation units during an accounting posting is available with the preparation ledger.

  • Derivation of consolidation units means that company and consolidation unit can be a one-to-many relationship:

    • One use case for consolidation unit derivation is that a company code/company can be split into multiple consolidation units to support segment reporting.
    • In this example, the requirement is to perform segment reporting with multiple consolidation units. This is in addition to the segment dimension in group reporting.
  • The consolidation unit derived during the accounting posting is stored in ACDOCA.

How is the Consolidation Unit Information Derived During Accounting Posting?

  • If a company is assigned only to a single consolidation unit, the derivation happens automatically by a SAP-delivered substitution rule.

  • If a company is assigned to several consolidation units, customer-defined substitution rules are required.

  • Customer-defined substitution rules may incorporate criteria such as segment, profit center, functional area, or combinations of these.

The figure gives a simple example of the Consolidation Unit Derivation concept which can be influenced substitution rules.

The figure gives a simple example of how to derive a consolidation unit.

  • On the left, 1:1 relationship between company and consolidation unit: derivation of the consolidation unit works according to SAP delivered substitution rule.
  • On the right, 1:n relationship between company and consolidation unit: if one company is assigned to several consolidation units in the same fiscal year/period:
    • the SAP delivered substitution rule will not provide any result.
    • customer defined substitution rules are required to derive the consolidation unit based on some context of the accounting posting (company code, segment, profit center, etc.).

When the Data Release task is executed in SAP S/4HANA Finance for group reporting, data from one company may now end up in different consolidation units, representing certain data slices (for example segments) of the company.

Summary

  • Consolidation units represent the smallest consolidable elements (legal subsidiaries) in group structures.
  • Can be non-integrated (external data) or integrated (SAP S/4HANA company data).
  • Flexible derivation allows one-to-many relationships between companies and consolidation units.
  • Time and version-dependent attributes enable tracking changes and support segment reporting.