If your business intelligence initiative or program is struggling it may be because you do not have effective BI solution architecture in place. BI solution architecture involves far more than just understanding a technology product stack. As its name suggests it is by nature a solution and it encompasses business, information, application, infrastructure, data, integration, and service architectures.
In this new video I show you how to design business intelligence solution architecture that will make your business intelligence initiatives successful. I use SAP BusinessObjects as my example but the concepts are actually vendor agnostic so you can use the ideas with numerous BI and data technologies.
Watch the video
The concept behind Query & Analysis is really about empowering the Business User and Analyst to interact with data on the fly in a Self-service BI environment. There a few tools available from SAP BusinessObjects that fulfil this criteria. First of all, here’s a little background, so as to avoid any confusion around what the products are.
Historically, the original Query & Analysis and Reporting tool was simply called ‘BusinessObjects’. Back then if you were to ask someone what reporting tool they were working with they would just say ‘BusinessObjects’. That was the only tool, until sometime later the first version of Web Intelligence was released. After BusinessObjects acquired Crystal Decisions the ‘BusinessObjects’ reporting tool was renamed Desktop Intelligence, sometimes also known as Deski. Running alongside Desktop Intelligence the thin client tool Web Intelligence was being developed.
Over the years Web Intelligence has grown to become SAP BusinessObjects’ flagship tool that allowing non-technical users to create new queries, slice and dice, and then drill down through their data all via a web browser. The advancement in Web Intelligence means that Desktop Intelligence is now coming to its end of life.
A second tool available is Voyager. Voyager is an Online Analytical Processing Tool (OLAP). In the BI 4.0 release Voyager is superseded by SAP BusinessObjects Analysis edition for OLAP and SAP BusinessObjects Analysis edition for Microsoft Office. It should be used when analysis is required against large data sets.
We also find it useful to think of a third tool under the Query & Analysis category. That is the search tool named Explorer. The original name for Explorer was Polestar.
Business Intelligence information consumers and analysts often have the important requirement to drill up and down through an organisation’s data hierarchies. The ability to drill up and down through an organisation’s data enables effective analysis allowing the analyst to identify both underperforming and over performing areas.
Native drilling capabilities exist within Web Intelligence under the name of ‘Scope of Analysis’. To understand Scope of Analysis it is important to know that a Web Intelligence report always returns data from the database in the form of a microcube. Enabling the ‘Scope of Analysis’ functionality then allows drill down and drill up functionality to be performed on the microcube. Web Intelligence uses a microcube because it is built for flexible ad hoc ability to quickly build reports on the fly and for fast query execution. However, the limitations of the ‘Scope of Analysis’ functionality must be understood. When a microcube is built with drilling capabilities beyond four levels (that is four dimensions) the query performance can suffer. Large multi-dimensional queries requiring drill down through numerous dimensions require tools such as OLAP.
Many organisations have hierarchies that run beyond four levels. When large hierarchies are being utilised it is best to use the SAP OLAP client or a suppression technique within a Crystal Report. However, if Web Intelligence must be used then the requirement to drill down beyond four levels without a performance hit can be realised through vertical drilling hierarchy tables.
The basic technique is to map the source system data through staging tables to a horizontal dimension table with hierarchies and then transpose the table to a vertical hierarchy dimension table. The existing horizontal hierarchy dimension data can be transposed to a vertical hierarchy structure using SAP BusinessObjects Data Integrator as part of the ETL process. Before this can happen the vertical hierarchy dimension tables must be modelled in the data warehouse.
The hierarchy tables are then configured in the SAP BusinessObjects universe where they become available to Web Intelligence. There is some complexity that must now occur in the development of the Web Intelligence report. Basically a data provider with a query which includes the @prompt syntax in a filter is developed to run against the vertical tables. After that a block is developed in the report with hyperlinks that use the opendocument.jsp function. The parent report hyperlinks are designed to call themselves with the opendocument.jsp function (the parent and target reports are the same report) but the logic of the report is such that the prompt will be populated with a node of the hierarchy one level up or down from the current level. This forces the report data to refresh at a level higher or level lower than the current and effectively allows the user to drill up or down through the hierarchy.
There are some limitations to this system. Firstly, the development overhead for the tables and ETL jobs. Secondly, it takes some advanced skill to be able to develop the report. Thirdly, drill down is only at one level per click i.e. there is no multi-level tree walking. That is that from level one in the hierarchy the user must go to level two, it is not possible to jump immediately to level three. This is not true if Crystal reports is utilised.