Upload
ledan
View
221
Download
1
Embed Size (px)
Citation preview
Technologies• Hyperion Application Link (HAL)• Data Integration Management (DIM) • Oracle Data Integrator (ODI)Oracle Data Integrator (ODI)• Enterprise Performance Management Architect (EPMA)• Financial Data Quality Management (FDM)• ERP Integrator (ERPi)ERP Integrator (ERPi)• Data Relationship Management (DRM)• Essbase Integration Services (EIS)• Essbase Studio (EAS)• Essbase Studio (EAS)• Outline Load Utility• DATAEXPORT Command• MaxL• MaxL• Windows Batch Scripting• Essbase SQL Loader• Essbase Analytics Link (EAL) for HFM• Essbase Analytics Link (EAL) for HFM
Hal
• Background– Hyperion tool for loading data and
metadata to Hyperion Essbase, Financial M d Pl iManagement, and Planning
– No longer supported by Oracle
Hal
• Common Uses– Loading data (text, relational) to Essbase,
Planning– Extracting outline information
Hal
• Use Case– Company wants to move GL data from a
relational data source and use it to update h li i Pl ithe outline in Planning
DIM
• Can load data and metadata to Essbase, Pl i HFM P f S dPlanning, HFM, Performance Scorecard
• Can process large volumes of data
DIM
• Use Case(s):– IT driven process passing large volumes
of data at high speeds– Complex mapping logic is required– Multiple workflows
ODI
• Oracle Data Integrator• Very flexible tool• Knowledge modules for interacting with
systems (Essbase, Planning, SQL Server, Oracle, Flat file, etc.)D i t kfl• Design custom workflows
ODI
• Can load data and metadata to Essbase, Pl i HFM tPlanning, HFM, etc.
• Can load data warehouses, ERP systems d t d t band most databases
• Strategic data integration tool from Oracle
ODI
• Use Case– Upstream data is in relational databases
accessible via JDBC driver, wants to bi d f fil i i icombine data from a file coming in via
FTP and use that to load to a Hyperion cube and send an email out on failurecube, and send an email out on failure.
EPMA
• Can manage metadata and hierarchies with hi l i t fgraphical interface
• Dimension Library centralizes data for diff t di idifferent dimensions
• Can move data with Data SynchronizationI t f T bl• Interface Tables
EPMA
• Manage Essbase, Planning, HFM in one lplace
• Mostly deals with metadata• Provides validation functionality• Provides limited data mapping / integration• Provides Application Library
EPMA
• Use Case– Administrator already uses EPMA,
deploys metadata to various applications– Ad hoc data sync across environments– Quickly build a new application for a
specific purpose by using metadata and data from existing applications
FDM
• Financial Data Quality Management• Load data to HFM, Essbase and Planning
from flat files• SQL based, business driven• Highly customizable with VB Script• Self-service or automated data loading• Allows drill back from target systems
FDM
• Use Case– Enable SME’s to map their own data– Real time validation & verification – SOX Compliance & Certification– Industrial strength ETL not requiredg q
ERPi
• New in 11.1.1.3• Pulls directly from source ERPs• Load metadata to HFM, Planning and
Essbase• Combined with FDM, loads data to HFM,
Pl i E bPlanning or Essbase• Facilitates user drill back and write-back to
ERP f HFR S t Visource ERP from HFR or Smart View
ERPi
• Use Case– Enhance functionality of existing FDM– With supported source ERPs, create
robust 2-way data flow for reporting and analysis. Provide access to detail with out
li ti li tireplicating across applications.– Push downstream data to all systems
DRM
• Data Relationship Management• For managing metadata only (no cube data)• Advanced features for versioning, pushing to
source systems, pushing to Hyperion
DRM
• Very robust metadata management tool• Can manage and deploy data for Hyperion
and non-Hyperion systems• Does not process data• Formerly known as MDM (Razza)
DRM
• Use Case– Hierarchies for dimensions in cube(s) are
sourced from external system– Multiple cubes need same hierarchies– Keep all Hyperion products in sync– Centralize and reduce metadata
maintenance– Segregate metadata management from
system administration
Essbase Integration Services
• Used to model cubes from relational data sources
• Can be used to build/update outline and load d tdata
• Supports complex SQL if neededV f t if d l• Very fast if used properly
Essbase Integration Services
• Pros– Very flexible– Rich dimension building capabilities
without having to mess around with load rules
• Cons– Once model is setup, you’re “married to it”– You need to really think to get it right
Essbase Integration Services
• Use Case– Data and metadata already exist in a SQL
database, and now the business would lik b ild l i l b idlike to build multiple cubes to provide analysis capabilities and possibly drill-thru
Essbase Studio
• Used to design cubes from relational data OBIEE EPMA & t t filsources, OBIEE, EPMA apps & text file
• Used for light-weight data modeling• Evolution of EIS• Common Metadata Repository• Lineage Tracking• Limited EAS functionality provided
Essbase Studio
• ProsV fl ibl– Very flexible
– Enables true artifact reusability– Introspection is very cool– Drill through (RDBMS, URL, HFM, Java,
t )etc.)• Cons
– Not your father’s Application Manager– Not your father’s EAS
Outline Load Utility
• Can load data and metadata• Create a load file in text (CSV)• Complex command line options
OutlineLoad [-f:passwordFile][/S:server] /A:application /U:userName [/M] [/E:outputFileName] [/I:inputFileName/D[U]:loadDimensionName|/DA:attributeDimensionName:baseDimensionName] [/TR] [/N] [[/R] [/U]] [/C] [/F] [/K] [/X:exceptionFileName] [L:logFileName] [/DX:HSP_Rates][/DS:HSP_SMARTLISTS] [/8][/?]
Outline Load Utility
• Pros– No ETL required– Perform batch outline updates to Planning– Can load data as well
• ConsCons– Arcane syntax– Practical limitations (Volume)Practical limitations (Volume)
Outline Load Utility
• Use Case– Company uses Planning to do yearly
forecast of employee salaries. HR id d h i h lprovides a spreadsheet with employee
data and salary basis dataO tli l d tilit b d– Outline load utility can be used periodically to update the employee members in the Planning outline and loadmembers in the Planning outline and load up their base data
DataExport
• Historically, an Essbase CDF (custom d fi d f ti ) d t t d t t t tdefined function) used to export data to text file or relational data sourceI ti f ti lit ( d t t• Is now native functionality (no need to setup CDF, which can be tricky)
• Useful for calling from MaxL (in place of• Useful for calling from MaxL (in place of report script)
• Can provide export capability to users by• Can provide export capability to users by giving them access to a calc script
DataExport
• Pros– Can be easier and more flexible than
report scripts• Cons
– Can only export data (no metadata)y p ( )• Use Case
– Exporting data to be used to load anotherExporting data to be used to load another cube
DataExport
• Use Case– Data exists in cube but not necessarily
easily accessible from other SQL sources, d i h fil i hand wish to generate a text file with a
certain subset of data (addressable with FIX)FIX)
MaxL
• Used to automate Essbase administrative t ktasks
• Replaced harder to read “ESSCMD”• Can do almost everything to a
server/application/cube/user that can be done in EASdone in EAS
MaxLset MY_NAME = "ProcessCube";login $ESSUSER identified by $ESSPW on $ESSSERVER;
spool stdout on to "$LOGPATH\\$CONTEXT $MY NAME $1 stdout txt";spool stdout on to $LOGPATH\\$CONTEXT.$MY_NAME.$1.stdout.txt ;spool stderr on to "$LOGPATH\\$CONTEXT.$MY_NAME.$1.stderr.txt";
alter database $1.$2 reset data;
import database $1.$2 dataconnect as $SQLUSER identified by $SQLPW using server rules_file
'LdQVSOS' on error write to "$LOGPATH\\$CONTEXT $MY NAME $1 error txt";on error write to $LOGPATH\\$CONTEXT.$MY_NAME.$1.error.txt ;
execute aggregate process on database $1.$2stopping when total_size exceeds $3;
spool off;logout;exit;
MaxL
• Use Case– Data/metadata available in text file or
relational data source, want to automate h k i i ion the server or work in to existing
automation
– Perl Module
Batch Scripting
• Simple batch files used to perform a f t ksequence of tasks
• Lends itself very easily to automating and h d li f i t kscheduling for recurring tasks
• Can glue together other data integration tools: MaxL ODI outline load etctools: MaxL, ODI, outline load, etc.
Batch Scripting
• Pros– Very easy to implement– Not limited to Hyperion products
• Cons– Large scripts can become unwieldy andLarge scripts can become unwieldy and
hard to test– Many scripts are not good at dealing with y p g g
an error in the middle of processing– Custom code not supportedpp
Batch Scripting
• Use case– Weekly close process consists of a series
of repetitive steps• Generate text file from another system• Copy text file
L d d t t E b• Load data to Essbase• Calc cube
A simple batch file and MaxL script can be– A simple batch file and MaxL script can be created and scheduled to automate this
Essbase SQL
• Used as the data source in a load rule• Primarily used for data loading• Also useful for dimension building• Very useful if you want to “skip” putting data
in a text file• Can serve as a stepping stone to using EIS,
ODI, Studio, etc.• Useful in conjunction with automation
Todd RebnerManaging Partner
8803 Brecksville Rd., Suite 7-198 / Brecksville, Ohio 44141Cell: (330) 212-3097 / eFax: (440) 201-7486