The SAP BusinessObjects Business Intelligence Platform 4.1 includes significant performance benefits when one reports on SAP BW. These benefits are a great reason to upgrade for those of you using BW. Specifically there are enhancemets:
On report creation or edit with Web Intelligence or Crystal Reports for Enterprise documents which are based on BEx Queries.
On report refresh with Web Intelligence or Crystal Reports for Enterprise on BEx queries with variables.
On addition of a BEx Query to an Analysis for OLAP workspace
Web Intelligence documents based on BEx Queries via BICS
A big advantage here is that when you select a BEx query with mandatory variables which do not have default values, a variable screen (shown below) will display BEFORE the query panel. This will save some time.
Additionally, you should see a substantial performance gain for the report refresh portion once you’ve entered the variable values via this prompt window. Note that this particular gain is not seen when user-defined prompts are combined in a document with BEx variables.
View time also brings quicker rendering of the prompt window (screenshot below) as well as a quicker refresh once the mandatory prompt is entered for your end users.
In addition, there is now a new “Design Time” API that has been implemented at design / edit time. This particular feature requires that your SAP BW server is updated to the level indicated at the bottom of this blog. This Design Time mode allows for the fetching of metadata and master data with far less RFC calls. Specifically, the new API is used when you select queries while designing a report.
How does that look in actual practice? Well as an example, when you select your query
You’ll see a lot less of the loading screen
before the BEx queries available objects are displayed (shown below). The first query you select on a particular server will take more time than the rest due to the initial handshake / warm-up process. Afterwards, it should be very fast. You’ll still get some of these benefits even if your BW server isn’t of the version listed below.
Crystal Reports for Enterprise
Report creation or modification on BEx Queries
Similar to the workflow in Web Intelligence, Crystal Reports also shows a variable screen before the query panel when the query contains mandatory variables without default values. Due to this, the variable screen should load more quickly. This allows the query panel itself to load more quickly. Finally the report itself is refreshed more efficiently.
The report consumers will also see benefits at view time. The prompt screen (shown below) will render more quickly. In addition, there are improvements with the generation of lists of values in this variable screen. The gain increases as the list grows larger. Finally, the report should refresh more quickly.
Analysis OLAP – selection of BEx Queries
The Open Data Source interface has changed slightly. It now opens to the Find tab instead of the Folders tab. This is helpful when there are a large number of queries on the system as you can immediately search without waiting for the initial folder / query view to load.
What are the BW server requirements to take advantage of the Design Time improvements?
As mentioned earlier, you should still see improvements without the following in most areas. However, to get the maximum you must meet the following criteria (subject to change):
The BW backend needs the following service pack levels and SAP notes in order for the design time improvements to be enabled and fully functional:
BW 7.30 SP8 or BW 7.31 SP5+, plus all the SAP notes listed below.
For critical cases, there is also a collection of notes for 7.30 SP7 available (excluding the notes mentioned below, so you need to apply them as well).
Even better, the versions which already contain everything are 7.30 SP10, 7.31 SP08 and 7.40 SP05
Additional SAP Notes:
- 1771995 – Wrong hierarchy level
- 1750788 – Meta data extension (contains a collection of extensions and fixes)
- 1767351 – Missing meta data of characteristics in the fix filter – only relevant for characteristics that do not support drill down (i.e. are only in the fix filter of the query).
- 1776999 – Sorting type of hierarchies is always “HIERARCHY” although it was changed in the query designer
- 1777544 – Missing meta data of hierarchy node type attributes
- 1778347 – Hierarchy node type attributes are not read
- 1770434 – Correction for selection state of compound characteristics
- 1762156 – Correction for nodes in selection space
- 1776688 – Optimization for reading hierarchy nodes, too many hierarchy levels are read
- 1798297 – Correction for issue found on Samsung queries
- 1806813 – Correction for missing text for members used as default variable values
- 1809517 – Correction for invalid variable order when retrieving the list of variables through the design time services
- 1811124 – This note fixes the sorting of the of drill down characteristics returned by the design-time API so that it matches the runtime sorting
- 1812142 – This note fixes the sorting of the hierarchies returned by the design-time API so that it matches the runtime sorting
- 1817482 – This note adds the feature for the Design Time API to choose whether members should be read initially or not. By default, there are not read; this provides a performance enhancement for SL.
I’ve heard good things about the performance gains from our BI 4.1 ramp-up customers and would love to hear stories of any improvements from those of you reading this blog.