Working With Template PDF

10/10/2014 ORACLE HYPERION CALC MANAGER Part 3 Working with Templates | Edgewater Ranzal Weblog
http://ranzal.wordpress.com/2010/07/31/oracle-hyperion-calc-manager-%E2%80%93-part-3-%E2%80%93-working-with-templates/ 1/9
ORACLE HYPERION CALC MANAGER
Part 3 Working with Templates
Posted on July 31, 2010 by richardsonjeff
In Part 1 of this series, we introduced Calc Manager, providing a general overview and
explanation of some new terms. In the second post in the series, we walked through the
development of a Planning rule that utilized a run time prompt. In this post, well explore
templates provided within Calc Manager.
As with the Rule Designer, which is a great tool to help less experienced developers build
rules, templates provide a simple way to develop rules for basic tasks in Planning and
Essbasetasks such as copying, clearing, exporting, allocating, and aggregating data. In
addition, you can design your own templates.
Well begin by logging on to Hyperion Workspace and navigating to Calc Manager. Once in
Workspace, the navigation path is: Navigate -> Administer -> Calculation Manager.
Once in Calc Manager, youll land on the System View tab, which appears as follows:
Once again, Ill use my EPMA enabled version of my Planning app based on Sample.Basic.
To access predefined templates, right click on Rules. Once you give the rule a name, the
graphical designer is launched. In the Existing Objects window, you should find a list of the
pre-existing templates. A list of the system templates follows:
CLEAR DAT A
In order to use the system template to Clear Data, drag and drop Clear Data from the
System Templates to the Rule Designer. This will then invoke a member selection window
asking you to specify the data to clear. Keep in mind that this template generates a calc
script utilizing the CLEARBLOCK command as opposed to a CLEARDATA command.
In my sample app, I select FY11 for the Years dimension and Final for the Version
dimension. The dropdown box for Clearblock Option can be used to define the blocks to be
clearedAll is the default. The code that is generated appears below.
FIX ("FY11","Final")
CLEARBLOCK ALL;
ENDFIX
COPY DAT A
The Copy Data template helps to walk the calc developer through the process of copying data
from one slice of the database to another.
In the remainder of the wizard, you select the Copy From member and the Copy To
member. The calc script generated follows:
FIX (@RELATIVE("Measures" , 0),@RELATIVE("Periods" ,0),@RELATIVE("Product"
DATACOPY "Working" TO "Final";
ENDFIX
AMOUNT -UNI T -RAT E
The Amount-Unit-Rate template allows the developer to build a calc script to solve for either
an amount, unit, or rate, basically whichever is missing. Ive added a couple of measures to
my application to facilitate the demo. Using the member selection wizard, Ive selected
Sales as my amount, Cases as my unit, and Revenue per Case as my rate. The script
generated by the template follows:
"Sales"(
IF ("Sales" == #missing and "Cases" != #missing and "Revenue per Case" !=
"Sales" = "Cases" * "Revenue per Case";
ELSEIF ("Sales" != #missing and "Cases" == #missing and "Revenue per Case"
"Cases" = "Sales" / "Revenue per Case";
ELSEIF ("Sales" != #missing and "Cases" != #missing and "Revenue per Case"
"Revenue per Case" = "Sales" / "Cases";
ELSE
"Sales" = "Cases" * "Revenue per Case";
ENDIF
)
ALLOCAT I ONS
Two types of allocation templates are provided within Calc Manager. The first template,
Allocate Level to Level, allows you to allocate from one level to another. In my example with
my Planning app, you would use this template to allocate marketing expenses from product
family to product using a driver like revenue. This approach utilizes @ANCESTVAL to build
the script.
The second template, Allocate Simple, allocates values based on a predefined relationship,
such as Marketing->Market * Cases/Cases->Market.
Both templates walk the developer through the setup of the allocations, selecting members
that are fixed throughout the process, offset members (if any), etc.
AGGREGAT I ON
The aggregation template aids the developer to create a script to aggregate the application.
The first screen of the wizard, pictured below, allows you to select members for the FIX
statement in the aggregation here you would limit the calc to a particular version, scenario,
or your non aggregating sparse dimension members.
Follow
Follow Edgewater
Ranzal Weblog
The next screen prompts for dense dimensions to aggregate. However, if dynamic calcs are
properly utilized, this should not be necessary.
The third screen asks for sparse dimensions for the aggregation. You should exclude any
non aggregating sparse dimensions from this selection.
Next, youre prompted for partial aggregations of dense dimensions. Again if dynamic calcs
are used properly, this should not be an issue.
In the final screen of the wizard, the developer selects settings for the script
Get every new post delivered
to your Inbox.
Join 51 other followers
Enter your email address
Sign me up
Powered by WordPress.com
The code generated by Calc Manager follows:
SET AGGMISSG ON;
SET FRMLBOTTOMUP ON;
SET CACHE HIGH;
FIX (@RELATIVE("Years" , 0),"Working","Budget")
CALC DIM ("Product");
CALC DIM ("Market");
ENDFIX
Please note that this code is not optimized. In this example, I would use the following:
AGG (Product,Market);
The code as generated by Calc Manager will result in an extra pass through the database
the calc can be accomplished with a single pass. Additionally, AGG can be used in place of
CALC DIM if there are no formulas on the dimensions being calculated. Generally speaking,
stored formulas on sparse dimensions should be avoided due to performance issues.
SET COMMANDS
The next template walks the user through setting various SET commands for the calc. This is
a fairly straightforward exercise.
ONE THOUGHT ON ORACLE HYPERION CALC MANAGER PART 3 WORKING WITH TEMPLATES
Pingback: ORACLE HYPERION CALC MANAGER Part 4 Creating RuleSets
EXPORT DAT A
This is another straightforward template that helps create a data export calc script. You need
to define the fixed members for the export, delimiter, #MISSING value, export type (flat file,
relational), etc.
In the final part of this series, due for posting on August 13, well walk through the creation of
a ruleset. If you have any questions before the next post, please leave a comment!
This entry was posted in HFM, Oracle Hyperion, Planning & Essbase and tagged calc
manager, Calculation Manager, Essbase, HFM, Hyperion, hyperion experts, Oracle,
Oracle Hyperion, Planning, Planning & Essbase by richardsonjeff. Bookmark the
permalink [http://ranzal.wordpress.com/2010/07/31/oracle-hyperion-calc-manager-
%e2%80%93-part-3-%e2%80%93-working-with-templates/] .
You May Like
1.
About these ads
Like
Be the f irst to like this.
RELATED
ORACLE HYPERION
CALC MANAGER Part
1
ORACLE HYPERION
CALC MANAGER Part
4 Creating RuleSets
ORACLE HYPERION
CALC MANAGER Part
2 Creating a Planning
Rule In "HFM" In "HFM"
In "HFM"
Ranzal & Associates Weblog

Working With Template PDF

Încărcat de

Informații document

Titlu original

Drepturi de autor

Formate disponibile

Partajați acest document

Partajați sau inserați document

Opțiuni de partajare

Vi se pare util acest document?

Este necorespunzător acest conținut?

Drepturi de autor:

Formate disponibile

Working With Template PDF

Încărcat de

Drepturi de autor:

Formate disponibile

10/10/2014 ORACLE HYPERION CALC MANAGER Part 3 Working with Templates | Edgewater Ranzal Weblog

S-ar putea să vă placă și