Hi All,
Hyperion Planning uses a relational database to store its metadata and other details like cell annotations or text etc. Also it uses Essbase to store its cube dimensions and members. Hence to run Hyperion planning your database which you have configured for planning and Essbase both should be up and running.
You can create Planning applications using either EPM Architect or Classic Application wizard. In both the places the menus and the options available are different. Classic application wizard is only for creating Hyperion planning applications but EPMA can be used to create Planning as well as HFM applications. EPMA consists of Application library and Dimension library and Calculation manager and can be launched from Hyperion workspace.
Classic Application wizard is the only one which I tried and it is more easier to understand and it created the application alongwith the Essbase application and all the dataforms automatically.
Here I will be disucussing more on the concepts which are not there in Oracle by example document.
For the complete steps and procedure, you can refer Oracle By Example- Planning also.
The various steps involved in creating an Application using Classis application wizard are-
Go to planning administration to create an application.
1. Creating a datasourse- An Essbase database alongwith the outline will be created for this purpose and information related to this application will be stored in the relational database also.
To populate the data you need to manually upload data into the Essbase cube.
Hence as I said earlier, for your application to run, both the databases should be up and running.
2. Now we need to define the settings for the application.
This is the most important stage in terms of understanding what does an application contains and how does it works.
The Classic application wizard allows you to select the defaults and directly create an application but we will try to discover each option and try to understand its meaning.
(a) Calender-
Base Time period- This basically makes an application understand how an Year in our application is distributed. You can choose from options like 12 Months or Quarters. If you want to define a customized time period, you can do that as well. But once an option is selected, it cannot be changed once the application is created. Here the months or quarters automatically roll up to the year level.
Now for the base time period defined we need to select the starting month and fiscal start year which again cannot be changed. However more years can be added.
Under weekely distribution, you have options to define how one quarter is divided. We understand that a Quarter has 13 weeks(52/4) and the options we can choose for the quarter distribution are 4-4-5, 4-5-4 or 5-4-4.
(b) Plan Types- You want to have different plans for your application and you can define upto 3 plan types for your applications.
For each plan type you select, Hyperion creates an Essbase cube for that plan under the same application node and data stored in one plan type is shared with another plan type.
(c) Currencies- For applications which needs to have different currencies, you can select the currencies you may need to have. Hyperion creates an extra dimension with the name HSP_Rates in Essbase and currency calculation script which holds the conversion rates for those currencies. The application has one default currency and all other curriencies will be calculated based on the currency conversion rates values.
Data Form or Web Form :-
Here I'm giving just a brief idea about Oracle Hyperion Planning. V 9.
Hyperion Planning is a part of Hyperion Enterprise performance management applications.
Lets first understand the architecture of Hyperion planning. Hyperion Planning applications sits on top of hyperion planning foundation which uses Hyperion essbase calculation Engine.
This hyperion planning foundation takes care of all the planning and budgeting workflows, creating and applying the business rules, managing user forms, managing various business models for example P&L, Balance Sheet, Cash flow, Workforce planning and Capital Expenditure plans and also some operational planning models like sales and marketing plans etc. Now the interactive users can access and manage this using either Hyperion Workspace which is a web component or Microsoft Excel Add in.
If you ask me why we use hyperion planning, my answer would be to perform whatever I have mentioned in Planning foundation. Other than this the need of Hyperion planning comes in when you want to manage your planning, budgeting and forecasting workflows which generally are very complex.
Most of the companies use Excel to handle this but you know these excel sheets are just scattered peices of a book which are very difficult to manage and consume lot of our time.
Budget and forecasting are generally an iterative proess which means there are levels of hirarchies involved and the allocation of budget from the top, its distribution among the levels and again its consolidation from lower level to the top level is really a very complex task and should be managed using a workflow.
If you ask me why we use hyperion planning, my answer would be to perform whatever I have mentioned in Planning foundation. Other than this the need of Hyperion planning comes in when you want to manage your planning, budgeting and forecasting workflows which generally are very complex.
Most of the companies use Excel to handle this but you know these excel sheets are just scattered peices of a book which are very difficult to manage and consume lot of our time.
Budget and forecasting are generally an iterative proess which means there are levels of hirarchies involved and the allocation of budget from the top, its distribution among the levels and again its consolidation from lower level to the top level is really a very complex task and should be managed using a workflow.
Some of the features are:
1. It uses multidimentional data structure which is powered by Essbase calculation Engine for data collection and Analysis.
2. Web based user data entry forms which users themselves can create.
3. Users can set their targets online and can do bottom-up planning.
4. Ability to create complex models using business rules.
5. Currency conversion feature for multi currency applications.
6. Ability to create complex models.
7. Users can create task lists which enables them to understand the status of their tasks.
7. Users can create task lists which enables them to understand the status of their tasks.
Hyperion Planning uses a relational database to store its metadata and other details like cell annotations or text etc. Also it uses Essbase to store its cube dimensions and members. Hence to run Hyperion planning your database which you have configured for planning and Essbase both should be up and running.
You can create Planning applications using either EPM Architect or Classic Application wizard. In both the places the menus and the options available are different. Classic application wizard is only for creating Hyperion planning applications but EPMA can be used to create Planning as well as HFM applications. EPMA consists of Application library and Dimension library and Calculation manager and can be launched from Hyperion workspace.
Classic Application wizard is the only one which I tried and it is more easier to understand and it created the application alongwith the Essbase application and all the dataforms automatically.
Here I will be disucussing more on the concepts which are not there in Oracle by example document.
For the complete steps and procedure, you can refer Oracle By Example- Planning also.
The various steps involved in creating an Application using Classis application wizard are-
Go to planning administration to create an application.
1. Creating a datasourse- An Essbase database alongwith the outline will be created for this purpose and information related to this application will be stored in the relational database also.
To populate the data you need to manually upload data into the Essbase cube.
Hence as I said earlier, for your application to run, both the databases should be up and running.
2. Now we need to define the settings for the application.
This is the most important stage in terms of understanding what does an application contains and how does it works.
The Classic application wizard allows you to select the defaults and directly create an application but we will try to discover each option and try to understand its meaning.
(a) Calender-
Base Time period- This basically makes an application understand how an Year in our application is distributed. You can choose from options like 12 Months or Quarters. If you want to define a customized time period, you can do that as well. But once an option is selected, it cannot be changed once the application is created. Here the months or quarters automatically roll up to the year level.
Now for the base time period defined we need to select the starting month and fiscal start year which again cannot be changed. However more years can be added.
Under weekely distribution, you have options to define how one quarter is divided. We understand that a Quarter has 13 weeks(52/4) and the options we can choose for the quarter distribution are 4-4-5, 4-5-4 or 5-4-4.
(b) Plan Types- You want to have different plans for your application and you can define upto 3 plan types for your applications.
For each plan type you select, Hyperion creates an Essbase cube for that plan under the same application node and data stored in one plan type is shared with another plan type.
(c) Currencies- For applications which needs to have different currencies, you can select the currencies you may need to have. Hyperion creates an extra dimension with the name HSP_Rates in Essbase and currency calculation script which holds the conversion rates for those currencies. The application has one default currency and all other curriencies will be calculated based on the currency conversion rates values.
Data Form or Web Form :-
If you want to create data forms manually, you can do that.
Log on to Hyperion planning.
Navigate to the folder where you want to save your form.
above you will see a create button. click on create.
First tab will be gereral properties where you will type the form name.
After that the next column is Rows and columns.
Select your rows and columns from the select button after every row or column.
You will see a list and select from that.
Here we need to understand what are we selecting in our rows and columns. I did not do that before and hence adding that to make you understand the concepts.
There are six predefined dimensions available which are required to create any application-
1. Period and Year- Period dimension allows you to define your time periods like starting year and end year for the application. upto 100 calender years can be defined and once application is created you cannot delete the years or reduce them however you can add more years to it.
You also define the distribution of a year.
2. Scenario- It describes the type of plan you are creating like actual, budget or forecast.
3. Version- You may have a need to have different versions like Working and Final, best and worst case etc.
4. Entity- These are generally different regions, departments, cost centers etc of an organisation for which you want to create the plans.
5. Accounts- The account dimension defines the data to be collected from the entities. for example- Expense accounts, P&L accounts etc.
These dimensions are required to create any planning application.
Other than this there are 14 user defined dimensions like products, channels or customers which you can use in a planing application. There is a limit of 20 dimensions which a planning application can have.
will discuss other dimensions soon...
After that the next column is Rows and columns.
Select your rows and columns from the select button after every row or column.
You will see a list and select from that.
Here we need to understand what are we selecting in our rows and columns. I did not do that before and hence adding that to make you understand the concepts.
There are six predefined dimensions available which are required to create any application-
1. Period and Year- Period dimension allows you to define your time periods like starting year and end year for the application. upto 100 calender years can be defined and once application is created you cannot delete the years or reduce them however you can add more years to it.
You also define the distribution of a year.
2. Scenario- It describes the type of plan you are creating like actual, budget or forecast.
3. Version- You may have a need to have different versions like Working and Final, best and worst case etc.
4. Entity- These are generally different regions, departments, cost centers etc of an organisation for which you want to create the plans.
5. Accounts- The account dimension defines the data to be collected from the entities. for example- Expense accounts, P&L accounts etc.
These dimensions are required to create any planning application.
Other than this there are 14 user defined dimensions like products, channels or customers which you can use in a planing application. There is a limit of 20 dimensions which a planning application can have.
will discuss other dimensions soon...
After you select them they will appear like this.
If you wish you can create POV (Point of Values) for your form, you can select any dimension which is not a part of row or column dimension. POV will basically allow you to select the dimension members from the list for example if you are creating a plan for best and worst scenario, you can select this in the POV and while entering the information in the data form you can select whether you want to enter the info for Best case or Worst case.
Just look at the options available in other options tab
Click on preview or finish. The form is ready and will look like this.
So its really simple and guided.
No comments:
Post a Comment