Identify the correct set of required dimensions for Planning.
A. Account
B. Entity
C. Version
D. Years and Periods combined into one dimension
E. Scenario
F. Minimum one user-defined dimension
Correct Answer: ABCDE
Explanation/Reference:
Explanation: 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.
Reference: Required Dimensions for a Hyperion Planning Application
Explanation/Reference:
Explanation: 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.
Reference: Required Dimensions for a Hyperion Planning Application
|
Download Printable PDF. VALID exam to help you PASS. |
 |