Pass the Oracle Planning 1z0-533 Questions and answers with ExamsMirror

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

D: Essbase reads the data values or members in the data source, changes them based on the rules in the rules file, and loads the changed data values into the database and the changed members into the outline. Essbase does not change the data source.

A: In all Planning Units states except the Not Started state, users with read access can view data, view the process state, view the history, and read and enter annotations.

E: The Administrator have full access.

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.

You can choose from four possible actions to include in a graphical business rule: Aggregate

Data, Copy Data, Clear Data, and Create Blocks.

Note:

* Aggregate Data —Use to calculate your database by specifying which dimensions to

calculate and what calculation options you want to use during the aggregation.

* Copy Data—Use to copy data from one part of your database to another. You select the

source data to copy and then specify the target or destination value.

* Clear Data—Use to define a subset of data that will be cleared from the database before a

new value is added. You can choose either to clear cells or to clear blocks of data.

* Create Blocks—Use to specify a data slice to ensure that blocks are created for all sparse

member combinations in that slice.

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.

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.

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.

Custom menus can be used to launch the following:

– Business Rules

– Context sensitive data forms

– URL

– Context sensitive Process Management

Where needed in the calculation script, you can use multiple SET CREATEBLOCKONEQ commands to define the Create Blocks on Equation setting value for the calculations that follow each command.

Ways to create data blocks:

1. Data Load, (B)

2. DataCopy Command, (A)

3. Sparse Dimension Consolidation,

4. Member Formulas:

4a. Assiging a constant value to a sparse member,

4b. Turning Create Block on Equation setting on and assiging a non constant value (C)

4c. Create non missing blocks

B: The moment we load data to essbase, It creates block for those combinations automatically.

C: Controls, within a calculation script, whether or not new blocks are created when a calculation formula assigns anything other than a constant to a member of a sparse dimension. SET CREATEBLOCKONEQ overrides the Create Block on Equation setting for the database.

If calculations result in a value for a sparse dimension member for which no block exists, Analytic Services creates a new block. Sometimes, the new blocks are not desired; for example, when they contain no other values. In large databases, creation and processing of unneeded blocks can increase processing time as well as the storage requirement for a database.

For the situation when new blocks would be created as a result of assigning something other than a constant to a member of a sparse dimension, Analytic Services provides the Create Blocks on Equation setting. For example, when the Create Blocks on Equation setting is ON and West is assigned a value where it did not have a value before, new blocks are created. When this setting is OFF, new blocks are not created.

Incorrect answer:

Copy Data—Use to copy data from one part of your database to another. You select the

source data to copy and specify the target or destination value.

D: Aggregate data. There is no such specific command or utility. It is just a general concept in the Hyperion context.