Question No : 1
Management dictates a major reorganization of the company structure, meaning you need
to rebuild the Entity dimension from the beginning. You need to delete members in the
Entity dimension. Identify the three true statements about deleting members from a
Planning application.
A. You must delete members one by one.
B. You must delete a reference to a member from all data forms before deleting it from the
dimension.
C. In a data form definition, you selected @IDescendants(IT) for the entity dimension in the
page section. The IT member will remain but 2 of its 10 cost centers are being removed.
You must remove the reference to "IT" in this data form.
D. You should back up all data for the deleted entity members; after a member is deleted,
the data is not retained.
E. A database refresh is required after deleting members from the Entity dimension.
Answer: B,D,E
Explanation:
B: members of the dimension entity must be first delete in data forms and
then in the library dimension
D: Make a backup to retain the information.
E: A refresh of the database is required.
Question No : 2
Identify the two true statements about Enterprise performance Management Architect.
A. If you decide to implement EPMA, all Planning applications must be EPMA-deployed
applications.
B. EPMA-deployed applications may either use EAS Business Rules or Calculation
Manager in 11.1.1.3.
C. You can create Planning, TM, Essbase, and FDM applications in EPMA.
D. Data can be shared from a Planning application to an FM application within EPMA.
E. EPMA can be used by end users to manage and update member properties such as
hierarchies and aliases.
F. In the Dimension Library, you can maintain one full dimension (for example. Account)
but filter portions of the dimension for different applications (for example, Revenue
accounts. Balance Sheet)
Answer: D,F
Explanation:
D: EPMA Data Synchronization—Enables data synchronization within
Hyperion applications. You can use the Data Synchronizer to:
* Create data movement synchronizations between Hyperion applications. For example,
an administrator can synchronize data between two Financial Management; two Planning
applications, and between one Financial Management(FM)and a Planning application
* Create data mappings for reuse
* Create flat file and interface table mappings to import data into Hyperion applications
F: You can use theEnterprise performance Management Architectto create filters to select
specified members of a dimension. For example, select the Balance
Sheet accounts of the Account dimension. This enables you toEnterprise performance
Management Architec
Question No : 3
Identify three key benefits of the Planning solution.
A. Standardized data forms for plan data entry available both for the Web and in Excel
B. One tool to budget and forecast as well as provide reporting for very detailed Actuals
Information
C. Central repository of business rules that can be run by end users to calculate plan data
D. Detailed security down to the cell level
E. Flexible solution customizable for almost any kind of budgeting and forecasting process
Answer: A,C,E
Explanation:
A: Hyperion Planning leverages Multidimensional functionalities and
capabilities of Essbase to the fullest to provide varied planning options along with inherent
Data Forms, MS Excel, Web based grid interface for the data entry and reporting needs.
ata Forms in Hyperion planning provides a standard centralized grid-based interface for
data entry and data-checks. Customizing or fixing a Data Form issues take lesser time and
effort compared to the Excel based spreadsheets.
C: Use of a central repository makes administration and maintenance of business rules
easy,
because the repository stores information for several applications in one database.
A user or group who has the role of basic user can do these tasks:
* Launch business rules and sequences to which the user has access
* View business rules and sequences to which the users has access
* View all variables and macros
Reference: Hyperion Business Rules, Administrative Guide
Question No : 4
Identify the three differences between Grid Spreader and Mass Allocate.
A. Grid Spreader processes on the client whereas Mass Allocate processes on the server.
B. Mass Allocate generates and runs a business rule behind the scenes, allowing members
not displayed on the form to be updated.
C. Both M-3CG Allocate and Grid Spreader require special roles in Shared Services.
D. Grid Spreader gives users a "preview" to the spread result before saving whereas Mass
Allocate will automatically save results to the server.
E. Both Mass Allocate and Grid Spreader support relational spread.
Answer: A,B,D
Explanation:
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) andan 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)
Question No : 5
Identify the two true statements about a sparse Entity dimension In Hyperion Planning.
A. You cannot build alternate rollups or assign custom attributes.
B. Base currencies are assigned to entity members.
C. Exchange rates are assigned to entity members.
D. Entity along with Scenario and Period make up a planning unit.
E. Entity along with Scenario and Version make up a planning unit.
Answer: B,E
Explanation:
E: 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.
Note:
Essbase maximizes performance by dividing the Essbase - Standard dimensions of an
application into two types:
dense dimensions
sparse dimensions.
Sparse and dense are a property of the values of an attribute.
Sparse
Data is normally stored in sparse form. If no value exists for a given combination of
dimension values, no row exists in the fact table. For example, if not every product is sold
in every market. In this case, Market and Product are sparse dimensions.
It's why in the reporting tool Obiee for instance, by default, data are considered sparse.
Dense
Most multidimensional databases may also contain dense dimensions. A fact table is
considered to have dense data if it has (of a high probability to have) one row for every
combination of its associated dimension levels.
No comments:
Post a Comment