Free Practice Questions for Oracle 1z0-533 Exam

Grid spread allocates data across the cells on the webform and runs on the client browser.Mass allocate triggers a calc script which can allocate data beyond cells those are available in the form.

If your administrator has enabled Grid Spread as a data form property, you can specify an amount or percentage by which Planning increases or decreases values across multiple dimensions on the data form, based on the existing values in the target cells. You immediately see the result in the data form and can save the new data or discard it. When calculating the spread data, Planning ignores read-only and locked cells and cells having supporting detail. Data integrity is ensured by spreading values only to cells to which you have access.

If you have the Mass Allocate role (assigned in Oracle's Hyperion® Shared Services) and an administrator has enabled Mass Allocate as the data form property, you can spread data using the powerful feature, Mass Allocate, which:

Allocates data to all the source cell's descendants

Allocates across multiple dimensions

Spreads data even to cells not displayed on the data form

Does not require that you have access to the target cells

Cannot be undone after you mass allocate values

Is processed with dynamically-created calc scripts

Executes the calc scripts against the Essbase server, against all dimension combinations

Can use customized spreading patterns, created by an administrator (see the Oracle Hyperion Planning Administrator’s Online Help)

You candynamically build the Entity dimension in the Planning applicationwith the help ofODI, DIM and EPMA.

With Version 11(and later)you can also use the outline loader.

Incorrect:

not A:you can't use essbase load rules, metadata has to be loaded to planning and then pushed to essbase.

A: If you select a weekly distribution pattern other than Even, Planning treats quarterly values as if they were divided into 13 weeks and distributes weeks according to the selected pattern.

E:

Weekly distribution sets the monthly distribution pattern, based on the number of fiscal weeks

in a month. This determines how data in summary time periods spreads within the base time

period. When users enter data into summary time periods, such as quarters, the value is

distributed over base time periods in the summary time period.

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.

A:Usage of dynamic calc in sparse dimensionincludes benefits such asshorter aggregations smaller database size.

C:Consider the number of members underneath a sparse parent. It's generally good practice to have few (up to 20) members under dynamic sparse parents if your block size is not massively huge. This number might increase if your block size is tiny.

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.

C, E: By assigning access to a data form, you control which users can change its design (for example,

its layout and instructions) and input data. Users can select only members to which they have

read or write access. Users can edit data forms only if they have access to at least one member

of each secured dimension. For example, if users have read-only access to the Europe entity, the

rows and columns on data forms that include the Europe entity are displayed as read-only. Users

can change data only for members to which they have write access.

D: For bottom-up versions, rows and columns with level 0 members allow data entry. Rows or

columns set to a parent member are read-only. The point of view must also be set to the level 0

member to allow data entry on a bottom-up version. Target versions allow data entry in parent

and children members.

If you assign children to bottom-up versions, these versions display as read-only parents on data forms.

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