Oracle EPM at Oracle: Hyperion Planning and Oracle … Oracle EPM at Oracle: Hyperion Planning and...

Preview:

Citation preview

5 Copyright © 2011, Oracle and/or its affiliates. All rights reserved. Insert Information Protection Policy Classification from Slide 8

ORACLE PRODUCT

LOGO

Oracle EPM at Oracle: Hyperion Planning and Oracle Essbase Presenters: Matthew Bradley, VP, EPM Applications Raju Krishnamoorthy, Director, AIT

Jim English, VP Finance

We run the applications that run Oracle We drive enhancements based on our experience We share best practices with our customers

6 Insert Information Protection Policy Classification from Slide 8Copyright © 2011, Oracle and/or its affiliates. All rights reserved.

7 Copyright © 2011, Oracle and/or its affiliates. All rights reserved. Insert Information Protection Policy Classification from Slide 8

How Oracle Replaced Its

Legacy Budgeting and Planning Systems and lived to tell about it

8 Copyright © 2011, Oracle and/or its affiliates. All rights reserved. Insert Information Protection Policy Classification from Slide 8

In the beginning�

•  Legacy systems were in place across Oracle

•  Financial reporting needed a consistent set of tools

• No standard solution for Corporate and LOB

• No enterprise-wide reporting solution

9 Copyright © 2011, Oracle and/or its affiliates. All rights reserved. Insert Information Protection Policy Classification from Slide 8

What we needed

• Replace legacy systems

•  Implement “Best in Class” solution – standardize! •  Provide unified and integrated reporting solution •  Incorporate enterprise BI and effective change

management

10 Copyright © 2011, Oracle and/or its affiliates. All rights reserved. Insert Information Protection Policy Classification from Slide 8

Legacy architecture

Consol Ledgers (GL)

Acquisition Ledgers (GL)

Primary Ledgers (GL)

Oracle Financial Analyzer (Multi dimensional Cubes)

End

Use

rs

��������� � �����

11 Copyright © 2011, Oracle and/or its affiliates. All rights reserved. Insert Information Protection Policy Classification from Slide 8

Where we started:

������� �������� ������ ��� ��� �����

�����

������� ����� ��

������������������ ������

���������������� �������

������������������ �������

12 Copyright © 2011, Oracle and/or its affiliates. All rights reserved. Insert Information Protection Policy Classification from Slide 8

Oracle’s EPM Strategy

Corporate Reporting (CORE) (Essbase)

Div

isio

nal L

OB

A

pplic

atio

ns

(Pla

nnin

g)

CRM

Corporate Data Warehouse

���

� ��� ��!"#$%&&

���

DRM

ERP

���

13 Copyright © 2011, Oracle and/or its affiliates. All rights reserved. Insert Information Protection Policy Classification from Slide 8

Definitions •  Aggregate Storage Option (ASO)

–  Fast aggregation –  Large, sparse data sets –  Large outlines – No specialized calculations required in the cube

•  Block Storage Option (BSO) – Data entry / Planning – Complex calculations / allocations – Separate data entry from data loads – Replicated partitions

14 Copyright © 2011, Oracle and/or its affiliates. All rights reserved. Insert Information Protection Policy Classification from Slide 8 Insert Information Protection Policy Classification from Slide 8

Take One

BSO only architecture

•  All data entry •  All actuals data load •  All required transformations •  Aggregation of data

Take One BSO

15 Copyright © 2011, Oracle and/or its affiliates. All rights reserved. Insert Information Protection Policy Classification from Slide 8

But there were problems

• Data aggregation took too long •  Extensive downtime • Data transformations took hours • Unpredictable and inconsistent

It just didn’t work. Good tool. Bad implementation.

16 Copyright © 2011, Oracle and/or its affiliates. All rights reserved. Insert Information Protection Policy Classification from Slide 8

Back to the drawing table

•  Explored various options to fix the issue – Essbase 32bit vs. 64 bit option –  Tuning various calc scripts – Reduce the amount of data in the cube

•  Partnered with PD to redesign the solution – Oracle’s Size + Complexity of requirements demanded a different

approach

17 Copyright © 2011, Oracle and/or its affiliates. All rights reserved. Insert Information Protection Policy Classification from Slide 8

Complexity

'�� ������� ( ' � )�������������� ������ *��+

,-��� ��./0�������1

2�����.3��� ��4���������������� 5���2 2�����.3��� ��4����������������� 5(��+ 2�����.3��� ��4���������3�������� 5*��+ 2�����.3��� ��4��������6$��������� 5-��+

18 Copyright © 2011, Oracle and/or its affiliates. All rights reserved. Insert Information Protection Policy Classification from Slide 8

Take Two

19 Copyright © 2011, Oracle and/or its affiliates. All rights reserved. Insert Information Protection Policy Classification from Slide 8

Rep

ortin

g

Fore

cast

, B

udge

t en

try

Forecast, Budget, etc (ODI)

End Users

pg

Data Entry BSO cube

Actuals ASO cube

The Hybrid ASO/BSO Architecture

20 Copyright © 2011, Oracle and/or its affiliates. All rights reserved. Insert Information Protection Policy Classification from Slide 8

Hybrid ASO/BSO architecture worked •  All Corporate forecasting/budgeting in Corporate

Reporting (CORE)

•  Source of truth for internal and external reporting

• Global solution covering all LOB 24/7

•  1000+ users

21 Copyright © 2011, Oracle and/or its affiliates. All rights reserved. Insert Information Protection Policy Classification from Slide 8

What did this REALLY get us? Results!

������� �������� ������ ��� ��� ����������

��������������

�����������

������� ����� �� 5� �� ����7 ������������������ ������ �� �� ���7 ���������������� ������� 8� �� 9��7 ������������������ ������� :*� �� 9��7

22 Copyright © 2011, Oracle and/or its affiliates. All rights reserved. Insert Information Protection Policy Classification from Slide 8

Planning is paramount!

• Settle on the dimensionality early on • Design the dimensions to allow for ease of synchronization • Synchronize dimensions between cubes • Follow best practices • Establish a metadata maintenance process

23 Copyright © 2011, Oracle and/or its affiliates. All rights reserved. Insert Information Protection Policy Classification from Slide 8

What were Oracle’s technical considerations?

•  BSO performance –  Fragmentation – Commit blocks – Memory requirements during outline restructure

•  ASO performance considerations – Stored and dynamic dimensions –  Logical clear vs. physical clear during data loads

The Special Sauce

24 Copyright © 2011, Oracle and/or its affiliates. All rights reserved. Insert Information Protection Policy Classification from Slide 8

What did we learn?

•  The right tools = dramatic performance improvement – Hybrid ASO/BSO architecture – Relational database

•  Intermediate data store (staging area) • Automation of various business rules

– Oracle Data Integrator • End to end automation (ETL) • Pre-built integration with EPM

25 Copyright © 2011, Oracle and/or its affiliates. All rights reserved. Insert Information Protection Policy Classification from Slide 8

What The Future Holds

•  Additional Essbase/Planning Solutions • OBIEE 11g on Essbase

–  Zero data discrepancy between OBIEE 11g and Smart View

•  Blending data between reporting systems (Global DW, CORE, ODS)

•  Pre-requisites – Conform dimensions – Common security definitions

Recommended