Correct Answer: BE

E: 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.

Note:

Essbase maximizes performance by dividing the Essbase - Standard dimensions of an application into two types:

dense dimensions

sparse dimensions.

Sparse and dense are a property of the values of an attribute.

Sparse

Data is normally stored in sparse form. If no value exists for a given combination of dimension values, no row exists in the fact table. For example, if not every product is sold in every market. In this case, Market and Product are sparse

dimensions.

It's why in the reporting tool Obiee for instance, by default, data are considered sparse.

Dense

Most multidimensional databases may also contain dense dimensions. A fact table is considered to have dense data if it has (of a high probability to have) one row for every combination of its associated dimension levels.

Correct Answer: BC

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

Correct Answer: CE

C: Columns cannot be split or joined at runtime in the source.

E: An external table cannot be used to map data.

Note: Data Load Rules file is the second type of rules files which is involved in the data load process.

A data source for data load must contain :

not only the values that you want to load but also identification of the location to which Essbase should load the values:

a data address that includes one member from every standard dimension in your outline.

Correct Answer: ABD

A: Specify access rights to members of the Scenario dimension for groups or users.

Access rights determine users or groups can view or modify data. A user or group can have only one of these access rights: Read, Write, or None. Access rights for a user can be combined based on groups to which the user belongs.

B: When creating a scenario For Start Yr., Start Period, End Yr., and End Period are used to select the time period to associate with the scenario.

D: The Scenario dimension has an Exchange Table property with value of the name of an exchange rate table defined in the application.

Reference: Oracle Hyperion Planning, Fusion Edition

Correct Answer: ABEF

Scenario,Version and Entity make up a planning unit so security needs to be applied here and then also to the custom dimension if it has security.

Correct Answer: ABCEF

A: Essbase data load rules: A set of criteria that determines how to load data from a text-based file, a spreadsheet, or a relational data set into a database.

You can use either the Data Load Rules and the Essbase Administration Services for Essbase 7/Analytic Administration Services for Analytic Services 9.2 or Hyperion Application Link with the Hyperion Essbase Adapter to load data into a

Planning application.

B: Oracle Data Integrator (ODI) is a comprehensive data integration platform that handles any data integration requirements--high-volume, high-performance batches, event-driven, trickle-feed integration processes, and SOA-enabled data

services.

C: One of the methods of loading Essbase cubes is by using the Hyperion Data Integration Management and its corresponding Essbase Adapter.

Data Integration Management is integrated with Informatica PowerCenter. It provides a way of uniting disparate sources of data across an enterprise. For example, it can integrate data stored in multiple warehouses and data marts, relational

database management systems (RDBMS), and on-line analytical processing (OLAP) stores.

E: The Outline Load Utility that comes with Oracle EPM 11 is a utility for loading the metadata as well as data into your Planning applications. Using the utility we can load metadata for the default dimensions like Account, Period, Year, Scenario, Version, Currency, Entity as well as user-defined dimensions, attributes and UDAs.

F: Enterprise Performance Management Architect or EPMA provides a uniform platform for metadata management across most of the Hyperion components. It enables administrators to manage, create, and deploy Hyperion applications within one interface. With EPMA you can configure dimensions, such as the Entity, and define properties from predefined, sample libraries.

Correct Answer: BDE

B: members of the dimension entity must be first delete in data forms and then in the library dimension

D: Make a backup to retain the information.

E: A refresh of the database is required.

Correct Answer: BE

Fragmentation is unused disk space.

EssBase Database fragmentation is likely to occur with the following:

Read/write databases that users are constantly updating with data (E).

Databases that execute calculations around the clock

Databases that frequently update and recalculate dense members (B)

Data loads that are poorly designed

Databases that contain a significant number of Dynamic Calc and Store members

Databases that use an isolation level of uncommitted access with commit block set to zero

Correct Answer: DE

D: The planning Calculation Manager Administrator enables you to create business rules using Hyperion Calculation Manager.

E: The global Shared Services role of Dimension Editor creates and manages dimensions.

The global Calculation Manager administrator role enables you to create, edit and delete Planning, FinancialManagement, and Essbase objects. The Financial Management Calculation Manager administrator role enables to create, edit and delete Financial Management objects.

Correct Answer: BC

B: Replicated Partition:

A portion of a database, defined through Partition Manager, used to propagate an update to data mastered at one site to a copy of data stored at another site. Users can access the data as though it were part of their local database.

C:

Transparent partition:

A form of shared partition that provides the ability to access and manipulate remote data transparently as though it is part of your local database. The remote data is retrieved from the data source each time you request it. Any updates made

to the data are written back to the data source and become immediately accessible to both local data target users and transparent data source users

Note: @XREF

Enables a database calculation to incorporate values from another Essbase database.

The following terminology is used to describe the @XREF function:

Data target: the database on which the current calculation is running (that is, the database on which the @XREF call originates).

Data source: the database that is queried by the @XREF function. This database may be remote (that is, on a different machine than the data target).

Point of view: the member combination currently being calculated on the data target (that is, the member combination that identifies the left hand side of a calculation).

The @XREF function retrieves values from a data source to be used in a calculation on a data target. @XREF does not impose member and dimension mapping restrictions, which means that the data source and data target outlines can be

different.

Note #2:

Hyperion planning's Plan Types treated as individual databases in underlying Essbase database comes with inherent facility to share data and dimension members across plan types in Hyperion Planning or equivalent databases in underlying

Essbase. This reduces the need for additional development/maintenance effort when compared to Planning systems based on Standalone Essbase. The Hyperion Planning user would seldom realize that the dimension members belong to

multiple databases. While this might be an area of concern while using Standalone Essbase to build planning system.