SAP HANA Modelers: How to Design for Better Performance

  • by Ned Falk, Senior Education Consultant, SAP
  • May 9, 2017
Value help and mapping of variables and input parameters have been underused features of SAP BW for many years. In native SAP HANA modeling these features can be implemented with just a bit more effort. Learn how these foundational concepts previously used in SAP BW can be used in SAP HANA to create calculation views.
Learning Objectives

Reading this article, you will learn how:

  • To use input parameters as filters
  • To map input parameters from higher-level views to lower ones
  • Input parameters and variables can improve performance
Key Concept
SAP HANA is fast, but fast in this sense is relative. By using value help views as well as advanced mapping of input parameters, you can use SAP HANA to make models run faster and more flexibly, and in a more user-friendly way.

SAP HANA provides some advanced and related modeling features that only a few users are currently leveraging. Two of these, value help views and mappings of input parameters, provide features that make SAP HANA run faster and, more importantly, make SAP HANA more flexible.

I show how to use these two SAP HANA concepts to provide better usability and improved performance. These two concepts are connected, as value help views can be attached to variables and input parameters; however, I mostly address each concept separately in this article. In the first example, I focus on value help views. In the second, I explore the advanced use of input parameters as filters and the mapping of these from a lower-level view to a higher-level view.

My purpose in writing this article is to show the advanced features of SAP HANA modeling. I do not go into step-by-step details to show the navigation basics or the basics of variables or input parameters, but rather concentrate on an overview of the concepts of these advanced features and how to implement them.

Value Help Views

A value help view is a view that contains a list of possible values that can be selected when filtering is performed by the user. The most common form of a filtering operation is when the user is asked for input to an SAP HANA variable—for example, pick a customer. The default view that SAP HANA uses to present this list would be the values that are available in the main view you are trying to analyze.

For example, say you have a view (in this case, sales), and it has a custom table with 500 customers linked to an order table with 50 million orders as your main view. Depending on the design of this view, the use of this as a view as the default help view could mean the view would scan all 50 million records to present just 500 as the list of choices.

Ned Falk

Ned Falk is a senior education consultant at SAP. In prior positions, he implemented many ERP solutions, including SAP R/3. While at SAP, he initially focused on logistics. Now he focuses on SAP HANA, SAP BW (formerly SAP NetWeaver BW), SAP CRM, and the integration of SAP BW and SAP BusinessObjects tools. You can meet him in person when he teaches SAP HANA, SAP BW, or SAP CRM classes from the Atlanta SAP office, or in a virtual training class over the web. If you need an SAP education plan for SAP HANA, SAP BW, BusinessObjects, or SAP CRM, you may contact Ned via email.

See more by this author


6/7/2017 9:55:42 AM
József Zérczi

Thanks for sharing this.
Tip and tricks related to HANA information view performance are always welcome as a 'badly' designed information view can bog down an otherwise fast HANA system.

Please log in to post a comment.

To learn more about subscription access to premium content, click here.