Tableau LOD Expressions from Oracle Developer POV

The main purpose of any Business Intelligence system is to provide business users ability to answer questions that are important to running the part of the business for which they are responsible. For example:

  • Show me sales for each client by month.
  • Show me the average sales amount for each client by month.
  • Show me the running total amount by date.

If Business Intelligence system designed really well your business users just have fun asking questions of their data.

But there are many questions to answer Business Intelligence system need to work with data that has been aggregated to different levels of detail.

Continue reading “Tableau LOD Expressions from Oracle Developer POV”


How to avoid “Distinct” in OBI analysis

As you know, by default, OBI reports doesn’t display duplicated records in the analysis. The reason for such behavior it’s that OBI it’s the analytical tool, not a query tool. The main “Use Case” scenario for OBI, as well as any other Business Intelligence tools, it’s when a business user starts their data analysis from higher levels of data and drill down to the details. If for one fact, several fact values are related to the same dimension values (i.e. several amounts for one client), it will aggregate the values and show only one row.

Continue reading “How to avoid “Distinct” in OBI analysis”

How to prevent browser caching on OBIEE client side

It’s a short story why I always use HTTP Server in my OBIEE installations.

I spent some time last week looking into a bug in the browser cache. The symptoms of this bug are as follows: users can see irrelevant data on dashboards, and F5 isn’t working to refresh data on the dashboard.

Continue reading “How to prevent browser caching on OBIEE client side”

Аудит изменений данных Hyperion Planning. Часть II – интерфейс

Вторая часть поста “Аудит изменений данных” посвящена визуализации протокола аудита изменений данных на уровне ячейки.

Continue reading “Аудит изменений данных Hyperion Planning. Часть II – интерфейс”