Planning data forms can be accessed from within the EPM Workspace and from Smart View Planning Provider.

Note: Smart View provides a common Microsoft Office interface for Oracle Essbase, Oracle Hyperion Financial Management, Fusion Edition, Oracle Hyperion Planning, Fusion Edition, Oracle Enterprise Performance Management Workspace, Fusion Edition, Oracle Business Intelligence Enterprise Edition, and Oracle's Hyperion® Enterprise® data. Using Smart View, you can view, import, manipulate, distribute and share data in Microsoft Excel, Word, and PowerPoint interfaces.

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.

Set the time balance as “last” when you want the parent value to represent the value of the last member in the branch (often at the end of a time period).

Note:

Essbase - Time balance properties

The tags :

first,

last,

average,

and expense

are available exclusively for use with accounts dimension members.

Using this tag requires an accounts dimension and a time dimension

If an accounts dimension member uses the time balance property, it affects how Essbase calculates the parent of that member in the time dimension. By default, a parent in the time dimension is calculated based on the consolidation and formulas of its children. For example, in the database in this scenarion, the Q1 member is the sum of its children (Jan, Feb, and Mar). However, setting a time balance property causes parents, for example Q1, to roll up differently.

If you set the time balance as first, last, or average, set the skip property to tell Essbase what to do when it encounters missing values or values of 0.

Since version 7, Essbase has supported two "storage options" (BSO and ASO) which take advantage of sparsity to minimize the amount of physical memory and disk space required to represent large multidimensional spaces. The Essbase patent describes the original method, which aimed to reduce the amount of physical memory required without increasing the time required to look up closely-related values. With the introduction of alternative storage options, marketing materials called this the Block Storage Option (Essbase BSO), later referred to as Essbase Analytics.

(BSO) enables driver-based scenario modeling, forecasting, and predictive analytic applications.

Note: To give you our idea of the ideal application of ASO and BSO,:

ASO Database: The ASO database is ideal for dynamically built Essbase cubes that are usually Read Only and used for reporting, presentation, and analysis. This type of database would also tend to have a rather large outline where at least one dimension has a significant amount of members. A parts dimension or product dimension comes to mind. Behind this ASO database would be a large BSO parent Essbase database, from which the dynamic ASO databases are built on the fly.

BSO Database: The BSO database is ideal for virtually any size cube, but where performance is not necessarily the number one priority. Accuracy and completeness of data would be the main consideration. The BSO database is ideal as the large parent database where users from many different departments can trigger jobs which will dynamically build ASO reporting cubes on an as needed basis. The typical BSO database is ideally suited for financial analysis applications.

The number of stored members in sparse Dimensions will help us in finding potential number of blocks

Potential Number of Blocks = Stored Members in Market * Stored Products in Scenario.

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.

Scenario,Version & Entity make up a planning unit so security needs to be applied here and then also to the custom dimension if it has security.

Not C: Business Rules are a powerful to automate complex calculations.

However, a rule typically runs a specific calculation/allocation on a single Essbase Database.

E: Macros are used to avoid duplicating code.

Incorrect:

not A: ESSCMD is the original command line interface for administration commands.

Not B: Cacl scripts is a powerful to automate calculations.

Not D: MaxL, a "multi-dimensional database access language" which provides both a superset of ESSCMD commands, but with a syntax more akin to SQL, as well as support for MDX queries.

Incorrect answer:

With a smart list you can only select from pre-defined options in a list-

You can change the status of the Employee through options from a Drop down/Smart List on a data form by running a Business Rule.

Incorrect answer:

Deleting the employee is a bad praxis. It would remove old salary entries.

You do not access the attributes directly on the Employee dimension.

Note: The Workforce Planning Module for Hyperion Planning provides a robust set of calculations and pre-defined web-forms that allows organizations to track and budget down to the benefit-level for each employee.