Free Oracle 1z0-588 Practice Exam with Questions & Answers | Set: 2

300-10 is called an Explicit Shared Node.

300-10 is called an Implicit Shared Node.

300 is not a valid shared node because only leaf nodes may be shared.

You can delete the node 300-10 in the alternate product hierarchy,

You can change local property values in the alternate product hierarchy.

You can change any of the system generated property values on the Shared Node property category forthe alternate product hierarchy.

1, 2, 4, 5 only

1, 2, 4, 5, 6 only

1, 3, 4, 5, 6 only

1, 2, 4, 5, 7 only

1, 3, 4, 5, 7 only

1, 2, 3, 4, 5, 6, 7

Node

Hierarchy

Version

Global Node

Global Hierarchy

Merge

One-to-one mapping

Mapping nodes across versions

Many-to-many mapping

One-to-many mapping

Validations for format of mapped nodes

To maintain monthly versions

To maintain versions for major reorganization

To apply security for different hierarchies

To allow multiple people to simultaneously work on the same data

For "What If" modeling for a hierarchy

To create property categories that are specific to a version

For historical comparisons

Working

Submitted

Final

Expired

Baseline

A System property category is automatically created out of the box.

If enabled in the system preferences, the Oracle EPM property categories are created, out of thebox.

If enabled in the system preferences, the Oracle EBS categories are created, out of the box.

Property categories are unique to a version.

Property categories are unique to a hierarchy.

Node access groups are assigned to property categories.

A property categories assigned to a user may be read or edit.

It is considered an upstream system.

It is considered a downstream system.

Because it is used as a source for the Entity dimension, you may not feed entity data back to the ERP system.

It may be imported into an existing version using Import.

The ERP system feed can be automated using the batch client.

Version

Property category

Hierarchy group

Node type

Hierarchy master

Node access groups use inheritance to assign the same access to descendants of a node but this inherited security may be overwritten at lower levels.

Valid node access levels are Read, Edit,LimitedEdit, Insert, Inactivate, and Add.

Access levels are assigned separately for leaf and limb nodes.

Node access groups can be used to filter the display of the hierarchy so that users only see the section of the hierarchy for which they have access.

Node access groups may be assigned by the Application Administrator or Access Manager.