essbase zola att july09

19
<Insert Picture Here> Essbase 11.1.1.3 (Zola) Advanced Team Training Aneel Shenker – Essbase Product Management July 28th, 2009

Upload: rams08

Post on 25-Nov-2015

48 views

Category:

Documents


3 download

DESCRIPTION

Essbase Zola ATT JULY09

TRANSCRIPT

  • Essbase 11.1.1.3 (Zola) OverviewBugfixesLocalized release as 11.1.1.2 (Dickens)Calc Manager support for BSOFusion Financials and E-Business SuiteData and Metadata LoadingDrill-through/ drill-Back

    See also ERP Integrator ATT recording July 22nd, 2009

  • Unified Calculation ManagementEssbase and Classic EPM AppsCalculation ManagerSingle interface for Hyperion Planning, Financial Management and EssbaseGraphical flow provides better understanding of calculation processRe-usable rules to share among applications Central repository of all calculation objectsFor Essbase BSO, deployment step will push the generated calc script to the Essbase server.

  • Drill-through OverviewProvide data drill back capabilitiesERP IntegratorDrill-through to Oracle E-Business Suite (EBS)Source Application EPMACreates Planning or HFM cubesNon-planning Essbase not supported in ZolaTarget URL ERPI landing pageFusion FinancialsSource Application Fusion FinancialsCreates Essbase cubesTarget URL Fusion GL

  • Drill-through OverviewEASDefine Drill through definitions using MaxLEBSERPI

  • FDM ERP Integrator Process.Fact Data

    Shared Staging TablesERP Integrator ERP Integrator EPM AppsReportingSmartviewFDME-BusinessSuiteGeneral Ledgers

    E-BusinessSuiteDrill BackDrillDataFile-based Data or SQL Pull SAPEPMAMetadata & DataPeopleSoft Source TargetDimensions & HierarchiesOracle DataIntegrator

  • Drill-through Essbase PersistencePersisted in .db file

    No outline restructure on DT editing

    Dynamically use the latest DTs

    Database copy handles .db files

  • Creating Drill-through definitionsFusion Financials or EPMA will create Drillable Essbase cubes by storing drill through XML URLs Components of Drill-through definitions: (a) Name: Name of the drill through definition (b) XML containing Drill through-URL. Contains URL Link which will is used for drill-through to landing page. (c) URL Level-0 Flag: A Boolean flag indicating whether drill through only is available at level 0. (d) Drillable region definitions: Symmetric regions defined using CALF functions. - Multiple entries text input (Ex: table), each entry requires member set + memberCALF functions are metadata functions that can be used for security definitions or for specifying drillable regions for DT.

  • ExampleURL Name: Drill through to Fusion GL

    URL XML:

    URL Level-0 Flag: True

    Drillable region: region 1:current_assets, Oct-08region 2:liabilities, @Idescendants(Yr 08)

  • Drill-through XML - BabelfishXML contains drill-through URL etcBabelfish compliant Clients resolve the URL links

  • Babelfish URL LinkExamplehttp://glserver:port/fusionapp/Assetsdrill.jsp?$SSO_TOKEN$&$CONTEXT$&$ATTR(ds,pos,gen,level.edge)$Substitution variablesServer, port variablesSSO tokenPOV context (fully qualified names)Grid specific variable like edge, positionGen, level informationLanding page resolved into fully qualified URLIntersection, layout etc

  • Main API ChangesNew C API for managing Drill-through definitionsCorresponding Java API

    Clients get cell drill through definitions through Babelfish XML

  • Query API ChangesGrid APINew query option for color coding (ESSG_OP_GET_DRILLTHRU_URLS)New flag for GL URL drillable cells (ESSG_CA_GLDT)New API EssGGetIsCellDrillable

    MDX APINew query option for color coding New flag for GL URL drillable cellsNew API EssMdxIsCellDrillable

    No support for Report Writer

  • Clients SupportedSmart View through APSPlanning forms through Planning FR through ADM driver

    No support for Excel Addin

  • Administrative InterfacesEssbase Administration servicesMaxL scripting

  • EAS Drill-through ManagementRight-click on db to edit DT definitions

  • EAS Drill-through Management

  • New Drill Through MaxL statements The following MaxL statements are available for managing drill through definitions.

    create/alter drillthru app.db. urlName using xml_file temp.xml on level0 only ; - For creating or editing drill through definitions

    Drop drillthru app.db.urlName; - For deleting drill through definition

    Display drillthru app.db; - For viewing all available drill through definitions on a particular database

    Display drillthru app.db.urlName; - For viewing a drill through definition

  • Questions & Answers

    This is an overview of the new features found in Essbase Zola.First of all, there are a number of bugfixes across all products. Secondly, it is a localized release like the Dickens release.Thirdly, Calc Manager, which is a graphical interface for defining calculations, is now supported against Essbase BSO cubes. This is strictly not a feature being delivered by the Essbase team, but it is something we mention to customers when we discuss roadmap, so wanted to include it very briefly here.Finally the major driving feature for the Zola release is the ability from financial applications to create drill-through/ drill-back definitions in Essbase. We are going to cover this in more detial.*As mentioned calc manager is a tool that makes it easier for users to define calculations certain EPM apps, and now also Essbase BSO cubes. It enables the user to graphically design Business rules and calculations, and since Calc manager stores them in a central repository, they can be shared amongst applications.From the Essbase point of view, rles result in calc scripts getting deployed to the Essbase server.*- ERPI will populate Planning cubes based on its source systems such as EBS and Peoplesoft via EPMA- ERPI will generate an XML representation of drill-through URLs and populate this in the Essbase structure.- Similarly Fusion Financials will populate Essbase cubes, generate and store drill-through URLs in Essbase.

    EBS consists of Oracle CRM Oracle Financials Oracle HRMS Oracle Logistics Oracle Mobile Supply chain Applications Oracle Order Management Oracle Transportation Management Oracle Warehouse Management Systems

    Oracle financials set relies on the Oracle RDBMS infrastructure and includes applications such as: Oracle Assets Oracle General Ledger Oracle Payables Oracle Receivables Oracle Cash Management

    Add EBS as a source for ERPI.Only Essbase cubes that are managed through EPMA. (limitation in Zola release). Register Source systems in ERPI by adding details of Oracle Data Integrator, ERPI, and source system. Map segments or chart fields in the source to dimensions in the target. Run dimension extract to import members and hierarchies into EPMA or classic applications. Define data rules. Run data rules to extract data from source system and push into target applications. If using FDM and ERPI togetherLoad metadata via EPMA or classic applicationLoad data via flat file through ERPI and then use the flat file in FDM to push the data into the target application Drill back through web forms, Smart View, or Financial Reporting to the source system either through FDM or the ERPI.

    *Drill-through definitions will be stored in the DB file. For EIS DT definitions are stored in the catalog as well as the Essbase cube, but with a static binding to the cells.For Studio DT definitions are stored in the catalog with a dynamic binding to the cells.From an Essbase point of view, this is how the Essbase DT definitions gets created:Fusion or EPMA creates Essbase cubes and stores the DT definitions in the cube.

    What gets stored in the cube is following:Name of DTXML containing the DT URL and other information conforming to the Babelfish protocol.A flag indicating whether DT is only available for level 0.Definition of drillable regions using metadata functions. New functions called CALF functions has been added.

    CALF functions are metadata functions. Can be used for security definitions or for specifying drillable regions for DT.Assets liabilities = equity

    Current assets for this month where as for liabilities you are interested in over this whole year.Babelfish compliant XML allows BBF compliant clients (fx Smart View) to resolve XML URL. Landing page will get context. Resolves to fully qualified URL. Intersection, grid layout etc. Protocol between client and landing page application.

    Allows BBF compliant client to resolve XML URL. Landing page will get context. Resolves to fully qualified URL. Intersection, grid layout etc. Protocol between client and landing page application.Viewing/ finetuning for administrator.