www.sapbo.graymatter.co.

in

Turbo charge your SAP Design Studio applications!

Executives want to gauge their business through well-organized metrics and KPIs to make timely, clear
and consistent decisions. Key decision makers expect to view their dashboards depicting real-time data
with minimal loading time, irrespective of type of device. In this blog I want to discuss how to design SAP
Design Studio Applications (containing Pagebook or Tablets) to reduce load time and improve
performance.

Most SAP Design Studio Plugins use Pagebook design with each page having one dashboard. I want to
address how to improve performance during initial load and also how to improve performance after
initial load when user navigates from one dashboard to the other.

Improving Initial Load of Dashboard:

Prompt Variables need to be assigned at Variable Initialization with Default values.

Data sources that are needed for the first page need to be loaded with load on script false and for rest
of the queries load on script need to be kept true (these queries need to be initialized through script
based on Dashboard Selection in Dropdown or List box based on requirement).

www.sapbo.graymatter.co.in

www.sapbo.graymatter.co.in

Improving Performance after Initial Load:

When loading data sources, based on selection of SAP BO Dashboard in Dropdown, its better to check
whether Data source is Initialized or not. If its initialized then no need of loading otherwise data source
needs to be loaded. Use if logic to check whether data source is loaded or not.

Where to Give Prompt Variable Values?

As there will analysis of data based on time period, e.g., from Month or To Month, its better to have
Variable Assigning script in last dropdown selection or its better to have a go button after all dropdown
selection, and then in Go button selection events write script to assign datasources to Prompt Variables.

When changing time period in Dashboard, Prompt Variables script need to be assigned with values in
sequence, without any other script in middle, and these Prompt Variables are merged as Variable
Container. However, this will impact performance as all datasources having same prompt variables will
be reloaded with new prompt Values. But there will be a change in this concept as there will be
possibility to have unmerged prompt variables SAP BO Design Studio 1.5, to improve performance.

Keeping Local Filters:

Sometimes based on requirement its better to have Local filter in query instead of using Variable
Prompt e.g., drill down from one portlet to other, by filtering Datasources.

For KPI Summary Display:

For Summary Dashboard or high level business objects dashboard presenting only KPI Values, as shown
below, write script to get that value in Change Event of datasources.

www.sapbo.graymatter.co.in

www.sapbo.graymatter.co.in

Reusability of Datasource:
If there is a need to use different measures and common dimension for assigning to different charts. Use
one datasource and can select measure based on chart requirement.

Reusability of Datasource (Bex Queries):

Using one Datasource, assign other datasource by assigning datasource with donnection names and
datasource type.

Use of Global Script in Technical Components:

Use global Script technical component to avoid writing script in different places by calling global script
where ever needed e.g., based on dropdown text selection append text with some CSS class.

Use of Base64 Image compression and Sprite Images:

Its better to use Base64 Code in CSS for big images like logos or background image, instead of calling
image from BOE server. For small Icons use Sprite Image.
(Note: In SAP Design Studio 1.5 Release, there will be parallel processing of Datasources to improve
performance and there will be unmerging of Prompt Variables in Variable Container)

www.sapbo.graymatter.co.in