Oracle 1z0-533 - Oracle Hyperion Planning 11 Essentials

C: You use the Scenario and Version dimensions to create individual plans to be reviewed and

approved. Each scenario/version combination contains its own set of data for the accounts and

other dimensions of each entity. After users complete data entry for an entity for a specific

scenario and version, they can submit or promote the data for the entity to another user for

review and approval. The intersection of entity, scenario, and version is referred to as a

planning unit. Planning tracks the status of each planning unit as it moves through the review

process.

D: Seems likely.

Capex (Capital Expense Planning Process) is:

- Planning for new asset purchase

– Depreciation/Amortization calculations

– Planning for action on existing assets

– Planning for driver based/user defined asset related expenses

– Capital purchases process management (future release)

– Reporting on Asset

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.

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.

Not C: Business Rules are a powerful to automate complex calculations.

However, arule typically runs a specific calculation/allocation on a single Essbase Database.

E: Macros are used to avoid duplicating code.

Incorrect:

not A:ESSCMD is the original command line interface for administration commands.

Not B: Cacl scripts is a powerful to automate calculations.

Not D:MaxL, a "multi-dimensional database access language" which provides both a superset of ESSCMD commands, but with a syntax more akin to SQL, as well as support for MDX queries.

A: If the user does not have the launch the Business Rules role, it could prevent the user from seeing the rule.

B: The Validate or launch Privilege enables a users or users you specify to validate and launch the business rule sequence

Incorrect answer:

C: The business rule has already been assigned to the Data Form.

A:

To create and change attributes, attribute values, and aliases:

1 Select Administration, then Dimensions.

2 Select a sparse dimension for which to define an attribute, attribute value, or alias.

Only sparse dimensions can contain attributes.

3 Select the top level in the dimension hierarchy, and click Edit.

4 In the Dimension Properties dialog box, click Custom Attributes.

5 Select options.

5.1 To create attributes, click Create. Type an attribute name, and select a data type: Text,

Date, Boolean, or Numeric.

5.2 To modify attributes, click Modify, and update the attribute name.

5.3 To set aliases for attributes, select an attribute and an attribute value, click Alias. Select an

alias table, type an alias name, and click Close.

6 Click Close.

When you click Close, the hierarchy is validated and an error displays if issues are detected.

7 Update and validate business rules and reports.

B: Attributes can have data types of text, date, Boolean, and numeric.

E: An attribute dimension is a special type of dimension that is associated with a standard dimension. A standard dimension is any dimension that is not an attribute dimension. When an attribute dimension is associated with a standard dimension, the standard dimension is the base dimension for that attribute dimension. I

Stored should be used.

Note: The accounts dimension is a dimension type that makes accounting intelligence available. Only one dimension can be defined as Accounts.

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.

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.