oracle hfm beginner's guide part iii

http://learnhyperion.wordpress.com

©Business Intelligence Solution Providers learnhyperion.wordpress.com [email protected] 1

Oracle Hyperion Financial Management

11.1.1.3 Beginner’s Guide

Part III

Provided By: BISP Created By: Rupam Majumdar

http://bispsolutions.wordpress.com Amit Sharma

[email protected] BISP Team


http://bispsolutions.wordpress.com/

mailto:[email protected]

http://learnhyperion.wordpress.com/



INTRODUCTION TO EPMA

WHAT IS EPMA?

Enterprise Performance Management Architect (EPMA) enables administrators to

manage, create, and deploy Hyperion applications within one interface. EPMA Provide

a central repository for metadata creation and maintenance across Oracle Enterprise

Performance Management Applications.

Ø EPMA can be used with Hyperion Planning, Hyperion Financial Management

(HFM), Essbase (ASO and BSO), Profitability and Cost Management applications.

Ø EPMA can be used to facilitate data movement across applications and Oracle

EPM products

Ø EPMA metadata deployments can be run on demand or in batch mode (lights

Out metadata management updates).

Ø Metadata updates can be run as a merge (addition) or replace.

Ø Can do add, moves, modify properties, etc.

WHY EPMA?

Streamline metadata management

Ø Improve synchronization across applications and Oracle EPM products

Ø Provide a single point of maintenance for metadata updates



Ø Can be used to reconcile dimensions (historic versus current) before

deployment.

Facilitate data movement

Ø EPMA has data movement capabilities to move data across applications and

products.

Reconcile hierarchies before deployment

Ø Provide information regarding differences between selected application and

current deployed application.

Alternative to Hyperion Application Link (HAL)

EPMA - Overview

Oracle Hyperion EPM Architect, Fusion Edition is a feature of Oracle's Hyperion®

Foundation Services and is integrated with Oracle Hyperion Financial

Management, Fusion Edition, Oracle Hyperion Planning, Fusion Edition, Oracle

Essbase, and Oracle Hyperion Profitability and Cost Management, Fusion Edition.

Performance Management Architect enables administrators to manage, create, and

deploy Hyperion applications within one interface.



What Does EPMA Do?

Application Management

Ø Application creation wizard

Ø Shared versus local dimensions

Hierarchy Management

Ø Alternate hierarchies

Ø Attribute dimensions

Ø Member formulas

Ø Application specific metadata (start and end dates in scenario)

Ø User defined attributes (UDA’s)

Ø Custom top members

Ø Intercompany partner (ICP)

Ø Currency assignment to entity

Ø Security class



How to Use EPMA?

Manual Entry

Ø Can maintain library and application manually

Ø Not recommended for mass metadata entry loads

File Load (ADS format)

Ø Load dimensions via text file (predetermined format)

Ø Excel templates develop by Emerging Solutions

Ø On demand or batch process

Interface Table Load

Ø Load dimensions via interface

Ø On demand or batch process

Ø No manual modifications

EPMA Components

EPMA actually consists of a number of components:

Ø A Dimension Library, for holding metadata on the shared and local

dimensions used by EPMA-enabled applications

Ø An Application Library, for holding definitions of the various Essbase,

Planning and HFM applications EPMA manages



Ø A Data Synchronization Engine, for loading data (numbers) into EPMA-

managed applications

Ø Workspace, Security and Taskflow elements

Dimension Library

Ø View and organize dimensions used by all applications in your Hyperion

environment

Ø Create/edit dimensions, members, and their properties for all application types

Ø Share dimensions and properties across application views

Ø Allow filtering and exception handling at application level

Ø Bulk import of dimensions using merge or replace

Ø Download transaction log to audit changes



Data Synchronization

Ø Transfer data from external sources or between Hyperion applications

Ø Graphically manage data flows for all applications in your Hyperion

environment

Ø Define mappings between data sources and targets

Ø Validate and execute synchronizations

Ø Enables multi-source and multi-stage processes

Job console

Ø Track jobs performed by users or batch operations

Ø Query and filter job listing by attribute



Ø View status and statistical information for each job

Ø Access detailed job results via job attachments

Calc Manager

Ø One tool to create calculations for FM and Planning

o Common interface to design calculation rules

Ø Easy way to create complex financial calculations

o Graphical flow provides better understanding of calculation process

o Re-usable rules to share among applications

Ø Central repository of all calculation objects

o One place to maintain all calculation rules

o Custom folders for easy navigation



Ø Central repository of all calculation objects

Ø Objects are organized by Application and by Calculation Type

Ø Within each object type (i.e. Rule set, Rule, Component) user can easily drill

down to next level of objects.

EPMA Application

Hyperion tends to create lots of services anyway (at last count, including Planning,

there were 31 Hyperion-related services running on my Windows machine) but as

you can see from the screenshot above, EPM Architect and Calc Manager take up

eight of their own.



EPMA has its own repository that holds all the metadata on the applications it

manages, and as with classic planning applications you define the dimensions

there first and then deploy them to Essbase. To start off them, as with the Classic

Application Wizard you can define the basics of the Planning application using a

wizard in EPMA, where you can say whether the application has one or more

plans, whether it’s multi-currency, what time periods it uses and so on.

EPMA WORKFLOW

It’s probably worth taking a moment out to understand how data and metadata

flows through Planning when EPMA is involved. As you can see from the

diagram below, data and metadata from the various sources goes first into

interface tables or files before being accessed by EPMA, which then takes this data,

maps it and then uses it to construct the applications that you want to create



Creating EPMA Application

We need to provide all these information to create a sample application



After successful Creation of Application



Workspace Navigation

Workspace is a web client that provides the user interface for viewing and

interacting with content created with Hyperion EPM application.

Workspace provides a single EPM interface. It provides users these access and

interacting capabilities for these components:

Ø Planning application tasks.

Ø Financial Management application tasks.

Ø High-performance, multidimensional modeling, analysis, and reporting with

Essbase.

Ø Financial reporting for scheduled or on-demand, highly formatted, financial

and operational reporting from most data sources, including Financial

Management and Planning.



Ø Interactive reporting for ad hoc relational queries, self-service reporting, and

dashboards against ODBC data sources.

Ø Production reporting for high volume, enterprise-wide reporting Web analysis

for interactive, ad hoc analysis, presentation, and reporting of multidimensional

data.

Ø Enterprise metrics for management metrics and analysis presented in easy-to-

use, personalized, interactive, dynamic dashboards In addition, Workspace

provides access and interaction with other published content, such as Word or

Excel documents.



Administer menu: Architect



LOGIN

To start with Hyperion Financial Management as Web Client we need to Log-in

http://<servername>:19000/workspace

The default credentials are

Username: admin

Password: password

The recently used application is showing. We can open it or can create new

application. To see newly created application in Win32 (Desktop Client) we need

to refresh the Application List

Workspace



Ø Tasklists provide quick access to frequently used tasks and documents.

Ø Data forms enable you to enter data for predefined views, such that specific

periods & accounts.

Ø Data Grid enables you to use a spreadsheet like application to enter, edit and

view data in Financial Management application.

Ø Reporting enables you to view various Financial Management reports, such as

journal reports and intercompany matching reports.

Ø Links enable to create link to Web pages or some documents.

Ø Related Contents enable you to incorporate Workspace content directly into a

financial management task lists.

Ø Custom Documents enable you to attach one or more documents to cell in data

grids , data forms and Process Management Cells



Working with MetaData : Web Procedure

Perform the following tasks to load metadata

1. Create an import profile

2. Specify load options

3. Map dimensions in the load file to dimensions in Master View

4. Map columns in the load file to dimension properties in Master View

5. Run the import profile

Login to Workspace

We need to login to Workspace and then Open a application

http://[servername]:19000/workspace

Login with Standard Credential:

User: admin

Password: password



1. Creating Import Profiles

Ø Select File > Import > Create Profile.

Ø You can select either Flat File or Interface table as the Import Type. (Interface

tables are discussed in a later topic in this lesson).

Ø After you create the profile, a wizard is launched that walks you through the

tasks for defining load

options, mapping

dimensions, and

mapping properties.

Before Loading MetaData ,

We Need to Load Security

File

/*Hyperion recommends that you add Financial Management to the exceptions for

your Web pop-up blocker. When you perform some Financial Management tasks,

such as loading data on the Web, a status window pops up showing the task

status. If you have a pop-up blocker enabled on your computer, the status window

is not displayed.*/



To load application security

1 Open the application.

2 In Browser View, expand Tasks, and select Load Tasks.

3 Select Load Security.

4 For Security File, enter the name of the file to load, or click Browse to find the

file.

Note:

Application security files use the SEC file extension.

5 For Delimiter Character, enter the character used to separate information in the

file. These characters are

Valid: ~ @ # $ % ̂ & | : ; ? \

6 Optional: Select Clear All Security Info Before Loading to clear security

information for the application before loading the new security information.

Caution! You can use the Clear All option only if you have been assigned the

Application Administrator and Provisioning Manager roles. Also, if you use this



option, you will have to reprovision users, as all users (including the user doing

the clear) will be removed in this process.

Click LOAD

To load metadata: Web procedure

Ø Open the application.

Ø In Browser View, expand Tasks, and select Load Tasks.

Ø Select Load Metadata.

Note: This option is only available if you open a Classic Financial Management

application.

4 In the Metadata File text box, enter the name of the file to load; or click Browse

to find the file.



If you are extracting to an APP file, in the Delimiter Character text box, enter the

character to be used to separate the metadata in the file.

Delimiter characters are necessary only for ASCII files with the APP file extension.

Delimiter characters are not necessary for XML files. The following characters are

valid: , ~ @ # $ % ^ | : ; ? \

6 Optional: In the Load Options section, select Clear All Metadata Before Loading.

Note: If you select this option, you cannot select elements in the Metadata Options

section.

7 Optional: Select Check Integrity to check the metadata file against the data in the

current application. It is highly recommended that you select this option as it

ensures that the application is not adversely affected by the metadata in the load

file.

Note: If integrity errors occur, they are written to the metadata log file and no

portion of the file is loaded into the application



8 In the Load Options section, select one of the following load methods:

Merge

Replace

9 In the Metadata Options section, select the types of metadata to load.

Use the Select All and De-select All buttons to quickly select or clear all metadata

types.

Choosing Replace or Merge

When you map a dimension in the load file to an existing dimension in Master

View, you can merge or replace members:



Mapping Dimensions

You can create a new dimension in Master View, or you can map a dimension in

the load file to an existing dimension in Master View. For each dimension in the

flat file, a dropdown list displays dimensions of the same dimension class in

Master View. You can select New Dimension, or you can select a Master View

dimension to which you want to map the flat file dimension.

If a dimension name in Master View exactly matches a dimension name of the

same dimension class in the load file, the matching dimension is the default

selection.

Mapping Properties

For each column for a dimension in the flat file, a drop-down list displays

properties for the same dimension class in Master View. We select the property to

which to map the column. If a property name in Master View exactly matches a

property name in the load file, that property is mapped by default.

Select the Ignore Nulls option for a property if you want blank values for a record

in the load file to be ignored.



Running Import Profiles

After creating a profile, you can run it from the Import Dimensions dialog box.

To access the Import Dimensions dialog box:

1. Select File > Import > Import Dimensions.

2. You must select a file to upload each time you run an import.



Viewing Job Status

You can select Navigate > Administer > Job Console to view the status of the

metadata load. Job Console shows the current job status and the percent

completion. You can click the Import Results link to view an error log for each

dimension included in the load.





Loading Metadata with Interface Tables

Architect interface tables are database tables used to import metadata from

external systems into the Dimension Library. They represent an alternative to flat

files.



1. Create a Architect interface database using a relational database Oracle.

2. In the interface database, you create tables that correspond to the sections in

a metadata flat file. For example, you would create a database table for

dimension associations with fields for Base Dimension, Property, and Target

dimension, similar to the Dimension Associations section of a flat file.

3. After you create the interface tables, you load data from you external

systems into the tables.

4. You can then import the data from the interface database into the Dimension

Library using an import profile, following the same procedure as with flat

files.

Prerequisites

1. Have access to the Configuration Utility.

2. Have Administrator access to Performance Management Architect.



3. Have access to data sources containing dimension metadata.

Configuring Interface Data Sources

Configuring data sources is required if you want to use interface tables in

Performance Management Architect. Interface tables provide a database interface

that enables you to import of metadata and data from external systems into the

Dimension Library.

Click Start > Programs > Hyperion > Foundation Services > Configuration Utility

In the product selection panel, under Hyperion System 9 BPM Architect,

select Interface Datasource Configuration



Creating Interface Table Definitions

Log on to Performance Management Architect - Data Synchronization and

select File > New > Data Interface Table Definition.

In the Data Interface Area Mapping Wizard, make the required selections and

click Next. For the interface area, select the interface table data source you created.

Next, select the table and column that contains the values to import.

Select a column, enter a dimension name, and click Next.



Enter a name and description for the interface area definition, and click Finish.

THE Interface tables structures



Importing Dimensions from Interface Tables

Before importing dimensions into the Dimension Library, you must create and run

a data synchronization or an import profile. Data synchronization enables you to

synchronize and map data between Hyperion applications, interface tables, and

external files. Profiles include important information about the dimensions to be

imported such as new dimensions, whether to merge or replace existing

dimensions, and dimension properties. You execute the profile to import

dimensions into the Dimension Library.



Select Hyperion Data Interface Area as the source type, and click Next.

Select a source data interface definition, and click Next..

Select an available destination application, and click Finish.

Drag a source dimension to a destination dimension to manually assign or change

mappings.



Select File > Import > Create Profile to create an import profile in the Dimension

Library

Enter the profile details and click OK. For Import Type, select Interface Tables as

the Import Type.

Select Create dimensions for the non-mapped dimensions with the source

dimension name, and click Next.



Review the mapping options, and click Finish.

When prompted to execute the profile, click Yes.



Click Close



