This document outlines a presentation on defining dimensions for an Oracle EPM solution. It discusses dimensional modeling concepts like facts, dimensions, and hierarchies. It also covers Oracle EPM's dimensional requirements like standard and custom dimensions. Finally, it explores common design scenarios such as currency conversion, audit trails, restatements, and time-based dimensions. The goal is to help companies properly define dimensions to meet business requirements and make data accessible in a timely manner.
Introduction to Prompt Engineering (Focusing on ChatGPT)
Dimension Decisions: A Guide to Defining Dimensions for Your Oracle EPM Solution
1. Dimension Decisions: A Guide to Defining
Dimensions for Your Oracle EPM Solution
September, 2013
RJ Linehan
rj@innovuspartners.com
2. Presentation Agenda
Profile
A True Story
Dimensional Modeling Concepts
Oracle EPM Dimensional Requirements
Common Design Scenarios
Questions
3. Company/Presenter Profile
Innovus Partners
Oracle/Hyperion Enterprise Performance
Management
Oracle Gold Partner
Based in the NY Tri-State Area
Follow us on Twitter, Facebook, and LinkedIn
RJ Linehan
Over thirteen years experience consulting in
the EPM/BI Space
OAUGNYC Board Member
Sleep Deprived…
4. A True Story Part 1
The Life of Tom Jones
Works at XYZ Company for past 15 years
Financial Planning & Analysis Department
Leverages Oracle/Hyperion EPM tools
Experienced two upgrades in past 8 years
No changes to core EPM solution in that time
Uses Excel to do his job
5. Dimensional Modeling Concepts
A single set of common data that satisfies the following user
requirements
Ability to make informed business decisions based on the right
data
Expectation of accurate data provided at the correct grain
Delivery of the data in a secure and timely fashion
Capacity to change with business requirements
What is a dimensional model?
(Borrowed from "The Data Warehouse Toolkit" by Ralph Kimball and Margy Ross)
6. • A fact is a business measure that is typically numeric
• A fact is the numerical data stored in an EPM application
• A fact can be additive or non-additive
• The list of dimensions that encompass an EPM application
defines the grain of the fact and the scope of measurement
What is a Fact?
(Borrowed from "The Data Warehouse Toolkit" by Ralph Kimball and Margy Ross)
Dimensional Modeling Concepts
7. • A dimension and its attributes describe the facts
stored in an EPM application
• Dimension attributes define the 'By' in a report
(Revenue by Quarter by Region)
• A dimension is a type of Metadata
What is a Dimension?
(Borrowed from "The Data Warehouse Toolkit" by Ralph Kimball and Margy Ross)
Dimensional Modeling Concepts
8. Dimensional Modeling Concepts
• Insist on complete functional/business requirements
• Know the data that will encompass the subject area
• Engage and learn from the business users
• Provide detailed pre-design questions for the business
and IT
• Request sample dimensions from source systems
Successfully Defining Dimensions During Design
9. A True Story Part 2
The Life of Tom Jones
Queries data against ERP system and DW
that is not available in Oracle/Hyperion
EPM tools
Uses Excel to incorporate that data into
his analysis
Uses Access to reorganize data
Process takes 3 days to complete
Publishes reports to management
10. Typical Dimensional Requirements
• Chart of Accounts
• Currency Conversion
• Calendars – Regular, Fiscal, Other
• Organization
• Legal Entity
• Business Groups
• Departments
• Operating Units
• Inventory Organization
• HR Organization
Dimension Definitions for Oracle Financials
11. Oracle EPM Dimensional Requirements
• Oracle EPM applications support standard and custom
dimensions
• A dimension member is an element of the dimension that is
typically unique to the application
• A hierarchy denotes a roll-up of dimension members within
a dimension that is either aggregating or non-aggregating
• Fact data must be loaded to a member from each dimension
in the EPM application
• Dimensions are often shared across EPM applications
Dimension Definitions for Oracle EPM Applications
12. • A standard dimension is a required dimension in an
EPM Application
• A standard dimension offers consistency
• A standard dimension provides out-of-the-box
functionality for select features of an EPM
Application
Standard Dimensions in an Oracle EPM Application
Oracle EPM Dimensional Requirements
13. • A custom dimension is typically not a required
dimension in an EPM Application
• A custom dimension provides for customization to
satisfy reporting requirements
• A custom dimension expands the perspective of
data stored in an EPM Application
Custom Dimensions in an Oracle EPM Application
Oracle EPM Dimensional Requirements
14. Common Design Scenarios
• Avoid building one application with many
dimensions to support all planned data
• Organize data sets that will be planned into
groups of common dimensionality
• Leverage a separate application to support
consolidated reporting
Dimensional Design for Budget & Forecasting Applications
16. Three types of currencies
Functional currency
Transactional currency
Reporting currency
Implementing currency conversion
Native vs. Custom
Design for future support of currency
conversion
Dimensional Design for Currency Conversion
Common Design Scenarios
18. Types of Audit Trails
User
Track data entry by user
Entity
Track data movement across entities
Scenario/Version
Track data movement across data sets
such as allocations
Dimensional Design to Support Audit Trails
Common Design Scenarios
20. View Dimension
Provides for different perspectives of
reporting
Calculation standardization
Dynamic calculations to reduce overhead
Dimensional Design to Extend Reporting
Common Design Scenarios
22. Time-Based Dimensions
DEMONSTRATION
A True Story Part III
The Life of Tom Jones
Initiative undertaken at XYZ Company to
better understand business requirements
Redesign of EPM Solution warranted to
support changing business requirements
3 day process drops to 1 hour process
Tom is now analyzing data and not
transforming it
23. Dimension Decisions: A Guide to Defining
Dimensions for You Oracle EPM Solution
September, 2013
RJ Linehan
rj@innovuspartners.com
Notes de l'éditeur
Blurb about presenting at Connection Point in Atlanta back in November
I had an hour and we went over, I have less time today and since it’s Friday, I don’t think we’ll be going over
Provide you with a brief background on my experience
Touch on basic concepts in dimensional modeling
Discuss the dimensional requirements for Oracle Financials as it pertains to other business activities
Discuss the dimensional requirements for in the EPM Stack
Dive into the meat of the presentation and walk through common design scenarios that you will encounter when building an EPM application
INVP
Consulting organization that specializes in working with and implementing the Oracle/Hyperion EPM Stack
Our team has an average of six years of consulting experience working with Oracle/Hyperion EPM
All members are Certified
Locally based right here in the tri-state area
RJ Linehan
13 years consulting, 15 years working with the products
Can do front-line consulting, Expertise in project management /
Starting number 32 next month
CPG, Retail, Ins/Fin
Mgt Rpt, Budg/Fcst, Capex, WrkFrc, Profitability, Exec Dashboards
This story will progress throughout the presentation
Title – “The Life of Tom Jones”
Get a little personal – first job out of college, lives out on long island and is married with two girls, commutes to midtown on the LIRR
Not covering all facets of Requirements Gathering and Design
Dimensional Design is most important concept for EPM
If not done properly -> user responses
The reports do not provide the answers I'm looking for
The data is not available when I need it
I don't have access to the data that I need to do my job
The reports and calculations take too long to execute, it would be faster if I did it manually in Excel
All existing features and functionality of EPM tool set will not be meaningful to the user if not properly designed
With the wrong data, the business user cannot do his or her job
To the user, the inability to get to the level-of-detail required for reporting and validation becomes unusable data
That truth is magnified when it is inaccurate or incorrectly pulled from the source system
Data is a valuable company asset that needs to be protected and secure
Out-of-date data will cause delays in reactions to ever changing market conditions and prevent an organization from being proactive
Organization Changes/Industry Changes All these changes drive changing reporting requirements
Before we dive into our discussion on dimensions, we need to talk about 'What is a fact?'
For the purposes of this discussion around Oracle EPM, a fact is numeric
Typed measures in Essbase, Smart Lists in Planning, Annotations in WorkSpace are all examples of metadata
Additive Accounts
GL accounts that roll-up to a P&L line item
Measures that aggregate along the time dimension (months->quarters->totalyear)
Non-Additive Accounts
Balance sheet accounts with EOM balances do not aggregate along the time dimension
Percent variance calculation that compares Current Year to Prior Year
This statement further demonstrates why dimensional design is SO important to dimensional design because it drives the architectural core of the dimensional model
For example,
The source system furnishes a numerical value (our fact) to be loaded to an EPM application
This numerical value, let's say it is $1,000 will have qualities that describe it
It was money spent to buy a laptop computer for an employee
It was an actual expense incurred by the organization - Scenario, Act
It is an expense booked to the Computer Hardware expense account in the GL - Accounts, Computer Hardware Expense
The computer was purchased in June of 2011 - Year, 2011 / Periods, Jun
The employee works for HR - Entity, HR Department
For example,
I would like to rank sales by region and quarter
I would like to track salaries by employee
I would like to report billing by client and attorney
The attributes or members (in EPM terms) make-up the dimension and the dimension describes the facts loaded to an EPM application
Metadata is not a dimension, often the terms are used interchangeably, which is not entirely incorrect
There are other types of metadata besides dimensions
Annotations and commentary
Security
Form definition
Business logic / Calc scripts
Preface with the challenge of setting expectations and ensuring all parties (IT, Business, Sponsors, Consultants) understand the deliverables and sign-off on them
Step back and review the overall state of a company's management reporting environment, take stock of what is available, what is usable, what the business users desire
Without proper requirements you are setting up yourself for failure
Confirm that the data exists and is in a state that it can be delivered by the source system within the parameters defined by the project
Make sure it is the correct data and supports the reporting requirements defined by the users
I always provide a list of questions specific to the solution being implemented to be answered by the business and IT
This information supplements the business requirements document during design to ensure nothing is missed
Request sample dimensions from legacy applications
Used to build out an outline before design
Working with the outline editor and excel to demonstrate reporting during design is useful in providing the business with a taste of what the solution will deliver and validate the requirements
This is a form of "Rapid BI"
This rule is used to determine if a two attributes of a fact should be in the same dimension or separate dimensions
Can be a challenge when defining dimensions during design if reporting needs are not clearly defined
Chart of Accounts
Types of Segments
Natural Account
Balancing Segment
Cost Center
Other Segments
Currency Conversion
Transaction Currency
Primary Currency
Reporting Currency
Calendars – Regular, Fiscal, Other
Organization
Legal Structure
Management Organization
Functional Organization
What are standard and custom dimensions? I'll explain in the next two slides
Essbase can support duplicate member names, but that design approach is normally discarded because of the challenges it poses to reporting
Examples include
June
Sales
FY11
Examples include
YearTotal is a popular roll-up that includes months, quarters, and yeartotal
All Years represents a non-aggregating roll-up of the year members
If there are 10 dimensions in an EPM application, each data point will have 10 members that describe it, one from each dimension
Important consideration for design because you want to build a solution that standardizes dimensions ensuring that the definition of that dimension is carried across applications
Of course there are times when a dimension may have different meanings to different units within an organization, but that usually identifies the need for additional attributes or hierarchies within that dimension
Users familiar with one application will have an easier time learning a new one with the same standard dimensions
Those dimensions that are common across applications can be created once and recycled for other applications
Workforce Planning includes the Employee dimension
Capex Planning includes the Asset Class and Line Items dimensions
These standard dimensions assist with providing out-of-the-box features such as pre-defined business rules and forms to streamline the build process
As we'll discuss, HFM requires that an application be deployed with all four of its custom dimensions
These dimensions offer expanded reporting capabilities required of an EPM application
At times loading more than one type of data to the same EPM application is justified and the use of custom dimensions allows for that to happen
Demo
Demonstrate how the dimensional design handles the different grains and scope of data across applications
Currency Dimension
Currently not used, but created a hook for currency to be used in the near future
BalanceSheetRoles Dimension
Support for security and auditing
Modeling Dimension
Utility dimension to support different attributes of data
In Workforce it supported the loading of bonus data and combo codes (job codes) in PS HR
In IncSt it supported additional reporting required for supply chain, marketing, and advertising
Demo
Use of User dimension
Track who makes changes, security designed around this dimension
Use of two entity dimensions
One supports the
Use of Restatement roll-up in the scenarios dimension
TotRst must equal Actual to ensure accuracy
A calc script is executed to derive the offsetting record stored in the RstFrom member
Blurb about presenting at Connection Point in Atlanta back in November
I had an hour and we went over, I have less time today and since it’s Friday, I don’t think we’ll be going over