Public

F4 Value Help for Groups & Hierarchies

in sFIN and S/4 HANA Reporting Apps

June, 2018
Disclaimer

The information in this document is confidential and proprietary to SAP and may not be
disclosed without the permission of SAP. This document is not subject to your license
agreement or any other service or subscription agreement with SAP. SAP has no obligation to
pursue any course of business outlined in this document or any related presentation, or to
develop or release any functionality mentioned therein. This document, or any related
presentation and SAP's strategy and possible future developments, products and or platforms
directions and functionality are all subject to change and may be changed by SAP at any time
for any reason without notice. The information in this document is not a commitment, promise
or legal obligation to deliver any material, code or functionality. This document is provided
without a warranty of any kind, either express or implied, including but not limited to, the
implied warranties of merchantability, fitness for a particular purpose, or non-infringement. This
document is for informational purposes and may not be incorporated into a contract. SAP
assumes no responsibility for errors or omissions in this document, except if such damages
were caused by SAP intentionally or grossly negligent.
All forward-looking statements are subject to various risks and uncertainties that could cause
actual results to differ materially from expectations. Readers are cautioned not to place undue
reliance on these forward-looking statements, which speak only as of their dates, and they
should not be relied upon in making purchasing decisions.

© 2017 SAP SE or an SAP affiliate company. All rights reserved. Public 2

Where are (account) groups (=hierarchies) used ?

Hierarchies are important in reports because they help to display the information in a structured
(hierarchical) way. At the same time summarization logic uses hierarchies.
Hierarchies are available for many dimensions.
Examples: Cost Centers, Profit Centers, Accounts, Customers, …

© 2017 SAP SE or an SAP affiliate company. All rights reserved. Public 3

 How does BPC access an account hierarchy ? 1/3
sFIN 1.0

FSV
Financial Statement
Version
Maintained with TA FSE2
Report

Read Hierarchy
Account Group
Set of GL Accounts; Set Type 0109

In order to create an Account Group:

 starting from a FSV: use TA KE5b
 starting from an Cost Element Group: use TA KE61

Cost Element Group

Set of Cost Elements;
Set Type 0102
Maintained with TA KAH1

© 2017 SAP SE or an SAP affiliate company. All rights reserved. Public 4

How does BPC access an account hierarchy ? 2/3
sFIN 2.0

Report

Read Hierarchy
Replicate
FSV
Financial Statement Tables
Version
HRRP*

Account Group
Set of GL Accounts;
Set Type 0102

Customer instruction:

a) Implement note 2311408 and execute the program delivered with this note (!)
Use report R_IBPF_USE_ACTGRP_HIER to switch
between usage of FSV or account groups.
b) Using KE61: copy selected Cost Element Groups to GL-Account Groups (Type 0102 to Type 0109)

c) The F4 Value help now shows the newly copied groups. See note http://service.sap.com/sap/support/notes/2311408
d) Report Relevancy / Replication is not necessary !

© 2017 SAP SE or an SAP affiliate company. All rights reserved. Public 5

 How does BPC access an account hierarchy ? 3/3
sFIN 3.0 and S/4HANA 1610 (and following)

If account groups for balance sheet accounts are needed, build them as Financial Statement Versions.
Prior to the first execution of the replication program, hierarchies are read only from FSV.
After this, hierarchies are read from tables HRRP*

Report
FSV

Read Hierarchy
Financial Statement
Version

Replicate
Cost Element Group Tables
Set of Cost Elements; HRRP*
Set Report
Relevancy

Set Type 0102

Account Group
Set of GL Accounts; X
HRY_REPRELEV

riTile or transaction HRRP_REP

SE38

FINS_REPLICATION_HIER
FINS_REPLICATION_JOB
Or

Or SE11 / SE16
Fiori Tile or transaction

Set Type 0109

HRRP_DIRECTORY
HRRP_DIRECTORYT
HRRP_NODE
HRRP_NODET
HRRP_TYP
In a previous version of this PPT, this arrow
HRRP_TYPT
was shown by mistake. Correct is:
HRRP_VTYP
It is possible to use account sets of type 109
or
FSV together with account sets of type 102

© 2017 SAP SE or an SAP affiliate company. All rights reserved. Public 6

Process to follow for using hierarchies in reports
sFIN 3.0

Step 1: This procedure

applies to following
Create Financial Statement Versions (FSV) and/or
dimensions in a
Create Cost Element Groups
similar way :
(Set Class 0102) and/or
Create Account Group
(Set Class 0109)
(See previous page on possible combinations)

Step 2:
Click Fiori tile “Set Report Relevancy“
and chose corresponding Set Class
for your controlling area
(This step is not necessary for FSV.
They are always “relevant”)

Result:
Step 3:
All FSV and the
Click Fiori tile “Replicate Runtime “relevant” Cost Element
Hierarchy” and schedule replication Groups are available in
job (for immediate execution) reporting to be used as
hierarchy

© 2017 SAP SE or an SAP affiliate company. All rights reserved. Public 7

Other hierarchies

In elder releases, not all relevant dimensions could be replicated or extracted for reporting
purposes:
Dimension Replication Extraction Dimension Replication Extraction
Cost Center X Cost Center X X
Internal Order X Internal Order X X
Account Group ? Account Group ?
Profit Center Profit Center X
Functional Area X Functional Area X X
Cost Element X Cost Element X X

As of sFIN3.0 (and S/4) the replication and extraction is available for:

Dimension Replication Extraction

Cost Center X X
Internal Order X X
Tip: You have problem with Profit Center
Account Group X ? hierarchy performance?  note 2514230
Profit Center X X
Functional Area X X
Replication = Write into table HRRP*
Cost Element X X Extraction = Read F4 from table HRRP*

© 2017 SAP SE or an SAP affiliate company. All rights reserved. Public 8

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

No part of this publication may be reproduced or transmitted in any form or for any purpose without the express permission of SAP SE or an
SAP affiliate company.

SAP and other SAP products and services mentioned herein as well as their respective logos are trademarks or registered trademarks of SAP SE
(or an SAP affiliate company) in Germany and other countries. Please see http://global12.sap.com/corporate-en/legal/copyright/index.epx for additional
trademark information and notices.

Some software products marketed by SAP SE and its distributors contain proprietary software components of other software vendors.

National product specifications may vary.

These materials are provided by SAP SE or an SAP affiliate company for informational purposes only, without representation or warranty of any kind,
and SAP SE or its affiliated companies shall not be liable for errors or omissions with respect to the materials. The only warranties for SAP SE or
SAP affiliate company products and services are those that are set forth in the express warranty statements accompanying such products and
services, if any. Nothing herein should be construed as constituting an additional warranty.

In particular, SAP SE or its affiliated companies have no obligation to pursue any course of business outlined in this document or any related
presentation, or to develop or release any functionality mentioned therein. This document, or any related presentation, and SAP SE’s or its affiliated
companies’ strategy and possible future developments, products, and/or platform directions and functionality are all subject to change and may be
changed by SAP SE or its affiliated companies at any time for any reason without notice. The information in this document is not a commitment,
promise, or legal obligation to deliver any material, code, or functionality. All forward-looking statements are subject to various risks and uncertainties
that could cause actual results to differ materially from expectations. Readers are cautioned not to place undue reliance on these forward-looking
statements, which speak only as of their dates, and they should not be relied upon in making purchasing decisions.

© 2017 SAP SE or an SAP affiliate company. All rights reserved. Public 9