Hey, "Classic" Metadata Managers: Want to Give EPMA a Try?Erich RanzFinit Solutions

Finit Solutions Who We AreWe strongly believe that Service + Solutions = Maximum Value

ServiceCompensation model - based upon client satisfaction with consultants work, not utilization / chargeability.No external owners - Finit partners are involved in every full-cycle implementation.Employees - not contractors.

SolutionsFinit consultants are Hyperion product experts who enjoy designing, building and deploying great solutions, applications and processes. We are CPAs and MBAs who have extensive SEC and managerial reporting experience.Finit works closely with Oracle development on product strategy and beta testing.Finit Solutions specializes in the design and implementation of Oracle EPM solutions.Superior Finance IT Services

Finit Solutions Why Believe in Us?Our client service approach has led to 100% customer satisfaction for every Finit client (200+ and counting) for every Oracle Hyperion project (over 350 and counting).Our record speaks for itself ask our clients. Our clients truly separate marketing from fact:

Live demo of entire conversion processClassic metadata managementWhen does converting to EPMA make sense?Conversion methodsMetadata management in EPMAApplication management in EPMAThis sucks - converting back to ClassicAgenda

Demo (done in VM)

MethodsHFM Desktop ClientExcelApp/XML File

Classic Metadata ManagementAdvantagesFamiliarCan be done offlineApp copy is easier

Improvement AreasChange loggingVisibility of metadata

Transaction loggingMetadata visibilitySharing metadataData synchronizationOracle trainingJust curiousWhy Convert to EPMA?

No indication Classic is being retiredNo need to share metadataSmall number of apps/productsProven processes already in placeWhy Remain Using Classic?

Rebuild from application elementsTime consumingCreates a new app / Requires a data copyRequires some EPMA knowledgeTransform Classic to EPM Architect WizardRuns quicklyTransforms application in-placeRequires little EPMA knowledgeConversion MethodsNot entirely accurate!

Use EPMA File Generator to obtain ADS fileFrom HFM FilesProfileSecurityMetadataFrom HFM ApplicationAdmin loginWorkspace URLHFM Web URLApplication + Cluster names

E:\Oracle\Middleware\EPMSystem11R1\products\Foundation\BPMA\EPMAFileGenerator\binCan be run from the server or local pc (copy contents of bin folder to local pc and run exe file)

Rebuilding From App Elements

EPMA File Generator Example

Roles RecommendedHSS EPMA AdministratorHSS Financial Management ManagerNow that we have the ADS fileRebuilding From App ElementsFrom Workspace: Navigate > Administer > Application LibraryFrom App Library: File > New > ApplicationEnter application settings:Enter new app nameType = ConsolidationEnter new app descriptionCreate Blank Application = Yes (check)From Dimension Library: Enter properties for new application (copy from old metadata)Default CurrencyDefault RatesEtc

Now that we have the ADS file (continued)Rebuilding From App ElementsFrom Dimension Library: File > Import > Create ProfileProfile Name = ImportFullApp (can be anything)Import Type = Flat FileDescription = Profile to import full ADS file exported from EPMA File GeneratorApplication = Select your new EPMA app from the listFileName = Brows to the ADS file created from the EPMA File GeneratorFile PropertiesColumn Delimiter = | (pipe via the EPMA File Generator)Remove Double Quotes on Strings = Yes (check)Remove White Space = Yes (check)Suppress Transaction Logs = Yes (check)Map DimensionsCreate dimensions for the non-mapped dimensions = Yes (check)Leave everything else defaultDimension Mapping Leave everything default

Now that we have the ADS file (continued)Rebuilding From App ElementsDo you want to execute the profile now? Yes!From the Application Library: Right-click new EPMA app > Deploy > ApplicationNavigate > Applications > RefreshNavigate > Applications > Consolidation > Open your new EPMA app!Copy in data, grids, security, rules, member lists, etc., via Copy App UtilitySelect existing Classic app to copy fromKey in the name of the new EPMA app to copy toProvision user access in HSSDONE!

Roles RecommendedHSS EPMA AdministratorHSS Financial Management ManagerTransform Classic to EPMA WizardFrom Workspace: Navigate > Administer > Transform Classic to EPM ArchitectFrom Welcome screen: Click NextFrom Application Summary: Click NextFrom Application Selection: Select app(s) to transform, click NextFrom Transformation Summary: Click FinishFrom Job Console: Review Transform Classic to EPM Architect LogDONE!

Note: App is deployed automatically and dimensions are set as Local

In-place transformation & real world optionsLarger production appBack up prodCopy prod to devTransform app in devTest EPMA appDelete Classic prod appCopy EPMA dev app to prodApply security to EPMA app in prod environmentTransform Classic to EPMA Wizard

In-place transformation & real world optionsSmaller production appBack up prodCopy prod to prod (new app name)Transform new appTest EPMA appDelete Classic appRename EPMA appApply security to EPMA appTransform Classic to EPMA Wizard

In-place transformation & real world optionsGo for it!Back up prodTransform prod app in placeNo provisioning changes needed

Transform Classic to EPMA Wizard

Local/Shared DimensionsMetadata VisibilityMetadata ManagementDimension LibraryGrid EditorLCM Export/ImportEPMA File GeneratorTransaction LoggingData SynchronizationTask Flows

EPMA Features

Local Dimensions originate within a single application and can be created directly within the application or as a copy of a dimension from the Shared Library or another dimension in the application. Local dimensions are separate dimensions and do not inherit any changes made to the dimension in the Shared Library.The initial copy of the dimension from the Shared Library copies the entire dimension. Any subsequent actions, such as adding new members, are performed within the application.If you make changes to the shared dimension that was used to create the local dimension, you have the option to explicitly merge any further changes to the dimension at the application level.Local Dimensions

Shared dimensions are available to all applications and can be individually linked to one or more applications. Changes made to the dimension in the Shared Library are automatically inherited to every application sharing that dimension. All types of modifications can be made to the dimension within the Shared Library but only certain types of changes can be made to the shared dimension within the application.Once a dimension has been included in an application as a shared dimension, changes can be applied to the shared dimension within the application to handle exceptions that may only be relevant to that application. These types of changes include:Member filtersProperty value overridesUsing parent members as baseStructural changes for shared dimensions, such as adding or moving members, can only be performed within the Shared Library.Shared Dimensions

Account ExampleDo in order!Alias (set default member in system properties)SecurityClassCustomsICPAccount

Note: Dimension associations can become lost when doing these out of order. Once the association is lost, consolidation property data may have to be re-entered.Converting Local Dimension to Shared

You create dimension associations to assign security classes, currency, and attributes to dimensions and their members. For example, if you associate an entity dimension with the security class and currency dimensions, the associations are inherited by all members of the entity dimension.You can also create dimension associations in a flat file. Existing associations are automatically created and activated when you transform an application from Classic to EPMA.

Note: It is impossible to create an association from a shared dimension to a local dimension. If you attempt to create this association, this would result in errors in the downstream products.Dimensions Associations

Dimensions Associations

Remove existing shared dimensions (if any)Extract ADS fileDelete existing local dimensionsCreate import profile and import ADS file into Shared LibraryDrag shared dimensions into local libraryActivate all associationsRe-set Period to Local (detach dimension)Deploy appdata is still there!Sharing All (most) Dimensions at Once

Dimension OwnerEdit dimension structure or propertiesCopy dimensionsSynchronize dimensions from or to dimensionsAdd dimensions to applicationsRemove dimensionsDelete dimensionsDimension WriterEdit dimension structure or propertiesCopy dimensionsSynchronize from or to dimensions (IF Writer in both from and to dimensions)Add dimensions to applications (IF also App Creator or App Admin)Dimension ReaderCopy dimensions (IF also Creator role in target of copy)Add dimensions to applications (IF also App Creator or App Admin)

*Applies to Shared Library or App Admins in Local LibraryMetadata Visibility*

Dimension Reader Example

Used for ongoing metadata managementUsed for changing properties and adding members in small numbersCan drag and drop, cut and paste and reorder childrenEasy insert shared members functionView Shared and Local LibrariesWeb based Dimension Library

Good for changing attributes on several members within a single dimension Create custom grids using Grid Editor WizardMembers and attributes are selected as neededNo function for base members / no member listsGrids cannot be savedGrid Editor

Tabular grid-based interfaceCan copy/paste within editorCannot copy/paste multiple cells from ExcelGrid Editor

Lifecycle ManagementLCM Export/Import

ADS Export FormatCan be re-importedCan be used in an existing import profileCan be used to create a new import profileCan be used with shared and local librariesLCM Export/Import

Copy contents to ExcelText to ColumnsAdd FormulaCopy contents to TextLCM Export/Import

Oracle provided utility to create ADS files in ExcelEPMA File Generator

Excel Add-inEPMA File Generator

Profiles include important information about the dimensions to be importedSource Options: Flat file, Interface Tables, DRMTarget Options: Shared Library or Existing EPMA applicationImport Profiles

Mapping and Load Methods

DeployDuplicateAs New ApplicationAs Deployed Application with option to copy dataDeleteCompareTo Shared Library To Deployed ApplicationDiagnosticsApplication Management

All operations performed in the Dimension Library are recorded in transaction logs. Logs can be filtered by date, application, dimension, and property. Each operation is recorded with a time stamp, the user name, the type of action performed, and other relevant information.Transaction Logging

The Data Synchronization module enables you to create synchronizations between HFM, Planning, and Essbase as destinations, and the following sources:HFMPlanningEssbaseExternal source (flat file)Interface tableData Synchronization

Execute Data SynchronizationImport DimensionFrom Flat FileFrom Interface TablesConsolidation RedeployAnalytic Services RedeployPlanning RedeployProfitability RedeployTask Flows

Delete existing EPMA shell in target systemUse LCM to migrate EPMA metadata to targetUse HFM application copy utility

Copying Apps Between Environments

Running the HFM copy application utility on an existing EPMA application will prompt to convert it back to Classic. If an EPMA app of the same name exists as the target, it must be deleted first. Converting Back to Classic

Erich Ranzeranz@finitsolutions.comwww.finitsolutions.com

Please fill out an evaluation!Questions and Answers

When Performance Management Architect imports an application, it is imported as an .xmlfile (metadata.xml). Performance Management Architect runs the transformation andcreates an .ads file from the metadata.xml file. Typically, this file is used for troubleshootingpurposes. For extremely large applications, we recommend that you do not select this option.*