SAP Community - SAP S/4HANA Embedded Analytics

SAP Premium Engagement: Analytics Strategy Workshop

2023-12-11T09:49:49+01:00

Who we are

We are SAP’s Center of Expertise (COE) for Analytics, Planning, and Consolidation in the globally operating Adoption Service Center. Our goal is to drive adoption and consumption of SAP Business Technology Platform technologies and lay the foundation for the Intelligent Enterprise. We are a trusted partner for customers with MaxAttention or Premium Engagement (PE). Also, we engage in the area of Professional Services, Preferred Success and other partnerships.

Introduction

In the fast-paced and ever-evolving landscape of business intelligence, having a robust analytics and data management architecture is crucial for staying ahead of the curve. Enter the SAP Analytics Strategy Workshop – a comprehensive solution designed to help organizations define a future-proof framework aligned with both business and IT requirements, laying the foundation for the Intelligent Enterprise.

Unveiling the Service Component

The SAP Analytics Strategy Workshop covers a spectrum of essential topics and provides orientation and guidance to define a strategic direction for a customer specific Analytics and Data Warehousing Architecture.

Key solutions are:

SAP S/4HANA Embedded Analytics

SAP HANA Data Warehouse Strategy (SAP Datasphere, SAP BW/4HANA , SQL-modeled HANA data warehouse)

SAP Analytics Cloud, SAP BusinessObjects

SAP Data Intelligence (Cloud)

Integration Scenarios (Data lakes, Hybrid Scenarios)

This encompasses both on-premise and cloud solutions, ensuring adaptability and scalability as organizations navigate the digital landscape.

The Customer's Agenda

The primary objectives for customers opting for this service include:

Leveraging Full Capabilities: Utilize the complete potential of SAP analytics and data warehousing solutions to enhance business efficiency, agility, and real-time decision-making for users.

Guidance on Latest Solutions: Receive expert guidance on the latest SAP Analytics solutions and the SAP Datasphere concept/design. Understand seamless integration with data lakes and other analytical applications, whether on-premise or in the cloud.

Holistic Analytics Concept: Establish a holistic analytics concept that seamlessly integrates SAP on-premise and cloud solutions, along with non-SAP solutions.

Delivery Approach & Scope

The delivery approach typically involves a 3 to 4-day remote or onsite workshop, beginning with a scoping call to tailor the agenda according to customer requirements. The scope includes:

Identifying crucial use cases, pain points, and challenges and mapping them to capabilities and solution components.

Knowledge transfer sessions covering recommended SAP solution components such as SAP S/4HANA embedded analytics, SAP Analytics Cloud, SAP BW/4HANA, SAP Datasphere, and SAP Data Intelligence.

Defining the target analytics solution landscape and creating a high-level milestone plan.

Example of a Target Solution Landscape in an AST Workshop

Value and Benefits

Engaging in the SAP Analytics and Data Management Service Component yields significant value and benefits for organizations. The outcomes include:

A final report with recommendations for a data warehouse and analytics architecture that aligns with specific reporting requirements.

A customer-specific roadmap complete with a high-level milestone plan.

Proposed target analytics solution landscapes (options) for the next 3 to 5 years, encompassing both on-premise and cloud components.

These service outcomes, in turn, serve as a foundation for subsequent phases, such as the analytics design service component in the explore phase, ensuring a seamless and future-proof analytics and data management journey for the Intelligent Enterprise.

Service Assignment Options

This service is available for a variety of SAP support frameworks, including Value Assurance, SAP MaxAttention, SAP Active Embedded, and SAP Active Attention. Customers are encouraged to engage in discussions about their Analytics and Data Warehouse solution landscape at an architecture level, delving into their business needs and aspirations.

Don’t hesitate to reach out to your Technical Quality Manager (TQM), your SAP Account, your Customer Success Partner (CSP), or our central entry channel, the Virtual Project Room (VPR) to unleash the full potential of SAC, the unrivaled symphony of data insights that elevate your business intelligence to new heights.

Conclusion

The SAP Analytics Strategy Workshop is more than a service; it's a strategic partnership in navigating the complex landscape of data-driven decision-making. As organizations embark on this journey, they do not merely adapt – they evolve into Intelligent Enterprises, equipped to thrive in an era where data is not just a resource but a strategic advantage. The future of analytics and data management is now, and with SAP, it's intelligent, insightful, and ready for whatever comes next.

Attribute Based Access Control (ABAC) – Field Masking scenario in Analytical Queries using Query Browser app

2023-12-18T06:40:22+01:00

Introduction

In this blog, we will learn how to mask Stock Quantity field information based on Stock Material field information of C_STOCKQUANTITYCURRENTVALUE (Current Stock Quantity and Value) Analytical Query. Analytical Queries are used for reporting and analysis.

Stock Quantity field information of C_STOCKQUANTITYCURRENTVALUE (Current Stock Quantity and Value) Analytical Query need to be masked where “Stock Material” is “CCMPROD01”, “CCMPROD03”, “CCMPROD05”, “CCMPROD07”, and “CCMPROD09”. For other “Stock Material”, “Stock Quantity” field will appear as unmasked.

Attribute based authorizations are dynamic determination mechanism which determines whether a user is authorized to access specific data sets which can be based on the context attributes of the user and data (for example, price of certain sensitive materials are masked).

S/4HANA Embedded Analytics

Analytics is one of the most typical and tangible value of S/4HANA. S/4HANA Embedded Analytics is the function for real-time operational analytics in S/4HANA. It consists of ABAP CDS Views as data source and Fiori Analytical application as the frontend. As the frontend, other than S/4HANA Embedded Analytics, SAP Analytics Cloud is available which is used together with S/4HANA embedded analytics.

SAP Query Browser app

SAP Query Browser is a powerful Fiori app for embedded analytics which is used to view, retrieve, and analyze analytical queries. It is used to search, browse, and tag the analytical queries quickly and easily. It is available as a tile in SAP Fiori Launchpad. It displays all the authorized SAP standard and custom analytical queries to which the user has access.

SAP_BR_EMPLOYEE Query Browser role must be assigned to a user to access the Query Browser app.

To launch the Query Browser application, choose Query Browser from the Query Browser catalog.

In Query Browser app, analytical queries can be searched using view names, view descriptions, view column names, annotations, tables, and user added tags.

Here, we will use SAP Query Browser to showcase masking of sensitive fields of analytical queries. We will configure Masking through Manage Sensitive Attributes app provided by UI Data Protection Masking for SAP S/4HANA 2011 solution based on Attribute Based Authorization Control (ABAC) concept.

Manage Sensitive Attributes app

The Manage Sensitive Attributes application allows you to maintain configuration for UI data protection in an SAP Fiori-based UI.

This application brings together several individual transactions, simplifying the maintenance of masking configuration and presenting a holistic picture to the end user. With this app, you can:

Create, update, and delete sensitive attributes

Define masking and blocking configurations

Manage technical attribute mappings

Create and assign context attributes

Create and assign derived attributes and lists of values

You can use the app on your desktop, tablet, or smartphone.

Prerequisite

UI Data Protection Masking for SAP S/4HANA is a solution that allows you to protect restricted and sensitive data values at field level by masking, clearing, or disabling fields for those users who are not authorized to view or edit this data.

Product “UI data protection masking for SAP S/4HANA” is used in this scenario to protect sensitive data at field level and must be installed in the S/4HANA system.

The product is a cross-application product which can be used to mask/protect any field in SAP GUI, SAPUI5/SAP Fiori, CRM Web Client UI, and Web Dynpro ABAP.

Requirement

Here, we want to configure masking for Stock Quantity field information based on Stock Material field information of C_STOCKQUANTITYCURRENTVALUE (Current Stock Quantity and Value) Analytical Query result using Attribute-based authorization concept.

Product “UI data protection masking for SAP S/4HANA 2011” is used in this scenario to protect sensitive data at field level and must be installed in the S/4HANA system.

Let’s begin

Configuration to achieve masking Stock Quantity field

Login to Fiori Launchpad and click on “Manage Sensitive Attributes” app available under “UI data protection masking” catalog.

Maintain Sensitive Attributes

A Sensitive Attribute is a type of logical attribute that define a field which needs to be configured for UI data protection.

Click on Add icon

Enter “LA_EA_STOCK_QTY” in Sensitive Attribute field

Enter “EA Stock Quantity” in Description field

Click on “Create” button

Sensitive Attribute with specified details will be created.

Maintain Mapping to Technical Addresses

In the Manage Sensitive Attributes application, you can link technical addresses of fields to sensitive attributes. A technical address describes the exact technical path or technical information which is used by the solution to process the field for UI data protection masking.

To suppress the records in Analytical Queries, Technical Information (InfoProvider-Query-InfoObject) is required. To retrieve the Technical Address for Analytical Query fields, you need to use Recording Tool feature to get the Technical Address as Technical Information on press of F1 key is not available here.

Refer to this blog to know how to use the Recording tool.

Under Technical Mapping > Analytics, choose the Add icon.

Use the value help to select the InfoProvider, Query, and InfoObject information. You can also enter the referenced query name as a comment to describe the mapping.

Maintain Context Attributes

In the Manage Sensitive Attributes application, you can create and update context attributes, and map them to sensitive attributes.

A context attribute is a type of logical attribute which is used to define the context within which a sensitive attribute is to be protected.

To assign a context attribute to a sensitive attribute, under Context Attributes, choose the Add icon.

To create a new context attribute, select Create New, enter the name of the context attribute beginning with LA_ and a description.

Open a context attribute by tapping the arrow next to it and under Technical Mapping, you can map technical addresses to the context attribute in the same way we did for sensitive attribute

Maintain Additional Attributes – Configure Value Range

In the Manage Sensitive Attributes application, you can create and update value ranges to provide context for protecting a sensitive attribute.

A Value Range is a static collection of values that can be used as the context within which a sensitive attribute is to be protected.

To create a new value range for,Sensitive Stock Materials

Navigate to “Additional Attributes” tab

Click on “Value Ranges” option

Click on “Add” icon

Select “Create New“

Select Range Type as “List of Values“

Enter the name of the value range beginning with VR_ for a list of values as “VR_STOCK_MATERIAL“

Description as “List of Stock Materials”

Click on “Create” button.

Value Range with specified details will be created.

Click on VR_STOCK_MATERIAL link to add values in this Value Range. You will be navigated to Manage Derived Attributes/Value Ranges app

Click on Include Value option under Maintain List of Values tab

Click on “Add” icon under Include Value section

Enter “Value” as “CCMPROD01”

Enter “Comment” as “CCM Product 1”

Click on “Create” button

Enter following entries in “VR_STOCK_MATERIAL” Value Range

Masking Configuration

In the Manage Sensitive Attributes application, you can configure masking for a sensitive attribute to define in detail how it is to be protected in the system. Masking configuration defines which fields are to be masked for unauthorized users and in which contexts.

To configure masking for a sensitive attribute, under Configuration > Masking Configuration, choose Edit.

Enable masking.

Select Attribute Based authorization concept.

Click on “Add” icon next to “Policy” edit box

Enter Policy Name as “POL_MASK_STOCKINFO“.

Enter Description as “Mask Stock info based on Stock Material in Embedded Analytics Query“.

Click on “Create” button.

Policy will get created.

Click on “Save” button.

Click on “Mask Stock info based on Stock Material in Embedded Analytics Query (POL_MASK_STOCKINFO)” link. You will be navigated to “Manage ABAC Policies” app

Choose “Edit” under “Rule” section of Policy

ABAC Policy Cockpit will be opened

Write following logic into Policy

Masking in Analytical Query

Click on Query Browser app

Enter “C_STOCKQUANTITYCURRENTVALUE” in Search field and click on “Search” button

Select the checkbox and click on “Open for Analysis” button

Enter highlighted search criteria in the corresponding fields and click on “OK” button

Stock Quantity field value will appear as masked where Stock Material is "CCMPROD01", "CCMPROD03", "CCMPROD05", "CCMPROD07", and "CCMPROD09".

Note: For Stock Quantity field, original value will be replaced by 0.00 as the same is a Key figure and a notification will also be displayed by the system for the same.

Conclusion

In this blog post, we have learnt how Attribute-based masking is achieved in Analytical Queries in SAP Query Browser app for masking sensitive field information.

Attribute Based Access Control (ABAC) – Field Masking scenario in Analytical Queries using SAP Analytics Cloud

2023-12-18T06:44:43+01:00

Introduction

In this blog, we will learn how to mask Controlling Area field information based on Order Number field information of Production Cost by Order (C_PRODUCTCOSTBYORDERQUERY) Analytical Query displayed in SAP Analytics Cloud Story. Analytical Queries are used for reporting and analysis.

Attribute based authorizations are dynamic determination mechanism which determines whether a user is authorized to access specific data sets which can be based on the context attributes of the user and data (for example, price of certain sensitive materials are masked).

S/4HANA Embedded Analytics

SAP Analytics Cloud

SAP Analytics Cloud is an end-to-end cloud solution that brings together business intelligence and enterprise planning, augmented with the power of artificial intelligence, machine learning technology, and predictive analytics in a single system.

The main benefits of SAP Analytics Cloud include ease of viewing content, connectivity to trusted data, access to various visualization tools, augmented analytic capabilities, and financial planning features. In a single cloud system one can analyze, ask, predict, plan, and report.

Stories are main part of SAP Analytics to explore data and to find deep insight using charts and tables. An SAP Analytics Cloud Story is a presentation-style document that uses charts, visualizations, text, images, and pictograms to describe data.

Here, we will use Story to showcase masking of sensitive fields of analytical queries in SAP Analytics Cloud. We will configure masking through Manage Sensitive Attributes app provided by UI Data Protection Masking for SAP S/4HANA 2011 solution based on Attribute Based Authorization Control (ABAC) concept.

Manage Sensitive Attributes app

Create, update, and delete sensitive attributes

Define masking and blocking configurations

Manage technical attribute mappings

Create and assign context attributes

Create and assign derived attributes and lists of values

You can use the app on your desktop, tablet, or smartphone.

Prerequisite

Requirement

Here, we want to configure masking for Controlling Area field based on Order Number field information in Production Cost by Order story in SAP Analytics Cloud using Attribute-based authorization concept.

Product “UI data protection masking for SAP S/4HANA 2011” is used in this scenario to protect sensitive data at field level and must be installed in the S/4HANA system.

Let’s begin

Configuration to achieve masking Controlling Area field

Login to Fiori Launchpad and click on “Manage Sensitive Attributes” app available under “UI data protection masking” catalog.

Maintain Sensitive Attributes

A Sensitive Attribute is a type of logical attribute that define a field which needs to be configured for UI data protection.

Click on Add icon

Enter “LA_EA_CONTROL_AREA” in Sensitive Attribute field

Enter “EA Controlling Area” in Description field

Click on “Create” button

Sensitive Attribute with specified details will be created.

Maintain Mapping to Technical Addresses

Maintain Context Attributes

To assign a context attribute to a sensitive attribute, under Context Attributes, choose the Add icon.

To create a new context attribute, select Create New, enter the name of the context attribute beginning with LA_ and a description.

Open a context attribute by tapping the arrow next to it and under Technical Mapping, you can map technical addresses to the context attribute in the same way we did for sensitive attribute

Maintain Additional Attributes – Configure Value Range

Navigate to “Additional Attributes” tab

Click on “Value Ranges” option

Click on “Add” icon

Select “Create New“

Select Range Type as “List of Values“

Enter the name of the value range beginning with VR_ for a list of values as “VR_ORDER_NUMBER“

Description as “List of Order Numbers”

Click on “Create” button.

Value Range with specified details will be created.

Click on VR_ORDER_NUMBER link to add values in this Value Range. You will be navigated to Manage Derived Attributes/Value Ranges app

Click on Include Value option under Maintain List of Values tab

Click on “Add” icon under Include Value section

Enter “Value” as “0000001000121”

Enter “Comment” as “1000121”

Click on “Create” button

Enter following entries in “VR_ORDER_NUMBER” Value Range

Masking Configuration

Enable masking.

Select Attribute Based authorization concept.

Click on “Add” icon next to “Policy” edit box.

Enter Policy Name as “POL_MASK_CTRAREA“.

Enter Description as “Mask Controlling Area based on Order Number in SAC Story“.

Click on “Create” button.

Policy will get created.

Click on “Save” button.

Click on “Mask Controlling Area based on Order Number in SAC Story (POL_MASK_CTRAREA)” link. You will be navigated to “Manage ABAC Policies” app.

Choose “Edit” under “Rule” section of Policy.

ABAC Policy Cockpit will be opened.

Write following logic into Policy

Masking in SAP Analytics Cloud Story

Click on “Production Cost by Order” Story.

Controlling Area field value will appear as masked where Order Number is “0000001000121”, “0000001000123”, "0000001000125", "0000001000127", and “0000001000129”.

Conclusion

In this blog post, we have learnt how Attribute-based masking is achieved in Analytical Queries in SAP Analytics Cloud for masking sensitive field information.

Attribute Based Access Control (ABAC) – Field Masking scenario in Analytical Queries using Query Monitor (RSRT TCode) in WD Grid (Embedded) Query Display mode

2023-12-18T06:45:18+01:00

Introduction

In this blog, we will learn how to mask Supplier field information based on Company Code field information of Cash Discount Forecast Analytical Query. Analytical Queries are used for reporting and analysis.

Supplier field information of Cash Discount Forecast Analytical Query need to be masked where “Company Code” is “KR01”, “RU04”, and “TP02”. For other “Company Code”, “Supplier” field will appear as unmasked.

Attribute based authorizations are dynamic determination mechanism which determines whether a user is authorized to access specific data sets which can be based on the context attributes of the user and data (for example, price of certain sensitive materials are masked).

S/4HANA Embedded Analytics

Analytics is one of the most typical and tangible values of S/4HANA. S/4HANA Embedded Analytics is the function for real-time operational analytics in S/4HANA. It consists of ABAP CDS Views as data source and Fiori Analytical application as the frontend. As the frontend, other than S/4HANA Embedded Analytics, SAP Analytics Cloud is available which is used together with S/4HANA embedded analytics.

Query Monitor (RSRT TCode)

The Query Monitor tests, checks, and is used to test or regenerate queries and query views, and to check or change query properties. A detailed analysis of queries can be done with the transaction RSRT (Query Monitor) in a very convenient way. With the help of the Query Monitor you can run and analyze queries without a BW front end.

To launch the Query Monitor, execute transaction RSRT.

Here, we will use Query Monitor to showcase masking of sensitive fields of analytical queries. We will configure masking through UI Data Protection Masking for SAP S/4HANA 2011 solution based on Attribute Based Authorization Control (ABAC) concept.

Prerequisite

Requirement

Here, we want to configure masking for Supplier field information based on Company Code field information in Cash Discount Forecast Analytical Query result using Attribute-based authorization concept.

Product “UI data protection masking for SAP S/4HANA 2011” is used in this scenario to protect sensitive data at field level and must be installed in the S/4HANA system.

Let’s begin

Configuration to achieve Masking

Logical Attribute is a functional modelling of how any attribute such as Social Security Number, Bank Account Number, Amounts, Pricing information, Quantity etc. should behave with masking.

Configure Context Attribute

Follow the given path:

SPRO -> SAP NetWeaver -> UI Data Protection Masking for SAP S/4HANA -> Sensitive Attribute Configuration -> Maintain Metadata Configuration -> Maintain Logical Attributes

Follow below mentioned steps:

Under “Maintain Logical Attributes”, maintain following logical attribute.

Company Code

Click on “New Entries” button

Enter “Logical Attribute” as “LA_EA_COMP_CODE”

Enter “Description” as “EA Company Code”

Click on “Save” button

Configure Sensitive Attribute

Supplier Code

Click on “New Entries” button

Enter “Logical Attribute” as “LA_EA_SUPL_CODE”

Enter “Description” as “EA Supplier Information”

Select “Is Sensitive” checkbox

Click on “Save” button

Maintain Analytics Technical Address

To suppress the records in Analytical Queries, Technical Information (InfoProvider-Query-InfoObject) is required. To retrieve the Technical Address for Analytical Query fields, you need to use Recording Tool feature to get the Technical Address as Technical Information on press of F1 key is not available here.

Refer to this blog to know how to use the Recording tool.

Follow the given path:

SPRO -> SAP NetWeaver -> UI Data Protection Masking for SAP S/4HANA -> Sensitive Attribute Configuration -> Maintain Metadata Configuration -> Maintain Analytics Technical Address

Follow below mentioned steps:

Under “Analytics Technical Address”, maintain technical address for following field.

Company Code

Click on “New Entries” button

Enter “InfoProvider” as “2CIFIAPCSHDISC”

Enter “Query” as “2CCFIAPCSHDISCFCST”

Enter “InfoObject” as “2CIFICOMPANYCODE”

Enter “Logical Attribute” as “LA_EA_COMP_CODE”

Enter “Description” as “EA Company Code”

Click on “Save” button

Supplier Code

Click on “New Entries” button

Enter “InfoProvider” as “2CIFIAPCSHDISC”

Enter “Query” as “2CCFIAPCSHDISCFCST”

Enter “InfoObject” as “2CI_SUPPLIER_CDS”

Enter “Logical Attribute” as “LA_EA_SUPL_CODE”

Enter “Description” as “EA Supplier Code”

Click on “Save” button

Configure Value Range

Value Ranges are a set of pre-populated values which can be used to derive the context under which an action should be executed.

Follow the given path:

SPRO -> SAP NetWeaver -> UI Data Protection Masking for SAP S/4HANA -> Sensitive Attribute Configuration -> Maintain Metadata Configuration -> Maintain Attributes and Ranges for Policy -> List of Values Definition – Follow below mentioned steps:

Sensitive Company List

Click on “New Entries” button

Enter “List of Values” as “VR_PROTECTED_COMPANY_CODE”

Enter “Description” as “Protected Company Codes”

Click on “Save” button

Enter following entries in “VR_PROTECTED_COMPANY_CODE” Value Range

Follow below mentioned steps:

Execute Transaction Code “/UISM/V_RANGE”

Click on “VR_PROTECTED_COMPANY_CODE” Value Range

Click on “Display<- -> Change” button

Click on “Add New Entry” button

Add following entries under “Include Value” tab and click on “Save” button

Policy Configuration

A Policy is a combination of rules and actions which are defined in one or more blocks. The actions are executed on a sensitive entity (field to be protected) which has to be assigned to a Policy. The conditions are based on contextual attributes which help derive the context.

Context Attributes are logical attributes which are used in designing the rules of a policy. They are mapped to fields which are used to derive the context under which an action is to be executed on a sensitive entity.

Sensitive Entities are logical attributes which are sensitive and need to be protected from unauthorized access.

Follow the given path:

SPRO -> SAP NetWeaver -> UI Data Protection Masking for SAP S/4HANA -> Sensitive Attribute Configuration -> Masking and Blocking Configuration -> Maintain Policy Details for Attribute based Authorizations – Follow below mentioned steps:

Click on “New Entries” button

Enter “Policy Name” as “POL_MASK_SUPPLIER”

Select “Type” as “Field Level Masking”

Enter “Description” as “Mask Supplier based on Company Code in EA Query”

Click on “Save” button

Write following logic into Policy

Maintain Field Level Security and Masking Configuration

Here, we will define how masking will behave with the logical attribute that we created in the above step.

Follow the given path:

SPRO -> SAP NetWeaver -> UI Data Protection Masking for SAP S/4HANA -> Sensitive Attribute Configuration -> Masking and Blocking Configuration -> Maintain Field Level Security and Masking Configuration

Follow below mentioned steps:

Click on “New Entries” button

Enter “Sensitive Entity” as “LA_EA_SUPL_CODE” and press “Enter” key. “Description” will get populated in corresponding fields

Check “Enable Configuration” checkbox

Select “Attribute Based Authorization” option

Enter “Policy Name” as “POL_MASK_SUPPLIER”

Click on “Save” button

Masking in WD Grid (embedded) Query Display Mode

Follow below mentioned steps:

Execute “RSRT” TCode

Enter “Query” as “2CIFIAPCSHDISC/2CCFIAPCSHDISCFCST”

Select “Query Display” mode as “WD Grid (embedded)”

Click on “Execute” button

Enter highlighted search criteria in the corresponding fields and click on “Go” button.

Supplier Code and Description field value will appear as masked where Company Code is “KR01”, “RU04”, and “TP02”.

Conclusion

In this blog post, we have learnt how Attribute-based masking is achieved in Analytical Queries in Query Monitor (RSRT TCode) in WD Grid (Embedded) Query Display mode for masking sensitive field information.

Attribute Based Access Control (ABAC) – Field Masking scenario in Analytical Queries using Query Monitor (RSRT TCode) in WD Grid Query Display mode

2023-12-18T06:45:48+01:00

Introduction

In this blog, we will learn how to mask Chart of Account field information based on G/L Account field information of Aging Analysis Smart Business app Analytical Query. Analytical Queries are used for reporting and analysis.

Chart of Account field information of Aging Analysis Smart Business app Analytical Query need to be masked where “G/L Account” is “0011230000”, “0013111000”, "0022010001", "0022020001", and “0024643000”. For other “G/L Account”, “Chart of Account” field will appear as unmasked.

Attribute based authorizations are dynamic determination mechanism which determines whether a user is authorized to access specific data sets which can be based on the context attributes of the user and data (for example, price of certain sensitive materials are masked).

S/4HANA Embedded Analytics

Query Monitor (RSRT TCode)

Prerequisite

Requirement

Here, we want to configure masking for Chart of Account field information based on G/L Account field information in Aging Analysis Smart Business app Analytical Query result using Attribute-based authorization concept.

Product “UI data protection masking for SAP S/4HANA 2011” is used in this scenario to protect sensitive data at field level and must be installed in the S/4HANA system.

Let’s begin

Configuration to achieve Masking

Configure Context Attribute

G/L Account

Click on “New Entries” button

Enter “Logical Attribute” as “LA_EA_GL_ACCOUNT”

Enter “Description” as “EA G/L Account”

Click on “Save” button

Configure Sensitive Attribute

Chart of Account

Click on “New Entries” button

Enter “Logical Attribute” as “LA_EA_CHART_ACCOUNT”

Enter “Description” as “EA Chart of Account”

Select “Is Sensitive” checkbox

Click on “Save” button

Maintain Analytics Technical Address

G/L Account

Click on “New Entries” button

Enter “InfoProvider” as “2CIAPFLXBLAGING”

Enter “Query” as “2CCAPFLXBLAGING”

Enter “InfoObject” as “2CIAPFLXBLAGING-GLACCOUNT”

Enter “Logical Attribute” as “LA_EA_GL_ACCOUNT”

Enter “Description” as “EA G/L Account”

Click on “Save” button

Chart of Account

Click on “New Entries” button

Enter “InfoProvider” as “2CIAPFLXBLAGING”

Enter “Query” as “2CCAPFLXBLAGING”

Enter “InfoObject” as “2CMBIWEI883S4US8477V0EERIY7”

Enter “Logical Attribute” as “LA_EA_CHART_ACCOUNT”

Enter “Description” as “EA Chart of Account”

Click on “Save” button

Configure Value Range

Value Ranges are a set of pre-populated values which can be used to derive the context under which an action should be executed.

Follow the given path:

Sensitive G/L Account List

Click on “New Entries” button

Enter “List of Values” as “VR_GL_ACCOUNT”

Enter “Description” as “List of G/L Accounts”

Click on “Save” button

Enter following entries in “VR_GL_ACCOUNT” Value Range

Follow below mentioned steps:

Execute Transaction Code “/UISM/V_RANGE”

Click on “VR_GL_ACCOUNT” Value Range

Click on “Display<- -> Change” button

Click on “Add New Entry” button

Add following entries under “Include Value” tab and click on “Save” button

Policy Configuration

Follow the given path:

Click on “New Entries” button

Enter “Policy Name” as “POL_MASK_COA”

Select “Type” as “Field Level Masking”

Enter “Description” as “Mask Chart of Account based on G/L Account in EA Query”

Click on “Save” button

Write following logic into Policy

Maintain Field Level Security and Masking Configuration

Click on “New Entries” button

Enter “Sensitive Entity” as “LA_EA_CHART_ACCOUNT” and press “Enter” key. “Description” will get populated in corresponding fields

Check “Enable Configuration” checkbox

Select “Attribute Based Authorization” option

Enter “Policy Name” as “POL_MASK_COA”

Click on “Save” button

Masking in WD Grid Query Display Mode

Follow below mentioned steps:

Execute “RSRT” TCode

Enter “Query” as “2CIAPFLXBLAGING/2CCAPFLXBLAGING”

Select “Query Display” mode as “WD Grid”

Click on “Execute” button

Enter highlighted search criteria in the corresponding fields and click on “Go” button.

Chart of Account Code and Description field value will appear as masked where “G/L Account” is “0011230000”, “0013111000”, "0022010001", "0022020001", and “0024643000”.

Conclusion

In this blog post, we have learnt how Attribute-based masking is achieved in Analytical Queries in Query Monitor (RSRT TCode) in WD Grid Query Display mode for masking sensitive field information.

Attribute Based Access Control (ABAC) – Field Masking scenario in Analytical Queries using Query Monitor (RSRT TCode) in ABAP BICS Query Display mode

2023-12-18T06:47:20+01:00

Introduction

In this blog, we will learn how to mask IBAN field information based on Company Code field information of SAF-T PL Bank Statement Item Analytical Query. Analytical Queries are used for reporting and analysis.

IBAN field information of SAF-T PL Bank Statement Item Analytical Query need to be masked where “Company Code” is “0001”, "PEG1", and "PCZ1". For other “Company Code”, “IBAN” field will appear as unmasked.

Attribute based authorizations are dynamic determination mechanism which determines whether a user is authorized to access specific data sets which can be based on the context attributes of the user and data (for example, price of certain sensitive materials are masked).

S/4HANA Embedded Analytics

Query Monitor (RSRT TCode)

Prerequisite

Requirement

Here, we want to configure masking for IBAN field information based on Company Code field information in SAF-T PL Bank Statement Item Analytical Query result using Attribute-based authorization concept.

Product “UI data protection masking for SAP S/4HANA 2011” is used in this scenario to protect sensitive data at field level and must be installed in the S/4HANA system.

Let’s begin

Configuration to achieve Masking

Configure Context Attribute

Company Code

Click on “New Entries” button

Enter “Logical Attribute” as “LA_EA_COMP_CODE”

Enter “Description” as “EA Company Code”

Click on “Save” button

Configure Sensitive Attribute

IBAN

Click on “New Entries” button

Enter “Logical Attribute” as “LA_EA_IBAN”

Enter “Description” as “EA IBAN Information”

Select “Is Sensitive” checkbox

Click on “Save” button

Maintain Analytics Technical Address

Company Code

Click on “New Entries” button

Enter “InfoProvider” as “2CCSAFTBNKSTITMC”

Enter “Query” as “2CCSAFTBNKSTITMQ”

Enter “InfoObject” as “2CF9SZ7VRFLVGPX8LFP23YH2722”

Enter “Logical Attribute” as “LA_EA_COMP_CODE”

Enter “Description” as “EA Company Code”

Click on “Save” button

IBAN

Click on “New Entries” button

Enter “InfoProvider” as “2CCSAFTBNKSTITMC”

Enter “Query” as “2CCSAFTBNKSTITMQ”

Enter “InfoObject” as “2CCSAFTBNKSTITMC-IBAN”

Enter “Logical Attribute” as “LA_EA_IBAN”

Enter “Description” as “EA IBAN Information”

Click on “Save” button

Configure Value Range

Value Ranges are a set of pre-populated values which can be used to derive the context under which an action should be executed.

Follow the given path:

Sensitive Company List

Click on “New Entries” button

Enter “List of Values” as “VR_PROTECTED_COMPANY_CODE”

Enter “Description” as “Protected Company Codes”

Click on “Save” button

Enter following entries in “VR_PROTECTED_COMPANY_CODE” Value Range

Follow below mentioned steps:

Execute Transaction Code “/UISM/V_RANGE”

Click on “VR_PROTECTED_COMPANY_CODE” Value Range

Click on “Display<- -> Change” button

Click on “Add New Entry” button

Add following entries under “Include Value” tab and click on “Save” button

Policy Configuration

Follow the given path:

Click on “New Entries” button

Enter “Policy Name” as “POL_MASK_IBAN”

Select “Type” as “Field Level Masking”

Enter “Description” as "Mask IBAN based on Company Code in EA Query”

Click on “Save” button

Write following logic into Policy

Maintain Field Level Security and Masking Configuration

Click on “New Entries” button

Enter “Sensitive Entity” as “LA_EA_IBAN” and press “Enter” key. “Description” will get populated in corresponding fields

Check “Enable Configuration” checkbox

Select “Attribute Based Authorization” option

Enter “Policy Name” as “POL_MASK_IBAN”

Click on “Save” button

Masking in ABAP BICS Query Display Mode

Follow below mentioned steps:

Execute “RSRT” TCode

Enter “Query” as “2CCSAFTBNKSTITMC/2CCSAFTBNKSTITMQ”

Select “Query Display” mode as “ABAP BICS”

Click on “Execute” button

Enter highlighted search criteria in the corresponding fields and click on “OK” button

IBAN field value will appear as masked where Company Code is "0001", "PEG1", and "PCZ1".

Conclusion

In this blog post, we have learnt how Attribute-based masking is achieved in Analytical Queries in Query Monitor (RSRT TCode) in ABAP BICS Query Display mode for masking sensitive field information.

CDS Hierarchy Directory: How to use NOTASSIGNEDNODE Annotation to suppress or to filter the Not Assigned(REST_H) nodes

2023-12-19T23:56:31+01:00

This blog is about how to handle Not Assigned(REST_H) nodes in CDS Hierarchy Directory of Analytical query, to get the result set either without Not Assigned node or filtered Not Assigned node. Let’s start with some basic information about CDS Hierarchy Directory.

Introduction to CDS Hierarchy Directory

There are two types of Hierarchy views. First where we use annotation ‘@Hierarchy’ and new one where we use ‘define hierarchy <NAME>’ (from 2023 on Prem and 2308 Cloud). In both the ways we can define association to a view which is then used as Hierarchy Directory.

Hierarchy Directory is CDS view.

It contains the List of all hierarchies available in the hierarchy view.

It can have Text for the hierarchies (language independent case) Or it can have an association to a text view (language dependent case)

It can contain a field which determine whether the Not Assigned node will be displayed or not.

It can contain a field which describes a filter which should be applied to the Not Assigned node.

It can contain a field which describes when a hierarchy was changed last time and which has annotation as ‘@Semantics.systemDate.lastChangedAt : true (for date)’ or ‘@Semantics.systemDateTime.lastChangedAt: true (for timestamp)’

When this field exist, then analytical engine will buffer the hierarchy and will renew the buffer when hierarchy is changed. Without this field hierarchy will always be rebuild and it can be performance overhead.

Use of NOTASSIGNEDNODE Annotations in CDS Hierarchy Directory

@HIERARCHY.NOTASSIGNEDNODE.SUPPRESSINDICATOR can be used to suppress the display of Not Assigned nodes.

It can be used for one field in a Hierarchy Directory view. The data type of the field must be Boolean (CHAR field with length 1 and with values '' or 'X'). If the flag is set for an entry in the directory, then the analytical engine doesn't create a 'Not Assigned' node. In this case the hierarchy itself acts as a filter and data which is not a leaf in the hierarchy is not part of the resultset.

@HIERARCHY.NOTASSIGNEDNODE.FILTER can be used to restrict the display of Not Assigned nodes.

It can be used for a field in the Hierarchy Directory view. The field needs in addition, a foreign-key association to a dimension view. This dimension view has also to be target of a foreign-key association defined in the dimension view which holds the hierarchy. The field with that foreign-key association must be a non representative key field. When the analytical engine resolves the 'Not Assigned' node, it derives a filter from the hierarchy’s name and applies this filter to the dimension values which have to be added to the 'Not Assigned' node. The other dimension values, which don't fulfil the filter criteria are ignored. In this case the hierarchy itself acts as a filter. The annotation can be used for key and for non-key fields in the Hierarchy Directory. Only constraint is that the field needs a foreign-key association.
With this feature you can improve the performance. It is only useful for hierarchies on dimensions with more than one key field and if one hierarchy should only contain leaves belonging to one value of a key field. A typical example is a cost center hierarchy. All cost centers of one hierarchy should belong to the same controlling area. Without this feature the analytical engine would also add cost centers of other controlling areas to the 'Not-Assigned' node. Notice that this happens independent of the filters used in a query. Therefore, in a query result there is no difference if the query contains a filter on the same controlling area. But the performance will be much better if the filter is also defined in the Hierarchy Directory.

Examples

Example 1: Without @HIERARCHY.NOTASSIGNEDNODE

@EndUserText.label: 'Connection Hierarchy Directory View'

@analytics : { dataCategory: #DIMENSION, dataExtraction.enabled: true }

@ObjectModel.representativeKey: 'hieid'

define view entity ZOQ_CONNECTION_HIERARCHY_DIR as select from ZOQ_CONNID_HD

{

@ObjectModel.text.element: 'hiertxt'

key hieid,

@Semantics.text: true

hiertxt,

@Semantics.systemDate.lastChangedAt: true

last_changed

}

Resultset will display Not assigned (REST_H) nodes

Example 2: With @HIERARCHY.NOTASSIGNEDNODE.SUPPRESSINDICATOR

@EndUserText.label: 'Connection Hierarchy Directory View'

@analytics : { dataCategory: #DIMENSION, dataExtraction.enabled: true }

@ObjectModel.representativeKey: 'hieid'

define view entity ZLR_CONNECTION_HIERARCHY_DIR as select from zoq_connid_hd

{

@ObjectModel.text.element: 'hiertxt'

key hieid,

@Semantics.text: true

hiertxt,

@Semantics.systemDate.lastChangedAt: true

last_changed,

@Hierarchy.notAssignedNode.suppressIndicator: true

'X' as suppressNotAssigned

}

Resultset will not display Not Assigned (REST_H) nodes

Example 3: With @HIERARCHY.NOTASSIGNEDNODE.FILTER

@EndUserText.label: 'Connection Hierarchy Directory View'

@analytics : { dataCategory: #DIMENSION, dataExtraction.enabled: true }

@ObjectModel.representativeKey: 'hieid'

define view entity ZLR_CONNECTION_HIERARCHY_DIR as select from zoq_connid_hd

association to ZOQ_AIRLINE as _carrid on _carrid.carrid = $projection.carrid

{

@ObjectModel.text.element: 'hiertxt'

key hieid,

@Semantics.text: true

hiertxt,

@Semantics.systemDate.lastChangedAt: true

last_changed,

@ObjectModel.foreignKey.association: '_carrid'

@Hierarchy.notAssignedNode.filter: true

cast( 'LH' as s_carr_id ) as carrid,

_carrid

}

Resultset will display Not Assigned(REST_H) node but only with LH as we have provided filter on carrid LH

Following are some of correction which are done for this feature:

3348310 - Problem with Hierarchy.notAssignedNode.filter
3377570 - Dump: GETWA_NOT_ASSIGNED in class CL_RSR_RRK0_HIERARCHY

SAP Premium Engagement: Analytics Design Workshop

2023-12-21T10:33:22+01:00

Who we are

We are SAP’s Center of Expertise (COE) for Analytics, Planning, and Consolidation in the globally operating Adoption Service Center. Our goal is to drive adoption and consumption of SAP Business Technology Platform technologies and lay the foundation for the Intelligent Enterprise. We are a trusted partner for customers with MaxAttention or Premium Engagement (PE). Also, we engage in the area of Professional Services, Preferred Success and other partnerships.

Introduction

In the rapidly evolving sphere of data analytics, cultivating a robust architecture for analytics and data management is imperative for maintaining a competitive edge. Introducing the Analytics Design Workshop (ADW) – a specialized service component dedicated to honing the implementation facets of analytics architecture and crafting a detailed transition project plan.

Expanding the Service Component

Within the Analytics Design Workshop , SAP offers options for empowering SAP analytics components and introduces crucial concepts like LSA++, along with empowerment and prototyping options. This includes modeling concepts for the SAP Analytics Cloud, SAP Business Intelligence, SAP Business Warehouse, SAP Datasphere, and SAP HANA business data platform.

Key focus areas for ADW include:

SAP S/4HANA embedded analytics integration with semantic layer, SAP BW, and SAP Analytics Cloud. --> ADW focus topic SAP S/4HANA embedded analytics

Implementation strategies for SAP Analytics Cloud covering stories, applications, planning, connectivity and SAP Business Intelligence --> ADW Focus topic SAP Analytics Cloud

Developing enterprise data warehouses using LSA++ in SAP HANA and SAP BW/4HANA, integrating with technologies like Hadoop, SAP IQ, and SAP Datasphere.

Detailed planning for transitioning infrastructure to the desired solution

The Customer’s Agenda

The customer's agenda for the Analytics Design Workshop (ADW) service in SAP typically revolves around refining analytics architecture and creating a structured transition plan. While specific agendas may vary based on the customer’s business needs, typical objectives or focus areas within ADW might include:

Refinement of Implementation Aspects: ADW aims to fine-tune how analytics architecture is practically implemented, ensuring efficiency and alignment with business objectives.

Creation of Transition Project Plans: Customers engaging in ADW often seek guidance in crafting detailed transition plans to smoothly shift from existing systems to new or optimized solutions.

Exploration of Specific Topics: This may involve diving into various aspects such as embedded analytics in SAP S/4HANA, modeling enterprise data warehouses using specific concepts like LSA++, integration strategies for SAP Analytics Cloud, and more tailored to their requirements.

Empowerment and Prototyping: Understanding empowerment options and prototyping techniques for SAP analytics components to enhance their utilization and efficiency within the organization.

Focus on Integration: Emphasizing seamless integration between various SAP solutions like SAP S/4HANA, SAP Analytics Cloud, SAP BW/4HANA, and other relevant platforms or technologies.

Roadmap : ADW delivers strategic roadmaps for SAC, S/4HANA, BW, DWC, BI, and more, aiding customers in planning their future technological advancements and aligning their business strategies with SAP's analytics solutions.

Delivery Approach & Scope

Delivery approach: on-site or remote, depending on scope, but typically it lasts 3 or 4 days. Optional focus topics: SAP S/4HANA embedded analytics, SAP Analytics Cloud

Scope:
- Knowledge transfer and interactive work sessions including hands-on on core topics such as layered scalable architecture
- Outline of a transition path to the new analytics architecture considering the customer-specific situation
- Definition of data temperature management concept
- Draft creation of development guidelines for SAP S/4HANA embedded analytics
- Definition of integration concepts for SAP and third-party SAP sources
- Prototype creation for specific scenarios, such as SAP Analytics Cloud on the CDS model with SAP S/4HANA, (remote delivery)

Value and Benefits

Engaging in the Analytics Design Workshop (ADW) service offers substantial value and benefits to organizations. The outcomes include:

Comprehensive Insight: Gain in-depth technical comprehension of new SAP Analytics solutions, particularly related to SAP S/4HANA, alongside a substantiated analytics architecture.

Results-Oriented Roadmap: Receive a detailed results report containing a roadmap or project plan facilitating a smooth transition from the current architecture to the new target structure.

Service Assignment Options

These service is available across various SAP support frameworks, including Value Assurance, SAP MaxAttention, SAP Active Embedded, and SAP Active Attention. To explore these offerings and harness the full potential of cutting-edge analytics solutions like SAC, connect with your Technical Quality Manager (TQM), SAP Account Manager, Customer Success Partner (CSP), or use our central entry channel, the Virtual Project Room (VPR). Elevate your business intelligence with unparalleled data insights for transformative growth.

Conclusion

The Analytics Design Workshop is a transformative journey, guiding businesses to evolve into Intelligent Enterprises. ADW ensures robust analytics architecture and smooth transitions, empowering organizations in the data-driven landscape. With SAP's support, it's about evolving intelligently, staying agile, and thriving in a dynamic data-driven world.

Inventory Aging Trend with S/4HANA Embedded Analytics

2024-01-05T19:47:33+01:00

Inventory aging trend with S/4HANA embedded analytics? Hmm...Sounds like data warehousing snapshot requirement. Actually S/4HANA inventory data model supports key date concept (with some limitation) making it possible trend analysis.

Example below demonstrates one of possible use cases - month to month comparison showing changes across different aging ranges

This blog describes Inventory Aging Trend model which is an evolution of Inventory Aging data model from my previous blog Inventory Aging Reporting with S/4HANA Embedded Analytics. I added monthly version dimension taking the model to a new level. Calculation of inventory quantity for any particular date was not a problem, but valuation (inventory value) was an issue and limited to current valuation. Now I made use of MBEWH Material Valuation: History table which is somewhat limited as well (contains only monthly snapshots of inventory quantity and values), but it is good enough for analysis on monthly level. I will only explain delta changes. Please refer to previous blog for complete details.

I added MBEWH Material Valuation: History table data to my model

Combined historical inventory valuation data with current valuation data. Created validity data ranges along the way making it easy to select valuation data which corresponds to selected date (key date).

I also exposed current date (key date) parameter as dimension for subsequent use as cube monthly version dimension

In my cube now I have two key date (P_Date_00 and P_Date_01) parameters one for each of two monthly versions we will compare. I pass these parameters to two table function views that I union.

Both key dates are set by BW query using OLAP variables (INVAGINGDATE00 and INVAGINGDATE01). INVAGINGDATE00 is open for entry add has current date default value set by OLAP BADI. INVAGINGDATE01 is not ready for input and is offset to prior month by OLAP BADI.

OLAP variable BADI also enforces data integrity making sure that input date variable is only limited to current date or end of the month in the past for which data model can provide correct valuation information.

See source below code for more information:

ZCL_INVENTORY_AGING

ZI_InventoryAgingFunc

ZCL_RSROA_VARIABLES_EXIT

ZI_InventoryAgingTrendCube

For more S/4HANA Embedded Analytics scenarios, please check out my book SAP S/4HANA Analytical Applications with Fiori Elements

Business Process Performance Optimization - a Premium Engagement offering

2024-01-09T10:33:40+01:00

In today's rapidly evolving corporate landscape, ensuring peak performance and efficiency within your business processes is cardinal. SAP's Business Process Performance Optimization service stands in the way of long waiting times and nerve-racking circling of the cursor.

At SAP’s Center of Expertise (COE) for Analytics, Planning, and Consolidation in the globally operating Adoption Service Center, our goal is to drive adoption and consumption of SAP Business Technology Platform technologies and lay the foundation for the Intelligent Enterprise. We are a trusted partner for customers with MaxAttention or Premium Engagement (PE). We also engage in Professional Services, Preferred Success, and other partnerships.
In this blog, I would like to give an insight what a BPPO looks like.

Overview of Business Process Performance Optimization service

The foundation of Business Process Performance Optimization service lies in its ability to analyze in detail and enhance critical business processes, offering a comprehensive suite of features aimed at uplifting operational performance.

A key feature includes a Comprehensive Analysis that delves deep into your business processes, providing valuable insights that lead to enhanced efficiency.

This service also encompasses the Evaluation and Enhancement of potential improvement areas. Through a detailed review, it suggests technical optimizations for more efficient operations, targeting areas ripe for improvement.

Service advantages

Streamlined Operations: Experience optimized response times and heightened throughput across your business operations.

Productivity Amplification: Witness a marked increase in overall productivity through more efficient processes.

Resource Utilization: Maximize hardware resources, ensuring their optimal use in driving your business's core functions.

Elevated User Satisfaction: With enhanced processes, your end-users are more likely to experience satisfaction in their workflow.

As organizations encounter specific issues, the BPPO service team delivers targeted solutions:

Response Time Concerns: Addressing extended delays in specific process steps, whether standard or customer-specific to SAP.

Deadline Challenges: Assistance in meeting deadlines and time frames for designated processes.

Resource Consumption Challenges: Mitigating resource spikes during certain processes or at specific times.

Performance Problems: Addressing performance issues that may arise during the operation of typically well-performing transactions.

The outcomes of this service are prompt and actionable. In one week following the session, you receive a comprehensive report that encapsulates a prioritized action plan based on the analysis. Topics are summarized, issues are highlighted, and actionable recommendations are provided. This actionable plan serves as a roadmap to drive performance enhancements within your operations.

Delivery details on SAP Analytics Cloud

SAP Analytics Cloud is rapidly growing. New features, approaches, optimizations are coming each quarter, challenging BI developers to keep up on all aspects. The power of a BPPO service is to get insight on fresh good practices while also applying the new knowledge on scoped dashboards. As mentioned in the previous section, our final report details our recommendations which is a starting point on optimizing end user satisfaction on performance. These steps also help to build a new mindset on implementing future dashboards as best practices are also shared during the service. And what kind of points we check? Excellent question!

Based on the requirements and current scenario, we first silo where performance issue is coming from – is it a front-end problem, or the query is running long? In either cases we go one level deeper and deeper until we identify the malicious part. Then, after researching and testing different options we suggest a solution or in rare cases, a workaround with detailed steps how to execute them.

Let me share 2 memorable cases:

SAC dashboard on mobile was running for 15-20 seconds. After analyzing the end user journey, we have identified the current design is not sufficient and replaced many small parts with a single chart – which provided even more than the required information. With this fix, we have managed to increase performance by almost 70%!

A complex dashboard with 26 charts were loading for 15 seconds. Taking the complexity, first it seemed reasonable, however it soon turned out the chart refreshing practices were neglected and the scripting was suboptimal too. After adjustments and refactoring, the loading time was at 6 seconds!

While not every BPPO service boasts such numbers, our commitment is unwavering – to make every service the best run. The final report doesn't just conclude; it paves the way for future endeavors, hinting at the promise of diverse follow-up services.

Performance has many blocks – all need to be checked to understand malfunctions

Our toolset helps us identify long running functions and queries to drilldown on suboptimal parts whether it’s on back-end side or front-end.

SAP Note 2511489 - Troubleshooting performance issues in SAP Analytics Cloud (Collective KBA) has a great recap on most important aspects for performance: “The overall performance of SAP Analytics Cloud (SAC) is mainly determined by the three components - client time (frontend), network time and the SAP Analytics Cloud service time (backend).”

Performance checks and tuning are of course not restricted to BI only. We provide the same checks and deliverables for SAC Planning, where the focus is usually on specific design like calculations, data actions and version handling. In fact, the BPPO is a mature, proven methodology which we apply to all SAP related business processes since decades. The key is to bring in all necessary functional and technical roles from our global expert pool.

Summary

Business Process Performance Optimization service seamlessly integrates into the operational phase of your solution. Moreover, it provides substantial value during the testing phase of any implementation project, proving its adaptability and necessity across different operational scenarios.

Are you ready for faster dashboards? Don’t hesitate to reach out to your Technical Quality Manager (TQM), your SAP Account, your Customer Success Partner (CSP), or our central entry channel, the Virtual Project Room (VPR).

SAP S/4HANA Cloud Public Edition 2402 亮点前瞻：分析报表

2024-02-05T13:46:47.399000+01:00

在本篇博客中，我将会重点展示在 SAP S/4HANA Cloud 2402 当中分析报表版块发布的功能，将会覆盖以下话题内容：

视图浏览器
术语更改：Web Dynpro 应用 -> 多维数据网格应用
新增：“管理 KPI 和报表”应用中的审核小册子设计器
升级后弃用的CDS

视图浏览器

在CE2402中，视图浏览器APP将新增一个变量信息“数据提取已启用”。当该字段标识为“√”，即表示该CDS视图可用于数据提取的场景。

客户可以通过APP中的设置，将数据提取变量字段进行显示。

术语更改：Web Dynpro 应用 -> 多维数据网格应用

为统一文档中的表述，自 CE2402 起，文档中的术语“Web Dynpro 应用”将会替换为“多维数据网格应用”。

另外需要注意的是只有分析类的应用会进行术语更改。其他的基于Web-Dynpro的事务应用，例如APP显示科目余额（W0130），该应用的术语不会进行更改。

审核手册亮点更新

全页模式下便于使用

侧边栏隐藏功能
专注于报表内容便于使用

通过MS Teams轻松共享见解

支持分享审核手册链接，携带预先设置好的变量信息等，无需重新设置
便于使用MS Teams聊天讨论报表相关内容

支持PDF导出功能

新增：“管理 KPI 和报表”应用中的审核手册设计器

拥有分析专家权限的客户现可以在APP管理KPI和报表中通过选项卡“审核手册”浏览访问审核手册，并支持客户创建自定义的审核手册。

审核手册设计器属于关键用户开发（Key User Extensibility）。客户可以复制并根据客户的分析需要进行调整，但只有状态为最终配置或应用程序已激活的审核手册才可以被复制。

此外，SAP 已预先提供了标准的审核手册，例如集团财务报表审核手册。

更多关于如何复制和配置审核手册可以参考文档。

升级后弃用的CDS

系统升级后有CDS会被弃用，例如I_Materialstock。建议客户查看弃用CDS清单，根据系统实际使用情况，尽快切换到后继CDS。

更多关于 SAP S/4HANA Cloud Public Edition分析报表话题:

SAP S/4HANA Cloud嵌入式分析业务用例汇总及简介查看
SAP S/4HANA Cloud公有云版本中三系统开发扩展性与二系统关键用户扩展性报表开发对比查看

SAP Activate – What’s New in User Experience guidance with SAP Fiori for SAP S/4HANA

2024-02-22T06:45:12.736000+01:00

Good news for those implementing SAP Fiori for SAP S/4HANA!

Over the last couple of months, the SAP S/4HANA RIG team have been hard at work bringing several updates to the User Experience content and accelerators for SAP S/4HANA roadmaps in SAP Activate.

These updates bring the latest information for SAP S/4HANA 2023 (and 2022) releases to your project planning.

The following roadmaps now include User Experience content and accelerators:

What’s Changed?

Much of the UX-related task content has been updated in SAP Activate Methodology for RISE with SAP S/4HANA Cloud Private Edition.
Several accelerators have been updated and shared across multiple related roadmaps. Here’s a quick summary of what’s changed.

Below you will find a quick summary of what to use when you are:

Getting started with SAP Fiori for SAP S/4HANA
Want to see an examples of how experts introduce UX
Planning to demonstrate SAP Fiori
Planning your SAP S/4HANA upgrade
Moving to Spaces and Pages layout
Looking to grow your usage of SAP Fiori
Looking to add SAP Build Work Zone and SAP Mobile Start
Want more User Experience advice in SAP Activate

P.s. Much of the content in SAP Activate related to system conversions has also been updated by the SAP S/4HANA RIG team. You can find more about the other updates in blog post News from SAP Activate SAP S/4HANA Cloud Public Edition 2402

Getting started with SAP Fiori for SAP S/4HANA ?

Not sure how to explain User Experience to your business?

You’ll find some useful slides and preparation ideas in UX Adoption: Establish the Business Value of UX Workshop (Public)

Want to see an examples of how experts introduce UX?

See how I do it in the openSAP course SAP S/4HANA UX for Business and Functional Experts. Missed it? No problem! Join the course self-paced.

Review the video:

Unit 1: How to explain the value of SAP Fiori

Planning to demonstrate SAP Fiori?

You will find it very helpful to review the SAP Fiori: Tips & Tricks for Users of SAP S/4HANA which is also listed in the SAP Activate accelerators.

You will need a User Experience Strategy to set your baseline expectations, architecture, features, and tools. Accelerator User Experience Strategy Template (Public) now contains much more assistance, along with some Guiding Principles to help you keep your team human-centred.

Want to discuss your UX Strategy with your business?

Accelerator UX Adoption: UX Strategy and Guiding Principles Workshop (Public ) now has a flipbook-style section showing how to make cross-functional feature in/out of scope decisions with your team.

Planning a SAP S/4HANA upgrade ?

Take a look at SAP Activate roadmap SAP Activate Methodology for SAP S/4HANA Upgrades

Even if you are going for a technical upgrade approach, you will still need to revisit your UX Strategy and launchpad feature usage. This ensures you cover any mandatory changes due to:

New, changed, or deprecated launchpad features
Obsolete, deprecated, or superseded apps
New, changed, or deprecated launchpad administration tooling

Accelerator UX Adoption: UX Strategy and Guiding Principles Workshop (Public ) shows how to make cross-functional feature in/out decisions with your team, and document the reasons for change. Accelerator User Experience Strategy Template (Public) has the latest best practices for launchpad features and administration tooling.

Missing some advice on upgrading your SAP Fiori for SAP S/4HANA? Please let us know what else you need in the comments.

Moving to Spaces and Pages layout?

You will find some suggestions on how to get started in UX Adoption: How to approach Design your Launchpad Layout Workshop (Public)

Doing a deeper dive with blog post Info Package: Making the Move from Launchpad Groups to Spaces (In SAP S/4HANA and in SAP S/4HANA Cloud, private edition)

Looking to grow your usage of SAP Fiori ?

Looking for ideas on which apps to use?

You will find updated guides for selecting apps by UX Value at UX Value Goal App Selection Guides (Public)

With more than 3K apps, even with suggestions from tools such as SAP Signavio Process Insights, and Readiness Check, you’ll need a way to narrow down the focus.

The UX Adoption Planning process shows how to have a now/next/later discussion to engage with your business stakeholders.

You can find an introduction to the major steps in openSAP course SAP S/4HANA UX for Business and Functional Experts. Missed it? No problem! Join the course self-paced.

Review the videos:

You will find the entire matching series of updated workshop templates in SAP Activate. You will even find some suggestions on which major decision points to focus on at each stage to keep it simple.

Use it all or just whatever helps you move forward. That’s the intention ... and how other customers tell us they are using the content.

Looking to add SAP Build Work Zone and SAP Mobile Start?

With SAP S/4HANA focus on SAP Build Work Zone, standard edition.

You will find the latest guidance and suggestions at SAP Community topic page for SAP Build Work Zone

As a first step, you should review the latest architecture guidance announcements in blog post SAP Fiori Deployment Options and System Landscape Recommendations

You will find some suggestions on where to incorporate SAP Build Work Zone in your UX Strategy in accelerator User Experience Strategy Template (Public). You can engage your business on your SAP Build Work Zone journey by using the Cross-Functional Feature Decisions approach shown in accelerator UX Adoption: UX Strategy and Guiding Principles Workshop (Public )

Then get the latest news on what’s possible by reviewing the latest roadmap blog posts from SAP such as:

SAP UX Innovations in Public Cloud Products, Joule, AI, Entry Points, Apple Vision Pro and more

Want more SAP Activate updates for User Experience?

Whew! There’s a lot of content in SAP Activate so if you see something that needs improving, please let us know in the comments!

Don't forget to use the User Experience tag (in the left-hand filter pane) of SAP Activate to find the rest of the recommended UX content and accelerators already available in SAP Activate.

Find out more about SAP Activate on the SAP Activate topic page.

Follow the SAP Activate page on the SAP Community. Remember to turn on your notification to receive updates or information about items requiring your attention.
Tune into the SAP Activate Minute videos in our SAP Activate Playlist. Subscribe to get notified when we drop new videos. We have big plans to add interesting new topics.

Find more from the SAP S/4HANA RIG team via tag S4HANA RIG

Find more on UX at our SAP Fiori for SAP S/4HANA topic page

New Asynchronous Export to Spreadsheet Feature for the Multidimensional Data Grid Apps

2024-02-27T11:20:25.612000+01:00

Dear SAP Community,

In 2021, the Web Dynpro Multidimensional Data Grid App replaced the SAP Design Studio app as default reporting tool for drill-down reporting in SAP S/4HANA.

Initially designed for human interaction, this web application offers an export feature that has been continuously improved and streamlined over time:

Export of PDF files
Streamlining of export to improve performance
Google workspace integration with the possibility to export spreadsheets to Google directly
etc.

However, there always was the possibility that the amount of data cells simply was too large, and the system would run out of memory, or into a timeout. SAP Note 2547776 introduced a popup message that warned a user of these risks in case more than 100.000 cells would be exported.

Now the next step in terms of performance optimization has been taken by offering to export large amounts of data in a background task. Furthermore, the user can trigger the export in the background (see Figure 1), and continue working in the application without having to wait until the export has finished, with or without the application still alive and running.

Figure 1: “Export to Spreadsheet” popup with a new function to trigger the export in the background.

Once the background task has finished, if the application that has triggered it is still running, the user is informed of the success (or failure) of the export. The exported file is then available for download for the next 72 hours. Expired files will be deleted automatically from the database table.

The files can be accessed either in a new tab “Downloads” (e.g. in the generic FPM_BICS_OVP apps), or in a dialog window that can be accessed via the download button choice for applications that do not offer the new tab directly (see Figure 2). In both cases, the same component is used, and the layout is the same.

Figure 2: List of downloads to monitor the status and access the result of the asynchronous exports.

In the list of downloads in this example, the first file “export.xlsx” already has been exported successfully, while the second file “demo_export” is currently being exported. Download is possible only for successfully exported files, while deletion is possible also for entries where the export has failed or is currently in progress. However, deleting an unfinished export does not abort the background process.

During a single user session, only one background export can be executed at any given time. If you start an export in background while there is still another process running, the new process will not be started, and an error message will be displayed.

It should be noted that this does not mean that unlimited amounts of data can be exported from the grid now. There are still scenarios where the amount of data required to export a file is outside the boundaries of memory allocation for a work process. This depends not only on the number of cells in the grid, but also on their (conditional) formatting and merging, variables, and filters, down to the definition of the query and the used database tables. Even the database technology may have an influence on how much data can be processed at once.

The feature is available with SAP Note 3427386 for SAP_BW 757 and 758, and SAP Note 3434831 for BW/4HANA 400, and it is planned to be contained in the 2408 updates of SAP S/4HANA Cloud Public Edition and SAP BW/4HANA Cloud Public Edition.
[A previous version of this blog stated that it will be contained in the 2408 update. Since this is current state of planning and may be changed by SAP at any time without notice, the wording has been adopted.]

With this new feature, you can more easily export data from a Multidimensional Data Grid Apps without blocking the application and reduce the risk of running into error situations.

CDS View: Time comparison

2024-02-28T22:27:29.400000+01:00

This blog is about CDS scalar functions - CALENDER_SHIFT and CALENDER_OPERATIONS and how to use it in analytical queries for time comparison. Similarly FISCAL_CALENDAR_SHIFT and FISCAL_CALENDAR_OPERATION can be used.

These CDS scalar functions are used to compare the measure value of current time period with previous time period. Further it can be used to calculate measure value for year to date (YTD), month to date (MTD) or quarter to date (QTD). Current member can only be used when time dimensions are in drilldown else restricted measure is used. The usage of current member is not as fast as restricted measure. Detail specification of the mentioned scalar functions can be found in Help.

Usage of Current Member

This function can be used by modeling an association with the cube. In the ON-condition, the scalar functions are specified on the right side.

association to ZOQ_FLIGHT as _previousMonth
    on _previousMonth.fyearMonth = calendar_shift( base        => $projection.fyearMonth, 
                                                   base_level  => calendar_date_level.#MONTH,	
                                                   shift       => abap.int2'-1',
                                                   shift_level => calendar_date_level.#MONTH  )

Constraints:

Current member to work properly, we have to mark all the time fields which are related with annotation - @ObjectModel.value.derivedFrom. We should also specify semantics. for example,

key fldate,
@ObjectModel.value.derivedFrom: 'fldate'
@Semantics.calendar.yearMonth: true
@ EndUserText.label: 'FL Month'
_calday.calmonth as fyearMonth,

The base parameter must be filled with the same field name as it appears on the left: for example, the field name __previousMonth.fyearMonth should be same as base => $projection.fyearMonth

The Semantics of field $projection.fyearMonth must match the base_level parameter. As In the cube view example, the fyearMonth field has the annotation @Semantics.calendar.yearMonth: true, base_level is specified as calendar_date_level.#MONTH.
In the example to restrict the measure to the previous month, shift is set to -1 and shift_level is set to #MONTH. There is a constraint in using shift_level with base_level : for example for base level #MONTH, shift _level can be #MONTH,#QUARTER or #YEAR But can’t be #DAY.

Example 1: Time comparison with time in drill-down (Current Member Variables)

@AccessControl.authorizationCheck: #NOT_ALLOWED
@EndUserText.label: 'Query: Current Memeber on Month'
define transient view entity ZLR_PC_CM_1 
provider contract analytical_query
as projection on ZOQ_FLIGHT

  association to ZOQ_FLIGHT as _previousMonth
    on _previousMonth.fyearMonth = calendar_shift( base        => $projection.fyearMonth, 
                                                   base_level  => calendar_date_level.#month,
                                                   shift       => abap.int2'-1',
                                                   shift_level => calendar_date_level.#month  )
  association to ZOQ_FLIGHT as _firstMonthOfQuarter
    on _firstMonthOfQuarter.fyearMonth between calendar_operation( base           => $projection.fyearMonth,
                                                                  base_level      => calendar_date_level.#month,
                                                                  operation       => calendar_date_operation.#first,
                                                                  operation_level => calendar_date_level.#quarter )  
                                          and $projection.fyearMonth  
      
  association to ZOQ_FLIGHT as _CMM1_CMP1
    on _CMM1_CMP1.fyearMonth between calendar_shift( base        => $projection.fyearMonth, 
                                                     base_level  => calendar_date_level.#month,
                                                     shift       => abap.int2'-1',
                                                     shift_level => calendar_date_level.#month  )     
                                 and calendar_shift( base        => $projection.fyearMonth, 
                                                     base_level  => calendar_date_level.#month,
                                                     shift       => abap.int2'1',
                                                     shift_level => calendar_date_level.#month  )  
 {
  @AnalyticsDetails.query: {
    axis: #ROWS,
    totals: #SHOW
  } 
  @EndUserText.label: 'Year Quarter'
  flquarter,
  
   @AnalyticsDetails.query: {
     axis: #ROWS,
     totals: #SHOW
  }  
   @EndUserText.label: 'Year Month'
   fyearMonth,
  
   @AnalyticsDetails.query.axis: #FREE
   .hidden: true
   currency,
   
   @Semantics.amount.currencyCode: 'currency'
   paymentsum,
   
   _previousMonth.currency as PrevMonthCurrency,
   @Semantics.amount.currencyCode : 'PrevMonthCurrency'
   @EndUserText.label: 'Previous Month'
   _previousMonth.paymentsum as PrevMonthPayment,

   _firstMonthOfQuarter.currency as firstMonthOfQuartCurrency,
   @Semantics.amount.currencyCode : 'firstMonthOfQuartCurrency'
   @EndUserText.label: 'Quarter to today'
   _firstMonthOfQuarter.paymentsum as firstMonthOfQuartPayment, 

   _CMM1_CMP1.currency as last3MonthCurrency,
   @Semantics.amount.currencyCode : 'last3MonthCurrency'
   @EndUserText.label: 'Previous month To next month'
   _CMM1_CMP1.paymentsum as CMM1_CMP1Payment

}
where flyear =  '2019'
  and currency = 'EUR'

Result:

In this Result

Red- column Previous Month -shows value from previous month.
Yellow- column Quarter to Today- shows the aggregate values of previous months in this quarter.
Green- column Gliding window of 3 month- shows aggregate value of previous month + current month + next month.

Usage of Restricted Measure

This can be done using the CASE statement, where one of the scalar function is used.

   case when fyearMonth = calendar_shift( base        => $parameters.p_month, 
                                          base_level  => calendar_date_level.#MONTH,
                                          shift       => abap.int2'-1',
                                          shift_level => calendar_date_level.#MONTH ) then paymentsum end as paymentPrev

Constraints:

The base parameter must be a parameter or a literal.
The type of parameter or literal must match to base_level. In the example for base_level calendar_date_level.#MONTH, the type of parameter p_month must be NUMC6.
In the example to restrict the measure to the previous month, shift is set to -1 and shift_level is set to #MONTH.

Example 2: Time comparison (Restricted key figure)

@AccessControl.authorizationCheck: #NOT_ALLOWED
@EndUserText.label: 'Query: Current Memeber on Month'
define transient view entity ZLR_PC_RSRT_SHIFT1 
provider contract analytical_query
with parameters
       p_month : /bi0/oicalmonth
as projection on ZOQ_FLIGHT
 {
   @AnalyticsDetails.query: {
    axis: #ROWS,
    totals: #SHOW
  } 
   carrid,
   
   currency,
   
   virtual currCur : abap.cuky,
   @Semantics.amount.currencyCode : 'currCur'
   @Consumption.dynamicLabel: {
     label: 'Bookings &1',
     binding: [{ index : 1 , element : 'fyearMonth' }]
   } 
      
   case when fyearMonth = $parameters.p_month then paymentsum end as paymentCur,
   
   virtual currPrev : abap.cuky,
   @Semantics.amount.currencyCode : 'currPrev'
   @Consumption.dynamicLabel: {
     label: 'Previous Bookings &1',
     binding: [{ index : 1 , element : 'fyearMonth' }]
   } 
     
   case when fyearMonth = calendar_shift( base        => $parameters.p_month, 
                                          base_level  => calendar_date_level.#month,
                                          shift       => abap.int2'-1',
                                          shift_level => calendar_date_level.#month  ) then paymentsum end as paymentPrev,  
   
  
   
   virtual currLastInYear : abap.cuky,                                     
   @Semantics.amount.currencyCode : 'currLastInYear'
   @Consumption.dynamicLabel: {
     label: 'Bookings from &1 To &2',
     binding: [{ index : 1 , element : 'fyearMonth', replaceWith: #LOW },
               { index : 2 , element : 'fyearMonth', replaceWith: #HIGH }]
   }  
   case when fyearMonth between calendar_operation( base            => $parameters.p_month, 
                                              base_level      => calendar_date_level.#month,
                                              operation       => calendar_date_operation.#first,
                                              operation_level => calendar_date_level.#year  ) and $parameters.p_month then paymentsum end as paymentToDate                                            
 
}
where currency = 'EUR'

Result:

In this example I have used @Consumption.dynamicLabel to dynamically set the column label with values calculated from parameter.

Release Info:

On-Prem SAP_BW from 7.58 and Cloud from 2308

Related Notes:

3270090-CurrentMember + FemsN

3359468-Current Member on reference characteristic and selection for Partial Time Characteristic

Create Popup in SAP Analytics Cloud

2024-03-25T13:29:21.820000+01:00

Hello All!

I wanted to share my Proof of concept about Creating an alert or popup in the SAP Analytics Cloud, This feature will be very useful for alerting purposes.

SAP Analytics Cloud is used to create reports and planning with many features, in that particularly the SAP Analytics cloud allows developers to develop a report in three types types

Optimized Design Experiences
Classic Design Experiences
Analytical Application

Each has its special features, in our case, we going to use Optimized Design Experiences (ODE), Since Classic Design Experiences doesn't support scripting features.

Step 1

Create a story in Optimized Design Experiences
Drag a chart and then select the data source, in my case, I choose a required model for the data source.

Step 2

Choose the required measure and dimensions that to be displayed in the corresponding chart.
In my case, I chose the Numeric chart and Revenue as measures.

Step 3

In the left side panel, you can find the Outline tab, click on it.

Step 4

Select Page 1, click on more options
Add Popup

Step 5

In Popup, I have added an image for the warning and a text box to display the alert message.
The popup is one of the best features, we can display one complete KPI chart or table in the popup itself.

Go to edit the script for Popup, initally it should be closed because whenever the revenue goes below 8000 then only it will be execute, so I coded accordingly.

Step 6

Select the Page_1 and go to Edit Scripts

Step 7

Select onInitialization
Here is my code, this code is used to get all the data in that particular chart and store it in a variable called Revenue, In my case, I want to display the popup when the Revenue goes below 8,000.
If the revenue value go below 8,000 then the Popup will display, If not then the Popup will remain closed.
Save the story and see it in view mode.

Output

Here The Revenue value is 7000, I coded it to show the alert popup whenever the revenue goes below 8000.

And So the Popup is displayed successfully.

Thank You.

Analytical Query CDS View creation and consumption in RSRT along with publishing OData Services

2024-03-26T20:25:51.107000+01:00

Introduction

In this blog you will learn about the creation of Query CDS Views for Analytical purpose and their consumption in RSRT tool, along with the required steps that needs to be followed to achieve it. Once after the Analytical query creation, I have tried replicating one of my project scenarios to have better understanding on defining key figures/ measures in CDS views. In the end blog explains about the process needs to be followed to expose the given Query CDS view into OData service links. The Query CDS Views are created specifically for Analytical reporting purposes within SAP systems. They can be optimized for certain reporting scenarios, analytical queries, aggregations and further can be integrated with SAP FIORI tool providing much better visual reporting experience.

Creation of query CDS view:

For the creation of query CDS view we must follow 3 basic steps as mentioned below:Screenshot1: Pictorial representation of Analytical Query CDS View

Steps to follow for the creation of query CDS view:

1. CDS Info Provider as source

We cannot use any standard R\3 DB tables as a source for the creation of Query CDS View. We can only use standard/existing CDS Views from the system that needs to be converted into CDS Info Provider. CDS Info Provider is called by the special annotation @Analytics.DataCategory: #CUBE. Here #CUBE means Info Provider. The significance of declaring your CDS View as cube because when we compare it with our BW terms, we will be creating report on top of Composite Provider, ADSO or Info Cube. Similarly, we need to convert our source CDS view as Info Provider to create the analytical report.

Screenshot2: Source CDS view2. CDS Query view

Once after creation of CDS Info Provider view, create new CDS view by utilizing the source Info Provider CDS view as a data source which is ZCDS_CUBE from my context. Then start building our Query CDS View report as per the Business requirement and logic. Important annotations required for enabling the CDS as query view is @analytics.query: true and VDM.viewType: #CONSUMPTION. By declaring our CDS view as consumption CDS View, we will be able to derive all the required fields from our source CDS view without facing error.Screenshot3: Creation of Query CDS View

Few important Annotations and their significance for the creation of the structure of our Query CDS View:

@AnalyticsDetails.query. axis: #ROWS – Used for defining attributes to row characteristics in Query Browser.
@AnalyticsDetails.query. axis: #COLUMN- Used for defining key figures to column in Query Browser.
@AnalyticsDetails.query. axis: #FREE - Used for defining attributes to Free characteristics in Query Browser.
@AnalyticsDetails.query. sortDirection: #DESC or #ASC – For sorting the values of the defined rows in Ascending or Descending order.
@AnalyticsDetails.query. display: #KEY_TEXT- Used for displaying the text of the key.
@AnalyticsDetails.query. totals: #HIDE – used for displaying the totals.
@AnalyticsDetails.query. formula: - To perform the calculations based on the Business requirements. We cannot see the formula calculations in data preview and can be displayed only when the query is processed in reporting tool.
@EndUser.text. label: – Can be used for labelling the new field that will be derived from Formula.
@consumption. filter.mandatory : True :- This annotation will give us prompts same as parameter.
@Aggregation.default: with this annotation domain, you can declare the required field as a measure.

3.CDS Consumption in RSRT

Two major stages involved in consuming the CDS View as Query in RSRT transaction as explained below:

For each Query CDS view created, first COMPU ID will be generated in RSRREPDIR backend table along with the Info Provider CDS View name under Info Cube field and query name in COMPID field as highlighted below. Provide the SQL view name of your CDS view with prefix 2C in COMPID tab and you will end up in the below screen as shown:Screenshot4: RSREEPDIR Table view
One basic rule to consume the Query CDS view in RSRT Query monitor transaction. Use the prefix “2C+SQL view name” given in the CDS View. Screenshot 5&6: Query monitor and Result view
Now let me try to explain you by replicating one of the issues I was facing in my project and thereby we will try to understand more about the the importance of Annotations related to Analytical report. In my source Info Provider CDS View ZCK_QUERY(structure provided below), I was calculating one field name called “calc” as shown below which populated the correct value as expected in the data preview. Screenshot7: Source CDS view for "calc" field and data preview
But when I was trying to create report on top of this CDS View, the field “calc” had null values in the report, even after calling the required annotation as shown below.
Screenshot8: Query CDS View structure and output result view for field "calc"
After going through series of analysis and understanding on the basics of CDS View annotations, came to know that, as my field “calc” is measure/key figure in nature and values which got populated were not aggregated and thus causing error in my Query CDS View. In CDS View when such calculation happens on the key figure, it is necessary to declare the annotation @Aggregation.default: #SUM to derive the values from the source CDS View to Query CDS View. Screenshot9: Corrected source CDS view and output result
Exposing CDS Query as OData Service:
One of my project requirements was to expose the query CDS View to OData service through sap gateway, so I got the opportunity to explore more about this OData services usage in CDS View and thought of sharing the required procedures in this platform.
Basically, OData Service is a standard web protocol used for querying and updating data present in SAP using ABAP/CDS. So, it is like a bridge between Backend to Front end systems like UI5/FIORI or any other integration systems. In this section let me try to explain to expose the given CDS View into OData service by activating the service link through Transaction code: /n/iwfnd/maint_service.
Usage of OData Annotation:
Declare the Annotation @OData.Publish: true in your CDS View as shown below and activate the CDS view.Screenshot10: OData annotation declaration for Query CDS View
Once after the activation of CDS View, a popup will appear near the OData annotation comment declared, which will show as “Service is not active”.Screenshot11: OData exposure popup
For the activation of OData service, get into the GUI system and follow the below mentioned steps:
1. Use the transaction code: /n/iwfnd/maint_service.
2. Click on the Add service tab in the Activate and Maintenance page. Screenshot12: Add service tab
3. Fill the System Alias option with “1. LOCAL” and External Service Name option with the “2. CDS Entity name + _CDS” and click on the “3. Get Services”. In my case ZCDS_CONS is my CDS entity name, so my service name will be ZCDS_CONS_CDS which will appear under the tab “4. Technical Service Name”. Screenshot 13: Add selected service view
4. Click on the service name been generated under the technical service name tab and provide the package assignment name as $TMP to store it locally where this service link will be generated. After providing the package name and then click on ok as highlighted below: Screenshot14: Create package for the service
5. Next you will have the popup saying “Service XXX_CDS was created, and its metadata was loaded successfully”.
6. As a next step for the confirmation, come back to your ADT tool where you have called OData Annotation in your CDS View. Now the popup will show the OData service link for your CDS View as shown below: Screenshot15: Activated OData service link reflecting in Query CDS view
7. Click on the OData -Service link and your OData server will appear like below: Screenshot16: OData server image
8. To get OData service in SAP gateway client, use the option SAP gateway client option which is available in the maintenance service page. Here first search your activated OData CDS view with technical name and click on sap gateway client.Screenshot17: SAP Gateway client
9. Once you enter the gateway client, click execute to display the OData service in gateway client. Screenshot18: OData service in Gateway client
10. To display the meta data structure of your OData service, use the $metadata in the Request URI. Screenshot19: Metadata structure view
  The scope of these Query CDS views can be extended to display in SAP FIORI as well. For this you need to be aware of creating the UI5 App through UI annotations for Analytical Query CDS view.

CDS View: Hierarchy node sign reversal

2024-04-15T13:30:04.285000+02:00

This blog is about how to use @Semantics.signReversal in CDS Views to revert the sign of a measure in dependence of the settings of a hierarchy node. Analytic query offers the functionality to reverse a sign after aggregation based on a hierarchy node attribute.

This functionality shall be made accessible from a CDS Query, for this it is necessary to determine the hierarchy node attribute which stores the sign reverse indicator.

To make use of the sign reversal feature in an analytical query, the following field needs to be added to the related hierarchy view:

@Semantics.signReversalIndicator

signref as signReversalFlag,

Example: Hierarchy view

@AbapCatalog.sqlViewName: 'ZOQ_CONNIDHIER'
@EndUserText.label: 'Connection Hierarchy View'
@ObjectModel.dataCategory: #HIERARCHY
@Hierarchy.parentChild : {
  name : 'ConnectionHierarchy',
  label : 'Connection',
  siblingsOrder: [{ by: 'seqno' , direction: 'ASC' }] ,
  recurseBy : '_parent',
  directory: '_dir'
}

define view ZOQ_CONNECTION_HIERARCHY
  as select from zoq_connid_h

  association [0..1] to ZOQ_CONNECTION_HIERARCHY     as _parent     on  $projection.parentid = _parent.nodeid

  association [1]    to ZOQ_CONNECTION_HIERARCHY_DIR as _dir        on  $projection.hieid = _dir.hieid

  association [1]    to ZOQ_CONNECTION_NODENAME as _node       on       $projection.hieid   = _node.hieid
                                                                    and $projection.nodename = _node.nodeName
                                                                    and $projection.carrid   = ''
                                                                    and $projection.connid   = '0000'

  association [1]    to ZOQ_AIRLINE                  as _airline    on  $projection.carrid = _airline.carrid
                                                                    and $projection.connid = '0000'

  association [1]    to ZOQ_CONNECTION               as _connection on  $projection.carrid = _connection.carrid
                                                                    and $projection.connid = _connection.connid

{
      @Consumption.filter: { mandatory : true, selectionType : #SINGLE, multipleSelections : false }
      @ObjectModel.foreignKey.association: '_dir'
  key hieid,
  key nodeid,
      parentid,

      seqno,

      @ObjectModel.foreignKey.association: '_airline'
      carrid,
      @ObjectModel.foreignKey.association: '_connection'
      connid,
      @ObjectModel.foreignKey.association: '_node'
      nodename,
      
      @Semantics.signReversalIndicator
      signref as signReversalFlag,

      _parent,
      _dir,
      _node,
      _airline,
      _connection

}

Preview:

In CDS views with "Analytics.query : true" or define as "transient view entity", function "HRY_NODE_SIGN_VALUE(elemRef)" is used in a formula (AnalyticsDetails.query.formula). This function works in the following way, At first the path from the element to its hierarchy view is evaluated. In the hierarchy view there should exist exactly one field with semantics signReversal. For each hierarchy node for which the value of the sign reversal element returns space, the function HRY_NODE_SIGN_VALUE will return +1. If the value is not initial, the function returns -1. With this,

for example- the formula $projection.paymentsum * hry_node_sign_value( dimension => $projection.connid) as paymentsumSignRef

will return the key figure paymentsum for all nodes/leaves in the hierarchy with initial sign reversal indicator and It will return "- paymentsum" for all nodes/leaves with not initial sign reversal indicator.

If there is no field with semantics signReversal in the hierarchy view, the function HRY_NODE_SIGN_VALUE always returns +1.

Example: Analytical query

@AccessControl.authorizationCheck: #NOT_ALLOWED
@EndUserText.label: 'SIGN REVERSAL'
@Metadata.ignorePropagatedAnnotations: true
define transient view entity ZLR_SIGN_REV_FLIGHT_1 
   provider contract analytical_query 
     with parameters
     @EndUserText.label: 'Hierarchy'
     @Consumption.defaultValue: 'CNTRY' 
     p_hienm : char5 
     
  as projection on ZOQ_FLIGHT
    
 {   
    @AnalyticsDetails.query.axis: #ROWS
    @AnalyticsDetails.query: {
      displayHierarchy: #ON,
      hierarchyBinding: [{ type : #PARAMETER , value : 'p_hienm' }]
    }  
    connid,
    @AnalyticsDetails.query.axis: #FREE
    currency,
    
    @Semantics.amount.currencyCode: 'CURRENCY'
    @Aggregation.default: #SUM
    @AnalyticsDetails.query.axis: #COLUMNS
    curr_to_decfloat_amount( paymentsum ) as paymentsum,
    
    @AnalyticsDetails.query.axis: #COLUMNS
    @EndUserText.label: 'HierSignRev'
    @Aggregation.default: #FORMULA
    $projection.paymentsum * hry_node_sign_value( dimension => $projection.connid) as paymentsumSignRef
  
}

Result:

In this example for Hierarchy ZOQ_CONNECTION_HIERARCHY (which is defined in the ZOQ_FLIGHT), signReversalFlag is set for Carried id 'A', 'JL', 'UA'. Therefore, in result of analytical query HierSignRev field is showing the –ve result of the booking total.

SAP Delivered Hierarchies:

There are few SAP delivered hierarchies which have this feature.

Following fields name: FinancialStatementItem, CnsldtnFinancialStatementItem, FinancialStatementLeafItem, GLAccount, etc.

Can have this feature because they have foreign key association with dimension view which has hierarchy association to hierarchy view supporting this feature.

For example: Field with name ‘FinancialStatementItem’ typically have a foreign key association to dimension view I_CnsldtnFinStmntItem and corresponding hierarchy view I_FinStmntItmHier will support this feature.

Constraints:

Only one element in a view of data category HIERARCHY can be marked with semantics signReversal. The data type of the element should be CHAR of length 1. Allowed values are X or space.

Related Note:

1385580 - How does a formula variable with a replacement path work?

Availability:

This feature is available from S/4HANA 1909 (ABAP Platform 7.54).

Why Don't We Use Data and Analytics Group on SAP Community?

2024-04-18T18:28:14.375000+02:00

Hey Data and Analytics Folks! Why Don't We Use Data and Analytics Group on SAP Community instead of Technology?

Of course, it does not matter at the end. As long as if you tag your posts with SAP Managed tags everybody can find your posts. But there is a really one huge difference for usability that here in Interests Groups we can reply-the-reply but under Products and Technology we cannot! Check out this blog post SAP Datasphere is ready to take over the role of SAP BW by @kenneth_dalvik and all responses that are very all boring sequential --there is no reply-the-reply option! 🙃

So let's start using this group Here is already available Data and Analytics. The group will be definitely a perfect fit for SAP Analytics Cloud SAP Datasphere SAP Analytics Cloud, hybrid analytics SAP HANA Cloud, SAP HANA database SAP Analytics Cloud, connectivity SAP Analytics Cloud, analytics designer SAP S/4HANA Cloud, extended edition SAP S/4HANA Embedded Analytics SAP Business Planning and Consolidation, version for SAP NetWeaver SAP Business Warehouse Accelerator BW (SAP Business Warehouse) SAP BW/4HANA BW SAP BEx Analyzer BW SAP BEx Web SAP ASE - BW Enablement BW SAP HANA Data Warehousing SAP Data Services SAP Data Intelligence SAP Data Custodian SAP Big Data Services SAP BusinessObjects - Platform Administration SAP BusinessObjects - Semantic Layer SAP BusinessObjects Mobile SAP BusinessObjects - Semantic Layer - SDK SAP BusinessObjects - Web Intelligence (WebI)

These are welcome too SAP Master Data Governance SAP NetWeaver Master Data Management SAP Data Quality Management for SAP NetWeaver MDM

One thing I've noticed we cannot submit the blog posts directly. We need to "Submit for Review" only. You can still post discussions aka questions directly.

Thanks owners @ColinC, @meganhoy, @moshenaveh, @caroleighdeneen, @craigcmehil for their support!

Regards,
Tuncay Karaca

Understanding Data Modeling Tools in SAP

2024-05-02T16:25:43.459000+02:00

Choosing the right SAP data modeling solution can be a challenging task, as there are multiple options available, including cloud-based or on-premise solutions with or without data visualization capabilities etc..so to select the best tool that can meet the project requirements and specifications, several factors need to be considered including, reviewing the raw data source and understanding how it will be used, assessing the need for data warehousing capabilities, evaluating the team's skill sets, and deciding whether a cloud or on-premise solution is preferred.

During the last few years, I've worked with almost all the SAP Data Modeling tools that are available, and In this blog article, I would like to briefly highlight the strength of each tool and where would be the best fit for it 🤗.

Understanding Data Modeling

so what it's data modeling in SAP and why it's important? 🤔

when we talk about Data modeling we are defining the process of creating diagrams that show how data flows in and out of a database. These diagrams define the data formats, structures, and functions required to support the data flow. Once the database is built, the data model becomes documentation for its existence and design. Data models provide a framework of relationships between data elements within a database. They enable different applications to share the same data and create a simple and logical database that eliminates redundancy, reduces storage requirements, and enables efficient retrieval.

SAP HANA Calculation Views

SAP HANA calculation views are the key data modeling object on HANA, it's a graphical object that describes all the data processing steps from raw data to the final, consumable output.

Common data processing steps include filtering data, combining data, aggregating data, calculating new values, converting values, and ranking data. Calculation views are built in layers so that each calculation view can consume other calculation views to form a stack of super-models. This approach promotes the reuse of calculation views at the lower levels.

Strengths:

In-Memory Processing: Data processing occurs directly in memory, ensuring high performance.
Graphical Interface: Intuitive tools make it easy to create and visualize models.
Custom Logic: Ability to integrate custom SQL for tailored data processing.
Advanced Analytics: Supports spatial, graph, text analytics, and predictive/machine learning.

Best Fit: Developing flexible data marts with custom logic requirements.

SAP BW/4HANA

SAP BW/4HANA is an on-premise data warehouse. The main purpose of a data warehouse is to extract data from any data source, integrate the data, store the cleansed data, and provide modeling tools so that data models can be created ready for use by any analytical tool. This is exactly what SAP BW/4HANA can do.

Strengths:

Ready-Made Models: Comprehensive data models are provided for virtual and physical storage.
Data Warehousing Features: Supports dimensional modeling, hierarchies, and efficient data storage.
Graphical Tool: User-friendly interface for efficient model visualization.
On-Premise Deployment: Ideal for industries requiring high security and data control.

Best Fit: Establishing on-premise data warehouses with strong data integration needs.

ABAP CDS Views

ABAP CDS Views enable developers to create data models that are semantically rich. These models are then exposed to UI clients by the application services. CDS Views is the central pillar of S/4HANA development and is used as the core technology in most of SAP's programming models.

Strengths:

High Performance: Data processing is pushed down to the database level, ensuring efficiency.
Ready-Made Models for SAP S/4HANA: Simplifies operational reporting on S/4HANA.
Flexible Development: Allows for code-based customization leveraging SQL skills.

Best Fit: Operational reporting on SAP S/4HANA with ready-made content.

SAP Analytics Cloud

SAP Analytics Cloud is an end-to-end cloud solution that brings together business intelligence, augmented analytics, predictive analytics, and enterprise planning in a single system. It is a solution aimed at business users for self-service analytics.

Strengths:

Integrated Modeling: Modeling seamlessly integrated with reporting tools for streamlined analytics.
Cloud-Based: No need for software installation; data modeling is conducted in the cloud.
Self-Service Analytics: Empowers business users to create their own models.

Best Fit: Organizations seeking self-service analytics with integrated modeling and reporting.

SAP Datasphere

which is so far My Absolute favorite tool 😁! It is a public cloud software as a service (SaaS) data warehouse that supports the business data warehouse architecture. This tool effortlessly harmonizes data across the enterprise, making it a must-have for any business. It includes services for data modeling, data integration, cataloging, and data warehousing across SAP and non-SAP data, making it a one-stop-shop for all data management needs

Strengths:

Comprehensive Data Warehouse Features: Supports dimensional modeling, data history management, and hierarchy modeling.
Scalability: Easily scale resources in the cloud, supporting new innovations.
Cloud Service: Simplifies software management through cloud consumption.

Best Fit: Cloud-based data warehousing with advanced features and scalability.

SAP BusinessObjects BI Semantic Layer (Universes)

An organized collection of objects that called a Universe, which consists of dimensions, measures, and attributes grouped by business topics. The skill of a Universe developer is to create objects that resemble business terms by mapping them to the columns of the database tables. In some cases, SQL coding may be required to generate the value of the objects.

Strengths:

User-Friendly Interface: Graphical tool simplifies data modeling tasks.
SQL-Based Development: Easy to understand for database developers.
Mature Tool: Offers a wide range of features for diverse modeling needs.

Best Fit: Supporting SAP BusinessObjects reporting tools with Universes.

for more information, I would recommend this Learning journey from SAP which will give you an overview of all the SAP data modeling solutions 😊

Currency Translation in SAP Datasphere

2024-05-07T09:57:57.155000+02:00

Currency translation refers to the process of converting financial data from one currency to another.

This is particularly important for multinational companies that operate in multiple countries and use different currencies for their financial transactions.

Currency translation in SAP typically involves the following steps:

1. Setting up currency exchange rates: Before performing any currency translation, exchange rates need to be maintained in SAP. These rates can be manually entered or automatically updated from external sources.

2. Defining translation ratios: Companies may have specific rules for currency translation, such as using average rates, closing rates, or historical rates. These rules need to be defined within SAP.

3. Executing currency translation: Once the exchange rates and translation rules are set up, currency translation can be executed. SAP usually provides standard functionality and reports to perform this task.

4. Reviewing translated financial data: After translation, it's essential to review the translated financial data to ensure accuracy and compliance with accounting standards.

Currency translation in SAP is crucial for financial reporting, consolidation, and analysis purposes, allowing companies to view their financial data in a common currency, facilitating comparisons and decision-making across different regions.

To perform currency translation in SAP Datapshere, the following tables must be available in your space:

TCURV - Exchange rate types
TCURW - Exchange rate type text
TCURX - Decimal places in currencies
TCURN - Quotations
TCURR - Exchange rates
TCURF - Conversion factors
TCURC - Currency codes
TCURT - Currency text

Creating currency translation related tables in SAP Dataspher:

Login to SAP Datapshere, go to Data Builder menu, and click on create icon.
Select 'Currency Conversion View' from the drop-down.
Select source which can be manual or any SAP connection in your SAP Datasphere space which is compatible for replicating currency translation tables.
If source is manual, upload the data to all the required tables either manually or via data flows.
If SAP source is selected, respective remote tables and data flows will also get created.
After clinking on create option, 32 objects will get deployed including below 8 data flows
Create a task chain and add all these data flows for uploading the data to required TCUR* tables. You can also schedule the task chain to keep your data updated.
Execute the task chain to update the data.
Create 'currency conversion column' in required object (for instance in view)
Enter business name, technical name, data type, precision and scale.
In currency properties, select source amount column, source currency (fixed value or columns), target currency (fixed value, columns, or input parameter) and reference date (input parameters, columns, expressions, fixed date) for conversion.
Enter client, conversion type and error handling
Preview the data and verify the rate maintained:

Reference: https://youtu.be/m4m1TNJ5Ekw