D53308

(1)

Hyperion Essbase Analytics 9.3.1

Bootcamp

Volume I • Student Guide

D52663GC10 Edition 1.0 December 2007 D53308 ® ®

(2)

Disclaimer

This document contains proprietary information and is protected by copyright and other intellectual property laws. You may copy and print this document solely for your own use in an Oracle training course. The document may not be modified or altered in any way. Except where your use constitutes "fair use" under copyright law, you may not use, share, download, upload, copy, print, display, perform, reproduce, publish, license, post, transmit, or distribute this document in whole or in part without the express authorization of Oracle.

The information contained in this document is subject to change without notice. If you find any problems in the document, please report them in writing to: Oracle University, 500 Oracle Parkway, Redwood Shores, California 94065 USA. This document is not warranted to be error-free.

Restricted Rights Notice

If this documentation is delivered to the United States Government or anyone using the documentation on behalf of the United States Government, the following notice is applicable:

U.S. GOVERNMENT RIGHTS

The U.S. Government’s rights to use, modify, reproduce, release, perform, display, or disclose these training materials are restricted by the terms of the applicable Oracle license agreement and/or the applicable U.S. Government contract.

Trademark Notice

Oracle is a registered trademark of Oracle Corporation and/or its affiliates. Other names may be trademarks of their respective owners.

Lisa Alexander Technical Contributors and Reviewers Steven Cranford Peter DeHaan Paul Hoch Michael Nader Sergiy Pecherskyy Graphic Designer Carisa Cannan Publisher Judy Gaitan

(3)

Preface

Course Objectives . . . xiii

Course Structure . . . xiii

Course Materials . . . xiv

Student Guide . . . xiv

Activity Guide . . . xiv

Conventions . . . xv

Additional Resources . . . xv

Future Courses . . . xvi

Module 1: Creating Databases

Lesson 1: Essbase Overview

Multidimensional Analysis . . . 1-2 Spreadsheet-Based Analysis. . . 1-3 Multidimensional View of Information . . . 1-5 Data Cubes . . . 1-7 Dimension Hierarchies. . . 1-8 Operations in Multidimensional Data Models. . . 1-9 Sparse and Dense Dimensions . . . .1-11 Oracle’s Enterprise Performance Management System . . . 1-12 Oracle Business Intelligence Suite Enterprise Edition Plus . . . 1-14 Hyperion Product Components . . . 1-15 Essbase . . . 1-17 Essbase Architecture . . . 1-18 Essbase Components . . . 1-19 Administration Services Console . . . 1-22 Production Environment Components . . . 1-24 Outlines . . . 1-26 Rules Files . . . 1-27 Calculation Scripts . . . 1-29 Smart View. . . 1-31 Essbase Spreadsheet Add-in . . . 1-32

(4)

Integration Services . . . 1-33

Lesson 2: Designing Applications and Databases

Block Storage Implementation Process . . . 2-2 Analyzing and Planning Implementations . . . 2-3 Identifying Business Results . . . 2-4 Examining Data Sources . . . 2-5 Analyzing Sample Reports. . . 2-6 Designing Block Storage Outlines . . . 2-7 Creating Applications and Databases . . . 2-9 Creating Block Storage Applications . . . 2-13 Creating Block Storage Databases . . . 2-15 Server File Structure . . . 2-17 Design Recommendations. . . 2-18 Creating Outline Structures . . . 2-20 Creating Dimensions and Members. . . 2-23 Moving Dimensions and Members. . . 2-25 Modifying Member Properties . . . 2-27

Lesson 3: Designing Data Descriptor Dimensions

Data Descriptor Dimensions Overview . . . 3-2 Designing Time Dimensions . . . 3-4 Generic Time Designs . . . 3-6 Fiscal Year Crossover Designs . . . 3-7 Designing Scenario Dimensions . . . 3-9 Tracking Data Sets. . . 3-10 Tracking Processes . . . 3-12 Outline Calculations . . . 3-13 Consolidation Operators . . . 3-14 Shared Members . . . 3-16 Member Formulas . . . 3-18 Designing Accounts Dimensions . . . 3-19 Consolidation Order . . . 3-21 Design Considerations. . . 3-23 Creating Accounts Hierarchies . . . 3-25

(5)

Table of Contents

Hyperion Essbase Analytics 9.3.1 Bootcamp v

Lesson 4: Optimizing Data Descriptor Dimensions

Creating Member Aliases. . . 4-2 Dimension Types . . . 4-4 Creating Period-to-Date Totals. . . 4-5 Creating Period-to-Date Calculated Members . . . 4-6 Implementing Dynamic Time Series . . . 4-8 Dynamic Calc Members. . . .4-11 Enhancing Accounts Dimensions . . . 4-13 Time Balance Reporting . . . 4-14 Expense Reporting . . . 4-16 Optimizing Data Storage . . . 4-18 Label Only Members . . . 4-19 Implied Shares . . . 4-21

Module 2: Building Rules Files

Lesson 5: Planning Dimension Designs

Business View Dimensions Overview . . . 5-2 Combining Business Views . . . 5-4 Planning Dimensions with Label Outlines . . . 5-8 Designing Primary Hierarchies . . . 5-10 Designing Secondary Hierarchies . . . .5-11

Lesson 6: Creating Basic Dimension Build Rules Files

Rules Files Overview . . . 6-2 Data Sources . . . 6-3 Dimension Build Rules Files . . . 6-4 Creating Dimension Build Rules Files . . . 6-6 Prepping Data Prep Editor (Steps 1–6) . . . 6-8 Creating Dimensions (Step 7) . . . 6-13 Selecting Dimension Build Method (Step 8). . . 6-15 Defining Field Properties (Step 9) . . . 6-17 Validating Dimension Build Rules Files (Step 10) . . . 6-20 Completing Dimension Build Rules Files (Steps 11 and 12) . . . 6-22 Configuring Dimension Maintenance Settings . . . 6-24 Moving Members . . . 6-25 Modifying Member Properties . . . 6-27

(6)

Sorting Members . . . 6-29 Updating Members. . . 6-31

Lesson 7: Creating Advanced Dimension Build Rules Files

Advanced Dimension Build Rules Files Overview . . . 7-2 Creating Shared Members. . . 7-3 Parent-Child Build Method . . . 7-4 Generation Build Method . . . 7-6 Level Build Method . . . 7-8 Manipulating Fields . . . 7-10 Arranging Fields. . . .7-11 Altering and Ignoring Fields . . . 7-14 Creating User-Defined Attributes . . . 7-16

Lesson 8: Creating Attribute Dimensions

Attribute Dimensions Overview . . . 8-2 Benefits . . . 8-3 Attribute Calculations Dimension . . . 8-5 Adding Attribute Dimensions to Outlines . . . 8-7 Associating Attribute Dimensions . . . 8-8 Assigning Attributes in Outline Editor. . . 8-10 Design Considerations. . . 8-12 Design Considerations: Database Size . . . 8-14 Design Considerations: Batch Calculation Performance . . . 8-15 Design Considerations: Report Layout . . . 8-16 Design Considerations: Report Performance . . . 8-19 Creating Attributes with Rules Files . . . 8-20 Adding Attribute Dimensions with Rules Files . . . 8-22 Assigning Attributes in Rules Files. . . 8-23

Lesson 9: Loading Data

Data Load Overview . . . 9-2 Free-form Data Sources . . . 9-4 Data Sources That Require Rules Files. . . 9-6

(7)

Table of Contents

Hyperion Essbase Analytics 9.3.1 Bootcamp vii Referencing Missing Dimensions (Step 8) . . . 9-15 Setting Data Load Values Options (Step 9) . . . 9-17 Validating Data Load Rules Files (Step 10) . . . 9-20 Completing Data Load Rules Files (Steps 11 and 12) . . . 9-21 Selecting and Rejecting Records. . . 9-23 Capturing New Members . . . 9-25

Module 3: Reporting with Smart View

Lesson 10: Getting Started with Smart View

Smart View Overview. . . 10-2 Smart View and Essbase Spreadsheet Add-in . . . 10-3 Smart View Architecture . . . 10-4 Smart View Toolbar . . . 10-5 Configuring Data Sources . . . 10-7 Configuring Provider Services . . . 10-8 Creating Essbase Database Connections . . . 10-10 Creating Essbase Database Connections (cont.) . . . 10-12 Retrieving Data . . . 10-13 Display of Multidimensional Data. . . 10-15 Label Placement Guidelines . . . 10-17 Setting the Point of View . . . 10-19 Selecting Dimension Members . . . 10-20 Filtering Dimension Member Selections . . . 10-22

Lesson 11: Creating Reports with Smart View

Manipulating Multidimensional Data . . . .11-2 Navigating Through Hierarchies . . . .11-4 Retaining and Removing Data Subsets . . . .11-6 Pivoting Data . . . .11-7 Updating Essbase Data . . . .11-9 Adjusting Data Values . . . .11-10 Submitting Data . . . .11-12 Calculating Data. . . .11-13 Integrating Essbase Data with Microsoft Office . . . .11-15 Copying Dynamic Data Points . . . .11-17 Creating Linked Views . . . .11-19

(8)

Module 4: Creating Basic Calculations

Lesson 12: Data Storage and Calculation

Calculation Overview . . . 12-2 Outline-Based Calculations . . . 12-4 Script-Based Calculations . . . 12-5 Calculation Script Editor. . . 12-8 Database Calculation Order. . . 12-9 Data Block Fundamentals . . . .12-11 Data Blocks and the Index System . . . 12-12 Data Cells . . . 12-14 Dense Dimensions. . . 12-16 Sparse Dimensions . . . 12-18 Database Statistics . . . 12-20 Dimension Properties. . . 12-21 Block Statistics . . . 12-22 Data Block Creation . . . 12-24 Data Load . . . 12-25 DATACOPY Command . . . 12-26 Sparse Dimension Consolidation . . . 12-27 Member Formulas . . . 12-28 Database Calculation Process. . . 12-29 Input Data Load . . . 12-30 Dense Dimension Calculation Process: Accounts . . . 12-31 Dense Dimension Calculation Process: Time . . . 12-32 Sparse Dimension Calculation Process: Customer . . . 12-33 Sparse Dimension Calculation Process: Product. . . 12-35

Lesson 13: Creating Calculation Scripts

Calculation Script Organization . . . 13-2 Information Section . . . 13-6 Housekeeping Section . . . 13-8 Baseline Fix Section . . . 13-10 Normalization Section . . . 13-12 Main Rollup Section . . . 13-14

(9)

Table of Contents

Hyperion Essbase Analytics 9.3.1 Bootcamp ix Correcting Calculated Percentages . . . 13-19 Design Considerations for Rates . . . 13-22 Preventing Consolidation of Rates. . . 13-24 Correcting Derived Rates. . . 13-25 Correcting Input Rates . . . 13-26 Troubleshooting CALC DIM Processes . . . 13-28 Viewing Calculation Messages . . . 13-29 Single-Pass Calculation with Incorrect Results . . . 13-31 Multiple-Pass Calculation with Correct Results . . . 13-33

Lesson 14: Controlling the Calculation Process

Top-Down Calculation . . . 14-2 Focusing Calculations with FIX Statements. . . 14-4 Calculating Conditionally with IF Statements . . . 14-7 Boolean Functions . . . 14-9 Syntax Requirements. . . .14-11 Comparing FIX and IF Calculation Processes . . . 14-13 Number of Data Blocks Processed . . . 14-14 Number of Calculation Passes. . . 14-16

Lesson 15: Referencing Members in Calculations

Referencing Members Explicitly. . . 15-2 Referencing Members Dynamically . . . 15-4 Referencing Sets of Members . . . 15-6 Referencing Related Members . . . 15-8 Creating Calculation Variables. . . 15-10 Creating Temporary Variables . . . .15-11 Creating Substitution Variables . . . 15-14

Module 5: Appendices

Appendix A: Creating Advanced Calculations

Script Development Process . . . A-2 Calculation Test Cycle . . . A-4 Prototype Phase . . . A-6 Pilot Phase. . . A-9 Upper-Level Data Loads . . . A-13

(10)

Aggregating Missing Values. . . A-14 Loading to Leaf Nodes. . . A-19 Intelligent Calculation. . . A-22 Data Block Marking: Clean Blocks. . . A-24 Data Block Marking: Dirty Blocks. . . A-27 Usage Considerations . . . A-29 Allocating Data. . . A-31 Calculating Fixed Rate Allocations . . . A-32 Calculating Dynamic Ratio Allocations . . . A-34 Normalization . . . A-36 Partitioning Calculations by Scenario . . . A-38 Developing Normalization Tables. . . A-40 Developing Block Diagrams. . . A-43 Normalizing Rates and Drivers . . . A-45 Copying and Clearing Data . . . A-47 Copying Data . . . A-48 Clearing Data with CLEARDATA . . . A-50 Clearing Data with CLEARBLOCK . . . A-52

Appendix B: Creating Reports with Essbase Spreadsheet Add-in

Essbase Spreadsheet Add-in Overview. . . B-2 Installing the Essbase Menu and Toolbar . . . B-3 Managing Database Connections . . . B-5 Retrieving Data . . . B-7 Representing Multidimensional Data in Two-Dimensional Reports . . . B-9 Label Scanning . . . B-11 Manipulating Multidimensional Data . . . B-13 Navigating Data . . . B-15 Retaining and Removing Data Subsets . . . B-17 Pivoting Data . . . B-19 Managing Worksheet Options . . . B-20 Global Options . . . B-21 Zoom Options . . . B-23 Style Options . . . B-25 Display Options . . . B-27 Preserving Excel Formulas . . . B-29

(11)

Table of Contents

Hyperion Essbase Analytics 9.3.1 Bootcamp xi Selecting Members from the Outline . . . B-35 Defining Selection Rules . . . B-37 Applying Additional Rules . . . B-39 Creating Savable Queries . . . B-41 Query Designer Interface. . . B-42 Creating Basic Queries . . . B-43 Creating Advanced Queries. . . B-44 Filtering Data . . . B-45 Sorting Data . . . B-47 Retrieving with Report Scripts . . . B-48

Appendix C: Working with Duplicate Member Names

Creating Duplicate Member Outlines . . . C-2 Qualifying Duplicate Member Names . . . C-4 Creating Members with Duplicate Names . . . C-6 Loading Data to Duplicate Members . . . C-8 Viewing Duplicate Names in Smart View. . . C-10 Viewing Duplicate Names in Essbase Spreadsheet Add-in. . . C-12

(12)

(13)

Preface

0

Welcome to Hyperion Essbase Analytics 9.3.1 Bootcamp!

Before you begin, please take a moment to review this section. The preface presents an overview of the following information:

• Course objectives • Structure of the course

• Course materials used in the class • Conventions used in the book

• Additional resources to enhance your learning

• Relevant follow-up courses that you might want to attend in the future

Course Objectives

After completing this course, you should be able to: • Create block storage databases

• Build rules files for dimension build and data load • Analyze data using Smart View

• Create basic calculation scripts

Course Structure

Hyperion Essbase Analytics 9.3.1 Bootcamp is a 5-day, instructor-led training course consisting of lectures, demonstrations, and hands-on exercises. In this course, the instructor presents a topic conceptually by explaining its purpose, demonstrating how it works, and then guiding the students through the exercises. Demonstrations and hands-on exercises reinforce the concepts and skills introduced during lectures.

(14)

Course Materials

You use two books in class—the student guide and the activity guide. The instructor may also give you handouts.

Student Guide

The student guide is designed to be used by students and the instructor during lecture time. It has 5modules:

• Module 1 describes creating Essbase databases.

• Module 2 describes building rules files for dimension building and data loading. • Module 3 describes reporting in Microsoft Excel with Smart View.

• Module 4 describes block data storage and creating basic calculation scripts. • Module 5 contains appendices to provide information about additional features of

Essbase not covered in this course.

Each module contains lessons. Each lesson begins with a list of objectives followed by the presentation of slides and accompanying text. The lesson ends with a summary of the topics covered in the lesson.

Activity Guide

The activity guide has four sections—exercises, exercise solutions, and two separate case studies

Exercises

A critical part of the learning process is the challenge of completing real tasks associated with each lesson. Each exercise is an opportunity to apply your new knowledge.

Exercise Solutions

The exercise solutions present the detailed steps to successfully complete the exercises. Case Studies

The case studies present less structured business scenarios than the exercises,

enabling you to synthesize your new knowledge in an innovative way. Thus, you practice problems-solving with your newly-acquired skills.

(15)

Preface

Hyperion Essbase Analytics 9.3.1 Bootcamp xv

Conventions

The following text conventions are used in this course book:

• Text to be typed, options to be selected, names of files and modules, and menu selections are displayed in bold type. Examples:

- Select Clear Profile.

- Click YES to clear the profile.

• When available, figures are used to identify an object or task. Example: Click Edit.

• Keyboard shortcuts are displayed as follows: Ctrl+Enter

• Alerts are used to direct your attention to different types of information.

Additional Resources

Use the following resources to enhance your learning:

• Hyperion Essbase 9.3.1 Database Administrator’s Guide • Smart View for Office User’s Guide

• Essbase Spreadsheet Add-in User’s Guide for Excel • Hyperion Developer Network (http://dev.hyperion.com)

N O T E

A note provides related information, common mistakes, or cautions about the current topic.

T I P

A tip provides information that helps you work more efficiently.

(16)

Future Courses

The following list presents relevant courses that can be taken after you complete this course.

• Hyperion Essbase Analytics 9.3.1 Calculate Databases

• Hyperion Integration Services 9.3.1: Create and Manage Data Structures • Hyperion Essbase 9.3.1: Deploy Aggregate Storage Databases

• Hyperion Essbase 9.3.1. for System Administrators • Hyperion Smart View 9.3.1 for Essbase

N O T E

Course names and learner paths may change.

Visit http://www.oracle.com/global/us/education/hyperion_select_country.html for the latest information.

(17)

M O D U L E 1

Creating Databases

0

Overview

This module provides an overview of OLAP concepts and the Essbase platform, introduces the primary user interfaces, and teaches basic

dimension design concepts. Based on a given business scenario, you learn how to create applications, databases, and outlines.

Lessons in this module include: • Essbase Overview

• Designing Applications and Databases • Designing Data Descriptor Dimensions • Optimizing Data Descriptor Dimensions

(18)

(19)

L E S S O N 1

Essbase Overview

1

Objectives

At the end of this lesson, you should be able to: • Describe multidimensional analysis

• Describe Oracle's Enterprise Performance Management System • Describe Essbase

(20)

Lesson 1 Essbase Overview

Multidimensional Analysis

Information is one of the most important assets of a business. Corporate information analysis offers a road map for strategic planning and enables executive managers to make informed and timely decisions.

Information analysis provides insight to the past, present, and future of your business; an understanding of past performance helps you address current concerns, which in turn helps you plan for future growth. To gain business intelligence, you must analyze data from many perspectives. For example, it is not enough to know the sales totals for a month, you must know which customers bought the most and which products sold the least.

Multidimensional Analysis

Analysis of data from multiple perspectives

January Gross Sales for All Products and All

Customers in the Current Year

(21)

Module 1 Creating Databases

Hyperion Essbase Analytics 9.3.1 Bootcamp 1-3

Spreadsheet-Based Analysis

Most businesses have many transactional systems that contain huge numbers of daily transactions. These fragmented systems force companies, most commonly using

spreadsheet programs, to spend too much time analyzing disconnected environments. In such environments, spreadsheet programs are extremely cumbersome, if not

unworkable, analysis tools; file corruption, user errors, and lack of data synchronization across disparate systems often lead to multiple versions of one truth. Businesses expend their resources developing multiple spreadsheets to answer multidimensional questions and then waste substantial time and manpower trying to validate reports against each other.

Spreadsheet-Based Analysis

Data integrity suffers because of user errors or stale data.

Validating spreadsheet reports wastes time and resources.

Two reports prepared by two users show two different totals. Which one is correct?

(22)

Legislation and other statutory reporting requirements place enormous pressure on companies to report with absolute accuracy, and, at the same time, the use of spreadsheet programs for data analysis is a requirement for most businesses.

Therefore, organizations require one system that not only satisfies their global reporting requirements but also provides the multidimensional spreadsheet-based analysis that executives need to make fast, accurate decisions. Essbase was created with these issues in mind; in fact, Essbase stands for extended spreadsheet database.

(23)

Multidimensional View of Information

Enterprise strategic information is structured around natural business concepts and can be visually represented as a multidimensional array. You can view data from different perspectives, depending on analytic needs.

OLAP

The term OLAP (online analytical processing) describes analysis tools that provide fast multidimensional analysis of information, enabling businesses to turn the wealth of data generated by transactional applications into usable business intelligence.

(24)

Lesson 1 Essbase Overview Benefits of Using OLAP

OLAP supports the natural tendency of users to view business results as facts organized by various dimensions. Implemented in a multiple-user, client-server multi-tier

environment, OLAP helps you synthesize enterprise strategic information through comparative, personalized viewing and analysis of historical and projected data. Essbase databases are OLAP databases.

(25)

Data Cubes

A data cube is a multidimensional extension of a two-dimensional table, just as a geometrical cube is a three-dimensional extension of a square.

A data cube is a multidimensional matrix that facilitates analysis from many perspectives. You can visualize a three-dimensional data cube as a spreadsheet program workbook that includes identically structured spreadsheets (each representing two dimensions) on multiple uniquely-named tabs (representing the third dimension). Each tab represents a data set that is contained within the structure of the spreadsheets.

Although data cubes are not restricted to three dimensions, visualizing dimensional cubes of more than three dimensions in spatial or geometrical terms is difficult. For analysis purposes, you usually view details for only two or three dimensions at a time, while the data cube is indexed along the remaining dimensions.

Data Cubes

Analysts prefer to view multidimensional data in cubes, rather than in relational tables.

Cube is a metaphor for multidimensional data storage.

Data is analyzed along only two to three dimensions at a time.

Sales Time Product 149 February Thunderball 131 January Thunderball 182 February Lightbolt 166 January Lightbolt 149 182 February 131 Thunderball 166 Lightbolt January

Relational table Data cube

1 measure: Sales

(26)

Dimension Hierarchies

in a multidimensional data model, the structural relationships between members within a dimension define the dimension hierarchy. A typical dimension consists of one or more members that in turn may consist of other members. For example, one possible

hierarchy in a time dimension is Year > Quarter > Month > Day. Hierarchies also define relationships that end users see during analytic operations.

N O T E

Members that consist of other members define consolidation levels in the dimension hierarchy.

Dimension Hierarchies

You can organize the members of each dimension in a hierarchy.

Year Tot Quarter 2 April Product Lightbolt Thunderball Value Mavrider Customer OEM IBM Retail Apple Gateway Performance Quarter 1 January February March

(27)

Operations in Multidimensional Data Models

The multidimensional data model supports the following cube operations: Slicing and Dicing

A dimension acts as an index for identifying values in the multidimensional array. Slicing and dicing are operations that select data from the data cube. In slicing, you select one member from all but two dimensions, and the remaining dimensions define a two-dimensional slice of the data cube. In dicing, you select a range of members from more than two dimensions, and the selection defines a multidimensional subcube.

Operations in Multidimensional Data Models

Selection (slice and dice)

Aggregation (roll up)

Navigation to more detailed data (drill down)

Visualization operations (pivot)

Sales to retail customers during January and February by product

Total sales by product

Supporting data for sales for retail customers during Qtr 1

Reorientation of the data cube

Display of a three-dimensional data cube in a series of two-dimensional planes

(28)

Lesson 1 Essbase Overview Rolling Up and Drilling Down

You can roll up (summarize the data cube) by traversing upward through the dimension hierarchy. As values are combined, cardinalities shrink, and the cube view becomes smaller. Drilling down is the reverse of rolling up. You traverse from summarized data to detailed data. To incorporate more detail into your analysis, you can drill down a

dimension hierarchy or add another dimension to your analysis. Pivoting

By rotating the data cube, you can view analytic data from multiple perspectives. You typically pivot to build a custom, two-dimensional analytic report.

(29)

Sparse and Dense Dimensions

The data sets of most multidimensional data models have two characteristics: • Data is not smoothly and uniformly distributed.

• Data does not exist for the majority of member combinations. For example, all products are not sold in all areas of the country.

Most multidimensional data sets are inherently sparse: they lack data values for the majority of member combinations. A sparse dimension is a dimension with a low percentage of available data positions filled.

Some dimensions in a multidimensional data model may be denser than others. A dense dimension is a dimension with a high percentage of available data positions filled.

Sparse and Dense Dimensions

Multidimensional data sets tend to be sparse:

Data is not uniformly distributed.

Data does not exist for the majority of member combinations.

Certain aspects of multidimensional data sets tend to be predictably sparser than others.

500 Measures 5 Years 2 Scenarios 1000 Customers 1000 Products 300 Regions 17 Time Periods Members

Dimension _{Possible member combinations: 25.5 trillion}

(30)

Oracle’s Enterprise Performance Management System

Oracle Business Intelligence (BI) is a portfolio of technology and applications that

provides the industry's first integrated, end-to-end Enterprise Performance Management (EPM) system, including category-leading financial performance management

applications, operational BI applications, BI foundation and tools, and data warehousing. It is pervasive, comprehensive, and hot-pluggable:

• Pervasive—Delivers intuitive, role-based intelligence for everyone in an organization from front line employees to senior management to enable better decisions, actions, and business processes. There is a common workspace and a range of real-time and event-based capabilities. It also covers all styles of reporting and analysis needs.

Oracle’s Enterprise Performance Management

System

(31)

Hyperion Essbase Analytics 9.3.1 Bootcamp 1-13 • Hot-Pluggable—Uses your existing transaction systems, databases, and

middleware applications. Oracle BI products are hot-pluggable with Oracle and non-Oracle environments.

(32)

Oracle Business Intelligence Suite Enterprise Edition Plus

Oracle Business Intelligence Suite Enterprise Edition Plus (Oracle BI EE Plus) is a comprehensive suite of enterprise BI products that delivers a full range of analysis and reporting capabilities. Featuring a unified, highly scalable, modern architecture,

Oracle BI EE Plus provides intelligence and analytics from data spanning enterprise sources and applications—empowering the largest communities with complete and relevant insight.

Oracle BI EE Plus bundles key Oracle Hyperion reporting products for integrated reporting with Oracle’s Hyperion financial applications.

Oracle Business Intelligence Suite Enterprise

Edition Plus

(33)

Hyperion Product Components

Oracle BI Suite Enterprise Edition Plus is a combination of Oracle BI Suite Enterprise Edition and Hyperion product components.

Primary components of Hyperion products:

• Financial Performance Management Applications—A modular suite of integrated applications that support the entire financial management cycle of goal-setting, modeling, planning, monitoring, analysis, and reporting

• Essbase—The business analysis server technology that provides an environment for rapidly developing custom analytic and enterprise performance management applications

• Reporting and Analysis—A suite of tools that enable you to create analytical, financial, and production reports as well as dashboards

Hyperion Product Components

Workspace

Data Management

Data Relationship Management Data Integration Management Financial Data Quality Management

Performance Scorecard Financial Management

Strategic Finance Financial Performance Management Applications

Planning Shared Services Foundation Services Smart View Interactive Reporting SQR Production Reporting Financial Reporting Web Analysis

Reporting and Analysis Essbase

Essbase Administration Services

Provider Services Integration Services

(34)

• Data Management—A packaged solution that enables organizations to integrate disparate sources of data across an enterprise, map data, and manage change • Foundation Services—A single, standardized infrastructure that facilitates the

deployment of Hyperion product solutions and simplifies ongoing maintenance • Workspace—The Web client for Reporting and Analysis, Planning, and Financial

Management. It enables you to access and interact with Hyperion-authored content as well as third-party documents, such as Microsoft Word and Excel files

(35)

Essbase

Most traditional database products are application specific, and the proliferation of application-specific packages results in multiple support for training and development. With Essbase as an application development environment, you can use one tool to build multiple databases. Individual applications are better integrated with each other. Only one environment needs to be supported for development, deployment, and training. Essbase enables the quick and easy implementation of analytic solutions, adds value to previously inaccessible data, and transforms data into actionable information.

(36)

Essbase Architecture

The Essbase product family incorporates powerful architectural features to handle a wide range of analytic applications across large multi-user environments. The slide diagram provides a high-level view of the integrated information flow between the source data and the product components.

(37)

Essbase Components

Essbase is a multidimensional database software optimized for planning, analysis, and management-reporting applications. Essbase offers aggregate storage databases for operational analysis and block storage databases for financial analysis.

Essbase uniquely blends an innovative technical design with an open, multi-tier architecture. The product enables you to extend decision support systems beyond ad hoc queries and reports on historical performance to dynamic, operational systems that combine historical analysis and future planning. Essbase enables you and others in the organization to share, access, update, and analyze enterprise data from any perspective and at any level of detail without learning new tools, query languages, or programming skills.

Block storage databases: Block storage databases support dense data sets, interactive user write-back, and complex financial analytics.

Essbase Components

Essbase: — Block storage — Aggregate storage — Administration Services — Smart View

— Essbase Spreadsheet Add-in

— MaxL

— ESSCMD

— MDX

— C API, VB API, and Java API

Additional components:

(38)

Aggregate storage databases: Aggregate storage databases drive operational analytics and are optimized specifically for high dimensionality, extreme sparsity of data, and dimensions with millions of members.

Administration Services: This database and system administrators' interface to Essbase provides a single-point-of-access console to multiple instances of Essbase Server. Using Administration Services Console, you can design, develop, maintain, and manage multiple instances of Essbase Server and multiple applications and databases. You can preview data from within the console, without having to open a client application such as Essbase Spreadsheet Add-in. You can also use custom Java plug-ins to

leverage and extend key functionality.

Integration Services: Integration Services provides a metadata-driven environment to bridge the gap between data stored in Essbase databases and transactional data stored in relational databases. Integration Server drill-though enables business users to view linked transactional data from Essbase reports. The Hybrid Analysis feature gives business users more detail for decision-making and information technology (IT) managers more modularity in designing and maintaining large-scale analytic applications.

Essbase Spreadsheet Add-in: This software program merges seamlessly with Excel. Using Essbase Spreadsheet Add-in, you can access instances of Essbase Server and perform ad hoc reporting on Essbase databases.

Smart View for Office: This software program provides a single Microsoft Office interface for multiple Oracle Hyperion products. Using Smart View , you can perform many of the same functions as Essbase Spreadsheet Add-in and also integrate live content from Oracle’s Hyperion Essbase, Planning, Financial Management, and various reporting and analysis tools into Microsoft Office programs.

ESSCMD: This command-line language performs server operations interactively or through batch or script files. ESSCMD is a legacy language and will not be enhanced for new features in future releases.

MaxL: This practical, expressive interface for administering the Essbase system is one of the two functional domains of the multidimensional database access language for Essbase. With MaxL Data Definition Language (DDL), you use statements to make requests; MaxL DDL statements usually begin with verbs and read like English

sentences. MaxL DDL improves on ESSCMD in that you can make it interact with the operating system by issuing shell commands and you can embed it in Perl programs by

(39)

Hyperion Essbase Analytics 9.3.1 Bootcamp 1-21 MDX: This multidimensional query language is the second of the two MaxL functional domains. MDX provides the ability to perform advanced data extraction and querying by means of statements that typically include the verb SELECT. You use MDX to construct member formulas in aggregate storage databases.

Essbase API: This developers' interface to Essbase enables you to create customized applications in either VB, C, or Java programming languages.

(40)

Administration Services Console

Administration Services Console is the common administration interface for Essbase. Database and system administrators use it to manage users and user security, server options, Essbase applications and databases, and database objects. The interface relies on context-sensitive, right-click shortcut menus to perform most actions and is organized into three frames: the navigation panel, object window, and message panel.

Navigation Panel

When you start Administration Services Console, the default navigation tab, Enterprise View, is displayed. Enterprise View is a graphical hierarchy view of the Essbase

environment. You can expand a node on the Enterprise View hierarchy by clicking the plus sign (+) next to an object. If you double-click an object, it opens in the object

Administration Services Console

Database and system administrators’ interface

Navigation

panel _Object

window

Message panel

(41)

Hyperion Essbase Analytics 9.3.1 Bootcamp 1-23 You can create custom views for specific servers, applications, or databases to reduce the number of mouse clicks required to navigate to an object in Enterprise View.

Object Window

This workspace is where objects are displayed after you open them. Administration Services Console is a multi-window environment, so every object that you open stays open in the object window until you close the object. You can tile objects inside the object window or switch between objects by using the Organize menu options. Object toolbars are displayed inside their respective objects. The main toolbar displays shortcuts, for example, for opening and saving files.

Message Panel

The message panel displays system information messages. When you check the formula syntax of an outline member formula, verification errors are displayed in the message panel.

N O T E

(42)

Production Environment Components

The block storage database production environment is comprised of three principal database objects for creating and managing your databases. Essbase also provides two interfaces for viewing and analyzing data in Excel.

The process of creating a production database, at its most basic level, demonstrates the relationships among components:

1. Create a database outline, defining database dimensions and hierarchies. 2. Load data, using rules files to map to the database dimensions.

3. Calculate data, using calculation scripts.

4. Analyze calculated data in Excel, using either Essbase Spreadsheet Add-in or Smart

Production Environment Components

Database objects

— Outline (.OTL)

— Rules files (.RUL)

— Calculation scripts (.CSC)

Data analysis interfaces

— Smart View

— Essbase Spreadsheet Add-in

(43)

Hyperion Essbase Analytics 9.3.1 Bootcamp 1-25 5. Alternatively, for an approach that is more integrated with your source data, use

Integration Services to create outlines and load data, and to support transactional-level detail in your reporting and analysis

(44)

Outlines

The database outline plays the key role in the life cycle of Essbase database design. Database development begins with creating a database outline.

The outline defines the database dimension hierarchy that describes the structural relationships between members within dimensions. The tree structure of the outline enables you to define consolidations between members. For example, a dimension represents the highest consolidation level in the database outline.

To create and modify the database outline, you use Outline Editor in Administration Services Console.

Outlines

Tree structure for dimension hierarchies

Consolidations and mathematical relationships between members

(45)

Rules Files

Loading data with rules files enables you to deal with unstructured data sources. You can load data manually or use MaxL to load data in a batch production environment. There are no fundamental restrictions on the size of data source files or on the number of records that can be loaded using rules files.

If a data source does not map perfectly to your database outline, you must format your data source during the data load process by applying data load rules. For example, you may want to process data in any of the following ways:

• Ignore certain fields or records in the data source

• Manage header information, such as ignoring extraneous headers or setting up special purpose headers for label identification

• Change the order of fields by moving, joining, splitting, or creating fields

Rules Files

Map data sources to a target Essbase database

Can apply to many data sources

Can load data and build outlines

Fields mapped to dimensions Header mapped to units Ignored field CustID-removed

(46)

• Resolve problems of member uniqueness by replacing member names with valid values

• Scale data values

• Overwrite loaded or calculated values

• Update unrecognized new members without creating error conditions • Set header records for missing data values

• Reject invalid records and continue the data load

Rules files contain a set of operations that Essbase performs on data when it loads the associated data source into the database. Rules act on data as it is loaded, without changing the data source. You can use a rules file with any data source that requires its set of data loading rules.

(47)

Calculation Scripts

A calculation script contains a series of calculation commands, equations, and formulas. You can use a calculation scripts in block storage databases to define calculations other than the calculations defined by the database outline.

You can use a calculation script to specify exactly how you want Essbase to calculate a database. For example, you can calculate part of a database or copy data values between members or define calculations other than the calculations defined by the database outline.

You can design and run custom database calculations quickly by separating calculation logic from the database outline.

Calculation Scripts

Calculate all or a portion of the database

Control the order in which dimensions are calculated

Perform complex calculations

Level 0 data

Calculated database

(48)

The following calculation script calculates only Actual values. FIX (Actual)

CALC DIM(Year, Measures, Market, Product); ENDFIX

The following calculation script is an example of a conditional calculation: SET UPDATECALC OFF;

COGS ( IF (@ISMBR(Forecast)) COGS = Sales*.25; ENDIF ) CALC ALL;

(49)

Smart View

Smart View is a Web-deployed, thin-client software program that is embedded in a client spreadsheet application. Smart View and Essbase Spreadsheet Add-in provide similar Excel functionality for Essbase: retrieving and analyzing data and creating ad hoc reports. However, Smart View offers an intuitive user interface and toolbar, provides a single Excel interface for Essbase, Planning, and Financial Management, and provides integration of content from Essbase, Planning, Financial Management and Oracle Hyperion reporting and analysis tools with other Microsoft Office products, such as Word and PowerPoint.

N O T E

Although Smart View provides connectivity for Planning and Financial

Management applications (versions prior to Release 9), Smart View is supported only for Essbase Release 9 and higher.

(50)

Essbase Spreadsheet Add-in

Essbase Spreadsheet Add-in is a software program that merges seamlessly with Excel. It enables you to use your spreadsheet application to interface with multiple instances of Essbase Server. With Essbase Spreadsheet Add-in loaded, you can retrieve data, create reports, and analyze data. You can also navigate, format, edit, and calculate data, as well as create customized settings to view data in particular formats.

After Essbase Spreadsheet Add-in is installed, a menu, toolbar, and keyboard shortcuts are added to the spreadsheet application. These added controls provide enhanced commands such as connect, pivot, drill down, and calculate. You can access and analyze data in Essbase databases by using mouse clicks and drag-and-drop operations.

Essbase Spreadsheet Add-in

Is a software program that is embedded in a client spreadsheet application

Enables you to retrieve data, create ad hoc reports, and analyze data

Provides an interface with Essbase Server

Excel with Essbase

Spreadsheet Add-in Essbase Server Essbase database

(51)

Integration Services

As an alternative to building outlines and rules files natively in Essbase, you can create metaoutlines and data loads in Integration Services, based directly on information in external data sources.

Integration Services is a suite of graphical tools and scalable data integration services that dramatically reduce the time required to create, deploy, and manage tailored applications. Integration Services provides a vital link between tailor-made applications built on the Essbase platform and detailed data stored in relational databases.

A centralized OLAP metadata repository simplifies application administration; promotes reusability of dimensions, calculations, and business rules; and facilitates delivery of business-focused applications. Built on a flexible, multi-tier architecture, Integration Services easily scales to accommodate changing requirements and delivers scalability, performance, and reliability.

(52)

Summary

In this lesson, you should have learned to: • Describe multidimensional analysis

• Describe Oracle's Enterprise Performance Management System • Describe Essbase

(53)

L E S S O N 2

Designing Applications and Databases

2

Objectives

At the end of this lesson, you should be able to:

• Describe the block storage database design process • Analyze and plan an implementation

• Create block storage applications and databases • Create block storage outlines

(54)

Lesson 2 Designing Applications and Databases

Block Storage Implementation Process

A block storage database implementation includes many steps. The block storage implementation process is a set of guidelines and suggested steps for planning, creating, and deploying block storage databases.

The process is iterative. Analysis of the results of one cycle may stimulate new questions, leading to newly defined business information requirements. New requirements may lead to new designs and implementations of the process.

Block Storage Implementation Process

1. Identify business results

2. Examine data sources

3. Analyze sample reports

4. Desig n block storage outlines Analysis and Planning

Database Creation

Deployment and Support

5.Create block storage outlines

6.Create rules files

7.Create calculation scripts

8.Maintain block storage outlines

9.Manage data flow

10.Analyze data

(55)

Analyzing and Planning Implementations

The design and operation of an Essbase multidimensional database plays a key role in creating a well-tuned system that enables you to analyze business information efficiently. Given the size and performance volatility of multidimensional databases, developing an optimized database is critical. A detailed plan that outlines data sources, user needs, and prospective database elements can save you development and implementation time. During the analysis and planning phase of implementation, three information-gathering steps lead to the fourth step: synthesizing the information into a working design.

Analyzing and Planning Implementations

Identifying business results

— Create preliminary user analysis

— Identify all participants

— Identify IT requirements

— Document current processes

Examining data sources

— Identify all source systems

— Develop data extract strategies

Analyzing sample reports

— Conduct extensive user requirement surveys

— Rate survey results to determine essentials

Designing block storage outlines

— Define dimensions, hierarchies, and attributes

(56)

Identifying Business Results

This step of the implementation process sets the groundwork for everything that follows. In it, you must identify all participants in the implementation process and establish the responsibilities, deadlines, and project scope of each group of participants. This is a prime opportunity to conduct preliminary user and hardware surveys and document current data processes.

Use this step to determine the scope of the database. If your organization has thousands of product families containing hundreds of thousands of products, you may want to store data values only for product families. Interview members from each user department to find out what data they process, how they process data today, and how they want to process data in the future.

Identifying Business Results

A user analysis survey asks the following questions:

Who will use the completed cube?

How are users analyzing data now?

What type of analysis is required from the completed cube?

(57)

Examining Data Sources

An information technology (IT) task force is typically responsible for the majority of the data examination step, in which all source data systems must be identified and data extract strategies must be developed.

Examine the current data:

• Where does each department currently store data? Do departments store data in a DB2 database on an IBM mainframe, in a relational database on a UNIX-based server, or in a PC-based database or spreadsheet?

• Is data in a form that Essbase can use?

• Who updates the database, and how frequently is the database updated? • Can individuals who need to update data access the data?

(58)

Analyzing Sample Reports

Data source analysis provides you with information about data in its raw form, but

analysis of sample reports (that is, reports that users want to create using Essbase data) provides a crucial look at the final requirements and architecture of the database.

Given a set of sample reports, a design team can determine how many database

dimensions are required, how much detail should be included, and what kind of hierarchy relationships are required to provide users with the details that they need.

During this step of the implementation, a design team makes decisions about which features and attributes are necessary and which features and attributes are desirable. Finalizing a feature-attribute list helps set expectations for the final design and for the end users. This step ensures a database design with usable results.

Analyzing Sample Reports

Sample reports:

Represent both ad hoc and production-style reports

Provide insight to the number, type, and granularity of dimensions

Ensure a database design with usable results

(59)

Designing Block Storage Outlines

Outline design is a synthesis of all previously gathered research. In the outline design step, you make the final decisions about the number of dimensions, the depth and nature of outline hierarchies, and the database calculation requirements.

The design team documents the preliminary outline design on paper, clearly defining the following information:

• Number of dimensions • Structure of hierarchies • Database time span

• Functional scenarios to be stored • Data storage settings

• Mathematical requirements for measures data

Designing Block Storage Outlines

Number of dimensions

Dimension hierarchies

Metadata granularity

Database time span

(60)

A design document also usually includes the process and frequency for updates to both data and metadata (outline structures), as well as the process for automating and

(61)

Creating Applications and Databases

Block storage applications and databases provide Essbase with a structure for organizing processes and related files.

Applications

A block storage application is a management structure that contains one or more block storage databases and related files. Block storage applications reside on the server where Essbase Server is installed. One server can store multiple block storage applications.

The main Essbase Server (ESSBASE) process, also called the Essbase Server agent, handles user logins and security and acts as a traffic controller for all other server requests.

(62)

Block storage applications run as an ESSSVR process controlled by the Essbase Server agent. When you start Essbase applications, the Essbase Server agent loads it and all associated databases into memory on the server computer. All client requests for data, such as data loads, calculations, reports, and spreadsheet lock and sends, are then handled through the application ESSSVR process. Multiple application processes can be run concurrently by one Essbase Server agent; in Windows, a command window is opened for each ESSSVR process that is running. If a block storage application contains multiple databases, all requests to the databases are managed by the same ESSSVR process.

When you stop the application process, the Essbase Server agent unloads all application information and databases from its memory and closes the application ESSSVR

process.

Application Design Choices

When you create an application, you need to make the following design decisions: • Create a block storage or aggregate storage application

• Create a Unicode-mode or non-Unicode-mode application

Block storage or aggregate storage: You need to decide to use block storage or aggregate storage when you create an application. In general, you choose block storage applications when creating models for financial data and aggregate storage applications when creating models for operational data. You can use the following rules as general guidelines:

T I P

You may want to start an application process before users connect to the

application databases; if you do so, users may experience improved performance when they connect to databases because the application and all associated databases are in memory. Try to manage your server resources by starting only the application processes that receive heavy user traffic.

If you... Then choose...

Have a large number of base dimensions (more than 10) Aggregate storage Have an extremely small batch calculation window or many

(63)

Hyperion Essbase Analytics 9.3.1 Bootcamp 2-11 Unicode: Unicode Standard was developed to enable computers with different locales to share character data. Unicode provides encoding forms with thousands of bit

combinations, enough to support the character sets of multiple languages

simultaneously. An application is either a Unicode-mode application or a non-Unicode-mode application. When choosing between Unicode and non-Unicode, keep the following in mind:

• Non-Unicode-mode applications support only one character set, which is defined by a locale value. The value for the server where Essbase Server is installed must match the value for all clients that work with non-Unicode-mode applications.

• Unicode-mode applications support multiple character sets. The locale value for the server where Essbase Server is installed does not have to match the locale value for the clients that work with Unicode-mode applications.

• By default, Essbase creates block storage applications in non-Unicode mode. • Aggregate storage applications do not support the Unicode-mode option. • Essbase Spreadsheet Add-in does not support Unicode-mode applications. • Smart View supports both Unicode-mode and non-Unicode-mode applications.

Databases

An block storage database is a data repository that contains a multidimensional data storage array.

Require write-back for users in releases prior to 9.3.1 (Write-back to level 0 members is supported for aggregate storage databases in Release 9.3.1 or higher.)

Block storage

Require users to perform interactive planning or sophisticated

allocations Block storage

N O T E

For additional information about Unicode Standard, see www.unicode.org. For additional information about Unicode-mode applications, see the Database

Administrator’s Guide.

(64)

Block storage databases consist of database objects that perform actions against the database, such as calculations or reporting. By default, database objects are stored in their associated database folder on the Essbase server. You can also save objects to a client computer or another available network directory. However, you cannot store, load, or calculate data on a client computer.

(65)

Creating Block Storage Applications

Before you create a block storage database, you need to create a block storage application that contains the database and other objects.

To create block storage applications:

1. In Administration Services Console, select File > New. The New dialog box is displayed.

2. On the Essbase tab, select Block Storage Application, and click OK. The Create Application dialog box is displayed.

3. Perform the following tasks:

• From the Essbase Server drop-down list, select a server name.

Creating Block Storage Applications

3 1

(66)

• In the Application name text box, enter the name for the new application.

• Optional: if the Essbase Server instance has permission and you want to support Unicode characters in your application, select Unicode mode to create the

application as a Unicode-mode application.

• Click OK.

Essbase creates the application and updates the Enterprise View tab.

N O T E

(67)

Creating Block Storage Databases

You must create an application before creating databases. To create block storage databases:

1. In Administration Services Console, select File > New. The New dialog box is displayed.

2. On the Essbase tab, select Database, and click OK. The Create Database dialog box is displayed. 3. Perform the following tasks:

• From the Essbase Server drop-down list, select a server name. • From the Application drop-down list, select an application name.

Creating Block Storage Databases

2

(68)

• In the “Database name” text box, enter the name for the new database. • Select a database type.

• Click OK.

Essbase creates the database and updates the Enterprise View tab.

(69)

Server File Structure

When you create a block storage application, Essbase creates a subdirectory for the application on the Essbase server in the $ARBORPATH\app directory. The new

subdirectory has the name of the application; for example, C:\Hyperion\AnalyticServices\app\Bigcorp.

When you create a block storage database, Essbase creates a subdirectory for the database within the application directory. The new subdirectory has the name of the database; for example, C:\Hyperion\AnalyticServices\app\Bigcorp\Sales.

Server File Structure

Essbase creates a directory for each application and database.

Outline

Calculation script Database file Bigcorp application

directory Directory for all applications %ARBORPATH% %HYPERION_HOME% Database backup Transaction control Kernel Sales database directory

Data source file Rules files

Data file Index file Free fragment file

(70)

Design Recommendations

Although block storage applications accept multiple databases per application, it is recommended best practice to create only one database for each application for the following reasons:

• During processes, Essbase logs messages only at the application level. There are no database-level process logs. If multiple databases exist in one application, Essbase logs all process messages for all databases to one log file. Multiple database logging makes it difficult to effectively interpret the log.

• If the administrator terminates an application process or if an application process becomes unavailable, all databases of the unavailable application are inaccessible to users until the application process is restored.

Design Recommendations

One database per application is recommended in a production environment:

Messages are logged at the application level, not the database level.

If an application becomes unavailable, all databases of the application become unavailable.

Server resources are more balanced. Exceptions:

Planning applications

(71)

Hyperion Essbase Analytics 9.3.1 Bootcamp 2-19 • To manage server resources effectively, you can balance the database load across

multiple, independent application processes, rather than using one application process to manage requests from multiple databases.

There are two common exceptions to the rule of one database per application: • Planning applications with multiple plan types automatically create a single block

storage application with multiple databases.

• If you licensed the currency conversion option for your block storage databases, you must create a primary database (where both input and converted data is stored) and a secondary currency database (where exchange rates are stored) inside one application in order to leverage automatic currency conversion.

(72)

Creating Outline Structures

Every dimension in an outline contains a hierarchy of members, with the dimension name at the top of the hierarchy. The composition of a dimension hierarchy is decided during the analysis and planning phase of the implementation; the number of levels, number of members, consolidation rules, and properties and attributes of the members vary with every database design. However, certain naming conventions, which apply globally to all hierarchies. facilitate reporting, calculating, security assignment, and other processes in which you need to use relationships, rather than names, to define a set of members.

Creating Outline Structures

Hierarchy terminology: Genealogy Generations Levels Generation 3 Generation 2 Generation 1 Level 0 (Leaf node) Level 1 Level 2 or Level 1 Ancestors of •Act vs Bud •Act vs Fcst •Bud vs Fcst Siblings, Children of Scenario Variances Descendants of Scenario