Sie sind auf Seite 1von 30

Efficiently Delivering Effective Solutions

OracleHyperionIntegration Products

IntroductionandOverview Introduction and Overview

www.finitsolutions.com

Agenda
Introduction

Efficiently D li i Effective Solutions Effi i tl Delivering Eff ti S l ti

OverviewofOracleHyperionIntegrationProducts ReviewofBusinessCasesandavailabletools Q&A

www.finitsolutions.com
2

Efficiently Delivering Effective Solutions

OracleHyperionIntegration Products

Introduction

www.finitsolutions.com

WhoisFinit? Who is Finit?


FinancialConsolidationandReporting Integration PlanningandBusinessIntelligence

Efficiently D li i Effective Solutions Effi i tl Delivering Eff ti S l ti

FinitSolutionsspecializesintheOracleHyperionPerformance ManagementSolutionssuiteofproducts: g p

Strongfocusoncustomerserviceandvalue: Strong focus on customer service and value:


Over105clientsandFinithasneverhadafailedproject.Everyclientisareference. ValueisdrivenfromconsultantswithHyperionexpertise,strongFinance/ Accountingknowledgeandproactivecustomerservice.

RankedbyInc.Magazinein2007and2008asoneoftheTop100fastestgrowing Ranked by Inc Maga ine in 2007 and 2008 as one of the Top 100 fastest growing privateITServicescompaniesintheUS. MemberofmultipleHyperioncustomeradvisoryboardsandnewproduct validationprograms.

www.finitsolutions.com
4

FinitSolutions:SampleClients Finit Solutions: Sample Clients

www.finitsolutions.com
5

Efficiently Delivering Effective Solutions

OracleHyperionIntegration Products

OverviewofOracle sIntegrationProducts Overview of Oracles Integration Products

www.finitsolutions.com

OracleHyperionIntegrationProducts Oracle Hyperion Integration Products


FinancialDataQuality Management(FDM) Management (FDM) OracleDataIntegrator(ODI)

DataIntegration Management(DIM) EnterprisePerformance p ManagementArchitect (EPMA)

HyperionApplicationLink (HAL)

DataRelationship Data Relationship Management(DRM)

ERPIntegrator(ERPi)

ClassicMetadataTools

www.finitsolutions.com
7

FinancialDataQuality g ( ) Management(FDM)
FDMisawebbasedfinancialdatatoolthatisusedtoload, mapandvalidatesourcesystemfinancialdataintoatarget. FDMhasaprebuiltdataloadworkflowthatwalksthrough thedifferentloadsteps(Import,Validate,Export,Check). FDMhasauserfriendlyinterfacethatallowsusersto maintaintheirsourcesystemtotargetsystemmappingtables andloadtheirdata. FDMcansourcefinancialdataeitherbydirectlyconnectingto sourcesystems(throughFDMsourceadaptersorvia (h h d Integrationscripts)oritcanreadsourcesystemfiles. FDMhasHyperiontargetadaptersforHyperionEnterprise, HFM,Planning/EssbaseandHyperionStrategicFinance. HFM Pl i /E b dH i St t i Fi FDMhasadatamartadapterthatcanbeusedtomaptonon Hyperionchartsofaccounts. FDMcanbeenhancedthroughVBscriptcustomization.
www.finitsolutions.com
8

FinancialDataQuality g ( ) Management(FDM)UseCase
StrengthsandUseCase
PreBuiltinterface(workflow,mapping,logging) Validationsareakeycomponent(mapping,data,targetsystem). Typicalusecaseisforfinancialdataprocessingthatinvolvesmappingina multiuserenvironment. FDMcannotperformanyMetadatafunctions(loadmetadataormanage metadatahierarchies) ODIandDIMwiththeirabilitytoloadfinancialdata. Noproductsintermsofpresetenduserdrivendataandmapping workflow. FDMdoesrequirelicensing. FDMwasoriginallyUpStreamWebLinkandacquiredbyHyperionin2006. g y p q y yp
www.finitsolutions.com
9

Limitations Li it ti

SimilaritiestoOtherIntegrationProducts Similarities to Other Integration Products


Licensing/Other

OracleData g ( ) Integrator(ODI)
ODIisanintegrationtoolthatcanloadfinancialdataand applicationmetadataintodifferenttargetsystems. ODIhastheflexibilitytodesignitsworkflowthrougha graphicalworkflownavigationinterface.Asaresult,the productdoesnotimposeaworkflowonyouinthebeginning. ODIhasstrongsourceconnectionabilitiesaswellasthe abilitytolaunchandcontroljobsorcalculations(callinga storedprocedurethatmovesdatafromonetabletoanother). ODIhasKnowledgeModulesthathaveprebuiltworkflow h l d d l h h b l kfl forcertainsystems. ODIdoesnothavearobustenduserdrivenmappingtable. Themappingistypicallystoredinarelationaltableand Th i i t i ll t d i l ti l t bl d processedthroughtheworkflowsteps. Additionally,unlesstheKnowledgeModulecontainsit, loggingandvalidationsneedtobebuilt. l i d lid ti d t b b ilt
www.finitsolutions.com
10

OracleDataIntegrator ( (ODI)UseCase )
StrengthsandUseCase
AbilitytoloadHyperionmetadataandfinancialdatatoEssbase,Planning andHFM. d ITdrivenfinancialdataormetadataloadprocessing. Situationswherelimitedmappingisneeded. ODIdoesnothaveaprebuiltwebbaseduserinterfacetomap,validateor loaddataormetadata. Validationsandloggingitemswillmorethanlikelyneedtobecustombuilt Validations and logging items will more than likely need to be custom built (i.e.logdataloaderrorsinatextfile). MostsimilartoDIM,HAL , FDMforfinancialdata,thoughtypicallyadifferentuse(Financevs.IT) ODIdoesnotrequirealicenseifusedwithHFM,Essbase,Planning. q , , g ODIwasoriginallySunopsisandacquiredbyOracle.
www.finitsolutions.com
11

Limitations Li it ti

SimilaritiestoOtherIntegrationProducts

Licensing/Other

DataIntegration g ( ) Management(DIM)
DIMisconceptuallysimilartoODIinthatitisanintegration toolthatcanloadfinancialdataandapplicationmetadatato differenttargetsystems. diff DIMdiffersfromODIinthatitisbuiltonInformatica PowerCenter8.1.InformaticaisoneoftheleadingETLtools inthemarket.BycontrastODIisselfcontained. i th k t B t t ODI i lf t i d DIMprovidesadaptersthatcanbeusedinInformatica PowerCentertoconnecttoHFM,PlanningandEssbase. DIMwasoriginallydevelopedtoallowHyperionclientsto ll d l d ll l leverageexistinginvestmentsinInformatica.

www.finitsolutions.com
12

DataIntegrationManagement ( (DIM)UseCase )
StrengthsandUseCase
AbilitytoloadHyperionmetadataandfinancialdatatoEssbase,Planning andHFM. d ITdrivenfinancialdataormetadataloadprocessing.Verypowerful enginethatcanprocesslargevolumes. DIMdoesnothaveaprebuiltwebbaseduserinterfacetomap,validate orloaddataormetadata. gg g y ( g Validationsandloggingitemsmayneedtobecustombuilt(i.e.logdata loaderrorsinatextfile). MostsimilartoODI,HAL FDMforfinancialdata,thoughtypicallyadifferentuse(Financevs.IT) DIMdoesrequirealicenseifusedwithHyperionproducts. InformaticaisanindependentcompanynotownedbyOracle.
www.finitsolutions.com
13

Limitations

SimilaritiestoOtherIntegrationProducts

Licensing/Other

HyperionApplication ( ) Link(HAL)
HALwasHyperionstoolthatprovidedfinancialdataand metadataloadcapabilities(similartoODIandDIM). HALisconceptuallysimilartoODIandDIMinthatitis workflowbasedandthattheworkflowisnotprebuiltand needstobesetup. HALdidhaveamappingtool,TranslationManager,toallow formappingtotakeplacebetweensourceandHyperion targets. HALwasanOEMproductforHyperion,developedby d f d l db Vignette. ItiscurrentlyonSustainingSupportandissettobe discontinuedinJune2010.Thisdiffersfromsustaining di ti di J 2010 Thi diff f t i i supportinthatHALwillbeunsupportedafterJune2010and Oracletechsupportwillnottakeanycallsonit.

www.finitsolutions.com
14

EnterprisePerformance g ( ) ManagementArchitect(EPMA)
EPMAwasreleasedinSystem9.3.0. EPMAprovideslimitedfinancialdatafunctionality. p y EPMAallowsfortheabilitytomanagethemetadata structures/hierarchiesforHyperiontargetsystems(HFM, Planning,Essbase).Ithasaprebuiltgraphicalinterfaceto designandmanagemetadataattributes,andhierarchies. MetadatacanbeloadedintotheHyperiontargetsystems. y g EPMAhasaDimensionLibrarytomanagethemetadataand hierarchiesfordifferentdimensionsandproducts. EPMAhasaDataSynchronizationfeaturegearedtowards g yp y movingdatabetweenHyperionsystems.Thisfeature currentlyhaslimitedmappingfunctionality(onetoone). CalculationManager,agraphicalcalculationmanagerreleased inFusion11.xistiedintoEPMA. EPMAcanbedeployedonanapplicationbyapplicationbasis.
www.finitsolutions.com
15

EnterprisePerformanceManagement ( ) Architect(EPMA)UseCase
StrengthsandUseCase
AbilitytomanageHyperionmetadataforHFM,Planning,Essbaseinone interface. i f AbilitytoloadorpushmetadataintothedifferentHyperiontarget systems. FullintegratedwithSharedServices(rolesandexternalauthentication). Full integrated with Shared Services (roles and external authentication) EPMAisgearedtowardsHyperionapplicationmetadataonly. EPMA sdatafunctionalityexists,butisverylimited. EPMAs data functionality exists but is very limited EPMAiswebbased,soitcanbedifficulttomakemasschanges.Mayhave tomakethemofflineandimportchangesin. DRM EPMAdoesnotrequirealicense,itisincludedwithHFM,Planningand q , , g Essbaselicensing.
www.finitsolutions.com
16

Limitations

SimilaritiestoOtherIntegrationProducts g

Licensing/Other

DataRelationship g ( ) Management(DRM)
DRMisarobustmetadatamanagementtool. DRMdoesnotperformanydataprocessing(sourceto p y p g( HyperionorHyperiontoHyperion). DRMallowsfortheabilitytomanagethemetadataof HyperionandnonHyperiontargetsystems. DRMcanbeusedtopushmetadatadownstreamtosource systemssuchasgeneralledgersystemsordatawarehouses. ItcanalsobeusedtopushmetadataupstreamtoHyperion targetsystems. Doeshavesomemoreadvancedmetadatafunctionalitysuch ascustomattributes,versioning,andcustomexportfile functionality. f ti lit Itallowsfortheabilitytocompareacrossversions,toidentify whatchangeswereapplied.
www.finitsolutions.com
17

DataIntegrationManagement ( (DIM)UseCase )
StrengthsandUseCase
MostrobustmetadatamanagementtoolforOracleHyperion. AbilitytomanageanddeploymetadatatobothHyperionsystemsand nonHyperionsystems. UsecaseversusEPMAiswhethermetadatamanagementistoextend beyondjusttheHyperionapplications. beyond just the Hyperion applications DRMdoesnotperformanydataprocessing. DRMisclientbased. DRM is client based EPMA DRMdoesrequirealicense. DRMwasformerlyMDM. MDMwasoriginallydevelopedbyRaazaandpurchasedbyHyperion. MDM was originally developed by Raaza and purchased by Hyperion.
www.finitsolutions.com
18

Limitations

SimilaritiestoOtherIntegrationProducts Licensing/Other Licensing / Other

ERPIntegrator(ERPi) g ( )
ERPiisanewproductthatwasreleasedin11.1.1.3. Itprovidesaframeworkandstructureofconnectionsto p sourcesystemssuchasOracleEBusinessSuite,tobeusedto movedata/metadataintoFDM,ODIand/orEPMA.It currentlyhasadaptersforOracleEBusinessSuiteand PeopleSoftEnterpriseGL. P l S ft E t i GL ERPihasitsownrelationalstagingtablesfortheprocessing. Data/metadatacanbemovedfromthesourcesysteminto ERPiandthenprocessedintothecorrecttoolbasedonthe ERPi and then processed into the correct tool based on the specificusecase. ERPiwillhelpsimplifysourcesystemconnectionsamongthe variousOracleHyperionintegrationproducts. various Oracle Hyperion integration products

www.finitsolutions.com
19

ERPIntegrator ( (ERPi)UseCase )
StrengthsandUseCase
SourceadapterconnectionsforOracleEBusinessSuiteandPeopleSoft EnterpriseGL. i Abilitytomanagesourceconnectionsandpullmetadata/data tothen bedistributedtotheappropriateIntegrationproduct. Providesdrill backtosourcesystems. Provides drillback to source systems Currentlynoabilitytoconnecttodatawarehouses,SAP,etc. Newproduct,limitedusage New product limited usage Uniqueformanagingthedifferenttoolsanddrillbackcapability. SimilaritiestoFDMifdataprocessing,ODIformetadataonly. Similarities to FDM if data processing ODI for metadata only ERPidoesrequirealicense,itislicensedthroughFDM.

Limitations SimilaritiestoOtherIntegrationProducts Licensing/Other

www.finitsolutions.com
20

ClassicMetadataApproaches pp
ManyHyperiontoolsallowformetadatatobebuiltorloaded directlyintothem. HFMhasaMetadataManagerformaintainingtheHFM metadata. HyperionPlanninghasaDimensionManagertoolinPlanning webformaintainingmetadata. Essbasehasaconsoleformaintainingmetadata. Thesetoolsallowforthecreationandmaintenanceof metadata,butareonanapplicationbyapplicationbasis.

www.finitsolutions.com
21

ClassicMetadata UseCase
StrengthsandUseCase
Doesnotrequireanyadditionalproductstobeinstalled. Dependingonsystem,canbemorerobustthanothertools. LimitedtoperformingmetadataindifferenttoolsfordifferentHyperion applications. li i Limitedtoperformingmetadatawithinatoolonanapplicationby applicationbasis. Limitedversioningandauditcapabilities. Limited versioning and audit capabilities SimilartoDRM/EPMAintheabilitytomanagemetadataattributesand y pp hierarchiesandabilitytoloadmetadataintheapplication. Allclassicmetadatatoolsareincludedinthebaseproductlicensing.

Limitations

SimilaritiestoOtherIntegrationProducts Licensing/Other

www.finitsolutions.com
22

Efficiently Delivering Effective Solutions

OracleHyperionIntegration Products

OverviewofUseCase Overview of Use Case

www.finitsolutions.com

Data p UseCaseExample1
ExampleUseCase
Companyhas25differentledgersystemsandisdeployingHFM.They needatooltohelpthemmaptheChartofAccountsintoHFM. d l h l h h h f i

ProductOptions
FDM,ODI,DIMfordataprocessing FDM ODI DIM f d i

Considerations
FDMisthebestfitherebecausemappingwillbeneededandendusers willneedauserfriendlytooltoloadandvalidatetheirfinancialdatainto HFM. ODIandDIMarenotasgoodoffitsastheydonothavepre built ODI and DIM are not as good of fits as they do not have prebuilt validations,loadworkflowandmappinginterfaces.

www.finitsolutions.com
24

Data p UseCaseExample2
ExampleUseCase
CompanyhasonemainledgersystemsthatwillbeloadingdatatoHFM andHyperionPlanning.TheHFMandHyperionPlanningapplicationsare d i l i h d i l i li i designedoffoftheGLchartofaccounts,thusnomappingisneeded. Companywantstofocusonspeedofmovementbetweenapplications.

ProductOptions
FDM,ODIandDIM ERPi Sincenomappingisneeded,FDMisnotasclearofafit. QuestionswillcenteronwhetherFDMsprebuiltloggingandvalidation p gg g functionalitycanaddvalueoverODI/DIM.Volumesizemaybea considerationaswellduetoitcomingfromonemainledger. Dependingonthesourcesystem,ERPimayprovideabenefittodirectly connecttothesourcesystemandtomanagedrillback. connect to the source system and to manage drill back.
www.finitsolutions.com
25

Considerations

Data p UseCaseExample3
ExampleUseCase
CompanyhasaHyperionPlanningapplicationthatcontainsDepartment budgetandforecastinformation.ItalsocontainsanHFMapplicationthat b d df i f i l i li i h containslegalentitymembers.Oncethebudgetandforecastsare completeinHyperionPlanning,thedatawillneedtobemovedfrom HyperionPlanningintoHFM,asHFMwillremainthefinalbookofrecords forconsolidatedActual,BudgetandForecastinformation. f lid d A l B d dF i f i FDM,ODI,DIMandEPMA Whattypeofmappingortransformationneedstotakeplacebetween HyperionPlanningandHFM?
EPMA DIM and ODI are limited in their mapping If more mapping functionality is EPMA,DIMandODIarelimitedintheirmapping.Ifmoremappingfunctionalityis needed,FDMmaybeabetterfit.

ProductOptions

Considerations d

WilltheintegrationtoolperformanyvalidationsbetweenPlanningand HFM? IsFDMalreadylicensed?Ifnot,islicensinganissue? Is FDM already licensed? If not is licensing an issue?


www.finitsolutions.com
26

Metadata p UseCaseExample1
ExampleUseCase
CompanyhasasingleHFMapplication.Theyneedtomakemetadata changesfornewaccountsandentitieseachmonthintheirapplication. h f d ii h hi h i li i TheirHFMapplicationisataconsolidatedchartofaccountsanddifferent thanothersystems. Classicmethods,EPMA,DRM Atoolisneededtomanagethehierarchiesandmembers,soODIandDIM A tool is needed to manage the hierarchies and members so ODI and DIM arenotviable. Sincethechartofaccountsisdifferentandthiscompanyonlyneedsto manageonehierarchy,DRMdoesnotappeartobeagreatfit. IsthereadesiretousetheCalculationManagerwithFusion11.x?Ifso, I h d i h C l l i M i h F i 11 ? If EPMAwouldbetheonlyoption. Ifmetadataupdatesarenottooconsuming,classicmaybeeasiest.

ProductOptions Product Options


Considerations

www.finitsolutions.com
27

Metadata p UseCaseExample2
ExampleUseCase
CompanyhasmultipleHFMapplicationsalongwithHyperionPlanning. ThereissomeconsistencybetweentheprimaryHFMandPlanning h i i b h i d l i applications,butPlanningextendstheEntityandChartofAccounts.The companyiscurrentlyusingtheclassicmethodstomanagetheirmetadata. Thechartofaccountsinallproductsdiffersfromwhatisinthesource systems. Classicmethods,EPMA,DRM Atoolisneededtomanagethehierarchiesandmembers,soODIandDIM arenotviable. Sincemultipleproductsarebeingused,DRMandEPMAarestronger Since multiple products are being used DRM and EPMA are stronger considerations.ForDRM sincenosourcesystemintegrationwillbe performed,thefocuswouldbewhetheritsmorerobustfunctionalityis worththelicensecostoverEPMA.

ProductOptions

Considerations d

www.finitsolutions.com
28

Mixed p UseCaseExample
ExampleUseCase
AcompanyhasoneHFMapplicationwheretheyarecurrentlyusingFDM fortheloadofthreemainledgers.Thecompanyisimplementing f h l d f h i l d h i i l i HyperionPlanningforoneoftheirmainledgers.Planningisbasedonthe ledgerchartofaccounts.PlanningdatawillneedtobemigratedintoHFM followingthecompletion.ThecompanydoesnotownInformatica. Data FDM,ODI,DIM,ERPi Metadata ODI,DIM,ERPi SinceFDMislicensed,itcanbeusedforloadingdatatoPlanning(Actuals) andthenfromPlanningtoHFMasvalidationscanbeusedinFDM. SincethePlanningapplicationwillbebuiltoffoftheledgerchartof Si h Pl i li i ill b b il ff f h l d h f accounts,atoolcanbeusedtobuildthehierarchiesoffoftheledger. SincethecompanydoesnotownInformatica,ODIwouldbethebetter choiceiflicensingisanissue. ERPimaybeanoptioniftheGLissupported.
www.finitsolutions.com
29

ProductOptions

Considerations

FinitContacts

Efficiently D li i Effective Solutions Effi i tl Delivering Eff ti S l ti

ThankYou!
RobCybulski FinitSolutions rcybulski@finitsolutions.com 2158802025

www.finitsolutions.com
30