Wednesday, 10 December 2014

OBIEE Projects - Typical Error Scenarios

The third chapter of session Success with Oracle BI? Typical Error Scenarios and their Solution outlines typical error scenarios we recognize during our first contact with OBIEE project teams requesting support as shown in chapter 2. Please follow our OBIEE project series presenting our process for solving typical OBIEE project issues:

1. OBIEE Project Success - Introduction
2. OBIEE Projects - Suspect Requests
3. OBIEE Projects - Typical Error Scenarios
4. OBIEE Projects - Turn-Around Approach
5. OBIEE Projects - Criteria for Fast Success and Assessment
6. OBIEE Projects - Solution Process

At first we ask different users and stakeholders to describe the current situation. Response is often very impressive:
  • Even simple reports are very labor-intensive.
  • All figures in OBIEE Answers (or newer Analysis ;-) ) need to be created by users themselves, because supplier says that's the only way to create calculations.
  • Detailed data is not available dynamically.
  • Star schema combination isn’t possible.
  • Excel is much more powerful than OBIEE Answers.
In the end normal business users cannot build any report although - to be honest - they just request for standard BI functionality. Stop the project would be understandable. So, our next step is to find out the reasons. But already after first interviews it's certain to say without a deeper analysis:
  • For item 1-3: OBIEE configuration is technically wrong and previous developers didn't understand OBIEE multilevel calculation logic.
  • For item 4: OBIEE is at least incomplete configured.
  • To solve item 5 users typically need some expert training. Please have a look to our presentation Tricks with Oracle BI Answers and training class OBIEE Analyses Insights.
To get a full picture of the situation we take a first look into OBIEE repository configuration for just a short time. Image shows a section of presentation layer from a German OBIEE project acting as basis for our series:

Bad OBIEE presentation layer example

Our assumptions are confirmed just verifying such a small section. It's a really nice example for a bad OBIEE repository presentation layer implementation:
  • There are technical names at GUI level.
  • No business structure is applied (dimension attributes are mixed).
  • No time dimension or figures are available.
It's obvious after the first analysis why OBIEE cannot work as it should. We will see the whole OBIEE repository configuration in one of the following series articles. As next step we describe our turn-around approach. For now we just know what's wrong, but customers need to be sure that it's worth to go ahead with OBIEE.

Any questions? We provide Oracle BI expert support & coaching regarding all relevant OBIEE topics like architecture, security, configuration, reporting and mobile.

No comments:

Post a Comment