1. Using a Seeded System Template for Calculations in Hyperion Financial Management Calculation Manager
Andrea Auld
Senior Principal Instructor Oracle University October 22, 2018
This is a Title Slide with Picture and Product, Service, or Industry Logo slide ideal for including a picture and product/service/industry or org logo with a brief title, subtitle and presenter information.
To Replace the LOGOs on this sample slide:
Right-click a sample LOGO and choose Change Picture. Navigate to the location where the new logo is stored, select desired logo file and click on the Open button to replace the sample logo.
The Presented with FPO logo placeholder box can be copy and paste to any of the Title Slides.
Confidential – Oracle Internal/Restricted/Highly Restricted

2. Using a Seeded System Template in HFM Calculation Manager
What we’ll cover
This presentation will cover:
The use of the “Days in Period” seeded system template in a Calculation rule
Setting up the DaysInPeriod account
Setting up the AvgUnitsSoldPerDay
Setting up the variables required by the template – povYear, povPeriod and nDaysInPeriod
Create a new rule to calculate AvgUnitsSoldPerDay
Use the template to calculate the value for the nDaysInPeriod variable
Create a formula to populate the DaysInPeriod account with the nDaysInPeriod variable value.
Create a formula to calculate AvgUnitsSoldPerDay as UnitsSold/DaysInPeriod
Deploy the rule
Test in a data grid
In this short presentation, I’ll show you how to use one of the seeded system templates for a calculation in Calculation in Hyperion Financial Management
Using a Seeded System Template in HFM Calculation Manager

3. The goal – calculate average sales per day
The goal is to calculate average sales per day for a given period. We are loading Sales and UnitsSold balances from the General Ledger system and want to calculate the Average Units Sold per day as Sales/Units Sols.
Using a Seeded System Template in HFM Calculation Manager

4. Create the Days in Period account
In Dimension library, I’ll first create an account to store the Days in Period balance. Because the account type is “Flow”, the balance at the quarter will be the sum of the balances for the individual periods. (So Days in Period for Q1 will be the sum of January, February and March). Because we want to use this account to calculate average units sold per day, we will make it valid with the LinesOfBusiness, Markets, Industries and Destinations dimensions, just like the UnitsSold account is valid with those dimensions. By checking the IsCalculated flag, it will not be possible to enter or load data to the account.
Using a Seeded System Template in HFM Calculation Manager

5. Create the Average Units Sold Per Day Account
I can create a second account called AvgUnitsSoldPerDay of type Flow. Once again, because this is measuring UnitsSold, we should make the account valid with LinesOfBusiness, Markets, Industries and Destinations.
Using a Seeded System Template in HFM Calculation Manager

6. Create the povYear execution variable
Using the template requires several variables.
The first variable will store the current year from the POV in the data grid where we will test our rule.
The variable can be GLOBAL, but it must be an execution variable, because it will store the output of one of the seeded functions. For more information on the seeded functions available in Hyperion Financial Management Calculation Manager, refer to the HFM admin guide..
Using a Seeded System Template in HFM Calculation Manager

7. Create the povPeriod execution variable
Using the template requires several variables.
The second variable will store the current period from the POV in the data grid where we will test our rule.
The variable can be GLOBAL, but it must be an execution variable, because it will store the output of one of the seeded functions. For more information on the seeded functions available in Hyperion Financial Management Calculation Manager, refer to the HFM admin guide..
Using a Seeded System Template in HFM Calculation Manager

8. Create the nDaysInPeriod execution variable.
Using the template requires several variables.
The third variable will store the number of days in the current period and will be populated by the template, so it will not have a value in the variable designer.
The variable would most likely be LOCAL, because it is being populated by a rule rather tha by the output of one of the seeded HFM Calculation functions.
Using a Seeded System Template in HFM Calculation Manager

9. Create a rule to calculate AvgUnitsSoldPerDay.
To create the rule, we give it a name, a caption and a description. The comments that we enter will show up in the Vbscript that Calculation manager will generated.
Using a Seeded System Template in HFM Calculation Manager

10. Using a Seeded System Template in HFM Calculation Manager
Use the GetDaysInMonth system template to calculate the value for the nDaysInPeriod variable
When you drag the template into a rule, the parameters window opens and allows you to choose the parameters required by the Days in Period seeded System Template.
- The Days in Month variable will store the result of the template.
-The Year variable will reference the current Year in the POV.
-The Period Number variable will reference the current period number from the POV.
Using a Seeded System Template in HFM Calculation Manager

11. Create the formula to populate the DaysInPeriod account
The formula shown will set the balance in the DaysInPeriod account using the value of the variable that was populated by the template
Using a Seeded System Template in HFM Calculation Manager

12. Create the formula to calculate the AvgUnitsSoldPerDay account
The formula will calculate the balance in the AvgUnitsSoldPerDay account by taking UnitsSold by the DaysInPeriod account populated in the previous formula
Using a Seeded System Template in HFM Calculation Manager

13. Review and validate the rule
The rule will execute the formulas in order:
-Populate the nDaysInPeriod variable
-Copy the value from the nDaysInPeriod variable into the DaysInPeriod account.
-Calculate the AvgUnisSoldPerDay account as UnitsSold/DaysInPeriod
Using a Seeded System Template in HFM Calculation Manager

14. Review the vbScript created from the rule
You can review the Vbscript created from the graphical rule by calculation manager
Using a Seeded System Template in HFM Calculation Manager

15. Create a ruleset and drag the rule into the ruleset.
You can review the Vbscript created from the graphical rule by calculation manager
Using a Seeded System Template in HFM Calculation Manager

16. Review the VBScript generated from the ruleset.
Note that the Ruleset for the Calculate rule type corresponds to the Sub Calculate subroutine. You can see the declaration of your execution variables in the beginning of the VBScript as well as the setting of the values to the output of one of the seeded functions.
Using a Seeded System Template in HFM Calculation Manager

17. Mark the ruleset for deployment and deploy
Remember that a rule type like the calculate rule type can have multiple rulesets, but only one can be deployed at a time. You mark the ruleset you wish to deploy in Deployment view, which will also let you see whether or not the ruleset has ever been deployed before and whether it has been modified since it was last deployed.
Using a Seeded System Template in HFM Calculation Manager

18. Using a Seeded System Template in HFM Calculation Manager
Test using a data grid
You can test the rule in a datagrid. In the datagrid, you could enter Units Sold. You cannot enter Days in Period or AvgUnitsSoldPerDay because both members of the Account dimension had the IsCalculated flag checked so both appear as green cells.
When you right click and choose calculate, both the DayInPeriod and AvgUnitsSoldPerDay accounts are populated by your rule.
Using a Seeded System Template in HFM Calculation Manager

19. An Overview of Approvals Management Engine in Ebusiness Suite
Summary
In this presentation you learned how to:
Set up the DaysInPeriod account
Set up the AvgUnitsSoldPerDay
Set up the variables required by the template – povYear, povPeriod and nDaysInPeriod
Create a new rule to calculate AvgUnitsSoldPerDay
Use the template to calculate the value for the nDaysInPeriod variable
Create a formula to populate the DaysInPeriod account with the nDaysInPeriod variable value.
Create formula to calculate AvgUnitsSoldPerDay as UnitsSold/DaysInPeriod
Deploy the rule
Test in a data grid
An Overview of Approvals Management Engine in Ebusiness Suite