Hyperion Essbase Integration Services Tips and Tricks for Utilizing Journal

Hyperion Essbase Integration Services: Tips and Tricks for Utilizing Journal Entry Drill-ThroughGreg Vlahos, President—Analytic VisionRob Osborne, Manager Financial Reporting—Sara Lee Business Services

Session #2037A

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

Agenda

Review original Hyperion Essbase implementation.

Present strategic vision of enhanced solution with Hyperion Essbase Integration Services.

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.

Questions and Answers


Review Original Hyperion Essbase Solution

Lawson data pump feeds 18 GL Hyperion Essbase cubes

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.

9 Account CubesLawsonData PumpLawson

9 Activity Cubes


New G/L Reporting Vision with Hyperion Essbase Integration Services

GL DataWarehouseLawson

9 Account/Activity Cubes

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 Hyperion Essbase Integration Services

Almost all processing is off the Lawson box.

Able to combine and optimize the Hyperion Essbase design.

The refresh performance is greatly improved.

Changes can now be made in one place rather than in multiple places, despite nine cubes.

Users can now drill through to journal entry detail, even from ad hoc views in Hyperion Analyzer or Microsoft Excel.


Hyperion Essbase Integration ServicesImplementation Technical Tips

Present the implementation schematic overview.Discuss the star schema design concept.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.

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.

Describe implementing drill-through reports.


Hyperion Essbase Integration Services Schematic Overview


Understanding Star Schema Design

DealDimension

SalesFacts

TimeDimension

ProductDimension

Sales RepDimension

CustomerDimension

• A dimension identifies a major perspective of a business data set.

• A fact table holds the metrics for a business data set.

• Fewer tables improves ease ofuse and performance

• Field names utilize end-user terminology.

• Optimizes query and reporting usage.

• Works well with data mart data loads (required for Hyperion Essbase Integration Services).


What Are Conformed Dimensions?

DealDimension

SalesFacts

TimeDimension

ProductDimension

Sales RepDimension

CustomerDimension

ProductDimension

TimeDimension

ConformedDimensions

InventoryFacts

LotDimension

WarehouseDimension

TransactionDimension


SLBS GL Star Schema Design


Hyperion Essbase Integration Services Impacts Star Schema Design

Relational dimensions need to hold new HyperionEssbase fields:

Alias

Consolidation unary rollup (e.g., + or -)

Data storage (e.g., dynamic calc or label)

Formula (if it needs to change dynamically, like rolling 12)

Two-pass calc

Expense reporting

Solve Order


Hyperion Essbase Integration Services Impacts Star Schema Design

Relational dimension to support jagged hierarchy is different from ideal relational reporting design:

Hyperion Essbase Integration Services Support: bottom up using NULL for empty levels

Relational report: Top down with lowest level repeating

Level 6 Level 5 Level 4 Level 3 Level 2 Level 1 Level 0

For EIS Dimension NULL NULL Balance Sheet Assets Current Assets Cash Acct 1234

For Relational Reporting Balance Sheet Asset Current Assets Cash Acct 1234 Acct 1234 Acct 1234


Key Tasks for Hyperion Essbase Integration Services Model

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

Identify fact table source:— Fact table metrics and associated Measures dimension— Join criteria for each dimension table

Identify column transformations:— Prefix, suffix, concatenations, etc.— Where clause filters


SLBS Hyperion Essbase Integration Services Financial Model

This Hyperion Essbase Integration Services model has eight Hyperion Essbase dimensions.

It’s created with a drag-and-drop interface.


Identify Dimension Hierarchy Columns

User can add multiple hierarchies to create alternate rollups with shared members.

Right-click a Dimension and select Properties, then choose the Hierarchy tab.

Double-click thecolumns in the leftframe in hierarchysequence.


Identify Dimension Attribute Columns

Dimension columns to be used as an attribute dimension must be identified.

Right-click the tablename in the modeland choose Properties.

Select the columnand click Attribute.


Key Tasks for a Hyperion Essbase Integration Services Metaoutline

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.

Use metaoutline filters to support multiple cubes.

Automate the driven by Hyperion Essbase Integration Services Hyperion Essbase refresh process.

Create drill-through reports with optimized SQL.


SLBS Hyperion Essbase Integration Services Metaoutline


Steps to Create the Metaoutline

Drag defined hierarchies from the model on the left side of the screen into the metaoutline:

Right-click each level to add properties such as:— Alias, storage, unary rollup, etc.— Sort sequence for outline build


Identify Attribute Dimension Level

Drag attribute columns into the metaoutline.

Right-click them and identify the associated attribute levels.


SLBS Metaoutline Filter Use


SLBS Metaoutline Filter Use

SLBS wanted nine “company group” cubes for security, refresh flexibility, and minor differences.

Filters allowed them to create one Hyperion Essbase Integration Services process that could be used for each cube.

Two filters were required for each cube:— One for creating the outline— The other for loading the data

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)


Apply Filters to Essbase Build/Load

This screen allowsthe user to buildand load aHyperion Essbase database.

This is where thefilters are applied.


Automate the Load Process

Hyperion Essbase Integration Services has a scripting language for automation.Use a text editor to create a CBS script:

The script is run from a batch file:

LOGIN NAWSSSHYPSQL002SETSOURCE "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

cd D:\EIS Load Files\SLBSOlapIcmd -f"SLBSGA refresh.cbs"


Automate the Load Process (Continued)

The filters are referenced with a filter ID number:

These numbers are found in the MO_FILTERS table in the Hyperion Essbase Integration Services catalog

LOADMEMBER "OTL=SLBSPRODDW;APP=SLBSGA;DBN=SLBSGA;FLT_ID_MEMBER=2;OTL_CLEAR=Y;"


Customize User Defined SQL Tip

Our initial data warehouse design included two “snowflaked” dimensions to handle alternate rollups,

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.

The solution was to customize the 30 data load SQL statements into one SQL statement.


Customize User-Defined SQL Tip

You can directly edit the generated SQL statements.

You must edit the OLAP metaoutline properties:— Select the Load Optimization tab.— Select “Use user-defined SQL for data load.”


Drill-Through Versus Hybrid Analysis

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.

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.


Drill-Through Setup Report

Hyperion Essbase Integration Services allows the user to identify the dimension levels from which the user can drill through to detail facts.

The user also selectswhich fields in the facttable will be retrieved.

Here SLBS selectsJE detail.

Users can drill fromany level and viewsupporting detail.

Even shared members


Drill-Through Setup Challenges

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.

Solution was to combine alternate hierarchies into a single traditional dimension, as shown here:

Acct Unit MainHierarchy Level_1 Level_2 Level_3

156-2020 Y Locn: 156 Comp:12 Comp Grp 5

156-2020 N GBR100 NULL NULL


Drill-Through Example


Drill-Through Example


Questions and Answers

Hyperion Essbase Integration Services: Tips and Tricks for Utilizing Journal Entry Drill-ThroughGreg Vlahos, President—Analytic [email protected]

Rob Osborne, Manager Financial Reporting—Sara [email protected]

Please Complete Your Session Evaluation

Session #2037A

Documents

Hyperion Essbase Integration Services Tips and Tricks for Utilizing Journal