Case Study Business Intelligence & Analytics

Implementation of Hyperion Planning for a Leading Financial Solutions & Services Provider, USA
Client Overview
Financial product and services provider with experience in technology system design

Business Situation
There was a need to “Modify the ENTITY Dimension in the Hyperion Planning Application by The Challenges
removing the Region member from Entity and adding Business Unit to the Entity Operational
Currently ENTITY Dimension comprises of “Operating Unit”, “Department” and “Region”. Modification to the Planning objects was
Proposed Entity Dimension will comprise of “Business Unit, Operating Unit and Department. dependent on the new hierarchy of
Entity Dimension. Getting the right
Solution & Engagement Model combination of Entity Dimension at right
The solution consisted of Designing, Development & Deployment of Hyperion Planning time was major challenge for the
Application Development

Impact Analysis carried out and Planning Objects (Data Forms, Calc Scripts, Business Rules, As this was fully an offshore project,
etc.) identified to modify as per new structure of Entity Dimension getting on-time clarification was a
problem. Again, there was no resource
SSIS packages created to generate flat files to re-map old data and load the actuals at client place in SIT, UAT and Deploy-
ment phase
Technologies Prioritization of Planning Objects before
Budgeting Application - Hyperion Planning proceeding for Development
OLAP Tools – Hyperion Essbase
ETL Tools – MS SQL Server Integration Services Technical
Reporting Tools - Essbase Excel Add-in, Smartview and Financial Reporting Mapping old data to new structure with
Databases – MS SQL Server Entity and Region Dimensions and
Source Systems – PeopleSoft Financials, HR Vantage loading the data into the planning
system
Statistics Changing the Currency from Local to
3 HAL routines developed to load the Entity Dimension in the planning application USD based on Business Units instead of
Region Codes
Changes made to 4 Cubes (P&L, Workforce, Balance Sheet and Cash flow) in Essbase
Elimination of records where the
Approximately 20 Data forms, 20 Reports, 10 Business Rules, 10 Calc Scripts, 5 Data load combination of Business Unit, Operating
Rules and 10 Smartview Templates modified according to new structure Unit and Department is not matching
2 SSIS packages created to remap the budgeted/forecasted and actual data of year 2008 and with the new Entity structure
2009 Implementation of access level Security
by Business Unit instead of Region wise,
which was provided earlier
Business Benifits
As Business Unit (BU) is one of the
Critical dimension from the Organization
perspective, Budgeted/Forecasted data
by Business unit wise can be entered to
Planning application and further can be
analyzed by the BU
Again, data can be further analyzed by
region wise, as a separate dimension
created for Region
Users can use the specific Data forms
/Reports based on the Business unit
they belong to
Data can be analyzed by multiple
currency wise. i.e., Local or USD

© Hexaware Technologies. All rights reserved. www.hexaware.com