1z0-533 Exam Dumps - Oracle Hyperion Planning 11 Essentials

Scenarios and versions are the basis of the planning review cycle. Entities submit planning data

for a particular scenario and version. The combination of scenario, version, and entity is called

a planning unit and is the basic unit for preparing, reviewing, and approving plan data.

B: Oracle Hyperion Essbase Administration Services (Essbase Administration Services) software is a robust, cross-platform graphical user interface that makes Essbase administration tasks easy to perform.

Administrators can simultaneously view and edit properties for multiple Hyperion Essbase databases, applications, users, scripts, and other objects from a single intuitive view.

Essbase Administration Services also provides wizards, editors, dynamic menus, and other tools to help you implement, monitor, and maintain analytic and enterprise performance management applications.

C: Enterprise Performance Management Architect (EPMA) enables administrators to manage, create, and deploy Hyperion applications within one interface. EPMA can do adds, moves, modify properties, etc.

D: Oracle Hyperion Data Relationship Management (DRM) is an enterprise change management solution for building and retaining consistency within master data assets despite endless changes necessary to support underlying transactional and analytical systems.

A: Planning is available within Oracle Enterprise Performance Management Workspace

B: Oracle Enterprise Performance Management Architect (EPMA) is accessible from the EPM Workspace.

D: The Shared Services Web application and the LCM utility communicate over TCP/IP to the EPM Workspace Core Service.

Note: One of the smartest tools Oracle/Hyperion ever integrated into its product suite was the migration utility. Overtime this has evolved to the LifeCycle Managment utility or LCM for short. Actually Oracle/Hyperion has taken it even one step further by calling its fully integrated migration tool the BI+ Artifact LifeCycle Management utility even though they have retained the same acronym, LCM.

E: Calculation Manager was introduced in EPM workspace common Foundation Services in release 11.

Single interface for both Hyperion

Planning and Financial Management

– Graphical flow provides better

understanding of calculation process

– Re-usable rules to share among

applications

Planner:

The majority of Hyperion Planning users are planners who are responsible for department or project budgets. They conveniently work over the Web or the Spreadsheet Add-in to:

Enter, submit, and view data

Use pre-defined policies, procedures, routines, reports, and worksheets to enter, analyze, and report on application data

Interactive User:

Examples of an interactive user include a department head, sales director, or unit manager who submits budget information and data for approval. Interactive users can enter and view data. They can also create, maintain, and initiate:

Data entry forms on the Web

Spreadsheet Add-in worksheets

Reports using Hyperion Reports

Integrations using Hyperion Application Link

Business rules using Hyperion Business Rules

The required dimensions for a Hyperion Planning Application.

Required Dimensions:

Period

Year

Scenario

Version

Entity

Account

Other Dimensions:

Alias

Smart Lists

Multicurrency applications require two additional dimensions:

Currency

HSP_Rates

Note:

Period and Year

You specify a time period and year for each value. Base time periods, such as months, are automatically rolled up to summary time periods, such as quarters and total year. As administrators, you specify base time periods and distribution of weeks in the Period dimension when you create application views. You use the year dimension to add years to the calendar.

Scenario and Version

The Scenario and Version dimensions represent the broadest categories of data in your application. Scenario describes the type of data that a plan includes, such as budget, actual, or forecast, as well as the time span that the plan covers.

Version allows for flexibility and iterative planning cycles. For example, your application could have two versions, Working and Final, for each scenario. You can also use versions to model possible outcomes based on different assumptions about interest rates, growth rates, and so on. For example, your application an have a Best Case and Worst Case version for each scenario.

Entity

The Entity dimension represents the flow of Planning information through your organization. You can establish an entity for each group or responsibility center that submits a budget plan. These units could be geographic regions, departments, or divisions, depending on your requirements.

Account

The Account dimension specifies the data to be collected from budget planners. You can establish accounts for all budgeted items to the necessary level of detail. Examples of accounts are Rent Expense and Cash on Hand.

Currency

You can plan in one or more currencies. The Currency dimension identifies the currency in which values are displayed. In the Currency dimension, you set up the following categories:

* Which currencies are used by applications and reporting

* How currencies are displayed in reports and data forms

* How currencies are translated into other currencies

* When currency conversion occurs

HSP_Rates

This dimension contains a member to store exchange rate values for each currency. It also contains a member for input values and currency overrides.

Alias and Smart Lists

In addition to the required Planning dimensions, you must set up an Alias dimension if you want to assign aliases to dimensions such as Account or Entity. If you want to use Smart Lists in your application, you must set up a Smart List dimension.

A: To develop a calculation script that exports a subset of data, you first specify the SET

DATAEXPORTOPTIONS command to define options for export content, format, and process Use FIX…ENDFIX or EXCLUDE…ENDEXCLUDE calculations to select a slice of the database and use a DATAEXPORTCOND command to select data based on data values.

Note: The DATAEXPORT command enables calculation scripts to export data in binary or text, or directly to a relational database. A set of data-export-related calculation commands qualify what

data to export and provide various output and formatting options.

Compared to using other methods to export data, using a calculation script has the following

advantages and disadvantages:

Advantages:

Enables exporting a subset of data.

* Supports multiple targets: flat files, relational databases, and binary files (not B, C, D)

* Provides many flexible options for type and format or data.

* As part of a calculation script, can be easily deployed in a batch process.

* Can be very fast when the dynamic calculation export option is not used because DATAEXPORT directly accesses Kernel storage blocks in memory. (E)

* Provides, through binary export-import, a faster way to back up and restore data because the

compressed format used by binary export requires less storage for the export files.

* Can be used as a debug tool to trace batch calculation results by using the DATAEXPORT

command before and after other calculation commands to track data changes.

Disadvantages

Contains limited data formatting options compared to Report Writer formatting.

A: Business Rules can be assigned to data forms.

C: You can manage database locations, and the access privileges of repository objects that are

assigned to them, using the Location Editor. You can use the Location Editor to create, edit, and

copy database locations, assign new access privileges to locations, copy access privileges from

one location to another, and copy business rules from one location to another.

E: When you validate a business rule, Business Rules determines whether the member or members you select exist in the database and whether the syntax of the business rule is correct.

You need to have access privileges to all rules in the sequence before you can launch it.