SAP S/4HANA for group reporting
2502 Feature Deck
SAP Product Management and Product Engineering
February 2025
Public
About this document
Author
SAP Product Engineering and SAP Product Management
Revision
February 2025
About
This document highlights the key new features of SAP S/4HANA Cloud for group reporting, release 2502. It is nonexhaustive and cannot be used as a training document as is.
Public
3
Disclaimer
The information in this presentation is confidential and proprietary to SAP and may not be disclosed without the permission
of SAP. Except for your obligation to protect confidential information, this presentation 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 presentation or any related document, or to develop or release any functionality mentioned therein.
This presentation, or any related document 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 presentation is not a commitment, promise or legal obligation to deliver any material, code or
functionality. This presentation 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 presentation is for
informational purposes and may not be incorporated into a contract. SAP assumes no responsibility for errors or omissions in
this presentation, except if such damages were caused by SAP’s intentional or gross negligence.
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.
Public
4
SAP S/4HANA Cloud for group reporting, release 2502
New and improved features 1/2
PREPARE
COLLECT
• Master data
– Master data read APIs go
– Manage consolidation hierarchies app go
– Delete financial statement items go
– Display master data change log information go
– Additional master data field configuration go
– Aggregation of additional fields in activity-based
consolidation of investments go
– Group Reporting Preparation Ledger configuration go
– Manage additional consolidation hierarchy types go
– Improved import consolidation master data app go
– Partner Fund available for public sector go
– Release Universal Journal – Support of prior periods
modes go
– Changed treatment of product group during universal
data release go
• Import reported data
– Improved UX with a new SAP Fiori app go
Public
• GRDC data mapping
– Advanced monitoring of jobs go
– Improved job processing and logs go
– OData v4 custom connection to SAP Green Ledger go
• GRDC forms
– Multiple fiscal years and periods in forms go
– Navigation between forms go
– Integrate package with data monitor task execution go
• Data quality
– Multiple line-validation tasks on group reporting and
unreleased accounting data go
– Multiple balance validation tasks in group reporting
and unreleased accounting data go
5
SAP S/4HANA Cloud for group reporting, release 2502
New and improved features 2/2
CONSOLIDATE
FOCUS TOPIC
• Manual journal entries
– Extending usability in creating manual journals
using new replace feature go
• Greenhouse gas
– Greenhouse gas emission reporting go
– Integrating SAP Green Ledger to group reporting go
ANALYZE
• Review booklet
– New app with an analytical group view on
unreleased accounting data go
– Commenting and notifications go
– AI-assisted financial business insights for
group statements (beta) go
Public
6
Prepare
Collect
Consolidate
Analyze
2408.1 release
Master Data Read APIs
Availability of global parameters read API
Global parameters read API
i As of S/4HANA 2408.1 an API to read global parameters of a user is provided.
➢
This synchronous inbound service enables you to read consolidation global
parameters for group reporting.
➢
This service is published on the SAP Business Accelerator Hub.
➢
The consolidation global parameters are a set of user-specific parameters which
are applied to applications used for financial consolidation in group reporting.
Constraints:
With this service, it is not possible to:
➢
Perform a create, update, or delete operation.
➢
Read global parameters for a business user who has not
actively set them in the system.
➢
Read global parameters for a user which is different to
the logon user.
This includes all values maintained for a specific user as global parameter values, e.g.:
➢
Consolidation group
➢
Consolidation unit
➢
Consolidation version
➢
Consolidation chart of accounts
➢
Fiscal year
➢
Fiscal period
Documentation:
➢
https://help.sap.com/docs/SAP_S4HANA_CLOUD/0056c
2b57fe34ddf865f0e396e7e91fc/9c71d739b3c04d4c8708
7b0338e6e0f2.html?version=2502.500
This API provides the prerequisites for answering the following business question:
➢
Which global parameters have been set by a business user?
Technical name of API:
➢
Public
API_CNSLDTNGLOBALPARAMETER
8
Prepare
Collect
Consolidate
Analyze
2408.1 release
Manage Consolidation Hierarchies application
Display unassigned master data values feature
“Manage Consolidation Hierarchies” app
Display unassigned master data values
2
3
4
1
i
1
2
3
Public 4
As of S/4HANA 2408.1 you may display master data values which are not (yet) assigned to a consolidation hierarchy in the “Manage Consolidation Hierarchies” app.
This feature is available for all consolidation hierarchy types except “Consolidation Posting Level” hierarchies.
In order to display master data values not (yet) assigned to a consolidation hierarchy, open the consolidation hierarchy in the “Manage Consolidation Hierarchies” app, …
… select the “Timeframe” section, …
… and choose the “Unassigned” tab.
In this example this shows a list of all FS items which are not assigned to the “Balance Sheet” FS item hierarchy, e.g. the P&L FS items.
10
Prepare
Collect
Consolidate
Analyze
2502 release
Delete financial statement items
Define FS Items app & FS items master data APIs
“Define Financial Statement Items” app – delete FS items – slide 1
Overview
1
1
As of S/4HANA 2502 you can delete financial statement items (FS items). You can do so in the Define Financial Statement Items app on the
overview screen as well as on the details screen, and you can as well delete FS items via the local and remote FS item master data APIs.
i
In general, all types of FS items may be deleted, that is, customer-defined FS items as well as FS items that are delivered with the SAP Content.
However a user may only delete FS items which are not used any more and he is authorized to delete (i.e. is authorized to change). In case one
of these two prerequisites is violated, an error message with the reason why an FS item could not be deleted is shown.
Public
Note: As the authorization to change and delete FS items is granted on the level of a consolidation chart of accounts the user can either change
and delete any FS item in a consolidation chart of accounts or none of them.
12
“Define Financial Statement Items” app – delete FS items – slide 2
Details – part 1
2
1
i
On the overview screen of the “Define Financial
Statement Items” app you can delete a single FS item
or several FS items in one rush.
1
As long as no FS item has been selected in the FS
items list on the overview page, …
2
3
... the “Delete” button is not active.
4
… the “Delete” button is active. After selecting the
“Delete” button …
Once one or several FS items have been selected in
the FS items list on the overview page, …
4
3
Public
13
“Define Financial Statement Items” app – delete FS items – slide 3
Details – part 2
3
1
2
1 … a warning pop up is shown.
2 Confirming “Delete” on the warning pop up will then
execute the deletion of the selected FS item(s).
3 In case all selected FS items could be deleted, a so
called message toast is shown which confirms the
number of deleted FS items. This message toast
vanishes automatically after some time.
4 In case at least one of the selected FS items could not
be deleted, an error pop up is shown.
4
6
5
5 The error pop up in any case shows the FS item(s)
7
that could not be deleted including the reason why the
deletion failed. This could either be, because an FS
item is still in use, or the user is not authorized to
delete the FS item(s).
6 In case some of the selected FS items could be
deleted, the error pop up also confirms the number of
deleted FS items.
Public
7 The error pop up has to be closed manually.
14
“Define Financial Statement Items” app – delete FS items – slide 4
Details – part 3
2
1
i
On the details screen of the “Define Financial Statement Items” app you can
delete the FS item which is shown on that screen.
1
Other than on the overview screen, where the “Delete” button is only active in
case at least one FS item has been selected, the “Delete” button on the details
screen is always active when the screen is in display mode. This is due to the
fact, that by definition exactly a single FS item has been selected on this screen,
namely the one for which the user navigated from the overview screen to the
details screen.
The deletion process as such is the same as on the overview page, i.e. after
selecting “Delete” a warning pop up is shown. Confirming “Delete” on the warning
pop up will then start the deletion of the FS item.
In case of successful deletion of the FS item a message toast which confirms the
deletion is shown and vanishes automatically after some time. Additionally the
user is automatically navigated back to the overview page.
In case the deletion fails because the FS item is still used or the user is not
authorized to delete FS items in the given consolidation chart of accounts, an
error pop-up which contains the reason for the failing deletion is shown. The error
pop up has to be closed manually and the user stays on the details screen of the
Define Financial Statement Items app.
2
Public
In case the user switches the details screen into the edit mode by selecting
“Edit”, the “Delete” button, as well as the other buttons, “Copy” and “Check
Where Used”, are not shown.
15
“Define Financial Statement Items” app – delete FS items – slide 5
Details – part 4
1
1 In case the user is not able to delete an FS item because it is still
used …
2 … the “Check Where Used” functionality in the “Define Financial
Statement Items” app may be used, in order to get information about
the usage of such an FS item. The “Check Where Used” functionality
is available on the overview screen as well as on the details screen
of the “Define Financial Statement Items” app.
2
Some usages, such as the assignment of a G/L account to an FS
item, the assignment as target FS item to another FS item, or the
assignment of an FS item role to the FS item, can be deleted. Other
usages, such as existing transactional data, can't be deleted.
3 After removing all usages of an FS item, the FS item can be deleted.
2
3
Public
16
FS item master data CRUD APIs – delete FS items – slide 1
Remote financial statement item CRUD API
i Already as of S/4HANA 2302.2 a remote API to create, read, and update financial statement (FS) item master data is
provided.
This includes all FS item attributes:
➢ Time- and version-independent attributes:
E.g. “FS Item Type”, “Breakdown Category”, “Link URL”
➢ Time- and version-dependent attributes:
E.g. “FS Item Role”, “Cash Flow Selection”, “Elimination Target”
➢ Language-dependent texts:
“FS Item Description”, “FS Item Medium Description”, “FS Item Long Description”
➢ All custom attributes for FS items (be it time- and version independent, or time- and version-dependent attributes)
Technical name of the remote API:
➢ API_CNSLDTNFSITEM
As of S/4HANA 2502 this remote API also allows the deletion of FS items and with that is now a fully fledged CRUD API.
Documentation:
➢ https://help.sap.com/docs/SAP_S4HANA_CLOUD/0056c2b57fe34ddf865f0e396e7e91fc/75c229bc96094cc3bde9b9c4896a9386.html
Public
17
FS item master data CRUD APIs – delete FS items – slide 2
Local financial statement item CRUD API
i As of S/4HANA 2502 also the local FS item master data API allows the deletion of FS items and with that is now also a
fully fledged CRUD API.
Technical name of the local API:
➢ I_CnsldtnFSItemTP
Public
18
Prepare
Collect
Consolidate
Analyze
2502 release
Display master data change log information
Define Financial Statement Items app
“Define Financial Statement Items” app – display change log – slide 1
Overview
1 The “Show Change Log” feature is available on the
1
overview screen and the details screen of the
“Define FS Items” app.
2 Changes are grouped for better readability by timestamp,
user, and type of change. So all changes applied by a
single user in a single save operation are shown as one
group of changes in the change log.
2
i The change log contains the FS item with all its master
data attributes, i.e.:
• Time- and version-independent attributes
(e.g. assigned breakdown category)
• Time- and version-dependent attributes
(e.g. FS item selection and target attributes)
• Language-dependent attributes
(i.e. all description texts)
The displayed change log information can be filtered
according to several dimensions (e.g. date, user name,
language, attribute, etc.), and can be exported if required.
For further details please refer to subsequent slides.
i As of S/4HANA 2502 you can display the master data change log of a financial statement item (FS item) in the “Define Financial Statement Items” app. For public
cloud customers this is the first time their users get access to the master data change log of FS items at all. For on premise and private cloud customers this replaces
the very technical access to the table change log via backend transaction SCU3 with a more end-user friendly integrated access.
So far we only cover the use case to get master data change log information on a dedicated FS item. Other use cases, e.g. the typical auditor use case: “What has
changed wrt FS items during the last 12 months?”, are not yet covered.
Public
20
“Define Financial Statement Items” app – display change log – slide 2
Access change log information
1
i
The master data change log information
for FS items can be accessed from two
different places in the “Define Financial
Statement Items” app:
1
• By pressing the “Show Change Log”
button on the overview page of the
app.
Note: The button is only active when
you select exactly a single FS item in
the FS item list. It is inactive as long as
no FS item has been selected or as
soon as several FS items have been
selected.
2
2
• By pressing the “Show Change Log”
button on the details page of an FS
item.
Note: The button is only available as
long as you’re in display mode on the
details page. As soon as you’re in edit
mode the button is not shown. This
avoids additional complexity and
eventually confusion in case of
unsaved changes.
Public
22
“Define Financial Statement Items” app – display change log – slide 3
Grouping of displayed change log information
3
1 Master data changes applied to an FS item by a
single user in a single save operation are
grouped in the change log information pop-up.
The group headers show the information what
kind of change (i.e. create, change, or delete)
was applied when (date and time) by which user
(user name / user ID).
1
Such a group may contain FS item attributes
from different categories such as time- and
version-independent, time- and versiondependent, and language-dependent attribute
changes.
2
Note: This grouping cannot be changed or
removed.
2 For technical reasons it may happen that the
changes a user applies to an FS item with a
single save operation are stored with slightly
different timestamps, as they are persisted in
different master data tables.
In that case such changes may occur in
separate groups showing slightly different
timestamps in the grouping header.
3 The FS item as well as the consolidation chart of
accounts of the FS item, for which the change
log information is shown, is displayed in the
header of the pop-up.
Public
23
“Define Financial Statement Items” app – display change log – slide 4
Change log information for time- and version-independent attributes
i
Time- and version-independent attributes of FS items
(e.g. the FS item type, the assigned breakdown category,
the “Blocked for Posting” indicator, or the “Link”
information) are shown in the change log with the “Field
Label” (i.e. the attribute label, e.g. “Breakdown Category”)
as well as the “Old Value” and the “New Value”.
1 In case the attribute value was newly assigned (i.e. there
3
was no attribute value assigned before), the “Old Value”
information is empty and the “New Value” information
contains the key of the newly assigned value.
2
2 In case the attribute value was changed, the “Old Value”
shows the key of the attribute value which was assigned
before the change, and the “New Value” shows the key of
the attribute value which was assigned as of the change.
3 In case the attribute value assignment was deleted (i.e.
without assigning a new attribute value), the “Old Value”
shows the key of the attribute value which was assigned
before the deletion and the “New Value” information is
empty.
!
1
Public
As the description text of an attribute value may change
over time, or an attribute value may even not exist any
longer, it is impossible to show the description texts of
attribute values in a consistent way. Therefore only the
attribute value keys are shown in the change log
information. This applies to all kind of FS item attributes.
24
“Define Financial Statement Items” app – display change log – slide 5
Change log information for time- and version-dependent attributes – part 1
1 Time- and version-dependent attributes of FS items
(i.e. all FS item selection attributes (including the “FS
Item Role” attribute) and FS item target attributes) are
shown in the change log with the “Field Label” (i.e.
the attribute label, e.g. “Currency Translation
Attribute”), the “Version”, the “From Fiscal Year
Period” and the “To Fiscal Year Period”, as well as the
“Old Value” and the “New Value”.
2
2 The “Version” value which is shown always
4
3
1
corresponds to the (consolidation) version which has
been selected in the context box of the time- and
version-dependent attributes on the details page, or
in the filter bar on the overview screen. With this only
changes of attribute assignments in the version
you’re currently in are shown.
3 The “From Fiscal Year Period” and “To Fiscal Year
Period” inform, to which time interval the change of a
time- and version-dependent attribute was applied.
For further details please refer to the next slide.
4 The “Old Value” and “New Value” show the key of the
attribute value, which had been assigned before the
change and which is assigned after the change for
the given version and time interval.
In case the “Old Value” is blank, there was no value
assigned before the change, and in case the “New
Value” is blank, the assigned value was removed
without assigning a new value.
Public
25
“Define Financial Statement Items” app – display change log – slide 6
Change log information for time- and version-dependent attributes – part 2
1
As already stated on the previous slide the “From Fiscal
Year Period” and “To Fiscal Year Period” inform, to which
time interval the change of a time- and version-dependent
attribute was applied.
In this example the currency translation selection attribute
value “S-CT-BS-HIST” was assigned as of “006.2024” until
“999.9999”, where before no value was assigned to (“Old
Value” is blank).
2
3
Later on a different attribute value “S-CT-BS-CLO” is
assigned to the FS item in the same version as of fiscal
year period “009.2024”.
Therefore the assignment of value “S-CT-BS-HIST”
changes to from value “S-CT-BS-HIST” to “S-CT-BS-CLO”
in the timeframe “009.2024” until “999.9999”.
This implicitly means that the assignment of value “S-CTBS-HIST” is shortened from “006.2024” until “999.999” to
“006.2024” until “008.2024”. But this is not shown in the
change log information, as the assigned attribute value in
this (shortened) timeframe did not change. What changed
from a user perspective, is the assigned attribute value in
the remaining timeframe “009.2024” until “999.9999” and
this is exactly what is shown.
2
1
3
Public
In very rare and practically not very relevant cases it may
happen, that several time intervals are shown, where the
same change was applied to. Logically they will always be
a single timeframe (i.e. there won’t be any gaps between
these time intervals), but for technical reasons they are
displayed separately.
26
“Define Financial Statement Items” app – display change log – slide 7
Change log information for language-dependent attributes
1 Language-dependent attributes of FS items (i.e. the
3
short, medium, and long description of FS items) are
shown in the change log with the field label (i.e. the
attribute label, e.g. “Medium Text for FS Items”), the
“Language” key (e.g. “EN”), as well as the “Old Value”
and the “New Value”.
2 Again the assigned descriptions may change from
blank to something, …
1
2
3 … from something to blank, …
4 … or from something to something else.
4
Public
27
“Define Financial Statement Items” app – display change log – slide 8
Change operation in change log information
i
As already stated on a prior slide, the change
operation (i.e. create, change, delete) is part of
the grouping headers in the change log table.
1 Usually you’ll see a single create change group
at the bottom of the change log.
Note: In case of many changes you may have
to page down to the bottom of the change log,
in order to see this entry.
4
2 Above this create change group you may
usually see a couple of groups with the change
operation.
3
3 The deletion of an FS item you will in most
cases not see in the change log. First of all,
because the deletion of an FS item is an
exceptional case and can only be perform a
deletion in case the FS item is not used
anywhere. Secondly, in case an FS item has
been deleted, you can neither select it in the
overview page of the app, nor can you
navigate to its details page, and with that you
cannot open the change log pop-up, in order to
see such a deletion.
2
1
4
Public
But as soon as you create a new FS item with
exactly the same key as the deleted one, you
will not only see the creation of the new FS
item in the change log, but any other change of
the “old” FS item, including its deletion, as well.
28
“Define Financial Statement Items” app – display change log – slide 9
Filtering change log information – part 1
1
1 You can filter the change log information according to
several dimensions via the filter bar.
2
2 For example by filtering a certain user name, you see
only the changes applied by that user.
i While filters on “User Name”, “User” (this filter may be
2
Public
added via the “Filters” button and it filters on the user
ID), “Date”, and “Operation” (i.e. create, change,
delete) always exclude or include complete groups of
changes …
29
“Define Financial Statement Items” app – display change log – slide 10
Filtering change log information – part 2
1
i … other filters such as “Language” and “Field Label”
2
may filter only a subset of rows in change groups.
1 For example the filter Language equals “EN” and
Field Label contains “Short” …
2 … provides you only with the changes that where
applied to the short description of the FS item in
language English …
3 … even though the respective change groups
contained also other attribute changes (in the shown
example this is the “FS Item Type” in the older
change and the “Medium Description” in the newer
change), which you can see in the unfiltered change
log display.
3
Public
30
“Define Financial Statement Items” app – display change log – slide 11
Filtering change log information – part 3
3
1
2
1 For some filters including and excluding
conditions are supported. These are “User
Name”, “User” (i.e. user ID), and “Field
Label”.
Public
2 For some filters only equals conditions with multi
selections are supported. These are “Language”
and “Operation” (i.e. create, change, and delete).
3 The “Date” filter last but not least provides even
a bunch of dynamic filter options, e.g. “Last
Year” or “Last X Months”.
These dynamic options especially make sense
in case you store your filter settings as “views”
31
to be applied repeatedly.
“Define Financial Statement Items” app – display change log – slide 12
Save views to persist filter settings
1
1 In order to persist filter settings which you defined and
want to be able to re-apply later at any point in time,
open the view menu, …
2
2 … save your filter bar as view, if required including
options such as “Set as Default”, …
3 … and re-apply them at any point in time by opening
the view menu, …
4 … and choosing the appropriate view in the list.
i Please note:
• The view contains all filter settings, i.e. the
displayed filters as well as the filter values.
3
4
• Dynamic date filters such as “This Month” will be
applied according to the current date (i.e. their
selection will change dynamically over time).
• Language dependent filters, such as a filter on the
language dependent field labels, may provide
different or no results in different languages.
• The view does NOT contain any changes you
applied to the table layout, i.e. changed number,
sequence, or width of displayed columns. These
changes cannot be stored at this point in time, but
have to be re-applied manually.
Public
32
“Define Financial Statement Items” app – display change log – slide 13
Download change log information – part 1
3
6 x
1
2
5 x
4
1 If required you can export the change log result.
By opening the “Export Table” menu …
2 … and choosing the “Export As…” option …
3 … a pop-up is opened with various options.
4 However be aware that the download will only
contain the columns of the change log display
table, …
5 … but neither the information of the grouping
headers, …
6 … nor the information of the pop-up header.
i How to get this information into the download,
please refer to the next slide.
Public
33
“Define Financial Statement Items” app – display change log – slide 14
Download change log information – part 2
2
1
In order to get any required
information of the change log
display pop-up (including
information from the grouping
headers as well as from the
pop-up header) exported,
open the “Settings” pop-up of
the table first, …
2
… select and arrange the
information you want to
export, …
3
4
…press “Ok”, …
5
The export file will now
contain all required
information.
1
4
3
and only then trigger the
export.
5
Public
34
“Define Financial Statement Items” app – display change log – slide 15
Example – Part 1 – Master data change for an FS item in “Define FS Items” app
1
2
3
5
6
4
8
9
7
abc
abc
abc
Created value assignment – from blank to “abc”
xyz
Changed value assignment – from “abc” to “xyz”
Deleted value assignment – from “abc” to blank
CONFIDENTIAL – SAP and External Parties under FBA Only
35
Display change log – slide 16
Change log display in transaction SCU3
Example – Part 2 – Resulting change log
2
3
1
Change log display in “Define FS Items” app
2
3
1
7
5 6 4
8
9
5
6
4
7
8
CONFIDENTIAL – SAP and External Parties under FBA Only
9
36
Display change log – slide 17
Comparison of change log display
Change log display in “Define FS Items” app
11
5
Change log display in transaction SCU3
2
1
7
5
6
8
4
10
12
9
3
i
i
1
Change log display functionality integrated in “Define FS Items” master data app.
Changes of FS items master data changes have to be looked up in generic table change log
transaction SCU3, which is only available for OP and private cloud, but not for public cloud
customers. Usage of transaction SCU3 requires knowledge about database table names.
Changes of all kind of attributes (i.e. time- and version-independent, time- and
version-dependent, and language-dependent attributes) in one place.
2 Changes of each kind of attributes (i.e. time- and version-independent, time- and version-
Changes of all kind of attributes (especially also the changes of time- and versiondependent FS item attributes) are presented in an end-user compatible way.
4 Especially changes of time- and version-dependent FS item attribute values are very difficult
5
Self explanatory labels for all fields.
6 Technical and abbreviated labels (e.g. “From Fiscal Year Period” and “To Fiscal Year Period”
7
i
9
Backend user ID as well as frontend user name is shown.
3
dependent, and language-dependent attributes) have to be looked up separately by selecting
the change log for the respective database table.
or even impossible to understand for an end-user.
have both the same label “Fisc. Y/P”).
Only information which is relevant for the end user is shown.
8 Only backend user ID is shown.
i Not relevant information (e.g. “TCode”, “Program”, “ETag”, …) is shown as well.
Consolidation version is shown instead of the FS item attribute special version.
10 Only the FS item attribute special version is shown.
11 Change operations (“Created”, “Changed”, “Deleted”) refer to the FS item.
CONFIDENTIAL – SAP and External Parties under FBA Only
12 Change operations reflect database operations. The “Created” in this example is from end37
user perspective a change of an already existing FS item.
Prepare
Collect
Consolidate
Analyze
2502 release
Additional Master Data Field Configuration
Limited configuration options for Assignment Reference in order to avoid unnecessary data volume
Limited Assignment Reference configuration to avoid unnecessary data volume – slide 1
Overview
1
1
i
Public
The field “Assignment Reference” in S/4HANA can be configured by
customers in many ways in accounting. In most cases the assignment
reference is more transactional information than master data information,
and has a huge number of values, which may even constantly grow over
time.
Transferring this information from accounting to group reporting during
release universal journal (RUJ) and transferring it from one fiscal year to the
next one by balance carryforward, will blow up the data volume significantly
over time, especially when it is configured in a way that the number of
values constantly grows over time. Furthermore the business value of the
assignment reference for consolidation purposes is seen as limited.
Therefore SAP recommended to aggregate over the field “Assignment
Reference” during RUJ task as well as during balance carryforward.
2
2
This is also the reason, why “Aggregate on Carryforward” and “Aggregate Data on Release” are
delivered as switched on for “Assignment Reference” via SAP content (as shown in the screenshot).
i
However before S/4HANA 2502 customers could simply switch off the aggregation during RUJ task
and balance carryforward task execution.
As of S/4HANA 2502 the configuration behavior was changed:
• New customers and upgrade customers that did not switch off the aggregation before the
upgrade cannot switch off this aggregation any more, as both fields are read only for them.
• In case of upgrade customers that changed the content setting and transferred the assignment
reference information via RUJ and/or balance carryforward task, this information is still
transferred (i.e. no changed behavior after system upgrade). However, once a customer decides
to aggregate over the field “Assignment Reference”, this configuration in principle cannot be
changed back. A warning pop-up makes users aware of this when they activate the aggregation.
For further details please refer to the subsequent slides.
39
Limited Assignment Reference configuration to avoid unnecessary data volume – slide 2
Details regarding “Aggregate Data on Release” for “Assignment Reference” – part 1
1
i
Before S/4HANA 2502 the “Aggregate Data on Release”
configuration option for “Assignment Reference” could be selected
or deselected by a customer at any point in time.
1
As of S/4HANA 2502 this configuration option is only active for
customers for “Assignment Reference” in case it has not been
activated, i.e. the assignment reference detail is transferred by the
RUJ task from accounting to group reporting.
2
As soon as “Aggregate Data on Release” gets activated and this
change is saved, the configuration field is read only, i.e. a
customer cannot deselect this option again. A warning pop-up
makes a customer aware of this when the aggregation is getting
activated.
With this changed configuration behavior the following is achieved:
i
2
Public
➢ In case of customers that activate the content as of S/4HANA
2502 and upgrade customers that did not change the delivered
content setting of “Aggregate Data on Release” for “Assignment
Reference”, the RUJ task does not transfer the assignment
reference detail from accounting to group reporting, and
customers cannot disable this aggregation.
➢ In case of upgrade customers that deactivated the “Aggregate
Data on Release” for “Assignment Reference” before S/4HANA
2502, the RUJ task continues to transfer the assignment
reference detail (i.e. no change in behavior). The configuration
field is empty and active, but when a customer activates the
“Aggregate Data on Release” option for “Assignment
Reference” and saves this changed configuration, it is not
possible any more to switch this off again. A warning pop-up
makes the user aware of this, directly after maintaining the
checkmark for the “Aggregate Data on Release” (see next
slide).
40
Limited Assignment Reference configuration to avoid unnecessary data volume – slide 3
Details regarding “Aggregate Data on Release” for “Assignment Reference” – part 2
1
1
As explained on the previous slide, upgrade customers that
deactivated the “Aggregate Data on Release” for the
“Assignment Reference” field before S/4HANA 2502 upgrade,
can still edit this configuration field.
2
Once such a customer selects the “Aggregate Data on
Release” setting for the “Assignment Reference” field, …
3
… a warning pop-up is shown, which explains that the change
the user applied, changes the system settings in a way, that the
system follows the changed standard system settings provided
by SAP for the “Assignment Reference” field, and that this
change, once saved, cannot be reverted.
2
3
6
4 After closing the warning pop-up, …
5 … the configuration field is still editable.
6 So the user can decide to either remove the “Aggregate Data
on Release” setting again, and with that still having the system
behavior deviating from the changed standard behavior, …
7 … or to stick to the change and save it. Only after saving the
4
change …
5
2
8
… the changed configuration field will be read only and the
“Aggregate Data on Release” configuration flag cannot be
removed any more.
i
With that customers do neither have a day-1 impact after
upgrade, as their system behaves as before the upgrade, nor
are they forced to change their system to standard behavior.
But once they change the system to the standard behavior and
save this change, they cannot revert this any more.
i
Please note that the same warning pop-up with the same
system behavior is shown, when a customer selects the
“Aggregate on Carryforward” setting for the “Assignment
41
Reference” field.
7
8
Public
Limited Assignment Reference configuration to avoid unnecessary data volume – slide 4
Details regarding “Aggregate on Carryforward” for “Assignment Reference” - part 1
i
Before S/4HANA 2502 the “Aggregate on Carryforward”
configuration option for “Assignment Reference” could be selected
or deselected by a customer whenever the “Enable Inputs” was
selected for “Assignment Reference”.
1
As of S/4HANA 2502 this configuration option is only active for
customers for “Assignment Reference” in case “Enable Inputs” is
selected AND “Aggregation on Carryforward” has not be activated,
i.e. the assignment reference detail is transferred by the balance
carryforward task from on fiscal year to the next one within group
reporting.
2
As soon as the “Aggregate on Carryforward” gets activated and this
change is saved, the configuration field is read only, i.e. a customer
cannot deselect this option again. A warning pop-up makes a
customer aware of this when the aggregation is getting activated.
i
With this changed configuration behavior the following is achieved:
1
➢ In case of customers that activate the content as of S/4HANA
2502 and upgrade customers that did not change the delivered
content setting of “Aggregate on Carryforward” for “Assignment
Reference”, the balance carryforward task does not transfer the
assignment reference detail from one fiscal year to the next one,
and customers cannot (directly) disable this aggregation.
2
Public
➢ In case of upgrade customers that deactivated the “Aggregate
on Carryforward” for “Assignment Reference” before S/4HANA
2502, the balance carryforward task continues to transfer the
assignment reference detail from one fiscal year to the next one
(i.e. no change in behavior). The configuration field is empty and
active, but when a customer activates the “Aggregate on
Carryforward” option for “Assignment Reference” and saves this
changed configuration, it is not possible any more to (directly)
switch this off again (for the displayed warning pop-up please
refer to the previous slide). But please also see next slide.
42
Limited Assignment Reference configuration to avoid unnecessary data volume – slide 5
Details regarding “Aggregate on Carryforward” for “Assignment Reference” - part 2
1
As described on the previous slide, the “Aggregate
on Carryforward” setting cannot directly be
deselected any more after it has been selected, as
the field turns read only.
2
When deselecting the “Enable Inputs” option for
“Assignment Reference”…
3
… automatically deselects the “Aggregate on
Carryforward” and disables the field. This is the
same behavior as for any other additional master
data field. With this the assignment reference detail
is still not carried over to the next fiscal year, as the
balance carryforward does not read the assignment
reference detail as it is not input enabled.
4
However when selecting the “Enable Inputs” option
again …
5
… the “Aggregate on Carryforward” setting stays
deselected and with that the assignment reference
detail is again transferred from one fiscal year to the
next one, which is not what SAP recommends.
i
This behavior is required for consistency reasons
and to avoid changes after system upgrade for
customers that actively deselected the “Aggregate
on Carryforward” option before S/4HANA 2502.
1
2
3
4
5
So this is neither a bug, nor should it be seen as
feature to switch off the aggregation for “Assignment
Reference”. SAP recommends to activate
“Aggregate on Carryforward” for “Assignment
Reference” to avoid unnecessary data volume.
Public
43
Prepare
Collect
Consolidate
Analyze
2502 release
Activity Based Consolidation of Investments (ABCOI)
Aggregation of additional master data fields during ABCOI
Additional master data field configuration – aggregation of fields during ABCOI – slide 1
Introduction
1
2
3
4
Public
1
As of S/4HANA 2502 a new column “Aggregate on Activity-Based COI” has
been introduced to the additional master data field configuration. This
provides flexibility in defining the level of granularity of ABCOI.
4 … whereas the information of additional master fields which are
!
In S/4HANA public cloud only customer systems which were set up before
S/4HANA 2402 allow to use ABCOI. Customer systems set up as of
S/4HANA 2402 do not allow to use ABCOI. Therefore in the latter systems
you won’t see the additional column.
i
2
3
Additional master data fields which are either not input enabled …
… or which are input enabled and “Aggregate on Activity-Based COI” has
been activated for, will be aggregated during ABCOI, …
input enabled, but for which the “Aggregate on Activity-Based
COI” has not been activated, will be kept during ABCOI.
The additional master data field configuration can be accessed
in solution builder via “Configure your Solution” → “Finance” →
“Corporate Close” → “Master Data” → “Define Consolidation
Master Data Fields”.
In case of CBC the additional master data field configuration can
be found under “Accounting” → “Group Valuation and Reporting”
→ “Data Model” → “Define Consolidation Master Data Fields”.
45
Additional master data field configuration – aggregation of fields during ABCOI – slide 2
Customer controlled toggle – part 1
1
2
3
4
i The feature to ignore or aggregate certain additional master data fields during the activity based consolidation of investments (ABCOI),
which is delivered with S/4HANA 2502 has to be activated by the customers via a customer controlled toggle, in order to avoid an
immediate day-1-impact after upgrade and give customers control when this impact shall occur.
Public
This toggle you find in the “Configure Your Solution” by selecting 1 the Application Area “Application Platform and Infrastructure”
→ 2 Sub Application Area “General Settings” → 3 Item “Basic Settings” → 4 Configuration Step “Activate Features”.
46
Additional master data field configuration – aggregation of fields during ABCOI – slide 3
Customer controlled toggle – part 2
2
3
3
4
1
5
1 As of S/4HANA 2502 the “Activate Features” configuration contains the
feature “FINCS_ADD_ABCOIAGGR_TO_FLDCONF” “Show column ‘Aggregate
Data on Activity Based COI’.
2
3
4
5
i
By selecting the feature and pressing the “Activate/Deactivate Feature” button …
… the feature can be activated, or deactivated.
Clicking the “i“ button in the “Documentation” column …
… opens the documentation of the feature in the “What’s New” documentation.
The feature toggle gives customers control on what is the best point in time to
activate the feature. However with S/4HANA 2508 the feature will be activated
for all customers in August 2025, as also stated in the “What’s New”.
Public
47
Additional master data field configuration – aggregation of fields during ABCOI – slide 4
Configuration Details – part 1
1
2
3
4
Availability of “Aggregate on Activity-Based COI” column:
1
In S/4HANA public cloud only customer systems which were set up
before S/4HANA 2502 allow to use ABCOI. Customer systems set
up as of S/4HANA 2502 do not allow to use ABCOI. Therefore in
the latter systems you won’t see the additional column.
The column is only available as of S/4HANA 2502 in systems
where a task with CACTT=40 and Dimension=Y1 is existing.
Customer systems set up as of S/4HANA 2402 do not have such a
task and therefore you won’t see this column in such systems.
Public
In addition the customer controlled toggle, mentioned on previous
slides, has to be activated by the customer to see this column.
Configuration settings and resulting behavior:
2
In case “Enable Inputs” is not set for an additional master data field, ABCOI is not
reading the field at all. With this the detail of the field is not kept in ABCOI, which is the
same effect as reading the field and then aggregating across the field.
3
In case “Enable Inputs” and “Aggregate on Activity-Based COI” is activated for an
additional master data field, ABCOI reads the field but then aggregates across the field.
The result is the same as in the case above: The detail of the field is not kept in ABCOI.
4
In case “Enable Inputs” is activated but “Aggregate on Activity-Based COI” is not
activated for an additional master data field, ABCOI reads the field and does not
aggregate across the field. With this the detail of the field is kept in ABCOI.
48
Additional master data field configuration – aggregation of fields during ABCOI – slide 5
Configuration Details – part 2
2
2
3
Configuration options for “Aggregate on Activity-Based COI”:
1
In case “Enable Inputs” is not set for an additional master data field, the “Aggregate on Activity-Based COI” cell is always cleared and disabled. ABCOI is not reading the field at all and
therefore there is nothing to aggregate or not aggregate across, and no configuration setting regarding aggregation is required.
2
In case “Enable Inputs” has been activated for an additional master data field, the “Aggregate on Activity-Based COI” cell is usually writing enabled and can either be selected or de-selected.
There are only two exceptions:
3
• When the “Aggregate on Activity-Based COI” option has been de-selected for a subordinate field (e.g. Profit Center), the “Aggregate on Activity-Based COI” cell for the superordinate field
(e.g. Controlling Area) is cleared and disabled. This is the same behavior as in the “Aggregate on Carryforward” and “Aggregate Data on Release” column. The reason is that it does not
make sense to keep the detail of the subordinated field (e.g. Profit Center) without keeping the detail of the superordinate field (e.g. Controlling Area). As soon as “Aggregate on ActivityBased COI” has be activated for all subordinate fields, the “Aggregate on Activity-Based COI” cell for the superordinate field is writing enabled and can either be selected or de-selected.
i
• Greenhouse gas emission (GHG) fields are not supported end-to-end by ABCOI. Therefore the “Aggregate on Activity-Based COI” is enabled in any case and the setting cannot be
removed by the customer, i.e. the respective configuration fields are always read only.
i
Public
With this, aggregation during ABCOI is in principle possible for all additional master data fields.
49
Additional master data field configuration – aggregation of fields during ABCOI – slide 6
Configuration Details – part 3
1
2
Content delivery:
1
For systems that were set up before S/4HANA 2402 but where the scope item 1SG is activated only after the upgrade to S/4HANA 2502, each
additional master data field is either be set to not input enabled …
2
i
… or input enabled and “Aggregate on Activity-Based COI” activated.
Therefore after content activation, ABCOI will either not read an additional master data field, or it will read the field but then aggregate across the
field. With that ABCOI by default will not keep the detail of any additional master data field.
In case a different behavior is required, the additional master data field configuration has to be adjusted accordingly by the customer.
Public
50
Additional master data field configuration – aggregation of fields during ABCOI – slide 7
Configuration Details – part 4
1
2
3
Upgrade customers:
Public
1
In case systems are upgraded to S/4HANA 2502, “Aggregate on Activity-Based COI” is not activated for any of the additional master data fields directly
after system upgrade, except for the greenhouse gas emissions (GHG) fields.
2
In case of additional master data fields which are input enabled this means, that ABCOI is keeping the detail of such a field, as the “Aggregate on
Activity-Based COI” is not activated. This is the same behavior as before the upgrade, where no aggregation was possible at all.
3
In case of additional master data fields which are not input enabled this means, that ABCOI is not reading this field at all what has the same effect as
aggregating across the field. This behavior is different than before the upgrade. Before S/4HANA 2502 all fields, including the ones which are not input
enabled, were read by ABCOI. With this the behavior of ABCOI changes. In order to avoid a day-1-impact for upgrade customers, this changed reading
behavior was put behind the same customer controlled toggle as the aggregation of fields during ABCOI. With this customers have control, when this
impact shall occur.
51
Prepare
Collect
Consolidate
Analyze
2502 release
Support FS Item and cons unit attribute
special version assignment to GRPL
Group Reporting Preparation Ledger (GRPL) Configuration
Support FS item and cons unit attribute special version assignment to GRPL – slide 1
Overview
2
i
The configuration of group reporting preparation ledgers (GRPL) can be accessed:
i
Note: For all group reporting preparation ledgers which belong to the same ledger
stack (of base ledger and extension ledgers) the same “FS Item Attributes Version”
and the same “Consolidation Unit Attributes Version” have to be assigned. When
you try to assign different versions to such ledgers, you’ll receive an error and
won’t be able so save your configuration.
i
Together with the fiscal year and period of an accounting posting, these GRPL
attributes are as of S/4HANA 2502 used to identify time- and version-dependent
FS item or consolidation unit attribute values which are used in the precondition of
a substitution rule in the business context “GRPL core fields” or “GRPL
subassignments to FS item” for accounting postings.
➢ In SSCUI via: Manage Your Solution → Configure Your Solution → Finance →
Corporate Close → Basic Settings → Define Group Reporting Preparation Ledgers
➢ In CBC via: SAP Business Configuration → Accounting → Group Valuation and
Reporting → Integration with S4HANA Cloud Accounting → Define Group Reporting
Preparation Ledgers
1
As of S/4HANA 2502 you can assign a “Consolidation Unit Attribute Version” as
optional attribute to a GRPL configuration.
2
An “FS Item Attributes Version” may already be assigned as optional attribute to a
GRPL configuration since S/4HANA 2202, however it was not yet consumed anywhere.
Public
1
For further details please refer to the subsequent slide.
53
Support FS item and cons unit attribute special version assignment to GRPL – slide 2
Consumption in substitution rules for accounting
2
3
1
1
When you create a substitution rule in the “Manage Substitution and Validation Rules –
Group Journal Entries” app using the business context “GRPL core fields” or “GRPL
subassignments to FS item”, you now get in the field catalog …
2
i
… the time- and version-dependent cons unit attributes and FS item attributes offered.
You may use these attributes in the definition of the precondition of the substitution rule.
Based on the ledger of the accounting posting the respective FS item attributes and/or
cons unit attributes version is derived from the group reporting preparation ledger
configuration. Together with the fiscal year and period of the accounting posting, the
derived version(s) is/are used to identify FS items and/or cons units, which have
assigned the time- and version-dependent FS item and/or consolidation unit attribute
value, that is specified in the precondition.
3
Public
In this example all cons units would be identified as precondition that have the currency
translation method “S0903” assigned in the derived consolidation unit attributes version
in the fiscal year and period of the accounting posting.
54
Prepare
Collect
Consolidate
Analyze
2502 release
Support of additional consolidation hierarchy types
& other changes in the Manage Consolidation
Hierarchies app
Support of additional hierarchy types in “Manage Consolidation Hierarchies” app
1
1 As of S/4HANA 2502 the following additional hierarchy
types are supported in the “Manage Consolidation
Hierarchies” app:
• Consolidation Billing Document Type
• Consolidation Distribution Channel
• Consolidation Division
• Consolidation Industry
• Consolidation Plant
• Consolidation Product Sold Group
• Consolidation Sales District
i As for any other additional master data field hierarchy,
these hierarchy types are available in the “Manage
Consolidation Hierarchies” app as soon as “Enable
Hierarchy” has been activated for the respective field in
the additional master data field configuration.
Public
56
Consolidation Material Group hierarchies now are time-dependent
1 As of S/4HANA 2502 the “Consolidation Material Group”
hierarchies are time-dependent, i.e. a validity timeframe
has to be entered.
The time-dependency works as in any other timedependent hierarchy type.
i Remark with regards to Consolidation Material Group
hierarchies that were created before S/4HANA 2502:
1
Consolidation Material Group hierarchies which were
created before S/4HANA 2502 will still be shown with a
validity timeframe “N/A” in the “Manage Consolidation
Hierarchies” app after system upgrade to S/4HANA 2502.
In case these hierarchies had been activated before
system upgrade, the runtime will treat them in a way, as if
they had the validity timeframe “01/01/1900 –
12/31/9999”. From this perspective there is no need for
immediate action!
1
Even changes of such a hierarchy can be maintained and
saved.
Only in case you want to activate such a hierarchy after
the upgrade to S/4HANA 2502 you have to enter a
validity timeframe in order to be able to do so.
In case you did not enter a validity timeframe for such a
hierarchy and try to activate it, you’ll receive an activation
error. After maintaining the validity timeframe the
activation will be possible.
Public
57
Prepare
Collect
Consolidate
Analyze
2502 release
Import Consolidation Master Data app now
supports all master data types & further
improvements
Import Consolidation Master Data app now supports all additional master data types – slide 1
Situation before S/4HANA 2502
Before S/4HANA 2502 there were two apps for
consolidation master data import:
2
1
4
1 1. The “Import Consolidation Master Data” app,
which supported consolidation units, consolidation
groups, consolidation group structures, FS items,
profit centers, segments, as well as the newly
introduced industry fields (for public sector and
financial services industry) and greenhouse gas
fields, …
2
… which was launched via the “Import
Consolidation Master Data” tile on the Fiori
launchpad.
3 2. The “Import Master Data for Consolidation Fields”
app, which supported all other additional master
data fields, such as cost centers, functional areas,
and all other additional master data fields, which
were configured as master data enabled in the
additional master data field configuration, …
3
4
Public
… which was launched via the “Import Master
Data for Consolidation Fields” link in the “Import
Consolidation Master Data” app.
59
Import Consolidation Master Data app now supports all additional master data types – slide 2
Situation as of S/4HANA 2502
2
i As of S/4HANA 2502 there is only a single app
remaining for consolidation master data import.
1 All master data types, i.e. consolidation units,
consolidation groups, consolidation group
structures, FS items, and all additional master
data fields, which are configured as master data
enabled in the additional master data field
configuration, can now be imported via the
“Import Consolidation Master Data” app.
1
2 As before S/4HANA 2502 this app is launched via
the “Import Consolidation Master Data” tile on the
Fiori launchpad.
Public
60
Import Consolidation Master Data app now supports all additional master data types – slide 3
Benefits of integration into Import Consolidation Master Data app
Old download file in “Import Master Data for Consolidation Fields” app:
6
i
1
4
Besides having all consolidation master data types covered in a single import application, instead of using two separate import
applications, which is obviously already one big advantage, the integration into the “Import Consolidation Mater Data” app has also
further advantages:
Language handling:
1
In the old download files there was no language indicator. The language of the descriptions in the download file, and the language
the descriptions of an upload file were stored into, was determined by the logon language of the user. In order to download or
upload descriptions in several languages, the user had to log on in different languages, which of course also impacted the
language of the UIs and menus.
2
In the “Import Consolidation Master Data” app the user chooses the language of the downloaded descriptions in a selection screen
of the download dialog. The language key is then part of the download file and also determines the language into which the
descriptions are imported. With this users logon in their preferred logon language, but still can download and import descriptions in
all required languages. Accidentally importing descriptions into the wrong language by using a logon language that does not fit to
descriptions in the import file is not happening any more.
New download file in “Import Consolidation Master Data” app:
Filtering:
i
2
While the old download only supported the download of all additional master data values of a master data type (e.g. all G/L
accounts of all G/L chart of accounts maintained as additional master data values in group reporting), it is possible in the “Import
Consolidation Master Data” app to filter the master data download, e.g. with regards to certain values of the superordinate field
(e.g. download G/L accounts for selected G/L chart of account(s)).
Value helps:
5
3
While the old download files in the “Import Master Data for Consolidation Fields” app had no value helps, value helps are now
available for the superordinated field (e.g. G/L Chart of Accounts) and language.
Column headers:
4
While in the old download files in the “Import Master Data for Consolidation Fields” app the column headers were completely
generic (e.g. “Master Data ID”, “Superordinate Field Value”) and had not information on the maximum length, …
5
… templates and download files in the “Import Consolidation Master Data” app contain master data type specific column headers
(e.g. “G/L Chart of Accounts” and “G/L Account”) and also show for each column the maximum length which is accepted (e.g. “(4)”,
“(10)”, …).
3
Superordinate field column:
6
Public
While in the old download files in the “Import Master Data for Consolidation Fields” app the column “Superordinate Field Value” is
shown even for master data types which do not have such a superordinate field (e.g. Segment, Functional Area, etc.), templates
and download files in the “Import Consolidation Master Data” app only contain such a column in case it is relevant for the
61
respective master data type.
Import Consolidation Master Data app now supports all additional master data types – slide 4
Further remarks for upgrade customers
Usage of already existing import files:
i In case you already prepared import files for the “Import Master Data for Consolidation Fields” app
1
before the S/4HANA 2502 upgrade, these files need to be adjusted, in order to be uploaded with the
“Import Consolidation Master Data” app after the S/4HANA 2502 upgrade:
1. Download an empty template by selecting the relevant master data type in the overview screen of
the “Import Consolidation Master Data” app and pressing the “Download Template” button (also see
next slide for screenshots).
Note: For each master data type a separate template has to be downloaded.
New download file in “Import Consolidation Master Data” app:
2
1 2. Copy field content from the columns “Master Data ID”, “Superordinate Field Value” (if applicable for
the master data type”, and “Description” from the old import file into the respective columns of the
template.
Note: Only copy the field content of the master data type of the new template!
2 3. Select the relevant language key of the descriptions.
4. Save the filled template, which then can be uploaded into the “Import Consolidation Master Data”
app.
Download, upload, and import multiple master data types:
i As already mentioned, the “Import Consolidation Master Data” app requires separate downloads and
import files per master data type. Downloading, uploading, and importing multiple master data types, as
it was possible with the download “- All Master Data Types -“ option and the import of mixed import files
(as shown in the screenshot on the upper left hand side) in the “Import Master Data for Consolidation
Fields” app, is not yet possible.
It is planned to regain that functionality in a future release.
Public
62
Import Consolidation Master Data app – changes on overview screen
Changed user interaction for download actions on overview screen
Download actions before S/4HANA 2502:
Download actions as of S/4HANA 2502:
3
4
1
7
6
2
5
1
Before S/4HANA 2502 every row in the table of the overview screen
had a separate “Actions” dropdown …
3
As of S/4HANA 2502 these actions are available as separate buttons in the header of the table
of the overview screen.
2
… which contained the same two actions “Download Template” for
downloading an empty template and “Download Master Data” for
downloading the template filled with already existing master data.
4
In addition a single row of the table can now be selected. As long as no row has been selected
the action buttons “Download Master Data” and “Download Template” are inactive.
5
6
7
As soon as a row in the table has been selected …
Public
… the action buttons become active and work with the context of the selected master data type.
The “Upload” button works independently from the selection of the master data type in the
63
table, i.e. the appropriate master data type is derived from the content of the upload file.
Prepare
Collect
Consolidate
Analyze
2502 release
Partner Fund available as additional
industry scenario field for public sector
Public Sector Fields in Group Reporting
Industry scenario fields for public sector – slide 1
Introduction
1
2
1
1 As of S/4HANA 2408 five industry specific fields for public sector were made available in group reporting:
•
•
•
•
•
Financial Management Area (FinancialManagementArea)
Fund (Fund)
Grant (GrantID)
Cash Origin Chart of Accounts (CnsldtnCashLedgerChartOfAccts)
Cash Origin Account (CashLederAccount)
2 As of S/4HANA 2502 one more industry specific field for public sector is available in Group Reporting:
• Partner Fund (PartnerFund)
i
Public
These industry specific fields are only available within group reporting, once a customer has activated them via a business function.
Once activated, these fields behave according to their additional master data field configuration settings as any other additional master
data field. For further details please refer to the subsequent slides.
65
Industry scenario fields for public sector – slide 2
Activation of public sector industry scenario fields – part 1
i The industry scenario fields for
public sector have to be
activated by the customer via
business function in order to
make them available in group
reporting. Only when the
business function has been
activated the public sector fields
will be visible and processed in
group reporting.
1
2
1 The activation of the business
functions can be accessed in
solution builder via “Configure
your Solution” → “Finance” → …
3
2 … “Corporate Close” → …
3 … “Basic Settings” → …
4 … “Activate Fields for Public
Sector”.
i In case of CBC the business
4
Public
functions can be found under
”Accounting” → “Group
Valuation and Reporting” →
“Data Model”
66
Industry scenario fields for public sector – slide 3
Activation of public sector industry scenario fields – part 2
1
2
3
1
In this screenshot you see the configuration activity to enable
the public sector industry scenario fields in group reporting.
2
As you can see the business function is currently switched off.
3
4
By selecting “Change State” …
… the business function is getting activated.
With this the industry scenario fields for public sector become
available in group reporting in the system. This includes the
public sector fields which were made available in group
reporting with S/4HANA 2408 as well as S/4HANA 2502.
4
Public
i
In case a customer activated the business function “Enable
Public Sector Fields in Group Reporting” even before the
upgrade to S/4HANA 2502 took place, the additional Partner
Fund field which is provided with S/4HANA 2502 will be
immediately available in group reporting after system upgrade.
But it is configured in a way that the system behavior does not
change. In order to make use of the field the configuration of the
field in the additional master data fields configuration has to be a
changed accordingly.
5
By selecting “Change State” in a situation where the business
function is active, the business functions is deactivated and the
respective industry fields are not available in group reporting
any more.
i
Please note: The deactivation of the business function is not
possible in productive systems, but only in development and test
systems. Once switched on in a productive system, or
transported as switched on into a productive system, it cannot
be switched off any more.
67
5
Industry scenario fields for public sector – slide 4
Additional master data field configuration for public sector industry scenario fields
Business function for public sector industry fields switched on:
Business function for public sector industry fields switched off:
1
2
1
When the business function for the public sector industry scenario is
switched off, the public sector industry scenario fields are not available in
the additional master data field configuration.
Also in other places such as for example manual posting or analytics these
fields will not be present.
Public
2
Only when the business function for the public sector industry scenario is
switched on, the public sector industry scenario fields are visible in the
additional master data field configuration and with that can be configured.
Note: In case the standard configuration (delivered via content) for some
public sector fields is changed and subsequently the business function is
deactivated, the configuration settings are not deleted, but any kind of
configuration will be ignored in group reporting.
68
Industry scenario fields for public sector – slide 5
Additional master data field configuration for public sector industry scenario fields
1
2
3
1 Here you can see the standard configuration which is delivered via content for the public sector industry scenario fields:
2 • All fields except Partner Fund are enabled for input (e.g. postings). For Partner Fund the “Enable Inputs” is inactive
to avoid any day one impact for upgrade customers that already have activated the business function for public
sector fields, but it may be activated at any point in time.
3
•
•
Global hierarchies are supported for Fund, Partner Fund, Grant, and Cash Origin Account. However by default only
hierarchies for Fund, Partner Fund, and Grant are enabled.
Note: As the “Enable Hierarchy” setting for Cash Origin Account and Partner Fund is taken over from the referenced
characteristic (i.e. G/L Account and Fund), it may happen that for upgrade customers Cash Origin Account is
hierarchy enabled after activation of the business function, or Partner Fund is not hierarchy enabled after upgrade.
This happens in case the customer activated hierarchy enablement for G/L Account before activation of the
business function for public sector fields, or deactivated the hierarchy enablement for Fund before upgrade.
Public
5
6
6
7
•
Hierarchical elimination is not supported for any of the fields.
•
Aggregation on balance carry forward is supported for all fields but not active, i.e.
the information of these fields is by default carried forward into the next fiscal year
within group reporting.
All six fields are enabled for additional master data values in group reporting.
Note: As the “Enable Master Data” setting for Cash Origin Chart of Accounts, Cash Origin Account, and Partner
Fund is taken over from the respective referenced characteristic (i.e. Chart of Accounts, G/L Account, and Fund), it
may happen that for upgrade customers Cash Origin Chart of Accounts, Cash Origin Account, and/or Partner Fund
are not master data enabled after upgrade or activation of the business function. This happens in case the customer
deactivated master data enablement for Chart of Accounts, G/L Account, and/or Fund before upgrade.
4
5
4
Note: The “Aggregate on Carryforward” option for Financial Management Area and
Cash Ledger Chart of Accounts can only be activated when it has been activated
for the referencing field (i.e. Fund and Cash Ledger Account) as well. Partner Fund
inherits its setting for “Aggregate on Carryforward” from the referenced field Fund.
7 •
Aggregation on release of universal journal is supported for all fields but not active
(except for Partner Fund), i.e. the information of these fields is by default
transferred from accounting to group reporting. For Partner Fund the “Aggregate
Data on Release” is activated to avoid any day one impact for upgrade customers
that already have activated the business function for public sector fields, but it may
be deactivated at any point in time.
Note: The “Aggregate Data on Release” option for Financial Management Area and
Cash Ledger Chart of Accounts can only be activated when it has been activated
for the referencing field (i.e. Fund and Cash Ledger Account) as well.
69
Industry scenario fields for public sector – slide 6
Behavior of public sector industry scenario fields in group reporting
i Apart from the specialty that the industry specific fields for public sector are only available within group reporting, once a customer has activated them via a business
function, they basically behave according to their additional master data field configuration settings as any other additional master data field.
For example they are available in the following applications, tasks, queries, and cubes:
Applications:
Tasks:
• Define Master Data for Consolidation Fields
• Release Universal Journal
Note: Due to the referenced characteristics additional master data values for Cash
Origin Account have to be maintained under the characteristic G/L Account in the app,
for Cash Origin Chart of Accounts under Chart of Accounts, and for Partner Fund
under Fund.
• Balance Carry Forward
• …
• Import Consolidation Master Data
Note: Due to the referenced characteristics master data values for Cash Origin
Account have to be maintained under the characteristic G/L Account in the app, for
Cash Origin Chart of Accounts under Chart of Accounts, and for Partner Fund under
Fund.
• Manage Consolidation Hierarchies
Note: Due to the referenced characteristic consolidation hierarchies for Cash Origin
Account have to be maintained under the characteristic G/L Account in the app, and for
Partner Fund under Fund.
• Define Selections
Queries:
• Balance Sheet – Query
(C_CnsldtnBalanceSheetQ)
• Cash Flow Statement
(C_CnsldtnCashFlowQ)
• Income Statement - Function of Expense (C_CnsldtnIncStmntFuncOfExpnQ)
• Income Statement - Nature of Expense
(C_CnsldtnIncStmntNatrOfExpnQ)
• Group Data Analysis
• Group Data Analysis - With Reporting Rules
• Group Financial Statements - Review Booklet
• Display Group Journal Entries
• Display Group Journal Entries - With Reporting Logic
Public
Cubes:
• Group Reporting Data - Cube
(I_CnsldtnGrpJrnlItemC)
• Rule-Based Group Data Analysis - Cube
(I_CnsldtnRuleBsdGrpJrnlItemC)
70
Prepare
Collect
Consolidate
Analyze
2502 release
Support of prior periods modes
Release Universal Journal
Release universal journal – support of prior periods modes – slide 1
Overview
1
As of S/4HANA 2502 the release universal journal (RUJ) task supports
two prior periods modes (one for complete data in prior periods, one for
delta data in prior periods) for the accounting integration with group
reporting preparation ledger and versions that are not a planning version.
i
The RUJ task can be executed in prior periods mode via the “Start with
Selection” option in the data monitor, or via scheduling a job in the
“Schedule Jobs for Consolidation Tasks” app.
The basic idea of the prior periods modes is, that accounting data from
periods before the current execution period needs to be processed (e.g.
because of late coming postings). As these periods may already be
closed, this would require re-opening of the periods and re-processing
the RUJ task (in current period mode) as well as all subsequent
consolidation tasks in respective periods.
1
The prior periods modes allow to process accounting data in prior
periods which may already be closed and to transfer the result of the
processing into the execution period. In case the RUJ task is for example
executed in “Prior Periods – Delta” mode in period 3, it may transfer late
coming postings in periods 1 and 2 into period 3. Periods 1 and 2 may
stay closed in consolidation.
While data transferred by RUJ task in current period mode is still on
document type 0F, data transferred by RUJ task in one of the prior
periods modes is stored on a separate document type 0I.
Public
!
For the resulting data on document type 0I drill-through to accounting
data cannot be supported. Therefore the execution of RUJ task in prior
periods mode should be the exception.
i
Another use case besides the late coming postings is to transfer data
from prior periods including the opening balances (i.e. data from period
0). This is especially relevant to create a starting point for a consolidation
unit in group reporting.
For further details on the RUJ task in prior periods mode please
refer to subsequent slides.
72
Release universal journal – support of prior periods modes – slide 2
High level concept – use case of late coming postings – part 1
1 In the use case of late coming postings,
data that was posted in accounting in
prior periods (i.e. periods 1 and 2 in the
example) was transferred to group
reporting as usual via RUJ task in current
period mode on document type 0F.
Period 1
Period 2
2
Data in
Accounting
1
Period 3
2 After transferring data to group reporting
(maybe even after periods 1 and 2 were
closed in group reporting) late coming
postings were posted in accounting.
2
1
4
Data in
Group Reporting
Data in accounting that was posted in time
Late coming postings in accounting
Data transferred to group reporting with RUJ task in current period mode on document type 0F
Data transferred to group reporting with RUJ task in prior periods mode on document type 0I
3 Instead of re-processing RUJ task in
3
3
periods 1 and 2 in current period mode
(which may require re-opening of periods
in group reporting and/or re-processing of
subsequent consolidation tasks), RUJ
task is executed in period 3 in “Prior
Periods – Delta” mode. It transfers any
not yet released data from periods 1 and
2 (which covers exactly the late coming
postings) to execution period 3 on a
dedicated document type 0I.
4 Accounting data of period 3 is not
processed by the RUJ task in prior
periods mode and is still transferred to
group reporting using RUJ task in current
period mode.
Public
73
Release universal journal – support of prior periods modes – slide 3
High level concept – use case of late coming postings – part 2
1 Late coming postings from periods 1 and 2 were transferred
Period 1
5
Period 2
to group reporting via RUJ task in “Prior Periods – Delta”
mode in period 3 on document type 0I.
Period 3
2 In case the RUJ task is re-processed after that in a prior
Data in
Accounting
period (e.g. period 2), for which data was already transferred
to a later period by RUJ task in prior periods mode, in
current period mode (no matter whether in “Current Period –
Complete Data” or “Current Period – Delta” mode), the late
coming postings from that period will be transferred once
more to that period (i.e. period 2) on document type 0F.
2
1
Data in
Group Reporting
7
6
3
4
Data in accounting that was posted in time
Late coming postings in accounting
Data transferred to group reporting with RUJ task in current period mode
Data transferred to group reporting with RUJ task in prior periods mode
Data transferred to group reporting with subsequent RUJ task in current period mode causing duplicates
“Negative” delta posting by RUJ task in “Prior Periods – Complete Data” mode removing duplicates
* Similar effects with duplicate data may occur in other constellations, e.g. when executing RUJ task in “Prior Periods – Complete Data” mode for a subset of
periods (e.g. in period 4 for periods 1 to 3) than it had been executed before (e.g. in period 6 for periods 1 to 5). In that case data from periods 1 to 3 which
has already been transferred to period 6 is now transferred to period 4 again.
It is also possible that effects with missing data occur. E.g. when executing RUJ task in “Prior Periods – Complete Data” mode for a prior periods interval
(e.g. execution in period 6 for periods 3 to 5) that overlaps only partially with the interval of prior periods including execution period of a previous RUJ task
execution in that mode (e.g. execution in period 3 for periods 1 and 2). In that case data from periods 1 and 2 which has already been transferred to period
3, will be taken into account during delta calculation for period 6, and with that will be missing when looking at YTD values in period 6 afterwards.
In all of these situations a warning message will be shown, that missing or duplicated data might be created and all of these issues may be corrected
afterwards by re-processing the RUJ task in “Prior Periods – Complete Data” mode for a certain period interval, as also described in the example.
** Please note that for technical reasons the several records may be created on group reporting side which only in total reflect this delta, this may even
happen in case the overall delta is zero.
Public
The reason is that the RUJ task in current period mode only
takes into account timestamps of other RUJ tasks in current
period mode in case of delta mode or data created by other
RUJ tasks in current period mode (i.e. data on document
type 0F) in case of complete data mode.
3 So the data is now in group reporting twice (in period 3 on
document type 0I and in period 2 on document type 0F)*.
4 This can be corrected by re-processing RUJ task in period 3
in “Prior Periods – Complete Data” mode for periods 1 and
2. This compares complete accounting data from periods 1
and 2 ( 5 ) with complete data transferred by any kind of
RUJ task (i.e. current period and prior periods mode) in
periods 1 and 2 ( 6 ) plus data transferred by RUJ task in
prior periods mode in period 3 ( 7 ). The resulting delta
( 4 ) is posted to the execution period 3**. In our example
this delta is “negative”, i.e. it removes exactly the late
coming postings from period 2 which were already
transferred to period 3, before they were transferred to
period 2 as well.
! In case the RUJ task is executed in “Prior Periods – Delta”
mode only, but not in “Prior Periods – Complete Data” mode
and in case RUJ task is not executed in any of the current
period modes for a period which was already processed by a
RUJ task in prior periods mode, such effects may not occur.
74
Release universal journal – support of prior periods modes – slide 4
High level concept – use case of creating starting point for cons unit
i
Period 0
Period 1
2
Period 2
Period 3
Data in
Accounting
6
Data in
Group Reporting
1
5
3
4
Data in accounting (including opening balances in accounting in period 0)
Data transferred to group reporting with RUJ task in prior periods mode on document type 0I
Data transferred to group reporting with RUJ task in current period mode on document type 0F
*
In our example nothing has been transferred into these periods so far, but it also works in case data has already been transferred into
these periods.
** Of course before the first execution of RUJ task in period 3 in prior periods mode, there is not such data. But in case the RUJ task is reprocessed in period 3 in “Prior Periods – Complete Data” mode for periods 0 to 2, the already existing data would be taken into account.
*** Please note: In order to make this work end to end without the need for realignment and without subsequent issues, the data which is
transferred by the RUJ task in “Prior Periods – Complete Data” mode needs to have filled the group reporting specific fields in universal
journal as of period 0 of the fiscal year in which you execute the RUJ task. I.e. already when the balance carry forward in accounting is
executed, the prerequisites for the group reporting field derivation have to be fulfilled.
As the RUJ task only incorporates accounting data as well as data transferred by RUJ task execution into the calculation of the delta to
be posted, inconsistencies (in the sense of duplicated data) may be created in case the opening balances of a cons unit were already
created with a different mechanism (e.g. via flexible file upload or GRDC data mapping). A respective warning is shown in most relevant
cases. Please see here for more details.
Public
As of S/4HANA 2502 it is possible to use the RUJ
task in a more convenient way, to create a starting
point for a cons unit in group reporting, for with
accounting data is existing in S/4HANA already for
a longer period in time (e.g. several years).
Before S/4HANA 2502 the RUJ task could not
process accounting data in period 0. Therefore
RUJ would have to be executed for every prior
period (back to ultimo) separately in current period
mode, as well as subsequent consolidation tasks
as currency translation, …, and BCF. In case the
respective company exists in accounting for a
longer period in time already this is practically not
feasible.
1 As of S/4HANA 2502 it is possible to transfer data
of period 0 up to the period before the execution
period of the RUJ task into the execution period
using the “Prior Periods – Complete Data” mode.
In our example RUJ task is executed in period 3
for periods 0 to 2 in that mode. This compares
complete accounting data from periods 0, 1, and 2
( 2 ) with complete data transferred by any kind of
RUJ task (i.e. current period and prior periods
mode) in periods 0, 1, and 2 ( 3 )* plus data
transferred by RUJ task in prior periods mode in
period 3 ( 4 )**. The resulting delta ( 5 ) is
posted to the execution period 3 on the document
type 0I for prior periods execution. In our example
this delta is the complete accounting data from
periods 0, 1, and 2.***
6 As of period 3 the ongoing accounting data can be
transferred via RUJ task in current period mode.
75
Release universal journal – support of prior periods modes – slide 5
Access via selection screen – part 1
2
1
1
Via the context menu of the RUJ task in the data monitor you can select the
“Start with Selection” option for the RUJ task.
2
The selection screen for the RUJ task now contains two new RUJ modes in the
“Selection Mode” section:
• Prior Periods – Complete Data
• Prior Periods – Delta
!
Public
Note: The “Delta for Prior Periods” option, which used to be available before
S/4HANA 2502, was removed. In case of accounting integration with group
reporting preparation ledger the same result is achieved by using the “Prior
Periods – Delta” mode in “Test Run”. In case of classic integration the RUJ task
has to be executed separately in any of the prior periods in “Current Period –
Delta” mode in “Test Run”, as the prior periods modes are not available in case
of classic integration.
76
Release universal journal – support of prior periods modes – slide 6
Access via selection screen – part 2
1
In case one of the two prior periods modes of RUJ task:
• Prior Periods – Complete Data
• Prior Periods – Delta
has been chosen in the “Selection Mode” section, …
1
2
… an additional section “Prior Periods Selection” is shown on the selection
screen. In this section the periods are specified, which should be
processed by the RUJ task in prior periods mode. This is always a range of
periods with a lower and an upper boundary (both can have the same
value, in that case the range only consists of a single period).
3
The upper boundary of the prior periods interval is predefined with the
execution period minus 1 and cannot be changed. The reason, why the
range does not include the current execution period is, that for the resulting
data from a prior periods mode execution the drill-through to accounting
source data cannot be supported. With that the prior periods mode should
only be used as an exception in case e.g. the periods to be processed are
already closed and shall not be reopened again. The current execution
period needs to be open (otherwise also the RUJ task in prior periods
mode could not be executed). Therefore data for the current period can
and shall be transferred by using a current period mode, so that a drillthrough may be performed for the resulting data.
4
The lower boundary of the prior periods interval is defaulted with 1 but may
be changed to any period between 1 and the predefined upper boundary.
2
4
3
5
Note: You cannot use period 0 as lower boundary of the prior periods
interval in the selection screen. To transfer data as of period 0 (i.e.
including the opening balances), you must schedule the RUJ task, using
the “Release Universal Journals – Prior Periods including Opening
Balances” job template.
5
Public
Clicking the “i” button besides the prior periods selection, opens a pop-up
with the explanation of the prior periods interval and the rules for the same.
77
Release universal journal – support of prior periods modes – slide 7
Access via selection screen – part 3
1 In two cases the prior periods mode options are inactive and cannot be
selected:
1. In case the selection screen is opened with a fiscal year that is not equal
or later than the “From Year for Preparation Ledger”.
The prior periods mode of RUJ task is only supported in case of
accounting integration with group reporting preparation ledger, i.e. as of
the ”From Year for Preparation Ledger” in your global system settings. In
any fiscal year before the ”From Year for Preparation Ledger” this mode is
not supported and therefore the option cannot be selected.
1
2. In case the selection screen is opened in period 1 of a fiscal year.
Using the “Start with Selection” option in data monitor, the prior periods
modes of the RUJ task can only process data as of period 1 up to the
period before the execution period (i.e. the period you selected in data
monitor). For example, when you execute the RUJ task in period 5, it can
process data as of period 1 up to period 4. It cannot process data from
period 0. Therefore, this mode is not supported in period 1 as there is no
period before the execution period 1 that could be processed.
Consequently, this option cannot be selected when you execute the RUJ
task in period 1 using the “Start with Selection” option.
Note: To transfer data as of period 0 (i.e. including the opening balances),
you must schedule the RUJ task using the “Release Universal Journals –
Prior Periods including Opening Balances” job template.
Public
78
Release universal journal – support of prior periods modes – slide 8
Access via selection screen – part 4
1 In the “Prior Periods – Delta” mode of the RUJ task, the system only processes universal journal
3
1
4
data, …
2 … that has been posted for the selected prior periods since the last release for the respective
combination of period and consolidation unit. Any kind of RUJ task execution is taken into
account, it doesn't matter if the last release has been in current period mode or prior periods
mode.
2
Selected data of the prior periods is written into the current period using a dedicated document
type 0I for prior periods release.
This mode is appropriate to process late coming postings in prior periods without reopening
respective periods and/or re-processing RUJ task as well as subsequent consolidation tasks in
these periods.
Note:
• You cannot perform a drill-through to accounting source data for the released data in prior
periods mode.
• In case data (e.g. late coming postings) of a prior period (e.g. period 2) was transferred by
RUJ task in prior periods mode to a later period (e.g. period 3) and subsequently the RUJ
task is re-processed in that prior period in current period mode, the same data will be
transferred once more into the prior period using document type 0F for periodic release.
In order to remove duplicate data on document type 0I, the RUJ task has to be re-processed
in the later period (i.e. period 3 in the example above) in “Prior Periods – Complete Data”
mode.
3 By pressing the “Details about Last Release” button, a pop-up is shown with an overview of the
timestamps of the last release per combination of period and consolidation unit.
4
Public
Detailed information on the “Prior Periods – Delta” mode the user can get by clicking the “i“ button.
79
Release universal journal – support of prior periods modes – slide 9
Access via selection screen – part 5
3
1
4
1 In the “Prior Periods – Complete Data” mode of the RUJ task, …
2 … the system reads the universal journal data for selected prior periods, independently from
any time stamp of a previous data release. If you released universal journal data for the
selected periods already before, this data will be selected again. Furthermore, data that has
been created since the last release of universal journal will be selected as well.
2
The system compares the universal journal data selected as described above with the universal
journal data already released to group reporting for the selected prior periods in previous runs.
Any kind of RUJ is taken into account, it doesn't matter if the release has been in current period
mode or prior periods mode.
If the newly released amounts differ from the amounts of the previous runs, delta postings are
created in current period using a dedicated document type 0I for prior periods release.
This mode is appropriate to remove duplicates resulting from executing RUJ task in prior
periods mode and subsequently re-processing the RUJ task in prior periods in current period
mode (for a description how such duplicates are created, please also see previous slide).
There are also some other very special cases where this mode is appropriate. For further
information see the pop-up which can be launched by pressing the “i“ button.
Note:
• You cannot perform a drill-through to accounting source data for the released data in prior
periods mode.
3 By pressing the “Details about Last Release” button, a pop-up is shown with an overview of the
timestamps of the last release per combination of period and consolidation unit. This is for
information only, as previous RUJ task executions and their timestamps do not have any impact
on the RUJ task execution in “Prior Periods – Complete Data” mode.
4
Public
Detailed information on the “Prior Periods – Complete Data” mode the user can get by clicking
the “i“ button.
80
Release universal journal – support of prior periods modes – slide 10
Access via job scheduling – part 1
i
The RUJ task can also be executed in prior periods mode by scheduling
the RUJ task. In the “Schedule Jobs for Consolidation Tasks” app there
are two job templates which can be used:
1
1. “Release Universal Journals”
In principle this is the job template for the RUJ task, that was already
available before S/4HANA 2502. This job template was enhanced with
the prior periods mode options and you can do exactly the same what
was already described in the context of “Start with Selection”.
Additionally some other enhancements were implemented.
1
2
2
This is a new job template. Using this job template the RUJ task is
scheduled exclusively in “Prior Periods – Complete Data” mode, and
always works as of period 0 up to the period before the scheduled
execution period. This job template was specifically designed to
create a starting point for a consolidation unit in group reporting using
the RUJ task.
i
Public
2. “Release Universal Journals – Prior Periods including Opening
Balances”
For further details on both job templates please refer to subsequent slides.
81
Release universal journal – support of prior periods modes – slide 11
Access via job scheduling – part 2 – “Release Universal Journals” job template
Parameter screen of “Release Universal Journals” job template as of S/4HANA 2502
5
Parameter screen of “Release Universal Journals” job template before S/4HANA 2502
4
3
6
5
4
3
1
1
2
The “Release Universal Journals” job template before and as of
S/4HANA 2502 differs only on the parameter screen. The following
changes were applied:
3• The “Calculate Year and Period” option was moved from the
5• The “Consolidation Group” is not mandatory any more. But at least
1• The “Replication Type” group was renamed to “Selection Mode”
Year” and “Period” are not mandatory any more and
4• “Fiscal
“Period” was renamed to “Execution Period”. So either a
“Start Period” field was introduced. This is only relevant in case one of
6• The
the prior periods modes has been selected. An error will be shown in case
“Fiscal Year” and “Execution Period” is specified or the
“Calculate Year and Period” flag is selected. In case all three
fields are empty “Schedule” and “Check” will show an error.
“Start Period” is empty and a prior periods mode has been chosen or in
case “Start Period” is filled and any of the other modes has been selected.
82
Parameters are now pre-filled with your global parameter values.
to be in sync with the selection screen of the RUJ task.
two prior periods modes “Prior Periods – Complete Data”
2• The
and “Prior Periods – Delta” were added to in the “Selection
Public
Mode” group.
“Technical Settings” group into the “Version / Time Period”
group.
“Consolidation Group” or “Consolidation Unit” has to be filled, otherwise
“Schedule” and “Check will show an error.
•i
Release universal journal – support of prior periods modes – slide 12
Access via job scheduling – part 3 – “Release Universal Journals” job template
Parameter screen of “Release Universal Journals” job template as of S/4HANA 2502
1
2
3
In addition to the checks that were already mentioned
on the previous slide some further checks are
executed:
1• Entering a “Fiscal Year” before the “From Year for
Preparation Ledger” and choosing one of the prior
periods mode options will result in an error as the
prior periods mode is only supported for group
Public reporting preparation ledger integration.
2• Entering an “Execution Period” which is not foreseen in the fiscal year variant
that is assigned to the selected consolidation version will result in an error.
2• In case a “Fiscal Year” has been selected that falls into the classic
integration, entering an “Execution Period” which is a special period
according to the fiscal year variant that is assigned to the selected
consolidation version will result in an error as in this type of integration the
special periods are not explicitly executed but automatically processed when
the last “regular” period is executed.
2• In case a “Fiscal Year” has been selected that falls into the group
reporting preparation ledger integration, also a special period can
be entered as “Execution Period”.
3• Entering a “Start Period” which is not before the “Execution Period”
results in an error.
3• Entering “0” as “Start Period” results in an error. Period 0
processing is only possible by using the “Release Universal
Journals - Prior Periods including Opening Balances” job template. 83
Release universal journal – support of prior periods modes – slide 13
Access via job scheduling – part 4 – “Release Universal Journals – Prior Periods including Opening Balances”
1
3
2
i
The “Release Universal Journals – Prior Periods including
Opening Balances” job template is only available as of
S/4HANA 2502.
It was specifically designed to create a starting point for a
consolidation unit in group reporting using the RUJ task.
Therefore it uses the “Prior Periods – Complete Data” mode
and always processes data as of period 0 (i.e. it processes the
opening balances of accounting) and up to the period before
Public
the execution period.
i•
Parameters on the parameter screen are pre-filled
with your global parameter values.
a “Consolidation Group” or a “Consolidation
1• Either
Unit” have to be specified. In case both are empty
“Schedule” and “Check will show an error.
“Consolidation Chart of Accounts” field is
2• The
mandatory. Even though is not required from a
business point of view, it is technically required (e.g.
for monitor status handling, locking, etc.).
3• “Fiscal Year” and “Execution Period” are mandatory. As a recurring scheduling of
the RUJ task in “Prior Periods – Complete Data” mode as of period 0 does not
make much sense the “Calculate Year and Period” option is not offered in this
template. Instead a “Fiscal Year” and an “Execution Period” have to be specified.
Entering a year before the “From Year for Preparation Ledger” will result in an
error as the prior periods mode is only supported for group reporting preparation
ledger integration.
Entering an execution period which is not foreseen in the FYV of the cons version
84
will result in an error. Special periods may be entered as execution period.
Release universal journal – support of prior periods modes – slide 14
Errors and warnings during execution – part 1 – errors
i
As the prior periods modes are only supported for accounting
integration with group reporting preparation ledger, it is checked
that the execution year is not before the “From Year for
Preparation Ledger”. In the selections screen the prior periods
mode options are inactive in such a case and cannot be chosen, in
the scheduling template an error is shown, when a fiscal year
before the “From Year for Preparation Ledger” is entered, but in
case the “Calculate Year and Period” option is chosen (e.g. for
recurring scheduling) it is not checked whether any scheduled RUJ
task would happen before that from year.
1
2
3
i
In case a RUJ task is triggered via the “Execute
with Selection” or via scheduling a task, this does
not necessarily mean, that the triggered RUJ task
can be executed as planned. For example you can
trigger a RUJ task via data monitor for a cons unit
which still has “Transfer from Universal Journal”
activated for a given version and period in master
data, but the cons unit does not meet the
prerequisites for accounting integration any more,
e.g. because currency settings of the cons unit,
version, or in accounting were changed.
Therefore a couple of checks are executed during
RUJ task execution, to guarantee that the task is
only executed in case all prerequisites are fulfilled.
These checks can result in errors or warnings. In
case of errors the RUJ task is not executed as
planned.
In the context of the prior periods modes this kind
of checks during RUJ task execution had to be
enhanced.
Public
Some other checks that were introduced are only relevant in case
of scheduling, as the selection screen of RUJ task already
prevents these errors:
i
The lower boundary of the selected prior periods has to be a
period before the execution period. Again in the selections screen
this is checked and an error is shown in case this check fails, in
the scheduling template also an error is shown, when periods are
entered as start and execution period, that violate this check, but in
case the “Calculate Year and Period” option is chosen (e.g. for
recurring scheduling) it is not checked whether in any scheduled
RUJ task this check will fail. In case you schedule the RUJ task
quarterly (in periods 3, 6, 9, and 12) with dynamic calculation of
execution year and period, and enter 1 as start period, this will
work fine from the perspective of that check for all scheduled
tasks. However if you do the same on a monthly basis, this check
will fail, once the calculated execution period is period 1 as well, as
then the start period is not before the execution period any more,
while in all other periods this will be fine.
Due to the fact that the RUJ task in prior periods mode by definition operates in
several fiscal periods (one or several prior periods to read data from, and the
execution period to transfer data to if required). This leads to the most prominent
enhancement of the checks:
While in current period mode it is sufficient to check in the execution period that the
cons unit fulfills all accounting integration prerequisites in the given version, this
needs to be checked in case of prior periods mode for all prior periods as well as the
execution period. In case these checks fail for a single combination of cons unit,
period, and version, the RUJ task is not executed for this cons unit at all.
1 E.g. you triggered the RUJ task via “Start with Selection” in “Prior Periods – Delta”
mode for a cons group (with two cons units assigned) in period 11 for periods 1 to 10.
2 But in the master data one of the cons units (“DD_TEST5”) is only integrated as of
period 5 of that fiscal year. Then no data is transferred for this cons unit because of
the failing check in periods 1 to 4, even though accounting integration in periods 5 to
11 might be o.k. for that cons unit.
3 The second cons group “1010”, which is assigned to the cons group, successfully
passed all integration checks in all periods and therefore is released as planned.
i
Note: There is no separate check of integration prerequisites for period 0. In case
accounting integration is possible in period 1, then also period 0 can be processed.
i
Last but not least a check was introduced which is only relevant for
on premise and private cloud environment but not for public cloud:
While for public cloud the document type for prior periods
execution is hard coded to 0I and cannot be changed, on premise
and private cloud customers have to assign a document type for
prior periods execution on their own. In case this did not happen,
an error is shown during RUJ task execution in any of the prior
periods modes.
85
Release universal journal – support of prior periods modes – slide 15
Errors and warnings during execution – part 2 – warnings
i
Even though the constellations where such issues with
duplicated or missing data may occur are somehow
complex to understand in detail, there are two things you
should know:
1. During RUJ task execution the system checks with the
metadata of already executed RUJ tasks, whether such
an issue may occur. If this is the case a warning
message is shown in the task log ( 1 ).
1
i
As already explained on this concept slide, there are certain constellations of RUJ task execution sequences which can lead to
duplicated or missing data in group reporting.
Duplicated data may for example occur, when a RUJ task is executed in current period mode (no matter whether “Current Period –
Complete Data” or “Current Period – Delta” mode is used) for a cons unit and period combination, that was already processed by a
RUJ task in prior periods mode before (no matter whether “Prior Periods – Delta” or “Prior Periods – Complete Data” mode was
used). Data may be transferred in the execution period period with the current period mode on document type 0F, which already had
been transferred to a later execution period with the prior periods mode on document type 0I before. An example for this is case
shown on the concept slide.
Similar effects with duplicate data may also occur in other constellations, e.g. when executing the RUJ task in “Prior Periods –
Complete Data” mode for a subset of periods (e.g. in period 4 for periods 1 to 3) than it had been executed before (e.g. in period 6 for
periods 1 to 5). In that case data from periods 1 to 3 which has already been transferred to period 6 in previous RUJ task execution,
is now transferred to period 4 again.
A situation with missing data may occur for example, when executing RUJ task in “Prior Periods – Complete Data” mode for a prior
periods interval (e.g. execution in period 6 for periods 3 to 5) that overlaps only partially with the interval of prior periods including
execution period of a previous RUJ task execution in that mode (e.g. execution in period 3 for periods 1 and 2). In that case data
from periods 1 and 2 which has already been transferred to period 3, will be taken into account during delta calculation for period 6,
and with that will be missing when looking at YTD values in period 6 afterwards.
Public
Clicking on the message opens a detailed diagnosis with
further instructions and background information. Please
also see an example screenshot on the next slide.
Note: The system is only checking the metadata of RUJ
task executions (such as cons unit, version, selection
mode, execution year and period, start period (if
applicable)). It does not (and cannot) check the release
data in accounting and the transferred data in group
reporting. Therefore the user needs to check, whether
duplicate or missing data indeed occurs. Analysis tools
like “Group View on Accounting” help to analyze this.
2. As long as:
•
The RUJ task is executed in “Prior Periods – Delta”
mode only, but not in “Prior Periods – Complete Data”
mode …
•
… and the RUJ task is not executed in any of the
current period modes (i.e. “Current Period –
Complete Data” or “Current Period – Delta” mode) for
a cons unit and period combination which was
already processed by a RUJ task in prior periods
mode, …
such effects may not occur.
86
Release universal journal – support of prior periods modes – slide 16
Errors and warnings during execution – part 3 – warnings
1
2
1 In case a warning message is shown in the task log of the RUJ task, that the RUJ task may have caused duplicate or
missing data, clicking on that message …
2 … opens a pop-up with a detailed diagnosis with further instructions and background information.
Public
87
Release universal journal – support of prior periods modes – slide 17
Errors and warnings during execution – part 4 – warnings
i
In case of scheduling a RUJ task with the “Release Universal Journals – Prior Periods
Including Opening Balances” job template, a special warning may be shown.
As the RUJ task only incorporates accounting data as well as data transferred by RUJ
task execution into the calculation of the delta to be posted, inconsistencies (in the
sense of duplicated data) will be created in case the opening balances of a cons unit
were already created with a different mechanism (e.g. via flexible file upload or GRDC
data mapping), because the RUJ task will post the opening balances again on posting
level blank and document type 0I.
In most relevant cases these opening balances which are not based on data
transferred by the RUJ task occur as data on posting level 00 and record type 0 in
period 0.
1 In case the system detects such data for the scheduled combination of cons unit,
fiscal year, version, and consolidation chart of accounts, it shows the warning which
you see in the screenshot.
In case the RUJ task is not scheduled for a dedicated cons unit but for a consolidation
group, the system executes the check for all cons units which are assigned to the
scheduled cons group in the execution period in the given cons version, and the error
is shown, in case such data exists for any of these cons units.
1
!
Situations where such data exists only in other periods than period 0 (because it was
only created/loaded in the given fiscal year and not yet carried forward from the
previous fiscal year to period 0 of the given fiscal year) cannot be detected by the
system (as such data cannot be distinguished from loaded data which does not
represent opening balances but periodic data). Therefore in such cases the warning
won’t be shown.
In case you created before mentioned duplicates because the warning was not shown
or because you ignored the displayed warning, you may either correct (i.e. invert the
opening balances on posting level 00 and record type 0) or you could execute the
RUJ task once more with the same parameters but as of prior period 1 instead of
period 0 in “Prior Periods – Complete Data” mode and the resulting delta postings in
the execution period will exactly invert the opening balances on document type 0I.
Public
88
Release universal journal – support of prior periods modes – slide 18
Configuration of RUJ task – part 1
1
!
2
Note:
•
This topic is only relevant for private cloud and on premise customers, as in public cloud
this configuration is not exposed to customers.
•
Instead public cloud customers get a pre-defined RUJ task “1015” delivered via content,
which has document type 0F assigned for periodic execution and document type 0I
assigned for prior periods execution. This configuration cannot be changed by public cloud
customers.
3
1 For private cloud and on premise customers a new configuration activity “Define Release
Universal Journal Tasks” is delivered. This configuration activity consists of two levels.
2 In the upper level one or several RUJ tasks may be defined.
Note:
•
4
5
3 By selecting a RUJ task in the upper level and clicking “Document Type Assignment”, …
4 … you navigate to the lower level of the configuration activity.
5 On this lower level two document types might be assigned time-dependent as of a from fiscal
year and period to a RUJ task:
i
Public
At the moment it does not yet make much sense to define several RUJ tasks, as all of
them are currently doing the same, using the same document types. This was mainly done
for compatibility reasons, but may be used in future to support multiple release tasks (e.g.
for staggered close).
•
The document type for periodic execution will always be used when a RUJ task is
executed in current period mode. This document type assignment is mandatory.
•
The document type for prior periods execution will be used when the RUJ task is executed
in prior periods mode. This document type assignment is optional. In case the RUJ task is
executed in prior periods mode and no document type for prior periods execution is
assigned, this will result in an error.
For upgrade customers an XPRA is executed which fills the new “Define Release Universal
Journals Task” configuration with their existing RUJ tasks including the document type for
periodic execution the system was using automatically before the upgrade. Therefore after
upgrade the system will behave after the upgrade the same as before.
89
But upgrade customers need to assign the document type for prior periods execution.
Release universal journal – support of prior periods modes – slide 19
Configuration of RUJ task – part 2
1
1 The document types which are assigned to a RUJ task for
periodic execution and for prior periods execution have to be
different ones, so that the data resulting from both execution
types of the RUJ task can clearly be separated.
In case you try to assign the same document type for both
execution types, you’ll get an error and cannot save your
configuration.
2
2 As long as multiple RUJ tasks are not supported end-to-end,
but are accepted by the system only for compatibility reasons
(because already before S/4HANA 2502 it was possible to
create multiple RUJ tasks), the document type which is
assigned for periodic execution has to be the same for all RUJ
task (as assigning different document types would result in
replicating the same data multiple times by using different
document types). The same applies to the document type
which is assigned for prior periods execution: It has to be the
same one for all RUJ task.
In case you do not maintain the document type assignment
consistently across all RUJ tasks, you’ll receive an error and
cannot save your configuration.
Public
90
Release universal journal – support of prior periods modes – slide 20
Summary of key facts
Public
1
RUJ task in prior periods mode, transfers data from prior periods into the execution period.
2
In the resulting data in GR the source period from accounting is not known any more.
3
Therefore drill-through to accounting source data cannot be supported for resulting data.
4
→ Prior periods mode should only be used as an exception.
5
→ Accounting data in execution period is not processed.
5
→ Cannot be used for quarterly data release.
7
A dedicated document type is used (0I in public cloud, configurable in private cloud / OP)
8
Resulting data is shown separately in “Group View on Accounting” app.
9
Prior periods mode of RUJ task is supported in accounting integration with GRPL only.
91
Prepare
Collect
Consolidate
Analyze
2502 release
Changed treatment of product group
during release universal journal
Changed treatment of product group during release universal journal – slide 1
Introduction
1 When enabled for RUJ task:
• Material Group should be filled by the content of the Product
Group field (as it is meanwhile called) in the universal journal
(coming from material management / procurement).
• Sold Product Group is filled by the content of the Sold Product
Group field (formerly called Product Group) in the universal
journal (coming from controlling – profitability analysis).
! Due to unfortunate circumstances a mistake was made in the
infrastructure of the RUJ task from the beginning:
1
• Material Group is not filled with the appropriate source filled,
but is filled with the content of the Sold Product Group field, ...
• … while Sold Product Group is filled as expected.
i This was fixed as of S/4HANA 2502.
• For new customers as of S/4HANA 2502 the correct behavior
is applied automatically and they don’t have to care about this
any more.
i In the release universal journal (RUJ) task two fields around product/material
group are supported:
• Material Group
• Sold Product Group
Both can be independently from each other enabled for RUJ task, by switching
off the “Aggregate Data on Release” configuration setting in the additional master
data field configuration.
Public
!
• For upgrade customers however, we could not simply apply
the changed behavior, as it would result in a mixture of
wrongly filled and properly filled data.
As we cannot correct already existing data automatically, we
introduced a configuration switch which is only visible to
upgrade customers, to give them control on when they want to
switch to a consistent filling of the Material Group in group
reporting. For further details please refer to the next slide.
93
Changed treatment of product group during release universal journal – slide 2
Recommendation for upgrade customers after upgrade to S/4HANA 2502 – part 1
!
After the upgrade to S/4HANA 2502, upgrade customers should check, whether in their system
the Material Group field was already filled in group reporting or not.
In case the field was not yet filled:
• We recommend to activate the “Correct Material Group for Acc. Integr.” switch in the
global system settings for group reporting configuration.
• This is without any risk of getting issues in the group reporting data and ensures that you’ll
get the field properly filled in case you activate it for the RUJ task at any point in future.
In case the field has already been filled:
• Check whether you can somehow correct the already existing data with regards to the
Material Group information.
• Only activate the “Correct Material Group for Acc. Integr.” switch in the global system
settings for group reporting only after you corrected the already existing data.
• We apologize for any inconveniences because of this process.
The global system settings configuration for group reporting can be accessed in solution
builder via “Configure your Solution” → “Finance” → “Corporate Close” → “Basic Settings” →
“Check Global System Settings”.
In case of CBC the additional master data field configuration can be found under “Accounting”
→ “Group Valuation and Reporting” → “Global Settings for Group Reporting” → “Check Global
System Settings”.
i
Note:
• Once activated and saved, the “Correct Material Group for Acct. Integr.” switch is hidden
and cannot be deactivated any more. A pop-up also shows a warning on this in the
configuration (see also next slide).
Public
94
Changed treatment of product group during release universal journal – slide 3
Recommendation for upgrade customers after upgrade to S/4HANA 2502 – part 2
1 The F1 help on the configuration
switch “Correct Material Group for
Acc. Integr.” (also accessible via
SAP companion help) shows the
explanation and recommendation
from the previous slide.
4
5
2
2 When activating the configuration
switch “Correct Material Group for
Acc. Integr.” …
3 … and pressing the “Save” button …
4 … a pop-up with a warning is shown,
that after saving this configuration
change for the material group
handling in RUJ task, this
configuration switch will be hidden
and therefore cannot be deactivated
any more.
3
1
5 Proceeding with “Yes” will activate
the correct material group handling
for RUJ task …
6
Public
6 … and the configuration switch won’t
be visible any more.
95
Prepare
Collect
Consolidate
Analyze
2502 release
New SAP Fiori app to import reported data
Improved UX with new SAP Fiori app
New SAP Fiori app to import reported data – slide 1
Overview
Replacing the current ‘Flexible Upload of Reported
Financial Data’ app with a new SAP Fiori ‘Import Reported
Data’ app offering:
•
Automatic recognition of the file format (“upload method”
parameter is not required anymore)
•
Option to download the file template
•
Change to asynchronous processing for mass data
enablement
Change management for existing customer users to
enable:
•
Continued support of old templates and files
•
Ability for logs to stay the same
•
Temporary parallel availability period of both old and
new app
•
Deprecation plans of the old app yet to be
communicated
Benefits
Public
•
Provide increased usability in an improved user
experience
•
Prepare for large data loads and further enhancements
97
New SAP Fiori app to import reported data – slide 2
1 The “Download Template” is available on the selection
screen of the new ”Import Reported Data” app and gives
option to download template in csv or xlsx format.
1
2 In order to select the file for the import, click on the
”Browse” button.
2
3 You can check the “Test Ignores Status” option to import
3
the file in the test run excluding task and period status
check. You use this option, for example, to simulate the
execution when the period is closed.
4 And you can import the data in the update run (if the “Test
Ignores Status” is not selected”) …
5 … or you can import the data in the test run (with checking
the task and period status).
4
Public
5
98
New SAP Fiori app to import reported data – slide 3
1
1 Once the import process is finished, there is a notification
popup in the header of the launchpad …
2 … where you can display the information about finished
process …
2
3 … and from where you can navigate to ’Task Logs’ app
with the corresponding log.
i
3
Public
This log processing and notification is due to change of the
import process from foreground to background job. Which
allows higher data volume to be processed as it is not
dependent on maximum runtime limit of the frontend
processing.
99
Prepare
Collect
Consolidate
Analyze
2502 release
Data Mapping
Advanced monitoring, improved job processing and logs, integration
with SAP Green Ledger
Advanced Monitoring
▪ Complete overview of the upload process at one glance
▪ Detailed information about the last job runs
▪ One-click access to logs and files
▪ Enhanced usability of the job list
Public
Click to access blog
101
Job processing – local currency optional
▪ Automatically derive the local currency from consolidation unit master data during import. The local
currency output field is no longer mandatory in the data mapping file.
Public
102
Job processing – import options in the data mapping definition
▪ Define the import options in the mapping definition (instead of in the job) and overwrite them in the job if
required.
Public
103
Job processing – job run header and Overview tab
▪ Streamline the job run header information.
▪ Add separate Overview tab with additional information.
Public
104
Job processing - .txt extension files
▪ Support .txt extension files as a source.
Public
105
Mapping log
• Display error and warning messages at the top of the log
• Display the name of the field and the value that are the origin of the error or warning
• Improve the quality of messages to provide more helpful guidance to users
Public
106
Traceability log 1/2
• Remove the limit of 30 million characters
• Enhance sorting and filtering capabilities (e.g., unmerge cells in header rows, freeze panes, etc.)
• Display mapping messages before mapping rules and the import messages before output fields
• Facilitate the filtering of messages to only display errors and warnings (planned for February 2025*)
*Legal disclaimer: dates are subject to change at the discretion of SAP.
Public
107
Traceability log 2/2
• Add a new sheet with Job Run Overview
• Include mapping file sheets if requested in definition
Public
108
Integrating SAP Green Ledger with group reporting
• Connect SAP Green Ledger to SAP
Group Reporting using OData services
• Map greenhouse gas emissions from
SAP Green Ledger with the ACDOCU
table
• Import greenhouse gas emissions and
other data into the ACDOCU table
using Data Mapping jobs
• Unlock value from ACDOCU data
More information:
Streamlining Sustainability Reporting
Public
109
OData V4 Custom Connection to SAP Green Ledger
▪ Support OData version 4
▪ Support GHG (greenhouse gas) emission fields
▪ Use OData version 4 destinations created in SAP BTP Cockpit as source instances in data mapping definitions
▪ Provide template to easily create GHG data mapping files, see also SAP Note 3524284
▪ Run data mapping job to connect to SAP Green Ledger, extract, transform and load greenhouse gas emission data into
the ACDOCU table
Public
110
Prepare
Collect
Consolidate
Analyze
2502 Release
Navigation between Forms in GRDC
Navigation links – User requirements
•
Navigation Links are user friendly and intuitive functions, supporting the end users when
entering/reviewing data in GRDC.
•
Navigation Links can be defined by the GRDC users/administrators and are additional to the
existing standard GRDC navigation (selecting of Forms, new Multi Tab functionality, etc.).
•
Navigation Links are user defined links between Forms of the same Package.
•
Links are defined at unique cell level in a Form (Form Designer).
•
The GRDC Administrator is expected to understand the functional relationships between
Forms (FS items, sub-items) and can define the Navigation Links to make the data entry/review
user friendly.
Public
112
New functionality – Define the link in Form Designer
Public
113
New functionality – Enter Package Data
Any defined Navigation Link can be recognized by the Purple triangle in the Form.
Using the ‘right-mouse’ click on the cell (in this example D8) the linked Forms (can be multiple) are
shown and can be selected.
By selecting the ‘Go to….’ the linked Form will be opened and the existing Form closed and saved.
Public
114
Prepare
Collect
Consolidate
Analyze
2502 Release
Define several Fiscal Years and Periods in GRDC Forms
Multi-Period requirements – User stories addressing the requirements
As a company accountant submitting my data in GRDC forms…
•
… when working on the current actuals period, I want to see the prior year data of the same
period in the form as a display column.
•
…when working on the current actuals period, I want to see the prior period of the same year
in the form as a display column.
•
… when working on a restatement of the prior year in an extension version, I want to enter data
for all periods of the year at the same time, both in Periodic or YTD mode.
•
… when working on the financial Plan of the next year(s) in a plan version, I want to enter data
for Fiscal Years or for the Budget all 12 months of the year at the same time.
•
… when working on the current actuals period, I want to see the corresponding budget
version in the form as a display column.
Public
116
New functionality – Periods and Fiscal Years in rows and columns
In Form Designer multi-periods/years can be selected in columns and rows.
Public
117
New functionality
Most common examples with multi-periods are the Forms with the additional previous period or
previous year in the Form. This is a good reference for end users, understanding the requested
data and improving data quality.
When defining the columns or rows in Form Designer, a special function will be added to select
Period Offset and the available list of values for Period or Fiscal Year will be presented.
Period -1 or +1, etc.
Fiscal Year -1 or +1, etc.
Public
118
New functionality – Multi Periods
Public
119
New functionality - Multi Fiscal years
Public
120
Prepare
Collect
Consolidate
Analyze
2502 Release
Integrate Group Reporting data monitor
tasks in the package
Integrate data monitor tasks into the package 1/5
The following tasks are integrated: release task, data collection task, annual
net income task and line validation task.
Public
122
Integrate data monitor tasks into the package 2/5
Manage Packages - General Information tab
Embedded Data monitor consistency checks
preventing to save the package definition
The package definition must point to only one
data monitor.
Check is based on the common parameters :
Consolidation Version / Year / Period
If the consistency check is in error, the package
definition can’t be saved. It must be adjusted for
the common parameters. Or the task group
assigned to the Data Monitor must be changed.
Public
123
Integrate data monitor tasks into the package 3/5
Manage Packages – Data Entry Steps tab
4
1
2
5
3
1 New section column : predefined sections (Data Release, Forms and Validations) ordered in this way. They organize tasks and forms inside the step later on in the left panel of the package
2
Tasks are by default assigned to the section according to its task category
New Data Monitor Task column : it displays the tasks from the underlying data monitor as selected in General Info tab.
When the data monitor contains multiple data collection tasks, each task must be assigned to one and only one step in order to propagate the lock of the task to the step. Then folders assigned to the
step/data collection task are locked to data entry through the document type.
When the data monitor contains one data collection task, the task can be assigned to multiple steps in the package definition.
Release and validations tasks are optional. If they don’t exist in the data monitor, they don’t appear as well in this column.
3 Write Document Type enhanced : the list of DT corresponds to the document types assigned to the data collection task selected in the Forms row. Only DT applicable to forms are displayed.
Synchronize Steps (with the data monitor): helps to maintain the data entry steps grid. In one click, each step is adjusted with a row for the release task and for the line validation task in case they are
4 missing or if the package definition has been broken with the data monitor. Add the rows or remove duplicate rows for these tasks in case of inappropriate changes from the user.
Public
5 Hide Single Tasks: hide the release and validation tasks rows in order to focus on the configuration of the Forms section where you add folders and document types.
124
Integrate data monitor tasks into the package 4/5
Enter Package Data – Run the task, update status and statistical information
1
New sections
(Data Release,
Forms,
Validations)
organize tasks
and forms inside
the steps of the
package.
4
Run Annual Net Income
Validate Line Items
1
2
2
Select the task
on the left
panel, it opens
on the right side
and can be run.
3
3
The status of the
task and
statistical
Information are
updated once
the task is
completed.
4
Run ANI or
multiple line
validation tasks
(If any) at once
for all the steps
of the package
Public
through
the
Action menu.
125
Integrate data monitor tasks into the package 5/5
Enter Package Data – Display the log of the task
Access the last log of the task in the Task Logs app through the Display Log button
Public
126
Prepare
Collect
Consolidate
Analyze
2502 release
Line-item validation
Multiple line-validation tasks on group reporting and unreleased accounting data
Definition of Terms
Validation
“Line Item Validation” vs. “Balance Validation”
Line Item Validation
Balance Validation
– Validation rules check posting lines
against rule definition
– Validation rules are maintained
within “Manage
Substitution/Validation”
– Automatic validation of Breakdown
Category
– Example: Consolidation Unit S001
does not allow Profit Center PC0001
– Validation rules check two selected
amounts against each other
– Validation rules are maintained
within “Validation Rules & Groups”
(groups will replace methods)
– Example: Assets has to equal
Liabilities and Equity
„Line Item Validation“ checks combination of field values | „Balance Validation“ checks amount & quantity
Public
128
Definition of Terms
Validation
“Line Item Validation” vs. “Balance Validation”
„Line Item Validation“ checks combination of field values | „Balance Validation“ checks amount & quantity
Public
129
Line Item Validation Feature
Line Item Validation
Five cases where “Line Item Validation” checks breakdown categories and validation rules of
Business context: GR Journal Entry Items
new
new
Reported Financial
Data
Manual Postings
Data to Release
Released and
corrected data
Rep. data for
staggered close
▪ Posting Level: 00
• Posting Level: 01,
10, 20 and 30
• Posting Level: #
▪ Posting Level: #
and 0C
• Posting Level: #,
0C
▪ Validation runs
during Flexible
Upload and GRDC
data entry
• Validation runs
during manual
posting process
• Validation runs on
accounting data
level with a task &
a job run
▪ Validation runs on
group reporting
data level with a
task
▪ Upload is not
possible, if a
validation error
appears
• Posting is not
possible if a
validation error
appears
• Posting of
accounting journal
is not blocked
▪ Validation runs
after data is
released,
uploaded or
posted
• Validation runs on
accounting or
group reporting
data level with a
task and Selection
• Validation can run
before or after
data is released ,
uploaded or
posted
„Line Item Validation“ checks combination of field values for non-automatic postings.
Public
130
Features with “Line Item Validation”
Existing features:
Validation of released and corrected data after data is in Group Reporting i.e. for posting level blank /# and 0C
•
▪
▪
Standard validation through the task 1050 - „Line Item Validation“
-> check released data, uploaded data and group journals against breakdown category
Custom Validation through the task 1050 - „Line Item Validation“
-> check released data, uploaded data and group journals against validation rules (Business context: GR Journal Entry Item)
Validation of uploaded, entered Data via GRDC and manual postings for posting level 00, 01, 10, 20 and 30
•
§
•
Standard validation through flexible upload, data entry and manual posting
-> check data against breakdown category
Custom Validation through flexible upload, data entry and manual posting
-> check data against validation rules (Business context: GR Journal Entry Item)
New additional features (2502) with GRPL:
Check accounting data after posting accounting journals and before releasing data to Group Reporting
•
▪
Validation of Accounting data with the Group Reporting perspective
Validation in staggered close (E.g. step 1 submit the P&L and step 2 submit the BS)
•
▪
▪
Public
More than one task for category „Line Item validation” is allowed
Use Selection to define different dataset e.g. P&L vs. BS accounts used in different validation tasks
131
New configuration for “Define Task for Line Item Validation”
IMG in On premise
Public
SSCUI in Cloud
132
New configuration for “Define Task for Line Item Validation”
Only one entry per
From Year/From Period
combination is allowed
Public
133
New configuration for “Define Task for Line Item Validation”
1
From Year/Period
Defines the
FiscalYearPeriod,
from which onwards
the settings shall be
valid
Public
Data Source
Two Options
•
•
Accounting
Group Reporting
Decides the table to be
checked
ACDOCA or ACDOCU
3
2
Selection Object
Default Acc. Read Mode
Two Options
(only applicable if
Data Source is
Accounting)
• Complete data in
accounting
• Unreleased data
4
Enable staggered close
to filter data by the
following:
•
•
•
•
FS Item
Subitem
Partner unit and/or
Document Types
134
New IMG Activity/SSCUI for “Define Task for Line Item Validation”
Special Case: Save without data source setting is not allowed
Exception for existing OP-Customer:
Existing line item validation task has no
data source setting and will work as it was
in past. But if a new task will be created,
data source setting from existing task will
be also queried during the saving process.
New configuration for “Define Task for Line Item Validation”
Selection Object:
Allows ‘FS Item’, ‘Subitem’,
‘Subitem Category’, ‘Partner unit’
and/or ‘Document Types’ which
are part of ‘Posting Level’ # (blanc)
and 0C.
An error will appear upon saving if fields
or field values included in the Selection
are outside the above allowed range.
Run Line Item Validation Tasks
Run the task via data monitor
Public
Run the task via job scheduler
137
Run Line Item Validation Tasks – Parameter screen
Special Case: Fetch of Data Source Settings
Data Source & Accounting Read Mode:
This section is dependent on Task, Fiscal Year and Period. These three
parameters fetch the Data Source Settings from the Task.
Note:
- Accounting Read Mode can be changed again during definition
- If GRPL is NOT active, this section will disapear (old logic will run)
- If no data source is defined, Group Reporting appears as the default
data source
Behavior of parameter screen – run via job scheduling
First view on the parameter screen:
▪ shown without sections of “Data Source” and “Accounting Read Mode”
The sections of „Data Source“ and
„Accounting Read Mode“ are dependent on
the task data source settings. As the task is
not prefilled, the data source is not clear.
Therefore, these sections are hidden until the
task is set and „Check“ at the bottom right is
pressed. The job can be scheduled without
showing these settings, but needs an entry of
the mandatory field task. The data source
settings are grabbed from the task during run
time.
Behavior of parameter screen – run via job scheduling
View for Data Source = Group Reporting
After clicking the „Check“
button
View for Data Source = Accounting
After clicking the
„Check“ button
Task logs for “Line Item Validation” tasks
Public
141
Task Log for “Line Item Validation” Tasks - Enhancement
Log Header Messages
Task is not assigned to a Task Group
"Task is not part of the monitor. There is no
monitor status management.“ - Info
Feature toggle is OFF.
“Line Item Validation is turned off. Data Source
Settings are ignored.“ - Info
GRPL is active / Version has no Preparation Ledger / Data Source is Accounting
"This version has no preparation ledger assigned. No process possible.“ - Error
Log details
Navigation from individual amount link to journals, Group Data Analysis and Group View on
Accounting App, dependent on data source.
Public
142
Prepare
Collect
Consolidate
Analyze
2502 Release
Balance Validation
Multiple balance validation tasks in group reporting and unreleased accounting data
Balance Validation – Group Reporting
In order to make use of the new feature, in your system, please follow the below steps:
▪ Toggle: FINCS_BV_ADAPTATION
▫ Login to the system with Role 'Configuration Expert - Business Process Configuration'.
▫ Select the following values: Application Area: Application Platform and Infrastructure
▫ Sub Application Area: General Settings
▫ Navigate to Basic settings -> 8. Activate Features
▫ Toggle ‘FINCS_BV_ADAPTATION' can be selected and switched on.
▪ Please refer to the note:
3553668 - Group Reporting: Migration of new Balance Validation Framework
The attachment of the above note explains the migration process with screenshots. The steps to attach
the new tasks in the Data Monitor and Cons Monitor is also provided in the note.
Public
144
Balance Validation – Group Reporting
The following apps will be visible on switching the toggle
▪ Assign Rule Group for Balance Validation
▪ Manage Balance Validation Rules and Rule Groups
▪ Run Balance Validation and View Results
Additionally you will be able to create
tasks in the app: Define Balance
Validation tasks, under Manage Your
Solution > Configure Your Solution >
Finance > Corporate Close > Data
Processing
Please refer to the below application help page to
get all the relevant details:
New Balance Validation Process | SAP Help
Portal
Public
145
Prepare
Collect
Consolidate
Analyze
2502 Release
“Post Group Journal Entries” App
Replace Journal
“Post Group Journal Entries” App – Replace – slide 1
Overview
1
1
The Replace action is available on the overview screen of the Post Group Journal Entries app. It combines the Reverse and Copy actions. The reversal document is posted
in the background and a draft of the copied document is prepared, allowing the user to make modifications.
i
If the reversal is part of a workflow, the system creates a workflow item in the background. The posting then waits for approval (suggestion: “the posting must be approved”).
If the new document isn’t part of a workflow, it might be posted before the reversal.
i
If you decide to replace a document that is part of a document bundle, the system replaces the entire bundle.
Public
150
“Post Group Journal Entries” App – Replace – slide 2
References
1
2
3
1
The original document references the reversal document in the Reversed With field.
2
The reversal document references the original document in the Reversed Document field.
3
The corrected document does not have any reference.
i
You can filter the original and reversal documents using the Reversed Document and Reversed With fields in the Display Group Journal Entries and Display Group
Journal Entries with Reporting Logic apps.
Public
151
Prepare
Collect
Consolidate
Analyze
2502 release
Review booklet
New app with an analytical group view on unreleased accounting data
Review booklet – new app with an analytical group view on unreleased
accounting data I Overview
Overview
▪ New group financial review app on real-time accounting
data
▪ Expose universal ledger accounting data into an
analytical group view through this new SAP Fiori app and
making use of previously delivered road map items:
– Integrate with group reporting for tighter accounting
– Leverage the app to review group financial statements
▪ New features of the new SAP Fiori app for readily
consumed reporting content in different pages based on
master data from group reporting and reporting rule
definitions:
– Balance sheet
– Profit and loss statement (cost of sales and nature of
expense structure)
– Cash flow statement
Public
▪ Predefined column and row structures:
– Data release status to group reporting (Accounting
data, released data in group reporting)
– Period comparison reporting (such as prior-year
actuals)
– Organizational hierarchies (consolidation unit,
segment, and profit center)
– Various measures, including month to date, quarter to
date, and year to date, as well as local currency,
transaction currency, group currency, and quantity
▪ Navigation and drill-through capabilities from:
– The financial review app on group reporting to this new
app
– This SAP Fiori app to analytical apps from accounting
and group reporting (depending on the source of data)
153
Review booklet – new app with an analytical group view on unreleased
accounting data I Benefits
Benefits
▪ Analyze data in a group view directly on accounting data
in a new financial review booklet for the following
scenarios:
– Any-time reporting on accounting data in a group view
reflecting the latest posting documents from
accounting (This can be combined with prediction and
transactional consolidation ledgers from accounting to
offer forward-looking consolidated management views
based on the latest accounting data.)
– Analysis reporting for companies submitting their data
to group reporting (for example, checking for
unreleased data and analyzing the impact on reports
like P&L of their next data release to group reporting)
Public
154
Group View on Accounting
In order to view the Group View on Accounting Review Booklet app, in your system, please follow the
below steps:
▪ Toggle: FIN_CS_GVA_RB
▫ Login to the system with Role 'Configuration Expert - Business Process Configuration'.
▫ Select the following values: Application Area: Application Platform and Infrastructure
▫ Sub Application Area: General Settings
▫ Navigate to Basic settings -> 8. Activate Features
▫ Toggle 'FIN_CS_GVA_RB' can be selected and switched on.
▪ Role: SAP_BR_GRP_ACCOUNTANT
Public
155
Group View on Accounting - Accounting Preview
Analytical preview on accounting
• Anytime group view on latest
accounting material
– Reflecting all accounting journals
– Translated @spot rate of the
transaction
• Presented in your group
definitions
– Filter parameters: consolidation
group, consolidation unit, GR
posting periods, etc.
– Reporting row structures driven
by FS item hierarchies
– Reporting rule definitions and
reporting item hierarchies (e.g.
Cash Flow Statement)
• Predefined column structures for
period, quarter, year comparison
Public
156
Group View on Accounting - Accounting Preview
Analytical preview on accounting
• With accounting fields filled even if not
integrated into GR
Public
157
Group View on Accounting - Columns
•
Column 1: “Accounting”: The measures (GC, LC, TC, Quantity) should be summed up (ACDOCA) without considering the release time
stamp
•
Column 2: “GR released”: The measures (GC, LC, TC, Quantity) should be summed up individually as per PL blank ACDOCU table
and consider the record type = U (only ACDOCU)
•
Column 3: GR Retranslated (GR PL blank CT, ANI): The measure (GC) should be summed up individually as per PL blank ACDOCU
table (only ACDOCU)
•
Column 4: “GR corrected”: The measures (GC, LC, TC, Quantity) should include PL 00, 01, 0C also. 1 (ACDOCU)
1 Rationale: with PL 00, 01, 0C we can correct inconsistencies on PL blank and the task “validation of universal journal” aggregates both PLs
before doing the checks. If we later want to propose data actions such as release data, validate universal journal, it is important that this is part
Public of the report also.
158
Prepare
Collect
Consolidate
2502 release
Review booklet
Commenting and notifications
Analyze
Review Booklet, analytical cell comments – Overview
Comment
pane
Cell-based
comment
Public
160
Review Booklet, analytical cell comments – Feature detail
Analytical Cell-based Comments
• Ability to discuss numbers in certain cell
• Categorize, tag, filter and edit
• History of comments and contributions
• Life cycle status for each comment
@Mention Feature
• Inform colleagues about comments via
email or notifications
Comments of All Loaded Cells
• Shows all loaded comments on a page
• Rename “Cell Comment Header”
• Classify and filter comments
Comments of Selected Cells
• Add and view comment via context menu
• Click on comment to see detailed history
Public
161
Review Booklet, analytical cell comments – In-app and email notifications
Emma: “@Paul, please double check gross margin”
Paul
In-app notification
Emma
Public
Email
162
Prepare
Collect
Consolidate
Analyze
2502 release
Review booklet
AI-assisted financial business insights for group statements (beta)
AI-assisted financial business insights for group statements (beta)
Public
164
AI-assisted financial business insights for group statements (beta)
Business insights for group financial statement
booklet using generative AI (beta)
• Analyze and summarize tabular data on a review
booklet page
• Identify and evaluate relevant business situations
• Highlight findings within large datasets
• Create a management summary of group-level
financial data
• Include comments and calculate KPIs
• Easier and faster analysis and insights into group
financial data for increased end user efficiency
Beta program
• Register and experience Business insights for group
financial statement booklet using generative AI
https://influence.sap.com/sap/ino/#campaign/3834
Public
165
Prepare
Collect
Consolidate
Analyze
2502 release
Greenhouse Gas (GHG) Emission Reporting
Additional fields for GHG emission reporting in group reporting
Fields in group reporting for greenhouse gas emission reporting – slide 1
Introduction
1
2
of S/4HANA 2408 five specific fields for greenhouse gas (GHG)
1 As
emission reporting are supported within group reporting. These are:
of S/4HANA 2502 another four fields for greenhouse gas (GHG)
2 As
emission reporting are supported within group reporting. These are:
i
These GHG emission reporting specific fields are only
available within group reporting, once a customer has
activated them via a business function.
•
GHG Scope (GHGScope)
•
GHG Data Quality Characteristic (GHGDataQualityCharacteristic)
•
GHG Category (GHGCategory)
•
GHG Energy Classification (GHGEnergyClassification)
•
GHG Scope 2 Calculation Method (GHGScope2CalculationMethod)
•
GHG Energy Mix (GHGEnergyMix)
Once activated, these fields behave according to their
additional master data field configuration settings as any
other additional master data field.
•
GHG Scope 2 Contractual Instrument (GHGScope2ContractualInstrument)
•
GHG Energy Sourcing Type (GHGEnergySourcingType)
For further details please refer to subsequent slides.
•
Sustainability Mode of Transport (SustainabilityModeOfTransport)
Public
167
Fields in group reporting for greenhouse gas emission reporting – slide 2
Activation of GHG fields – part 1
i
The fields for GHG emission
reporting have to be activated by
the customer via business
function in order to make them
available in group reporting.
Only when the business function
“Activate Fields for Greenhouse
Gas” has been activated the
GHG fields will be visible and
processed in group reporting.
1
The activation of the business
function can be accessed in
solution builder via “Configure
your Solution” → “Finance” → …
2
3
… “Corporate Close” → …
4
… “Activate Fields for
Greenhouse Gas”.
i
In case of CBC the business
functions can be found under
“Accounting” → “Group
Valuation and Reporting” →
“Data Model”
1
2
3
4
Public
… “Basic Settings” → …
168
Fields in group reporting for greenhouse gas emission reporting – slide 3
Activation of GHG fields – part 2
1
2
3
1
In this screenshot you see the configuration activity to enable
the GHG emission reporting fields in group reporting.
2
As you can see the business function is currently switched off.
3
4
By selecting “Change State” …
… the business function is getting activated.
With this the GHG fields become available in group reporting in
the system. This includes the GHG fields which were made
available in group reporting with S/4HANA 2408 as well as
S/4HANA 2502.
4
Public
5
i
In case a customer activated the business function “Enable
Greenhouse Gas Fields in Group Reporting” before the upgrade
to S/4HANA 2502 took place, the additional four fields which are
provided with S/4HANA 2502 will be immediately available in
group reporting after system upgrade. But they are configured in
a way that the system behavior does not change. In order to
make use of them,+ the configuration of these fields in the
additional master data fields configuration has to be a changed
accordingly.
5
By selecting “Change State” in a situation where the business
function is active, the business functions is deactivated and the
GHG fields are not available in group reporting any more.
i
Please note: The deactivation of the business function is not
possible in productive systems, but only in development and test
systems. Once switched on in a productive system, or
transported as switched on into a productive system, it cannot
be switched off any more.
169
Fields in group reporting for greenhouse gas emission reporting – slide 4
Additional master data field configuration for GHG fields – part 1
Business function for GHG fields switched off:
Business function for GHG fields switched on:
1
2
1
When the business function for GHG fields is switched off, the GHG fields
are not available in the additional master data field configuration.
Also in other places such as for example manual posting or analytics these
fields will not be present.
Public
2
Only when the business function “Enable Greenhouse Gas Fields in Group
Reporting” is switched on, the GHG fields are visible in the additional
master data field configuration and with that can be configured.
Note: In case the standard configuration (delivered via content) for some
GHG fields is changed and subsequently the business function is
deactivated, the configuration settings are not deleted but any kind of
configuration will be ignored in group reporting.
170
Fields in group reporting for greenhouse gas emission reporting – slide 5
Additional master data field configuration for GHG fields – part 2
1
2
3
4
5
6
1 Here you can see the standard configuration which is delivered via content for the GHG fields:
2 • All nine GHG fields are enabled for input (e.g. postings). For more information why this setting cannot be deactivated for GHG Scope, GHG Category, and GHG Scope 2 Calculation Method please refer to the next slide.
Note: For upgrade customers the new GHG fields (i.e. GHG Data Quality Characteristic, GHG Energy Classification, GHG Energy Mix, and GHG Energy Sourcing Type) will be input enabled as well. In case an upgrade
customer already activated the business function for GHG fields before the upgrade to S/4HANA 2502, the additional fields will be immediately available after upgrade e.g. for manual posting.
3 •
SAP delivers master data for the GHG fields according to the GHG protocol. Using these delivered values is sufficient for group reporting in most cases. Therefore additional master data is not supported for most of the GHG
fields. For Sustainability Mode of Transport additional master data is supported but not activated by default, but may be activated by customer at any point in time if required.
4 •
5 •
Global hierarchies and hierarchical elimination are not supported for any of the nine GHG fields.
6 •
As transactional data for GHG emission reporting does not reside in universal journal, the release universal journal task cannot be used to transfer GHG data to group reporting (instead GRDC data mapping or flexible file
upload have to be used). In order to make this transparent the “Aggregate Data on Release” setting is shown as activated for any of the GHG fields and cannot be deactivated by customers.
Aggregate on carryforward is supported for any GHG fields except GHG Scope, GHG Category, and GHG Scope 2 Calculation Method, but is not activated by default (i.e. by default this information is carried forward into the
next fiscal year in group reporting). For more information why this setting cannot be activated for the other three GHG fields please refer to the next slide.
• Only relevant for customers using activity-based consolidation of investments (ABCOI) and not shown on the screenshot: As ABCOI does not support the GHG fields end-to-end, for all nine GHG fields “Aggregate on
171
i Public
Activity-Based COI” is enabled and the setting cannot be removed by the customer. For further details please refer to the dedicated chapter on “Aggregation of additional master data fields during ABCOI”.
Fields in group reporting for greenhouse gas emission reporting – slide 6
Additional master data field configuration for GHG fields – part 3
2
1
3
1
For GHG Scope, GHG Category, and GHG Scope 2 Calculation Method there is specialty in the additional master data field configuration compared to other additional master data fields:
“Enable Inputs” is activated for all three fields and cannot be switched off by customer, and “Aggregate on Carryforward” is deactivated and cannot be switched on by customers.
Therefore these fields are read only in the configuration at any point in time. This slide explains why these settings cannot be changed by customers.
2
Reasons for not allowing the deactivation of the “Enable Inputs” setting:
Public
3 Reason for not allowing the activation of the “Aggregate on Carryforward” setting:
•
GHG Category is the leading key for GHG emission reporting which has to be filled in any case for GHG emission
reporting. By switching on the business function “Activate Fields for Greenhouse Gas” the customer decided to go for
GHG emission reporting. Consequently GHG Category has to be filled and therefore "Enable Inputs" is activated by
content and cannot be deactivated by the customer.
•
As leading key of GHG emission reporting GHG Category has to be filled in any case for
GHG emission data. Therefore it is not allowed to activate the “Aggregate on
Carryforward” setting for GHG Category, as this would clear this information for data
carried forward into the next fiscal year in group reporting.
•
According to the GHG data model GHG Scope is an implicit part or mandatory attribute of GHG Category, e.g. the
GHG Category “2.01 – Scope 2 - Purchased electricity” automatically requires “2 – Purchased energy” as GHG
Scope. So for each GHG Category value, automatically a dedicated GHG Scope value can be derived. Therefore
“Enable Inputs” for GHG Scope is consequently activated by content as well and cannot be deactivated by customer.
•
As GHG Scope goes hand in hand with the GHG Category, GHG emission data that is
carried forward always has a GHG Scope. Consequently it is not allowed to activate the
“Aggregate on Carryforward” for GHG Scope.
•
•
According to the GHG data model the same Scope 2 carbon emission data may be reported along different GHG
Scope 2 Calculation Methods (“LB – Location-based” and “MB – Market-based”). Therefore “Enable Inputs” is
activated by content for GHG Scope 2 Calculation Method and cannot be deactivated by the customer.
As explained, the same GHG Scope 2 carbon emission data may be reported along
different GHG Scope 2 Calculation Methods (“LB – Location-based” and “MB – Marketbased”). In order to avoid double counting of data by aggregation across GHG Scope 2
Calculation Methods, the “Aggregate on Carryforward” setting cannot be activated.172
Fields in group reporting for greenhouse gas emission reporting – slide 7
Behavior of GHG fields in group reporting
i Apart from the specialty that the GHG fields are only available within group reporting, once a customer has activated them via the business function “Activate
Fields for Greenhouse Gas”, they basically behave according to their additional master data field configuration settings as any other additional master data field.
For example they are available in the following applications, tasks, queries, and cubes:
Applications:
Tasks:
• Define Master Data for Consolidation Fields
• Balance Carry Forward
• Import Consolidation Master Data
• …
• Define Selections
• Group Data Analysis
• Group Data Analysis - With Reporting Rules
• Group Financial Statements - Review Booklet
• Display Group Journal Entries
• Display Group Journal Entries - With Reporting Logic
Queries:
• Balance Sheet – Query
(C_CnsldtnBalanceSheetQ)
• Cash Flow Statement
(C_CnsldtnCashFlowQ)
• Income Statement - Function of Expense (C_CnsldtnIncStmntFuncOfExpnQ)
• Income Statement - Nature of Expense
(C_CnsldtnIncStmntNatrOfExpnQ)
Cubes:
• Group Reporting Data - Cube
(I_CnsldtnGrpJrnlItemC)
• Rule-Based Group Data Analysis - Cube
(I_CnsldtnRuleBsdGrpJrnlItemC)
! Please note: As transactional data for GHG emission reporting does not reside in universal journal, the release universal journal task cannot be used to
transfer GHG data to group reporting. Instead GRDC data mapping or flexible file upload have to be used.
Public
173
Task Log: Data Collection
Public
174
Group journals for elimination of inter-company sales
Inter-company sales
and costs of sales are eliminated in
Unrealized profits of the same inter-company transaction are eliminated in
Public
175
Group journals for elimination of carbon emissions of inter-company sales
CO2 emissions
Public
of the Inter-company sales are eliminated along with the GHG information in
176
Group Data Analysis example
Public
177
Appendix
Public
Building blocks for an integrated group close
[cloud]
SAP Group Reporting
Data Collection
[cloud]
SAP Analytics
Cloud
AVAILABLE NOW
AVAILABLE NOW
[cloud / on-premise]
SAP S/4HANA Accounting
and Consolidation
AVAILABLE NOW
[cloud/on-premise]
SAP or
third party apps
[on-premise]
SAP disclosure
management
FUTURE
Public
AVAILABLE NOW
ǀ MORE: https://blogs.sap.com/2019/05/13/sap-s4hana-finance-for-group-reporting-product-strategy/
179
SAP’s integrated platform for group reporting
SAP
ERP
▪ Ensure data
quality
continuously
SAP
ERP
Non SAP
ERP
Non SAP
ERP
SAP Group Reporting
Data Collection (GRDC)
SAP Analytics
Cloud
SAP Disclosure
Management
Non-SAP sources | Non-financials | Notes
Dashboarding | Analytics | Planning
Publish online / print | Electronic submission
▪ Accelerate your
group close
process
SAP S/4HANA
Universal journal
▪ Simplify the user
experience from
entity to group
close
Group Reporting
▪ Transparency
and auditability
down to the line
item
General and Operational
Accounting
SAP
ERP
Public
Public
SAP
ERP
Non SAP
ERP
Non SAP
ERP
180
Simplification of group reporting in SAP S/4HANA (cloud and on-premise)
LEGACY LANDSCAPE
S/4HANA LANDSCAPE
Financial consolidation/Group close
SAP S/4HANA Finance for group reporting
R
R
R
Consolidation/Group close [ACDOCU]
R
Data warehouse
CSV
Accounting/Local close [ACDOCA]
CSV
R
R
R
ETL tools
R
R
Other
ERP
R
R
R
SAP
ERP
SAP
ERP
SAP
ERP
Public ǀ MORE: https://blogs.sap.com/2019/05/13/sap-s4hana-finance-for-group-reporting-product-strategy/
R
Other
ERP
Other
ERP
SAP
ERP
SAP
ERP
SAP
ERP
Other
ERP
182
Fundamental concepts
Data model and master data
Data model
Master data content
Global parameters / reporting event
- Version, CoA, ledger, year, period
FS items
- Chart of Accounts
- Functions controlled through attributes
Documents
- Posting level, document types
- Document number, …
- Local currency, group currency, transaction currency, quantity
Consolidation organizational objects
- Consolidation group (representing the legal group)
- Consolidation units (companies)
- Partner unit
FS item/ consolidation characteristics
- FS items
- Subitems / subitem category
Additional characteristics
- Unified accounting & consolidation master data on objects such as GL
account, profit center, cost center, profitability accounting objects, etc.
- Hierarchies
“Virtual” characteristics, i.e. calculated at report run time
- Reporting items
- Elimination dimensions for cons units / segment / PC
Public
Subitems- transaction types
- All B/S accounts
- Integration with accounting consolidation transaction type
Subitems - functional areas
- All P&L accounts for I/S by functional area (Cost of Sales)
- Integration with accounting functional area
Cons Units, Partner Units, Cons Groups
- Sample set for testing, demo and customer evaluation
- Set of companies that exist in accounting + some for flexible upload
Additional characteristics
- Sample master data
Reporting items
- Master data for I/S by functional area, Cash Flow, Statement of changes in
Equity, etc.
183
Fundamental concepts
Posting level / document type
Every data record is assigned to a document type with user, date/time of entry information.
Each document type is assigned to a posting level.
Consolidated data
Standardized data
Reported data
Posting levels
Public
Auto only
Relation for reporting logic or PCC
Blank
Accounting data (actuals, plan)
0C
Corrections to reported data (combined consistency check with blank)
00
Reported data (file, manual data collection, API)
01
Corrections to reported data carried forward to 00
10
Adjustments to reported data
20
Eliminations
Pair (Cons Unit + Partner)
30
Consolidations
Cons Group
02, 12
Preparation of changes to the consolidation group

22
Preparation of changes to the consolidation group

Cons Unit
Cons Group + Cons Unit Pair
184
Fundamental concepts
Data monitor
Corporate / Group view
Data monitor functions
• Balance carry forward
• Release accounting docs (ACDOCA, ACDOCP)
• Data collection (Flexible upload, API, GRDC input reports and
mapping)
• Line item validation (consistency on reported & corrected data)
• Calculation of Net Income (LC)
• Validation of reported data (LC) and standardized data (GC)
• Manual standardizing entries (PL10 / LC + GC)
• Currency translation
• Delivered content:
o
o
o
o
Single company view
Y0901: Standard YTD
Y0902: Keep GC value from S4; B/S retranslate @ closing
S0901, S0902: period of acquisition (YTD / periodic)
S0903: Standard periodic
• I/C Reconciliation (Fiori tiles, not integrated in the monitor)
– >=1908 / 1909 IC matching and reconciliation solution
– <1908: IC report company level
– < 1902: IC report company level, group level
Public
185
Fundamental concepts
Consolidation monitor
Consolidation monitor functions
•
•
•
•
•
•
•
•
Single sub-group view
IC P&L Sales & COGS one-sided (one-sided)
IC P&L other income / expense (two-sided)
IC Dividends (one sided triggered by receiving company)
IC Eliminations B/S (two-sided)
Manual Eliminations Entries (PL20)
Preparation for Cons Group Changes
Manual Consolidation Entries (PL30)
Validation of Consolidated data
Options for group shares and Consolidation of
Investments (COI)
2 alternative options for COI which can be setup in the monitor
• Activity-based COI
– Requires tasks 2101 Activity Based COI
– Can use task 2141 to post group shares to statistical FS
items (optional for information purpose in analytics)
• Rule-based COI
– Requires tasks 2100 Investment / Equity elimination (incl.
NCI, dividends, change in equity, change in ownership %),
2180 Total divestiture
– Enter group shares with task 2140 or calculate group
shares with task 2141 based on direct shares entered
through flat file
Public
Activity based COI
(as alternative option to rule-based)
Rule based COI
186
Fundamental concepts
Consolidation of investments (C/I) involving steps on ownership %
1.
Load reported data w/o ownership (DT “00”)
2.
Load investment related data incl. ownership percentage
A Direct share % as a metric of investment account ; reverse data loaded in step 1. above (DT “0B”), or
B Post group share % to FS item S00001 (PL 30) for rule based CoI
3.
(optional) Run calculation of group share in the monitor if step 2.A. above is chosen and rule
based C/I is adopted-> the task will update FS items $000000SHG , $000000SHD, etc.
4.
Run consolidation of investment
A Rule based (based on reclass. method) or
B Activity based (built-in logic based on automatically calculated group share %)
5.
Public
(optional) If adjustment of group share is needed, repeat step 2. onwards above
187
Fundamental concepts
Task logs
The most important logs are integrated
into this app:
▪ File import
▪ API
▪ Journal import (manual journals)
▪ Currency Translation
▪ Validation
▪ Reclassification (consolidations)
Public
188
Fundamental concepts
Group Reporting Data Collection (GRDC)
GRDC is an app to help you collect
financial data, non-financials and
comments into SAP S/4HANA for group
reporting – in the ACDOCU
consolidation table. It provides two
main features. With GRDC Data
Mapping, you can automate the
mapping, transformation and data load
from SAP and non-SAP systems into
ACDOCU. With GRDC Forms, you can
enter data and comments manually in
ACDOCU using pre-delivered forms, or
by creating your own.
More information: SAP Group Reporting
Data Collection in Brief
Public
189
SAP S/4HANA Cloud for group reporting
SAP Help Portal and Consulting notes
SAP Help Portal
S/4HANA for group reporting Cloud
https://help.sap.com/S4_CE_GR
S/4HANA for group reporting On Premise
https://help.sap.com/S4_OP_GR
Group Reporting Data Collection (GRDC)
https://help.sap.com/viewer/product/SAP_Group_Reporting_Data_Collection/1.0/en-US
Consulting Notes
Use totals validation and ICMR elimination for extension version
2659656 - FAQ about SAP S/4HANA Cloud for
group reporting https://launchpad.support.sap.com/#/notes/2659656
2659672 - FAQ about SAP S/4HANA Finance for group reporting
(On Premise) https://launchpad.support.sap.com/#/notes/2659672
2916087 – Configuration guide for IC Matching & Reconciliation
https://launchpad.support.sap.com/#/notes/2916087
3048807 - Group Reporting: Combined stack of Old and New reporting logic is delivered with S4H 2105 CE
https://launchpad.support.sap.com/#/notes/3048807
Public
190
SAP S/4HANA Cloud for group reporting
SAP Road Map Explorer
SAP Road Map
Public
https://roadmaps.sap.com/board?BC=6EAE8B27FCC11ED892E919ED096400CC&range=FIRST-LAST
191
SAP S/4HANA Cloud for group reporting
SAP Community, release blogs
Join our Group
Reporting community
https://community.sap.com/topics/s4hana-group-reporting
Product Engineering
strategy
https://blogs.sap.com/2019/05/13/sap-s4hana-finance-for-group-reporting-product-strategy/
New features’ in Group
https://blogs.sap.com/2020/05/20/sap-s-4hana-finance-for-group-reporting-release-blogs/
Reporting / SAP Blogs
Public
192
SAP S/4HANA Cloud for group reporting
SAP Community, how-to guides
How to Integrate SAP
Analytics Cloud for
https://blogs.sap.com/2022/08/02/how-to-integrate-sap-analytics-cloud-for-planning-with-sap-s-4hana-forPlanning with SAP S/4HANA group-reporting/
for Group Reporting
How to create your own
Dashboard/Story
https://blogs.sap.com/2019/12/25/embedded-analytics-sap-analytics-cloud-in-sap-s-4hana-cloud-how-tocreate-your-own-dashboard-or-story/
How to create Data
Analyzer Report
https://blogs.sap.com/2019/12/29/embedded-analytics-sap-analytics-cloud-in-sap-s-4hana-cloud-how-tocreate-data-analyzer-report/
How to transport
Embedded Story/Data
Analyzer Report
https://blogs.sap.com/2019/12/29/embedded-analytics-sap-analytics-cloud-in-sap-s-4hana-cloud-how-totransport-embedded-story-data-analyzer-report/
Intercompany Matching
and Reconciliation video
https://www.youtube.com/watch?v=05jadAXVlEY
Public
193
Thank you.
Contact information:
SAP Group Reporting community
https://community.sap.com/topics/s4hana-group-reporting
https://community.sap.com/topics/s4hana-group-reporting
© 2025 SAP SE or an SAP affiliate company. All rights reserved. See Legal Notice on www.sap.com/legal-notice for use terms, disclaimers, disclosures, or restrictions related to this material.