It is time for Carlo to take a closer look at some of the settings available in a financial statement version. He is particularly interested in the semantic tag parameter, which can be customized to meet Bike Company’s specific reporting needs.
Semantic Tags
Semantic tags in SAP S/4HANA Cloud are textual identifiers used to highlight key figures in financial statement versions (FSVs).
These tags are linked to structures of financial statement versions (FSVs), easing the calculation of metrics and key performance indicators (KPIs) for analytical reporting.
Standard semantic tags, along with incorporated calculation logic, are provided as a standard feature of the system within the following semantic tag groups:
- BS (Balance Sheet Group)
- IS (Income Statement)
- FIX (Fixed Semantic Tags).
Semantic tags provide a wealth of benefits when applied to financial statement versions in SAP S/4HANA, such as: improved data accessibility, interpretation and consistency, enhanced reporting capabilities and simplified data querying.

The special nodes also use pre-delivered semantic tags, for example, for the calculation of Total Assets or Liabilities and Equity.
Moreover, additional semantic tags can be assigned to structuring components of a financial statement version, such as financial statement hierarchy nodes and G/L accounts. This enables the system to determine and exhibit accurate results in financial statements, like balance sheets, income statements, and cash flow statements.
Beyond the standard semantic tags that are offered, SAP S/4HANA Cloud also allows you to construct your own custom semantic tags to cater to your unique reporting requirements. These custom tags need to be associated with the correct financial statement versions (FSVs).
Advanced technical users can subsequently create customized analytical queries to reference the new semantic tags in order to use them.
For instance, Carlo needs to create a semantic tag that captures data specific to local accounting reporting standards. He can create the custom semantic tag and assign it to the corresponding financial statement version that is used to represent the local accounting reporting standards. Aligning his custom semantic tags with the FSV ensures that those specific metrics are accurately represented in his reports.
However, making these changes in the system might not be enough. Eventually, he will also have to adjust the correlating analytical queries in order to accommodate these modifications. For example, if he created a new semantic tag called 'Local GAAP Adjusted Sales', he would need to update his sales report queries to include this tag. This way, his reports will pull information based on the new semantic tag, providing a more detailed and specific analysis as per Bike Company’s needs.
The advantage of this procedure is that it is very easy to maintain the new semantic tag in the financial statement version, for example, to include or exclude certain accounts. Once this update of the semantic tag is completed, the reports or KPIs using it will not need further modification.