BI – Into the fifth dimension
Oracle BI – Thoughts (2) – Cadran publishes a series of articles exploring the philosophy behind Oracle Business Intelligence in combination with Oracle JD Edwards. Each article provides practical insights to help you make the best decisions when implementing and using these systems. In this second article, we examine the Star Schema and what this model can mean for your organization.
Star scheme
The foundation of the Star Schema was laid by Ralph Kimball, whose theories on dimensional modeling predated the rise of BI software and remain highly relevant for how data is represented in Oracle’s BI environment. The Star Schema is essentially a visual model that places facts and dimensions at the core.
In an abstract sense:
Star Schedule Conrete
Fact
The foundation of the Star Schema was laid by Ralph Kimball, whose theories on dimensional modeling predated the rise of BI software and remain highly relevant for how data is represented in Oracle’s BI environment. The Star Schema is essentially a visual model that places facts and dimensions at the core.
Example of a Star Schema:
Consider revenue, where different calculations group data, such as by invoices or revenue amounts. A fact becomes a KPI when associated with a standard, budget, or evaluation.
Within Oracle BI, a fact only gains significance when it has a clear definition that aligns with your operations using Oracle JD Edwards. This prompts questions such as:
- What counts as revenue? For instance, all invoiced amounts.
- Which currency applies?
- What is the correct date (invoice or general ledger date)?
Dimension
A dimension can be recognized whenever the term “per” is used alongside a fact:
- What is Revenue per Customer?
- What is Revenue per Month?
A dimension also requires a clear definition. For instance, what precisely defines a “customer”? Each detail matters, as attributes like country or invoice number add context to your analysis.
Together, these elements form a business information model, also known as Oracle’s Common Enterprise Information Model, providing a single source of truth. In the next article, we’ll explore how facts and dimensions work together for clear business insights.
Hierarchy
When a dimension also has a structure, it is referred to as a hierarchy.
In Oracle JD Edwards, data is often organized using category codes. The correct interpretation of these codes can make all the difference. Consider the time dimension with its logical calendar structure. This structure opens up many options within Oracle BI to explore your data: Drill Down, Roll Up, Zoom In, and Zoom Out. You can also summarize or detail information at different aggregation levels.
In my next article, I will further illustrate the interplay between facts and dimensions with examples.
Implementing a BI solution goes beyond installing software. Cadran’s vision centers on ensuring that the right information is available to the right people in your organization at the right time. A thorough project approach is essential to avoid the pitfalls of such an implementation. BI is not about generating reports or creating attractive dashboards; it’s about managing your organization. Cadran is your partner for Business Intelligence and JD Edwards.
Author: Rick Brobbel
BI Consultant at Cadran Consultancy
