Profit from our Knowledge

2011-02-21 | Candid Rutz
BO Universe Design Best Practices
According to the book of Genesis, the universe was created in seven days. The following day-by-day analogy provides a best practices guide for the creation of an SAP Business Objects Universe. Seven days actually might just be enough.

2010-12-10 | Dr. Stamatis Stefanakos
Improved Customer Understanding with Survival Analysis
In this paper we discuss how survival analysis can be used to study the active lifetime of customers. We show how to calculate hazard probabilities and survival curves for segments of the customer base and how these can be used to extract valuable key performance indicators and to fine-tune the timing of campaigns.

2010-11-26 | Adrian Wyss
SAP BusinessObjects: Standard Development Kits (SDK)
SAP BusinessObjects (BO) is a leading suite of data analysis and reporting tools designed to deliver insight to executives where and when they need it. Beyond a broad variety of desktop and web applications, BusinessObjects Enterprise provides a Standard Development Kit (SDK) for customized developments. This paper outlines the possibilities of the SDK and its tremendous value for the BO platform.

2009-12-01 l Dr. Andreas Hauenstein
Neue Datenbanken für BI - Wie gut sind sie?
In letzter Zeit tauchen bemerkenswert viele neue Datenbanksysteme am Markt auf, was vor allem auf die Verfügbarkeit billiger 64-Bit Systeme mit grossem RAM zurückzuführen sein dürfte. Ein praxisorientierter Test zeigt, wie gut sie im Vergleich zu bekannten Systemen wie Oracle oder Mysql abschneiden.

2009-09-01 l Dr. Andreas Hauenstein
Managing Dimension Hirarchies for Reporting
Every business has to aggregate numbers along hierarchies, like geography or department. Hyperion Essbase is very popular with financial controllers for facilitating this task. However, dimension design typically works on a per cube basis, which causes considerable maintenance overhead when the same dimension is used in multiple cubes or with other reporting tools.
We describe a method where dimension maintenance is done in one cube ? the metadata cube ? and then exported to a relational table. From there, the dimension flows into any number of reporting cubes that want to use it.
The dimension is automatically augmented to include all members occurring in the facts, even if they were forgotten during the dimension design process. We automatically create bridge tables to make the dimension acessible in relational queries and with any reporting tool.

