Hyperion Planning 11.1.2 Implementation Boot Camp Laboratory Manual V1

HYPERION PLANNING IMPLEMENTATION BOOTCAMP
18 December 2010
Author:
Roger Cressey
Qubix International Limited
Highclere House
5 High Street, Knaphill
Surrey, GU21 2PG
Tel: +44 (0) 1483 480222
CONTENTS
ENVIRONMENT SETUP LAB INITIATION................................................................ 4

1.1 COPY EXERCISE FILES ................................................................................................................... 4
1.2 LAUNCH THE ESSBASE SERVICES........................................................................................................ 5
1.2.1 Start Services ................................................................................................................... 5
1.2.2 Order For Starting: ............................................................................................................. 5
1.3 BUILDING AN ESSBASE APPLICATION ................................................................................................. 6
ESSBASE MODELLING .............................................................................................. 8

2.1
2.2
2.3
SECTION OBJECTIVES ....................................................................................................................... 8

CREATE NEW ESSBASE APPLICATION AND DATABASE ............................................................................. 8
RESTORING AN ESSBASE MODEL FROM A PREVIOUSLY CREATED DATABASE .............................................. 16
SMART VIEW FOR OFFICE FOR AD-HOC QUERIES AND REPORTS ......................... 19
ESSBASE DIMENSION AND DATA LOADING .......................................................... 23

4.1
4.2
4.3
4.4
4.5
CLASSIC PLANNING APPLICATION DEVELOPMENT ............................................... 38

5.1
5.2
5.3
5.4
SECTION OBJECTIVES .................................................................................................................... 38

PREPARE THE WAY FOR THE PLANNING APPLICATION ......................................................................... 38
CREATE PLANNING APPLICATION..................................................................................................... 43
CREATING PLANNING DIMENSIONS.................................................................................................. 52
OUTLINE LOAD UTILITY ......................................................................................... 59

6.1
6.2
BUILD DIMENSIONS FROM FLAT FILES ............................................................................................... 23

USING ESSBASE LOAD RULES TO POPULATE AN ESSBASE DATABASE ....................................................... 28
ESSBASE DENSE/SPARSE SETTINGS AND DATABASE PROPERTIES, DIMENSIONS, STATISTICS AND STORAGE .... 32
CALC DIM COMMAND AND REVIEW OF BLOCK CREATION AND DATABASE STATISTICS ............................... 32
OPTIMISING ESSBASE - GUIDELINES ................................................................................................. 34
USING THE OUTLINE LOAD UTILITY WITH CLASSIC PLANNING................................................................ 59

EXERCISE 3.4 ADDING AN ATTRIBUTE DIMENSON ............................................................................ 61
DATA FORM DESIGN.............................................................................................. 65

7.1 SECTION OBJECTIVES .................................................................................................................... 65
7.2 FORMS DESIGNER ........................................................................................................................ 65
7.2.1 Create Simple Data Forms ............................................................................................... 65
7.3 COMPOSITE DATA FORMS........................................................................................................... 71
7.4 VALIDATION ON DATA FORMS ........................................................................................................ 73
7.5 CALCULATIONS ON DATA FORMS .................................................................................................... 74
7.6 ADDITIONAL FORM COMPONENTS .................................................................................................. 78
7.6.1 Adjust Data ...................................................................................................................... 79
7.6.2 Lock Unlock Cells .............................................................................................................. 79
7.6.3 Add or Edit Document ...................................................................................................... 80
7.6.4 Grid Spread....................................................................................................................... 80
7.6.5 Account Annotations ..................................................................................................... 81
7.6.6 Cell Text ............................................................................................................................ 82
7.6.7 Supporting Detail ............................................................................................................. 82
Qubix International Limited Hyperion Planning Bootcamp
Page 2
7.6.8 Menus............................................................................................................................... 83
7.6.9 Task Lists .......................................................................................................................... 84
7.6.10
Ad Hoc Browsing in Forms ............................................................................................ 89
8
CALCULATION MANAGER ..................................................................................... 91

8.1
8.2
8.3
CREATE BUSINESS RULE USING CALCULATION MANAGER WITH AGGREGATION TEMPLATE ........................ 91
CREATE BUSINESS RULE USING CALCULATION MANAGER WITH AMOUNT UNIT RATE TEMPLATE................. 95
CREATE BUSINESS RULE SEQUENCE IN CALCULATION MANAGER ........................................................... 96
SECURITY AND ADMINISTRATION ......................................................................... 98

9.1 SECTION OBJECTIVES .................................................................................................................... 98
9.2 PLANNING SECURITY..................................................................................................................... 98
9.2.1 Create New User .............................................................................................................. 98
9.2.2 Create New User .............................................................................................................. 99
9.3 PROVISION GROUP (OR USER) ..................................................................................................... 101
9.4 ADD FORM ACCESS .................................................................................................................... 103
9.5 ADD DATA ACCESS .................................................................................................................. 103
9.6 REFRESH SECURITY ..................................................................................................................... 105
10 PLANNING UNIT HIERARCHIES (PUH).................................................................. 107

10.1
10.2
10.3
10.4
SECTION OBJECTIVES ............................................................................................................... 107

ASSIGN ACCESS TO USERS ........................................................................................................ 107
CREATE PUH......................................................................................................................... 109
CREATE MATRIX APPROVAL ...................................................................................................... 112
11 LIFE CYCLE MANAGEMENT .................................................................................. 117

11.1
LIFE CYCLE MANAGEMENT ....................................................................................................... 117
11.1.1
Log On to Shared Services........................................................................................... 117
11.1.2
Review Planning Artefacts ....................................................................................... 117
Page 3
ENVIRONMENT SETUP LAB INITIATION
In this section, you:

Copy the distributed required files for completion of the exercises
(if using your own machine)
Launch the services required to run Essbase Server, Essbase
Administration Services (EAS) and Smart View
1.1
COPY EXERCISE FILES
Insert the USB drive that is distributed by the facilitator and copy
folder EPMTraining
It is ideal if this could be on the laptop main drive, but will work if
run from a USB Disk if space is at a premium
Students will need approximately 125 gigabytes of disk space free,
the image is just under 110 gigabytes
VMware Player or VMware server can be used to run the image.
Macbook users can use VM Fusion.
Start your Virtual Image.
All class files are already available on the Virtual image in a directory located at:
D:\1BootCamp.
Where the course is being delivered remotely, students will use their own laptop and via the web
connect to a hosted environment using windows remote desktop. Log in credentials and IP
Page 4
addresses will be made available at the start of the course, and be available to each student for the
duration of the week.
Please note that where students will be using their own hardware, it is highly recommended that a
64 bit laptop with at least 8 gigabytes of ram is used for the class.
1.2
LAUNCH THE ESSBASE SERVICES
In this exercise, we will launch all the services necessary for us to use Essbase and its associated
tools as we become familiar with the core technology on which Hyperion Planning is based. The
products we will use are: Essbase, Essbase Administration Services, and Analytic Provider Services
(Smartview Office Integration).
Once the VM image is started we log onto Windows with User: demouser and password:
Demov52
1.2.1
START SERVICES
1.
Log into Windows using Demouser as the user, and Demov52 as the password
(once logged into windows, all Hyperion logins can be accessed by using user:
Admin and password: password)
2.
Start Services
This will require that we start:

The relational database which stores all the metadata for our
environment
The Foundation Services which permissions and provisions our
users
The EPM Process, which initiates our Essbase service
The Weblogic Process which initiates our web or http server
environment
The Analytic Provider Services which facilitate our office
integration tools via Smartview.
1.2.2
ORDER FOR STARTING:
1.
OracleServiceORCL
2.
OracleOraDb11g home1TNSListener
3.
Hyperion Foundation Services Managed Server
Page 5
4.
Oracle Process Manager (EPM_epmsystem1)
5.
Oracle Process Manager (ohsinstance.)
6.
Hyperion RMI Registry
7.
Hyperion Provider Services
8.
Hyperion Administration Services Web Application.
After completion of exercises it is beneficial (..and significantly quicker for shut down) to stop all
the services in the opposite order to that in which they were started.
1.3
BUILDING AN ESSBASE APPLICATION
In this exercise, you will be introduced to the case study that we will use for the entire boot camp.
You will be provided with reports and a sample input data format and asked to plan out the
application structure in terms of dimensions and members.
Review the following report and spreadsheet snapshots, and we will then discuss the
dimensions that we will require in our Essbase model.
Page 6
The Dimensions we require in Essbase are obvious; we will now recreate these lists as dimensions
in an Essbase cube.
We need to foresee the questions that may be asked by the user. To do this it is imperative that we
understand clearly the Business and its processes so that our solution can be fit for purpose.
The dimensions in an Essbase database should reflect your business structure. There will always be
a Measures / Accounts dimension and usually a Time dimension. Dimensionality can be
derived from asking the questions:
What? - Products / Services
When? Regularity of Transactions / Regularity of Reporting /
Periodicity
Who? Which person / Business Unit / Channel / Region
How? Which Medium / method
How much / many? Amount / Value / Quantity.
Always iteratively develop your prototype Essbase model (even when it is for planning) interactively
with the intended user community.
Page 7
ESSBASE MODELLING
2.1
SECTION OBJECTIVES
At the end of this section, you will be able to:

Create a new Essbase Application and Database
Build a new Essbase Database Outline
Use Smart View for Office to do ad-hoc queries and create reports
Build and Run Essbase Data Load Rules
Understand Essbase Architecture: Dense, Sparse, Blocks and Index
2.2
CREATE NEW ESSBASE APPLICATION AND DATABASE
In this exercise, you log in to Essbase Administration Services and create a new Application and
Database.
3.
From the Windows Start

button select All Programs > Oracle EPM System
> Essbase > Administration Services > Start Administration Services Console
Page 8
4.
Under Username, type admin

Under Password, type password
Click OK
5.
Expand Essbase Servers so that Demodrive appears
6.
Right-click on Demodrive and select Create > Application > Using block storage
(you can also Create Application with Demodrive Server selected and by selecting
menu bar item Actions > Create > Application for demodrive > Using block
storage)
The following dialogue appears:
7.
Under Application name, type Shops and click OK.
8.
Expand the Demodrive node so that Applications appears in next level.
Page 9
9.
Expand Applications node so that Shops appears in next level.
10.
Right-click on Shops and select Create database
The Create Database dialog box displays:
11.
Under Database name: type Fin and click OK.
12.
Expand Shops node so that Fin appears in next level.
13.
Expand Fin node so that Outline appears in next level.
14.
Right-click on Outline and select Edit.
15.
Hide/Unhide the Navigation Pane on the left by selecting View and then
uncheck/check Navigation.
16.
Select the Maximize button to display Outline Editor in a larger view.
Page 10
17.
Click on button to Add a child to selected member button (see above) and enter
the Dimensions: Accounts, Periods, Year, Scenario, Organisation and Products.
Please note that when adding members which make use of numeric codes as their member name,
these members should be prefixed with alpha characters. E.g. If an account code for Sales is
100099 then it would be prudent to prefix this code with AC. This would generate a code:
AC100099 as the member name. This ensures that users can clearly distinguish between values
and member names. It is also best practice (in most cases) to concatenate the Alias or description
with its member name. e.g. Sales (AC100099). This ensures uniqueness when using Essbase
cubes which are not set up for Duplicate members. We will discuss the merits of this functionality
as a class.
18.
Press Enter to close the input box
19.
Select Periods and click on button to Add a child to selected member
20.
Enter Time dimensions members: FullYear, Q1, Q2, Q3 and Q4. Include the
months for each quarter, and press Enter to exit Input box
Page 11
Essbase administration Services allows for different levels of confirmation when working with the
Essbase models. This can be amended by going into the Console Options menu, and changing the
outline tools options.
21.
Select the Year member, right-click and select 1st option Edit member properties
22.
The Member Properties dialog box displays, enter Default Alias of Total Year
and click Next button to Save modifications and change selection to the next
member
23.
Update remaining Aliases for Time dimension using Quarter 1, January, February,
March, Quarter 2, April
24.
Add Members for the Accounts dimension. Remember that there are icons for
most of the member properties adjustments, but if in doubt, right click. In the
Hyperion world there is almost always a menu with relevant options available to
the user
Page 12
25.
Tag the Accounts dimension as Accounts and the Periods dimension as Time
using the Member Properties dialog box > Dimension type:
26.
Select one of Account members and Edit member properties , Notice new
properties under Account information
27.
Select Time dimension, right-click and select Dynamic time series
28.
Enable Y-T-D as Gen1 and Q-T-D as Gen2 and click OK
Page 13
29.
After Time dimension you will now see (Active Dynamic Time Series Members: QT-D and Y-T-D). Year is the predefined generation name for the Y-T-D Dynamic
Time Series. If Year already exists as member anywhere in the outline, then
Essbase wont allow a Y-T-D Dynamic Times Series member to be added
30.
Add Scenario members Actual (+), Budget (~), Forecast (~) ActvsBud (~) and
ActvsBudPC (~)with appropriate Consolidation properties
31.
While in the Member Properties dialog box for ActvsBud, select the Formula
tab
32.
Check the checkbox for Insert Arguments and under Math category (or near
bottom of Alphabetical listing), select @VAR function, and double-click @VAR to
move it to the Script pane.
33.
Expand the Scenario dimension and with mbrName1 highlighted, double-click on

Actual, then with mbrName2 highlighted, double-click on Budget
Please note that best practice is to include the member name of the member being calculated in
the calculation script. This is not technically necessary, but should there be a requirement to
change the formula to a calculation script at a later stage, this would make it a much easier
exercise.
The script should show as a minimum @var (actual, budget). We would recommend doing it as
below:
Page 14
Please note that the execute character for Essbase is a semi colon. Without this the formula will
not validate.
34.
Click on the Verify button. The Member Formula dialog box will then show:
35.
Click OK button, then click OK button in Member Properties dialog box
36.
What are two other ways to calculate Actual Budget?

What are the pros and cons of each approach?
37.
Save the Outline and remain in Essbase Administration Services for following
exercise
Page 15
2.3
RESTORING AN ESSBASE MODEL FROM A PREVIOUSLY CREATED DATABASE
In this exercise, you will create a new Shops2 :Fin database from a previously created Outline file in
1bootcamp folder, load a previously exported database. We will complete the exercise by executing
a calculation.
38.
Create a new block storage application: database as before called Shops2:Fin
39.
From the menu bar, select File > Open and in the Open dialog box, with tab on
File System, navigate to D:\1BootCamp\EssbaseFiles\Fin.otl and press OK button.
40.
The outline will appear in the Outline Editor. From the menu bar, select File >
Save As and in Save As dialog box, with tab on Essbase Server, double-click on
Fin, select Fin.otl and click OK button.
41.
Click Yes button
42.
You will then be prompted by Essbase to open the new outline, select the No
button
43.
In Navigation pane, select the new Shops2:Fin. Right-click and select Load data
Page 16
44.
In the Load Data dialog box, click on Find Data File button and in Open dialog
box, with tab on File System, navigate to D:\BootCamp1\EssbaseFiles\explev0.txt
and click OK button
45.
Back in Load Data dialog box click OK button to start the data load.
The Data Load Results dialog box displays:
46.
After confirming Status of Success, click Close button
47.
In Navigation pane, select the Shops2:Fin database. Right-click and select Execute
calculation
48.
The Execute Database Calculation dialog box displays:
49.
Click OK button to initiate the default calculation which will complete almost
instantly
Page 17
50.
In Navigation pane, select the Shops2:Fin database. Right-click and select Preview
data
51.
Take time to experiment as per the facilitator demo:
52.
Double click on dimensions to drill down
53.
Use icons on the tool bar / ribbon to keep, remove only, member select etc.:
This method really is only something that would be used to quickly preview data. A far more
intuitive way of investigating the data would be to use Smartview.
54.
Leave the Essbase Administration Services console open to review the outline as
we work through further exercises.
Page 18
SMART VIEW FOR OFFICE FOR AD-HOC QUERIES AND REPORTS
In this exercise, you will familiarise yourself with using the Smart View for Office to create ad-hoc
queries and reports in Excel.
55.
From the Excel 2007 Hyperion ribbon, select the Smartview tab and click on the
Open button.
56.
Select the Shared Connections link, and this will pop up a login window for
Smartview
57.
Login using the Admin user
58.
Once logged in, you have the opportunity to select an Essbase link, the Planning
link or the General Reporting and Analysis link. For this exercise we are going to
use the Essbase option.
Page 19
59.
Select the Essbase Demodrive option, you will then be presented with a list of
Databases to choose from
60.
Click on the Plus next to Shops2
61.
Right Click on Fin and choose the Ad Hoc Analysis option, this will open an
additional tab in the office ribbon.
62.
The top two dimensions will appear as the top level row and column members
63.
All the other Dimensions will appear in the Point of View drop downs
Page 20
64.
Before beginning navigation, please select the Smartview tab, and click on the
options icon, and select the Member link
65.
Ensure that the Member Zoom In option for Next Level is selected
66.
Now begin to experiment with navigating the data. The first method is to use
mouse clicks:
67.
Double left click zooms in
68.
Double right click zooms out
69.
Left click on a POV dimension and drag it onto the grid to include it on the grid
dimensions
70.
Right click on a grid dimension, pause until the member name prompt appears
then drag it onto the POV selector to remove it from the grid
71.
Use the selector ellipses to enter the member selection form and create drop
downs of the dimension members
Page 21
72.
The Second method is simply to use the Essbase ad-hoc icons on the MS Excel
ribbon
Page 22
ESSBASE DIMENSION AND DATA LOADING
In this exercise you will learn about using Essbase load rules to both build dimensions and load
data.
4.1
73.
Log on to Essbase Administration Services
74.
Expand Essbase Servers node, Demodrive node, Applications node, and Shops2
node, right-click on Shops2 and select Create database
75.
Under Database name type Fin2 and click OK
76.
Now that we have created our database, open up the blank otl file by clicking on
the Fin2 outline node and add the same dimensions we used in the first exercise
we carried out
77.
Please ensure that you save the outline at this point, otherwise the dimensions
will not be available in the Data Preparation Editor we are going to use for our
load rules
BUILD DIMENSIONS FROM FLAT FILES

78.
Right-click on Fin and select Create > Rules file, the Data Prep Editor pane
displays
79.
From menu bar select File > Open data file (NOT Open), select File System tab
and select D:\1BootCamp\EssbaseFiles\DimFiles\ Fin_Account.txt file, click OK
Data source header records can be used if a header row contains all the data load or dimension
build field names. However, we will build our rule by mapping the members.
80.
Toggle the Build Properties Icon
Page 23
81.
Next select Options>Data Source Properties, and going to the Header tab, elect
to skip the first line
82.
Select OK
83.
Now select Field1, row1 of the data prep editor and select: Field > Properties.
When the Field Properties form opens, select the Dimension Build Properties Tab
84.
Now for each of the fields (using the first line of sample data from the Data Prep
editor grid) select the dimension and the relevant field property
Page 24
85.
Do the same for each of the fields in the grid by clicking Next and choosing the
relevant property. All the dimension selections will be Account in this instance
Please note that the fields will not reflect the updated value until you select ok and close the field
properties form. Also if you have set a number of fields by this method and you inadvertently
close the form, your selections will not be saved
86.
Now we need to move a field, as Essbase requires that the Parent field appear
before the Child field in a Parent / Child build file
87.
Select the Child Column, and then click on the move field icon. We could also
select Field>Move from the menu
88.
Select Child and click Down, then select OK. The order of Parent and Child
will now appear as below, and is correct for loading
Page 25
89.
Now select Options>Dimension Build Settings and go to the Dimension Build

Settings tab
90.
Scroll down the form until you reach Build Method and select Use
Parent/Child References
91.
Now select OK
92.
The rule is now ready for saving. First verify it by selecting the Validate icon,
and ensuring it reports no errors
93.
Click on the save icon and name the file BdAcc
Note: it is a good best practice to use a naming convention which is consistently used. In our
company we generally prefix the rule with bd if it is for dimension building, or ld if it is for
data loading. Names cannot contain more than 8 characters if saved as Essbase server objects,
and we normally use as much of the dimension name as makes the name relevant. Hence bdacc
for the dimension building rule for accounts.
94.
Now to update the dimension in the outline, we first open the outline we had
created our dimension headers in. (These must exist, and dont forget to save the
outline!)
95.
Now select Outline>Update Outline (This is only available for block storage not
aggregate storage)
Page 26
96.
Next the Update Outline form will open and we need to select the data file, and
build rule we have created. Make a note of the error file path and then select
OK
97.
Now continue and build the other dimensions in the same manner
We can however take a short cut and use the first line of the file as the header.
98.
You do this by going to the Header tab of the data source properties and
electing to use the first line, rather than ignoring it as we did the first time
around
99.
The need to map the individual fields is now obviated, but we still need to correct
the order of the Parent and Child fields; and set dimension build properties
correctly
Page 27
4.2
USING ESSBASE LOAD RULES TO POPULATE AN ESSBASE DATABASE
Note: Now we are going to first create a flat file of data to load, and then create a data load rule
to load it into Essbase. This method still makes use of the Data Prep editor, and is in fact even
simpler than the Dimension Building rule, in that there is less to map.
When loading data into an Essbase model we need to ensure that each piece of data is referenced
by every primary dimension in the database. We do not need to reference attribute dimensions.
It is also best practice to endeavour where possible to input data at level 0 only. We will have a
class discussion in this regard.
Open an excel spreadsheet and start by typing out all the dimensions in
reverse order of the outline, adding one additional column called data
100.
101.
The optimal way to load data into Essbase is by:

Referencing the most sparse dimensions first and from left to right
arriving at the largest dense dimension on the right
Columns should also be sorted (ascending or descending, as long
as this is consistently applied across all columns) by column from
left to right.
When using files as small as we are working with now, there is no noticeable difference, but
sorting data files (or tables if using relational sources) can result in the difference between
minutes and hours for the load file to process the records and update Essbase. All dimensions
must be correctly built and saved before attempting to load data.
Now we will use Smartview to assist with creating some random data to populate our fields with.
102.
Create around 200 rows of data
On the second tab of the workbook connect to Smartview and our Fin2
database
103.
Before continuing, go to the Smartview tab and select Options. Go to the

Member options and elect to have no indent, and to zoom to Bottom level
104.
Now, a dimension at a time, zoom to bottom level and then copy and paste
the members into the relevant column of our first tab
105.
Page 28
Now using simple excel copy and paste, extend all the columns such that we
create around 200 rows of data
106.
In the data column create the following formula: =ROUND(RAND()*10000,0),

and copy and paste this for each row of data
107.
Lastly save the file as a tab delimited file with a .txt suffix in the
d:\1Bootcamp\EssbaseFiles\ directory. We are now ready to create our data load
rule
108.
Open Essbase administration services and once you have navigated to our
Fin2 database, elect to create a new rule
109.
The data prep editor will open as before, and we now browse to our newly
created data file, by selecting File> Open Data File (Open File will not work!) to
introduce the sample rows into our data prep editor grid
110.
Go to the Options> Data Source Properties, and once you have selected the
Header tab, elect to ignore the first line of the file
111.
Page 29
Now open the Field Properties dialogue once more, and go this time to the
Data Load Properties tab
112.
113.
Next for each field simply select the relevant dimension mapping
Once all dimensions are mapped, you will have only the Data field remaining.
Select Data as the property for this field
114.
Page 30
115.
Validate and save the rule as LdFin
Now, go to the navigation pane and right click on Fin2. Select the Load data
option
116.
Once the Data load form is open, browse to find the .txt data file we
created, and then the LdFin rule we created. Select OK
117.
Lastly calculate the database as we did previously, and then browse the data
in Smartview
118.
Tip: Start by replicating a row of the data from your data file using Smartview, and then zoom
out.
Page 31
4.3
ESSBASE DENSE/SPARSE SETTINGS AND DATABASE PROPERTIES, DIMENSIONS,

STATISTICS AND STORAGE
In this exercise you will review Dense/Sparse settings of the Shop2:Fin database, calculate the block
size and review Database Properties.
From the Essbase Administration Services Console Navigation Pane, select
Shop2:Fin2 Outline, right-click and select Edit, the Outline Editor pane displays
119.
Select Properties tab and scroll down to bottom to review Dimension Storage
Types
120.
Select the Outline tab and expand the dense dimensions by selecting
dimension name and then Outline > Expand to descendants
121.
Count the stored members for each dense dimension remembering to ignore
Shared Members and Dynamic Calc Members and Implied Shared Members
122.
Calculate the Block Size (Dense Dimension1 stored members x Dense

Dimension2 stored members x x 8 bytes per member)
123.

Shop2:Fin2 Database, right-click and select Edit > Properties, the Database
Properties pane displays
124.
Select Dimensions tab and review Type, Members and Member Stored
columns. Notice that no members are stored for Attribute Dimensions. Do values
of Members Stored for Dense dimensions match your calculations from step 4?
125.
126.
Select Statistics tab, does Block Size match your calculations from step 5?
The average clustering ratio of 1.0 indicates no fragmentation. If you experience fragmentation
that degrades performance, consider a database restructure or alternatively, export lev0 data,
clear database, load export file and calculate.
Select Storage tab and review information. When is RLE or ZLIB compression
appropriate?
127.
4.4
CALC DIM COMMAND AND REVIEW OF BLOCK CREATION AND DATABASE ST ATISTICS
In this exercise you will create a Rollup Calc script using CALC DIM command and iteratively add
additional dimensions to gain better understanding of how CALC DIM command works and when
blocks are created.
Shop2 : Fin, right-click and select Clear > All data. The Confirm Database Clear
dialog box displays. Clink Yes button. Database Clear dialog box will then be
displayed. Click OK button
128.
Page 32
Right-click on Fin database and select Create > Calculation script, the
Calculation Script Editor pane displays
129.
On bottom left-hand side of Calculation Script Editor pane, make sure Insert
Arguments is checked and with Categorical tab selected, expand Functional and
scroll down and double-click on SET UPDATECALC
130.
Edit command to be SET UPDATECALC OFF; and press Enter to go to 2 nd line.

Review Essbase Technical Reference to understand details for this command.
131.
Add 2nd command SET MSG DETAIL; and press Enter to go to 3rd line.
Review Essbase Technical Reference to understand details for this command.
132.
Add 3rd command CALC DIM(dimlist); with dimlist highlighted, right-click on

Account and select Insert member name.
133.
From menu bar select Syntax > Check syntax (or use Check syntax shortcut
button)
134.
Page 33
135.
The Calculation Script Editor confirmation box will be displayed:
136.
If there are any errors, they should be displayed in the Messages pane.
From menu bar select File > Save as, and save in Essbase Server, Look in: Fin
as File name: CalcDim and click the OK button
137.
4.5
OPTIMISING ESSBASE - GUIDELINES
There are certain guidelines which should be adhered to when optimising Essbase. One of the key
factors is determining how Essbase creates and stores blocks. This will form part of a class
discussion, however in simple terms:
Essbase calculates in the following order:
Account dimension
Period Dimension
Then dense dimensions from top to bottom in the order of the
outline
Lastly the sparse dimensions from top to bottom in the order of
the outline.
When Calculating dense dimensions, the density of the block is
increased, but no new blocks are created
When Calculating sparse dimensions, blocks are created
The Block size, which is the sum of the stored dense dimension members times 8 bytes;
should be greater than 20,000 bytes and less than 200,000 bytes. With todays high
spec hardware, it is possible to increase this substantially. This should be done
iteratively. The larger the block size, the greater the amount of data to be inserted
into memory. As long as there is reasonable density, and the majority of calculation
is performed within the dense dimensions of the cube, this may allow for significant
improvements in calculation performance.
Block density this is the average percentage of each block which contains data. Multidimensional data is commonly very sparse, and block density of 6% to 8% is good.
Any cube with Density less than 1% is not acceptable
Page 34
The art of good optimisation is finding the perfect balance between the block size and its density.
Cache settings The Essbase guidelines state the following:
Index Cache Setting should equal the size of the index cache on the disk
The Data File Cache should be set to at least 3 times the Index Cache (although this is
not used when the Disk access mode is set to Direct IO it is still a good discipline to
set it)
The Data Cache should be a minimum of .125 of the Data File Cache. In practice that can
be set much larger if performance is slow, and there are lots of dynamic calculations
Outline dimension order Dimensions should be ordered according to the hourglass or
Concave method. Based on the stored members in each dimension, the order goes
firstly from largest dense dimension to smallest dense dimension, and then from
smallest sparse dimension to largest sparse dimension. Any dimensions which are
not calculated can be put to the bottom of all the other dimensions. This order
optimises the number of passes which Essbase needs to make through the database
while calculating
To see the impact of calculating Dense versus sparse dimensions, lets first
prepare our database
138.
First clear all data from Shops2:Fin2 do this by right clicking on the Fin2
database node in EAS and selecting Clear > All Data
139.
Next import the level zero random data file which we used in our earlier
exercise
140.
Page 35
In Navigation pane, select the new Shops2:Fin. Right-click and select Load
data
141.
In the Load Data dialog box, click on Find Data File button and in Open dialog
box, with tab on File System, navigate to D:\BootCamp1\EssbaseFiles\explev0.txt
and click OK button
142.
Right click on the Database and select Edit>Properties. Then select the
Statistics tab. Take note specifically of the Existing Blocks level0 and Upper, and
the Block Density.
143.
Next right click on the Fin2 database and select Execute Calculation. Select
the CalcDim calc and click OK
144.
Now refresh the statistics tab, and look for the differences. Note that as a
minimum the number of blocks will not have changed.
145.
146.
Now browse to the CalcDim calc and right click on it, electing to Edit it
Page 36
147.
Change Account to Product and execute the calculation
148.
Now review the statistics once more. What do you notice?
Notice that more blocks have now been created because we calculated a sparse dimension.
Therefore to optimise Essbase calculation, endeavour to perform all the calculations in the Dense
dimensions while there are fewer blocks which need to be calculated, and then aggregate the
sparse dimensions last.
Page 37
CLASSIC PLANNING APPLICATION DEVELOPMENT
5.1
SECTION OBJECTIVES

Create a new Planning Database,
Application and Data Source
Model the Dimensions and
Members in the new Planning
Application
Use the Outline Load Utility to load
or refresh dimensions in the
Planning Application
5.2
PREPARE THE WAY FOR THE PLANNING APPLICATION
In this exercise you will create the Hyperion Planning Relational Database Repository which stores
Planning metadata and security and then a Data Source. Each Planning application must be
associated with a Data Source, which links the relational database and the Essbase server
For the exercises in this section, we need to start the same services as we did
for the first exercises, but in addition to start the services required for us to
access the Workspace, and Hyperion planning. We will also start the Calculation
Manager service
149.
In this instance we have provided a start up script for ease to carry out the
initiation of all the right services in the right order
150.
The script can be found in the d:\1Bootcamp\Scripts directory and is called

StartPlanEssential.bat
151.
One could double click on it to activate it, but it is better to run it inside a
DOS command prompt window so that we can view progress
152.
Page 38
153.
Open a command prompt and then type in D: and hit return
154.
Next type CD 1Bootcamp\Scripts and hit return
155.
Lastly type StartPlanEssential
Once you hit the return key this will initiate all the services required for our Planning exercises. This
takes some time to start all services as in some cases the services have to fully initiate prior to each
dependant service starting.
Please note that to stop all services at the end of the day, instead of StartPlanEssential in Task
154, type StopAllServices and enter.
We are going to create an application to facilitate the Planning process of a specialist Fashion
Department store called Hallsworth and Sons. In keeping with this we will name all objects to do
with the application Hallsworth, or where only eight characters are permitted, Halswrth
Open a new Internet Explorer window and on the home page in the left hand
frame, go to Oracle Database DemoUtilities
156.
On the left-hand side of page, expand Oracle Database DemoUtilities and

click on Create User to display C:\Home\CreateUser.html page on right as shown
below:
157.
158.
Double-click on RunCreateUser.exe
Create User Utility dialog box displays
Page 39
159.
Enter Oracle User Hallsworth and click OK button
OK Pressed dialog box displays:
Now we can create a planning data source file. You will require one of these for each planning
application. Although we have a planning system database, a new relational database, and a
new Essbase application are created each time we create a new Planning application. The data
source provides a means of telling each application which relational schema and Essbase
application it will make use of.
160.
Open a new internet explorer window
161.
On right, select Oracle EPM Workspace link under Workspace
The default link, should it be required, is

http://servername:19000/workspace
162.
http://demodrive:19000/workspace/index.jsp page displays:
Page 40
Login to the screen as the Admin user, once again using password:
password. The screen below will appear:
163.
Click on Navigate and then browse to Classic Application Administration ->

Planning Administration
164.
Page 41
On the next screen select the option Manage Data Source, and the
following form will be presented
165.
Next we elect to Create Data Source, and complete the following fields, as
shown in the example below:
166.
Page 42
The database schema Hallsworth and password password you created

earlier are used for the Oracle database, while admin and password are used
for the Essbase connection
167.
168.
5.3
Once finished, the data source will appear in the list of data sources
CREATE PLANNING APPLICATION
Now we have a data source we can initiate the wizard which will step us through the creation of
our Planning Application.
Once the Data Source has been created click on Create Application, and
complete the following fields, as shown in the example below:
169.
Page 43
170.
The only available Data Source is pre-populated in the form
We will use the Default Application Group. If this were for a specific Project
or Division we could create a new project specific for the purpose and all
applications: Essbase, Planning, HFM, HPCM, HSF where relevant would all
reside in that project
171.
The Application is a general one, and not Public Sector or a sample

application
172.
We can use either Calculation Manager or business rules to create calculation

scripts for our application. We will use the most recent addition to the Oracle
EPM stable in this respect
173.
174.
Next we set the Calendar options:
175.
Our plan will be generated at the month level of granularity
We will start our model from 2010 and include 3 years using January as our
Fiscal start month
176.
177.
We will use an even weekly distribution
Select Next and we move onto the Currency tab. We will not be using
Currency during our training
178.
Page 44
Select Next to go to the Plan Types tab. For the purposes of our exercise, we
will only really use one Plan Type. However, we are going to create a Workforce
Planning Plan type just to demonstrate how to initialise the prebuilt modules sold
by Oracle:Hyperion
179.
Our standard Plan will be called Fin, and our Workforce Plan will be called
HR
180.
Click on Next and we are presented with a summary of all the options we
have selected
181.
Page 45
Once we select Finish, Planning will take a minute or so to create our new
Planning application
182.
The final Result!
Page 46
At this stage, all of the static Dimensions for our applications have been created in the
Relational schema, and the Application placeholder has been created in Essbase.
Page 47
Now we are going to create the two databases, which constitute the application in Essbase. At this
time all the dimension data exists only in the relational database, and not in Essbase.
Click on Administration > Application > Create Database. When the form
opens, select just the Database check box, and then the Create button
183.
184.
Click on Create, and a confirmation window will pop up
At this point the Essbase databases relating to the Halswrth application have been
created.
Page 48
Open the Essbase Administration Services Console and View Halswrth: Fin to
see the Dimensions and members which have been created as a result of our
initial Planning wizard selections
185.
Next we will initialise the Workforce Planning database. This has the result of creating all the
dimensionality required for workforce planning in both the Fin and the HR database
Go to Administration > Initialization > Workforce. You will be asked to verify
that you do want to initialise Workforce planning. This is because the process
does result in the addition of new dimension members, forms and Business rules
186.
Page 49
Once this has been completed, we have to push the changes through to our
Essbase databases. Do this by going to Administration > Application > Refresh
Databases
187.
Please note that any changes carried out using the Classic Planning Web Interface only exist in
the Planning Application Relational database until such time as a Database Refresh or if the
necessary Database Create process is run.
This is almost identical to the Create database we carried out earlier. Once
complete, go and verify that the Essbase dimensions have been updated
188.
We are now going to add a Product dimension to the Fin database. We will
not need to Plan our workforce by product, but we will use Price and volume of
Products to derive our income numbers for the Fin Plan
189.
Page 50
Go to Administration, manage Dimensions and click on the Add dimension

button
190.
191.
In the dialogue fill in the fields as per the screenshot below:
You will be asked whether you really want to add a new custom dimension. This is because once
the dimension has been created there is no simple way to remove it.
We can now begin to add dimension members to our Dimensions. Using the
same dimensions we used to build our Essbase model, begin to replicate these in
our Planning model. Begin with the Account dimension and progressively work
through the other dimensions
192.
This will form a large part of the following lab exercise.
Page 51
5.4
CREATING PLANNING DIMENSIONS
In this exercise you will learn how to change member names and aliases, add members to existing
dimensions, add Account members and understand Account Types, add Custom Dimensions and
add Attribute Dimension.
From menu bar on Halswrth page, select Administration > Manage >Alias
Tables. On Alias Tables page click the Add button
193.
Enter name for new Alias Table I have used Afrikaans, but use any language
you might be comfortable with
194.
Now go to Administration > Manage > Dimensions, and select Period from
the drop down list
195.
Page 52
Expand YearTotal and Q1, select Jan and click the Edit button. Enter a default
alias. Then change the value for the Aliases drop down list from Default to
Afrikaans and enter an Alias of Januarie and click Save button
196.
Do this for all months. If you wish to use Afrikaans aliases, they are as
follows:
197.
Jan = Januarie
Feb = Februarie
Mar = Mars
Apr = April
May = Mei
Jun = Junie
Jul = Julie
Aug = Augustus
Sep = September
Oct = October
Nov = November
Dec = Desember
198.
Carry out a Refresh Database as previously
Open Essbase Administration Services Console and Edit Halswrth:Fin Outline

to confirm changes to Period member Names and Aliases
199.
To change Alias table, go to Properties tab, under Alias tables right-click on

Afrikaans and select Set as Active
200.
Page 53
201.
Return to Outline tab and confirm Afrikaans aliases for Jan, Feb and Mar
202.
Return to Properties tab and reset Default as the Active alias table
203.
Close Outline Editor
Now to create some additional scenarios:

From menu bar on Halswrth page, select Administration > Manage >
Dimensions
204.
205.
From the dimensions drop down list select Scenario
Select Current and Delete it (We will be creating a Current member in

Versions)
206.
Note: One of the ways in which we can restrict input periods is via the use of start and end period
settings in the scenario. For example, if we set the Start Yr to FY10 and the start month to Jan,
and the End Yr to 2010 and End Period to Dec for a particular scenario; this would mean that this
scenario would only accept input for the periods Jan to Dec in 2010.
Select Actual and click the Edit button. Change to Start Yr: FY10, de-select
the checkbox next to Enabled for Process Management
207.
We want to ensure that there is no input to the Actual scenario. To do this

we leave no open periods, and so it should have the following
characteristics:
Scenario: Actual
Start Yr.: FY10
Start Period: Jan
End Yr.: FY10
End Period: Jan
Alias: Act
Enabled for Process Management: de-selected
Click Save button
208.
We only want to allow Budget input between Jan and Dec of 2010.
Next edit Budget:
Scenario: Budget
Start Yr.: FY10
Start Period: Jan
End Yr: FY10
End Period: Dec
Alias: Bud
Enabled for Process Management: selected
Click the Save button
Page 54
Next edit Forecast, we want to ensure that input can be accepted in

Future years periods as well as the current one:
Scenario: Forecast
Start Yr: FY10
Start Period: Jan
End Yr: FY12
End Period: Dec
Alias: Fcst
Enabled for Process Management: selected
Click Add Sibling button and enter following values:
Scenario: ActvsBud
Start Yr: FY10
Start Period: Jan
End Yr: FY10
End Period: Jan
Data Storage: Dynamic Calc
Enabled for Process Management: unchecked
Click on Member Formula tab and
Enter Member Formula: @VAR(Actual,Budget);
Validate Member Formula does not provide accurate validation until such time as the component
calculation members have been created in Essbase.
Click Add Sibling button and enter following values:

Scenario: ActvsFcst
Start Yr: FY10
Start Period: Jan
Page 55
End Yr: FY10

End Period: Jan
Data Storage: Dynamic Calc
Enabled for Process Management: unchecked
Click on Member Formula tab and
Enter Member Formula: @VAR(Act,Fcst);
Click the Save button.
Before continuing please refresh the database to ensure that our changes are pushed through to
the Essbase database. (Administration > Application > Refresh). Next we will set up our version
dimension.
Dimensions
209.
On Dimensions tab and from Dimensions drop down list select Version. Select
BU Version_1 and click Edit button
210.
211.
Change Name: to Current and Alias: to Working and click Save button
212.
Click Add Sibling button and enter Version: 2ndPass and click the Save button
213.
Click Add Sibling button and enter Version: Final and click the Save button.
Once again refresh the changes through to the Essbase database before continuing.
Now we need to go and make the additions we require to create the Accounts hierarchy. As per the
Essbase exercise we will now go and replicate that hierarchy in Planning.
Dimensions. On Dimensions tab and from Dimensions drop down list select
Account. Create the Account hierarchy based on worksheet below from
D:\1BootCamp\EssbaseFiles\ExampleReport.xlsx (you may want to open the
worksheet in order to cut and paste Account member names)
214.
For appropriate higher level Account members (e.g. Total Cost of Sales,
Allocated Costs, Operating Expenses and Taxes) change Account Type: to
Expense and use Subtraction after Plan Types: for both Fin and HR
215.
When you add descendants of these members, they will default to expense.
216.
Leave default of Source Plan Type: Fin
217.
Also add Metric accounts:
Select Net Sales, click Add Sibling button and enter:

Name: Metrics
Page 56
Plan Types: Ignore (for both Fin and HR)

Click Add Sibling button and enter:

Name: Rebate % Sales
Account Type: Expense
(Variance Reporting: will also change to Expense)
218.
Select the Member Formula tab and Enter member Formula:

i. Rebate % Sales = "Rebates" % "Auto Sales";
219.
Optional Additional Measures

Click Add Sibling button and enter:
Name: Average Inventory
Account Type: Asset
220.
221.
Refresh the Essbase database with changes made
Open Essbase Administration Services Console and View Halswrth:Fin Outline

to confirm Account hierarchy Member Names, Consolidations and Expense
Reporting properties. Close Outline Editor
222.
Right-click on Halswrth:Fin and select Set > Default calculation , add SET
UPDATECALC OFF;
223.
Page 57
224.
Click the OK button
Now that you are familiar with the means of manually adding members and their respective
properties, we are going to complete the main build of our Entity and Products hierarchy by using
the Outline Load Utility. This is one of a number of different methods for building and maintaining
hierarchies in Hyperion Planning. We will have some discussion in class around the different options
and their strengths and weaknesses.
Page 58
OUTLINE LOAD UTILITY & ADDING AN ATTRIBUTE DIMENSION
6.1
USING THE OUTLINE LOAD UTILITY WITH CLASSIC PLANNING
In this exercise you will learn how to use the Outline Load Utility including setting up Password
Encryption and how to load dimension members into a Planning Application. This works in a very
similar fashion to our Essbase dimension building rules.
We have created example scripts which you may make use of, but if you
wish, you can create your own
225.
Open D:\1BootCamp\PlanningFiles folder and open up the hp_admin.pdf. Go

to page 79 of the guide, and use this guide to set the parameters you wish to use
to build your dimensions. The section continues through to half way down page
107
226.
227.
Open a Command Prompt Window by selecting
shortcut
228.
Type in D: and then Enter to get you to the correct drive
Next type: CD
Oracle\Middleware\EPMSystem11R1\products\Essbase\eas\console\bin
229.
The PasswordEncryption utility creates a file that stores the password in

encrypted form and is used to suppress password prompts for Planning utilities
using the [- f:passwordFile] option as the first parameter in the command line
230.
Type PasswordEncryption \1Bootcamp\CommandLineUtility\password.txt

and press Enter. After prompt to Enter password to encrypt, enter password. You
should see message Password has been encrypted and written to the file
successfully
231.
Page 59
Once we have created our source file in the correct format.

(CommandlineUtility requires headings to be exactly right), and our command
files with the necessary parameters, we can go and run these to update our
Planning application
232.
It is possible to include multiple dimension building commands in one file, but

we separate them out for ease of bug fixing
233.
Run the files in our case is to use a command prompt to browse to the
1Bootcamp\CommandLineUtility folder, and then to execute the cmd file by
typing its name at the prompt
234.
Check the resultant logs in folder: D:\1BootCamp\CommandLineUtility to be

sure no error messages were generated. Do this for Account (if you did not finish
building it manually), Entity and Product
235.
Dimensions. Review new members for Entity, Products and Products dimensions.
Select Administration > Application and Refresh Database
236.
Now that we have built the main dimensions, we are going to go and tidy up. First take note that
some dimensionality is only for one plan while other dimensionality is used in both. Fin has a
product dimension which Hr does not require, and Hr has an employee dimension which fin does
not require. In the accounts dimension there are a number of accounts which are only valid for one
Page 60
plan or the other. Having built our accounts dimension from a load file, we need to verify that we
are happy with what has been built.
You will notice accounts that are product related in the HR plan. We could go and amend these so
that they do not appear in the HR model. However, it is common that drivers or key indicators may
be derived from sales information for staff. Where the account dimension is small there will be no
problem with leaving these dimension members valid for both plans.
237.
Open D:\1BootCamp\EssbaseFiles\HalswrthInput.xlsx
Select Data Source Manager and connect to Halswrth:Fin database using

right-click and selecting Ad-hoc Analysis
238.
When you open a workbook which was previously used with the Smartview
add-in, you will be asked whether you wish to: clear the sheet, leave the grid
members on the sheet, or leave the grid members and the POV as they are
239.
Ensure that you select the one which allows you to retain both the grid
members and the point of view members
240.
241.
Submit both the income and expense tabs of the workbook
Select the icon for Calculate, select the Default Calculation Script for Fin Cube
and click Launch button
242.
Calculation Script has been processed dialog box displays. Click OK button
and click Close button to close Calculation Scripts dialog box
243.
Select the ExampleReport worksheet and connect to Halswrth:Fin database

using right-click and selecting Ad-hoc Analysis. Select No button so that the
contents of the sheet are NOT cleared
244.
245.
Confirm that value for Net Sales matches that of the Examplereport.xlsx
If there are differences, identify differences, make corrections to Account

members, Refresh Database and revalidate
246.
We are briefly going to explore adding an attribute dimension before we move onto the form
design section of our workshop.
6.2
EXERCISE 3.4 ADDING AN ATTRIBUTE DIMENSON
We are going to create an attribute of StoreType to associate with our Entity dimension.
Dimensions. Then select the Entity dimension from the drop down list
247.
Click on the Custom Attributes button and then on the resultant form, elect
to create
248.
Page 61
Click on the Custom Attributes button and then on the resultant form, elect
to create
249.
Once this has been created, StoreType will appear as an option on the right
hand side of the form. Now click on Create on the right hand side of the form,
and insert the 3 entries as above Now we can associate these attributes with the
stores, allowing us to analyse our chart of accounts by Storetype, rather than just
Store or Region which already exist in the hierarchy
250.
Now navigate to the Ldn: London member, and click Edit. Select the
Attribute Values tab, and select one of the Storetype attributes we have just
created
251.
Page 62
This can be done manually via this interface, or automatically as part of a dimension build routine.
We have now built our dimensions but before we move onto building forms we should verify that
the dimensionality is ordered correctly, and that the evaluation order is initiated.
Select Administration > Manage > Dimensions. Once the dimension manager
frame set is open, click on the Performance Settings tab. The dimensions are
listed with their Dense / Sparse characteristics, and the numbers of stored
members for each dimension
252.
Select the radio button for a dimension you wish to re-order and then click
on the up and down arrow to put it in position
253.
254.
Lastly, select the Evaluation order tab
This has particular importance once we begin to create menus and smart lists as it determines in
which order the objects will have priority when operating more than one object on a form. If the
evaluation order is not set, menus and smart lists will not work.
It is safe to set the order as a minimum for the dense dimensions. Convention is as
below:
Page 63
Page 64
DATA FORM DESIGN
7.1
SECTION OBJECTIVES

Design new data forms including Asymmetric, Tabbed and
Composite forms
Perform Validation in the web forms
Create new Business Rules with Prompts and link them to Data
Forms
Use additional Data Form Components including Adjust Data, Grid
Spread, Account Annotations, Planning Unit Annotations, Cell
Text, Cell Level Documents, Supporting Detail and Menus
Use the Ad Hoc mode for browsing web forms.
7.2
FORMS DESIGNER
In this exercise you will design basic forms and then be shown how to design more complex
Composite and Tabbed forms.
7.2.1
CREATE SIMPLE DATA FORMS
Start services as before, but at the prompt D:\1Bootcamp\Scripts> type

StartPlanExclRA.bat
255.
256.
We will first create three initial forms to use for the new Planning application:
for entering Unit Sales and Prices, and other Sales Income
Page 65
for entering Operating Expenses

one for entering Allocated Expenses.
From menu bar on Halswrth page, select Administration >Manage > Data
Forms. Click on Create button above Data Form Folders
257.
You will be prompted to enter a new folder name:
258.
Enter - BootCampForms
259.
Click on Create button above Data Forms
Page 66
Enter Data Form name 1 Volume and Price Capture, Enter Instructions and
click on Next button
260.
Plan Type defaults to 1st Plan Type Fin. This determines the data form's valid Account and
Entity members. Accounts included on data form with a source plan type other than the assigned
data form plan type are read-only on that data form. You can NOT change the Plan Type for Data
Form after it is assigned.
On this Layout tab, there are four key areas where dimensions can be dragged to:
Drag by selecting
and change member selection by clicking on
. When selecting multiple Row or Column members you have

the option to put selections in separate rows or columns
POV Point of view, this allows for one member to be selected
which will filter all data on the grid
Page This allows for multiple member selection which on the
form will allow for a single selection of data to show at a time via a
drop down selection box
Rows This allows for multiple selections of dimension members,
and nesting of multiple dimensions
Page 67
Columns - This allows for multiple selections of dimension

members, and nesting of multiple dimensions
The layout for our first form should look like the screenshot below:
Specification:
POV Members: Year - FY11; Scenario Budget; Version 1st Pass
Page Members: Account Unit Sales, Price, Other Sales Income
Organisation All level 0 Descendants
Row Members: Product All level 0 Descendants of Total Products
Column Members: Period All Descendants of YearTotal
Please note that you can functionally select (children of.., descendants of etc.) by clicking on the
icon in between the two panes as below; or just select individual items.
Page 68
Please note that when you first open the form, it will be greyed out such that you will not be able
to input data to it. Why do you think this is? The clue is in the start and end periods set for the
Scenario Budget.
Amend these dates such that the end period includes FY11, and then try again...... you will now be
able to enter data into level 0 items.
As data is entered, cell background colour changes from white (default) to yellow indicating dirty
cells, whose values changed but are not yet saved. Cells in the Net Sales row have background
colour of light blue indicating read-only cells
In left-hand pane, under Folders, expand Forms, select BootCampForms and
select 1 Volume and Price Capture data form and wait for the form to be
rendered
261.
From menu bar, select Administration > Manage > Data Forms. Expand Forms
folder, select BootCampForms folder and follow above steps to Create data form
2 Operating Expenses
262.
Specification:
POV Members: Year - FY11; Scenario Budget; Version 1st Pass; Product NoProduct
Page Members: Account Operating Expenses and its children
Row Members: Entity - All Descendants of Organisation
Column Members: Period All Descendants of YearTotal, and YearTotal
Page 69
From menu bar, select Administration > Manage > Data Forms. Expand
Forms folder, select BootCampForms folder and follow the above steps to Create
data form. 3 Cost of Sales
263.
Specification:
POV Members: Year - FY11; Scenario Budget; Version 1st Pass; Entity No Entity;
Product No Product
Page Members: None
Row Members: Account Total Cost of Sales and descendants
Column Members: Period YearTotal and Descendants
Please note that settings for the appearance of Grid, Row and column members appear
in the right hand panes as you select the relevant area.
Page 70
Next we go to the other options tab. Here we can determine the general
behaviour of the form. The options are self explanatory, but experiment with
them to be comfortable with what they do
264.
7.3
COMPOSITE DATA FORMS
Now we will create one form to enter Volume and Prices, as well as Operating Expenses.
Page 71
From menu bar on Halswrth page, select Administration > Manage > Data
Forms. Expand Forms folder, select BootCampForms folder and click on Create
button to create data form - 4 Composite Form
265.
266.
On Properties tab enter Data Form name Composite and click Next button
You will be presented with three options:

Custom
Columns
Rows
267.
Select Rows, and the next screen will look as below:
Drag Volume and Price Capture onto the top panel, and Operating Expenses
onto the bottom panel
268.
269.
Select the Top Panel, so that 1 Volume and Price Capture is in focus
Page 72
Now type into the Section Name placeholder Price Mix, and format the
text to something colourful using the T icon next to it
270.
271.
Next rename the bottom panel section name, and format the text
Decide which dimensions you wish to control from the Global form controls.
Any Global POV or Page Members must be POV or Page Members on their own
form, to be valid member for the composite form
272.
273.
Preview the form to see that you are happy with the way the form looks
Note: Where possible, try and keep the dense dimensions the closest ones to the grid for optimal
performance.
7.4
VALIDATION ON DATA FORMS
Go to Administration > Manage > Forms and elect to Edit the 2 Operating
Expenses Form
274.
275.
Save the form as 5 Operating Expenses with Validation, and click Finish
276.
Open the new version of the form for data input
Open the excel workbook at D:\1Bootcamp\PlanningFiles\Operating

Expenses data.xlsx
277.
278.
Copy and paste the data into the form and elect to save the data
Go to Essbase Administration Services, right click on Halswrth: Fin and

calculate the database using the default calculation
279.
Go to Administration > Manage > Forms and elect to Edit the 5 Operating
Expenses Form with Validation
280.
Click on the corner cell between rows and columns. To add validation either
click on the down arrow and choose Add or edit validation or click on the Green
Plus sign
281.
Please note that it is possible to create validation for the Grid, individual rows and individual
columns.
When the Data validation rule form opens, name it ExpensesValidation,
and set the location to Column A
282.
283.
Next add criteria as below:
Page 73
Save and Preview the form. Then select Finish and go and open the form for
data entry. Insert a value greater than 20,000 to verify that validation occurs
284.
7.5
CALCULATIONS ON DATA FORMS
Go back to the Forms management area. Now elect to edit form 5 Operating
Expenses with Validation, and immediately save it as 6 Operating Expenses
with more complex Validation
285.
Go to the Layout tab and add a new calculated column by right clicking on
column B and selecting Add Formula Column
286.
Page 74
287.
Name the column Contribution and then click in cell C1
Select PercentOfTotal from the drop down list and add the arguments
[B],[B,1] inside the brackets
288.
Lastly apply rounding to two decimals by adding the Round(,2) syntax as

per the screenshot below
289.
290.
Validate the formula by clicking the
button. If the syntax is correct a
green flag will show next to it

291.
Save and Preview the grid to verify that the results are what you expect
292.
Add another row by right clicking on row 1 and electing to add a Formula row
293.
Name it Total on Form and create a sum formula as per the screen shot
Page 75
Note that our grid validation now highlights all the totals because they are
over 20,000. Edit the Validation rule and change its Location to Cell A1
294.
295.
Save and Preview the form to ensure that only cell values are validated
296.
Next, Select column C
Click on the green plus sign

to the right of the box which should be
headed Validation Rules: Column C
297.
Name the rule PCTolerance and then add conditions as per the screen shot
below
298.
Page 76
= Remove Condition
= Add Condition
= Cut Condition
= Copy Condition
= Paste Condition
= Process (This allows you to define what action will occur).
Note: Create, save and test one condition at a time to ensure you are on the
right path, returning to Edit the rule for each successive condition.
299.
300.
Validate the rule and if you have it correct, you will see:
Next Select Row 2, and click on the green plus

rules box, which now refers to Row 2
301.
302.
Set the location to Row 2
303.
Name the rule TotalTolerance
adjacent to the Validation
Page 77
304.
Add conditions as per the screen shot below:
After validating the rule, save the form and open it in data input mode and it
should look like this:
305.
We will revisit Validation once we have created our Planning Unit Hierarchy to manage the
workflow process.
7.6
ADDITIONAL FORM COMPONENTS
In this exercise you will gain experience using Data Form capabilities and components including
Adjust Data, Grid Spread, Account Annotations, Planning Unit Annotations, Cell Text, Cell Level
Document, Supporting Detail and Menus.
From left to right, these icons are:

Save, this saves any data that has been entered into the web form
Page 78
Refresh, This will refresh the form. If you have input data without saving, selecting this will
have the effect of cancelling the input
Print, this will generate a Print dialogue
Adjust Data, facilitates the increase or decrease of data by a percentage or value
Grid Spread, this facilitates the spreading back of an amended number across a block of
data
Mass Allocate, this facilitates the spreading of adjusted data using cross dimensional
Comment, allows input of text comments
Lock / Unlock, this allows for cells to be locked or unlocked when wanting to exclude from a
proportional spread across time periods when inputting into an aggregated time period
Supporting detail, facilitates creation of additional granular levels of dimensionality for
more detailed data input
Add / Edit Document, attached to the Planning Web Form
Open Document
Cut
Copy
Paste
Instructions
Open in Smartview, opens the existing form in Excel automatically passing on the users
credentials
Task List, allows the user to at any time view their progress through their task list
Note: the majority of these functions are available from right click menus once initiated.
306.
Open 1 Volume and Price Capture data form
307.
Ensure that Unit Sales and London are selected in the page drop downs
Enter 120,000 units in the YearTotal Column, this will then break back,
inserting 10,000 units in each month for Mens Casual Shirts
308.
309.
7.6.1
7.6.2
Click the save icon to insert the data into Essbase
ADJUST DATA
310.
Now select Jan, Feb and Mar, and click on the adjust data button
311.
In the mini form that is generated elect to increase by value 500
312.
Each of the months is increased by 500 units, save when done
LOCK UNLOCK CELLS
Now lock the cells using the Lock / Unlock icon, you will notice the cells go
Brown
313.
Page 79
Insert 120,000 in the Total Year cell, you will notice that the break back now
spreads proportionally across all the cells except for those that were locked
314.
7.6.3
ADD OR EDIT DOCUMENT
Select Jan data cell for Mens Casual Shirts and click on the Add/Edit
Document icon. When the dialogue opens, browse to sample content and add
the html document to the cell
315.
You will notice that the cell now has a comment triangle in the top right hand corner. Before
you add a cell-level document, the document must be added to the Workspace repository.
Click on the Open Document Icon, and the document will be opened in
workspace
316.
7.6.4
GRID SPREAD
Next, we need to change the Accounts dimension to Stored as opposed to

Dynamic. Do this by going to Administration > Manage > Dimensions, and change
the properties for Cost of Sales and its descendants
317.
318.
Refresh the changes through to the Essbase model
Go to Administration > Manage > Data Forms and on the layout tab, change
the Version POV to 2ndPass
319.
Now insert 60,000 into YearTotal; Incentives and Rebates. This will spread
back across the months
320.
Now, click on the grid spread icon and elect to adjust the amount by 5000
and proportionally spread
321.
Page 80
The result will appear like this:
Grid Spread is only available with Versions defined as Standard Target where Values are
entered from the parent level down. Versions defined for Halswrth were all Standard Bottom Up
Where Values are entered at the lowest member level and aggregated upward.
Note: We will revisit Planning annotations after we have initiated workflow.
7.6.5
ACCOUNT ANNOTATIONS
Open 3 Cost of Sales form. From menu bar select View > Edit Account
Annotations. This option is greyed out, by default Account Annotations are NOT
enabled for data forms. If this is not enabled the form will need to be edited, and
on the other options tab, Enable Account Annotations must be checked.
322.
323.
Enter annotations as shown below:
Save form, select different Page settings and click Go button. Notice that
Account Annotations remain with form across all Page combinations
324.
Page 81
7.6.6
CELL TEXT
Open 1 Volume & Price Capture data form. From menu bar select Edit >
Comment
325.
Enter text and click on Submit button. Cell Text indicator will appear in upper
right-hand corner of cell and message This cell has cell comment displays when
cursor hovers over cell
326.
7.6.7
SUPPORTING DETAIL
Open 1 Volume and Price Capture data form. Highlight cells for Mens Casual
Shirts Jan, Feb and Mar. Select Edit> Supporting Detail. Enter the data as below:
327.
328.
Now save and the cells will be shaded blue as below:
Cells change to a teal background colour indicating cells have supporting details. The cell values can
no longer be changed on the data form, values can only be changed by updating the Supporting
Detail.
Page 82
7.6.8
MENUS
From menu bar select Administration > Manage > Menus

Select the Create button and a dialog box displays. Enter ReportJump and click
the OK button
329.
330.
Once created, select the box next to ReportJump and click Edit
331.
Once the edit menu appears, select add child
332.
Enter details:
Menu Item Item1
Label Sales Input
Type Data Form.
Once saved, click add sibling and add a similar entry for forms 2
and 3
333.
Next go to Administration > Manage > Data Forms,
334.
Go to the other Options tab
335.
Select ReportJump from the Available Menus
336.
Click Save and then Finish
Page 83
Now go and edit forms 1 through 3 by going to the Other Options tab in each
one and adding the menu ReportJump to the forms
337.
Now open any of the forms we have edited and ensure that the right click
menu now includes our 3 options. Verify that when selected the correct form
opens
338.
7.6.9
TASK LISTS
Task lists allow users to step through a Planning Process. They are usually function specific. E.g.
There would be a task list for Sales people, another for the Marketing teams, and another for
Financial Controllers and Executives.
339.
Go to Administration > Manage > Task Lists
Page 84
340.
Click on Create
341.
Once it is complete, select the check box for Regional and click Edit
342.
Now click Add Child, and the following Form is generated
Page 85
343.
Fill in details for the Task name, and select the Data Form type
344.
Complete the Due Date details as above
345.
Now continue and complete the other entries as below
346.
A task for Operating Expenses
347.
A task for Cost of Sales
Page 86
348.
A Task to run our Business Rule
Please note that you will only be able to carry out this task once you have completed the
workshop on Calculation Manager (Chapter 8). Remember to revisit this.
We should end up with 5 Tasks once we have added the task for Business
Rule later on
349.
If you create the task in the wrong order, select its check box and use the up
or down arrow to reposition it
350.
Page 87
7.6.9.1 ASSIGN ACCESS TO TASK LIST
Please note that you will only be able to assign access to users once we have created them in the
chapter concerning security(Chapter 9). However it is shown here as once again it is a Planning
Web Front end component.
Once we have saved our task list, as per most planning objects, we then have to assign access to it.
351.
Click on the Assign Access
352.
Select Larry and Lucy, leave the default Assign selected, click Add
Page 88
353.
Add Manage Access to Sherlock and Stuart
354.
Add Manage and Assign access to Timothy
355.
Now log out of Planning, and log back on as Larry
356.
Go to View and select Basic mode
This can be set to be the default user view, and allows for the user to be led
very simply through the Planning process
357.
7.6.10 AD HOC BROWSING IN FORMS
One of the new features released in version is the ability to Ad Hoc browse and input data.
When designing the form, Enable for Ad Hoc, must be enabled on the Other options tab. The
icon of the form then appears like this:
To make use of the functionality, right click on the grid once you have opened
a relevant form for Data Input
358.
359.
Select Enter Ad-Hoc Mode
Page 89
Now right click and go to the Ad-hoc sub menu and experiment with
manipulating the form
360.
Page 90
CALCULATION MANAGER
8.1
CREATE BUSINESS RULE USING CALCULATION MANAGER WITH AGGREGATION

TEMPLATE
In this exercise you will learn how to create a new Business Rule from Calculation Manager, add
Run-time Prompts and link Business Rule to a Data Form.
In the previous lab when we had input our data, we had to go and run the default calculation to
ensure that data across the Entity dimension was totalled. We are now going to create a Calculation
script to calculate just the Entity dimension and to fix on just the relevant form dimensions. We will
then attach this to the Operating Expenses form.
361.
In Workspace, select Navigate > Administer > Calculation Manager
Click on the plus next to the Planning node, and navigate to the Halswrth
application
362.
Click on the plus next to the Fin database and right click on the Rules node
under Fin. Select New from the right click menu
363.
364.
Select the Begin icon
On the Properties tab fill in the name as CalcEntity, no other fields need to
be completed
365.
Select the Global Range tab. We are going to set the calculation so that it
focuses just on the area of the database that we need it to for our calculation
366.
Click in the field to the right of the Account label and then click on the
selection icon on the right hand side
367.
368.
Select the Variable option
Page 91
When the select variable form opens select Global from the category drop
down list, and then Create as we are going to create our own variables for this
exercise
369.
8.1.1.1 CREATING VARIABLES
The Variable Designer window / tab opens and we need to select the Global
node
370.
371.
Right click on Global and elect to create a new variable
372.
Fill in the parameters as above, and then save
While we are in this area, create variables for Entity, Scenario, Version and
Year as below
373.
Var_Entity Type: Member / Dimension Type: Entity / Default Value: Entity /

Deselect RTP
374.
Var_Scenario Type: Member / Dimension Type: Scenario / Default Value:

Budget / Deselect RTP
375.
Var_Version Type: Member / Dimension Type: Version / Default Value:

Final / Deselect RTP
376.
Var_Year Type: Member / Dimension Type: Year / Default Value: FY11 /

Deselect RTP
377.
Return to the CalcEntity tab and set the remaining ranges as per the screen
shot below:
378.
Page 92
Next, from the systems templates node, drag a SET Commands module
between Begin and End
379.
Make the following selections from the Set options by selecting the Edit
button on the right hand side of the screen and changing the options from the
relevant drop downs as per the screen shots below:
380.
SET UPDATECALC OFF (Calculate all data blocks) ;

SET AGGMISSG ON; (Consolidate Missing Values.)
SET CALCPARALLEL 2 ;
SET CLEARUPDATESTATUS OFF ;
SET CREATEBLOCKONEQ OFF ;
SET CREATENONMISSINGBLK OFF ;
SET EMPTYMEMBERSETS OFF ;
SET FRMLBOTTOMUP OFF ;
SET FRMLRTDYNAMIC OFF;
SET REMOTECALC OFF ;
SET CACHE HIGH;
Select Begin once again and then view the script tab. A text view of the script
will be available to view, and should look like this:
381.
Page 93
382.
Save the script
383.
Return to System View
384.
Right click on the script and validate it
385.
Right click on the calculation and Deploy it
Once the Rule has been deployed, as with all of our planning objects, we
must assign access to it
386.
387.
Go to Administration > Manage > Business Rule Security
388.
Select CalcEntity and then Assign Access
389.
Select All users and add
Page 94
Select the Launch radio button for all relevant users, and click Add. If you
have already assigned permissions, a Set button and not Add will appear as
above
390.
Verify in the summary that Launch access has been given to the users
required
391.
Next go to the Planning application window and elect to edit our version
form 6 of the operating expenses (Administration > Manage > Data Forms)
392.
393.
Select the Business rules tab and the CalcEntity should be available to select
394.
Select CalcEntity and then click on Properties
Select the Run on Save check box, and elect to Use the members on Data
Form
395.
396.
8.2
Save the form, click Finish and go and test that the form works
CREATE BUSINESS RULE USING CALCULATION MANAGER WITH AMOUNT UNIT RATE
TEMPLATE
Next we will use a different template to create a script.
Page 95
Go back to the Calculation Manager window and elect to add a new rule to
the Halswrth: Fin database
397.
We would normally set our global properties to focus in on just the data we
need to, however in this instance because our model is so small we will just move
straight onto the script itself
398.
399.
Make the following selections from the wizard:
400.
The script tab should appear as below:
401.
Once again save, validate and deploy the script
Go back into the Planning interface and Administration > Manage > Business
Rule Security
402.
403.
8.3
Assign launch access to users
CREATE BUSINESS RULE SEQUENCE IN CALCULATION MANAGER
Having calculated our Sales information at bottom level of Product and bottom level of Entity, we
now need to aggregate these two dimensions.
Page 96
404.
Firstly edit CalcEnt
405.
Save it as CalcEntProd
406.
Include Products in the sparse aggregation dimensions selection
407.
Save, validate and deploy
Now from the system view, navigate to the Halswrth application and select
RuleSets
408.
409.
Right click and select New
410.
Name the Ruleset SalesPriceAgg
411.
Navigate in the left hand pane down to Fin > Rules
412.
Drag Sales Price and CalcEntityProd onto the grid
413.
Save, validate and deploy
414.
Then go and edit the Volume and Price capture form
415.
Save it as 1 Volume and Price Capture Using Calc
Take the Version dimension from being a POV member and place it on the
Page member section
416.
417.
Edit the selection for Version to include 1st Pass and 2nd Pass
418.
Drag the Account selection onto the column area, and deselect Other Income
419.
Add Sequence from list of Business rules on the Business Rules tab
420.
Select Save and Finish
421.
Go and test the form by:

Entering Unit and Price data and verifying that Sales is calculated
Entering Price and Sales Data and verifying that Unit data is
calculated
Entering Sales and Unit data and verifying that Price is calculated.
Page 97
SECURITY AND ADMINISTRATION
9.1
SECTION OBJECTIVES

Add new users and groups, provision them with appropriate
role(s) and set up appropriate access to Forms and Data
Use Life Cycle Management
9.2
PLANNING SECURITY
In this exercise, you will add a new user, provision user as a Planner and set up appropriate Form
and Data access.
9.2.1
CREATE NEW USER
Before people can be allowed to input their budgets, we will need to give them access.
Security in Planning is comprehensive and makes use of:
Assigning access to the various objects for Planning such as
Planning web forms
Task lists
Calculations
Dimensions
Assigning ownership via the Planning Unit Hierarchy (this is not
technically security but will mandate that those who need to, see
the Plans
Page 98
Essbase filters.
However, before any Planning security can be applied we need to create our users in shared
services and Provision them to have access to Planning.
9.2.2
CREATE NEW USER
From in Workspace, click on the Navigate > Administer > Shared Services
Console, or open a new internet explorer window and open Oracle EPM Shared
Services from the list of shortcuts
422.
423.
Open up the User Directories > Native Directory > Users node as below:
424.
Click on File > New, or the New icon
Enter values as per the screen shot below, Password password and click
the Save button
425.
426.
Now create 4 additional users as below:
Page 99
Next we need to provision these users to have access to any of the Hyperion Products they are
likely to require. In this instance we are going to give them access to our Halswrth Planning
Application. We can do this individually or we could create a group which we provision, and then
just add these users to. Individual Provisioning will supersede any group provisioning. The
Provisioning process works in exactly the same fashion whether it is being applied to a group or an
individual
427.
Click on Groups, and File > New
428.
Create a Group as per the screen shot below:
Once we have named the Group and given a description (Description not
mandatory, but useful), click Next
429.
Note that tab 2 allows for Groups to be nested into groups should it be required
Page 100
430.
Click Next and this will take you to the User Members tab
431.
Add our users to the Group as per the screen shot
The Status Message window displays - Group 'Halswrth - UK' created. Click
OK button
432.
9.3
PROVISION GROUP (OR USER)

433.
On Shared Services Console, right-click on 'Halswrth - UK' group and select
Provision, or click on the Green man!
Page 101
After selecting Planner, click on the save button. Our users now have access
to the Halswrth Planning application
434.
From Shared Services Console menu bar, select File > Log Off. Shared Services
Log On window displays.
Log On as new user
435.
436.
Log On using Larry and password, and an error will display as below:
Log On again as admin and from the menu bar select Administration >
Application > Settings, and then change the setting for Enable Use of the
Application for: to All Users
437.
438.
Log Off and Log On as User Name Larry
Page 102
Notice that no Forms are available and that the Administration menu bar option is not available.
This is expected behaviour. There is No Access to Forms for Planners or Interactive Users unless the
Administrator specifically assigns access.
9.4
ADD FORM ACCESS
Log On as admin and from menu bar select Administration > Manage > Data
Forms and select 1 Volume and Price Capture form
439.
440.
Click on Assign Access button and then the Add Access button
Select Larry, the radio button next to Write and click the Add button.
Message will display - Adding of Users/Groups succeeded
Click the button
441.
442.
Log Off and Log On as with User Name Larry
Notice that now the 1 Volume and Price Capture form is available, but when you select it an error is
displayed. Again, this is expected behaviour. Planners can select only members to which they have
read or write access and can edit data forms only if they have access to at least one member of
each secured dimension.
9.5
ADD DATA ACCESS
Log On as admin and from menu bar select Administration > Manage >
Dimensions. Select Accounts dimension and Net Sales member, click Assign
Access button. Assign Access for Net Sales window displays, click the Add Access
button
443.
Select Larry, the radio button for Write and Descendants (inclusive) from the
dropdown box. Click the Add (or Set button if you had already assigned access
previously to someone) button, then Close button. On the Assign Access for Net
Sales window click Close button.
444.
Page 103
Now that you have the hang of this, we will Assign Access to all the
dimensions as per the screen shots below:
445.
Total Products shows Larry and Lucy with only read access.
446.
For Menswear we set Larry to have Write access and Lucy Read access
Page 104
For Womens Wear we set Lucy to have write access and Larry to have Read
access
447.
Note that setting Lucy and Larry to Read Access for Menswear and Womenswear respectively in
this instance is superfluous as they already have Read Access for these members, by virtue of the
fact that they are descendants of Total Products. Once viewed, remove Lucys entry from this
dialogue and Larrys from the Womenswear one. There is also no need to add write access for Bert
and Sherlock as their write access to descendants of Total Product still holds true.
Note: Assign Access is NOT available for Period and Year dimensions.
9.6
REFRESH SECURITY
Now Refresh Security Filters by going to Administration > Application >

Refresh Database. Select Security Filters and click Refresh
448.
Page 105
The filters are all created in the underlying Essbase database. Filters can be
viewed in the Essbase Administration Services Console if required
449.
From Planning Web Client, Log Off and Log On as Larry. Select the 1 Volume
and Price Capture form
450.
Notice that only Menswear (Level 0 members) are available to Larry for editing. All of the
Womenswear section is greyed out.
If you go to the 8 Matrix Approval Form, although the colours are as per the Validation Rules,
Larry will still not be able to enter data into the Womenswear cells.
Page 106
10 PLANNING UNIT HIERARCHIES (PUH)
10.1 SECTION OBJECTIVES

Add a new Planning Unit Hierarchy using a classic hierarchical
approval process
Use validations to improve the quality of the submission process.
The following exercises will take you through the Process Management interface. It will assist you
when defining the promotional path for plan submissions and data validations.
This first exercise will use a classic hierarchical approval process.
In the second exercise, you will extend the primary approval process by associating validation rules
that will require additional approvals outside of the normal hierarchical path.
The last exercise will apply conditional data thresholds that will prevent users from submitting their
budgets.
10.2 ASSIGN ACCESS TO USERS
Before we begin, we are going to set up some access for our Users. Go to
Administer > Manage > Dimensions
451.
Browse to the Entity Hierarchy and Assign write Access to UK and its
descendants for both Larry and Lucy
452.
Page 107
Next assign write access to Stuart for all descendants (inclusive) of

Organisation
453.
Page 108
10.3 CREATE PUH

454.
Now go to Administration > Process Management > Planning Unit Hierarchy
In this first step, you will define the granularity of the submission process, as well as the ownership
of the different planning unit that you will define.
Under the Process Management Dimension tab, click Create and add the
following details:
455.
456.
Give a name to the PUH : Entity Hierarchy
Select Custom from the Enable Process Management list and select
Organisation using the member selector icon
457.
458.
Select 3 levels of members using 02 into the relative generation numbers
box
0 corresponds to the selected member from where the approval process will
start 1 corresponds to its direct children, 2 to its grandchildren and so on
459.
460.
Elect to use a bottom up Process Management template
Using the Primary and Subhierarchy Selection tab, hit the Planning Unit icon
and expand Descendants
461.
462.
Next to the UK Member select Products from the Dimension drop down
Select T55 as the Parent Member (Note there is a bug which will not allow
selection using the Alias)
463.
Under Relative Generation, enter 1 (this means that only children of T55 will
be added) Experiment by putting 2 (Children and Grand children of T55) and
seeing how this would increase the selected members from 5 to 16
464.
Page 109
465.
Under Display, select All Entities
Browse to SFO and in the Parent member box select T65, and insert a 1 into
the Relative Generation box
466.
Next go to Sydney, choose Account as the dimension, and Total Gross Sales
as the Parent member. Insert 1,2 in the Relative Generation box
467.
468.
Click Next
469.
Expand the view by clicking on the double plus icon
470.
Under the Assign Owners tab:

For all Menswear product line combinations, set Larry Lurcher as
the owner. Larry is the Mens Product Manager
For all Womenswear product line combinations set Lucy as the
owner. Lucy is the Womens Product Manager
For All UK Countries set Stuart Greenback as the owner. Stuart is
a Senior exec responsible for all Product operationally
For SFO set Timothy as the owner. This is a special project he is
involved with
For Sydney we are only interested in unit sales across all product
not by Department, again we assign this to Timothy
Lastly Assign reviewers as per the screen shots
Page 110
Next click on the icon to review the promotional path of Ldn:T55

a visual map of the promotional path will be presented
and
471.
472.
Click on Save and Finish
Next, from the Planning Unit Hierarchy screen, select the Scenario and
Version assignment
473.
Page 111
474.
Click on the
icon next to the newly created Entity Hierarchy
475.
Select Budget and 1st Pass version and click OK
476.
Click Save
477.
Select Tools Menu > Manage Process
478.
Display in Tree view mode, select Organisation and Start the Plan Cycle
479.
Select Budget and 1st Pass and hit Go
Click on the Promotional Path icon to verify the Path, in the same fashion as if
we were in the PUH editor screens
480.
Next log out of Workspace, and log on as Larry. Once logged on, open the
Volume and Price Capture form for data entry, and verify that Larry has access to
menswear and not Womenswear
481.
10.4 CREATE MATRIX APPROVAL

482.
Create a new form called 8 Matrix Approval
Go to Administration > Manage > Data Forms, select BootCampForms folder

and click create
483.
484.
Select the layout tab and make the selections as per the screen shot below:
Page 112
485.
Select Cell A,1 and click on the green plus to create a new validation rule
486.
Complete the rule as per the screenshot below:
487.
Process the cell by electing to Update Promotional Path
488.
The Process cell criteria appear below:
If you now go and Manage the workflow process, you will see that the
promotional path for Menswear units under London has changed and now
requires that Sherlock signs them off
489.
Page 113
Open the form 8 Matrix Approval for Data Input and it should appear as
below:
490.
491.
Now log into Planning as Larry
492.
Go to Tools > Manage Process
Page 114
493.
Select Budget and First Pass and then Go
If you Select Mine, then all plans under review by that user will be
selected...Dont select this in this instance
494.
495.
Select the Check box adjacent to Ldn: T55
If you click on the link for Details this will allow for comments to be
assigned to the whole form
496.
497.
Click Change Status
Please note that all selected nodes will have their status changed if you have selected more than
one.
Elect to promote the Plan, and you will notice that it only allows automatic
promotion
498.
499.
Once submitted your summary should look like this:
If you attempt to go and input data into the Data forms as Larry, you will see
that these are now all greyed out
500.
Page 115
Now log out as Larry and Log in as Stuart and repeat the process, your
summary should look as below:
501.
Providing that permissions have been correctly set you will be able to do this
repeatedly for the complete Promotional Path for each planning node.
Page 116
11 LIFE CYCLE MANAGEMENT

11.1 LIFE CYCLE MANAGEMENT
In this exercise you will gain experience using Shared Services, exploring Planning application
artefacts and migrating artefacts.
11.1.1 LOG ON TO SHARED SERVICES
Select ORACLE EPM Shared Services from Internet Explorer Favourites

(http://demodrive:28080/interop/index.jsp) and Log On as User Name: admin
502.
11.1.2 REVIEW PLANNING ARTEFACTS
Navigate to Application Groups > Default Application Group > Halswrth. You
will be presented with a list of Artefacts for our application
503.
Expand categories such as Data, Global Artefacts and Plan Type to explore
level of detail available for Planning application artefacts
504.
505.
Click Select All button and then the Define Migration button
506.
Click on the Select All button, and all the artefacts will be selected
Page 117
507.
Next select the Define Migration button
508.
Next a summary of the destination is provided
Next we are given the choice of destination and whether to create a file of all
the exports, or to put it into an existing application
509.
Page 118
We then have the option of Executing or Saving the Migration definition,

elect to launch it and the following dialogue comes up:
510.
511.
Expand File System, enter Halswrth and click the Next button
The default destination on the Shared Services computer is

D:\Oracle\Middleware\user_projects\epmsystem1\import_export\admin@Nativ
e Directory\Halswrth
512.
Page 119
Confirm status of Success, select View Details and click on Cancel button
several times
513.
From Explore, navigate to:

D:\Oracle\Middleware\user_projects\epmsystem1\import_export\admin@Nativ
e Directory\Halswrth\resource\Relational Data, select Cell Texts.xml
514.
Right-click and Open With > Notepad. You will see the Cell Text that we
entered in previous exercise as part of this Boot Camp
515.
Please note that if we want to restore from this file export to an application it is necessary to save
a copy of the Migration definition file. This xml file and the resultant folder which is created
during execution will need to be copied to the target system and opened in the target system
shared services. The target application must pre-exist, and have identical year, time and currency
dimensionality to the application being restored from the LCM files.
Page 120

Hyperion Planning 11.1.2 Implementation Boot Camp Laboratory Manual V1

Загружено:

Сведения о документе

Исходное описание:

Авторское право

Доступные форматы

Поделиться этим документом

Поделиться или встроить документ

Параметры публикации

Этот документ был вам полезен?

Это неприемлемый материал?

Авторское право:

Доступные форматы

Hyperion Planning 11.1.2 Implementation Boot Camp Laboratory Manual V1

Загружено:

Авторское право:

Доступные форматы

HYPERION PLANNING IMPLEMENTATION BOOTCAMP

ENVIRONMENT SETUP LAB INITIATION................................................................ 4

ESSBASE MODELLING .............................................................................................. 8

SECTION OBJECTIVES ....................................................................................................................... 8

ESSBASE DIMENSION AND DATA LOADING .......................................................... 23

CLASSIC PLANNING APPLICATION DEVELOPMENT ............................................... 38

SECTION OBJECTIVES .................................................................................................................... 38

OUTLINE LOAD UTILITY ......................................................................................... 59

BUILD DIMENSIONS FROM FLAT FILES ............................................................................................... 23

USING THE OUTLINE LOAD UTILITY WITH CLASSIC PLANNING................................................................ 59

DATA FORM DESIGN.............................................................................................. 65

Qubix International Limited Hyperion Planning Bootcamp

CALCULATION MANAGER ..................................................................................... 91

SECURITY AND ADMINISTRATION ......................................................................... 98

10 PLANNING UNIT HIERARCHIES (PUH).................................................................. 107

SECTION OBJECTIVES ............................................................................................................... 107

11 LIFE CYCLE MANAGEMENT .................................................................................. 117

Qubix International Limited Hyperion Planning Bootcamp

ENVIRONMENT SETUP LAB INITIATION

In this section, you:

COPY EXERCISE FILES

Qubix International Limited Hyperion Planning Bootcamp

LAUNCH THE ESSBASE SERVICES

This will require that we start:

ORDER FOR STARTING:

Hyperion Foundation Services Managed Server

Qubix International Limited Hyperion Planning Bootcamp

Oracle Process Manager (EPM_epmsystem1)

Oracle Process Manager (ohsinstance.)

Hyperion RMI Registry

Hyperion Provider Services

Hyperion Administration Services Web Application.

BUILDING AN ESSBASE APPLICATION

Qubix International Limited Hyperion Planning Bootcamp

Qubix International Limited Hyperion Planning Bootcamp

At the end of this section, you will be able to:

CREATE NEW ESSBASE APPLICATION AND DATABASE

From the Windows Start

Qubix International Limited Hyperion Planning Bootcamp

Under Username, type admin

Expand Essbase Servers so that Demodrive appears

The following dialogue appears:

Under Application name, type Shops and click OK.

Expand the Demodrive node so that Applications appears in next level.

Qubix International Limited Hyperion Planning Bootcamp

Expand Applications node so that Shops appears in next level.

Right-click on Shops and select Create database

The Create Database dialog box displays:

Under Database name: type Fin and click OK.

Expand Shops node so that Fin appears in next level.

Expand Fin node so that Outline appears in next level.

Right-click on Outline and select Edit.

Select the Maximize button to display Outline Editor in a larger view.

Qubix International Limited Hyperion Planning Bootcamp

Press Enter to close the input box

Select Periods and click on button to Add a child to selected member

Qubix International Limited Hyperion Planning Bootcamp

Qubix International Limited Hyperion Planning Bootcamp

Select Time dimension, right-click and select Dynamic time series

Enable Y-T-D as Gen1 and Q-T-D as Gen2 and click OK

Qubix International Limited Hyperion Planning Bootcamp

Expand the Scenario dimension and with mbrName1 highlighted, double-click on

Qubix International Limited Hyperion Planning Bootcamp