1z0-533 Oracle Hyperion Planning 11 Essentials Questions and Answers

A: Properties for User-Defined Custom Dimensions include property Valid for Plan Types which is used to select plan types for which the dimension is valid. Clearing this option makes all members of the dimension invalidfor the deselected plan type.

User-defined custom dimensions differ from the Entity and Account dimensions in that you

assign valid plan types at the dimension level, not at the member level. All members of a user-defined custom dimension are valid for plan types assigned at the dimension level.

Note: Specify one to three plan types for the application. A separate Essbase database is created for each plan type. You cannot change the name or number of plan types after creating an

application.

As you create accounts, entities, and other elements of the application, you associate them with

plan types, so the database for each plan type contains only information relevant to the plan

type. This optimizes application design, size, and performance.

First calculate the aggregated saleries.

Then make the custom calculation on the saleries.

Finally use the result of the custom calculation to product the benefits.

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

Administrators can use Copy Data to copy plans from one dimensional intersection to another (A), including relational data and supporting detail (C).

You can copy account annotations (E), supporting detail, and cell text (D). You cannot copy

planning unit annotations.

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.

Asymmetric rows and columns are ones in which different sets of members are selected across the same dimension.

During refresh:

* Essbase security filters are updated (C, D)

* Currency conversion calc scripts are updated

* Accounts or associated properties are propagated from the relational database to the Essbase database

* Custom attributes are added, modified, or deleted in the Essbase database

* Exchange rate values are repopulated in the Essbase outline

* Member formulas for certain accounts are generated or updated

* Additions or changes to alias tables and their association to dimensions or members are updated (A)

* The Essbase database is restructured

* UDAs are added to the Essbase database