Managing Metadata in EPMA vs Classic HFM

www.finitsolutions.com
Getting the Most out of EPM:
HFM: Managing Metadata: EPMA versus Classic
March 21, 2014
Greg Barrett (gbarrett@finitsolutions.com)
Christine Ong-Estrada (cong-estrada@finitsolutions.com)

- 2 -
Finit Overview
About Finit
– In business over 11 years: Company
founded in July 2002.
– 60+ employees in 20+ states (mostly
East Coast, South, and Midwest)
– 80+ HFM Clients
– Recognized as the Market Leader in
ARM/FCM
– Recognized as the World Leader in FDM
Project Work and FDM Customizations
– 50+ Planning / Essbase Clients
– Finit has managed many of the largest
EPM projects in the U.S.
– Our employees are generally CPA’s,
MBA’s, and have extensive Product and
Financial Reporting Backgrounds
Implementation Services
– Full cycle implementations
– Infrastructure and Data Services
– Project / Program Management
– Product Upgrades
– Redesign / Enhancements
Dedicated Support – Finit Answers
– Access to Hyperion SME’s (Dedicated support team
and guaranteed response times)
– Customer Service Focus
– Flexible Time and Material support packages with a
‘Pay as you Go’ option
– Technical and Admin / Functional Support
– Contact Greg Barrett (gbarrett@finitsolutions.com)
for info

Finit Solutions Introduction
Finit as a company: Who
we are….Why? How?

- 4 -
 We believe in making and delivering personalized
financial reporting solutions and experiences for others.
Making Solutions with Personalized Experiences
We value craftsmanship, authenticity and solution making
We believe in listening, questioning and analyzing the issues and
wishes of those we work with.
We look to build relationships, not as company to company but
person to person.
We are honestly aligned to the cause of those we work with.
We are Makers and Doers who roll up their sleeves and dig in.
WHY is Finit Here?

- 5 -
Running Finit like a Family
Finit has no debt or external owners.
This lets us keep focused on the customer in all cases as
Finit’s goal is not to maximize profit but maximize the value
we add to clients.
All owners are involved in the business.
We do not use contractors, employees only.
Finit’s compensation model is based upon client
satisfaction with consultant’s work, not utilization /
chargeability.
HOW do we achieve our beliefs?

- 6 -
Below are Finit’s core values
These are the same values we ask you to provide
consultant feedback on
Finit Values

- 7 -
Our values, culture and approach to becoming a
trusted advisor to clients has led to 100%
customer success for every Finit client (200+
and counting) and for every Oracle Hyperion
project (over 350+ and counting).
Finit’s Client Service

- 8 -
About the Presenter
Christine Ong-Estrada
(cong-estrada@finitsolutions.com)
• Former Enterprise and HFM administrator
• More than 10 years of Hyperion products experience
• HFM, FDM, EPMA, LCM, Financial Reporting
• HFM Project Lead
• 10 years of HFM build and implementation experience
• Worked on mostly Fortune 500 HFM Builds
• Based in Austin, TX

- 9 -
 Introduction to EPMA Metadata Management
 EPMA versus Classic Comparison
 Pros an Cons of each tool
 Transforming Classic to EPMA
 Synchronizing Metadata with LCM
 Q and A
Agenda

- 10 -
 Enterprise Performance Management Architect
 Feature of Foundation Services
 Integrates with:
 HFM
 Planning
 Essbase
 Profitability and Cost Management
 Data Relationship Management
 Enables administrators to create, manage, and deploy Hyperion
applications within one interface.
 Consists of different modules
What is EPMA?

- 11 -
A centralized location to manage dimensions and dimension
properties.
Used to:
 Create dimension import profiles
 Add, delete, and modify dimension members in the Shared Library
or directly in applications
 Modify dimension and member properties in the Shared Library or
directly in applications
Dimension Library

- 12 -
A summary of applications that have been created and/or deployed.
Used to:
 Create and manage applications in one centralized location
 Deploy applications
 Migrate applications to different servers within the same
environment
 Diagnositcs
 Compare (to Shared Library or to Deployed Application)
 Duplicate Application (EPMA and Deployed Application)
Application Library

- 13 -
 Data Synchronization
 Enables data synchronization between or within Hyperion applications.
 Create data mappings for reuse.
 Create flat file and interface table mappings to import data into Hyperion applications.
 Calculation Manager
 Enables you to create, validate, and deploy business rules and business rule sets.
 Transform Classic to EPM Architect
 Enables transformations of applications managed in Classic Financial Management to EPMA.
 Library Job Console
 Provides a summary, including status, of Dimension Library and application processes (including
imports, deployments, and data synchronizations).
 Configure Interface Data Sources
 For use of interface table to import metadata
Other Modules

- 14 -
 Classic
Creating an HFM Application

- 15 -
 EPMA
Application Library >
< Auto Create Local Dimensions
Define Customs >

- 16 -
 EPMA
Populate Calendar Dimensions >
Set Up Rate Accounts >
Define Application Settings >

- 17 -
Dimensions
Note: EPMA application is not the same as HFM application

- 18 -
Dimension Association

- 19 -
 Classic
 Desktop Client (Metadata Manager)
 Excel Macros / Text Files (.app or xml)
 EPMA
 Desktop Client (Metadata Manager)
 EPMA File Generator
 Dimension Library
 LCM (.lcmext, ads)
 Excel Macros / Text Files (.ads)
Managing Metadata

- 20 -
Methods of Loading Metadata
 Classic
Desktop Client

- 21 -
 Classic
Web Client

- 22 -
 EPMA
Dimension Library Shared Services
- Import Profile - LifeCycle Management (LCM)

- 23 -
Sharing Metadata
EPMA CLASSIC
Shared Library Extract and Load to another App

- 24 -
Comparing Metadata
EPMA CLASSIC
Compare to Shared Library or Deployed
Application
Text editor to compare extracts

- 25 -
Logging – Metadata Changes
EPMA CLASSIC
Transaction Log No equivalent
Transaction log of metadata changes are downloaded in excel format.
Logs time, date, username, type of changes made in the dimension library.

- 26 -
Logging – Process
EPMA CLASSIC
Job Console No equivalent

- 27 -
Renaming Members
EPMA CLASSIC
Retains data Extract data - rename member – edit
extracted data file – reload data file

- 28 -
Exclude Members
EPMA CLASSIC
Can exclude member/s from Shared
Library and deploy application
Delete member

- 29 -
Reordering Children
EPMA CLASSIC
Sort Members (Ascending/Descending)
Cut and Paste
Reorder Children
Drag and Drop
Cut and paste
Manually move up and down (arrows)

- 30 -
Default Parent
EPMA CLASSIC
Automatically Updated – no need to
specify
Specify default parent or leave blank
when member is moved

- 31 -
Copy Application
EPMA CLASSIC
Duplicate Application (copy EPMA
application) – Application Library (Admin)
Duplicate Application as Deployed –
Application Library (Admin)
Copy App Utility (IT)
Copy App Utility (IT)

- 32 -
Metadata File Back-up
EPMA CLASSIC
Use LCM
EPMA File Generator
- Will need to set up automated back up
process. (IT)
Save app or xml file in local or network
drive
Extract full application text file
(.ads)

- 33 -
Diagnostics
EPMA CLASSIC
Tests common issues with EPMA
application or process state
No equivalent

- 34 -
Transforming Classic to EPMA
Copy Classic Application
Basic Transformation Steps

- 35 -
Register Application with Shared Services

- 36 -
Provision user as Application Administrator

- 37 -
Transform Classic to EPM Architect

- 38 -
Lifecycle Management
• LCM provides a consistent way to migrate an application, a
repository, or individual artifacts between applications or across
environments.
• Lifecycle Management enables users to export artifacts to the file
system, edit them, and then re-import them.
• Tasks can be automated via integration with work flows.
• Integrated applications: HFM, Essbase (ASO & BSO), Planning
• Not currently integrated: DRM, EIS, FDM, HSFM

- 39 -
 Lifecycle Management
Destination: File System
LCM

- 40 -
 HFM Artifacts
Destination : HFM application or File System
LCM

- 41 -
Save as same file format before Importing after
Edit.
Shared Services = .csv
EPMA artifact - .lcmext
LCM

- 42 -
LCM

- 43 -
 ADS Export Format
 Can be re-imported
 Can be used in an existing
import profile
 Can be used to create a
new import profile
 Can be used with shared
and local libraries
LCM – ADS Format

- 44 -
 Copy contents
to Excel
 Text to
Columns
 Add Formula
 Copy contents
to Text
LCM – Editing in Excel

- 45 -
Questions?
Email us for a
copy of the slides or
link to the recording.
Thank you for attending!
- > Christine Ong-Estrada
(cong-estrada@finitsolutions.com)
- > Insights@finitsolutions.com
- > General Questions
 Greg Barrett
(gbarrett@finitsolutions.com)
 Joe Mizerk
(jmizerk@finitsolutions.com)

Managing Metadata in EPMA vs Classic HFM

Recommandé

Recommandé

Contenu connexe

Tendances

Tendances (20)

Similaire à Managing Metadata in EPMA vs Classic HFM

Similaire à Managing Metadata in EPMA vs Classic HFM (20)

Plus de finitsolutions

Plus de finitsolutions (20)

Dernier

Dernier (20)

Managing Metadata in EPMA vs Classic HFM

Notes de l'éditeur