03_Designing Data Descriptor Dimensions - Copy

3Copyright © 2011, Oracle and/or its affiliates. All rights reserved.

Designing Data Descriptor Dimensions

Copyright © 2011, Oracle and/or its affiliates. All rights reserved.

Objectives

After completing this lesson, you should be able to:

• Describe data descriptor dimensions

• Design time, scenario, and accounts dimensions

• Explain outline calculations

• Test outline calculations


Data Descriptor Dimensions Overview

• Define data in its essential form

• Are manually developed and maintained

• Incorporate variances (both value and percentage differences)

• Are calculation-intensive

• Are densely populated with data


Designing Time Dimensions

Decisions to make:

• Lowest level of data granularity– Depends on the type of analysis required– Can be very summarized (quarters) or very detailed (15-

minute intervals)

• Number of years to represent and representation method– Generic time designs– Fiscal year crossover designs


Tracking Time in Multiple Dimensions

A multidimensional time design requires at least two dimensions:

• A time dimension with generic time periods

• Discrete years represented in a scenario dimension or in a separate years dimension

Two-dimension design

Three-dimension design


Tracking Time in a Single Dimension

A single-dimension time design requires one of the following:

• Year-specific time periods

• Duplicate names

Year-specific time period


Quiz

Select the typical characteristics of data descriptor dimensions.

1. Calculation-intensive

2. Densely populated with data

3. Specialized perspectives of data

4. Manually developed and maintained


Quiz

A multidimensional time design is more efficient when time-based calculations cross the fiscal year end.

1. True

2. False


Designing Scenario Dimensions

Scenarios are the primary tool for variance analysis. They typically take one of two forms:

• Scenarios that track data sets

• Scenarios that track processes


Tracking Data Sets

Scenarios that track data sets:

• Are typical in financial applications

• Define the foundation of the planning and control process


Tracking Processes

Scenarios that track processes:

• Are typical in forecasting applications

• Define a single data set

• Track adjustments by distinct functional groups

Tracking month-end close Tracking sales forecasting


Outline Calculations

The database outline facilitates calculations two ways:

• Hierarchy structures

• Member formulas


Hierarchy Structures: Consolidation Operators

Consolidation operators define how child members Are consolidated to parents. Valid consolidation operatorsinclude:

• Addition (+)

• Subtraction (-)

• Multiplication (*)

• Division (/)

• Percent (%)

• Exclude from consolidation (~)

• Never consolidate (^)

Act Vs Bud = Current Year – Budget

Current Year (+)

Budget (-)

Act Vs Bud


Hierarchy Structures: Shared Members

• Do not store data

• Create a pointer to a stored member

• Are always level 0 members

• Are positioned after (below) the stored member in the outline

Scenario

Act Vs Bud

Current Year

Budget

Scenario Variances

Budget

(~)

(~)

(~)

(~)

SharedCurrent Year (+)

(-) Shared


Member Formulas

• Member formulas define calculations in the outline:

• Calculation script functions return sets of members or data values:


Quiz

Select the statements that are true about scenario dimensions.

1. Usually have many members and a complex hierarchy

2. Facilitate the comparison of data sets

3. Can be used to track processes

4. Are a required dimension


Quiz

Shared members require Essbase to store data for the original member and every shared instance of the member as well.

1. True

2. False


Designing Accounts Dimensions

Design choices are based on input data and sample reports:

• Profit and loss accounts, balance sheet accounts

• Units, rates, prices, and other assumptions

• Analysis metrics

Gross Margin = Net Sales – Cost of Sales

Gross Margin = Net Sales + Cost of Sales


Consolidation Order

• Consolidation order is defined by the order of members in the outline.

• Essbase calculates data in top-down order.

Parent

Member 4

Member 2

Member 1

Member 3

Member 7

Member 5

Member 6

(+)

(+)

(-)

(*)

(%)

(/)

(~)

10

20

25

40

50

60

70

30

5

200

400

25

40

50

60

6.67

6.67 Parent = ((((M1 + M2) – M3) * M4) % M5) / M6


Design Considerations

Net Sales

Discounts

Gross Sales

Units

List Price

Discount %

(-)

(+)

(*)

(+)

Gross Sales (+)

(*)

(+) Net Sales

Units * List PriceGross Sales (+)

Input Drivers (^)

Units (~)

Discounts (-) Gross Sales * Discount %

List Price (^)

Discount % (^)

(+)

1

3

2

3

1

2

Hierarchy calculation order Formula calculation order


Creating Accounts Hierarchies

Net Sales

Gross Sales (+)

Discounts (-)

(+)


Testing Outline Calculations

• Disable intelligent calculation• Set default calculation script• Follow standard test procedure

Calculation Testing Procedure

1. Clear all data from the database.

2. Load calculation test data.

3. Execute your calculation.

4. Audit your calculation results.


Intelligent Calculation

Only data blocks marked as changed are recalculated.


Setting the Default Database Calculation

• Default calculation string

• Optional default calculation script


Quiz

Select the correct calculation of a member with three childrenthat have the following consolidation operators: Child1: (+) Child2: (-) Child3: (*)

1. Child1 + Child2 * Child3

2. Child1 - (Child2 * Child3)

3. Child1 + Child2 - Child3

4. (Child1 - Child2) * Child3


Quiz

To optimize the performance of outline calculations, use hierarchy relationships and consolidation operators instead of formulas whenever possible.

1. True

2. False


Summary

In this lesson, you should have learned to:

• Describe data descriptor dimensions

• Design time, scenario, and accounts dimensions

• Explain outline calculations

• Test outline calculations

03_Designing Data Descriptor Dimensions - Copy

Documents

Transcript of 03_Designing Data Descriptor Dimensions - Copy