PUBLIC

Document Version: SAP S/4HANA 2022 (October 2022) – 2022-10-03

Group Reporting (FIN-CS)

© 2022 SAP SE or an SAP affiliate company. All rights reserved.

THE BEST RUN

Content

1 Group Reporting. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .4
1.1 Consolidation. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .5
Authorization Objects in Group Reporting. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8
1.2 Getting Started. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13
Set Global Parameters. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13
Master Data. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .13
Consolidation Settings. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 98
Currencies in Group Reporting. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .134
1.3 Period Preparation. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 140
Maintain Exchange Rates. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 141
Consistency Check of Accounting Integration. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 141
1.4 Data Preparation. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 142
Data Monitor. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 142
Copy Transaction Data. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 182
Flexible Upload of Reported Financial Data. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 183
Group Journal Entries. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 193
Data Validation. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 207
Interunit Reconciliation. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 217
Task Logs. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 218
1.5 Intercompany Matching and Reconciliation. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 221
Features. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 221
Architecture. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 222
Quick Start. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 223
Intercompany Document Matching. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 230
Intercompany Reconciliation. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 273
Intelligent Intercompany Reconciliation. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 295
Advanced Settings. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 313
Data Management in Intercompany Matching and Reconciliation. . . . . . . . . . . . . . . . . . . . . . . 376
1.6 Consolidation Process. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 381
Consolidation Monitor. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 381
Group Journal Entries. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 404
Data Validation. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .413
Consolidation of Investments (Activity-Based). . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 414
Task Logs. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 504
1.7 Analytics for Group Reporting. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 507
"Manage Global Hierarchies" in Group Reporting. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 508

Group Reporting (FIN-CS)

2 PUBLIC Content
 Reporting Logic. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 513
Group Data Analysis. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .522
Group Data Analysis - With Reporting Rules. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 531
Validation Result Analysis - Unit View. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 533
Validation Result Analysis - Group View. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 536
Rule-Based Reports. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 538
Reports Using Outdated Reporting Logic. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 540
1.8 Plan Consolidation. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 543
1.9 Restatement and Simulation. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 545
1.10 Customizing and Integration. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 552
Customizing. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 552
ICMR Elimination Method. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 553
Custom Field Extensibility . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 559
Rules for Substitution/Validation. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .562
Integration with SAP Analysis for Microsoft Office. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 578
Data Management in Group Reporting. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 578
1.11 Focus Topics. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 581
Equity Pickup. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 582
Flexible Derivation of Consolidation Units. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 597
Integration with Group Reporting Preparation Ledger. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .613

Group Reporting (FIN-CS)

Content PUBLIC 3
1 Group Reporting

Group reporting consists of topics such as consolidation process and analytical reports and supports the
computation, creation, and disclosure of consolidated reports that provide information on the performance of
a corporate group.

Integration

The figure below depicts how group reporting as part of SAP S/4HANA is integrated with SAP Group Reporting
Data Collection and SAP Analytics Cloud and is followed by an explanation:

SAP Group Reporting Data Collection

SAP Group Reporting Data Collection helps you gather financial data for your business units. The app is hosted
on the SAP Business Technology Platform and relies on data such as master data and allowed breakdowns
from group reporting within SAP S/4HANA.

With SAP Group Reporting Data Collection, you can map data, create forms, design your own reports, and use
these or the predefined reports to collect data as part of your data preparation for consolidation.

For more information, see https://help.sap.com/viewer/p/SAP_Group_Reporting_Data_Collection.

SAP Analytics Cloud

(SAC) provides deep insights into your business using reporting and data visualization, which will help you
make better decisions.

With live data connections, the integration between SAP S/4HANA Finance for group reporting and SAC
enables business analysis at group or corporate level without data replication.

In this release, the following detail and overview reports are available out of the box:

• Consolidated report book for actual data

• Periodic overview report book
• Actual and budget comparison report book

Group Reporting (FIN-CS)

4 PUBLIC Group Reporting
 • Actual, budget, and forecast comparison report book
• Predictive consolidated P&L analysis
• Group financial KPIs overview

 Note

For more information about the integration between SAP S/4HANA and SAP Analytics Cloud, see SAP
Analytics Cloud product help page.

For troubleshooting information, the configuration content predelivered by SAP, and the frequently asked
questions about Group Reporting, see SAP Note 2659672 .
For the configuration settings and test steps required after installation or upgrade, see the “Test Script”
available at SAP Best Practices Explorer (https://rapid.sap.com/bp/#/browse/scopeitems/1SG ).

1.1 Consolidation

A complete consolidation process typically starts with preparatory steps, such as setting global parameters,
checking the master data of your organizational units and financial statement (FS) items, and specifying
effective exchange rates.

After that, you can proceed with collecting data reported by consolidation units, and standardizing the data
with features available in the Data Monitor. When the data is ready for consolidation, go to the Consolidation
Monitor to perform the consolidation tasks, such as various interunit eliminations and data validation. For a list
of the tasks and their descriptions, see Data Monitor [page 142] and Consolidation Monitor [page 381].

Throughout the process, you can cross check your processed data using reconciliation reports and currency
translation analysis reports, or generate various group reports in real time.

Group Reporting (FIN-CS)

Group Reporting PUBLIC 5
The process described above is shown in detail in the following diagram:

Prerequisites

• You have set up the proper authorizations for your users according to their job responsibilities. SAP
delivers the following roles for your reference:
• SAP_BR_GL_ACCOUNTANT_GRP: General Ledger Accountant - Group Reporting
• SAP_BR_GRP_ACCOUNTANT: Group Accountant
• SAP_BR_ADMINISTRATOR_GRP: Administrator - Group Reporting
• SAP_BR_EXTERNAL_AUDITOR_GRP: External Auditor - Group Reporting
• SAP_BR_BUSINESS_ANALYST_GRP: Business Analyst - Group Reporting
In your SAP Fiori front-end server, you can copy a delivered business role to create your own role, adapt its
contained business catalogs, and assign the created role to relevant users.
In addition, you need to set the necessary permissions by authorization object in the back-end systems, for
example, restrict the filed values a role can access by using the transaction code PFCG. After that, you can
assign the adapted roles to your business users using user administrator tool, such as transaction SU01.
For more information, see User and Role Administration of ABAP Platform.

Group Reporting (FIN-CS)

6 PUBLIC Group Reporting
 • You have created consolidation units and set the Data Transfer Method to Read from Universal Journal or
Flexible Upload, depending on whether they are integrated with company codes in financial accounting
(FI). This can be done in the Consolidation Units - Create and Change [page 22] app.
• You have maintained the FS items for your consolidation charts of accounts and map them to the relevant
general ledger accounts. For more information, see Financial Statement Items [page 41].
• To use SAP S/4HANA Finance for group reporting, SAP recommends that you install the SAP Best
Practices configuration content for the solution. You will gain a configuration starting point, which you can
adapt to your needs in Customizing. Examples in this documentation are based on the SAP Best Practices
content. For more information, see https://rapid.sap.com/bp/#/browse/scopeitems/1SG and
Administration Guide.

Integration

Consolidation is integrated with different modules within SAP S/4HANA. Integration enables the following:

• Generation of the organizational units for consolidation, based on the units in the transaction system
• Collection of the reported financial data. There are two methods of collecting transaction data:
• Data can be read directly from the universal journal.
• Data that is not stored in the universal journal, for example, the transaction data of companies that use
non-SAP systems, can be uploaded flexibly.
• Drill-through to the accounting app Manage Journal Entries for the source accounting documents
• Hierarchy definition for the consolidation-specific master data by using the framework app Manage Global
Hierarchies

Features

• You can use different methods for transferring transaction data to the consolidation system. Which
methods you use depends on your consolidation scenario.
• You can post manual journal entries (documents), for example, to standardize the reported data to the
group's methods of balance sheet valuations.
• You can use validations to check the consistency of the reported, standardized, or consolidated financial
data.
• You can translate the reported financial data into the currency of the consolidation group.
• You can automatically execute the following elimination tasks:
• Interunit eliminations (elimination of payables and receivables, elimination of revenue and expense,
elimination of investment income)
• Consolidation of investments

Group Reporting (FIN-CS)

Group Reporting PUBLIC 7
1.1.1 Authorization Objects in Group Reporting

Group Reporting offers the following authorization objects:

Authorization Object Description Where it is Used

E_CS_BUNIT Consolidation unit Processing of master data consolida­

tion unit.

E_CS_CACTT Consolidation tasks Running a consolidation task; When a

user starts the task for a consolidation
group/s for which he has the authoriza­
tion, all subassigned consolidation units
are included automatically; no exclu­
sion is possible.

The authorization for subassigned con­

solidation units is not checked, when
the user starts the task with the non-ini­
tial consolidation group parameter and
authorization for this consolidation
group is granted. It is not possible to ex­
ecute the task for the consolidation unit
and exclude any of subassigned consol­
idation units.

The authorization for consolidation

units is only checked, when the consoli­
dation group parameter is initial.

E_CS_CONGR Consolidation group Processing of master data consolida­

tion group.

E_CS_DIMEN Dimension Full authorization for dimension Y1 nec­

essary.

E_CS_ITCLG Consolidated chart of accounts Processing of master data consolida­

tion chart of accounts. Read access is
required to reading transactional data.

E_CS_PERMO Monitor, opening/closing of periods When opening/closing a period, author­

ization for both, the consolidation unit
and the consolidation group is checked.
If an authorization for a consolidation
unit is missing, the period is not opened
for this consolidation unit.

E_CS_RPT Group reporting organizational units Used for analytics in group reporting.

Group Reporting (FIN-CS)

8 PUBLIC Group Reporting
 Authorization Object Description Where it is Used

E_CS_RPTNG Data reporting Reporting of consolidation data; The

rules for CG/CU are the same as for
E_CS_CACTT.

E_CS_RVERS Version Processing of master data consolida­

tion version.

G_881_GRLD Financial Accounting Processing of master data ledger.

FIN_CS_EPU Equity Pickup Authorization to run Equity Pickup.

FI_CS_MD Group Reporting master data Used in the Define Master Data for
Consolidation Fields app.

FI_CS_RULE Reporting rule assignment Used in the apps Define Reporting Rules
and Assign Reporting Rules to Versions.

FI_CS_FSM Financial statement item mapping Used in the Map FS Items with G/L
Accounts app.

FI_CS_FSMA Financial statement item mapping as­ Used in the Assign FS Item Mappings
signment app.

FI_CS_ADH Define Adhoc Items and Adhoc Sets Note that adhoc items can only be de­
fined by using an OData Service which
is not published on the API Hub. It is in­
cluded in the communication scenario
of GRDC (0241).

FI_CS_SEL Selections in Group Reporting Used in the Define Selections app.

FI_CS_RPT Reporting regarding organizational Used in analytical reports.

units

FI_CS_PLV
Posting Level Processing of posting level when using
the authorization object FI_CS_RPT in
analytics for group reporting.

FI_CS_LOG Group Reporting logs Obsolete; see SAP note 3028675 .

FI_CS_XPRA Group Reporting XPRA Used for X persistent remote applica­

tion (XPRA) in group reporting.

For more information about the authorization checks, see the system documentation for the authorization
objects. To display this documentation, run transaction PFCG, and choose More Environment
Authorization Objects Display . Expand the corresponding node and choose Information (I) for the relevant
authorization object.

Group Reporting (FIN-CS)

Group Reporting PUBLIC 9
Related Information

User and Role Administration of ABAP Platform

1.1.1.1 Authorization Object E_CS_RPT

The authorization object E_CS_RPT (Group Reporting: Organizational Units) is used to maintain user
authorizations for analytics in group reporting.

Fields

The authorization object E_CS_RPT has the following fields:

• RVERS: Consolidation Version

• CONGR ($CONGR): Consolidation Group
• BUNIT ($BUNIT): Consolidation Unit
• PRCTR ($PRCTER): Profit Center
• KOKRS ($KOKRS): Controlling Area
• SEGMENT: Segment for Segmental Reporting
• FICSDOCTY: Document Type
• RITEM: Financial Statement Item
• FICSPSTLV: Posting Level
• ACTVT: Activity

Dependencies Between Fields

This authorization object considers dependencies between fields. For example, a certain consolidation unit
may be assigned to more than one consolidation group, or a consolidation group may be relevant in more than
one consolidation version. You can maintain authorizations that give access to specific data based on these
dependencies. It’s possible to maintain multiple authorizations to leverage these dependencies in different
ways for different fields.

For example, you can create an authorization where one consolidation unit is dependent on multiple groups to
which it belongs. At the same time, you can also create another authorization for a different consolidation unit
where it is dependent on only one group to which it belongs. This is illustrated in the following example.

 Example

Group Reporting (FIN-CS)

10 PUBLIC Group Reporting
 You want a user to have access to all the data of consolidation unit Cons Unit 1. So, you maintain Cons Unit
1 for the field BUNIT ($BUNIT). However, Cons Unit 1 is assigned to the consolidation groups Cons Group
A and Cons Group B. So, you need to make sure that you maintain Cons Group A and Cons Group B for
the field CONGR ($CONGR). Alternatively, you can simply maintain * so that a user has access to all
consolidation groups, including Cons Group A and Cons Group B.

You also want this user to have access to the data of Cons Unit 2, but only as it relates to Cons Group A. In
other words, you don’t want the user to access the data of Cons Unit 2 in Cons Group B. In this case, you
create a new authorization and maintain Cons Unit 2 for the field BUNIT ($BUNIT) and specify Cons Group
A only for the field CONGR ($CONGR). This way, the user can only see the data for Cons Unit 2 that's part
of Cons Group B.

Maintaining Fields

You can maintain specific values for each field in the authorization object. This gives a user the authorization to
access specific data for a field. For more information, see ABAP Authorization Concept.

 Note

It’s recommended to maintain values for all fields. If you leave a field blank, it receives the status
Unmaintained Organization Level.

Maintaining Fields with *

You can maintain a field with the value * to give full authorization for that field. This means that a user has
access to all data of that particular field. For example, if you set * for the field CONGR ($CONGR), then a user
with that authorization can access the data for all consolidation groups, including cases where the
consolidation group is maintained as blank.

Maintaining Fields with ‘’

You can maintain a field with the value ‘’ (two apostrophes with no space in between) to indicate a field with an
empty field value. This refers to fields that are maintained as blank in the Consolidation Journal Entries (table
ACDOCU). When you maintain ‘’, the system treats these empty fields in the same way as fields that are
assigned with actual values.

 Note

For the field CONGR ($CONGR), it’s important to maintain the value ‘’ if you want to give the user access to
data which is stored without group dependency and without consolidation group derivation by the
reporting logic, such as data on posting levels Blank, 00, 10, and 20. This can be necessary even if you
additionally give the user access to specific consolidation groups.

The one exception where this isn’t necessary is if you maintain the value * for CONGR ($CONGR). This
indicates full authorization for all consolidation groups and inherently includes cases where the
consolidation group is not assigned, such as data on the posting levels Blank, 00, 10, and 20 without
consolidation group derivation by the reporting logic.

Field BUNIT ($BUNIT) and Posting Level 20

The maintenance of the field BUNIT ($BUNIT) impacts the posting level 20 (two-sided elimination entries for
consolidation unit pairs – reporting unit and partner unit). When you maintain a consolidation unit for BUNIT

Group Reporting (FIN-CS)

Group Reporting PUBLIC 11
($BUNIT), the consolidation unit is only considered as the reporting unit in posting level 20, not as the partner
unit.

 Example

For Cons Group A, there are two elimination lines on the posting level 20:

Reporting Unit Partner Unit FS Item Amount in Group Currency

Cons Unit 1 Cons Unit 2 FSI001 100

Cons Unit 2 Cons Unit 1 FSI002 -100

You create the following authorizations and assign them to a user:

CONGR ($CONGR) Cons Group A

BUNIT ($BUNIT) Cons Unit 1

In this case, the user is authorized to view data for Cons Unit 1 only, not for Cons Unit 2. Also, since the
posting level is 20, the only accessible data for Cons Unit 1 is the data where Cons Unit 1 is the reporting
unit. As a result, the user can only view the first line of the elimination entry because here Cons Unit 1 is the
reporting unit.

Reporting Unit Partner Unit FS Item Amount in Group Currency

Cons Unit 1 Cons Unit 2 FSI001 100

The second line is not visible. This is because the user is not authorized to view data of Cons Unit 2. And
even though the user is authorized to view data for Cons Unit 1, Cons Unit 1 is the partner unit in this
second line, not the reporting unit. As a result, the authorization doesn’t allow access to this data.

Activating E_CS_RPT with the Switchable Authorization Check Framework

(SACF)

To start using the authorization object E_CS_RPT, you must activate it with the Switchable Authorization Check
Framework (SACF). For a complete guide on how to do this, see SAP Note 3120976 .

Related Information

ABAP Authorization Concept

Authorization Objects in Group Reporting [page 8]

Group Reporting (FIN-CS)

12 PUBLIC Group Reporting
1.2 Getting Started

The following sections describe how you set up the system.

1.2.1 Set Global Parameters

With this app, you can specify the global parameters that will apply to all further steps of the consolidation
process.

Inputs to the following global parameter fields are required:

• Version: Versions make it possible to consolidate different sets of financial data or consolidate in different
group currencies. You can only select standard versions. Therefore, if you select a version which is a group
currency extension version or an extension version, your selection is adjusted to the corresponding
standard version. For more information, see Consolidation Versions [page 68].
• Fiscal Year/Period
• Consolidation Chart of Accounts: A systematic grouping of financial statement (FS) items that belong
together and are used on the group reporting or consolidation level.

 Note

If the old reporting logic is active, you also need to select the Consolidation Ledger. For more information,
see Consolidation Ledger [page 74].

 Note

Preset versions, consolidation chart of accounts, and consolidation ledgers exist in the system. You can
also make your own configuration settings via Customizing activities under SAP S/4HANA for Group
Reporting.

You can also enter a consolidation group or unit to perform consolidation tasks only on that group or unit.

1.2.2 Master Data

This section describes how to display and define consolidation-specific master data, such as organizational
units and financial statement (FS) items.

In group reporting, master data includes the following:

• Configuration objects, such as version, subitem, and document type

• Consolidation-specific master data objects, such as consolidation units, consolidation groups, and FS
items
• Additional consolidation master data values

Group Reporting (FIN-CS)

Group Reporting PUBLIC 13
Each object is treated differently when defining master data. This section describes how to display and define
consolidation-specific master data.

1.2.2.1 Organizational Units Master Data

The organizational units of Group Reporting include consolidation groups and consolidation units.

In the consolidation group structure, consolidation units are assigned to consolidation groups. Also,
consolidation group-specific settings for the consolidation units are maintained, such as the fiscal year and
period of first consolidation as well as consolidation method.

1.2.2.1.1 Consolidation Units

A consolidation unit is the smallest element in a consolidation group structure.

1.2.2.1.1.1 Consolidation Unit Maintenance

Learn how to maintain consolidation units using the different consolidation unit master data apps.

Depending on your system settings, you can use one or more of the following apps to enter and display master
data of consolidation units:

• Define Consolidation Units

• Consolidation Units - Create and Change
• Consolidation Units - Display

The following table gives an overview of which consolidation unit master data app must be used, can't be used,
or is recommended to be used in which situation:

Consolidation Units - Create and

Change

SAP S/4HANA system using... Define Consolidation Units Consolidation Units - Display

…the new reporting logic exclusively. The app must be used in any fiscal year. The app can't be used.

The system was set up as of the release

2020 or higher, or a migration from EC-
CS to Group Reporting took place.

...the old reporting logic exclusively. The app can't be used. The app must be used in any fiscal year.

The system that was set up before the

release 2020 and not yet migrated to
the new reporting logic.

Group Reporting (FIN-CS)

14 PUBLIC Group Reporting
 Consolidation Units - Create and
Change

SAP S/4HANA system using... Define Consolidation Units Consolidation Units - Display

...the old and new reporting logic. The app must be used for master data The app must be used for consolidation
maintenance as of the from year of the unit master data maintenance before
The system was set up before the re­ new reporting logic. the from year of new reporting logic
lease 2020 and migrated to the new re­
SAP recommends to use this app for The app can't be used for consolidation
porting logic later.
parallel maintenance of consolidation unit master data changes as of the from
unit master data changes applied by year of the new reporting logic.
the Consolidation Units - Create and
Change app before the from year of the
new reporting logic.

 Note

The following section is only relevant for systems that were migrated from the old reporting logic to the new
reporting logic.

The new reporting logic uses the new consolidation unit master data, and the old reporting logic uses old
consolidation unit master data. The old and the new master data environments don't share the master data
and are completely separate from each other. This includes consolidation unit descriptions and master data
attributes. There is no synchronization of changes taking place between the old and new consolidation unit
master data environment.

This results in a special situation when you have to apply consolidation unit master data changes in a fiscal year
where the old reporting logic is still active. For these changes to have any effect, you have to maintain them
using the Consolidation Units - Create and Change app in the old consolidation unit master data environment.
To have consistent consolidation unit master data, SAP recommends that you make these changes in the
Define Consolidation Units app in the new consolidation unit master data environment as well

Related Information

Consolidation Units - Create and Change [page 22]

Define Consolidation Units [page 15]
Consolidation Units [page 14]

1.2.2.1.1.1.1 Define Consolidation Units

With this app, you can display, change, create, or delete consolidation unit (CU) master data individually.

Group Reporting (FIN-CS)

Group Reporting PUBLIC 15
Key Features

This app provides the following key features:

• Display consolidation units

• Change consolidation units
• Create consolidation units
• Delete consolidation units

Creating and Maintaining Consolidation Units

To create a consolidation unit, choose Create and enter the name of the consolidation unit. You can also copy
an existing consolidation unit to create a new one. To do so, you choose Copy, enter the name of the
consolidation unit and select if you want to copy the time- and version-dependent data as of the current fiscal
year and period and version or for all fiscal years and periods and versions.

 Note

If you're working in a year before the From Year for Group Reporting Preparation Ledger or in a planning
version, universal journal integration for a consolidation unit with special characters in its name is not
possible. This is because the system requires a company with the same name as the consolidation unit in
this case, and special characters are not supported for the company name.

When displaying the details of a consolidation unit, you can change the settings of the selected consolidation
unit by choosing Edit. After making changes, choose Save to apply the changes.

 Note

If you want to change the hierarchy of the consolidation units, use the Manage Global Hierarchies app.

The following settings can be made for each consolidation unit:

Basic Data (not time- and version-dependent)

• Consolidation Unit Description: Maintained in the log-on language, other languages need to be maintained
in the Language-Dependent Texts section.
• Country

Time-Dependent Attributes:

• Local Currency (mandatory)

 Note

You can only change the local currency as of the first period of the year. When you change the local
currency of a consolidation unit, the system translates the old local currency values into the new local
currency during the balance carryforward. Because of this, you must assign a currency translation
method to the consolidation unit.

Group Reporting (FIN-CS)

16 PUBLIC Group Reporting
 However, be aware that changing the local currency of a consolidation unit can lead to inconsistencies
in cases where data already exists for a consolidation unit that uses the local currency that’s to be
changed.

• Company: You can only assign companies to consolidation units if the following prerequisites are met:
• You’re working in fiscal year period as of the From Year for Group Reporting Preparation Ledger.
• You’re working in a version that is not a plan version.

 Note

If you're working in a year before the From Year for Group Reporting Preparation Ledger, you can't assign the
company yourself. Instead, a company with the same ID as the corresponding consolidation unit is
assigned to the consolidation unit. If such a company doesn't exist, then no company is assigned to the
consolidation unit.

Time- and Version-Dependent Attributes:

 Note

The following attributes are time- and version-dependent for a consolidation unit. If you create, display, or
change consolidation unit attributes, you make the changes to these attributes for the selected version
(and related versions) only and as of the selected fiscal year and period onwards. Time- and version-
dependency for consolidation units works in the same way as it does for financial statement items. For
more information, see Time- and Version-Dependency [page 45].

• Consolidation Unit is Partner Unit Only: Specifies if the new consolidation unit is to be used as a partner
unit only. If you select this checkbox, all other time- and version-dependent attributes are disabled. A
consolidation unit is specified as partner unit where it is not relevant for a consolidation process and
requires only a minimal set of master data to be used, for example, as where a consolidation unit is
specified as a partner unit in transferred data or in consolidation postings.
• Currency Translation Method: Required if the local currency is different from the group currency. The
translation method determines the exchange rate used for specific financial statement (FS) items, and
how translation and rounding differences are posted.
You can choose from the following predelivered currency translation (CT) methods:
• S0902 (Translation-FC@First Period - Periodic): You can assign this method to CUs that are newly
integrated into the group starting from the first period of the fiscal year. For the FS items in the P&L
statement and the movements-related FS items in the balance sheet, S0902 translates periodic values
at the exchange rates for their respective periods.
• S0903 (Standard Translation - Periodic): It translates values for all FS items at the monthly average
exchange rate for each period.
• S0904 (Translation-FC@Incoming Unit): It translates incoming units at a specific rate (exchange rate
indicator J) maintained for incoming unit. This offers more flexibility to incoming units.
• S0905 (Standard Translation Activity-Based C/I): You assign this method if you are using the task for
automatic consolidation of investments in the consolidation monitor. The translation method uses the
No Retranslation of Existing Group Currency Value translation key for investment and equity, to fix their
group currency values to the historical rate. This means that in data collection of reported financial
data for investment and equity, you must maintain the amounts in both local and group currency.
• Y0901 (Standard Translation - YTD): Same as S0903, except that for the FS items in the P&L
statement and the movements-related FS items in the balance sheet, S0903 translates periodic values

Group Reporting (FIN-CS)

Group Reporting PUBLIC 17
 at the exchange rates for their respective periods while Y0901 translates cumulative values at the
monthly average exchange rate of the current period.
• Y0902 (S4 Accounting GC): It can be assigned to CUs that set Read from Universal Document as the
data transfer method and therefore read financial data from universal documents.
The main differences between these CT methods are the Exchange Rate Indicator (ERI) and the Translation
Key (CT Key) that are assigned to the FS item selections. ERI determines the exchange rate to be used in
the currency translation, either monthly average rate (AVG) or monthly closing rate (CLO). CT key controls
whether cumulative values are translated at the rate for current period (YTD) or periodic values are
translated at the rates for their respective periods (PER). The table below displays the detailed settings for
each method.

Descrip­ P&L, B/S Move­ Opening Balances in B/S FS Items - In­ Investments and
Method tion ments B/S* coming Units Equity in B/S*

ERI CT Key ERI CT Key ERI CT Key ERI CT Key

S0902 Transla­ AVG PER AVG PER CLO PER AVG PER
tion-
FC@First
Period -
Periodic

S0903 Standard AVG PER AVG PER AVG PER AVG PER
Transla­
tion - Peri­
odic

S0904 Transla­ AVG PER AVG PER INC2 PER AVG PER
tion-
FC@In­
coming
Unit

S0905 Standard AVG PER AVG PER AVG PER Existing group cur­
Transla­ rency values are not
tion Activ­ retranslated.
ity-Based
COI

Y0901 Standard AVG YTD AVG PER AVG PER AVG PER
Transla­
tion - YTD

Y0902 S4 Ac­ Existing group currency values are not retranslated.

counting
GC

*Since the opening balance is stored on period 000, the amount in the group currency is kept at its original
value.
When an FS item is not included in any rule, the reference exchange rate defined in the methods applies.
When the translation results in rounding differences, these differences are posted in the group currency on
the following FS item:
• 900: B/S rounding difference is posted on FS item 314800

Group Reporting (FIN-CS)

18 PUBLIC Group Reporting
 • 901: Annual net income - B/S, P&L rounding difference is posted on FS item 799000
• 902: P&L rounding difference is posted on FS item 604000

• Tax Rate: Used to automatically calculate the deferred tax in manual or automatic journal entries, if the
deferred tax calculation is enabled in the document type.
• Deviating Fiscal Year Variant: By maintaining a deviating fiscal year variant (FYV) on the consolidation unit
level, you're able use the numbers from a local close of a company code in the group close, which result
from a shifted fiscal year compared to the group close. This is allowed from a legal point of view under
certain circumstances so that an additional local close of such a company code isn’t necessary.

 Note

This scenario is only supported if the number of "normal" fiscal year periods in the deviating FYV of the
consolidation unit is that same as the number of "normal" fiscal year periods in the FYV of the
consolidation version.

This field is disabled in all consolidation versions except planning versions unless you're working in a year
before the From Year for Group Reporting Preparation Ledger. In this case or in case you're working in a
planning version, you only need to enter a deviating FYV if the FYV for the selected consolidation unit is
different from the FYV assigned to the selected version.

 Note

As the deviating FYV is time- and version-dependent, you can change the assignment of the FYV over
time. This can lead to double assignments or missing assignments when transferring transaction data
to consolidation. In this instance, you need to correct the transaction data in consolidation by using
manual posting or flexible file upload.

Example: If you have assigned an FYV value for period 001/2020, where the fiscal year periods start on
the 1st of the month, and change the FYV value in period 002/2020 to a variant, where the fiscal year
periods start on the 15th of the month, assignments between day one and 14 of period 002 are missing.

To avoid having to correct transaction data in consolidation, you can define an FYV that changes its
behavior over time and you assign only this FYV to the consolidation unit. The FYV definition
guarantees that every date is assigned to exactly one fiscal year period. Or you can assign a third FYV
for the transition period between the other two FYVs. This third FYV is defined in a way that this
transition happens without double assignments or missing assignments.

• Universal Journal Integration: Specifies how the local reported financial data is collected from CUs for
consolidation.
• The Transfer from Universal Journal method is first of all only applicable for CUs where their reported
financial data resides in the same SAP S/4HANA system as group reporting. If you're working in a year
as of the From Year for Group Reporting Preparation Ledger, then the following prerequisites must be
fulfilled before you can choose Transfer from Universal Journal:
• The selected consolidation version must have a group reporting preparation ledger assigned for
the source ledger.
• A company must be assigned to the CU.
• A company code must be assigned to this company. 
• The company code assigned to this company must have the same fiscal year variant as the
selected consolidation version. Deviating fiscal year variants are not supported by the integration
with group reporting preparation ledgers. For more information, see the in-app help for Deviating
Fiscal Year Variant.

Group Reporting (FIN-CS)

Group Reporting PUBLIC 19
 • The company code assigned to this company must have the same functional currency as the local
currency of the selected CU.
• If the optional attribute Group Currency Source has been maintained for the selected version, the
currency derived from this source field for the company code assigned to this company must be
the same as the group currency defined for the selected consolidation version. For example, if the
Group Currency of the version is set to EUR and the Group Currency Source of the version is set to
Freely Defined Currency 2, then the Freely Defined Currency 2 set for all company
codes assigned to the company, which is assigned to the consolidation unit, must be EUR.
If you're working in a year before the From Year for Group Reporting Preparation Ledger, then the
following prerequisites must be fulfilled before you can choose Transfer from Universal Journal:
• A company exists that has the same ID as the consolidation unit.
• At least one company code has to be assigned to this company.
• The selected consolidation version needs to have an accounting source ledger assigned.
• The Source for Local Currency Key Figure, if configured, provides the same currency for all relevant
company codes as the local currency of the consolidation unit.
• The Source for Group Currency Key Figure, if configured, provides the same currency for all
relevant company codes as the group currency of the consolidation version.

 Note

If any of these prerequisites for the selected CU in the selected consolidation version and fiscal
year period are not met, the Transfer from Universal Journal option is disabled and can't be chosen.
You can check which prerequisites are not fulfilled by clicking the Information icon ( ).

 Note

If you have selected Transfer from Universal Journal for a consolidation unit, you can still use
flexible file upload or data transfer from SAP Group Reporting Data Collection for this consolidation
unit.

• If you select No Integration for a certain CU, you have to use flexible file upload or data transfer from
SAP Group Reporting Data Collection. If you have specified an Upload Method, it is used during the
flexible file upload. If you haven't, you have to select an upload method when you run the flexible file
upload.

 Note

You can choose from the predelivered upload methods.

• Group Currency is Leading Currency: You can specify if the group currency should be used as the leading
currency instead of the local currency in data collection. Selecting this option has the following
implications:

 Note

The option Group Currency is Leading Currency is only available if you've selected Group Currency is
Leading in the Check Global System Settings configuration activity. Otherwise, this option is not visible.

• Flexible File Upload: When collecting data with flexible file upload, the flexible file upload always takes
the values explicitly provided by the upload file, regardless of whether those values are in local
currency or group currency. However, if there's no explicit value provided in the file, then the flexible file

Group Reporting (FIN-CS)

20 PUBLIC Group Reporting
 upload copies values from the leading currency to the not leading currency, but only if the local
currency and group currency are the same. If the option Group Currency is Leading Currency is
selected, then the group currency is the leading currency. If not, then the local currency is the leading
currency.
• Document Posting: When posting a document, the document posting always posts exactly the values
provided in the posting, regardless of whether those values are in local currency or group currency.
However, if there's no amount provided for the not leading currency, then the amount from the leading
currency is copied over, but only if the local currency and the group currency are the same. If the
option Group Currency is Leading Currency is selected, then the group currency is the leading currency.
If not, then the local currency is the leading currency.

 Note

If you're working in a year before the From Year for Group Reporting Preparation Ledger and you've
selected the Transfer from Universal Journal option for the consolidation unit, then the Source for Group
Currency Key Figure becomes mandatory when you select Group Currency is Leading Currency. If you
don’t select Group Currency is Leading Currency, the Source for Local Currency Key Figure becomes
mandatory, and data is collected in local currency.

Source for Group Currency Key Figure and Source for Local Currency Key Figure specify the key figure in
the universal journal that the system imports for the selected consolidation unit. The amounts taken
over from that key figure are then processed as group or local currency during consolidation. The
system checks if the respective source field for the consolidation unit provides the correct currency for
the local and group currency. You cannot save your selection if this is not the case. Setting the source
for group and local currency key figure for a consolidation unit is only relevant if you want to transfer
from the universal journal. For planning versions, the system always takes fields HSL (Amount in
Company Code Currency) or KSL (Amount in Global Currency) from the planning database table as
long as one of these fields has a currency that matches the local currency of the consolidation unit (for
field HSL). Therefore the two source fields are inactive where the selected consolidation version is a
plan version.

Source fields that are already defined and that are relevant for other consolidation versions that are not
plan versions but share the same consolidation unit attribute version with the plan version are not
affected.

Displaying Consolidation Units

Using the filter criteria, you can display consolidation units and their settings, such as local currency, upload
method, or currency translation method.

 Note

You have to select exactly one consolidation version and fiscal year and period. This is required to display
the time- and version-dependent consolidation unit attribute values in the table below the filter bar. Filter
values for consolidation version and fiscal year and period are taken from your global parameter settings
but can be changed at any time.

In the list, you can sort or filter the consolidation units using any of the available criteria. You can also drill down
to the details of each consolidation unit to display more information. Here you can also change the context for
the time and version and display attribute value assignments over time or across versions.

Group Reporting (FIN-CS)

Group Reporting PUBLIC 21
Deleting Consolidation Units

You can delete one or more consolidation units. You must select at least one consolidation unit to activate the
Delete button. If you delete a consolidation unit, it is deleted across all versions, not only in the selected
version.

A where-used check is run when you delete a consolidation unit. A consolidation unit can only be deleted if it is
not used. If you have selected more than one consolidation unit, the consolidation units that are not used
anywhere are deleted. If some of the selected consolidation units are still used, these consolidation units are
not deleted. If a consolidation unit is not deleted, because it is still used, you can use the where-used feature to
get information on the usage. Some usages, such as the assignment of a consolidation unit to a consolidation
group can be deleted, other usages, such as existing transaction data, can't be deleted. If you have deleted all
usages, you can delete the consolidation unit.

To check if a consolidation unit is used, select one consolidation unit and choose Check Where Used.

Information for Key Users

The SAP Fiori apps reference library has details about the content necessary for giving users access to an app
on the SAP Fiori launchpad. To see this app’s Fiori content, go to the SAP Fiori apps reference library and
search for the app. Then select the product. On the Implementation Information tab, select the correct release.
The details are in the Configuration section.

Supported Device Types

• Desktop
• Tablet
• Smartphone

1.2.2.1.1.1.2 Consolidation Units - Create and Change

You can maintain or create consolidation unit (CU) master data individually. If you want to change the hierarchy
of the consolidation units, use the Manage Global Hierarchies app.

To create a consolidation unit, choose More Consolidation Unit Create . Enter the name of the
consolidation unit and confirm.

The following settings should be made for each consolidation unit:

• Tax Rate
• Local Currency
• Translation Method: You can maintain or create consolidation unit (CU) master data individually. If you:
Required if the local currency is different from the group currency. The translation method determines the

Group Reporting (FIN-CS)

22 PUBLIC Group Reporting
 exchange rate used for specific financial statement (FS) items, and how translation and rounding
differences are posted.
You can choose from the following SAP Best Practices predelivered currency translation (CT) methods:
• S0902 (Translation-FC@First Period - Periodic): You can assign this method to CUs that are newly
integrated into the group starting from the first period of the fiscal year. For the FS items in the P&L
statement and the movements-related FS items in the balance sheet, S0902 translates periodic values
at the exchange rates for their respective periods.
• S0903 (Standard Translation - Periodic): It translates values for all FS items at the monthly average
exchange rate for each period.
• S0904 (Translation-FC@Incoming Unit): It translates incoming units at a specific rate (exchange rate
indicator J) maintained for incoming unit. This offers more flexibility to incoming units.
• S0905 (Standard Translation Activity-Based C/I): You assign this method if you are using the task for
automatic consolidation of investments in the consolidation monitor. The translation method uses the
No Retranslation of Existing Group Currency Value translation key for investment and equity, to fix their
group currency values to the historical rate. This means that in data collection of reported financial
data for investment and equity, you must maintain the amounts in both local and group currency.
• Y0901 (Standard Translation - YTD): Same as S0903, except that for the FS items in the P&L
statement and the movements-related FS items in the balance sheet, S0903 translates periodic values
at the exchange rates for their respective periods while Y0901 translates cumulative values at the
monthly average exchange rate of the current period.
• Y0902 (S4 Accounting GC): It can be assigned to CUs that set Read from Universal Document as the
data transfer method and therefore read financial data from universal documents.
The main differences between these CT methods are the Exchange Rate Indicator (ERI) and the Translation
Key (CT Key) that are assigned to the FS item selections. ERI determines the exchange rate to be used in
the currency translation, either monthly average rate (AVG) or monthly closing rate (CLO). CT key controls
whether cumulative values are translated at the rate for current period (YTD) or periodic values are
translated at the rates for their respective periods (PER). The table below displays the detailed settings for
each method.

Descrip­ P&L, B/S Move­ Opening Balances in B/S FS Items - In­ Investments and
Method tion ments B/S* coming Units Equity in B/S*

ERI CT Key ERI CT Key ERI CT Key ERI CT Key

S0902 Transla­ AVG PER AVG PER CLO PER AVG PER
tion-
FC@First
Period -
Periodic

S0903 Standard AVG PER AVG PER AVG PER AVG PER
Transla­
tion - Peri­
odic

Group Reporting (FIN-CS)

Group Reporting PUBLIC 23
 Descrip­ P&L, B/S Move­ Opening Balances in B/S FS Items - In­ Investments and
Method tion ments B/S* coming Units Equity in B/S*

S0904 Transla­ AVG PER AVG PER INC2 PER AVG PER
tion-
FC@In­
coming
Unit

S0905 Standard AVG PER AVG PER AVG PER Existing group cur­
Transla­ rency values are not
tion Activ­ retranslated.
ity-Based
COI

Y0901 Standard AVG YTD AVG PER AVG PER AVG PER
Transla­
tion - YTD

Y0902 S4 Ac­ Existing group currency values are not retranslated.

counting
GC

*Since the opening balance is stored on period 000, the amount in the group currency is kept at its original
value.
When an FS item is not included in any rule, the reference exchange rate defined in the methods will apply.
When the translation results in rounding differences, these differences are posted in the group currency on
the following FS item:
• 900: B/S rounding difference is posted on FS item 314800
• 901: Annual net income - B/S, P&L rounding difference is posted on FS item 799000
• 902: P&L rounding difference is posted on FS item 604000

• Data Transfer Method: Specifies how the local reported financial data is collected from CUs for
consolidation.
• Method Read from Universal Document is only applicable for CUs whose reported financial data resides
in the S/4HANA system. If you select this method, and if the consolidation version is not linked to a
source category and source ledger in the version settings, the effective year should also be specified
(this setting is not required if data is sourced from ACDOCP).
• If you select the Flexible Upload method for a certain CU, you can also specify the Upload Method.

 Note

You can choose from the 2 pre-delivered upload methods SRD1 and SRD2.

• In the Methods tab, you can view what validation methods have been assigned to your consolidation units.
If no validation method has been assigned for reported or standardized data yet, choose the Assign
Validation Methods button to go to the respective app.
• Source for Group Currency Key Figure : You can specify the source for group currency key figure by
choosing Goto Fiscal Year Variant Source for Group Currency Key Figure . Note that setting the
source for group currency key figure for a consolidation unit is only relevant if you want to use the data
transfer method Read from Universal Document, and you want to integrate one of the accounting key
figures into the group currency of group reporting. SAP recommends that you use the global currency key

Group Reporting (FIN-CS)

24 PUBLIC Group Reporting
 figure in accounting for all company codes to carry the group currency value that you want to integrate into
group reporting. Also note that the source for local currency key figure and source for group currency key
figure settings are only applicable to regular versions that are not marked as Version for Plan Data. For
planning versions, the system always takes fields HSL (Amount in Company Code Currency) or KSL
(Amount in Global Currency) from the planning database table as long as one of these fields has a currency
that matches the local currency of the consolidation unit (for field HSL) or the ledger group currency (for
field KSL). This means, the ledger currency setting in the Define Consolidation Ledgers configuration step
is considered.

To display a list of the consolidation units, go to More Consolidation unit Print .

More Information

• The SAP Fiori apps reference library has details about the content necessary for giving users access to an
app on the SAP Fiori launchpad. The SAP Fiori apps reference library is available here: https://
fioriappslibrary.hana.ondemand.com
To see this app’s Fiori content, search for the app. Then select SAP S/4HANA as the product. On the
Implementation Information tab, select the correct release. The details are in the Configuration section.

1.2.2.1.1.2 Consolidation Unit Selection Attributes

Consolidation unit selection attributes classify consolidation units so that they can be selected and processed
together for various activities in group reporting. Learn more about how consolidation unit selection attributes
work, how to assign them to consolidation units, and how to use them.

Overview

A consolidation unit selection attribute is a classification you use to classify consolidation units. You do this by
assigning values for the selection attribute to individual consolidation units. After assigning attribute values to
consolidation units, all consolidation units that share the same attribute value can be selected together so that
they can be treated in the same way for certain activities, such as consolidation tasks.

SAP delivers the following consolidation unit selection attributes:

• Data Collection Selection

• Partner Selection
• Posting Rule Selection
• Validation Selection

For example, you can use the Posting Rule Selection attribute to select consolidation units for use as a trigger in
reclassifications. Or you can use the Data Collection Selection attribute to select consolidation units for
package definitions in SAP Group Reporting Data Collection.

Group Reporting (FIN-CS)

Group Reporting PUBLIC 25
Creating Attribute Values

To add attribute values for the predelivered consolidation unit selection attributes, use the Define Consolidation
Unit Attribute Values configuration activity. For more information, see the help documentation for the
configuration activity.

Assigning Attributes to Consolidation Units

You can assign values for consolidation unit attributes to consolidation units by using the Define Consolidation
Units [page 15] app or alternatively by using the Import Consolidation Master Data [page 90] app. When
you’re defining a consolidation unit, you assign attribute values to the consolidation unit in the Time- and
Version-Dependent Attributes section.

Using Consolidation Unit Attributes in Selections

When defining a selection using the Define Selections [page 84] app, you can choose Consolidation Unit for
the Field. Then, under Time- and Version-Dependent Attribute, you can select the available consolidation unit
selection attributes. The value helps provide you with the relevant selection attributes to define your selection
expressions.

You can then select a selection attribute to restrict your selection to a group of consolidation units that share
the same attribute value.

After you’ve defined selections using the consolidation unit selection attributes, you can use the selections in
the settings of various activities, such as in reclassifications. The selections then identify which consolidation
units to use in these actions. For more information, see Selections [page 83].

Related Information

Import Consolidation Master Data [page 90]

Define Consolidation Units [page 15]
Define Selections [page 84]
Selections [page 83]

Group Reporting (FIN-CS)

26 PUBLIC Group Reporting
1.2.2.1.1.3 Consolidation Unit Extensibility

You can create your own consolidation unit attributes for the new reporting logic. They can then be used in
selections, totals validation rules, and analytics.

Prerequisites

You need authorizations for extensibility to create your own consolidation unit attributes.

Creating Custom Fields

To create your own consolidation unit attributes, you must first define new custom fields for consolidation unit
master data in the Custom Fields app.

There are two types of consolidation unit attributes that you can define: attributes that are time- and version-
independent and attributes that are time- and version-dependent. Depending on which of these two types you
want, you select a specific Business Context from the following options:

• For time- and version-independent attributes, select Consolidation Unit for the business context.
• For time- and version-dependent attributes, select Consolidation Unit by Time and Version for the business
context.

Enable Usage for the Import Consolidation Master Data App

To be able to display and filter your custom consolidation unit attributes on the Import Consolidation Units
screen of the Import Consolidation Master Data [page 90] app, you must first enable this usage in the UIs and
Reports tab. To do so, navigate to the UIs and Reports tab and select Enable Usage for Consolidation Master
Data.

Publish
Be sure to Publish your custom fields once you finish defining them. If you don't publish the fields, they won't
be visible anywhere for users.

Using Consolidation Unit as the Business Object

You can select Consolidation Unit as the Business Object for a custom field of type Association to Business
Object. If you do this, then the existing consolidation units in your system appear as values that can be selected
for the field.

In this way, you can use the custom field to refer to a consolidation unit in the master data of another
consolidation unit. There's also no need to update the custom field with more values as you create more
consolidation units because your new consolidation units will appear automatically in the value help once you
create them.

 Example

For example, a custom field with Consolidation Unit

Group Reporting (FIN-CS)

Group Reporting PUBLIC 27
 In this case, there may be a "root" consolidation unit that the other "associated" consolidation units refer
to. To model this relationship between a "root" consolidation unit and "associated" consolidation units, you
can create a custom field with the business object as the business object is useful when the data of a
company is divided into several consolidation units. Consolidation Unit. Then, in the master data of the
"associated" consolidation units, you can use the custom field to select the "root" consolidation unit.

The "associated" consolidation units are then all grouped together because of their reference to the "root"
consolidation unit.

Maintenance

After you’ve defined custom fields, you can maintain consolidation unit attribute value assignments for your
custom attributes with the Define Consolidation Units [page 15] app and the Import Consolidation Master Data
[page 90] app.

Define Consolidation Units

In the Define Consolidation Units [page 15] as app, you can add your custom fields to the UI on the
Consolidation Unit Details screen, which you can access by selecting an entry in the table. With these fields on
the UI, you can then assign your attribute values to consolidation units. You can add these fields with the Adapt
UI option in the user actions menu.

 Note

You must have extensibility authorizations to adapt the UI and add custom fields. All UI adjustments made
with the Adapt UI option are visible to every user of the app.

On the main screen of the Define Consolidation Units [page 15] app, you can add filters for your custom
consolidation unit attributes with Adapt Filters. Also, you can add columns to the table of consolidation units in
the table’s Settings. By doing so, you can filter for consolidation units that have certain attribute values
assigned for your custom consolidation attributes and see these attribute value assignments in the table.

Anyone can adjust the filters and columns on the main screen of the Define Consolidation Units [page 15] app
for their individual use. However, only a user with special authorizations can adjust the filters and columns and
then save the result centrally as a public view. The adjustments then appear for all users who select such a
public view.

Import Consolidation Master Data

In the Import Consolidation Master Data [page 90] app, you can maintain the assignments of your custom
consolidation unit attribute values in spreadsheets. When you download a template for consolidation units with
or without existing master data, your custom fields for the custom consolidation unit attributes appear as
columns. You can then maintain the value assignments for the custom consolidation unit attributes in these
columns for each consolidation unit.

 Note

For custom defined consolidation unit attributes, the field types Code List and Checkbox automatically have
a value help in the spreadsheet. You can pick values from the value help or directly enter them into cells.
However, if you enter values that aren’t included in the value help, you'll receive check errors later, and the
respective data records can't be imported.

Group Reporting (FIN-CS)

28 PUBLIC Group Reporting
You can add filters for your custom consolidation unit attributes on the Import Consolidation Units screen with
Adapt Filters. Also, you can add columns to the table of consolidation units in the table’s Settings. By doing this,
you can filter uploaded master data for consolidation units that have certain attribute values assigned for your
custom consolidation attributes and see these attribute value assignments in the table.

 Note

To display and filter your custom consolidation unit attributes, make sure you've already enabled the usage
of Consolidation Master Data in the UIs and Reports tab when you defined the custom field.

Anyone can adjust the filters and columns on the Import Consolidation Units screen of the Import
Consolidation Master Data [page 90] app for their individual use. However, only a user with special
authorizations can adjust the filters and columns and then save the result centrally as a public view. The
adjustments then appear for all users who select such a public view.

Use

After assigning the attribute values to consolidation units, you can use your custom consolidation unit
attributes in the following ways:

• In selections with the Define Selections [page 84] app

• In totals validation rules with the Define Validation Rules [page 99] app
• In Analytics for Group Reporting [page 507], such as in the Group Data Analysis [page 522] app

 Note

Only custom consolidation unit attributes that are time- and version-independent can be used in
analytics.

Related Information

Custom Field Extensibility [page 559]

1.2.2.1.2 Consolidation Groups

A consolidation group is a user-defined group of consolidation units created for consolidation.

In the consolidation group maintenance apps, you can do the following:

• Create a new group.

• Specify master records for a group, such as name, country/region, and validation method assignment.
• Assign consolidation units to a group and specify a consolidation unit as the parent unit for this group.
Note that a given consolidation unit can belong to different consolidation groups.

Group Reporting (FIN-CS)

Group Reporting PUBLIC 29
• For the unit/group assignment, define group-dependent attributes, such as consolidation method,
acquisition date, and divestiture date.

 Note

With the introduction of a new architecture/reporting logic, if you are working with the SAP S/4HANA 1909
release or a later release, consolidation groups should be maintained as flat lists of consolidation units by
using the Manage Group Structure - Group View [page 32] or Manage Group Structure - Unit View [page
35] app.

If working with a release earlier than 1909, you should continue using the Consolidation Group Hierarchy -
Display and Change [page 38] and Accounting Method Assignment - Display and Change [page 40] for
consolidation group maintenance, where consolidation groups can still be arranged in multiple hierarchies.

You can create an incident with the FIN-CS-COR component to activate the new reporting logic when
working with a release earlier than 1909.

1.2.2.1.2.1 Consolidation Groups - Create and Change

With this app, you can maintain or create consolidation group (CG) master data individually.

When you open the app, you can create a new consolidation group. To change a CG, choose More
Consolidation Group Change . Enter the name of the consolidation group and confirm.

Enter the name for the consolidation group you want to create and confirm.

The following settings should be made for each consolidation group:

• Description: Enter a short and medium text to describe the consolidation group.
• Consolidation Frequency
• Validation Methods: When you assign validation methods, you are redirected to the Assign Validation
Methods [page 109] app.
• If the new reporting logic is active, the fiscal year variant (FYV) is assigned in the Define Versions
transaction.
If the old reporting logic is active, you can access the menu by selecting More Go to Fiscal Year
Variant (FYV) to assign the consolidation group's fiscal year variant, which determines the fiscal year and
period based on the posting date.

 Note

You can only assign a FYV to the consolidation group in a fiscal year prior to the from year of the new
reporting logic. In fiscal years where the new reporting logic is active, the FYV is assigned to the
consolidation version and not to the consolidation group. Therefore, the navigation to the assignment
of FYV to the consolidation group is not active as of the from year of the new reporting logic.

 Note

When transferring accounting financial data, on group reporting side, the system derives the posting
period based on the accounting posting date and the period definition of the assigned FYV. Note that

Group Reporting (FIN-CS)

30 PUBLIC Group Reporting
 the special periods defined for FYVs are not considered in group reporting, that is, only the posting date
is used to derive the posting period.

• If the old reporting logic is active, you should also select a Ledger: The group currency is determined by the
currency of the ledger assigned to the group. To define a ledger, see Define Consolidation Ledgers in the
Customizing for SAP S/4HANA for Group Reporting under Master Data. When multiple group currencies
are required for consolidation groups, the corresponding ledgers must be assigned to the consolidation
groups in different versions.

To display a list of the consolidation groups, go to More Consolidation group Print .

Supported Device Types

• Desktop
• Tablet
• Smartphone

1.2.2.1.3 Consolidation Group Structure

In the consolidation group structure, consolidation units are assigned to consolidation groups. Also,
consolidation group-specific settings for the consolidation units are maintained, such as the fiscal year and
period of first consolidation as well as consolidation method.

Depending on your system settings, there’s a slightly different concept behind the consolidation group
structure. Because of this, different apps are used to maintain the consolidation group structure.

As of the From Year for New Group Reporting Logic, the group structure manager is used to maintain the
consolidation group structure as a flat list of consolidation units assigned to a consolidation group.

If you’re working in a system where the old reporting logic is active (either exclusively or before the From Year
for New Group Reporting Logic), the consolidation group structure is maintained as hierarchies of consolidation
units and consolidation groups. These may be multi-level hierarchies. They are maintained using the
Consolidation Group Hierarchy - Display and Change [page 38] app and the Accounting Method Assignment -
Display and Change [page 40] app.

1.2.2.1.3.1 Group Structure Manager

With the group structure manager, you create and maintain consolidation group structures as of the From Year
for New Group Reporting Logic.

With the group structure manager, the consolidation group structure is maintained as a flat list of consolidation
units assigned to a consolidation group. Also, consolidation group-specific settings are maintained for the
assigned consolidation units. You can define such a consolidation group structure for any consolidation group.

The group structure manager consists of two apps:

Group Reporting (FIN-CS)

Group Reporting PUBLIC 31
• Manage Group Structure - Group View [page 32]
• Manage Group Structure - Unit View [page 35]

The same actions can be done in both apps, but they have a different point of view on the consolidation group
structures. In the Manage Group Structure - Group View [page 32] app, the focus is on the consolidation
group, the list of assigned consolidation units, and the maintenance of consolidation group-specific settings of
the consolidation units. The focus of the Manage Group Structure - Unit View [page 35] app is rather on the
consolidation unit and the assignment of the consolidation unit to different consolidation groups. However, the
consolidation group-specific settings can still be maintained in the Manage Group Structure - Unit View [page
35] app.

 Note

You can only use these apps after you’ve maintained a fiscal year in your global parameters that’s the From
Year for New Group Reporting Logic or a later year.

Related Information

Manage Group Structure - Group View [page 32]

Manage Group Structure - Unit View [page 35]

1.2.2.1.3.1.1 Manage Group Structure - Group View

With this app, you manage the assignments of consolidation units to consolidation groups and make
consolidation relevant settings for these assignments, such as the period of the first consolidation, the period
of the divestiture, and the consolidation method.

Key Features

This app provides the following key features:

Display a Consolidation Group and Its Assignments

The consolidation version, consolidation group, and fiscal year/period are automatically taken from the global
parameters. If you want to use different values, you can make the changes in the filter bar. However, the
changes are only saved for the current session. If you open the app again, the filter bar values are taken from
the global parameters again. To display the assignments or the selected consolidation group, choose Go.

 Note

A consolidation unit can be assigned to more than one consolidation group in the same fiscal year/period.
However, multiple assignments of one consolidation unit to the same consolidation group in a specific fiscal
period is not possible.

Group Reporting (FIN-CS)

32 PUBLIC Group Reporting
You can add or delete filters to and from the filter bar. Editing status, consolidation version, consolidation
group, and fiscal year/period are visible in the filter bar by default. The filter changes are not saved
automatically. When you open the app in a new session, the default filters are displayed. If you want to keep the
changed filter options, you have to save the layout as a new view. To do so, choose the dropdown list for your
views and choose Save or Save As.

You have the following options to save your view:

• Set as Default
If you set a view as the default view, the app opens with the filter bars, filter values, list report, and settings
you defined for the view. Filter values are no longer taken from the global parameters.
• Public
If you set a view as public, other users can use, change, and delete the view.
• Apply Automatically
If you choose Apply Automatically, the list report is updated automatically after choosing the view, so you
do not have to choose Go.

Assign a Consolidation Unit

Prerequisite: If you want to assign a consolidation unit to a consolidation group, you must enter a fiscal year
and period, because this entry is used as the start of the assignment. If you display the assignments without
entering a fiscal year and period, the entire history of the consolidation group is displayed and multiple entries
for one consolidation unit including past and future assignments can show up. In this case, you can't assign a
consolidation unit.

1. Choose Assign and select at least one consolidation unit. If you select more than one consolidation unit,
the information you enter in these steps is valid for each of the consolidation units you selected.
2. Choose Next and adjust the period and year for the first consolidation and, if required, for the divestiture,
and choose a consolidation method.
The start of the assignment uses the fiscal year/period from the filter bar. You can't change the start of the
assignment. The period and year of the first consolidation uses the start of the assignment as a default
value but you can change that value. It must be the same as or later than the start of the assignment and
earlier than the divestiture. The period of the divestiture is set to 999/9999 by default. You can change it to
any period later than the first consolidation. If necessary, the changes you make to the divestiture
automatically change the year for the end of the assignment.
The default value for the first consolidation is set to the beginning of the period. If you want the first
consolidation at the end of the period, select First Consolidation at End of Period.
The default value for the divestiture is set to the end of the period. If you want to divest at the beginning of
the period, select Divestiture at Beginning of Period.
If you set the Divestiture due to Merger checkbox, this causes the special logic for merger activities in
preparation for consolidation group changes and consolidation of investments. You can only select this
checkbox, if you have activated the merger feature. For more information, see Merger [page 489].
Select a consolidation method and choose Assign. You can choose between the following consolidation
methods:
• Parent (Direct Share) (00)
• Parent (Group Share) (01)
• Purchase Method (Direct Share) (10)
• Purchase Method (Group Share) (11)
• Equity Method (Direct Share) (20)
• Equity Method (Group Share) (21)
If you choose Parent, data is automatically consolidated using the accounting technique purchase method.

Group Reporting (FIN-CS)

Group Reporting PUBLIC 33
  Note

If you choose Assign, other existing assignments that conflict with this assignment are deleted. A
conflict can exist between assignments if, for example, the dates overlap. If an assignment is locked,
you receive an error message and you cannot make the assignment.

Delete Assignments
Select at least one assignment and choose Remove.

 Note

There is no consistency check with transactional data. If you remove a consolidation unit that has
transactional data, the status can be inconsistent. If you, for example, run the Preparations for
Consolidation Group Changes task and respective documents are generated, these documents might
become inconsistent or obsolete when you remove the assignment. However, they are not deleted with the
removal of an assignment.

Edit Assignment
If you select an assignment, you can display its data. To change data, choose Edit. To save the changes and
overwrite previous entries, choose Save. If you edit an assignment without saving, the changes are
automatically saved as a draft version.

Other users only see the active assignment and not the draft. However, they can see if an assignment is locked
and who has locked it. Once a lock is removed, other users see that there are unsaved changes. You can only
overwrite a draft version that was created by other users, if the assignment is not locked anymore.

 Note

The data saved as draft is not considered for consolidation. To display only the active version of the
assignments instead of the draft version, choose Show Active Items Only.

The start of the assignment is read only and cannot be changed. The start of the assignment must be the same
as or earlier than the first consolidation. It can be different from the first consolidation. You can assign a
consolidation unit to a consolidation group before it is consolidated, for example, in order to prepare the data of
that consolidation unit for consolidation.

The end of the assignment is automatically derived from the divestiture. The end of the assignment must be
later than the first consolidation. It reflects the end of the fiscal year of the divestiture. The consolidation unit is
assigned to the group until the end of the fiscal year even if the consolidation unit was divested during the fiscal
year.

Open Unit View

Choose Open Unit View to change from the group view to the unit view. The unit view displays the consolidation
groups to which the consolidation unit you selected is assigned. Consolidation version, fiscal year/period, and
consolidation unit are transferred to the Manage Consolidation Group Structure - Unit View app. For more
information, see Manage Group Structure - Unit View [page 35].

 Note

This app contains Web Assistant documentation for key fields and concepts. To display the documentation
while working in the app, press F1 or click the question mark displayed in the app header.

Group Reporting (FIN-CS)

34 PUBLIC Group Reporting
Supported Device Types

• Desktop
• Tablet
• Smartphone

1.2.2.1.3.1.2 Manage Group Structure - Unit View

Use this app to manage the assignments of consolidation units to consolidation groups and make
consolidation relevant settings for these assignments, such as the period of the first consolidation, the period
of the divestiture, and the consolidation method.

 Note

With the introduction of a new architecture/reporting logic, this app can only be used with the 1909 release
or later releases. However, if you're working with a release earlier than 1909, you can activate the new
reporting logic by creating an incident with the FIN-CS-COR component. If you are working with a release
earlier than 1909 and do not activate the new reporting logic, you should use the Consolidation Group
Hierarchy - Display and Change [page 38] and Accounting Method Assignment - Display and Change
[page 40] apps instead.

Key Features

This app provides the following key features:

Display a Consolidation Unit and the Consolidation Groups It Is Assigned to.

The consolidation version, consolidation unit, and fiscal year/period are automatically taken from the global
parameters. If you want to use different values, you can make the changes in the filter bar. However, the
changes are only saved for the current session. If you open the app again, the filter bar values are taken from
the global parameters again. To display the assignments or the selected consolidation unit, choose Go.

 Note

A consolidation unit can be included in more than one consolidation group but only once in one specific
consolidation group in a specific fiscal period.

You can add or delete filters to and from the filter bar. Editing status, consolidation version, consolidation unit,
and fiscal year/period are visible in the filter bar by default. The filter changes are not saved automatically.
When you open the app in a new session, the default filters are displayed. If you want to keep the changed filter
options, you have to save the view as a new view. To do so, choose the dropdown list of your views and choose
Save or Save As.

You have the following options to save your view:

• Set as Default

Group Reporting (FIN-CS)

Group Reporting PUBLIC 35
 If you set a view as the default view, the app opens with the filter bars, filter values, list report, and settings
you defined for the view. Filter values are no longer taken from the global parameters.
• Public
If you set a view as public, other users can use, change, and delete the view.
• Apply Automatically
If you choose Apply Automatically, the list report is updated automatically after choosing the view, so you
do not have to choose Go.

Assign a Consolidation Group

Prerequisite: If you want to assign a consolidation group to a consolidation unit, you must enter a fiscal year
and period, because this entry is used as the start of the assignment. If you display the assignments without
entering a fiscal year and period, the entire history of the consolidation unit is displayed and multiple entries for
one consolidation unit including past and future assignments can show up. In this case, you can't assign a
consolidation group.

1. Choose Assign and select at least one consolidation group. If you select more than one consolidation
group, the information you enter is valid for each of the consolidation groups you selected.
2. Choose Next and adjust the period and year for the first consolidation and, if required, for the divestiture,
and choose a consolidation method.
The start of the assignment uses the fiscal year/period from the filter bar. You can't change the start of the
assignment. The period and year of the first consolidation uses the start of the assignment as a default
value but you can change that value. It must be the same as or later than the start of the assignment and
earlier than the divestiture. The period of the divestiture is set to 999/9999 by default. You can change it to
any period later than the first consolidation. If necessary, the changes you make to the divestiture
automatically change the year for the end of the assignment.
The default value for the first consolidation is set to the beginning of the period. If you want the first
consolidation at the end of the period, select First Consolidation at End of Period.
The default value for the divestiture is set to the end of the period. If you want to divest at the beginning of
the period, select Divestiture at Beginning of Period.
Select a consolidation method for the assignment and choose Assign. You can choose between the
following consolidation methods:
• Parent (00)
• Purchase Method (10)
• Equity Method (20)
If you choose Parent (00), data is automatically consolidated using the accounting technique purchase
method.

 Note

If you choose Assign, other existing assignments that conflict with this assignment are deleted. A
conflict can exist between assignments if, for example, the dates overlap. If an assignment is locked,
you receive an error message and you cannot make the assignment.

Open Group View

Delete Assignments.
Select at least one assignment and choose Remove.

 Note

There is no consistency check with transactional data. If you delete a consolidation unit that has
transactional data, the status can be inconsistent. If you, for example, run the Preparations for

Group Reporting (FIN-CS)

36 PUBLIC Group Reporting
 Consolidation Group Changes task and respective documents are generated, these documents might
become inconsistent or obsolete when you remove the assignment. However, they are not deleted with the
removal of an assignment.

Edit Assignment

If you select an assignment, you can display its data. To change data, choose Edit. To save the changes and
overwrite previous entries, choose Save. If you edit an assignment without saving, the changes are
automatically saved as a draft version.

Other users only see the active assignment and not the draft. However, they can see if an assignment is locked
and who has locked it. Once the lock is removed, other users see that there are unsaved changes. You can only
overwrite the draft version that was created by other users, if the assignment is not locked anymore.

 Note

The data saved as draft is not considered for consolidation. To display only the active version of the
assignments and not the draft version, choose Show Active Items Only.

The start of the assignment is read only and cannot be changed. The start of the assignment must be the same
as or earlier than the first consolidation. It can be different from the first consolidation. You can assign a
consolidation unit to a consolidation group before it is consolidated, for example, in order to prepare the data of
that consolidation unit for consolidation.

The end of the assignment is automatically derived from the divestiture. The end of the assignment must be
later than the first consolidation. The end of the assignment reflects the end of the year of the divestiture. The
company stays with the group until the end of the fiscal year even if the consolidation unit was divested during
the fiscal year.

Open Group View

Choose Open Group View to change from the unit view to the group view. The group view displays the
consolidation units that are assigned to the selected consolidation group. Consolidation version, fiscal year/
period, and consolidation group are transferred to the Manage Consolidation Group Structure - Group View app.
For more information, see Manage Group Structure - Group View [page 32].

 Note

This app contains Web Assistant documentation for key fields and concepts. To display the documentation
while working in the app, press F1 or click the question mark displayed in the app header.

1.2.2.1.3.2 Consolidation Group Hierarchy

Consolidation group hierarchies are used as the consolidation group structure in fiscal years before the From
Year for New Group Reporting Logic.

The consolidation group structure is maintained as hierarchies of consolidation units and consolidation groups.
These may be multi-level hierarchies. They are maintained using the Consolidation Group Hierarchy – Display
and Change [page 38] app and the Accounting Method Assignment – Display and Change [page 40] app.

Group Reporting (FIN-CS)

Group Reporting PUBLIC 37
  Note

You can only use these apps after you’ve maintained a fiscal year in your global parameters that’s before
the From Year for New Group Reporting Logic.

Related Information

Consolidation Group Hierarchy - Display and Change [page 38]

Accounting Method Assignment - Display and Change [page 40]

1.2.2.1.3.2.1 Consolidation Group Hierarchy - Display and

Change

With this app, you create, change, or display consolidation groups and their units within the hierarchy of
consolidation groups.

Key Features

1. Create consolidation group hierarchies by choosing Create and entering the hierarchy ID and description.

 Note

You can create multiple consolidation group hierarchies in one dimension. Furthermore, a consolidation
group can be included in more than one hierarchy. This enables you to structure consolidation groups
to meet different requirements within a single dimension.

2. Create consolidation groups in the hierarchies as follows:

1. Place the cursor on the consolidation group hierarchy or on the upper-level consolidation group in a
hierarchy, and choose Create.
2. In the dialog box, enter an ID and a description for the consolidation group you want to create.
3. Create consolidation units for each consolidation group by following the same procedure used when
creating consolidation groups.
• If you want to integrate company codes that exist in Financial Accounting (FI), you need to choose the
same ID for both the consolidation unit and the company. Then set Read from Universal Document as
the data transfer method. You can then select the Sender Local Currency in the Master data tab and
specify the Effective Year for Reading Universal Documents in the Data collection tab.
In this way, you can release the local reported data of these integrated companies by running the
Release Universal Journals task in the Data Monitor app.
• If you want to create consolidation units that are not integrated in FI, you need to set Flexible Upload as
the data transfer method.

Group Reporting (FIN-CS)

38 PUBLIC Group Reporting
 4. By double-clicking on a hierarchy, a consolidation group, or a consolidation unit, you can display or change
its master data. For details about defining master data for consolidation units, see Consolidation Units -
Create and Change [page 22].
5. You can also delete groups or units from the hierarchy by choosing Delete from Hierarchy.
6. In the Methods tab, you can view what validation methods have been assigned to your consolidation group.
If no validation method has been assigned yet, choose the Assign Validation Methods button to go to the
respective app.
7. For any selected consolidation group or unit, you can access the menu More Go to Fiscal Year
Variant to assign its fiscal year variant, which determines the fiscal year and period based on the posting
date.

 Note

When transferring accounting financial data, on group reporting side, the system derives the posting
period based on the accounting posting date and the period definition of the assigned FYV. Note that
the special periods defined for FYVs are not considered in group reporting, that is, only the posting date
is used to derive the posting period.

8. In the Assignments tab, the consolidation groups and consolidation units of the selected consolidation
group are displayed. You can maintain the first and last consolidation data (period/year). You can also
specify the parent unit for the group.

 Note

When a consolidation unit is divested during the year, you need to maintain the period and year of the
divestiture in the Assignments tab. However, the divested unit must remain in the consolidation group
hierarchy until the last period of the year. In the first period of the year following the divestiture, you can
remove the divested unit from the hierarchy.

To display the where-used list, choose Go-to Where-used list .

More Information

• The SAP Fiori apps reference library has details about the content necessary for giving users access to an
app on the SAP Fiori launchpad. The SAP Fiori apps reference library is available here: https://
fioriappslibrary.hana.ondemand.com
To see this app’s Fiori content, search for the app. Then select SAP S/4HANA as the product. On the
Implementation Information tab, select the correct release. The details are in the Configuration section.

Supported Device Types

• Desktop

Group Reporting (FIN-CS)

Group Reporting PUBLIC 39
1.2.2.1.3.2.2 Accounting Method Assignment - Display and
Change

You use this app to assign the accounting methods to the consolidation units.

You must assign a method, either Purchase method or Equity method, to all consolidation units, so that their
financial statements and the relevant eliminations and adjustments can be integrated into that of the group's.

 Note

The equity method provides the following limitations:

• The system does not integrate reported data for the consolidation unit in the Integrate Data into
Consolidation Group task in the Consolidation Monitor.
• The automatic reclassification rules cannot process this accounting method yet. You can post the
adjustments using the manual posting function available in the Post Group Journal Entries [page 193]
app.

Features

Various options are available for viewing the assignments and the methods:

• Dimension view
• Consolidation group view (CG view)
• Consolidation unit view (CU view)

 Note

Consolidation unit either inherits one method that dominates its consolidation group or gets a method
directly assigned to it. The latter assignment takes precedence.

Basic Procedure for Method Assignment

1. Check which methods are already assigned to the consolidation units (CUs).
2. Choose the Dimension View.
3. If possible, use the inheritance feature for making your method assignments:
1. Position the cursor on the consolidation group and choose More Edit Choose or double-click
the mouse button.
2. In the dialog box, enter the method and select the type of inheritance. The effective year and the
effective period are inherited from the Global Parameters.
4. For those consolidation units that should not inherit a method that dominates its consolidation group,
assign the deviating method directly: position the cursor on the consolidation unit and perform the
remaining actions, as described in step 3.
5. If you want to change a CU's method, replace the method assignment for the prior period with the new
method.
In the hierarchical view of the method assignments, besides the current method, you can also look at the
method assigned to the prior period.
You can use the CG View and CU View to correct your method assignments, when needed.

Group Reporting (FIN-CS)

40 PUBLIC Group Reporting
More Information

• The SAP Fiori apps reference library has details about the content necessary for giving users access to an
app on the SAP Fiori launchpad. The SAP Fiori apps reference library is available here: https://
fioriappslibrary.hana.ondemand.com
To see this app’s Fiori content, search for the app. Then select SAP S/4HANA as the product. On the
Implementation Information tab, select the correct release. The details are in the Configuration section.

Supported Device Types

• Desktop

1.2.2.2 Consolidation Chart of Accounts

A consolidation chart of accounts (COA) is a systematic grouping of financial statement (FS) items that belong
together and are used for group reporting.

Use
In local accounting, consolidation units use a local COA with corresponding levels of detail. In group reporting,
to enable the preparation of consolidated financial statements from the financial data of the consolidation
units, however, the operational data must first be aggregated uniformly across the group. Therefore, at least
one consolidation COA must be defined.

The predefined consolidation COA is Y1.

Settings
To set up your own consolidation COA other than Y1, go to Customizing for SAP S/4HANA for Group Reporting
under Master Data Define Consolidation Chart of Accounts . After that, there are multiple follow-up steps
you need to complete in your system. These steps are described in the how-to guide “Creating New
Consolidation COA or Replacing FS Items”, which is attached to the SAP Note 2659672 (SAP customer
access only).

The FS items and the breakdown categories are dependent on the consolidation COA. In the consolidation
COA, you arrange the FS items into FS item hierarchies, for example, an FS item hierarchy for balance sheet
items and a hierarchy for profit & loss statement items. For more information, see Define Hierarchies [page
51].

1.2.2.3 Financial Statement Items

Financial statement (FS) item represents the fundamental account assignment in the consolidation system. It
forms the basis for consolidation data collection, posting, and reporting along the consolidation process.

Group Reporting (FIN-CS)

Group Reporting PUBLIC 41
FS items are dependent on the consolidation chart of accounts. They are not only used for accounting
purposes on balance sheets, P&L statements, or statements of retained earnings, but can also be used for
maintaining metrics and key figures.

SAP pre-delivers a set of FS items. You can find their usage, attributes, and posting examples on the SAP Best
Practices help page Financial Statement Items.

You can change the pre-delivered FS items or their hierarchies, or create your own ones by using the Define FS
Items [page 49] and the Manage Global Hierarchies apps. In addition, more apps are available for mapping FS
items with general ledger accounts, viewing attributes of all FS items, or deleting FS items. These apps are
described in this section.

1.2.2.3.1 FS Item Type

Financial statement (FS) item type is an attribute that indicates the nature of FS items. The following item
types are available:

• INC: Income items in P&L statements

• EXP: Expense items in P&L statements
• AST: Asset items in balance sheets
• LEQ: Liabilities and equity items in balance sheets
• STAT: Statistical items that can be used to record financial and non-financial data. This data is not directly
linked into P&L statements or balance sheets, such as headcount information.
• REPT: Reporting items that are used in reporting. Reporting item is a reporting characteristic that allows
you to define a report row or column structure. Reporting rules have to be defined to determine how the
reporting items are calculated in each relevant report row or column. These rules are applied at report run-
time. For more information about how to define reporting rules, see the Define Reporting Rules [page 118]
app help.

The item type settings for FS items are used by some of the system functions, such as balance carryforward
and annual net income calculation. It is a mandatory setting when you define FS items.

1.2.2.3.2 FS Item Selection and Target Attributes

A financial statement (FS) item selection attribute is a classification you assign to FS items so that all FS items
that share the same attribute value can be selected in order to be treated in the same way, for example, in
consolidation tasks.

FS item target attributes are designed to derive an FS item based on another FS item for specific purposes.
This may be used, for example, for automatic postings in reclassification rules. You assign target attributes for
FS items and then specify the target attributes in the reclassification rules. For example, for the FS item
411100-Sale, you select the FS item 412100-Inventory variation for the elimination target attribute.

If you use target attributes, you don't have to assign the FS items in the rule itself. Instead the system identifies
FS items based on the master data.

Group Reporting (FIN-CS)

42 PUBLIC Group Reporting
SAP delivers the following FS item attributes and respective attribute values:

Selection attributes:

• FS Item Role: An FS item attribute that is used in the configuration for automatic posting to determine the
FS item on which a posting must be recorded. The FS item role can be used, for example, to configure the
calculation of annual net income, deferred tax, retained earnings, currency translation (CT) difference, and
rounding difference. Note that an FS item can only have one role, and a role can only be assigned to one FS
item in a certain fiscal year and period and consolidation version.
• Data Collection: An FS item attribute that selects similar FS items in the data entry reports to make the
reports as dynamic as possible.
• Currency Translation: FS items that are assigned with the same attribute value are treated in the same way
in CT, that is, they share the same CT settings in a specific translation method, for example, whether
translated by the monthly average rate or the monthly closing rate.
• Elimination: FS items that are assigned with the same elimination value are treated in the same way in a
reclassification rule for interunit elimination.
• Cash Flow: Selects FS items in the reporting rules that are dedicated to the consolidated statement of cash
flows.
• Scope: The scope can be used, for example, for validations or in group reporting data collection input
reports. You specify the scope of data entry based on the FS item dimension, meaning specify which FS
items are relevant for a certain reporting cycle. You can, for example, differentiate whether FS items are
relevant for actuals and planning data only, or for both.
• Other Selection Attribute: You can set this attribute for your own purpose, for example, in validations or
reports.

 Note

You have to create values for this selection attribute before you can use them in the FS item
maintenance.

Target attributes:

• Elimination Target: You use the elimination target to specify the offsetting FS item for eliminations in
reclassification rules.
• Non-Controlling Interest (NCI) Target: You use the NCI target to specify the FS items for NCI postings in
consolidation of investments in reclassification rules.
• Planning Target: If your consolidation chart of accounts includes FS items that are specific to planning
versions and that correspond to aggregations of FS items reported in actuals data, use the planning target
attribute to define the mapping between actuals FS items, and the corresponding planning FS items
(many-to-one relationship). This target attribute can be imported into external tools, such as SAP
Analytics Cloud (SAC), and can then be used to initialize the planning data with aggregated actuals data.

 Note

FS item selection attribute and target attribute value assignments are time- and version-dependent. When
you work with FS items, be aware that the attribute value assignments for these attributes are valid for the
selected version (and related versions) only and as-of the selected fiscal year and period.

Group Reporting (FIN-CS)

Group Reporting PUBLIC 43
Procedure

To add more attribute values for the pre-delivered FS item selection attributes, go to Customizing for SAP S/
4HANA for Group Reporting under Consolidation FS Items Configuration Define FS Item Attribute Values .
After selecting an attribute, you can add or change the attribute values, including value names and
descriptions.

Usage

Assign Attributes to FS Items

You can assign the attribute values to FS items by using the Define FS items app.

 Example

For the attribute Currency Translation, you assign the attribute value CT-BS-CLO (B/S items - closing rate)
to relevant FS items that will be processed in the same way in currency translation.

Use FS Item Attributes in Selections

When defining a selection using the Define Selections [page 84] app, you can choose Financial Statement
Item Additional Attribute and then select an attribute to restrict your selection to a range of FS items that
share the same attribute value.

 Example

In the selection S-CT-BS-CLO-OPE (B/S FS items - opening balances), you use the currency translation
attribute value CT-BS-CLO to include only these relevant FS items.

Later on, selections can be used in settings for reclassification methods or currency translation methods, for
example. In this way, FS item attributes influence the system behavior for currency translation or eliminations.
For more information, see Selections [page 83].

Use FS Item Role Attribute in Configuration

When making configuration using Customizing activities, for example, defining reclassification methods or CT
methods, you can use FS item attributes in the following settings:

• Source Item Role and Destination Item Role in source and destination account assignment of
reclassification methods.
• Debit - Item Role and Credit - Item Role in translation difference settings of CT methods.

The following table lists the FS item roles and where they are used:

Attribute Value Name Value Long Description Used in the Configuration of:

S-ANI-BS Annual Net Income – B/S Specify Selected FS items for Auto­
matic Posting

Group Reporting (FIN-CS)

44 PUBLIC Group Reporting
 S-ANI-PL Annual Net Income – P&L Specify Selected FS items for Auto­
matic Posting Define Currency Transla­
tion Methods

S-DEF-TAX-AST Deferred tax – Assets Specify Selected FS items for Auto­

matic Posting

S-DEF-TAX-LIA Deferred tax – Liabilities Specify Selected FS items for Auto­

matic Posting

S-DEF-TAX-PL Deferred tax – Expense Specify Selected FS items for Auto­

matic Posting

S-CT-DIFF C/T difference Define Currency Translation Methods

S-CT-ROUND-PL C/T rounding difference – P&L Define Currency Translation Methods

S-NET-INC-CLEARING Clearing C/I Define Reclassification Methods

S-RETAINED-EARNING Retained earning Define Reclassification Methods

S-NCI-RETAINED-EARN NCI - Retained earning Define Reclassification Methods

S-NCI-NET-INC-BS NCI - net income BS Define Reclassification Methods

S-NCI-NET-INC-PL NCI - net income P&L Define Reclassification Methods

S-INVEST-CLEAR-OWN Investments clearing - Owner Define Reclassification Methods

S-INVEST-CLEAR-HELD Investments clearing - Held Define Reclassification Methods

S-PERCENTAGE-GS Percentage (%)-Group Share Define Reclassification Methods

Note that some FS item roles are also used by Consolidation of Investments (Activity-Based) and Preparation
for Consolidation Group Changes.

Related Information

Consolidation of Investments (Activity-Based) [page 414]

Preparation for Consolidation Group Changes [page 397]

1.2.2.3.3 Time- and Version-Dependency

Some attribute value assignments for financial statement (FS) items are time- and version-dependent. These
are the value assignments for all selection and target attributes. For more information, see FS Item Selection
and Target Attributes [page 42].

When you select a consolidation version, you see value assignments only for the selected version. If you make
changes to the attribute value assignments for an FS item that are version-dependent, the changes are valid for
the selected consolidation version. The version-dependent attribute value assignments for FS items aren't
directly stored in a consolidation version but in an FS item attributes special version, which may also be
consumed by other consolidation versions. For this reason, changes can also affect other consolidation
versions.

Group Reporting (FIN-CS)

Group Reporting PUBLIC 45
For the time-dependency, the system uses an as-of logic. This means that if you make changes in a certain
fiscal year/period, for example, 003/2022, the changes are effective starting from this period onwards.

If for future periods, other entries have been maintained, for example, for 005/2022, the changes you make in
period/fiscal year 003/2020 are valid until 005/2022 (see example 1).

If you make changes in 003/2020 to an existing assignment that is valid from 000/0000 until 999/9999, the
first assignment is valid from 000/0000 until 002/2020 and the second assignment is valid from 003/2020
until 999/9999 (see example 2).

If you change the validity period for an existing assignment, for example, starting in 003/2020 instead of
005/2022, the assignment is then valid from 003/2020 until 999/9999 (see example 3).

 Example

Group Reporting (FIN-CS)

46 PUBLIC Group Reporting
For the consolidation functions displayed in the table below, FS items are determined according to their time-
and version-dependent value assignments. The consolidation version and the fiscal year and period are used to
determine the FS items according to their assigned attribute values.

1.2.2.3.4 Breakdown Categories

Breakdown categories classify subassignments that are required for Financial Statement (FS) items to perform
consolidation tasks.

With the Define FS Items app, you can assign the breakdown categories to the relevant FS items. In addition to
the predefined breakdown categories, you can define your own ones by using the Customizing SAP S/4HANA
for Group Reporting under Master Data Define Breakdown Categories .

The following breakdown category fields are supported:

• Partner Unit
• Subitem Category
• Subitem
• Transaction Currency
• Unit of Measure

For each FS item, the breakdown category determines which subassignments must be entered.

 Example

If an FS item is assigned with breakdown category 1A10, the data records of this FS item:

• The value of the partner unit field is optional. You can leave it blank or use specific consolidation unit ID.
• The value of the subitem category field is required and fixed to 1 (Transaction Type).

Group Reporting (FIN-CS)

Group Reporting PUBLIC 47
 • The value of the subitem field is required. If you leave it blank, the system uses the default value from
the specified selection S-BC-TT-01.

The breakdown category 1A10, for example, has the following predefined settings:

Breakdown Cate­
gory Characteristic Breakdown Type Text Fixed Value Max. Selection

1A10 Partner Unit 1 Optional break­

down: Initialized
value allowed

Subitem Category 3 Required break­ 1 (Transaction

down: Entry is Type)
mandatory, de­
fault allowed

Subitem 2 Required break­ S-BC-TT-01

down: If blank, the
default value is
used.

Transaction Cur­ 0 No breakdown

rency

Unit of Measure 0 No breakdown

Breakdown type 4 is a required breakdown: the entry is mandatory, the default value is not allowed.

Fixed value: The characteristic value of the subassignment is determined by this value.

Max. Selection: Specifies the value range of the characteristics. For more information about how selections are
defined, see Define Selections [page 84].

 Note

The balance carryforward task does not consider the maximum selections, which you have specified in the
breakdown categories. Therefore, the balance carryforward task does not detect disallowed values that are
outside the allowed value ranges according to the maximum selections.

More Information

• The SAP Fiori apps reference library has details about the content necessary for giving users access to an
app on the SAP Fiori launchpad. The SAP Fiori apps reference library is available here: https://
fioriappslibrary.hana.ondemand.com
To see this app’s Fiori content, search for the app. Then select SAP S/4HANA as the product. On the
Implementation Information tab, select the correct release. The details are in the Configuration section.

Group Reporting (FIN-CS)

48 PUBLIC Group Reporting
1.2.2.3.5 Financial Statement Item Maintenance

This section describes how to display or define financial statement (FS) items and their hierarchies in the
context of your specified consolidation chart of accounts.

1.2.2.3.5.1 Define FS Items

With this app, you can display or update financial statement (FS) items and their properties based on your
specified criteria.

Key Features

 Note

FS item selection attribute and target attribute value assignments are time- and version-dependent. If you
create, display, or change FS items, be aware that you make the changes to these attribute value
assignments for the selected version (and related versions) only and for the selected fiscal year and period
onwards. For more information, see Time- and Version-Dependency [page 45].

This app provides the following key features:

Display FS Items
Using the filter criteria, you can show FS items of your selection and their properties such as consolidation
chart of accounts, item type, breakdown category, elimination attribute, currency translation attribute, and role
attribute.

In the list, you can sort or filter the FS items using any of the available criteria.

You can drill down to the detail screen of each FS item to show more information, such as:

• Breakdown Category:
• Which breakdown category fields are assigned to the FS item, for example, Partner Unit, Subitem, and
Subitem Category.
• Which fields are required for using the FS item in performing consolidation tasks, indicated by
Breakdown Type. For example, the Partner Unit field might be required for receivable and payable items
to perform the interunit elimination task.
• What the fixed values or allowed values for these fields are.
• If configured, the Maximum Selection column controls the range of allowed values. For more
information, see Selections [page 83].
• FS item name and description in all supported languages

Change FS Items
When displaying any FS item in the detail screen, you can change any property above of the FS item by
choosing Edit. After making any changes, choose Save to apply the changes.

Group Reporting (FIN-CS)

Group Reporting PUBLIC 49
  Note

Statistical FS items are created automatically by Consolidation of investments. These FS items are
necessary to record historical values needed to process future activities, such as divestiture. These FS
items are prefixed by the dollar ($) symbol. These FS Items must not be changed because any changes
that are made are overwritten by Consolidation of Investments.

Create FS Items
You can create a new FS item by choosing Create and then define its properties in the detail screen. You can
also copy an existing FS item to create a new one. To do you, choose Copy, enter the name of the FS item and
select if you want to copy the time- and version-dependent data for the current fiscal year and period and
version or for all fiscal years and periods and versions.

Note that the following fields are required:

• Financial Statement Item: FS item ID that contains up to 10 characters.

• Consolidation Chart of Accounts
• FS Item Type: An attribute that indicates the nature of FS items. See FS Item Type [page 42] for details
about each item type.

 Note

For FS items with the FS item type AST (Asset) or LEQ (Liabilities and Equity), their balances are always
carried forward to the next year because this is a business requirement. For the same reason, the
balances of FS items with the FS item type INC (Income) or EXP (Expense) are never carried forward to
the next year.

For FS items with the FS item type STAT (Statistical Item) or REPT (Reporting Item), you have the
option to carry forward their balances to the next year. To do so, select the Carry Forward Balances
checkbox. This setting is typically required for share ownership percentages and non-financial data.

To upload, download, and import FS items into the system, see Import Consolidation Master Data [page 90].

To check if an FS item is used, select one FS item and choose Check Where Used.

Follow-Up Activities

After creating or changing any FS items, you may need to perform the following activities:

• Include the new FS items in any relevant FS item hierarchies or reporting item hierarchies using the
Manage Global Hierarchies app. See Define Hierarchies [page 51] for details.
• Map the new FS items with general ledger accounts using the Map FS Items with G/L Accounts [page 55]
app.
• Update all FS item-related settings as necessary, such as the following:
• Selected FS items for automatic posting (annual net income and deferred taxes), currency translation
methods, and reclassification methods in the respective Customizing activities.
• FS items to be carried forward or not, validation rules, selections, and reporting rules using the
respective app on the SAP Fiori launchpad.

Group Reporting (FIN-CS)

50 PUBLIC Group Reporting
  Note

This app contains Web Assistant documentation for key fields and concepts. To display the documentation
while working in the app, press F1 or click the question mark displayed in the app header.

Supported Device Types

• Desktop
• Tablet
• Smartphone

1.2.2.3.5.2 Define Hierarchies

In a specified consolidation chart of accounts, you can edit hierarchies for financial statement (FS) items with
the Manage Global Hierarchies app. The item hierarchies determine the layout of respective reports.

SAP pre-delivers the following FS item hierarchies:

Hierarchy Type Hierarchy ID Description Remarks

Consolidation Financial BS Balance Sheet All FS items that belong to

Statement Item balance sheets.

PL Profit & Loss Statement All FS items that belong to

P&L statements.

BS_PL Balance Sheet and P&L All FS items that belong to

Statement balance sheet and P&L state­
ment.

ST Statistical FS Items All FS items needed for post­

ing group shares of individual
investee units.

X6 Currency Translation – Re­ All investment and equity

serve items translated at historical
exchange rates.

Consolidation Reporting Item X1 Statement of Equity All reporting items that be­
long to statement of changes
in equity.

X2 Cash Flow Statement All reporting items that be­

long to cash flow statement
(indirect method).

Group Reporting (FIN-CS)

Group Reporting PUBLIC 51
Hierarchy Type Hierarchy ID Description Remarks

X3 Statement of Comprehensive All reporting items that be­

Income long to statement of compre­
hensive income.

X4 P&L by Function of Expense All reporting items that be­

long to P&L statement by
function of expense.

X5 Interunit Reconciliation All reporting FS items that

belong to interunit reconcilia­
tion reports. Each reporting
item stands for a reconcilia­
tion case, for example, for in­
terunit reconciliation for re­
ceivables and payables, or in­
come and expense.

Change Item Hierarchies

If you have created or changed any FS items and want to update the above listed FS item hierarchies, you can
proceed as follows:

1. In the app, select Consolidation Financial Statement Item in the Type field.

 Note

To edit the item hierarchies X1, X2, X3, X4, or X5, select Consolidation Reporting Item as the hierarchy
type. These item hierarchies contain the FS items with Reporting Item as their item type. See FS Item
Type [page 42] for more information.

2. Select an existing hierarchy in the Hierarchy ID field, for example, BS (balance sheet). Choose Go.
3. Choose the item hierarchy from the result list to edit it in the detail screen.
4. Choose Edit.
5. Expand the hierarchy to the relevant node level and perform any following steps as necessary:
• Import a node: Choose Import Nodes from the More menu ( ) to import a node and its contained
subnodes and FS items from another item hierarchy.
• Add a node or FS item: Choose the Add icon ( ) in the last column to open the Add Node dialog and
enter the necessary information, that is, FS item ID, or node ID and description.
• Change a node or FS item: Choose the node or FS item itself to open the Change Node dialog and
replace with a new FS item ID, or node ID and description.
• Delete a node or FS item: Choose the Delete icon ( ) to delete the FS item on the respective row or
choose Delete from the More menu ( ) to delete a node and all FS items it contains.
6. Choose Activate to apply the changes you made to the hierarchy.

Group Reporting (FIN-CS)

52 PUBLIC Group Reporting
  Note

Choosing Save will generate a version with In Revision status. The original active version stays
unchanged and continues being used in any relevant reporting structure.

The hierarchies for Consolidation Financial Statement Item and Consolidation Reporting Item don't have
time-dependency, meaning they are valid permanently, hence the noneditable Dates Valid field.

Create Item Hierarchies

If you want to create an item hierarchy with a new ID, you can use either of the following approaches:

Use Copy Feature

1. Open one of the existing item hierarchies that most resembles what you want to create.
2. On the detail screen, choose Copy To New Hierarchy .
3. In the dialog, enter an hierarchy ID and a description, and choose Copy.
4. The new hierarchy is created. You can proceed to edit the hierarchy as described above.

Use Export/Import Feature

1. Open one of the existing item hierarchies that most resembles what you want to create.
2. On the detail screen, choose Export/Import Export to Spreadsheet . The hierarchy is exported to an
MS Excel file, which contains all its node levels and FS items.
3. Choose Create on the initial screen.
4. In the dialog, select Consolidation Financial Statement Item or Consolidation Reporting Item in the Type
field, depending on the usage of your hierarchy, and specify a hierarchy ID, description, and the
consolidation chart of accounts.
5. For the new empty hierarchy, repeat step 2 to export it to a second spreadsheet.
6. Copy the information in Type, ID, Description, and Parent ID columns from the first spreadsheet to the
respective columns of the second spreadsheet.
7. Edit the information in the second spreadsheet to fulfill your needs.

 Note

The top node ID (and the parent ID of level-2 nodes) should be same as the ID you specify for the new
hierarchy.

8. On the detail screen of your new hierarchy, choose Export/Import Import from Spreadsheet to
import the second spreadsheet to system.

 Note

If the spreadsheet you upload exceeds 250 KB, a hierarchy upload job is triggered automatically, and
you can use the Display Hierarchy Upload Jobs app to display detailed logs about the job.

9. Save or activate the new hierarchy, depending on whether you want to use it in reporting structure
immediately.

Group Reporting (FIN-CS)

Group Reporting PUBLIC 53
Supported Device Types

• Desktop

Related Information

Manage Global Hierarchies

1.2.2.3.6 Integration with G/L Accounts

In SAP S/4HANA, group reporting is integrated with financial accounting (FI). Applications in group reporting
can directly access the documents of the universal journal (table ACDOCA), while some of the accounting
source data fields are converted to group reporting fields.

One prerequisite for the FI integration is that the financial statement (FS) items under the consolidation chart
of accounts and general ledger (G/L) accounts under any relevant G/L chart of accounts need to be mapped,
so that the data posted in financial accounting (FI) can be correctly processed in group reporting. The
mappings also need to be assigned to the relevant consolidation versions and effective periods. For an initial
set-up, you can follow the procedure below to import the SAP delivered mapping between FS items under
consolidation chart of accounts Y1 and G/L chart of accounts YCOA, and assign the mapping to a validity
period:

1. Open the Map FS Items with G/L Accounts app and check if the mapping Y1 revision 01 exists with status
Active.
2. If it doesn’t exist, create the mapping Y1/01: Choose Import and upload the file
Financial_Statement_Item_Mapping.xlsx that you can download from the SAP Note 2659656
3. Open the Assign FS Item Mapping app and check if the following assignment exists:

From Period/ FS Item Mapping Consolidation G/L Chart of Ac­

Year Version COA counts Mapping ID Revision

001/1900 Y10 (FS item Y1 YCOA Y1 1

mapping version)

4. If the assignment doesn’t exist, make the assignment by choosing New and entering the values mentioned
in the table above.

If you want to create your own mapping or revise the pre-delivered one, you can use the apps described in the
following sections.

Related Information

Map FS Items with G/L Accounts [page 55]

Group Reporting (FIN-CS)

54 PUBLIC Group Reporting
Import/Export FS Item Mappings [page 58]
Assign FS Item Mappings to Periods and Versions [page 59]

1.2.2.3.6.1 Map FS Items with G/L Accounts

With this app, you can display, create, or change financial statement (FS) item mapping revisions, including the
mapping relationships between individual FS items and general ledger (G/L) accounts.

Key Features

This app provides the following key features:

Display Mapping Revisions

Using the filter criteria, you can show FS item mapping revisions of your selection，including the following
information:

• G/L Chart of Accounts, Consolidation Chart of Accounts, Mapping ID, and Revision: A combination of these
values identify a unique FS item mapping revision.
• Status: Each mapping revision can have one of the following statuses:
• Draft: The mapping revision was uploaded using the Import FS Item Mappings app. From there, you
navigated to its detail page, which is part of this app, and made some changes without saving them.
System automatically saves your changed version as a draft and displays in this list.
• Active: The mapping revision is saved.
• Active (With Draft): The mapping revision was saved before. After that, you opened the saved version
and made some changes without saving them. System automatically saves your changed version as a
draft with the same revision ID. When opening a revision with this status, you are editing its latest draft.
Saving it will generate a new active version and overwrite the previous one.
• Assigned: Whether a mapping revision is assigned to an effective period and an FS item mapping version
using the Assign FS Item Mappings app. Note that an assigned revision cannot be deleted.
• Mapped G/L Accounts and Unmapped G/L Accounts： Number of the G/L accounts that are mapped or
not mapped to an FS item. Note that multiple G/L accounts can be assigned to one FS item, not the other
way around.

In the list, you can sort or filter the mapping revisions using the available criteria.

By choosing the arrow icon ( ), you can navigate to the detail page of each mapping revision to view which G/L
accounts are mapped to which FS items.

Group Reporting (FIN-CS)

Group Reporting PUBLIC 55
The process described above is depicted in the following figure:

Change Mapping Revisions

When displaying any mapping revision in the detail screen, you can add or change the mapping relationships
between any G/L accounts and FS items by choosing Edit.

When assigning FS items to G/L accounts in the Unmapped G/L Accounts tab page, you can check the column
Posting Data Exists. It indicates whether the general ledger (G/L) account has any data posted in the specified
period range. If posting data exists for any G/L account, the Open Document List icon ( ) is displayed for that
G/L account, listing the respective accounting documents, from where you can drill through to more details at
line item level for each document.

You can choose Recheck Posting Data to specify different parameters other than the default ones to check if
any posting data exists, for example, for a different consolidation version or a fiscal year/period range.

 Note

If a G/L account already has data posted and released in the Release Universal Journals task, you can't
change or delete its existing mapping with FS items in the mapping revision that has been assigned to the
respective period and version.

Create Mapping Revisions

You can create a new mapping revision as follows:

• If you want to create a new revision based on a new mapping rather than an existing one, choose Create
Mapping. In the pop-up window, keep the With Revision option selected, select a G/L chart of accounts and
a consolidation chart of accounts, and enter the ID and description for the new mapping and revision.
• If you want to create a revision for an existing mapping, choose Create Revision. In the pop-up window,
select the mapping ID, G/L chart of accounts, and consolidation chart of accounts from the drop-down
lists, and enter the ID and description for the new revision.
• If you only want to create a revision based on an existing revision that has the same mapping ID, G/L chart
of accounts, and consolidation chart of accounts, select that existing revision and choose Copy, then enter
the ID and description for the new revision.

Group Reporting (FIN-CS)

56 PUBLIC Group Reporting
  Note

This is particularly useful when a new FS item has been created and you must change the G/L account
mapping to source this new FS item.

After creating the revision, you can go to its detail screen to maintain the mapping relationships between
individual FS items and G/L accounts using the procedure described above.

Export or Import Mapping Revisions

You can select one or more revisions and choose Export to export them into a spreadsheet. The exported list
contains the mapping details at the G/L account level, that is, which G/L accounts are mapped to which FS
items in the respective mapping context.

By choosing Import, you can navigate to the Import/Export FS Item Mappings [page 58] app, where you can
upload a number of mapping revisions into the system all at once.

Exclude G/L Accounts

If you want to exclude G/L accounts from being released into Group Reporting, for example secondary cost
elements, you can map these G/L accounts to a specific FS item using the FS item ID &NORELEASE. You can
exclude G/L accounts as follows:

1. Create an FS item named &NORELEASE. Use the Define FS Items app to create the FS item with the
following attributes:
• FS Item Type: Statistical Item
• Is Blocked For Posting: Yes
2. Map the G/L accounts you want to exclude to the FS item &NORELEASE

Follow-Up Activities

After creating or changing any FS item mapping revision, you may need to adjust its assignment of the effective
period and version. You can do this by selecting a mapping revision and choosing Assign within this app. You
are then brought to the Assign FS Item Mappings to Periods and Versions [page 59] app to complete the
assignment.

 Note

This app contains Web Assistant documentation for key fields and concepts. To display the documentation
while working in the app, press F1 or click the question mark displayed in the app header.

Supported Device Types

• Desktop
• Tablet
• Smartphone

Group Reporting (FIN-CS)

Group Reporting PUBLIC 57
Related Information

Release Universal Journals [page 151]

1.2.2.3.6.2 Import/Export FS Item Mappings

With the Import FS Item Mappings app, you can maintain or view the mapping between financial statement
(FS) items and general ledger (G/L) accounts using the import and export feature.

Import Mapping Revisions

To create or change mapping revisions using the import feature, follow this procedure:

1. In the app, download a template.

2. In the template, enter the following information for each row:
• Consolidation COA: Y1.
• Mapping ID: Enter the ID of the mapping between FS items under a specific consolidation chart of
accounts and G/L accounts under the G/L chart of accounts.

 Note

By entering a non-existing mapping ID, you can create a new mapping. Optionally, specify a
meaningful mapping name in the Mapping Name column.

• Mapping Revision: Differentiates multiple mapping variants within the same mapping ID.

 Note

By entering a non-existing revision ID, you can create a new mapping revision. Optionally, specify a
meaningful revision description in the Revision Description column.

• G/L Chart of Accounts: A classification scheme consisting of a group of G/L accounts. This chart of
accounts is the operative chart of accounts and is used in financial accounting (FI).
• G/L Account: Contains the G/L account number to which the transaction data are posted to record
values during a posting period.
• FS Item: Enter the ID of an existing FS item that you want to map with the G/L account in the same row.
3. In the app, choose Browse... to upload the completed file to the app.
4. Select the relevant rows and choose the Check button to check the data for any errors.
5. After correcting any detected errors according to the hints provided in the Check Message column, choose
the Import button to import the mapping revisions to the system.
6. If necessary, you can choose the arrow icon ( ) on any mapping revision row to navigate to the Map FS
Items with G/L Accounts [page 55] app for further changes.

Export Mapping Revisions

When downloading a template, you can select the With Existing Master Data option and specify any necessary
criteria, such as consolidation chart of accounts, G/L chart of accounts, mapping ID, and revision. In this way, a
list of FS item mapping revisions are exported to a spreadsheet, which contains the mapping details at the G/L
account level, that is, which G/L accounts are mapped to which FS items in the respective mapping context.

Group Reporting (FIN-CS)

58 PUBLIC Group Reporting
  Note

The export feature in this app is equivalent to that in the Map FS Items with G/L Accounts [page 55] app,
except that it offers the option for including unmapped G/L accounts in the exported list. This can be done
by selecting the With Unmapped G/L Accounts checkbox when downloading the spreadsheet.

Follow-Up Activities

After creating or changing any FS item mapping revision, you may need to adjust its assignment of the effective
period and version. For more information, see Assign FS Item Mappings to Periods and Versions [page 59].

 Note

This app contains Web Assistant documentation for key fields and concepts. To display the documentation
while working in the app, press F1 or click the question mark displayed in the app header.

1.2.2.3.6.3 Assign FS Item Mappings to Periods and Versions

With the Assign FS Item Mappings app, you assign the existing financial statement (FS) item mappings to
consolidation versions and effective periods, so that the mappings between FS items under a consolidation
chart of accounts and general ledger (G/L) accounts under a G/L chart of accounts can be applied to a certain
consolidation version within the specified time frame.

Prerequisite

To assign FS item mappings to versions and periods, you must have defined the relevant FS item mappings as
described in the previous help topics.

 Note

The assignment to consolidation versions is through the special version FS Item Mapping Version, which is
assigned to various consolidation versions. For more information about special versions, see Customizing
SAP S/4HANA for Group Reporting under Master Data Define Versions .

The SAP pre-delivered mapping Y1 revision 01 is assigned to the FS item mapping version Y10 and a
prolonged effective period. You can change the assignment by following the procedure below.

Group Reporting (FIN-CS)

Group Reporting PUBLIC 59
Key Features

This app provides the following key features:

Display or Delete Assignment

You can view the current assignments of FS item mappings, for example, for a certain mapping revision, the
valid-from and valid-to periods, and which FS item mapping version it is assigned to.

You can delete an assignment of FS item mapping. In this case, the assignment for its earlier period will apply,
provided that it is assigned to the same FS item mapping version, consolidation chart of accounts, and G/L
chart of accounts.

 Example

You deleted the assignment for the period 008/2015 to 012/2016 from the following list:

Consolidation
From Period/ To Period/ FS Item Map­ Chart of Ac­ G/L Chart of
Year Year ping Version counts Accounts Mapping ID Revision

001/2015 007/2015 Y10 Y1 YCOA Y1 001

008/2015 012/2016 Y10 Y1 YCOA D01 001

001/2017 012/9999 Y10 Y1 YCOA Y1 002

The assignment for the earlier period, mapping Y1 and revision 001 take effects for the period 008/2015 to
012/2016.

 Note

To Period/Year is not visible in the app. You only need to define the valid-from period, and the system will
help derive the valid-to period.

The assignment of the FS item mapping you are trying to delete may already be used in transactional data.
Please delete assignments with caution.

New Assignment
You can assign an existing mapping revision to a certain effective period and FS item mapping version by
choosing the New button. In the New Assignment dialog box, the consolidation chart of accounts and G/L chart
of accounts are automatically populated after you enter a mapping ID and a revision. You only need to
additionally specify the valid-from year/period and FS item mapping version, then the assignment is created.

Change Assignment
After selecting an assignment row and choosing the Edit button, you can change the assigned mapping ID and
revision for the valid-from period and FS item mapping version.

When changing an assignment, the consolidation chart of accounts and G/L chart of accounts are not editable.
If you want to change them, you need to delete the assignment and create a new one.

Group Reporting (FIN-CS)

60 PUBLIC Group Reporting
  Note

This app contains Web Assistant documentation for key fields and concepts. To display the documentation
while working in the app, press F1 or click the question mark displayed in the app header.

More Information

• The SAP Fiori apps reference library has details about the content necessary for giving users access to an
app on the SAP Fiori launchpad. The SAP Fiori apps reference library is available here: https://
fioriappslibrary.hana.ondemand.com
To see this app’s Fiori content, search for the app. Then select SAP S/4HANA as the product. On the
Implementation Information tab, select the correct release. The details are in the Configuration section.

1.2.2.3.7 Maintain Default Values

With this app, you can define the default values for the following characteristics:

• Partner Unit
• Subitem

These default values are used when information is missing for the given characteristic and the use of default
values is permitted. For example, the default subitem for subitem category 1 (Transaction Types) is 915 (Net
Variation). This subitem will be used as default when its value is missing during the real-time update of reported
financial data.

1.2.2.3.8 Check and Correct Breakdowns of Transaction

Data

Following the changes to financial statement (FS) items on their assigned breakdown types for
subassignments such as Partner Unit or Subitem, you should check if the existing transaction data is
consistent with the FS item settings.

 Example

The FS item 112000 has a breakdown type 1 (Optional breakdown: Initialized value allowed) for Partner
Unit.

The following transaction data exists:

FS Item Partner Unit Amount

112000 None 1000 USD

Group Reporting (FIN-CS)

Group Reporting PUBLIC 61
 You change the breakdown type of the Partner Unit to 4 (Required breakdown: Entry is forced, default not
allowed) for this FS item. The transaction data record becomes invalid because a partner unit is missing.

You can identify and correct the inconsistency by using this app.

After specifying the criteria, such as consolidation chart of accounts and fiscal year, choose the Execute
button. The list of inconsistent data records is displayed. Go to the Subassignments tab to enter the missing
values. Or, if the breakdown type was changed to 2 or 3, which allow default values, the values you defined in
the app Maintain Default Values are, or can be used, to solve the inconsistency.

1.2.2.3.9 Selected FS Items

It can be necessary to make manual or automatic postings on the selected financial statement (FS) items, such
as for net income and deferred income tax.

You can post deferred tax in the B/S and in the P&L directly. However, you cannot post annual net income (ANI)
in the balance sheet (B/S) or the profit and loss statement (P&L) directly. These items are posted
automatically based on the deferred tax you posted.

The posting concept with selected FS items is displayed in the following figure:

To specify selected FS items for automatic posting, go to Customizing for SAP S/4HANA for Group Reporting
under Consolidation FS Items Configuration Specify Selected FS Items for Automatic Posting .

Group Reporting (FIN-CS)

62 PUBLIC Group Reporting
1.2.2.3.10 Financial Statement Item Extensibility

You can create your own financial statement (FS) item attributes. They can then be used in selections,
reclassification rules, totals validation rules, and analytics.

Prerequisites

You need authorizations for extensibility to create your own FS item attributes.

Overview

Creating Custom Fields

To create your own FS item attributes, you must first define new custom fields for FS item master data in the
Custom Fields app.

There are two types of FS item attributes that you can define: attributes that are time- and version-
independent and attributes that are time- and version-dependent. Depending on which of these two options
you choose, you select a specific Business Context when creating a new custom field.

For time- and version-independent attributes, select Consolidation Financial Statement Item for the business
context.

For time- and version-dependent attributes, select Consolidation Financial Statement Item Time/Version
Dependent for the business context.

Custom Field Settings for FS Item Selection Attributes and Target Attributes
You can create time- and version-dependent FS item attributes that can be used like standard selection
attributes or target attributes. To do so, you must make specific selections when defining the custom fields.

• For FS item selection attributes:

• For Type, select Code List. This then reveals the List Values section.
• In the List Values section, define a list of Code Value and Description combinations. Later, users can
choose entries from this list to assign them as attribute values to FS items. If necessary, descriptions
can be translated into different languages.

 Note

Descriptions must be maintained language dependent. If your description is translated into

multiple languages, then any changes to the description must also be maintained for each
language that the description is translated in.

 Note

You can use the download and upload functions in the List Values section to maintain these
combinations of code values and descriptions in a CSV file, rather than create single entries
manually.

Group Reporting (FIN-CS)

Group Reporting PUBLIC 63
• For FS item target attributes:
• For Type, select Association to Business Object. This then reveals the selection field Business Object.
• For Business Object, select Consolidation Financial Statement Item.

Enable Usage for the Import Consolidation Master Data App

To be able to display and filter your custom FS item attributes on the Import FS Items screen of the Import
Consolidation Master Data [page 90] app, you must first enable this usage in the UIs and Reports tab. To do
so, navigate to the UIs and Reports tab and select Enable Usage for the data source FINCS_MD_XLSX_SRV.

 Note

Don't forget to Publish your custom fields once you define them. Without publishing the fields, they won't
be visible anywhere for users.

Maintenance

After you’ve defined custom fields, you can maintain FS item attribute value assignments for your custom
attributes with the Define FS Items [page 49] app and the Import Consolidation Master Data [page 90] app.

Define FS Items
In the Define FS Items [page 49] app, you can add your custom fields to the UI on the Financial Statement Item
Details screen, which you can access by selecting an entry in the table. With these fields on the UI, you can then
assign your newly defined attribute values to FS items. You can add these fields with the Adapt UI option in the
user actions menu.

 Note

You must have extensibility authorizations to adapt the UI and add custom fields. Any UI adjustment will be
visible to every user of the app.

On the main screen of the Define FS Items [page 49] app, you can add filters for your custom FS item attributes
with Adapt Filters. Also, you can add columns to the table of FS items in the table’s Settings. By doing so, you
can filter for FS items that have been assigned with your custom FS item attributes and see these assignments
in the table.

 Note

Anyone can adjust the filters and columns on the main screen of the Define FS Items [page 49] app for their
individual use. However, only a user with special authorizations can adjust the filters and columns and then
save the result centrally as a public view. The adjustments then appear for all users.

Import Consolidation Master Data

In the Import Consolidation Master Data [page 90] app, you can maintain the assignments of your custom FS
item attribute values in spreadsheets. When you download a template for FS items with or without existing
master data, your newly defined custom fields for the FS item attributes appear as columns. You can then
maintain the FS item attribute value assignments in these columns for each FS item.

Group Reporting (FIN-CS)

64 PUBLIC Group Reporting
  Note

For custom defined FS item target attributes, two columns appear in the spreadsheet: one for the
consolidation chart of accounts (COA) and one for the target FS item. The values in the consolidation COA
column must be the same as the consolidation COA in the Mandatory Filter Values section of the
spreadsheet. If not, this will result in check errors later, and the entries won’t be able to be imported.

On the Import FS Items screen after uploading the master data from the spreadsheet, you can add filters for
your custom FS item attributes with Adapt Filters. Also, you can add columns to the table of FS items in the
table’s Settings. By doing this, you can filter for FS items that have been assigned with your custom FS item
attributes and see these assignments in the table.

 Note

Anyone can adjust the filters and columns on the Import FS Items screen of the Import Consolidation
Master Data [page 90] app for their individual use. However, only a user with administrator authorizations
can adjust the filters and columns and then save the result centrally as a public view. The adjustments then
appear for all users.

 Note

Before you can display and filter your custom FS item attributes on the Import FS Items screen of the
Import Consolidation Master Data [page 90] app, you must first enable the usage of data source
FINCS_MD_XLSX_SRV in the UIs and Reports tab when defining the custom field.

Use

After assigning the attribute values to FS items, you can use your custom FS item attributes in the following
ways:

• In selections with the Define Selections [page 84] app

• In reclassification rules with the Define Reclassification Methods customizing activity
• In totals validation rules with the Define Validation Rules [page 99] app
• In Analytics for Group Reporting [page 507], such as in the Group Data Analysis [page 522] app

 Note

Only custom FS attributes that are time- and version-independent can be used in analytics.

Related Information

FS Item Selection and Target Attributes [page 42]

Custom Field Extensibility [page 559]

Group Reporting (FIN-CS)

Group Reporting PUBLIC 65
1.2.2.4 Ad Hoc Item

An ad hoc item is an item that is created on an ad hoc basis as it is required. It facilitates the naming, collection,
and reporting of a set of values that are supplemental to the modeled data.

 Note

The Define Ad Hoc Items app is not yet in productive use. You can define ad hoc items, but these items can’t
be used in other apps. For more information and to get early updates about changes in the productive
availability of ad hoc items, please see Define Ad Hoc Items.

Ad hoc items allow you to select and display data collected from your consolidation units in SAP S/4HANA and
SAP Analytics Cloud. When you use an ad hoc item, data values are still stored in the Group Journal Entries
(ACDOCU) table.

If the dimension combination you want to collect data for does not yet exist, you can define ad hoc items using
the Define Ad Hoc Items app in SAP Group Reporting Data Collection.

1.2.2.5 Subitem Categories/Subitems

Subitem and subitem category are subassignments for financial statement (FS) items. Both characteristics are
in a compound with each other. The subitem is dependent on the subitem category. The subitem category
classifies the subitems.

1.2.2.5.1 Define Subitem Categories

The subitem category enables you to classify your subitems, which are needed for the subassignment of FS
items.

A subitem category is assigned to the relevant FS items via breakdown categories. This also applies to
subitems.

The SAP standard system contains two predefined subitem categories:

• Transaction Types
• Functional areas

Subitems are predefined for each subitem category that is provided with the delivered content.

Neither the subitems nor the subitem categories are dependent on the consolidation chart of accounts.

Group Reporting (FIN-CS)

66 PUBLIC Group Reporting
Procedure

To define subitem categories, go to Customizing for SAP S/4HANA for Group Reporting under Master Data
Define Subitem Categories and Subitems

1.2.2.5.2 Define Subitems

Subitems are used to further breakdown the values recorded on financial statement (FS) items with
transaction types or functional areas. For example, transaction type 900 (opening balance) is used for balance
carryforward..

In the breakdown category, you specify which subitems must be used. The subitem category is fixed to 1
(Transaction Types) or 2 (Functional Area) in breakdown category. Furthermore, you can to specify a range of
subitems by defining the maximum selection. For more information, see Breakdown Categories [page 47].

 Note

Subitems defined in subitem category 1 (Transaction Type) share the following selected subitems::

Carry forward to subitem 900 Opening balance

Subitem for retirements/divestitures 998 Outgoing unit

Acquisition subitem 901 Incoming unit

Example

The breakdown category 1B00 is assigned to FS item 111100. This breakdown category has two
subassignments:

• Subitem category fixed value: 1 (Transaction Types)

• Subitem; all subitems under the selection S-BC-TT-02 are allowed (900-903, 909, 915, 950, 970, 980, 998,
955). The default value 915 (net variation) is defined in the Maintain Default Values app.

When you post journal entries using FS item 111100, the subitem 915 is automatically selected. If you don’t
want to use the default value, you can change the subitem to one of the allowed subitems.

Procedure

To define subitems, go to Customizing for SAP S/4HANA for Group Reporting under Master Data Define
Subitem Categories and Subitems .

To display all subitems and their details, such as subitem category, carry forward to subitem, and acquisition
subitem, go to the Subitems List app.

Group Reporting (FIN-CS)

Group Reporting PUBLIC 67
For defined subitems, you can additionally maintain their hierarchies using the Manage Global Hierarchies app.
For more information, see Define Hierarchies [page 95].

1.2.2.6 Consolidation Versions

Use
A consolidation version identifies a separate data area in the consolidation database. Versions make it possible
to consolidate different sets of financial data or consolidate in different group currencies. For example, you
might have separate parallel versions to fulfill different reporting needs, such as actuals data for publishing
official reports, and planning and forecast data for internal evaluation.

Settings
You can change any settings for the preset versions by using the Define Versions configuration step. However,
to create a new version, you need to first copy from an existing version by using the Create Version from
Reference Version configuration step and then modify the settings of the new version.

 Note

With the new group reporting logic, you now assign the group currency and source ledger in the Define
Versions configuration step.

If the new group reporting logic is active, the following version types are available:

• Standard version:
The standard version is a version that does not have a reference version. It leads the process run and the
task status for the standard version also applies to the versions that reference it. A standard version can
store data in local currency (LC), group currency (GC), transaction currency (TC), and quantity (QTY).
• Group currency extension version:
The group currency extension version has a reference version but it has a different group currency than the
reference version. This reference version must be a standard version. The group currency extension
version can only store data in group currency.
• Extension version:
The extension version has a reference version but it has the same group currency as the reference version.
It, for example, translates financial data using a different translation approach, such as using budget rates.
This reference version can be a standard version or an extension version. From a technical perspective, it
carries only the delta amount to the reference version. The extension version can only store data in group
currency.

The reference version specifies the source version for the local currency, transaction currency, and quantities.
It also specifies the version that initiates the task run.

 Example

In this example, you want to consolidate financial statements in currencies EUR, USD, and CNY. The GC
extension versions Y12 and Y13 use the reference version Y11, where local currency values are stored.
Additionally, you want to consolidate financial statements in EUR using the exchange rate from the budget.
In this case, Y14 is an extension version. The GC extension versions and the extension version are run
synchronously with the standard version.

Group Reporting (FIN-CS)

68 PUBLIC Group Reporting
 Reference Ver­ Group Cur­
Version sion rency Rates Version Type Stores Amounts

Y11 - EUR Standard rate Standard LC, TC, Qty, GC Full

Y12 Y11 USD Standard rate GC extension GC Full

Y13 Y11 CNY Standard rate GC extension GC Full

Y14 Y11 EUR Budget rate Extension GC Delta

Note that you can only assign one group currency to one version and the tax rate needs to be the same for
related version types.

 Note

If data exists on a version, the reference version can't be changed anymore.

You can assign a source ledger to the version, which you use to select the ledger from accounting to read
accounting documents.

 Note

If you do not select a fiscal year variant (FYV), the system uses K4 as the FYV if necessary. If you have
selected an FYV, do not change it again, because the periods are stored in system tables and are not
changed if you change the FYV. You must assign the same FY variant to all versions that have the same
special versions with reference to time-dependent settings, for example, for attributes, data entry, or tax
rate. You also need to assign the same fiscal year variant to the standard version and the extension version
that refer to the standard version.

SAP recommends that you use the same FYV in all versions. Do not use the FYV to define various valid
periods in different versions related to each other. This would significantly increase the complexity of your
comparison reporting and other system tasks (for example, data copy). You should, for example, use the
same FYV (here, with 12 periods) for monthly (management) reporting and for quarterly financial reporting.

For more information, see Fiscal Year Variant [page 97].

For each consolidation version, you can assign special versions.

The following special versions are applicable for the new and old reporting logic:

• Structure: Controls the assignment of consolidation units to consolidation groups as well as consolidation
relevant settings for consolidation units, such as the period of the first consolidation, the period of the
divestiture, and the consolidation method.
• Exchange Rates: Controls the assignment of exchange rate type to exchange rate indicator.
• FS Item Attribute: Controls the time and version dependency of FS item attributes.
• Reporting Rules: Controls the assignment of reporting rule variants to consolidation version. For more
information, see Assign Reporting Rules to Versions [page 131].
• FS Group Items: Controls the mapping relationship between financial statement (FS) items and general
ledger accounts. For more information, see Assign FS Item Mappings to Periods and Versions [page 59].

The following special version are applicable for the new reporting logic only:

• Data Entry: Acts only for the validation method.

Group Reporting (FIN-CS)

Group Reporting PUBLIC 69
• Consolidation Group Attributes: Controls the assignment of version-dependent attributes to consolidation
groups.
• Consolidation Unit Attributes: Controls the assignment of version-dependent attributes to consolidation
units, for example, universal journal integration, source fields for local and group currency, upload method,
currency translation method, and tax rate.
• Reclassification and Elimination: Controls the assignment of method and document type to task.

The following special version are applicable for the old reporting logic only:

• Data Entry: Acts on data transfer method, flexible upload method, and validation method.
• Tax Rate: Determines the tax rate of consolidation units.
• Ledger: Controls the assignment of ledger and currency to consolidation groups.
• Translation Method: Controls the assignment of translation method to consolidation unit.
• Reclassification: Controls the assignment of method and document type to task.

The assignment of special versions enables reuse of the maintained settings among different consolidation
versions, that is, you only need to enter the control parameters once in special versions and assign the special
versions to consolidation versions. For example, consolidation versions for actuals data and planning data can
share all special version settings except that for Exchange Rates. In this case, you can assign different Exchange
Rates special versions but different special versions to each consolidation version. When you perform a task in
a consolidation version, the system reads the special versions that are relevant for that task and that are
assigned to that consolidation version.

Multiple template consolidation versions are preset in the system, such as actuals (Y10 and Y20), budget
(YB*), year-end forecast (YF*), and actuals using budget exchange rates (Y11 and actuals using simulated
exchange rates (Y12).

For the new reporting logic, the standard version and the related extension versions must have the same
special version for the structure, reclassification and elimination, FS item attributes, reporting rules, FS group
items, fiscal year variant, and source ledger.

For the new reporting logic, the standard version and the related extension versions must have the following
identical attribute values:

• Fiscal year variant

• Source ledger
• Use plan data integration
• Special versions:
• Data entry
• structure
• Reclassification and elimination
• FS item attributes
• Consolidation group attributes
• Reporting rules
• FS group items

Group Reporting (FIN-CS)

70 PUBLIC Group Reporting
1.2.2.6.1 Version Stack

The version stack comprises a group of consolidation versions that are linked together by each of their
respective reference version settings. Each version in a version stack represents a different view of the
consolidation financial statements, and these views correspond to specific scenarios.

Definition

In a version stack, there’s one standard version and any number of extension versions that are linked to the
standard version. These extension versions can also be group currency (GC) extension versions.

This link to the standard version can be either direct or indirect. A direct link is where the standard version is
the reference version of an extension version. An indirect link is where an extension version is the reference
version of another extension version. These indirect links eventually lead to the same standard version, since
the first extension version is created using the standard version as a reference version.

The following graphic illustrates a version stack with extension versions that link to the standard version
directly and indirectly.

Group Reporting (FIN-CS)

Group Reporting PUBLIC 71
In the graphic, Z01 is the standard version. Z10, Z20, Z30, and Z31 are all extension versions. Z10 was created
first, and Z01 was assigned as its reference version. As a result, Z10 is directly linked to the standard version.
Z20 was created next, and Z10 was assigned as its reference version. Since its reference version is not the
standard version, Z20 is indirectly linked to the standard version. Similarly, Z30 and Z31 were created, and Z20
was assigned as their reference version. So, they're both indirectly linked to the standard version as well. Since
all these versions are built on top of one another, they all link to the same standard version via their reference
version settings and thus comprise a version stack.

For more information on versions, see Consolidation Versions [page 68].

Group Reporting (FIN-CS)

72 PUBLIC Group Reporting
Purpose

In a version stack, you combine a standard version and one or more extension versions to produce different
views of the consolidation financial statements. Each of these views corresponds to a different scenario, such
as Multiple Group Currencies [page 134] or Restatement and Simulation [page 545].

 Example

You can have a version stack that contains a standard version for standard consolidation in EUR. Then, you
can add to the version stack a GC extension version for consolidation in USD. Next, you can add an
extension version to consolidate using budget rates. Lastly, you add another extension version to restate
the consolidation financial statements in the standard version according to a new accounting standard.
This produces a version stack with one standard version, a GC extension version, and two extension
versions. Each of the versions in the stack represents a different view of the consolidation financial
statements for a unique scenario.

Consistency Checks in the Version Stack

To do certain activities in group reporting, some settings must be consistent across all versions in a version
stack. Consistency checks verify the consistency of these settings for version attributes as well as attributes of
other entities, such as consolidation unit and document type.

Here's an example of a consistency check for a version attribute:

 Example

The setting for the option Use Planned Data Integration must be consistent across the version stack. For
example, you can't copy a version with the option Use Planned Data Integration selected into a version stack
where none of the versions have this option selected.

Here are some examples of consistency checks for attributes of other entities:

 Example

The settings for the deviating fiscal year variant (FYV) of a consolidation unit must be consistent across the
version stack. The system uses the FYV in many instances when processing data, such as selecting
exchange rates in the currency translation. So, if the settings for the deviating FYV are inconsistent, this
could lead to inconsistencies when processing data.

You can adjust the settings for the deviating FYV of a consolidation unit in the Define Consolidation Units
[page 15] app.

 Example

The automatic reversal settings of a document type must be consistent across the version stack. Different
automatic reversal settings result in inconsistent data in the different versions that are processed together.
For example, if you posted a manual journal entry in multiple versions, the bundled documents would be
inconsistently reversed (or not reversed) if the automatic reversal settings were not identical in the different
versions.

Group Reporting (FIN-CS)

Group Reporting PUBLIC 73
 You can adjust the automatic reversal settings of a document type in the Define Document Types
configuration activity.

Related Information

Define Consolidation Units [page 15]

Consolidation Versions [page 68]
Document Types and Posting Levels [page 77]

1.2.2.7 Consolidation Ledger

 Note

With the introduction of a new architecture/reporting logic, the consolidation ledger is only applicable to a
SAP S/4HANA Finance for group reporting release earlier than 2020 or if you have not activated the new
reporting logic. With the new group reporting logic, the assignment of group currency and source ledger is
now done in the version definition. To activate the new reporting logic, please create an incident with the
FIN-CS-COR component.

A consolidation ledger serves two purposes:

• Defining the group currency. Currency of the ledger determines the currency of the financial data of the
consolidation groups (CGs) in the ledger report. If you want to consolidate in different currencies, you need
a separate ledger for each group currency. You assign a different ledger to the group for each version. In
one version, all consolidation groups should be assigned to the same ledger. You need to change the global
parameters before you adjust the ledger of the consolidation group.
• Defining the valuation. With the FI accounting integration, an accounting reference ledger is assigned to a
consolidation ledger. The reference ledger specifies the source ledger of the universal journal on the FI
accounting side. The integrated values are taken from the reference ledger.

SAP delivers ledger Y1 with the currency EUR and Y2 with the currency USD.

Settings

The following settings should be considered in the context of consolidation ledger:

1. A special version
Ledger does not have any status control in Data Monitor or Consolidation Monitor, which means processes
cannot be tracked or controlled based on ledger. Instead, a dedicated version is required. As a general
recommendation, you should create at least one version for each consolidation ledger to control the
process for this ledger, such as its group currency and valuation.
2. Ledger attribute in the consolidation group master data

Group Reporting (FIN-CS)

74 PUBLIC Group Reporting
 The ledger attribute of a consolidation group is dependent on the version (Ledger special version). You
should maintain the same ledger for all consolidation groups you want to process in the same version.
3. Sender Group Currency attribute in the consolidation unit master data
For consolidation units with the data transfer method Read from Universal Document, you can assign a
source key figure for the group currency if you wish to integrate group currency values from FI accounting.
This assignment is also ledger-dependent.

Procedure

You can make the assignment by following the steps below:

1. Assign a Ledger special version to the relevant consolidation version.

2. Under the context of a relevant consolidation version, define a consolidation ledger and assign it with a
currency and reference ledger.

 Note

When creating your own ledgers, make sure to use the prefix C to follow the naming convention.

3. In the consolidation group master data, under the context of the same consolidation version, assign the
ledger you defined in step 2 to the relevant consolidation groups.
4. In the consolidation unit master data, choose Go to Fiscal Year Variant to assign the Sender Group
Currency (and the fiscal year variant) to the ledger. By doing so, the group currency data in the universal
journal can be transferred.

Note that later on, in any apps or reports such as the Set Global Parameters app, where a version, consolidation
group currency, and ledger are required, you need to enter the parameters consistently according to the
settings above. Otherwise, some of the data listings might display meaningless results.

The following graphic illustrates the process:

Group Reporting (FIN-CS)

Group Reporting PUBLIC 75
Related Information

Consolidation Groups - Create and Change [page 30]

Consolidation Units - Create and Change [page 22]

Group Reporting (FIN-CS)

76 PUBLIC Group Reporting
1.2.2.8 Document Types and Posting Levels

Document type identifies the type and source of data, for example, reported data is stored on different
document types than elimination data. Document types can be used in various consolidation settings, tasks,
and reports.

Document types have various attributes assigned, including data sources (manual or automatic posting, file
upload, or API), posting levels, deferred income tax handling, automatic reversal, and currencies to be used in
posting. SAP Best Practices pre-delivers the following document types:

Deferred Tax Automatic Re­

Document Currency/ Balance Check (Debit/Credit) versal in Next
Source of Data Type ID Description Quantity Applied Relevant Period

Flexible Upload 00 Upload re­ Local Currency No No No

(LC)/Group
ported data
Currency
(00)
(GC)/TC/Quan­
tity

0B Consolidation LC/GC/TC/ No No No

of investment Quantity
control data
(00)

API: 07 External re­ LC/GC/TC/ No No No

Quantity
Reported ported data us­
Financial ing API (00)
Data for 08 External plan LC/GC/TC/ No No No
Group data (0C) Quantity
Reporting
– Bulk
Import and
Update

SAP Group 03 Manual input of LC/GC/TC/ No No No

Quantity
Reporting Data reported data
Collection App (00)

04 Manual correc­ LC/GC/TC/ No No No

Quantity
tion of universal
journal (0C)

Manual Journal 01 Manual correc­ LC/GC/TC/ Yes No No

Quantity
Entry tion of universal
journal (0C)

02 Manual correc­ LC/TC/Quan­ Yes No Yes (but not re­

tity versed into next
tion of reported
fiscal year)
data (01)

Group Reporting (FIN-CS)

Group Reporting PUBLIC 77
 Deferred Tax Automatic Re­
Document Currency/ Balance Check (Debit/Credit) versal in Next
Source of Data Type ID Description Quantity Applied Relevant Period

11 Manual stand­ LC/TC Yes Yes No

ardizing, defer­
red tax (10)

12 Manual stand­ LC/TC Yes Yes Yes

ardizing, defer­
red tax, auto­
matic reversal
(10)

13
Manual stand­ LC/TC Yes No No

ardizing (10)

14 Manual stand­ LC Yes Yes Yes

ardizing, auto­
matic reversal
(10)

16 Manual stand­ LC/GC Yes Yes No

ardizing, defer­
red tax (10)

17 Manual stand­ LC/GC Yes Yes Yes

ardizing, defer­
red tax, auto­
matic reversal
(10)

18 Manual stand­ LC/GC/TC Yes No No

ardizing (10)

19 Manual stand­ LC/GC Yes No Yes

ardizing, auto­
matic reversal
(10)

1E Manual equity LC/TC Yes No No

pick-up posting
(10)

1U Revoke equity LC/TC Yes No No

pick-up posting
(10)

Group Reporting (FIN-CS)

78 PUBLIC Group Reporting
 Deferred Tax Automatic Re­
Document Currency/ Balance Check (Debit/Credit) versal in Next
Source of Data Type ID Description Quantity Applied Relevant Period

21 Manual elimina­ GC - No Yes

tion correction
for interunit
payables and
receivables
(20)

22 Manual elimina­ GC/TC - No No

tion correction
for interunit
payables and
receivables
(20)

31 Manual consoli­ GC - No Yes (but not re­

versed into next
dation adjust­
fiscal year)
ments (30)

32 Manual consoli­ GC - No No

dation adjust­
ments (30)

33 Consolidation GC - No No

of investment
manual adjust­
ment, no rever­
sal (30)

39 Group shares Quantity No No No

(30)

Automatic 05 Annual net in­ LC/GC/TC No No No

Posting
come calcula­
tion (00)

06 Rounding in LC/GC/TC No No No

currency trans­
lation (00)

0Z Preparation for LC/GC/TC Yes No No

consolidation
group changes
(02)

1A Automatic LC Yes Yes Yes

standardizing
(10)

Group Reporting (FIN-CS)

Group Reporting PUBLIC 79
 Deferred Tax Automatic Re­
Document Currency/ Balance Check (Debit/Credit) versal in Next
Source of Data Type ID Description Quantity Applied Relevant Period

1B Automatic LC Yes No Yes

standardizing
(10)

1C Automatic GC Yes No No

standardizing
(10)

1O Automatic LC Yes Yes No

standardizing
(10)

1P Automatic GC Yes Yes No

standardizing
(10)

1Z Preparation for LC/GC/TC Yes No No

consolidation
group changes
(12)

2E Interunit elimi­ GC Yes No Yes (but not re­

versed into next
nation of sales
fiscal year)
(20)

2F Interunit elimi­ GC Yes No Yes (but not re­

versed into next
nation of other
fiscal year)
income/
expenses (20)

2G Interunit elimi­ GC Yes No No

nation of bal­
ance sheet (20)

2H Interunit elimi­ GC Yes No Yes (but not re­

versed into next
nation of divi­
fiscal year)
dends (20)

2I Interunit elimi­ GC Yes No No

nation for ICMR
(20)

2J Interunit elimi­ GC Yes No Yes

nation for IPI
(20)

2O Auto Reclassifi- GC Yes No Yes (but not re­

cation (20) versed into next
fiscal year)

Group Reporting (FIN-CS)

80 PUBLIC Group Reporting
 Deferred Tax Automatic Re­
Document Currency/ Balance Check (Debit/Credit) versal in Next
Source of Data Type ID Description Quantity Applied Relevant Period

2P Auto Reclassifi- GC Yes No Yes (but not re­

cation (20) versed into next
fiscal year)

2Z Preparation for LC/GC/TC - No No

consolidation
group changes
(22)

3A Investments/ GC Yes No No

equity elimina­
tion (30)

3B Consolidation GC Yes No No

of investment
automatic post­
ing (30)

3Z Total divestiture GC Yes No No

(30)

30 Auto Reclassifi- GC Yes No No

cation (30)

34 Auto Reclassifi- GC - No Yes

cation (30)

38 Group shares Quantity No No No

(30)

Read from Uni­ 0F Realtime up­ Transaction Yes No No

Currency/LC/G
versal Journal date from Ac­
C/Quantity
counting
(Blank)

Manual Data 0A Consolidation LC/GC/TC/ No No No

Collection of investment Quantity
control data
(00)

0C Mapping from LC/GC/TC/ No No No

import (00)
Quantity

0D Mapping from LC/GC/TC/ No No No

Accounting Quantity
(00)

Group Reporting (FIN-CS)

Group Reporting PUBLIC 81
 Deferred Tax Automatic Re­
Document Currency/ Balance Check (Debit/Credit) versal in Next
Source of Data Type ID Description Quantity Applied Relevant Period

0G Consolidation LC/GC/TC/ No No No
of investment Quantity
control data
(00)

 Note

The numbers in parenthesis denote the posting level for each document type. Posting levels enable you to
distinguish posting entry types and select data accordingly. Posting levels are predefined by SAP as follows:

• Local close, group-independent, and with reporting level CO (Company)

• 00: Reported data of individual consolidation units
• 01: Adjustments to reported data
• 0C: Reported data with deactivated checks
• 10: Standardizing entries which adjust local reported data to perspective of group close, for
example, adapting to financial statement items in the consolidation chart of accounts. This is
usually done by manual postings or by reclassifications.
• Pairwise eliminations, group-independent, and with reporting level PA (Pair)
• 20: Two-sided elimination entries for consolidation unit pairs (reporting unit and partner unit),
which are executed by reclassification tasks.
• Group-dependent eliminations and with reporting level GR (Group)
• 30: Consolidation entries that represent elimination postings that are explicitly dependent on
consolidation groups, for example, consolidation of investments.
• 02, 12, and 22: Represents adjustments made to reported data, standardized data, and two-sided
eliminations respectively in order to accommodate the consolidation group change, for example,
when a consolidation unit comes into a consolidation group or divests from a consolidation group
during the year.

 Note

Document types with this posting level should not use the automatic reversal option.

Defining your own posting levels is not supported in the current release.

 Note

When the document types are defined with auto reversal in the subsequent year, the reversal documents
are created during balance carryforward.

Procedure

To create your own document types and define their attributes, go to Customizing for SAP S/4HANA for Group
Reporting under Master Data Define Document Types .

Group Reporting (FIN-CS)

82 PUBLIC Group Reporting
Usage

Assign Document Types to Monitor Tasks

The relevant document types created for manual or automatic postings need to be assigned to various tasks in
Data Monitor and Consolidation Monitor.

 Note

SAP-delivered document types have been assigned to the respective monitor tasks.

Filter by Document Type

Document type can be used as a filter criterion in defining selections or reporting rules and in displaying
reports.

1.2.2.9 Selections

A selection groups a range of consolidation master data, typically the financial statement (FS) items, by using
various filter criteria. The defined selections can then be reused in consolidation-related settings, such as
validation rules, reclassification methods, currency translation (CT) methods, and breakdown categories.

Usage

Validation Rules
When defining data validation rules, you can use selections to restrict the dataset that the rule is applicable to.
For more information, see Define Validation Rules [page 99].

Reclassification Methods
When defining reclassification methods using the Customizing for SAP S/4HANA for Group Reporting under
Reclassification Define Reclassification Methods , selections can be used in the following settings:

• Selection for Trigger: The selection that triggers reclassification from the source account assignment to the
destination account assignment.
• Selection for Percentage: The selection that the system uses when selecting transaction data for
determining the percentage for reclassification. If you assign a selection for the Trigger and the Percentage
tab, both selections must use the same fields. For example, if the trigger selection includes the Document
Type field, the percentage selection must also include the Document Type field. An exception to this is
when a field is not needed to select data in one of the two selections. For example, in the Selection for
Percentage, you use the BaseUnit field, but in the Selection for Trigger, you don't need to select data with
BaseUnit. You then don't need to include theBaseUnit field in the Selection for Trigger.

CT Methods

When defining CT methods using the Customizing for SAP S/4HANA for Group Reporting under Currency
Translation for Consolidation Define Currency Translation Methods , on the method entry level, you can

Group Reporting (FIN-CS)

Group Reporting PUBLIC 83
choose from the Selection list a selection that represents a certain combination of FS items and subitems you
want to apply the following CT settings to:

• Exchange Rate Indicator: Determines the exchange rate to be used in CT, either monthly average rate (AVG)
or monthly closing rate (CLO).
• Translation Key: Controls whether cumulative values are translated at the rate for current period or
periodic values are translated at the rates for their respective periods.
• How translation and rounding differences are posted.

Breakdown Categories
When defining breakdown categories using the Customizing for SAP S/4HANA for Group Reporting under
Master Data Define Breakdown Categories , selections can be used to group a range of subitems or
partner units in the Max. Selection.

 Example

The selection S-BC-TT-02 contains only the standard subitems for transaction types for transferred
assets. You can set this selection as the maximum selection for a breakdown category, so that the FS items
assigned with this breakdown category will not exceed the range of the allowed subitems.

Related Information

Define Validation Rules [page 99]

Consolidation of Investments (Rule-Based) [page 387]

1.2.2.9.1 Define Selections

With this app, you define selections that consist of one or more filters for restricting the data range for relevant
master data fields, for example, financial statement (FS) items, subitems, document types, and posting levels.

 Note

In the prior release, selections were maintained using the Customizing activity Define Selections. Starting
from SAP S/4HANA 1909, you can define selections using the Define Selections Fiori app with enhanced
functionalities and more user-friendly interfaces. All selections you defined in prior releases have been
migrated to this app during your system upgrade.

Group Reporting (FIN-CS)

84 PUBLIC Group Reporting
Key Features

This app provides the following key features:

Create Selection

When creating selections, you first enter a selection ID and a short description, and then set the filter fields in
the Selection Expression section as follows:

1. In the Field column, select a master data type whose values you want to restrict. Depending on the master
data type you select, value range, hierarchy node, or attribute can be used as a criterion.
2. In the Operator column, first select Include or Exclude, then a comparison operator such as Equal to
or Greater than.
3. In the Value column, specify a value range, an attribute value or a hierarchy node depending on your choice
in step 1.

Important Considerations

• Using multiple filters for a same field: Multiple filters for a same field have an OR logic between each
other, provided they all use the same Include or Exclude operator. However, if both Include and
Exclude operators are used in different filters for the same field, the AND logic is applied. For example, the
following selection expression restricts to the dataset whose document type ID is either within the scope of
00~1Z or equal to 2H, but excluding 0F:

Field Operator Value

ConsolidationDocumentType Incl.Between 00 And 1Z

ConsolidationDocumentType Incl.Equal to 2H

ConsolidationDocumentType Excl.Equal to 0F

The logic is shown more clearly if you choose the Selection Condition Details button to convert the filter
conditions to SQL WHERE clauses:

 Sample Code

WHERE ((CONSOLIDATIONDOCUMENTTYPE BETWEEN '00' AND '1Z'

OR CONSOLIDATIONDOCUMENTTYPE = '2H')
AND NOT (CONSOLIDATIONDOCUMENTTYPE = '0F'))

This logic also applies if for a same field, you define filters using both value range and hierarchy node (and
attribute for some fields such as FinancialStementmentItem). For example, the following selection
expression restricts to the dataset whose consolidation unit ID is either under the unit hierarchy REGION/
ASIA or equal to 1000, but not within the scope 2010~2200:

Field Operator Value

ConsolidationUnit.Hierarchy Incl.Equal to REGION/ASIA

Node

ConsolidationUnit Incl.Equal to 1000

Group Reporting (FIN-CS)

Group Reporting PUBLIC 85
 Field Operator Value

ConsolidationUnit Excl.Between 2010 And 2200

• Using filters for different fields: Filters for different fields have an AND logic between each other. For
example, the following selection expression restricts to the dataset that meets the both requirements:
partner unit ID falls within the scope of 0~ZZZZZZ and subitem ID within 901~998:

Field Operator Value

PartnerConsolidationUnit Incl.Between 0 And ZZZZZZ

Subitem Incl.Between 901 And 998

• Using hierarchy node: For the master data types that have hierarchies enabled and maintained, you can
use Hierarchy Node to restrict their values.
Some hierarchies, for example those for consolidation unit, profit center, and segment, have time
dependency, meaning they are valid within the periods you specify in the Manage Global Hierarchies app.
When defining a selection using Hierarchy Node for these master data types, you additionally need to
specify a Valid From/To timeframe so that the system retrieves the corresponding hierarchy nodes.
Note that when using the selection at run time, for example, when executing validation, reclassification, or
currency translation, the selected hierarchy node selects master data in the hierarchy that is valid for the
execution period/year.
• Using superordinate field: The following fields have superordinate fields:

Field Superordinate Field

FS Item Consolidation Chart of Accounts (COA)

General Ledger (G/L) Account Chart of Accounts

Cost Center/Partner Cost Center Controlling Area

Profit Center/Partner Profit Center Controlling Area

When defining filters using Hierarchy Node for a field that has a superordinate field, you need to specify the
value for the superordinate field. However, the superordinate field value doesn't act as an additional filter
criterion unless you explicitly add a filter row using the superordinate field in Selection Expression.
For example, if you specify a hierarchy node for FS item by using FinancialStatementItem Hierarchy
Node , you are prompted to choose an FS item hierarchy node from a consolidation COA. If you choose
the hierarchy Y1/BS in Consolidation COA/FS Item Hierarchy and then the node TAC000 (Current assets)
underneath Y1/BS, the consolidation COA Y1 merely acts as a selection criterion for locating the right
hierarchy node, but does not restrict the data for the whole selection expression. That is, the following
selection expression doesn't restrict FS items to those only belong to consolidation COA Y1:

Group Reporting (FIN-CS)

86 PUBLIC Group Reporting
 However, by explicitly adding a filter row using the ConsolidationChartOfAccounts superordinate field and
the exact same consolidation COA value Y1, you restrict to the FS items that only belong to Y1.

• Using operator Between: Numeric and alphanumeric value ranges need to be defined in separate filter
rows if you use the Between. For example, to include all 6-character FS items that start with 1, you need to
define the following two filter rows:
• FinancialStatementItem Between 100000 And 199999
• FinancialStatementItem Between 10000A And 1ZZZZZ
Or you can simply use the operator Like, that is, FinancialStatementItem Like 1*.
• Custom fields supported: When defining selections, you can also include custom fields that are created by
using the Custom Fields and Logic app. The selections defined with custom fields are supported in
reclassification and data validation settings and tasks. For more information about extensibility in Group
Reporting, see Custom Field Extensibility [page 559].

Edit or Copy Selection

You can make changes to existing selections or you can copy an existing selection to create a similar one with a
new selection ID.

Activate or Deactivate Selection

After a selection is created, you can choose to save the selection as a draft or an active version. For an active
selection, you can choose to deactivate it as long as it's not being used in any configuration or settings, such as
validation rules, breakdown categories, currency translation methods, and reclassification methods.

A selection can have one of the following statuses:

• Draft: The selection is saved as a draft version. It cannot be used in any configuration or settings, and can
be deleted.
• Active: The selection is saved as an active version. It can be used in any relevant configuration and settings.
Active selections cannot be deleted.
• Inactive: The selection was active and is now deactivated. Note that the selections that have been used in
any configuration or settings cannot be set to inactive.

You can also choose Mass Activation to schedule background jobs to activate your selections in bulk
immediately or at a later point in time.

Show Value List

After editing a selection expression, you can view the filtered values by choosing Show Value List.

The value list displays the fields and their values, such as FS items, that meet the criteria you specified for the
current selection. When the Show Details checkbox is selected, values are listed under Include and Exclude
sections respectively by each master data type. When the checkbox is deselected, only the values that meet
the defined filter conditions for each field are listed.

 Note

If a selection contains filters for hierarchy-type fields and the relevant hierarchies are time-dependent
(such as consolidation unit hierarchy), you additionally need to specify a validity date so that the system
retrieves the valid hierarchies.

Group Reporting (FIN-CS)

Group Reporting PUBLIC 87
Show Where-Used List
For an active selection, you can choose Show Where-Used List in display mode. The list displays the IDs and
descriptions of the currency translation methods, reclassification methods, validation rules, and breakdown
categories that use the selection.

 Note

This app contains Web Assistant documentation for key fields and concepts. To display the documentation
while working in the app, press F1 or click the question mark displayed in the app header.

Supported Device Types

• Desktop
• Tablet
• Smartphone

1.2.2.10 Consolidation Master Data Fields

In addition to the master data described in previous sections, there are additional master data types that are
maintained for consolidation use only, such as business area, segment, profit center, and customer group.
These master data are sometimes referred to as Additional Characteristics.

The master data used in SAP S/4HANA Finance for group reporting uses accounting and group reporting
master data values. Master data values for accounting can automatically be used in group reporting, if
integrated with financial accounting. Master data values that do not exist in accounting, because certain parts
of the data are not reflected in SAP S/4HANA, can be maintained as additional master data values in group
reporting. If you maintain the master data values in group reporting instead of accounting, you don’t have to
specify detailed settings for accounting.

1.2.2.10.1 Define Master Data for Consolidation Fields

With this app, you can define additional master data for use in consolidation, such as segment, profit center,
and customer group as well as view the master data for these fields that are available from accounting. This
allows you to support the consolidation process and produce more insightful analysis reports.

Prerequisite

You have defined the master data fields to be used in consolidation by using the configuration activity Define
Consolidation Master Data Fields.

Group Reporting (FIN-CS)

88 PUBLIC Group Reporting
Key Features

• Create individual master data for consolidation-specific fields

• Change or delete existing consolidation master data
• Navigate to the Manage Global Hierarchies app to define hierarchies for master data types that have
enabled hierarchies

 Note

The links to the Manage Global Hierarchies app are context-sensitive. This means that when you click on a
link for a certain master data type, you're directed to a page in the Manage Global Hierarchies app that's
already filtered for the corresponding master data type in consolidation. For example, if you click the link for
the master data type Functional Area, then the resulting page in Manage Global Hierarchies only lists the
hierarchies specific to Consolidation Functional Area. Also, if you create a new hierarchy from this page, the
only available hierarchy type to select is Consolidation Functional Area.

These links only appear for master data types for which you've selected Enable Hierarchy in the
configuration activity Define Consolidation Master Data Fields.

The process described above is depicted in the following figure:

More Information

• The SAP Fiori apps reference library has details about the content necessary for giving users access to an
app on the SAP Fiori launchpad. The SAP Fiori apps reference library is available here: https://
fioriappslibrary.hana.ondemand.com
To see this app’s Fiori content, search for the app. Then select SAP S/4HANA as the product. On the
Implementation Information tab, select the correct release. The details are in the Configuration section.

Group Reporting (FIN-CS)

Group Reporting PUBLIC 89
Supported Device Types

• Desktop
• Tablet
• Smartphone

1.2.2.10.2 Import Consolidation Master Data

With this app you can import consolidation-related master data entries into the consolidation system. You can
download a template file or a file with existing master data, enter or change the master data, and upload the
completed file back to the app. You can then import the validated master data into the database.

The following master data types are available in this app:

• Consolidation Group Structure: You can upload and download assignments of consolidation units to
consolidation groups, including consolidation group specific settings of these assignments, such as
consolidation method, fiscal year and period of first consolidation, and fiscal year and period of divestiture.
This master data is alternatively maintained in the Manage Group Structure apps.
• Consolidation Unit: You can upload and download consolidation unit master data that are alternatively
maintained in the respective master data app.

 Note

If your system was migrated from the old to the new reporting logic,
• you upload and download old consolidation unit master data by selecting a fiscal year in your
global parameters that is before the from year of the new reporting logic. This upload can only be
used for fiscal years before the from year of the new reporting logic.
• you upload and download new consolidation unit master data by selecting a fiscal year in your
global parameters that is later than or equal to the from year of the new reporting logic. This
upload can be used for any fiscal year.

• Financial Statement (FS) Items: You can upload and download financial statement items (FS) including all
their master data attributes that are alternatively maintained in the Define FS Items app.

 Note

The consolidation group structure import function is only available with the New Group Reporting Logic
activated in the Customizing for SAP S/4HANA for Group Reporting Check Global System Settings. This
logic is activated by default when working with the SAP S/4HANA 1909 release or later releases. If you are
working with a release earlier than 1909, it is possible to activate the new group reporting logic. Please
create an incident with the FIN-CS-COR component to activate the new reporting logic.

To import other master data types, such as account number, chart of accounts, cost center, functional
area, profit center, segment for segmental reporting, and transaction type, use the Import Master Data for
Consolidation Fields [page 93] app.

In the settings, you can add or delete columns to and from the table. The changes are not saved automatically.
When you open the app in a new session, the standard view is displayed. If you want to keep the changed

Group Reporting (FIN-CS)

90 PUBLIC Group Reporting
columns, you have to save the layout as a new view. To do so, choose the dropdown list for your views and
select Save or Save As.

The following figure displays the process of importing master data:

Procedure

1. To import consolidation master data, you need to upload a source file. You can download a file template for
the master data type you want to import. Choose Action Download Template .
You can also download a file with existing master data. To do so, choose Action Download Master
Data . Enter values for all mandatory filters and use optional filters if required. Then choose Download.

 Note

FS item selection attribute and target attribute value assignments are time- and version-dependent.
The Consolidation Version and Effective Fiscal Year and Period filters are added to the download option
for financial statement master data types. The uploaded time- and version-dependent attributes are
then loaded into a single FS item attribute version and are valid as-of the selected fiscal year and
period. For more information, see Time- and Version-Dependency [page 45].

2. Fill out the source file or make changes to the existing master data in the file.
3. Upload the completed file to the app.

 Note

For upload errors, see the Status Detail column. To correct upload errors, you can download the master
data with the status details. That way, you can see the cause of the errors and change the data
accordingly. After you correct the errors, upload the file again.

4. Choose Check All to verify all the uploaded entries from the file. Alternatively, you can also select individual
rows and choose Check Selected to verify only the selection of entries. Rows with the status To Be Checked
have not been checked yet.

Group Reporting (FIN-CS)

Group Reporting PUBLIC 91
  Note

Check All checks all entries uploaded from the file, even if they're not visible on the UI.

If you've uploaded a large quantity of entries, such as anything over 1,000, the UI may only show the
first few rows of entries until you scroll down. Only once you scroll to the bottom, more entries will
appear. However, Check All checks all uploaded entries, including ones not yet appearing on the UI.

5. For check errors or warnings, see the Status Detail column. Rows containing errors cannot be imported.
Change the data accordingly and upload and check again. Rows containing warnings can be imported.

 Note

For Consolidation Group Structure, conflicting entries in the database are deleted if the rows contain
warnings.

6. Finally, choose Import All to import the data of all entries into the master data tables. Alternatively, you can
select individual rows and choose Import Selected to import only the selected entries.
Both Import All and Import Selected can be executed without previously checking entries with Check All or
Check Selected. This is because the import also checks the entries to be imported and only imports entries
which pass this check successfully. Entries that result in check errors can't be imported and are set to
status Checked with Errors immediately. Entries which result in check warnings are set to status Checked
with Warnings but can be imported upon special request in the import pop-up. They are then set to status
Imported.

Status overview:

• To Be Checked: Data is uploaded but not checked. Data can be checked or imported directly.
• Upload Errors: Data is not uploaded, because, for example, the entry format is incorrect or the maximum
field length is exceeded. Data cannot be checked or imported but must be adjusted in the source file.
• Checked Successfully: Only guarantees that the status is technically correct and consistent. It does not
check consistency problems with existing consolidation master data.
• Checked with Warnings: Check the status details and adjust if necessary. If you want, you can import the
data ignoring the warning.
• Checked with Errors: Check the status details for the reason for the errors. The status can have various
reasons. Before you check the data again or import the data, the error must be resolved.

Group Reporting (FIN-CS)

92 PUBLIC Group Reporting
 • Imported: Data is imported from the staging area into the final master data tables.

You can add or delete filters to and from the filter bar. Some filters are set by default. The filter changes are not
saved automatically. When you open the app in a new session, the default filters are displayed. If you want to
keep the changed filter options, you have to save the layout as a new view. To do so, choose the dropdown list
for your views and select Save or Save As.

To download only certain master data records, for example, only records with status Checked with Errors,
select the respective filter, select the select all checkbox, and download the file.

 Note

This app contains Web Assistant documentation for key fields and concepts. To display the documentation
while working in the app, press F1 or click the question mark displayed in the app header.

Supported Device Types

• Desktop
• Tablet
• Smartphone

1.2.2.10.3 Import Master Data for Consolidation Fields

With this app you can import a number of consolidation-related master data entries into the consolidation
system all at once. You download a template file that contains a list of available master data types, enter the
master data, and upload the completed file back to the app. You can then import the verified master data into
the database.

The master data types marked as Enable Master Data in Customizing for SAP S/4HANA for Group Reporting
under Master Data Define Consolidation Master Data Fields are available for importing their data in this
app, for example, cost center, controlling area.

 Note

These master data types are sometimes referred to as Additional Characteristics. The master data
maintained for them are for consolidation use only.

The following master data types are available for importing their data in this app:

• Financial statement (FS) items

• FS item mappings that are used to match FS items with general ledger accounts
• The master data types marked as Use as Master Data in the Customizing activity Define Consolidation
Master Data Fields, for example, cost center, controlling area.

 Note

These master data types are sometimes referred to as Additional Characteristics. The master data
maintained for them are for consolidation use only.

Group Reporting (FIN-CS)

Group Reporting PUBLIC 93
Procedure

Perform the following steps to upload master data:

1. In the app, download a template for your selected master data type.

 Note

When downloading a template, if you choose the With Existing Master Data option, a complete master
data list is exported. You can always export the existing master data in this way.

2. In the downloaded file, select the master data type from the drop-down list of the Master Data Type ID
column.
3. Add a new master data ID, its superordinate field value if necessary, and the master data description (or
change the existing ones if you chose the With Existing Master Data option). Note that whether a
superordinate field value is required depends on your settings in the Customizing activity.

 Example

You want to add a cost center PROD0006 under controlling area CN02.

1. Select Cost Center as the master data type.

2. Enter PROD0006 as the Master Data ID and CN02 as the Superordinate Field Value. Note that
controlling area CN02 must exist in the system.
3. Optionally, enter a description for the master data, for example, Plant 0006.

4. Upload the completed file to the app.

5. Choose Check All to verify all the uploaded entries from the file. Alternatively, you can also select individual
rows and choose Check Selected to verify only the selection of entries.

 Note

Check All checks all entries uploaded from the file, even if they're not visible on the UI.

If you've uploaded a large quantity of entries, such as anything over 1,000, the UI may only show the
first few rows of entries until you scroll down. Only once you scroll to the bottom, more entries will
appear. However, Check All checks all uploaded entries, including ones not yet appearing on the UI.

6. In case of errors, choose Show Log to see error details and correct the errors directly in the app.
7. Finally, choose Import All to import the data of all entries into the master data tables. Alternatively, you can
select individual rows and choose Import Selected to import only the selected entries.

 Note

Both Import All and Import Selected can be executed without previously checking entries with Check All or
Check Selected. This is because the import also checks the entries to be imported and only imports entries
which pass this check successfully. Entries that don't pass this check are set to the status Import Failed.

 Note

Check All and Import All can securely check and import up to 100,000 entries. However, checking and
importing even more entries may still be possible with these options, although with an increased waiting
time.

Group Reporting (FIN-CS)

94 PUBLIC Group Reporting
  Note

This app contains Web Assistant documentation for key fields and concepts. To display the documentation
while working in the app, press F1 or click the question mark displayed in the app header.

More Information

• The SAP Fiori apps reference library has details about the content necessary for giving users access to an
app on the SAP Fiori launchpad. The SAP Fiori apps reference library is available here: https://
fioriappslibrary.hana.ondemand.com
To see this app’s Fiori content, search for the app. Then select SAP S/4HANA as the product. On the
Implementation Information tab, select the correct release. The details are in the Configuration section.

Supported Device Types

• Desktop
• Tablet
• Smartphone

1.2.2.10.4 Define Hierarchies

For master data types that have hierarchy enabled, you can edit their hierarchies with the Manage Global
Hierarchies app. The hierarchies determine the layout of respective reports.

Prerequisites

• You have set the relevant hierarchical master data types to Enable Hierarchy in Customizing for SAP S/
4HANA for Group Reporting under Master Data Define Consolidation Master Data Fields , such as for
segment and profit center. These master data types are therefore listed as available hierarchy types in the
Manage Global Hierarchies app, with the prefix Consolidation, for example Consolidation Segment and
Consolidation Profit Center.
• You have maintained the master data for the master data types you want to define hierarchies in the Define
Master Data for Consolidation Fields [page 88] app.

Change Hierarchies

If you want to change the hierarchical relationship of any master data type, you can proceed as follows:

Group Reporting (FIN-CS)

Group Reporting PUBLIC 95
1. In the app, select the relevant master data type in the Type field.
2. Select an existing hierarchy in the Hierarchy ID field. Choose Go.
3. Choose the hierarchy from the result list to edit it in the detail screen.
4. Choose Edit.
5. In the header area, you can change its effective period or add remarks if necessary.
6. Expand the hierarchy to the relevant node level and perform any following steps as necessary:
• Import a node: Choose Import Nodes from the More menu ( ) to import a node and its contained
subnodes and master data entries from another hierarchy.
• Add a node or a master data entry: Choose the Add icon ( ) in the last column to open the Add Node
dialog and enter the necessary information, that is, master data ID, or node ID and description.
• Change a node or master data: Choose the node or master data entry itself to open the Change Node
dialog and replace with a new master data ID, or node ID and description.
• Delete a node or master data: Choose the Delete icon ( ) to delete the master data on the respective
row or choose Delete from the More menu ( ) to delete a node and all master data entries it contains.
7. Choose Activate to apply the changes you made to the hierarchy.

 Note

Choosing Save will generate a version with In Revision status. The original active version stays
unchanged and continues being used in any relevant reporting structure.

Create Hierarchies

If you want to create a hierarchy with a new ID, you can use the copy feature as follows:

1. Open one of the existing hierarchies that resembles the most what you want to create.
2. On the detail screen, choose Copy To New Hierarchy .

 Note

You can also choose Copy To New Timeframe to create a hierarchy version with a different
effective period and the same hierarchy ID. The timeframe acts as an identifier for each hierarchy
version and they must not overlap with each other. Afterwards, you can edit the individual hierarchy
versions and activate them.

3. In the dialog, enter an hierarchy ID, description, valid-from date, and valid-to date, and choose Copy.
4. The new hierarchy is created. You can proceed editing the hierarchy as described above.
Or, you can create a hierarchy for your selected master data type from scratch by choosing Create on the
initial screen of the app and following a similar procedure described above.

Usage

The defined hierarchies can be used in the follow-on activities, such as:

• Customizing the layout of analytical reports. For more information, see Group Data Analysis [page 522]

Group Reporting (FIN-CS)

96 PUBLIC Group Reporting
 • Defining selections. For more information, see Define Selections [page 84]
• Defining validation rules. For more information, see Define Validation Rules [page 99].

Related Information

Manage Global Hierarchies

1.2.2.11 Fiscal Year Variant

The fiscal year variant (FYV) is used to define periods, such as the number of periods in a year, period texts,
and period definitions.

In Group Reporting, you use this setting to do the following:

• Translate periods into a calendar date to determine the values for a selection that is specified based on
time-dependent hierarchies.
• Translate periods into a calendar date to determine exchange rates.
• Translate periods into a calendar date to select accounting documents, with their posting dates, when you
release accounting documents.

Example K4 (in line with cal­

endar date: January – De­ Example V6 (shifted date:
Function How the FYV is used cember) July – June)

Release task and drill down Accounting documents are When you release docu­ When you release docu­
to G/L documents* selected using the range of ments for period 1, account­ ments for period 1, account­
posting dates that corre­ ing documents from January ing documents from July 1st
spond to the fiscal year/ 1st to January 31st are se­ to July 31st are selected.
period in which the task is lected.
run.

Group structure When a consolidation unit is If the FYV contains 12 normal If the FYV contains 12 normal
divested, the period of the
periods and no special peri­ periods and no special peri­
end of the assignment is de­
ods, the period of the end of ods, the period of the end of
rived from the last period of
the FYV. the assignment is period 12. the assignment is period 12.

If the FYV contains 12 normal If the FYV contains 12 normal

periods and 4 special periods periods and 4 special periods
the end of assignment period the end of assignment period
is period 16. is period 16.

Selections and consuming When the selection is defined When a selection is used in When a selection is used in
functions with a time-dependent hier­ period 1, the hierarchy valid period 1, the hierarchy valid
archy node, the hierarchy is on January 31st is used to on July 31st is used to deter­
selected using the FYV. determine the values for the mine the values for the selec­
selection. tion.

Group Reporting (FIN-CS)

Group Reporting PUBLIC 97
 Example K4 (in line with cal­
endar date: January – De­ Example V6 (shifted date:
Function How the FYV is used cember) July – June)

Intercompany Matching and Documents are selected us­ When G/L documents are When G/L documents are
Reconciliation (ICMR) ing the range of posting read for intercompany recon­ read for intercompany recon­
dates based on the FYV. ciliation, accounting docu­ ciliation, accounting docu­
ments from January 1st to ments from July 1st to July
 Note January 31st are selected. 31st are selected.

ICMR uses the FYV as­

signed to the relevant
consolidation version. If
no FSV is specified there,
ICMR cannot read data
from ACDOCA and it
causes missing data.

Currency Translation* Exchange rates are selected When you run the currency When you run the currency
according to the validity date translation task in period 1, translation task in period 1,
that corresponds to the pe­ the exchange rate that is the exchange rate that is
riod/year of execution. valid on January 31st is used. valid on July 31st is used.

Group Reports In the report prompt, the In the prompts, the text for In the prompts, the text for
texts for the period in the the period displays January the period displays July for
value lists use the FYV that is for period 1. period 1.
assigned to the consolidation
version. Texts are adjusted if
you switch the selected con­
solidation version.

*These functions use the FYV that is assigned to the consolidation unit. If no FYV is assigned to the
consolidation unit, the function uses the FYV that is assigned to the consolidation version. If no FYV is selected
for the consolidation version or the consolidation unit, the system uses K4 as the FYV.

 Note

Only assign an FYV to a consolidation unit if the consolidation unit needs a different FYV than the FYV that
is assigned to the consolidation version. For example, you might want to include your financial data in the
group statement with shifted dates because your local reporting period differs from the corporate reporting
date.

1.2.3 Consolidation Settings

To make sure all consolidation-related tasks and reports work well, you need to complete some settings using
the apps and procedures described in this section.

Group Reporting (FIN-CS)

98 PUBLIC Group Reporting
1.2.3.1 Validation Settings

To run data validation, you need to make the relevant validation settings, including defining validation rules and
validation methods, and assigning validation methods to consolidation groups (CGs) and units (CUs).

To define rules and methods, you have two options:

• Set up everything in a quality system and export the tested settings to a spreadsheet via the Import/Export
Validation Settings app. Then import the settings to your production system using the same spreadsheet
and app. After being activated, the imported rules and methods are ready for validation run.
• Define them directly in your production system. It saves the effort of import and export.

Afterwards, the method assignment to CGs and CUs has to be done using the Assign Validation Methods app in
the production system.

When all validation settings are complete, you can run validation tasks in one of the following ways:

• By scheduling data validation jobs in the Schedule Jobs for Consolidation Tasks
• Through the respective validation task in Data Monitor or Consolidation Monitor
• Using the relevant Manage Data Validation Tasks as described in Data Validation [page 207].

The figure below illustrates the whole process:

1.2.3.1.1 Define Validation Rules

With this app, you define validation rules that contain the logical conditions the relevant financial data should
fulfill. The defined validation rules can be used to verify reported data, standardized data, and consolidated
data along the consolidation process.

Group Reporting (FIN-CS)

Group Reporting PUBLIC 99
Key Features

The app provides the following key features:

• Create Basic Rules [page 101]

• Create Compound Rules [page 105]
• Activate/Deactivate Rules [page 106]
• Simulate Validation [page 107]

 Note

SAP pre-delivers the validation rules that start with S in their IDs and can't be changed or deleted. These
pre-delivered rules verify data correctness according to basic financial principles, such as the net income
calculated in the P&L statement must equal the net income in the equity of the balance sheet, the total
assets must equal the sum of the total liabilities plus the sum of total equity, and the net accounting value
of lands and buildings must be greater than or equal to 0.

You can copy any of these rules to create your own rules in the customer namespace, that is, rule IDs not
starting with the prefix S.

 Note

This app contains Web Assistant documentation for key fields and concepts. To display the documentation
while working in the app, press F1 or click the question mark displayed in the app header.

Supported Device Types

• Desktop
• Tablet
• Smartphone

Information for Key Users

The SAP Fiori apps reference library has details about the content necessary for giving users access to an app
on the SAP Fiori launchpad. To see this app’s Fiori content, go to the SAP Fiori apps reference library and
search for the app. Then select the product. On the Implementation Information tab, select the correct release.
The details are in the Configuration section.

Related Information

Manage Data Validation Tasks - Reported Data [page 208]

Group Reporting (FIN-CS)

100 PUBLIC Group Reporting
1.2.3.1.1.1 Create Basic Rules
When creating a validation rule, you can choose the rule type, basic rule or compound rule. Follow the
procedure below to create a basic rule.

Enter General Information

In the General Information tab, specify the following information:

1. Specify a rule ID and a meaningful description, and optionally, a long description.

2. Group By: If necessary, specify up to 3 grouping criteria for the data to be validated by the rule. For
example, you can specify subitem, posting level, and partner unit as the 3 group-by fields. They will be
applied sequentially in the validation result display. However, the rule only validates data on the lowest
grouping level, that is, the 3rd level if there are level 1 and level 2 group-by fields.
3. Tolerance: You can specify tolerance value or tolerance percentage, or both, so that the calculated values
of left and right formulas are considered equal if their absolute difference does not exceed the tolerance.

 Tip

In a rule defined with comparison operator > (Greater Than) or < (Less Than), the tolerance should be
used with caution. This is because the left-side and right-side values of the rule expression are
considered equal (neither greater nor less) if their absolute difference is within tolerance, which may
result in an undesired failed validation result. Therefore, use > or < without setting tolerances, or use >=
(Greater Than or Equal To) or <= (Less Than or Equal To) instead.

 Note

If multiple group-by fields are specified, the tolerance is applied down to the lowest grouping level.

You can also specify tolerance currency so that later, in validation results, you can convert all the displayed
values to this currency.
4. Control level: Specify how strict the rule is, in other words, whether a failed validation result leads to an
error status for the respective validation task in monitors. Out of the three control levels (Error, Warning,
and Information), only when data fails to pass a rule with control level Error does the respective validation
task show  Task Has Errors status in the monitors.
5. Process No Data As: Specify how the validation works when no data exists for any operands in a rule
formula. Select one of the following:
• Success with Warning (or leave the field empty): The rule is passed with a Warning result regardless of
the control level of the rule. In addition, a "No data" exception shows under the Warning result.
• Failed: The rule is not passed and the validation result is Failed, Warning or Information depending on
the control level.
• Zero: All the no-data operands are treated as having the value zero. The system then applies the rule
formula to evaluate the data and return a validation result based on the control level.

 Note

The no-data setting works when all sum-type operands of the rule have no data. If only some operands
of the rule lack data, these operands are treated as having a zero value.

Group Reporting (FIN-CS)

Group Reporting PUBLIC 101
6. Comments required: Select the checkbox if comments are needed to provide further explanation for the
validation result in the Manage Data Validation Tasks app. Note that the existence of a comment is reflected
by the Commenting Status in the validation result. However, it has no effect on the validation result or
monitor status.

Build Rule Expression

In the Rule Expression tab, compose a rule expression to validate data. The expression includes left formula,
comparison operator, and right formula. Each formula is typically composed of operands and mathematical
operators (+, -, *, or /) and each operand represents a set of data you select by using filters.

Take the following steps to build a rule expression:

1. Create the left formula, starting by adding an operand. For a sum-type operand, do the following:
1. Specify an operand name in the Alias field.
2. Optionally, select a function from the f(x) list to perform a mathematical calculation for the operand
value. The following functions are available:
• ABS: Returns an absolute value with 2 decimal places.
• Sign: Returns 1 if the operand value is positive, zero (0) if the value is 0, and -1 if the value is
negative.
• Round (0): Rounds the operand value to the nearest single digit.
• Round (1): Rounds the operand value to one decimal place.
• Round (2): Rounds the operand value to two decimal places.

 Note

These functions are also applicable to the calculated values of the left or right formula.

3. In the Operand row, select Sum and one of the following YTD or periodic amount (or quantity)
measures:

Period Mode Measure Data to be validated at run time

Period Amount/Amount in Transaction Cur­ Amount or quantity of the specified

rency/Quantity period

Previous Period Amount/Amount in Transaction Cur­ Amount of the prior period

rency

Period of Previous Year Amount/Amount in Transaction Cur­ Amount of the specified period of
rency prior year

YTD Amount/Amount in Transaction Cur­ Cumulative amount from year begin­

rency ning to the specified period

YTD for Previous Period Amount/Amount in Transaction Cur­ Cumulative amount from year begin­
rency ning to prior period

Group Reporting (FIN-CS)

102 PUBLIC Group Reporting
 Period Mode Measure Data to be validated at run time

YTD for Previous Year Amount/Amount in Transaction Cur­ Cumulative amount from year begin­
rency ning to the specified period of prior
year

Opening Balance Amount/Amount in Transaction Cur­ Opening balance of the specified pe­
rency riod

 Note

If you select Amount or Quantity (instead of Amount in Transaction Currency) as the measure, the
amount currencies or the quantity measuring units are inherited from the data being validated at
run time.

4. In the Where row, use Include and Exclude filters to define the data scope for the sum operation. For
example, an operand can aggregate the amounts posted to a range of your filtered FS items.
When defining multiple Where conditions, be aware of the AND or OR logic between filters and the
considerations for defining hierarchy-type filters. For more information, see the Important
Considerations [page 85].

 Note

Instead of using the Where conditions, you can use the selections that are created using the Define
Selections [page 84] app. A selection groups a range of consolidation master data, typically the FS
items, subitems, document types, and posting levels.

For non-sum-type operands, such as Amount, Number, and Quantity, the steps above are not applicable.
These operands are constant values. Unless explicitly specified, their amount currency or measuring units
are inherited from the data being validated at run time.

2. If necessary, add an operator and create more operands by choosing Add Operand and repeating the
procedure above.
The left formula is created.
3. Select a comparison operator, such as =, >=, or <=.
4. Repeat the procedure for the right formula.
The rule expression is created.

The video below shows how to define a basic validation rule (English only):

Open this video in a new window

Set Up Reference Links (Optional)

In the Reference Links tab, you can add reference links, which can be static URL links or dynamic links that
contain variables. The links provide more contextual information of the rule, and will display on the validation
result page in Manage Data Validation Tasks so that users can drill through for more details, especially when
validation fails for a specific rule.

Group Reporting (FIN-CS)

Group Reporting PUBLIC 103
To use a dynamic link, you can add the following variables in the URL, using the pattern <Property> for any of
the following supported properties. In this way, on the result page, you can display a context-sensitive reference
link, for example, to a journal entry list with the values of your specified variables pre-populated.

Property Description Value Example

Drruuid Request ID 42f2e9af-c4ef-1ed8-9684-ef0f2f8ab5f3

ScenId Scenario ID FINCS

Ryear Fiscal Year 2020

Poper Posting Period 012

Dimen Dimension Y1

Rvers Version Y10

Unit Consolidation Unit S3006

Group Consolidation Group CG30

Ritclg Consolidation Chart of Accounts Y1

Task Task ID RPTVAL4

TaskType Task Type 01

Jobcount Job No. 10442600

Method Validation Method SZK01

RuleId Rule ID SRULE003

 Note

Property names are case-sensitive.

 Example

Dynamic link address can be http://<host>:<port>/ui?sap-client=902#ConsolidationLog-log&/

LogHeaderSet/<Jobcount>

Assign Rule to Validation Method

After creating a validation rule, you may want to assign it to a validation method, which can be assigned to
consolidation units or groups afterwards. To do so, you can choose the Define Validation Methods button to
directly navigate to the Define Validation Methods [page 107] app.

Group Reporting (FIN-CS)

104 PUBLIC Group Reporting
Related Information

Manage Data Validation Tasks - Reported Data [page 208]

1.2.3.1.1.2 Create Compound Rules

Compound rules are composed of basic rules connected by logical operators (AND, OR, and NOT). Follow the
procedure below to create a compound rule:

Enter General Information

In the General Information tab, specify the following information:

1. Specify a rule ID and a meaningful description, and optionally, a long description.

2. Control level: Specify how strict the rule is, in other words, whether a failed validation result leads to an
error status for the respective validation task in monitors. Out of the three control levels (Error, Warning,
and Information), only when data fails to pass a rule with control level Error does the respective validation
task show  Task Has Errors status in the monitors.
3. Comments required: Select the checkbox if comments are needed to provide further explanation for the
validation result in the Manage Data Validation Tasks app. Note that the existence of a comment is reflected
by the Commenting Status in the validation result. However, it has no effect on the validation result or
monitor status.

Build Rule Expression

In the Rule Expression tab, compose a logical expression, which is comprised of left formula, comparison
operator, and right formula:

• Left Formula: A string expression that consists of multiple basic rules connected with logical operators
(AND, OR, and NOT).
The logical operators work as follows:
• AND: Returns TRUE if both basic rules connected by the operator evaluate to TRUE.
• OR: Returns TRUE if any of the two basic rules connected by the operator evaluates to TRUE.
• NOT: Reverses evaluation result of the basic rule that follows the operator, for example, if the rule
evaluates to TRUE, then FALSE is returned and vice versa.

 Note

In the formula evaluation, AND and OR have the same priority and are therefore evaluated from left to
right. NOT has a higher priority. If you want to change the order of evaluation, use brackets.

• Comparison operator: Choose either equal to or not equal to.

• Right Formula: Value TRUE is auto-filled. You can't change the value to "false", instead, you reverse the
comparison operator.

The expression forms a compound condition that the relevant data is to fulfill in validation tasks.

 Example

If you require the data meets both basic rules MN001 and MN004 or meet the basic rule MN003, you can
create a compound rule that has the rule expression (MN001 AND MN004)OR MN003 = TRUE.

Group Reporting (FIN-CS)

Group Reporting PUBLIC 105
The following animated GIF (English only) shows how to create the compound rule in the example above:

Set Up Reference Links (Optional)

This part is the same as described in Create Basic Rules [page 101].

Assign Rule to Validation Method

After creating a validation rule, you may want to assign it to a validation method, which can be assigned to
consolidation units or groups afterwards. To do so, you can choose the Define Validation Methods button to
directly navigate to the Define Validation Methods [page 107] app.

1.2.3.1.1.3 Activate/Deactivate Rules

After a rule is created, you can choose to save the rule as a draft (Save) or an active version (Save and
Activate). Only active rules can be applied in data validation. You can also deactivate any active rules by
choosing Set to Inactive or activate them again by choosing Set to Active.

Therefore, a rule can have one of the following statuses:

• Draft: The rule is saved as a draft version. It cannot be used in data validation yet, and can be deleted.
• Active: The rule is saved as an active version. It can be assigned to a method for data validation. Active
rules cannot be deleted.

 Note

After activation, when you choose Edit for the rule for the first time, a draft is generated. After editing
the draft:

Group Reporting (FIN-CS)

106 PUBLIC Group Reporting
 • If you choose Save, the changes are only saved to the draft. In the rule list, the rule displays as the
Active status with a  Draft created by: <user name> link underneath. You can choose to edit the
draft again by choosing the draft link.
• If you choose Save and Activate, the draft rule changes to the Active status and overwrites the
original active version.

• Inactive: The rule was active and is now deactivated. It cannot be used in data validation even if it is
assigned to a validation method.

 Note

Any draft or inactive rules you created using Define Validation Rules can only be activated with this app. The
Schedule Mass Activation Jobs - Rules, Methods, and Selections [page 114] app can only be used to
activate rules (or methods) imported from other systems.

1.2.3.1.1.4 Simulate Validation

After editing and saving a rule, you can simulate a validation run by choosing Simulate and specifying the
following criteria:

• Global parameters such as Consolidation Chart of Accounts, Consolidation Version, and Ledger
• Validation Task Type: Enter 01 for reported data validation, 02 for standardized data validation, or 03 for
consolidated data validation.
For information about what data is included in each task type, that is, which currency types and posting
levels are included, see Manage Data Validation Tasks - Reported Data [page 208], Manage Data Validation
Tasks - Standardized Data [page 216], and Manage Data Validation Tasks - Consolidated Data [page 413].
• Fiscal Year and Posting Period: Enter the year and period for which you want to validate the data using the
current rule.
• Consolidation Unit/Group: For 01 or 02 validation tasks type, enter the ID of a consolidation unit for which
you want to validate its data. For 03, enter the ID of a consolidation group for which you want to validate its
data.

The simulation result shows whether your selected data passes or fails the current rule. For detailed
explanations of a validation result, see Check Result Details [page 210] part in the app description for Manage
Data Validation Tasks.

1.2.3.1.2 Define Validation Methods

With this app you can create or update validation methods that may contain multiple groups of validation rules.

Group Reporting (FIN-CS)

Group Reporting PUBLIC 107
Key Features

This app provides the following key features:

Create Method
You can create validation methods and assign them with multiple defined rules as follows:

• Enter the general information for a new validation method, such as an ID and a description.
1. Under the default header row Totals Validation, add one or more groups with meaningful names.
2. Select a group and assign existing validation rules to it.
3. If necessary, you can drag and drop rules to change their sequence or group assignment. The rule
sequence and grouping will determine the layout of the validation result page in the Manage Data
Validation Tasks app.

 Note

You can only add one group hierarchy level and then include rules within each group, that is, you
cannot add a group under another group.

For a step-by-step guide, see the following animated picture (English only):

 Note

SAP pre-delivers the validation methods SRD1 (Local Data Validation Method) and SCD1 (Consolidated Data
Validation Method) that contain a set of predefined rules. You can only create methods in the customer
namespace, that is method IDs not starting with the prefix S.

Edit or Copy Method

You can make changes to any existing methods or you can copy an existing method to create a similar one with
a new method ID.

Group Reporting (FIN-CS)

108 PUBLIC Group Reporting
Activate or Deactivate Method
After a method is created, you can choose to save the method as a draft or an active version. For an active
method, you can choose to deactivate it later on, so that it isn't applied in data checks, even if it is assigned to a
consolidation group or unit.

A method can have one of the following statuses:

• Draft: The method is saved as a draft version. It cannot be used in data validation yet, and can be deleted.
• Active: The method is saved as an active version. It can be assigned to a consolidation group or unit. Once
activated, a method cannot be deleted.
• Inactive: The method was active and is now deactivated. It cannot be used in data validation even if it is
assigned to a consolidation group or unit.

You can also choose Mass Activation to schedule background jobs to activate your selections in bulk
immediately or at a later point in time.

 Note

This app contains Web Assistant documentation for key fields and concepts. To display the documentation
while working in the app, press F1 or click the question mark displayed in the app header.

More Information

• The SAP Fiori apps reference library has details about the content necessary for giving users access to an
app on the SAP Fiori launchpad. The SAP Fiori apps reference library is available here: https://
fioriappslibrary.hana.ondemand.com
To see this app’s Fiori content, search for the app. Then select SAP S/4HANA as the product. On the
Implementation Information tab, select the correct release. The details are in the Configuration section.

1.2.3.1.3 Assign Validation Methods

With this app you can assign the defined validation methods to consolidation groups or units depending on
which task type you selected, reported data validation, standardized data validation, or consolidated data
validation. You can run validation tasks for your consolidation groups and units only after the method
assignment.

Key Features

This app provides the following key features:

Choose Task Type

You can choose one of the following available task types:

Group Reporting (FIN-CS)

Group Reporting PUBLIC 109
• 01: Reported Data Validation
• 02: Standardized Data Validation
• 03: Consolidated Data Validation

The method assignments for these task types are used for running validation tasks for reported data,
standardized data, and consolidated data respectively from the Data Monitor and Consolidation Monitor, or
from the Manage Data Validation Tasks app.

Assign Method
For the 01 and 02 task types, you can assign a validation method to each consolidation unit, while for the 03
task type, you can assign a validation method to each consolidation group. Use the following procedure to
assign methods to consolidation units or groups:

1. Select a consolidation version in the Version field. The method assignment is version-dependent, that is,
you can assign different methods to a same consolidation unit or group for different versions, for example,
one for actual data and one for budget data. Among all special versions of a consolidation version,
validation method assignment applies to Data Entry Version, meaning all consolidation versions with the
same special version of Data Entry share the same method assignment. For more information, see
Consolidation Versions [page 68].
2. Select a period category. The method assignment applies to all of its contained periods.

 Note

The period category 16 Periods is pre-delivered, which contains all 16 periods in a fiscal year. If
necessary, you can define additional period categories in Customizing for SAP S/4HANA for Group
Reporting under Data Collection for Consolidation Define Period Categories .

3. In each row of the assignment table, do the following:

1. In the Consolidation Units or Consolidation Groups column, select individual consolidation units or
groups or specify a range of them.
2. In the Validation Method column, select a validation method you maintained using Define Validation
Methods.
3. If you want to specify a validity period for a method-to-consolidation unit/group assignment, choose
the consolidation unit or group name. Then, in the dialog box, enter the fiscal year and period in the
Valid From Period field, following the date format in your system regional settings, for example,
002.2018 or 2018/002.
4. Save your changes.

The process described above is depicted in the following graphic:

Group Reporting (FIN-CS)

110 PUBLIC Group Reporting
  Note

The validity period setting works in this way:

• Leave Valid From empty if you want to make the method assignment valid indefinitely. This is the case
for the consolidation unit C1000 in the screenshot example above.
• If you enter a valid-from period, the assignment is only valid from that period.
• If for a same consolidation unit (or group), a second method assignment exists with a later valid-from
period, the first method assignment is valid until the period before the second valid-from period. Taking
the consolidation units from 1010 to 1409 in the screenshot above as an example, they are assigned
with the validation method VM1 from 008.2018 to 001.2019 and assigned with the validation method
VM2 from the period 002.2019 onward. However, if you run validation tasks for these units for any
period before 008.2018, you will run into the error No validation method is assigned.
• If a consolidation unit has two method assignments and the first one has no valid-from period, the first
assignment is valid until the period before the valid-from period of the second method assignment.
This is the case for the consolidation unit S3000 in the screenshot above, it has the validation method
SRD1 until 005.2018 and VM3 from 006.2018 onward.

View Assignment List

By choosing the Assignment List button, you can display the list of assigned methods for each consolidation
group or unit for the current task type. To view the method assignments for a different consolidation version,
you need to go back to the Assignment tab to switch version. And here's a graphic that highlights the main
aspects:

Group Reporting (FIN-CS)

Group Reporting PUBLIC 111
You can also export the list to a spreadsheet. The file can be first exported to the browser's file system, which
starts with Z:\, and then saved to your native file system.

 Note

When maintaining master data for consolidation groups or units using the Consolidation Groups - Create
and Change [page 30] or Consolidation Units - Create and Change [page 22] app, you can also view their
assigned validation method under Methods Validation . From there, you can also navigate to this app
by choosing the Assign Validation Methods button.

1.2.3.1.4 Import/Export Validation Settings

With this app, you can export your specified selections, validation rules, and methods to a spreadsheet, or
import any selections, rules, and methods exported from another system. This is particularly useful when you
want to export the validation settings that are defined, activated, and tested in your quality system and import
them to your production system.

Key Features

This app provides the following key features:

Export
You can export selections, validation rules, and/or methods that exist in your current system to a spreadsheet
file as follows:

1. Choose Download.
2. In the dialog box, specify which selections, validation rules, and/or validation methods are relevant for the
export. such as ID, created by, and date of creation.

Group Reporting (FIN-CS)

112 PUBLIC Group Reporting
  Note

If you select Include referenced objects, the following are exported together with their dependent
objects:
• The selections that are reused by your specified rules
• The basic rules that make up your specified compound rules
• The rules that are assigned to your specified methods.

3. Choose Download.
The file that contains your selected validation setting items is downloaded and saved to your native file
system. Keep it intact. The next logical step is to upload the file to the target system,

 Remember

Only active selections, rules and methods are included in the export. Draft or inactive ones are not
included.

Import

In the target system, you can import the downloaded selections, rules, and methods still with this app. First
choose Upload, and then select the spreadsheet file you downloaded from the source system. Make sure the
required master data exist in your target system. For example, the selections to be imported may contain
multiple financial statement (FS) items. You need to make sure the referenced FS items exist in your target
system.

The uploaded items, grouped by selections, rules, and methods, will have either of the following statuses:

• New for Import: The uploaded items don't yet exist in your current system. The next step is to import these
new items.
• Duplicated: The uploaded items have IDs identical to the existing ones in your current system. The existing
items may have Active, Draft, or Inactive status. Therefore, you need to compare the duplicates and decide
if you want to skip the uploaded items or to import them so that the existing items are overwritten.

 Note

If you choose to import the duplicated items anyway, only the draft versions of existing items are
overwritten because all the imported items have an initial status Draft. However, the subsequent Mass
Activation action can activate these imported items and overwrite the existing active rules, methods, or
selections.

You need to select explicitly the items you want to import and then choose Import. The imported items may
have either Imported or Import Failed status. For the failed items, you can check the root cause according to the
hints provided in Check Message.

Since all the imported items will initially have the status Draft in the target system, during the import, you are
asked if you want to activate them right away. If you choose not to, you can take one of the following actions
later on in the target system:

• Activate the uploaded items individually by using Define Selections [page 84], Define Validation Rules
[page 99], and Define Validation Methods [page 107], or
• Schedule mass activation jobs as described below.

Group Reporting (FIN-CS)

Group Reporting PUBLIC 113
Mass Activation
You can also choose Mass Activation to navigate to the Schedule Mass Activation Jobs - Rules, Methods, and
Selections [page 114] app, where you can schedule a background job to activate your specified selections,
rules, and methods in bulk immediately or at a later point in time.

 Note

After the import, all the items have the status Draft in the target system. To use them in the data validation
process, you must activate these items.

The process described above is depicted in the following graphic:

 Note

This app contains Web Assistant documentation for key fields and concepts. To display the documentation
while working in the app, press F1 or click the question mark displayed in the app header.

Supported Device Types

• Desktop
• Tablet
• Smartphone

1.2.3.1.5 Schedule Mass Activation Jobs - Rules, Methods,

and Selections

With this app, you can schedule jobs to activate the rules, methods, and selections imported from other
systems. To do that, you use the provided job template Mass Activation for Selections, Rules and Methods.

Group Reporting (FIN-CS)

114 PUBLIC Group Reporting
Context

Any rules, methods, selections imported using the Import/Export Validation Settings [page 112] app have an
initial status Draft. To be used in the data validation process, these items must be activated. You can activate
them either individually in their definition apps such as Define Validation Rules or by scheduling mass activation
jobs.

Key Features

This app provides the following key features:

• Create Job: You can choose New ( icon) to create a job based on the Mass Activation for Selections, Rules
and Methods job template.
• Choose Scheduling Option: You can launch an immediate job run, define a future start date and time for a
single run, or define the recurrence pattern for the jobs you want to run regularly.
• Specify Parameters: You can specify the range of selections, rules and/or methods that you want to
activate in the background job.

 Note

Only the selections, rules and methods that are imported from other systems are available in the
search help. If you leave the fields empty, all the selections, rules and methods imported to your
current system are included.

• Check Job Status: For any scheduled job, you can monitor its status (Finished or Failed) by checking the
Status column.
• Check Activation Results: When job status shows Finished, you can choose the icon ( ) in the Results
column to view which selections, rules, and methods are activated.

 Note

Any draft or inactive rules or methods you created manually in Define Validation Rules or Define
Validation Methods can only be activated with the respective definition app. Even if you include these
rules or methods in a mass activation job, you will find activation errors for these rules and methods on
the Results page.

Related Information

Import/Export Validation Settings [page 112]

Group Reporting (FIN-CS)

Group Reporting PUBLIC 115
1.2.3.2 Reporting Items and Reporting Rules

Reporting items and reporting rules allow you to create reports with flexible data selection and aggregation
along a row or column axis. You can use reporting items as an additional analytical dimension in a report.
Reporting rules allow you to define the content of these reporting items.

Overview

Reporting items are reporting characteristics that can be used as analytical dimensions in various reports,
such as statement of cash flow, statement of changes in equity, statement of comprehensive income, and
profit and loss (P&L) statement by function of expense. Reporting items are arranged into reporting item
hierarchies. These hierarchies are used in reports to display the reporting items in a hierarchical structure.

Reporting items can be used in two distinct ways. Firstly, a reporting item is technically a financial statement
(FS) item whose FS item type is REPT (Reporting Item). Because of this, you can use reporting items like any
other statistical item.

Secondly, a reporting item can be enhanced by assigning it a set of selection criteria of specific data, such as
FS items, consolidation units, document types, and subitems. The assignments of data selection criteria to
reporting items are called reporting rules. These reporting rules determine how the values for a reporting item
are derived in a report.

With the reporting rules in place, a reporting item can then be used as an analytical dimension in reports. When
you use a reporting item in a report, its values are calculated by aggregating the data from the selection criteria
defined in the reporting rules. The following graphic shows how this comes together in a report. It also shows
the relationship between an FS item, reporting item, reporting rules, and reporting item hierarchy.

 Example

Using this graphic as an example, you can create the FS item Reporting Item 1 with the FS item type REPT.
This defines the FS Item as a reporting item. You can then include Reporting Item 1 into a reporting item
hierarchy, such as X2 (Statement of Cash Flow). This allows the reporting item to be displayed in a report.
You then use reporting rules to assign Reporting Item 1 with data selection criteria, such as the range of FS
items from FS Item 1 to FS Item 5. This determines how values for Reporting Item 1 are derived in reports.

Group Reporting (FIN-CS)

116 PUBLIC Group Reporting
 With these reporting rules in place, you can use the hierarchy X2 to create a statement of cash flow and
show amounts by reporting item. In the report, the system calculates an aggregated amount for Reporting
Item 1. This amount is derived based on the selection criteria that you’ve assigned in the reporting rules. In
this case, that means the amount for Reporting Item 1 aggregates all the amounts from the range of FS
items from FS Item 1 to FS Item 5. In this way, a reporting item acts as one entity but actually represents a
set of data defined by these selection criteria in the reporting rules.

Reporting Items
Reporting items can be created in the Define FS Items [page 49] app. When you create a new FS item in the
app, select REPT (Reporting Item) for FS Item Type to define it as a reporting item.

Reporting Item Hierarchies

After the reporting items are created, they can then be arranged into reporting item hierarchies or inserted into
existing reporting item hierarchies with the Manage Global Hierarchies app. The reporting item hierarchies can
be used to define reporting rules and then displayed in reports.

SAP delivers the following reporting item hierarchies that are ready to use:

• X1: Statement of Changes in Equity

• X2: Statement of Cash Flow
• X3: Statement of Comprehensive Income
• X4: P&L by Function of Expense

 Note

Reporting item hierarchies do not have key dates that determine the start of their validity. Because of this,
they’re not time- and version-dependent.

To learn more about reporting items, see FS Item Type [page 42]. And to learn more about reporting item
hierarchies, see Define Hierarchies [page 51].

Reporting Rules and Reporting Rule Variants

Reporting rules define the selection criteria of data for a reporting item. For example, these selection criteria
can be a range of FS items, consolidation units, document types, or subitems. You can also set sign reversal
settings. A specific set of reporting rules is contained within a reporting rule variant. You create and manage
reporting rules and reporting rule variants in the Define Reporting Rules [page 118] app.

SAP delivers the reporting rule variant Y10, which contains all the rules for all the SAP-delivered reporting item
hierarchies – X1, X2, X3, and X4.

Where Are Reporting Rules Used?

Apps "With Reporting Rules"

Some apps in analytics for group reporting are duplicated to enable the use of reporting rules. The apps that
use reporting rules contain the suffix “With Reporting Rules” in the title. In these apps, the reporting items are
used as analytical dimensions, and you use the mandatory filters Reporting Item Hierarchy and Reporting Rule
Variant. Apps without the suffix “With Reporting Rules” do not use reporting items, reporting item hierarchies,
or reporting rule variants.

Group Reporting (FIN-CS)

Group Reporting PUBLIC 117
Report Rule Versions
Once your reporting rules are in place, you can assign the reporting rule variants to report rule versions using
the Assign Reporting Rules to Versions [page 131] app. These report rule versions can then be mapped to
consolidation versions with the configuration activity Define Versions. With this mapping between consolidation
versions and report rule versions, the consolidation versions are implicitly assigned with reporting rule variants.

 Note

Variants cannot be changed after you’ve assigned them to report rule versions. That means that you can’t
make any adjustments or additions to the reporting rules contained in the reporting rule variant. This
protects reports from being changed accidentally in case changes are made to the selection criteria, such
as changes to hierarchies or FS item attributes.

If you want to make changes, you must create a new reporting rule variant by copying the variant that’s
already been assigned to the report rule version. Then, you can make changes to the newly copied variant.

Related Information

Define Reporting Rules [page 118]

How to Use "Manage Global Hierarchies" in Group Reporting [page 509]
Define FS Items [page 49]
FS Item Type [page 42]
Define Hierarchies [page 51]
Assign Reporting Rules to Versions [page 131]

1.2.3.2.1 Define Reporting Rules

With this app you can define reporting rule variants by selecting reporting items and assigning each with
financial statement (FS) items and selection criteria for other data, such as consolidation unit, document type,
and subitem. The use of reporting rules enables flexible data selection and structuring of data in reports and
therefore fulfills various reporting requirements.

Before Defining Reporting Rules

If you want to create reporting rules for your own reporting items, you must create the reporting items first. You
can do this in the Define FS Items [page 49] app. When you create a new FS item in the app, select REPT
(Reporting Item) for FS Item Type to define it as a reporting item. Alternatively, SAP delivers reporting items in
the reporting item hierarchies X1, X2, X3, and X4.

Similarly, if you want to create your own reporting item hierarchies in addition to the SAP-delivered hierarchies
X1, X2, X3, and X4, use the Manage Global Hierarchies app. To learn more about creating and managing
hierarchies, see Define Hierarchies [page 51] and How to Use "Manage Global Hierarchies" in Group Reporting
[page 509].

Group Reporting (FIN-CS)

118 PUBLIC Group Reporting
  Note

Reporting item hierarchies do not have key dates that determine the start of their validity. Because of this,
they’re not time- and version-dependent.

Procedure

Create a Reporting Rule Variant

1. Enter the Reporting Rule Variant that you want to create and specify the Consolidation Chart of
Accounts (COA) and Reporting Item Hierarchy as the rule context.

 Note

Although you select a reporting item hierarchy for the rule context, you can define reporting rules in a
variant for reporting items that are not part of the selected hierarchy. As a result, when you use the
hierarchy and variant later in reports, the reporting items that are not part of the hierarchy will be
categorized separately under the node Not Assigned Reporting Item(s). This Not Assigned Reporting
Item(s) node appears at the same level as the top node of the hierarchy being used in the report. The
following simplified screenshot shows this Not Assigned Reporting Item(s) node in a report.

The following screenshot is only available in English. Interfaces may differ slightly depending on the
version of your apps or on your configuration settings.

In this example, the reporting item hierarchy being used is Demo - Reporting Item hierarchy, and the
reporting rule variant being used is 1. All reporting items in the report have rules defined in variant 1.
The reporting items that are part of the hierarchy will appear under the node Demo - Reporting Item
hierarchy. The reporting items that are not part of the hierarchy will appear under the node Not
Assigned Reporting Item(s).

2. Select Create to create a new variant. Alternatively, you can select Copy to copy all the rules of an existing
variant that you’ve selected for Reporting Rule Variant. For example, you can copy the SAP-delivered rule
variant Y10, which contains rules for the hierarchies X1, X2, X3, and X4. This way, your new variant will
already have reporting rules that you can then just adjust. If you do this, you don’t need to specify
the Reporting Item Hierarchy.
After selecting Copy, the Copy Reporting Rule ID window will appear. Here, you enter the new variant to
which you want to copy the reporting rules from the existing variant.

Group Reporting (FIN-CS)

Group Reporting PUBLIC 119
3. Enter a description for the variant in the Description field.
4. If necessary, add reporting items one by one and assign only one of the following FS item selection criteria
to each:
• A range of FS items using FS Item From and FS Item To. To assign just one FS item, you can select the
same FS item for FS Item From and FS Item To.
• FS Item Attribute Name and FS Item Attribute Value. By assigning these to a reporting item, the
reporting rules for that item become inherently time- and version-dependent. This is because FS item
attributes are time- and version-dependent.
• FS Item Hierarchy and Hierarchy Node.

 Note

The FS Item selection criteria are mandatory when defining reporting rules. The selection criteria
for other data are optional, such as subitems, document types, and consolidation units.

5. If necessary, add other selection criteria, such as for subitems, document types, and consolidation units.
6. If necessary, adjust the sign reversal settings in the Rev. Sign column. If you insert an X in this column, then
the amounts displayed in reports for the reporting item will have the opposite +/- sign than what is
typically displayed. For example, 100 will appear as -100, or -100 will appear as 100.
7. If necessary, make other changes to individual rules by changing the values in a row. You can also delete
rows.

 Note

Alternatively, you can create reporting rules in an offline CSV file and import the file so that all reporting
items contained in it are uploaded to the system in one go.

The offline CSV file should use commas as field separators, and follows the exact same order of column
headers as on the rule definition screen, that is:

FS At­
Item Item trib­ Item Doc
At­ At­ At­ ute FS Hier­ Sub­ ume Doc Re­
Re­ trib­ trib­ trib­ Valu Item arch FS item Sub­ nt ume vers
porti ute ute ute e Hier­ y Item FS Cat­ item Sub­ Type nt CU e
ng Nam Desc Valu Desc arch Nod Fro Item egor Fro item Fro Type Fro CU Sign
Item e . e . y e m To y m To m To m To (X)

Re­
port­
ing
Item
ID 1

Re­
port­
ing
Item
ID 2

Group Reporting (FIN-CS)

120 PUBLIC Group Reporting
 FS At­
Item Item trib­ Item Doc
At­ At­ At­ ute FS Hier­ Sub­ ume Doc Re­
Re­ trib­ trib­ trib­ Valu Item arch FS item Sub­ nt ume vers
porti ute ute ute e Hier­ y Item FS Cat­ item Sub­ Type nt CU e
ng Nam Desc Valu Desc arch Nod Fro Item egor Fro item Fro Type Fro CU Sign
Item e . e . y e m To y m To m To m To (X)

...

You can also choose to download the file from an existing reporting rule by choosing Export and saving
the file to CSV (Comma delimited) (*.csv) format.

In the CSV file, the following fields are mandatory:

• FS Item From, FS Item To
• FS Item Hierarchy
• Attribute Name, Attribute Value

These fields make up the three independent groups that are used to specify the FS items list. You can
specify the FS items list by selecting the range fields FS Item From and FS Item To. Alternatively, you
can specify wither the FS Item Hierarchy or Attribute Name and Attribute Value. Do not specify a
combination of these groups.

Other fields are optional, but are grouped in the following way:
• Subitem Category, Subitem From, Subitem To
• Document Type From, Document Type To
• CU From, CU To

If you make an entry in one field from a group, the other fields in the same group become mandatory.

8. Save and exit.

9. Select Replicate Reporting Rules to activate your newly created variant so that you can use it in the system.
If you don’t select Replicate Reporting Rules, then your new variant will be inactive, and you won’t be able to
use it.

Make Changes to a Reporting Rule Variant

1. Enter the Reporting Rule Variant that you want to edit and specify the Consolidation Chart of Accounts
(COA) and Reporting Item Hierarchy as the rule context.

 Note

Variants cannot be changed after you’ve assigned them to report rule versions. If you want to make
changes, you must create a new reporting rule variant by copying the variant that’s already been
assigned to the report rule version. Then, you can make changes to the newly copied variant.

2. Select Change.
3. If necessary, make changes to individual rules by changing the values in a row. You can also delete rows.
4. If necessary, add reporting items one by one and assign only one of the following FS Item selection criteria
to each:
• A range of FS items using FS Item From and FS Item To. To assign just one FS item, you can select the
same FS item for FS Item From and FS Item To.

Group Reporting (FIN-CS)

Group Reporting PUBLIC 121
 • FS Item Attribute Name and FS Item Attribute Value. By assigning these to a reporting item, the
reporting rules for that item become inherently time- and version-dependent. This is because FS item
attributes are time- and version-dependent.
• FS Item Hierarchy and Hierarchy Node.

 Note

The FS item selection criteria are mandatory when defining reporting rules. The selection criteria
for other data are optional, such as subitems, document types, and consolidation units.

5. If necessary, add other selection criteria, such as for subitems, document types, and consolidation units.
6. If necessary, adjust the sign reversal settings in the Rev. Sign column. If you insert an X in this column, then
the amounts displayed in reports for the reporting item will have the opposite +/- sign than what is
typically displayed. For example, 100 will appear as -100, or -100 will appear as 100.

 Note

Alternatively, you can create reporting rules in an offline CSV file and import the file so that all reporting
items contained in it are uploaded to the system in one go.

The offline CSV file should use commas as field separators, and follows the exact same order of column
headers as on the rule definition screen, that is:

FS At­
Item Item trib­ Item Doc
At­ At­ At­ ute FS Hier­ Sub­ ume Doc Re­
Re­ trib­ trib­ trib­ Valu Item arch FS item Sub­ nt ume vers
porti ute ute ute e Hier­ y Item FS Cat­ item Sub­ Type nt CU e
ng Nam Desc Valu Desc arch Nod Fro Item egor Fro item Fro Type Fro CU Sign
Item e . e . y e m To y m To m To m To (X)

Re­
port­
ing
Item
ID 1

Re­
port­
ing
Item
ID 2

...

You can also choose to download the file from an existing reporting rule by choosing Export and saving
the file to CSV (Comma delimited) (*.csv) format.

In the CSV file, the following fields are mandatory:

• FS Item From, FS Item To
• FS Item Hierarchy

Group Reporting (FIN-CS)

122 PUBLIC Group Reporting
 • Attribute Name, Attribute Value

These fields make up the three independent groups that are used to specify the FS items list. You can
specify the FS items list by selecting the range fields FS Item From and FS Item To. Alternatively, you
can specify wither the FS Item Hierarchy or Attribute Name and Attribute Value. Do not specify a
combination of these groups.

Other fields are optional, but are grouped in the following way:
• Subitem Category, Subitem From, Subitem To
• Document Type From, Document Type To
• CU From, CU To

If you make an entry in one field from a group, the other fields in the same group become mandatory.

7. Save and exit.

8. Select Replicate Reporting Rules to activate your changes to the variant so that you can use it in the
system. If you don’t select Replicate Reporting Rules, then your changes will be inactive, and they won’t
take effect in the variant for future use.

Maintaining Reporting Rules After Saving and Replicating

Once you save and replicate the reporting rules, they’re activated in the system only with the most up-to-date
settings at the time of saving and replicating. This means that the reporting rules won't automatically register
any changes made to relevant FS items or FS item attributes if those changes are made after saving the
reporting rule variant. So, the reporting rules need to be maintained after making changes to FS items and FS
item attributes.

To do so, after making changes to any FS items or the FS item attributes that are used in reporting rules, return
to the relevant reporting rule variant and make a separate change (even a dummy change that you can later
delete). Then, save and replicate the reporting rules again. Only then will the changes to the FS items and FS
item attributes be registered in the reporting rule variant.

Example with FS Item Attribute

You assign FS item FSI1 with the FS item attribute ATT1. Then, you define a reporting rule where you assign
reporting item RPI1 with the FS item attribute value ATT1. You then save your changes to the reporting rule
variant and replicate the reporting rules. When using the reporting rule later, amounts for FSI1 are derived,
aggregated, and displayed for RPI1, which is the anticipated behavior.

However, if you then assign a new FS item, for example FSI2, with the same attribute ATT1 after having already
defined the reporting rule based on ATT1, amounts for FSI2 aren't derived, aggregated, or displayed for RPI1.
This is because this change was made after the reporting rule variant was saved and replicated.

To remedy this, you return to the reporting rule variant in which you’ve created the original assignment
between RPI1 and ATT1. In this variant, you must make a separate change (it could be a dummy change) and
then save and replicate. Only then are amounts for FSI2 derived, aggregated, and displayed for RPI1.

Group Reporting (FIN-CS)

Group Reporting PUBLIC 123
Information for Key Users

The SAP Fiori apps reference library has details about the content necessary for giving users access to an app
on the SAP Fiori launchpad. To see this app’s Fiori content, go to the SAP Fiori apps reference library and
search for the app. Then select the product. On the Implementation Information tab, select the correct release.
The details are in the Configuration section.

Supported Device Types

• Desktop

1.2.3.2.1.1 Example: Create Reporting Rules and Use Them in

Reports

This example illustrates the end-to-end process of defining reporting rules with newly created reporting items
and then using the reporting rules in a report. For the sake of demonstration, this example specifically shows
how to use reporting rules in a statement of cash flow. Nonetheless, the process is the same for other reports,
such as statement of changes in equity, statement of comprehensive income, and P&L by function of expense.

Procedure

This process is divided into the following four major steps, each with an individual sequence of actions.

1. Create a Reporting Item

In this step, you create a new reporting item by creating a financial statement (FS) item with REPT (Reporting
Item) selected for the FS Item Type.

Procedure
1. Go to the Define FS Items [page 49] app.
2. Select Create.
3. Enter the name of the reporting item you’d like to create in the Financial Statement Item field and select a
Consolidation Chart of Accounts (COA). Then, select Create.

 Note

When you define reporting rules later, you’ll need to select a consolidation COA to establish the rule
context. You’ll only be able to define reporting rules for reporting items from that consolidation COA.

Group Reporting (FIN-CS)

124 PUBLIC Group Reporting
 So, keep in mind that the consolidation COA that you select here must be the same that you select later
when defining the reporting rules.

4. For FS Item Type in the Basic Data section, select REPT (Reporting Item). This defines the FS item as a
reporting item.
5. Make any other necessary selections for the reporting item.
6. Save and exit.

2. Insert a Reporting Item into a Reporting Item Hierarchy

In this step, you insert your newly created reporting item into an already existing reporting item hierarchy.
Since this example is all about using reporting rules in a statement of cash flow, you use the SAP-delivered
hierarchy X2 (Statement of Cash Flow) as the reporting item hierarchy.

It’s also possible to create an entirely new reporting item hierarchy from scratch. To learn more about creating
and managing hierarchies, see Define Hierarchies [page 51] and How to Use "Manage Global Hierarchies" in
Group Reporting [page 509].

Procedure
1. Go to the Manage Global Hierarchies app.
2. For the filter Type, select Consolidation Reporting Item.
3. Select Go.

 Note

The hierarchies that appear after filtering Consolidation Reporting Item for Type are all reporting item
hierarchies. As such, you can add reporting items into any of them, including the following hierarchies
delivered by SAP:
• X1: Statement of Changes in Equity
• X2: Statement of Cash Flow
• X3: Statement of Comprehensive Income
• X4: P&L by Function of Expense

4. Select the hierarchy X2 (Statement of Cash Flow).

5. Select Edit.
6. Find the node under which you want to add your newly created reporting item and select the Add icon ( )
from the row of the node to add it.
If necessary, you can also create a new node first. To do so, find the node that you want to serve as the
superordinate node to the one you want to create. Then, select the Add icon ( ) from the row of the node.
In the Add Node pop-up window, select the Subnode option. Enter an ID and optionally a description.
Finally, select OK.
7. In the Add Node pop-up window, select the Consolidation Reporting Item option, and then enter your newly
created reporting item either by selecting it from the value help or by typing it in directly. Finally, select OK.
8. Select Save to save your changes. After saving, the hierarchy is still in the status In Revision. As a result,
you aren't be able to use the hierarchy with your saved changes in reports.
9. Select Activate to activate the hierarchy. Once activated, the hierarchy receives the status Active. You can
now use the hierarchy with your saved changes in reports.

Group Reporting (FIN-CS)

Group Reporting PUBLIC 125
3. Define Reporting Rules

In this step, you define reporting rules by assigning the selection criteria for FS items and other data to your
newly created reporting item. You can also adjust any settings for other reporting items in the reporting rule
variant. When you later use reporting items as analytical dimensions in reports, the system considers all the
selection criteria you define here and derives the aggregated amounts for each reporting item accordingly.

For the sake of demonstration, this step also guides you through the process of creating a new reporting rule
variant by first copying over the rules from an existing variant. Keeping with the example of a statement of cash
flow, you copy the existing rules from the SAP-delivered reporting rule variant Y10, which contains reporting
rules for the reporting item hierarchy X2 (Statement of Cash Flow). Once the new variant is created, you can
adjust the reporting rules by adding your new reporting item and assigning it with selection criteria for FS items
and other data.

Procedure
1. Go to the Define Reporting Rules app.
2. Select a Consolidation COA. You must select the same consolidation COA for which you created your
reporting item in section 1. Create a Reporting Item of this guide.
3. For the Reporting Item Hierarchy, select X2 (Statement of Cash Flow).
4. For the Reporting Rule Variant, select Y10.
5. Select Copy.
6. In the Copy Reporting Rule ID pop-up window, enter a name for the new variant you want to create and
select Enter. Now, the existing rules from Y10 are copied into your new variant.
7. Double check that the values are correct for Consolidation COA, Reporting Item Hierarchy, and Reporting
Rule Variant. Your new variant should be the value for Reporting Rule Variant.
8. Select Change.
9. In the Description field, give your new reporting rule variant a description.
10. Select the Insert Row icon ( ), to insert a new row into the variant.
11. In the new row, select the reporting item that you created for Reporting Item.
12. Assign only one of the following FS item selection criteria to each:
• Assign range of FS items using FS Item From and FS Item To. To assign just one FS item, you can select
the same FS item for FS Item From and FS Item To.
• Assign an FS Item Attribute Name and an FS Item Attribute Value.
• Assign an FS Item Hierarchy and a Hierarchy Node.

 Note

The FS item selection criteria are mandatory when defining reporting rules. The selection criteria for
other data (such as subitems, document types, and consolidation units) are optional.

13. If necessary, add other filter criteria for the reporting item, such as subitems, document types, and
consolidation units.
14. If necessary, adjust the sign reversal settings in the Rev. Sign column. If you insert an X in this column, then
the amounts displayed in reports for the reporting item will have the opposite +/- sign than what is
typically displayed. For example, 100 will appear as -100, or -100 will appear as 100.
15. If necessary, make any other adjustments to the other rows of reporting items. You can also delete rows.
16. When you’re finished with your changes, select Save and then Exit. After exiting, you’ll be redirected to the
initial main screen of the Define Reporting Rules [page 118] app.

Group Reporting (FIN-CS)

126 PUBLIC Group Reporting
 17. Lastly, select Replicate Reporting Rules to activate your changes to the variant so that you can use it in the
system. If you don’t select Replicate Reporting Rules, then your changes will be inactive, and they won’t
take effect in the variant for future use.

Example of Defining Reporting Rules

To illustrate how amounts for reporting items are derived from reporting rules, let's say you define the following
rules for the new reporting item AAA111:

Consolidation Unit Consolidation Unit Reverse Sign

Reporting Item FS Item From FS Item To From To Indicator

AAA111 111100 111111 U00001 U00001 X

Please note that this is a simplified table for this example. It doesn't depict all the possible options for data
selection criteria in reporting rules.

After saving and replicating the reporting rules, you can now use the reporting rule variant in a report to display
amounts for reporting item AAA111. When the report is generated, the system displays an amount for AAA111
that aggregates all the assignments you’ve made for its reporting rules. In this case, that means the system
does the following:

• Aggregates all postings for the range of FS items from 111100 to 111111.
• Filters only for amounts related to the consolidation unit U00001, since the range of consolidation units is
only the one consolidation unit U00001.
• Reverses the +/- sign of the aggregated amount. So, if the amount is positive, it’s displayed as negative.
And if it’s negative, it’s displayed as positive.

4. Use Reporting Rules in a Statement of Cash Flow

In this step, you use the reporting rules you’ve created to make a statement of cash flow. This is done in the
Group Data Analysis - With Reporting Rules [page 531] app. In the app, you use the Reporting Item Hierarchy
and the Reporting Rule Variant as filters to display the relevant reporting items. In this example, the relevant
reporting items are those belonging to the hierarchy X2 (Statement of Cash Flow) and the variant you created in
step 3. Define Reporting Rules of this guide.

Procedure
1. Go to the Group Data Analysis - With Reporting Rules [page 531] app.
2. For the Reporting Item Hierarchy filter, select X2 (Statement of Cash Flow).
3. For the Reporting Rule Variant filter, select the reporting rule variant you created.
4. Set all other filters as necessary.
5. Select Go. Some results should now appear in the table.
6. If the dimension for rows in the table is anything but reporting items, change it so that reporting items are
displayed for each row. To do so, right-click on the very top-left cell of the table, which names which
dimension is being displayed for the rows. Select Drilldown and then Exchange with. The Select Fields pop-
up window appears. In this window, select Reporting Item and then OK.
7. The table now displays amounts based on reporting items. Since this report uses X2 (Statement of Cash
Flow) as the reporting item hierarchy, this report serves as a statement of cash flow and can be exported
and saved.

Group Reporting (FIN-CS)

Group Reporting PUBLIC 127
Use
By using Reporting Item Hierarchy and Reporting Rule Variant as filters to show reporting items as analytical
dimensions, you can display amounts based on reporting item. Since you’ve defined reporting rules for each
reporting item in the reporting rule variant, the system considers all the assignments of data selection criteria
for each reporting item and derives the aggregated amount. In this way, you can flexibly display fine-grained
results of your data in analytical reports.

1.2.3.2.2 Posting to Reporting Items

Posting to reporting items enables you to make adjustments directly to the values calculated for reporting
items in reports that use reporting rules (rule-based reports). To take advantage of posting to reporting items,
you assign the same reporting item as the financial statement (FS) item in the reporting item’s reporting rules.

Background with Business Scenario

There may be a scenario where you’re not satisfied with a certain value for a reporting item in a rule-based
report. So, you’d like to adjust it.

To do so, you need to analyze the reporting rules of the reporting item because the reporting rules determine
how the value for the reporting item is calculated. From the various factors in the reporting rules, you must find
out which one needs to be adjusted to get the desired final value in the report. For example, you may need to
post to a specific FS item that’s assigned to the reporting item in the reporting rules.

To avoid the process of figuring out what needs to be adjusted in the reporting rules, you can assign the
reporting item as the FS item in the reporting item’s reporting rules instead. This is possible since a reporting
item is an FS item with the FS item type REPT (Reporting Item). This way, you can just post directly to the
reporting item (FS item), and these postings are directly reflected in the value calculated for the reporting item
in the report.

How Does Posting to Reporting Items Work?

To understand how posting to reporting items works, it's important to keep in mind that a reporting item plays
two roles in the system:

1. As an FS item. Specifically, an FS item with the FS item type REPT (Reporting Item).
2. As an analytical dimension. A reporting item becomes an analytical dimension when you assign reporting
rules to it. The analytical dimension can then be used in rule-based reports.

 Note

To learn more about reporting items, reporting rules, and how they both relate to FS items and reports,
see Reporting Items and Reporting Rules [page 116].

These two roles of a reporting item serve two distinct purposes. This is important to keep in mind because a
reporting item as an FS item can be used like any other statistical item. This means that you can post to it, and

Group Reporting (FIN-CS)

128 PUBLIC Group Reporting
you can choose to carry forward its balances to the next year. However, in its role as an analytical dimension, a
reporting item is used in reports to represent values that are calculated based on the reporting rules. This
calculation of data in the reporting rules happens when the report is generated.

Since a reporting item plays these two roles for two distinct purposes, it’s possible to assign the reporting item
(FS item) to itself (analytical dimension) in the reporting rules. That way, when you post to the reporting item
(FS item), the postings are directly reflected in the value calculated for the reporting item (analytical
dimension) in the report. The following graphic illustrates this process:

 Example

Using the graphic as an example, you create the reporting item AAA001 as an FS item with the FS item type
REPT (Reporting Item). You then assign reporting rules to AAA001 so that it can be used as an analytical
dimension in rule-based reports. In the reporting rules, you assign itself (FS item AAA001) as one of the FS
items. In this case, AAA001 is the first in the range of FS items from AAA001 to AAA005. Because of this
assignment, any postings you make to the FS item AAA001 are directly reflected in the value for the
analytical dimension AAA001 in the rule-based report. This is visible by the amount a in the report. The
amount a represents all postings you make to FS item AAA001. This amount is aggregated with amounts of
the other FS items to calculate the value for reporting item AAA001. The reporting item AAA001 is then
used as an analytical dimension to display this value in the rule-based report.

How to Make Use of Posting to Reporting Items

To make use of posting to reporting items, follow the procedure in Example: Create Reporting Rules and Use
Them in Reports [page 124], but pay special attention to step 12 in section 3. Define Reporting Rules. In this
step, you assign FS items to the reporting item in the reporting rules. Here, you must assign the reporting item
(FS item) to itself (analytical dimension), as previously shown in the example.

 Note

In the reporting rules, there are several ways to assign FS items to the reporting item. For example, you can
assign FS items using an FS item hierarchy node, an FS item attribute, or the options FS Item From and FS
Item To. Regardless of which method you use, make sure that the reporting item (FS item) is a part of this

Group Reporting (FIN-CS)

Group Reporting PUBLIC 129
 selection. For example, if you assign FS items using an FS item hierarchy node, make sure that the
reporting item (FS item) is included in the hierarchy node.

Related Information

Reporting Items and Reporting Rules [page 116]

Example: Create Reporting Rules and Use Them in Reports [page 124]

1.2.3.2.3 How to Analyze Reporting Rules

After you define reporting items and their reporting rules, you can then test the reporting rules. To do this, you
check the aggregation of values for reporting items to verify that the aggregation aligns with what you've
defined in your reporting rules.

How to Verify the Aggregation of Values for Reporting Items - Range of FS

Items

If you've defined reporting rules by assigning a range of FS items to a reporting item, you can check the
aggregation of values for the reporting item. Check out this video to find out how:

 Note

The following multimedia content displays screens and interfaces in English only.

 Note

Captions are available for multiple languages. Use the CC (Closed Captions) button in the video player to
see which languages are supported.

You can also use the Search within video field to search for specific text in the English or German captions.

How to Verify the Aggregation of Values for Reporting Items - FS Item

Selection Attribute

If you've defined reporting rules by assigning an FS item selection attribute to a reporting item, you can check
the aggregation of values for the reporting item. Check out this video to find out how:

Group Reporting (FIN-CS)

130 PUBLIC Group Reporting
  Note

The following multimedia content displays screens and interfaces in English only.

 Note

Captions are available for multiple languages. Use the CC (Closed Captions) button in the video player to
see which languages are supported.

You can also use the Search within video field to search for specific text in the English or German captions.

1.2.3.2.4 Assign Reporting Rules to Versions

With this app you can assign your defined reporting rule variants to report rule versions. The latter is mapped
to the consolidation version by using the Define Versions customizing activity. In this way, the consolidation
versions that are mapped to reporting rule version will be implicitly assigned to the reporting rule variant.

Follow this procedure for the assignment:

1. Specify a Report Rule Version and assign it with a defined reporting rule variant.
2. In the Period From field, specify from which fiscal year and month the assignment takes effect.

The following diagram shows how the reporting rule variants are mapped to the consolidation versions and are
applied to build rule-based reports:

Group Reporting (FIN-CS)

Group Reporting PUBLIC 131
Changing Variants of Report Rule Versions

Variants cannot be changed after you’ve assigned them to report rule versions. That means that you can’t
make any adjustments or additions to the reporting rules contained in the reporting rule variant. This protects
reports from being changed accidentally in case changes are made to the selection criteria, such as changes to
hierarchies or FS item attributes.

If you want to make changes, you must create a new reporting rule variant by copying the variant that’s already
been assigned to the report rule version. Then, you can make changes to the newly copied variant.

Supported Device Types

• Desktop

1.2.3.3 Schedule Jobs for Consolidation Tasks

You can use this app to schedule and monitor jobs for consolidation tasks using the provided templates. If you
have manual activities that you often need to do at a specific time, this app can reduce your workload by
running these tasks smoothly in the background.

Key Features

This app provides the following key features:

• Scheduling jobs: Choose Create to schedule jobs based on the following job templates provided for
consolidation tasks:
• Balance carryforward
• Release universal journals
• Calculation of net income
• Currency translation
• Preparation for consolidation group changes
• Reclassification
• Validation of universal journals
• Validation of reported data
• Validation of standardized data
• Validation of consolidated data
• Realign group reporting preparation ledger
Depending on the template you choose, you need to specify the job-specific parameters in the Parameters
section, for example consolidation chart of accounts, consolidation version, fiscal year/period, and
consolidation group/unit.

Group Reporting (FIN-CS)

132 PUBLIC Group Reporting
 The Preparation for Consolidation Group Changes (PCC) and Reclassification job templates bundle multiple
tasks as follows. You need to choose one specific task in Parameters Task .

Job Template Tasks

Preparation for Consolidation Group Changes • 1130: PCC task as available in Data Monitor
• 2060: PCC task as available in Consolidation Monitor

Reclassification The interunit elimination tasks as available in

Consolidation Monitor:

• 2011: Interunit elimination of sales

• 2021: Interunit elimination of other income/expenses
• 2031: Dividends elimination
• 2041: Interunit elimination of balance sheet
• 2100: Investments/equity elimination
• 2180: Total divestiture

 Note

All the t