Venkatakrishnan J

One of the best ways to understand the BI EE repository design is to start designing the Business Model Layer for a single Physical table. Any person who is new to BI EE will always start with testing the repository for a single physical table. This is where BI EE

One of the issues that people often face while using BI EE is the lack of control on Multi-Select prompts. One cannot set Multi-Select prompts to a presentation variable & similarly one cannot display the multi-selected values in a report (only filter view supports the display of all the selected

One of the flexibilities of the BI Server is its ability to fine-tune certain sql queries being fired back to the database. One such example is its ability to enforce certain outer joins when required. For example, lets consider a simple example containing the Customer dimension and the Sales fact

Whenever BI Server is used for creating reports containing data from multiple databases, BI Server acts like a mini-database engine. It does a lot of operations itself like joins, sorts, group bys etc, everything in its own memory space. Since it acts like a database engine, it has to have

In the last blog entry here [https://www.rittmanmead.com/blog/2009/08/21/oracle-bi-ee-10-1-3-4-1-oltp-reporting-switching-tables-based-on-chosen-dimensions-use-case-1/] , i had shown a very simple transactional reporting use case wherein i made the BI Server to switch tables based on the measures chosen. Basically switching of tables would result in hitting a specific table

Though BI EE is well known for reporting on Stars, Facts and Dimensions, one of the lesser known or lesser advertised features is its extensive transactional or OLTP modeling capabilities. Steve Devine (our guest author last week) documents his experience well here [https://www.rittmanmead.com/blog/2009/08/17/

I saw a peculiar requirement being discussed in a pentaho forum(i was actually browsing for some unique Pentaho features and stumbled upon the requirement) this week wherein end users wanted to get the sub-totals automatically while drilling on a dimension. In normal cases, i would have left it as

As with any reporting tool BI EE works on the premise of converting the front-end column selection to the corresponding physical queries. But one of the advantages that makes BI EE stand apart from other reporting toolsets is its ability to do certain joins/sorting etc in-memory without pushing them

One common issue that gets highlighted when someone uses BI EE is its inability to leverage Parent Child Hierarchies out of the box. 11g release scheduled sometime later next year is supposed to address this seamlessly. Having said that, being consultants ourselves most of the times we find ourselves in