Hyperion Essbase Integration Services Tips and Tricks For Utilizing Journal

Hyperion Essbase Integration Services:
Tips and Tricks for Utilizing Journal

Entry Drill-Through
Greg Vlahos, PresidentAnalytic Vision
Rob Osborne, Manager Financial ReportingSara Lee Business Services
Session #2037A
Agenda
y Review original Hyperion Essbase implementation.
y Present strategic vision of enhanced solution with
Hyperion Essbase Integration Services.
y Review implementation and provide technical tips:
Present the implementation schematic overview.
Discuss the star schema design concept.
Provide tips on implementing the Hyperion Essbase
Integration Services model.
Provide tips on implementing the Hyperion Essbase
Integration Services Metaoutline.
Describe steps to implement a drill-through report.
y Questions and Answers

2037A | Hyperion Essbase Integration Services: Tips and Tricks for Utilizing Journal Entry Drill-Through
Review Original Hyperion Essbase

Solution
Lawson
Lawson
Data Pump
9 Account Cubes
9 Activity Cubes
y Lawson data pump feeds 18 GL Hyperion Essbase

cubes
y Issues with solution:
Data pump was slow and impacted month-end process.
Data pump could not combine GL account and activity.
Data pump restricted aspects of Hyperion Essbase design.
Users could not drill into journal entry detail.
Relational reports ran directly from Lawson.
New G/L Reporting Vision with

Hyperion Essbase Integration Services
Lawson
GL Data
Warehouse
9 Account/Activity Cubes
y Pull reporting and cube-building process off Lawson:

Create a central data store for journal entry data.
Design Hyperion Essbase cubes to combine accounts and
activity.
Use Hyperion Essbase Integration Services to facilitate journal
entry drill-through reporting.
Use Hyperion Essbase Integration Services to eliminate the
need for Hyperion Essbase build tables.
Use the central data store for relational reporting.
Benefits of New Process Based on

y Almost all processing is off the Lawson box.
y Able to combine and optimize the Hyperion Essbase
design.
y The refresh performance is greatly improved.
y Changes can now be made in one place rather than in
multiple places, despite nine cubes.
y Users can now drill through to journal entry detail, even
from ad hoc views in Hyperion Analyzer or Microsoft
Excel.

Implementation Technical Tips
y Present the implementation schematic overview.
y Discuss the star schema design concept.
y Provide details on implementing the Hyperion Essbase
Integration Services model:
Describe tasks performed with the Hyperion Essbase
Integration Services model.
Present tips from implementing the SLBS model.
y Provide details on implementing the Hyperion Essbase

Integration Services metaoutline:
Describe tasks performed with the Hyperion Essbase
Integration Services metaoutline.
Present tips from implementing the SLBS metaoutline.
y Describe implementing drill-through reports.


Schematic Overview
Understanding Star Schema Design
Customer
Dimension
Deal
Dimension
A dimension identifies a major

perspective of a business data set.
Product
Dimension
Fewer tables improves ease of

use and performance
Sales
Facts
Sales Rep
Dimension
A fact table holds the metrics for

a business data set.
Field names utilize end-user

terminology.
Time
Dimension
Optimizes query and reporting

usage.
Works well with data mart data
loads (required for Hyperion
Essbase Integration Services).
What Are Conformed Dimensions?
Customer
Dimension
Deal
Dimension
Sales
Facts
Sales Rep
Dimension
Warehouse
Dimension
Product
Dimension
Conformed
Dimensions
Inventory
Facts
Time
Dimension
Lot
Dimension
Transaction
Dimension
SLBS GL Star Schema Design
10

Impacts Star Schema Design
Relational dimensions need to hold new Hyperion

Essbase fields:
y Alias
y Consolidation unary rollup (e.g., + or -)
y Data storage (e.g., dynamic calc or label)
y Formula (if it needs to change dynamically, like rolling
12)
y Two-pass calc
y Expense reporting
y Solve Order
11

Impacts Star Schema Design
Relational dimension to support jagged hierarchy is different
from ideal relational reporting design:
y Hyperion Essbase Integration Services Support: bottom up
using NULL for empty levels
Relational report: Top down with lowest level repeating

Level 6
For EIS
Dimension
NULL
For Relational
Balance Sheet
Reporting
Level 4
Level 3
Level 2
NULL
Balance Sheet
Assets
Current Assets
Asset
Current Assets
Cash
Acct 1234
Level 5
Level 1 Level 0
Cash
Acct 1234
Acct 1234 Acct 1234
12
Key Tasks for Hyperion Essbase

Integration Services Model
y Identify dimension source tables - include all data
elements required to support a Hyperion Essbase
model:
Dimension hierarchies, including alternate hierarchies
Columns to be used for attribute dimensions
y Identify fact table source:

Fact table metrics and associated Measures dimension
Join criteria for each dimension table
y Identify column transformations:

Prefix, suffix, concatenations, etc.
Where clause filters
13
SLBS Hyperion Essbase Integration

Services Financial Model
y This Hyperion Essbase Integration Services model has
eight Hyperion Essbase dimensions.
y Its created with a drag-and-drop interface.
14
Identify Dimension Hierarchy Columns

y User can add multiple hierarchies to create alternate
rollups with shared members.
y Right-click a Dimension and select Properties, then
choose the Hierarchy tab.
y Double-click the
columns in the left
frame in hierarchy
sequence.
15
Identify Dimension Attribute Columns

y Dimension columns to be used as an attribute
dimension must be identified.
y Right-click the table
name in the model
and choose Properties.
y Select the column
and click Attribute.
16
Key Tasks for a Hyperion Essbase

Integration Services Metaoutline
y Define the Hyperion Essbase dimensions:
Use model hierarchies, other columns, user-defined.
Set up and associate attribute dimensions.
Set outline member sorting.
Identify alias, rollup math, data storage, formula, etc.
y Use metaoutline filters to support multiple cubes.

y Automate the driven by Hyperion Essbase Integration
Services Hyperion Essbase refresh process.
y Create drill-through reports with optimized SQL.
17
SLBS Hyperion Essbase Integration

Services Metaoutline
18
Steps to Create the Metaoutline

y Drag defined hierarchies from the model on the left side
of the screen into the metaoutline:
y Right-click each level to add properties such as:

Alias, storage, unary rollup, etc.
Sort sequence for outline build
19
Identify Attribute Dimension Level

y Drag attribute columns
into the metaoutline.
y Right-click them and
identify the associated
attribute levels.
20
SLBS Metaoutline Filter Use
21
SLBS Metaoutline Filter Use

y SLBS wanted nine company group cubes for security,
refresh flexibility, and minor differences.
y Filters allowed them to create one Hyperion Essbase
Integration Services process that could be used for
each cube.
y Two filters were required for each cube:
One for creating the outline
The other for loading the data
y Typical filter constraints included:

A company group filter for both dimension and data loads
A data load filter to constrain on the main hierarchy for
dimensions with alternate rollups (avoiding duplicate data)
22
Apply Filters to Essbase Build/Load

y This screen allows
the user to build
and load a
Hyperion Essbase
database.
y This is where the
filters are applied.
23
Automate the Load Process

y Hyperion Essbase Integration Services has a scripting
language for automation.
y Use a text editor to create a CBS script:
LOGIN NAWSSSHYPSQL002
SETSOURCE "DSN=SLBSPRODDW;UID=xx;PWD=zz;"
SETTARGET "DSN=NAWSSSHYPSQL002;UID=xx;PWD=zz;"
SETCATALOG "DSN=SLBSHHyperion Essbase Integration Services PROD;UID=xx;PWD=zz;"
LOADMEMBER
"OTL=SLBSPRODDW;APP=SLBSGA;DBN=SLBSGA;FLT_ID_MEMBER=2;
OTL_CLEAR=Y;"
LOADDATA "OTL=SLBSPRODDW;APP=SLBSGA;DBN=SLBSGA;FLT_ID_DATA=3;
REPLACE_ZEROS=Y;CALC_SCRIPT=CALCALL;"
EXIT
y The script is run from a batch file:

cd D:\EIS Load Files\SLBS
OlapIcmd -f"SLBSGA refresh.cbs"
24
Automate the Load Process (Continued)

y The filters are referenced with a filter ID number:
LOADMEMBER "OTL=SLBSPRODDW;APP=SLBSGA;DBN=SLBSGA;FLT_ID_MEMBER=2;
OTL_CLEAR=Y;"
y These numbers are found in the MO_FILTERS table in

the Hyperion Essbase Integration Services catalog
25
Customize User Defined SQL Tip

y Our initial data warehouse design included two
snowflaked dimensions to handle alternate rollups,
y The first issue with this approach was that the
automatically generated data load SQL process
created around 30 different SQL statements:
The data loaded correctly.
But it took 2 to 3 minutes for each SQL load statement.
y The solution was to customize the 30 data load SQL

statements into one SQL statement.
26
Customize User-Defined SQL Tip

y You can directly edit the generated SQL statements.
y You must edit the OLAP metaoutline properties:
Select the Load Optimization tab.
Select Use user-defined SQL for data load.
27
Drill-Through Versus Hybrid Analysis

y Drill-Through:
Drill-through provides the ability to drill from Hyperion
Essbase into the supporting details in a fact table.
An example of this would be drilling from month-level account
values into the supporting journal entries.
y Hybrid Analysis
Hybrid analysis provides the ability to drill from Hyperion
Essbase into a lower level of detail of a dimension table.
An example of this would be a large retail shop that has
100,000 SKUs; they could drill down from product categories
in Hyperion Essbase, to SKUs in the Product table.
The aggregate storage option should minimize this usage.
28
Drill-Through Setup Report

y Hyperion Essbase Integration Services allows the user to
identify the dimension levels from which the user can drill
through to detail facts.
y The user also selects
which fields in the fact
table will be retrieved.
y Here SLBS selects
JE detail.
y Users can drill from
any level and view
supporting detail.
y Even shared members
29
Drill-Through Setup Challenges

y We had issues using snowflaked dimensions:
Could not drill on a hierarchy with a user-defined member
(e.g., Alternate Hierarchy parent label).
We also had issues with jagged alternate hierarchies.
y Solution was to combine alternate hierarchies into a

single traditional dimension, as shown here:
Acct Unit
Main
Hierarchy
Level_1
Level_2
Level_3
156-2020
Locn: 156
Comp:12
Comp Grp 5
156-2020
GBR100
NULL
NULL
30
Drill-Through Example
31
Drill-Through Example
32
Questions and Answers
33
Hyperion Essbase Integration Services:

Tips and Tricks for Utilizing Journal
Entry Drill-Through
Greg Vlahos, PresidentAnalytic Vision
gvlahos@analyticvision.com
704-414-6675
Rob Osborne, Manager Financial ReportingSara Lee

rosborne@saralee.com
336-519-2947
Session #2037A
Please Complete Your Session Evaluation

Hyperion Essbase Integration Services Tips and Tricks For Utilizing Journal

Uploaded by

Document Information

Original Title

Copyright

Available Formats

Share this document

Share or Embed Document

Sharing Options

Did you find this document useful?

Is this content inappropriate?

Copyright:

Available Formats

Hyperion Essbase Integration Services Tips and Tricks For Utilizing Journal

Uploaded by

Copyright:

Available Formats

Hyperion Essbase Integration Services:

Tips and Tricks for Utilizing Journal

y Questions and Answers

Review Original Hyperion Essbase

y Lawson data pump feeds 18 GL Hyperion Essbase

New G/L Reporting Vision with

y Pull reporting and cube-building process off Lawson:

Benefits of New Process Based on

Hyperion Essbase Integration Services

y Provide details on implementing the Hyperion Essbase

y Describe implementing drill-through reports.

Hyperion Essbase Integration Services

Understanding Star Schema Design

A dimension identifies a major

Fewer tables improves ease of

A fact table holds the metrics for

Field names utilize end-user

Optimizes query and reporting

What Are Conformed Dimensions?

SLBS GL Star Schema Design

Hyperion Essbase Integration Services

Relational dimensions need to hold new Hyperion

Hyperion Essbase Integration Services

Relational report: Top down with lowest level repeating

Acct 1234 Acct 1234

Key Tasks for Hyperion Essbase

y Identify fact table source:

y Identify column transformations:

SLBS Hyperion Essbase Integration

Identify Dimension Hierarchy Columns

Identify Dimension Attribute Columns

Key Tasks for a Hyperion Essbase

y Use metaoutline filters to support multiple cubes.

SLBS Hyperion Essbase Integration

Steps to Create the Metaoutline

y Right-click each level to add properties such as:

Identify Attribute Dimension Level

SLBS Metaoutline Filter Use

SLBS Metaoutline Filter Use

y Typical filter constraints included:

Apply Filters to Essbase Build/Load

Automate the Load Process

y The script is run from a batch file:

Automate the Load Process (Continued)

y These numbers are found in the MO_FILTERS table in

Customize User Defined SQL Tip

y The solution was to customize the 30 data load SQL

Customize User-Defined SQL Tip

Drill-Through Versus Hybrid Analysis

Drill-Through Setup Report

Drill-Through Setup Challenges

y Solution was to combine alternate hierarchies into a

Questions and Answers

Hyperion Essbase Integration Services:

Rob Osborne, Manager Financial ReportingSara Lee

Please Complete Your Session Evaluation

You might also like