Essbase Lab Guide-I For
Essbase Lab Guide-I For
For
Prepared By
Sushuma P
Change Record
Reviewers
MODULE 2.................................................................................................................................16
BUILDING LOAD RULES.......................................................................................................16
EXERCISE - LOADING THE FAMILY TOTAL HIERARCHY............................................................................16
EXERCISE - (OPTIONAL) USING THE LEVEL BUILD METHOD....................................................................16
EXERCISE - CREATING A PARENT-CHILD LOAD RULE..............................................................................17
EXERCISE - LOADING DIMENSIONS USING A PARENT-CHILD RULE..........................................................17
EXERCISE - (OPTIONAL) CLOROX MINTY..................................................................................................17
EXERCISE - LOADING A CHANNELS HIERARCHY TO CUSTOMER...............................................................18
EXERCISE - CREATING A REGION TOTAL ATTRIBUTE DIMENSION............................................................18
EXERCISE - (OPTIONAL) BUILDING THE CAPACITY TOTAL ATTRIBUTE....................................................19
MODULE 3.................................................................................................................................20
SPREADSHEET REPORTING................................................................................................20
EXERCISE - INSTALLING THE ADD-IN AND TOOLBAR................................................................................20
EXERCISE - MANAGING CONNECTIONS......................................................................................................23
EXERCISE - ANALYZING DATA..................................................................................................................24
EXERCISE - CHALLENGE 1.........................................................................................................................26
EXERCISE - CONTROLLING EXPANSION.....................................................................................................26
EXERCISE - TROUBLESHOOTING REPORTS.................................................................................................27
EXERCISE - MANAGING DISPLAY OPTIONS...............................................................................................28
EXERCISE - SELECTING MEMBERS FROM THE OUTLINE............................................................................29
EXERCISE - DESIGNING QUERIES...............................................................................................................30
EXERCISE - (OPTIONAL) REPLICATING REPORTS WITH CASCADE.............................................................31
EXERCISE - SPREADSHEET FORMULAS.......................................................................................................34
MODULE 4.................................................................................................................................37
CREATING BASIC CALCULATIONS...................................................................................37
Exercise - Examining the Anatomy of a Rollup.......................................................................................37
Exercise - Adding a Back Calculation.....................................................................................................41
SOLUTIONS.............................................................................................................................120
DESIGININGOUTLINES
Exercise - Creating a Database
You have decided to analyze your sales data in Essbase, and the first step is to build an
application and database shell. In this exercise, you create the Bigcorp application and Sales
database.
1) On the Administration Console, select File > New > Block Storage Application.
2) Click OK.
The Create Application dialog box opens.
3) Verify that localhost is selected in the Analytic Server drop-down list box.
5) Click OK.
The Bigcorp application is displayed under the Applications node on the Enterprise View
tab.
8) Verify that localhost is selected in the Analytic Server drop-down list box.
In this exercise, you build the Time dimension and add dimension members. This exercise
assumes that you are working in the Outline Editor.
To open the Outline Editor for the Sales database, expand the Sales database node in the
Enterprise View tree and then double-click the Outline icon.
4) Press Enter.
5) Press Esc.
9) Press Enter .
10) Create additional sibling members for Quarter 1 named Quarter 2, Quarter 3, and
Quarter 4.
11) Create child members, Jan through Dec, to populate the months in each quarter.
3) Add similar aliases for the remaining quarters. Add aliases to the months where Jan's
alias is January,
Feb.’s alias is February, and so on.
3) Click OK.
4) Highlight Year Tot and select Outline > Dynamic time series.
6) In the Gen drop-down list box, select 1 (representing the generation where the Y-T-D
accumulation should occur).
9) Click OK .
Create a Scenario dimension for the Sales database. Add the following children to Scenario:
Current Year
Prior Year
Forecast
Bud get
Scenario Variances
Use this table to create children for the Scenario Variances members:
Set the Consolidation property for the children of Scenario and the children of Scenario
Variances to (~) Ignore .
Set the Data Storage property for the Scenario dimension member and the Scenario
Variances member to Label Only.
Create an Accounts dimension for the Sales database. Open Corpacct.xls, and select the
Gross Margin Analysis worksheet. Convert from spreadsheet analysis format to Essbase
outline Structure. Use this worksheet as a guide for member names and member
relationships.
Use this worksheet as a guide for member formulas and consolidation operators.
In this exercise, you add time balance accounting and expense reporting features to the
Accounts dimension. This exercise assumes that you are working with the Sales outline.
5) Right-click and select Edit member properties and then select the Formula tab.
8) Double-click the @VAR math function. The function is displayed in the Formula
Editor window.
12) Complete the comparable formulas for the Act Vs Fcst and Bud Vs Fcst.
15) Under Account information, set the Variance reporting expense property to true.
17) Select File > Save to verify and save the Sales outline.
In this exercise, you create a load rule to build the Family Total hierarchy. To complete this
exercise:
Create a new load rule.
Associate the load rule with the Sales outline.
Read the FamGen.xls data file (located in the \BCI\LoadRule directory) into
the blank load rule.
Set the load rule to Dimension build fields view mode.
Specify the data file delimiter type.
Ignore any header records.
Set the correct dimension build method.
Associate field headers with dimension and generation references.
Verify and save the rule.
Update the outline using the rule.
Rebuild the Family Total hierarchy using the level load rule:
Delete the product structures from the previous Family Total loading exercise.
Load the FamLev.xls file using the Fam_Lev.rul.
Create a parent-child load rule for the Product dimension of the Sales outline.
Use the Configpc.xls data file (located in the BCI \LoadRule directory).
Associate the columns with field properties.
Ignore any header records.
Save the load rule as Par_C h.
Use the parent-child load rule you constructed to load the Configuration Total and Line
Total product hierarchies. To complete this exercise:
Based on what you have learned in this chapter, create a new load rule to load
Minty.txt into the Mint dimension in the Sales database. To complete this exercise:
When the data is loaded, the dimension should look similar to the following sample
Create a load rule that adds Channel information under the Customer dimension in
the Sales database. To complete this exercise:
Create a load rule to define a Region Tota l attribute dimension. To complete this
exercise:
Create a text attribute dimension in the Sales outline called Region Total
with the following children: Mid West , South , East , and West .
Select Customer as the base dimension for Region Total.
Create a load rule, using CusReg.xls (located in the
BCI\LoadRule directory) as your sample data file.
Specify a build method.
Edit data file fields where necessary.
Ignore headers if necessary.
Reject records if necessary.
Define field properties.
Save the load rule.
Load CusReg.xls into the Sales database.
Create a new load rule to build a Capacity Total attribute dimension in the Sales
outline. To complete this exercise:
In this exercise, you examine several data files with different structures and create load
rules to load them into the Sales database. The sample data files are called Budget.txt ,
PriorYr.txt , and Forecast.txt . For each load rule:
1) Create a new load rule, using one of the files listed above as the sample data file.
2) Examine the data file and identify any problems in the data.
5) If possible, use dynamic headings. Otherwise, ignore header records and specify field
Properties manually.
7) Use your load rule to load the data file into the Sales database.
8) After all data is loaded; calculate Sales with the CalcAll calculation script (located in
BCI\Load Rule).
MODULE 3
Spreadsheet reporting
You have been asked to configure the Essbase Spreadsheet Add-in several different
ways for different users. In this exercise, you enable and disable the add-in, and you
install the Essbase toolbar.
If you have not fully completed the exercises in modules 1 and 2, you may want to reset
25936855.doc Confidential Page 20 of 14820
© Adaequare, Inc
your database to rebuild the outline and reload the data.
2) Double-click the ssheet.bat file. The automatic reset script runs and outputs
messages in a command window. Wait until its completion.
Testing Default Behavior
When you install Essbase, let your users know the default behavior, as the add-in
circumvents some normal Excel functionality.
Open the SSReports.xls file and go through the following steps on the Sandbox
worksheet. Ask yourself the following questions: What happened? How is this different
from Excel without the add-in? How would your users react if this were a worksheet of
non-Essbase data?
As you can probably tell from those tests, the mouse buttons behave differently when
the add-in is installed. Since most users do not need Essbase functionality all of the
time, you can give them different options for enabling it.
3) Click OK .
4) Clear the Sandbox worksheet and repeat some of the previous default behavior
tests. How are the results different?
The Essbase menu is no longer displayed on the Excel menu bar. Now Excel behaves
as usual, but users have no ability to connect to Essbase until they reverse the preceding
steps.
1) If necessary, select Tools > Add-Ins menu and enable the add-in in Excel.
4) Clear the check boxes for the Enable Secondary Button and Enable Double-
Clicking options and then click OK .
5) Clear the Sandbox worksheet and repeat some of the default behavior tests from
above. How are the results different?
The mouse now retains normal Excel behavior. Moreover, since the Essbase
Spreadsheet Add-in is still enabled, these users retain the ability to explore and analyze
their data through Essbase menu commands or by using the Essbase toolbar.
5) In a new Excel workbook, test the mouse button behavior for double-clicking and
right-clicking.
6) Select Essbase > Connect , enter your login information, and then click OK .
7) Now that the worksheet is connected to Essbase, test the mouse button behavior
again.
8) Select Sheet2 in the workbook and test the mouse button behavior.
With this option selected, you should see Essbase mouse functionality on worksheets
that you have explicitly connected to Essbase, and Excel mouse functionality on
nonconnected worksheets.
The Essbase toolbar is not installed automatically; macros install it when you open the
Esstoolb.xls file (located in Essbase\Client\Sample).
3) Repeat step 1 and then check Hyperion Essbase to display the toolbar again
You have a workbook with multiple sheets, requiring various database connections. In this
exercise, you enable and disable connections, and you view your open connections in the
Disconnect dialog box.
Connecting to Essbase
1) On Sheet1 of a new Excel workbook, select Essbase > Connect.
2) Select or type the correct server name, enter your username and password, and click
Update.
6) Select Sheet3, select Essbase > Connect, and then connect to Sample: Basic.
8) Click Close.
3) Click Close.
4) Close the Excel workbook (do not save the changes) and open a new one.
6) Click Disconnect to close the selected connection, and then repeat until all connections
are closed.
7) Click Close.
In this exercise, you use basic retrieve operations to navigate from a top-level retrieval to a
more refined data set. This exercise assumes that the SSReports.xls file is open. Before you
begin, establish a connection to Bigcorp:Sales on the Sandbox worksheet, and ensure that
your options are set so that Essbase mouse actions are enabled.
Basic Zooming
There are many ways to control zoom behavior in the Essbase Spreadsheet Add-in:
Action Options
Zoom in Essbase > Zoom In
Double-click member name
Zoom In toolbar button
Starting with a basic, top-level retrieval, try the following steps and note what happens:
Other basic Retrieve Operations: In addition to Zoom , there are four basic operations
that can help analysis:
Action Options
Flashback Essbase>flashblack
Flashblack toolbar button.
If necessary, clear the spreadsheet to start again with a basic, top-level retrieval. Try the
following steps and note what happens:
Exercise - Challenge 1
Starting from a basic top-level retrieve, use the skills you have learned up
to this point to duplicate this report. Use SSReports.xls worksheet
Challenge1.
4) Zoom in on Accounts .
5) Zoom in on Scenario .
6) Zoom in on Product .
You receive an error message that the maximum number of rows in Excel has been
exceeded.
It is very easy, even in a small database, to exceed the maximum number of rows in
Excel when you use the deeper zoom options, so they should be used sparingly. Choose
other Zoom In settings from Essbase > Options > Zoom and then repeat the preceding
steps, noting any differences in the behavior.
In this report, your products are grouped by customer. IBM has the highest sales in the
OEM Channel, and you want to see their sales details for the LIGHTBOLT
performance products, which are the company’s best-sellers. Because retrievals take
more time the more real estate you are using in Excel, focus your zooms as tightly as
possible.
2) Select Essbase > Flashback to return the report to its original state.
3) On the Zoom tab, select Within Selected Group ( Essbase > Options ).
4) Zoom in on Family Total for IBM again. How is this different from your results
for step 1?
Even though you are interested only in LIGHTBOLT data, this option still leaves other
8) Zoom in on Family Total for IBM, and continue to zoom in to find the
LIGHTBOLT products again. How does this option differ from the previous one?
Errors in reports are commonly caused by incorrect labels or label placement. The
Troubleshooting.xls file contains a series of tabs that may or may not have retrieval
problems. For each tab, diagnose and correct the issue.
Labels 1
Labels 2
Labels 3
Labels 4
Labels 5
Labels 6
Labels 7
Labels 8
Essbase gives you many different options for displaying your reports. In this exercise,
you take a prebuilt report and change the display options so it matches the finished
result.
On the Managing Options tab in the SSReports.xls file, make the necessary changes to
display the report as shown in the following sample:
Display aliases.
Display member names and aliases for rows.
Display styles.
Suppress #Missing rows.
Display no indentation.
Select Apr for the latest time period in Dynamic Time Series.
Even with their most focused settings, the basic zoom options can return more
information than is necessary for more selective reporting. In this exercise, you are
asked to create a report for the Config A LIGHTBOLT and MAVRIDER products
only. Since this product list does not exist as part of the natural outline hierarchy,
you use the advanced selection options in the member selection tool to build it.
On the Member Selection tab in the SSReports.xls file, build the report to the following
specifications:
You have been asked by the Channels organization to modify the previous report to
include a list of all level 0 products grouped by the customers in the OEM channel. In
addition, they want to see the products sorted within each group in descending order
based on the YTD totals, and they want to filter out rows with no YTD totals.
Because this report requires nested dimensions in the rows and server-based sorting,
Essbase Query Designer is the best tool for the job.
On the Member Selection tab in the SSReports.xls file, build the report to the following
specifications:
Many organizations need to regularly create many similar reports based on a standard
template. Rather than replicating these reports manually, Essbase can do it
automatically with the Cascade option. In this exercise, you create reports for
distribution using the Cascade option. This exercise assumes that the SSReports.xls file
is open.
2) Select OEM .
4) On the Cascade Information tab, ensure that the member is set to cascade on
OEM, Next level .
12) Click OK .
The OEMRpt.xls file is generated.
4) Select OEM0Cust.lst .
You may have to select All Files from the Files of Type drop-down list box to see this
file in the directory.
5) Click Open .
3) Click No
To Retain on Zooms
1) Zoom in on PERFORMANCE .
6) Zoom in on PERFORMANCE .
The formula is preserved for Performance, but its children now have no formula.
In this exercise, you create a new calculation script that calculates each dimension in
the Sales database one by one. This exercise assumes that the database was cleared of
all data and that Actual.txt and Forecast.txt were loaded with Loadcorp.rul.
2) Select File > New > Scripts > Calculation script and click OK .
4) On the Categorical tab, expand the Functional category and double-click SET
UPDATECALC .
This commands turns off Intelligent Calculation functionality for this calculation script.
5) In the Calculation Script Editor, modify SET UPDATECALC to OFF; (be sure
to include the semicolon).
3) In the Dimensions list, right-click Accounts and select Insert member name .
dimlist is
replaced by the
Accounts
6) Click OK .
11) Select Essbase > Retrieve and analyze the result. The upper-level Accounts
dimension members now contain data.
4) Open Anatomy.xls .
4) Open Anatomy.xls .
8) Select Essbase > Retrieve and analyze the result. Data is displayed for Accounts
and Year Tot for upper-level blocks across the Customer dimension. New upper-level
Customer blocks are created.
4) Open Anatomy.xls .
Although you have rolled up all dimensions in the outline, some data is not aggregating
correctly. In this exercise, you modify the CalcCorp.csc file to correct rates that are
aggregating incorrectly.
2) After the CALC DIM statement, add a block of formulas to derive the correct rates
for the following accounts:
List Price , Discount % , Labor/Unit , Matl/Unit , Overhead Rate , Gross
Margin % .
Enclose the group of formulas in parentheses to prevent jump-ahead behavior from the
CALC DIM statement.
Current Year
January, February, and March
/* Housekeeping */
SET UPDATECALC OFF;
1) Open Anatomy.xls .
Extra Credit
The 10% accelerator for Units creates partial units in some months. Modify your script
so that units are rounded to the nearest whole number.
Mix calculations are typically a percent-to-total type of ratio calculation that takes a
data value at an given level and figures what percentage it is of a related total. You
have been asked to create several mix calculations in the Sales outline.
1) Examine the formulas on the Mix Calculation Required tab in the SSReports.xls
2) In the Sales outline, add a formula to Unit Mix that calculates the current product’s
units divided by the units for its generation 3 ancestor.
3) Add a formula to Sales $ Mix that calculates the current product’s Net Sales divided
by the Net Sales for its generation 3 ancestor.
5) Save the outline and check your results on the ANCESTVAL It tab in the
SSReports.xls file.
Write a calculation for the Moving Average account that takes a three-month moving
average (the current month plus the previous two months) of unit sales. The calculation
should span Prio r Year and Current Year .
For the first two months in Prior Year, use the units sold for Moving Average.
Extra Credit
Write your calculation script so that #Missing data is not counted.
Many calculation scripts contain values or member names that are variable and must
therefore be updated regularly. To make maintenance easier, create server-based
substitution variables. This gives you one place to update multiple calculation scripts.
6) Press Enter .
8) Click Close .
In this exercise, you create a new application and database named Dynamic and use
the information in the Aggressive.xls workbook such that a back calculation is not
necessary to produce correct values.
The values in the No Dynamic spreadsheet represent a retrieve from the Bigcorp
database with no dynamic calculations. These values are correct.
2) Create a new application called Dynamic with a new database called Dynamic .
3) Open the dynamic.otl file from the BCI\CalcIt\Dynamic directory and save it to the
Dynamic database (overwrite the existing outline file).
4) Load Actual.txt and Forecast.txt using Loadcorp.rul (those files are also in the
BCI\CalcIt\Dynamic directory).
7) In the comparison spreadsheet, create a formula that subtracts the two spreadsheets
and copy it to all data cells. Investigate all nonzero values.
8) Return to the Dynamic database and make any changes required to correct the
calculation until the Comparison worksheet in the Agressive.xls workbook indicates
that the No Dynamic and Dynamic spreadsheets are in sync.
9) When you are satisfied that the spreadsheets are in sync, return to the database and
make a note of the current block statistics.
MODULE 5
Copying data from one scenario to another is often a handy way to quickly populate a
scenario with useful data that you can then manipulate as necessary. In the first part of
this exercise, you create a budget by copying prior year Actual data into the Budget
scenario and then modifying it. In the second part, you populate a Rolling Forecast
scenario with a combination of Current Year (Actuals) and Budget data.
4) Populate all current and future months for Rolling Forecast with Bud get data
As the result of a data load, you realize erroneous data was loaded into Lightbolt 540
Clear data from Lightbolt 540 S and its ancestors for the Current Year
Extra Credit
Modify this script so that the Customer Count stores a 1 for every occurrence of a
product sale. To see all customers for a given product, you must look at the Customer
level.
7) Allocate Other CGS expenses to level 0 using variable allocation ratios. Focus
calculations using FIX to level 0 members for Customers and Products.
2) Run CalcAll.csc .
3) After the consolidation is complete, lock and send the data on the Allocations Input
worksheet.
5) Write a new script to push Labor Variances down to the next level of Family
Total based on an even split between the children with data.
6) For Overhead Variances , combine steps 3 and 4. Use the straightline allocation
method to push Overhead Variances to the next level of Family Total. At the next
generation of Family Total, Overhead Variances should be allocated based on a ratio
of individual unit sales for each customer and product over all units sold.
Extra Credit
Write a stepped allocation to push Obsolete Charges down to level 0 of Product so
that each level is based on an even split between the children with data.
Exercise solution
Module 1
5) Select Scenario .
13) Add these children to Act Vs Bud: Current Year and Budget .
14) For both children of Act Vs Bud, open the Member Properties dialog box and set
the storage type to Shared Member .
8) Position the cursor and the end of the formula and type a
semicolon ( ; ).
3) Change the Consolidation property of the Current Year member to (~) Ignore .
4) Click OK .
5) Change the Consolidation property to (~) Ignore for the following members:
Prior Year , Budget , Forecast , Scenario Variances , Act Vs Bud , Act Vs Fcst ,
and Bud Vs Fcst .
Label Only is used for outline members that are a label and whose value has no
meaning to the data. When marked Label Only, the member is not included in the
data block structure of the database.
4) Click OK .
In this exercise, you create the Accounts dimension for the Sales database. This
exercise assumes that you have the Sales outline open.
5) Right-click and select Edit member properties .The Member Properties dialog box
is displayed.
6) Change the Consolidation property of the List Price member to (*) Multiplication .
7) Click OK .
10) Compare the formulas and entries for computing Gross Sales in Excel to the
Accounts model.
4) Right-click and select Edit member properties . The Member Properties dialog
box is displayed.
6) Click Next .
The Member Discount % is active.
8) Click OK .
Since Gross Sales and Discounts calculate Net Sales, they are children of Net Sales.
10) Move Gross Sales and Discounts from their position as siblings of Net Sales to
children of Net Sales.
11) Change the Consolidation property of the Discounts member to (-) Subtraction .
2) Create siblings of Net Sales : Direct Labor, Material, Overhead, Cost Of Sales,
Material Variances, Labor Variances, Overhead Variances, Obsolete Charges,
Inventory Adjustments, Other CGS, Gross Margin, Gross Margin % .
5) Move Net Sales, Cost of Sales and Other CGS to children of Gross Margin .
11) Use this table to change the properties for the members in the Accounts dimension:
In this exercise, you create a load rule and associate the rule with the Sales outline. You
open the source file to be loaded and make the appropriate settings to match the
2) Make sure that the outline is set to the Bigcorp application and the Sales database,
and then click OK .
2) On the File System tab, select Excel sheets (*.xls) in the Files of type list.
To see the file, you need to set the file type to XLS or All files.
Load Rules can dynamically build dimensions or load data into a database. The
different modes enable you to define the settings for each of these activities.
4) Click OK .
3) Select Rules File and, next to Dimensions , click Click here to edit .
4) Enter Product .
5) Press Enter .
Product is displayed in the Rules file Dimensions list.
10) Click OK .
The Dimension Build Settings dialog box is displayed.
11) Click OK .
5) Click OK .
You return to the Data Prep Editor.
4) In the Field type section, double-click Generation , for the generation Number,
enter 2 .
5) Click Next .
Field Number: 2 is displayed above the Field Definition area.
6) For Field 2, select Product for the Dimension, Property for the Field Type, and
2 for the Number. The property for the preceding generation 2 member is set.
7) Click Next .
Field 3 is displayed.
8) Continue the process for the subsequent fields using the information in the following
table:
9) Click OK .
You return to the Data Prep Editor.
4) Click OK .
You return to the Data Prep Editor.
3) When you receive the message, “The rules file is correct for
dimension building,” click OK .
2) Click Find Data File and select the FamGen.xls file located in the BCI\LoadRule
directory.
4) On the Analytic Server tab, select the Fam_Gen.rul file from the list.
5) Note the location of the dimbuild.err file directory. Review this file if errors occur
during the loading process.
6) Click OK .
If the load fails, open the error file and make corrections, and then try again
Module 2
In this exercise, you review the level rule structure and redo the Family Total Rollup
using the level load rule. This exercise assumes that you have the Essbase
Administration Services Console open and the Bigcorp application and Sales database
selected.
6) On the File System tab, select Excel sheets (*.xls) in the Files of type list.
4) Click Ye s .
Family Total and all its children are deleted from the outline.
2) Click Find Data File and select the FamLev.xls file located in the
BCI\LoadRule directory.
4) On the File System tab, select the Fam_Lev.rul file from the
BCI\LoadRule directory.
5) Note the location of the dimbuild.err file directory. Review this file if errors
occur during the loading process.
In this exercise, you create a new dimension build load rule and set the rule to use the
Parent-Child method.This exercise assumes that you have the Administration Console
open and the Bigcorp application with the Sales database selected in the Enterprise
View.
2) Select Options > Associate outline to associate the rule with the Sales outline.
6) Select Options > Dimension build settings and then select the Dimension Build
Settings tab.
9) Click OK .
You return to the Data Prep Editor.
5) Click OK .
The Field Properties dialog box closes and you return to the Data Prep Editor.
Rather than clicking OK at this point, you could also click Next to move through the
columns of the file while making the assignments as directed. Then, you would select
OK only when all columns had been assigned values.
6) Select any member in column two and then repeat steps 1 to 5 with the following
changes:
• In the Field Type list, choose Property .
•Enter 0 for Number.
• In the Dimension list, select Product .
7) Select any member in column three and then repeat steps 1 to 5 with the following
changes:
• In the Field Type list, choose Child .
•Enter 0 (zero) for Number.
• In the Dimension list, select Product .
8) Click OK .
Ignoring the First Header Row
1) Select Options > Data source properties and select the Header tab.
3) Click OK .
3) When you receive the message, “The rules file is correct for dimension building,”
click OK .
Use the Parent-Child load rule just constructed to load the Configuration Total and Line
Total hierarchies to the Product dimension in the Sales outline.This exercise assumes
that you have the Sales outline open.
2) Click Find Data File and select the ConfigPC.xls file located in the
BCI\LoadRule directory.
4) On the Analytic Server tab, select the Par_Ch.rul file from the list.
5) Note the location of the dimbuild.err file directory. Review this file if errors occur
during the loading process.
6) Click OK .
If the load fails, open the error file, make corrections, and then try again.
2) Click Find Data File and select the LinePC.xls file located in the BCI\LoadRule
directory.
4) On the Analytic Server tab, select the Par_Ch.rul file from the list.
5) Note the location of the dimbuild.err file directory. Review this file if errors occur
during the loading process.
6) Click OK .
In this exercise, you create a new dimension, Mint. Then you create
a new load rule to load the data. This exercise assumes that you
have the Sales outline open.
2) Select Options > Associate outline and associate the rule with the
Sales database.
3) Select File > Open data file and double-click Minty.txt (located on
the File System tab in the LoadRule directory).
2) Click OK .
Field 1 is duplicated.
4) Select Field 4 and then select Field > Create using join .
5) Click OK .
Two copies of this field now exist.
Moving Members
1) Select Field 4 and then select Field > Move .
3) Click OK .
3) Repeat steps 1 and 2, inserting a blank space between the current Field 5 and Field
6 and between Field 6 and Field 7 .
There are total of nine fields with just a single space in fields 3, 6, and 8.
2) Click OK .
The three fields are joined into a single Field 2 with correct spacing between the words.
4) Click OK .
6) Click Next .
8) Click OK .
2) Select Options > Associate outline and associate the load rule with
the Sales database.
5) Select View > Dimension Build Fields to set the mode for loading
members to the outline.
Creating the Customer Dimension
1) Select Options > Dimension build settings .
5) Type Customer .
6) Press Enter .
11) Click OK .
The Dimension Properties dialog box closes.
12) Click OK
The Dimension Build Settings dialog box closes and you return to the Data Prep Editor.
13) Select Options > Dimension build settings and then select the
Dimension Build Settings tab.
14) In the Dimension list, double-click Customer and confirm that the Build Method
is set to Use Generation References .
15) Click OK .
You return to the Data Prep Editor
4) Click OK .
You return to the Data Prep Editor.
Organizing Columns and Associating Them with Generations
1) Select a member of Field 1 and then select Field > Properties .
4) Click OK .
The information in Field 1 changes to gray; if it does not, check your settings.
7) Click OK .
The field title Channel is displayed as Field 2 between the Cust Class and Customer
fields.
8) Select the new Field 2 and then select Field > Create Using Text .
10)Click OK .
11) Select the new Field 3 and then select Field > Create Using Text .
13) Click OK .
15) On the Dimension Build Proper ties tab, perform the following tasks:
• For Dimension, double-click Customer .
• For Field Type, select Generation .
• For generation number, enter 2 .
20) In the Replace text box, type Disti and, in the With box, type Distributor
22) For Dimension, double-click Customer , and for Field Type select
Generation .
The number 3 is displayed for the generation number.
24) For Dimension, double-click Customer , and for Field Type select Generation .
The number 4 is displayed for the generation number; if it is not, en ter it.
25) Click OK .
You return to the Data Prep Editor.
30) Click OK .
3) When you receive the message, “The rules file is correct for dimension building,”
click OK .
7) Click Find Data File and select the CusChan.xls file located in the
BCI\LoadRule directory.
9) On the Analytic Server tab, select Channel.rul from the file list.
10) Note the location of the dimbuild.err file directory. Review this file if errors occur
during the loading process.
In this exercise, you create a new load rule that defines the Region
Total attribute dimension. This exercise assumes that you have the
Sales outline open.
2) Add the following children to Region Total: Mid West , South , East , and West
5) Set the Dimension type to Attribute and the Attribute type to Tex t .
6) Click OK .
7) Select Customer .
9) Select the Attributes tab and assign Region Total to the Customer dimension.
2) Select Options > Associate outline and associate the load rule with the Sales
database.
3) Select File > Open data file and open the LoadRule/CusReg.xls file from the
File System
4) In the Attribute members section, select Allow association changes and Do not
create members .
5) Click OK .
You return to the Data Prep Editor.
5) Click OK .
You return to the Data Prep Editor.
Defining the Field Column Properties
You want to assign the Region Total attributes to the Level 0 customers.
3) Select the Dimension Build Proper ties tab.Information for Field Number 1 is
displayed.
7) Click Next .
9) In the Field Type section, select Region Total (located under Attribute
dimensions).
11) Click OK
3) Save the file as AttReg to the Essbase Server under the Sales database.
2) Click Find Data File and select the CusReg.xls file located in the BCI\LoadRule
directory.
4) On the Analytic Server tab, select AttReg.rul from the file list.
5) Note the location of the dimbuild.err file directory. Review this file if errors occur
during the loading process.
6) Click OK .If the load fails, open the error file, make corrections, and then try again.
7) To verify that region attributes were added for customers, expand the Customer
dimension
regions to respective
customers
In this exercise, you create a new dimension build load rule to build a Capacity Total
Attribute dimension. This exercise assumes that you have the Sales outline open.
2) Select Options > Associate outline , and then associate the load rule with the Sales
database.
6) Skip the first header row in the data source ( Options > Data source properties
To create the attribute dimension, you attach it to a base dimension. To do that, you
create the attribute dimension as an attribute of the base dimension. You also define the
type of attribute: numeric, text, Boolean, or date.
3) Right-click the Product dimension (your base dimension) and select Edit
properties .
7) Click OK .
You return to the Dimension Build Settings dialog box.
8) Click OK .
You return to the Data Prep Editor.
15) Under Attribute Members, select Allow association changes and Do not create
members .
Alter the transparent partition between Bigwest (source) and Bigcorp (target) in the
following manner:
2) Highlight Field 1 and click Down until Field 1 is in the bottom position in the
displayed list.
3) Click OK .
You return to the Data Prep Editor where the field titled Product is now displayed as
Field 3.
Copying Field 2 (Production)
1) Highlight any item in Field 2, and then select Field > Create using join.
3) Highlight any item in Field 3, and then select Field > Move .
The Move Field Dialog is displayed.
You want the base member field (Lightbolt 365 A) to precede the new Production
column. Anything that is not a member in the database is applied to the preceding
column of member information.
Defining the Field Column Properties
1) Highlight any item in Field 1 and select Field > Properties .
2) On the Dimension Build Properties tab, complete the field properties as indicated in
this table:
3) When you receive the message “The rules file is correct for dimension building,”
click OK .
4) On the Essbase Server, save the file as AttCap to the Sales database.
2) Click Find Data File and select the attcap.xls file located in the BCI\LoadRule
directory.
4) On the Analytic Server tab, select AttCap.rul from the file list.
5) Note the location of the dimbuild.err file directory. Review this file if errors occur
during the loading process.
6) Click OK .
If the load fails, open the error file, make corrections, and then try again.
7) To verify that the dimension build was successful, expand the Product dimension.
Data files can come from a variety of sources and may have very different structures
and challenges. In this exercise, you create data load rules for three files with different
structures. Some of the challenges you may encounter are:
Incorrect format of some data fields The need to ignore some fields and rows in the file
Missing dimension information needed for a successful load
Try to identify as many specific challenges as possible before beginning the exercise.
This exercise assumes that you have the Administration Console open and the Bigcorp
application and Sales database selected.
2) Select Options > Associate outline and associate the rule with the
Sales database.
This is the correct mode setting for creating a load rule that loads data.
4) Click OK .
You return to the Data Prep Editor.
8) Click Next .
9) Repeat steps 7 and 8 to set Field 2, Field 3, and Field 4 to Product , Yea r Tot ,
and Accounts , respectively.
11) Select Data field for Field 5 and then click OK . The Field Properties dialog box
closes and your field names are updated based on your choices.
Remember that each dimension must be identified in the data file. In this file, Scenario
is not represented. The data applies to the Budget scenario. Set up a Scenario header to
identify this dimension with the data.
3) Expand Scenario .
3) Save the rule as Budget on the Essbase Server under the Sales database.
2) Click Find Data File and then select Budg et.txt from the File System tab
(located in the BCI\LoadRule directory).
4) Click Find Rules File , select the Analytic Server tab, and then select the
Budget.rul load rule.
5) Click OK .
The load rule is executed. A message informs you that the files loaded with no errors.
6) Click Close .
You return to the Administration Console.
If the header record in the data source matches the member names in your Essbase
database, you can direct the load rule to read the information in the source file rather
than manually creating field names. This method cuts down on maintenance and allows
you to store fewer load rules.
1) Select Options > Data source properties , and then select the Header tab.
3) Click OK .
5) On the Global Properties tab, set up a rule to replace CustID- with nothing. You do
not need to select the Case Sensitive, Match Whole Word, or Replace All Occurrences
options.
6) Click OK .
The customer names appear scrubbed of their prefix and ready to load into the
database.
8) Save the rule as PriorYr on the Essbase Server under the Sales database.
2) Click Find Data File and then select PriorYr.txt from the File System tab
(located in the BCI\LoadRule directory).
4) Click Find Rules File , select the Analytic Server tab, and then select the
PriorYr.rul load rule.
5) Click OK .
The load rule is executed. A message informs you that the files loaded with no errors
and provides the location of the data file.
6) Click Close.
You return to the Administration Console.
4) Ignore the first header row.Ignoring Fields and Setting Field Properties
1) Select fields 7 , 9 , 10 , 12 , and 14 .
4) Click OK .
Field1 Scenario
Field2 Product
Field3 Customer
Field5 Units
Field8 “Discount %”
Field11 “Labor/Unit”
Field13 “Matl/Unit”
8) Save the rule as Loadcorp on the Essbase Server under the Sales database.
2) Click Find Data File , select the File System tab, and then select Actual.txt and
Forecast.txt (located in the BCI\LoadRule directory).
4) Click Find Rules File , select the Analytic Server tab, and then select the
Loadcorp load rule.
5) Click OK .
The load rule is executed. A message informs you that the files loaded with no errors.
6) Click Close .
You return to the Administration Console.
5) Select Bigcorp and Sales from the Application and Database drop-down lists,
respectively.
6) Click OK .
9) Double-click Scenario to expand it and verify there is data for Current Year, Prior
Year, Forecast, and Budget scenarios
This exercise assumes that you are logged on to the Bigcorp application and Sales
database and are working in the Essbase Spreadsheet Add-in.
There are a variety of ways to produce this challenge report. This is one possible
solution. This exercise assumes that you have the SSReports.xls file open.
3) Select Product .
7) Select Customer .
9) Select Customer .
This exercise assumes that you are logged on to the Bigcorp application and Sales
database and are working in the Essbase Spreadsheet Add-in. There are a variety of
ways to produce this challenge report. This is one possible solution. This exercise
assumes that you have the SSReports.xls file open.
5) In the Members , expand Channel Total and OEM . section The children of
OEM are displayed under Members.
6) Select IBM .
7) Click Add .
IBM moves under Rules.
8) Click OK .
IBM replaces Customer on the report.
9) Select Accounts .
13) Click OK .
18) Click OK .
26) In the Members section, expand Quar ter 2 and select Apr .
31) In the Rules section, right-click Y-T-D and select Specify Latest .
33) Under Output Options , clear the Place Down the Sheet option.
34) Click OK .
The selected time periods become column headers in your report.
45) Click OK .
The Essbase Member Selection dialog box is displayed.
46) Click OK .
Configuration A names beginning with LIGHT and MAV replace Product.
2) Drag Accounts to
Page Dimensions .
3) Double-click Units .
Units is displayed under Selection Rules.
8) Under Selection Rules, right-click OEM and then select Select >
Children .
10) For Yea r Tot , select Jan , Feb , Mar , and Apr .
You can select the Qtr 1 children by adding Qtr 1 to the selection rules, then right-
clicking to select children.
11) Right-click in the Members box and select View by > Dynamic Time series
13) Under Selection Rules, right-click Y-T-D and select Specify Latest .
16) Right-click the Member box and select View by > Level .
18) Right-click the Member box and select Suppress Shared Members .
Filtering Data
1) In the navigation panel, select Data Filtering .
Sorting Data
1) In the navigation panel, select Data Sorting .
3) Under Column Used for Sort , double-click to create a new sort rule.
5) Select Y-T-D(Apr) for Column Used for Sort. As you make your selections, the data
sort rule is built in the navigation panel.
4) Click OK .
5) In the navigation panel, right-click any member in the query and then select Apply
Query .
Module 4
2) After the CALC DIM statement, add a block of formulas to derive the correct rates
for the following accounts: List Price , Discount % , Labor/Unit , Matl/Unit ,
Overhead Rate , Gross Margin % .
Enclose the group of formulas in parentheses to prevent jump-ahead behavior from the
CALC DIM statement.
/* Housekeeping */
SET UPDATECALC OFF;
/* Housekeeping */
25936855.doc Confidential Page 131 of 148
131
© Adaequare, Inc
SET UPDATECALC OFF;
ENDFIX
Save the script as FixIt and calculate. Check your results on the FixIt
tab of the Anatomy.xls file.
/*Housek eeping.*/
SET UPDATECALC OFF;
CLEARBLOCK NONINPUT;
Units
(
IF (@ISMBR (Sep))
Units = @Prior (Units, 1);
"List Price" = @Prior ("List Price", 1) * .9;
ELSEIF (@ISDESC ("Quarter 4"))
Units = @Prior (Units, 2) * 1.1;
"List Price" = @Prior ("List Price", 1) * .9;
ENDIF
)
Extra Credit :
/*Housek eeping.*/
SET UPDATECALC OFF;
CLEARBLOCK NONINPUT;
Units
(
IF (@ISMBR (Sep))
Units = @Prior (Units, 1);
"List Price" = @Prior ("List Price", 1) * .9;
ELSEIF (@ISDESC ("Quarter 4"))
Units = @Round ((@Prior (Units, 2) * 1.1), 0);
"List Price" = @Prior ("List Price", 1) * .9;
ENDIF
)
Account Formula
2) Make both Unit Mix and Sales $ Mix and enable Two Pass calculation .
3) Save the outline and check your results on the ANCESTVAL It tab in the
Anatomy.xls file.
Since the calculations are dynamic, you do not have to recalculate them.
There are various solutions to this exercise. The following calculation script represents
one possible answer:
/* if prior year and jan or feb, then Moving Average = jan and feb respectively */
"Moving Average"
(
If (@ismbr("prior year") AND @ismbr(jan,feb))
"Moving Average"=units;
In this exercise, you create a new application and database, load data, and calculate the
new database. You use a Microsoft Excel workbook to compare precalculated data
without dynamic calculations to the new data that was calculated with dynamic
calculation settings in the database outline. You use one of two solutions to correct the
calculation so that both the nondynamic and dynamic data values are equal. You record
data block statistics. In the new database outline, you use dynamic calculations and
two-pass calculations wherever possible and in a way that still keeps the dynamic data
in sync with the nondynamic data.
1) In the Administration Console, right-click the Dynamic database and select Stop .
The Confirm Database Stop dialog box is displayed.
2) Click Ye s .
3) Right-click the Dynamic database and select Start . The Confirm Database Start
dialog box is displayed.
4)Click Ye s .
You can select both files by pressing the Ctrl key and
clicking the files.
5) Click OK .
10) Click OK .
11) Click OK .
The data is loaded and the Data Load Completed dialog box
is displayed.
16) Click OK .
The values in the No Dynamic spreadsheet represent a retrieve from the Bigcorp
database with no dynamic calculations. These values are correct and should be used
to compare your dynamic calculation results.
6) Select cell B3 .
9) View the results and investigate all nonzero values. Correct values that were not
calculated properly.
A zero indicates that there is no difference between the “no dynamic” and the dynamic
spreadsheet values.
Solutions
The comparison spreadsheet should show several nonzero amounts in the Act vs Fcst
column as well as #VALUE in the Other CGS and Balance Sheet rows. The Other CGS
and Balance Sheet rows are correct. A review of the “no dynamic” and the dynamic
spreadsheets for those rows show that both of them have no data (N/A). The nonzero
numeric values indicate a problem with the dynamic data. The problem is created
because the calculation order is sparse, then dense. There are two possible solutions for
correcting the calc.
5) Click Save .
7) Select (Default) .
8) Click OK .
All values are now zero with the exception of Other CGS and Balance Sheet, which is
correct.
2) Select Properties
3) Scroll down to the dimension storage types and, next to Scenario, click Sparse .
6) Click Save .
The Restructure Database dialog box is displayed.
8) Click OK .
11) Click OK .
All values are now zero with the exception of Other CGS and Balance Sheet, which is
correct.
Module 5
2) Click Ye s .
4) Load Actual.txt and Forecast.txt to Sales using the loadcorp.rul rules file (all
located in the BCI\CalcIt\AdvancedCalcs directory).
6) Select CalcAll .
7) Click OK .
5) Click Verify .
Fix any verification errors before continuing.
6) Click Save .
The Save As dialog box is displayed.
11) Click OK .
Viewing the Result
1) In the calculations.xls workbook on the Datacopy worksheet,
select Essbase > Retrieve .
2) To test and verify some of the budget figures, multiply the Prior
Yea r value times 110% ( 1.1 ).
Updating Substitution Variables
1) On the Administration Console, select Essbase Analytic Servers >
<server name> > Variables .
4) Click Set .
6) Click Set .
7) Click Close .
Creating a Rolling Forecast from Actual and Budget Data
1) Open a new calculation script.
The Calc Script Editor is displayed.
/*this is a generic calc to copy all data prior to the current month from
actuals for current year to rolling forecast followed by a copy of all budget
data for current year and the following months to rolling forecast*/
FIX (Jan:&PriorMonth)
DATACOPY “Current Year” TO “Rolling Forecast”;
ENDFIX
FIX (&CurrentMonth:Dec)
3) Click Save .
The Save As dialog box is displayed.
7) Select BudcopyB .
8) Click OK .
Viewing the Result
1) In the calculations.xls workbook on the Datacopy spreadsheet,
select Essbase > Retrieve .
/* main roll-up */
CALC DIM (Product);
/* back calc */
(
"List Price" = "Gross Sales" / Units;
"Discount %" = Discounts / "Gross Sales";
"Labor/Unit" = "Direct Labor" / Units;
"Matl/Unit" = Material / Units;
"Overhead Rate" =Overhead / "Direct Labor";
)
/* this the first part: count the number of customers who bought a given product */
"Customer Count" = @count(SKIPMISSING, @RANGE (Units, @LEVMBRS
(Customer, 0)));
Extra Credit
Units
(
IF (Units <> #Missing AND @ISLEV (Customer, 0))
"Customer Count" = 1;
ELSE /* set the customer count to missing when units are missing */
CLEARBLOCK ALL;
/*HOUSEKEEPING.*/
FIX (Budget)
/*THE NORMALIZATION.*/
/*Focused rollup for allocation of Other Expenses: calculate Net Sales, then sum
Units
(
"List Price" = "Gross Sales" / Units;
"Discount %" = Discounts / "Gross Sales";
"Labor/Unit" = "Direct Labor" / Units;
"Matl/Unit" = Material / Units;
"Overhead Rate" =Overhead / "Direct Labor";
Material Variances
Extra Credit
FIX(@children(Performance))
"Obsolete Charges"="Obsolete Charges"->Performance->Customer/
@count(SKIPMISSING,@Range(units,@ISIBLINGS(@Currmbr(Product))));
endfix
FIX(@children(Value))
"Obsolete Charges"="Obsolete Charges"->Value->Customer/
@count(SKIPMISSING,@Range(units,@ISIBLINGS(@Currmbr(Product))));
endfix
FIX(@children(LIGHTBOLT))
"Obsolete Charges"="Obsolete Charges"->Lightbolt->Customer/
@count(SKIPMISSING,@Range(units,@ISIBLINGS(@Currmbr(Product))));
endfix
FIX(@children(THUNDERBALL))
"Obsolete Charges"="Obsolete Charges"->Thunderball->Customer/
@count(SKIPMISSING,@Range(units,@ISIBLINGS(@Currmbr(Product))));
endfix
FIX(@children(ROADRANGER))
"Obsolete Charges"="Obsolete Charges"->Roadranger->Customer/
@count(SKIPMISSING,@Range(units,@ISIBLINGS(@Currmbr(Product))));
endfix
FIX(@children(MAVRIDER))
"Obsolete Charges"="Obsolete Charges"->Mavrider->Customer/
@count(SKIPMISSING,@Range(units,@ISIBLINGS(@Currmbr(Product))));
endfix
FIX(@children(FIREBRAND))
"Obsolete Charges"="Obsolete Charges"->Firebrand->Customer/
@count(SKIPMISSING,@Range(units,@ISIBLINGS(@Currmbr(Product))));
endfix
FIX(@children(Performance),@children(Value))
"Obsolete Charges"=@mdancestval(2,product,3,customer,2,"Obsolete
Charges")/
@count(SKIPMISSING,@Range(units,@ISIBLINGS(@Currmbr(Product))));
endfix