Planning Certification

Imports Planning application access for users and group

Imports Users and groups into planning

Requires the source text file to be named PLANSECFILE.txt

Can be scheduled to run nightly using an encrypted password

Clears existing security definitions by default before the import takes place

You cannot build alternate rollups or assign custom attributes

Base currencies are assigned to entity members

Exchange rates are assigned to entity members

Entity along with Scenario and Periods make up a planning unit

Entity along with Scenario and Version make up a planning unit

Dimension and member changes are pushed to Essbase

Cell text and supporting detail changes are pushed to Essbase

Security filters for dimensions and members are pushed to Essbase

Security filters for shared members are pushed to Essbase

Data changes are pushed to Essbase

Use the Planning data form utility to update data forms; Use "CurMo" Global variable for business rules and use a "CurMth" substitution variable for essbase data load rules, and reports

Manually update the forms each month and use a "CurMth" substitution variable for Business Rules, Essbase data load rules, and reports.

Manually update the forms each month; Use "CurMo" Global variable for Business Rules and use a "CurMth" substitution variable for Essbase data load rules, and reports.

Use the Planning data form utility to update data forms and use a "CurMth" substitution variable for Business Rules, Essbase data load rules, and reports.

Use a "CurMth" substitution variable for data forms, Business Rules, Essbase data load rules, and reports.

Standardized data forms for plan data entry available both or) the Web and in Excel

One tool to budget and forecast as well as provide reporting for very detailed Actuals Information

Central repository of business rules that can be run by end users to calculate plan data

Detailed security down to the cell level

Flexible solution customizable for almost any kind of budgeting and forecasting process

Grid Spread

Planner

Interactive User

Mass Allocate

Offline User

Dynamically calculated members should roll up to stored members.

You cannot calculate and store dynamic calculated members in calc scripts and business rules.

Consider dynamic calc members on sparse parents with 100 t children.

Tagging upper-level members ofspaise dimensions can reduce block size.

If you use a large number of dynamiccalcs, you should consider increasing the Dynamic Calculator Cache.

Consider Dynamic Calc and Store over Dynamic Calc.

Versions control data entry based on time periods set by the administrator.

There is only one Version to one Scenario.

Versions allow several "what-if" Scenarios.

Users must have the same security settings in the Version dimension as they have in the Scenario dimension.

Versions can be top down or bottom up.

Member access has been assigned to a group.

Member access has been assigned to a user.

New group is created.

Member "East" has OHDESCENDANTSCREAD.access assigned; A new

New business rule is created.

Select or reject records based on certain criteria.

Flip the sign for records with a certain member tagged with a comment.

Split or join columns in a source.

Find and replace manipulations on source records.

Map data based on an external table.

Aggregate

Copy Data

Clear Block

Clear Data

Create Block

Allocate

A user-defined custom dimension may exist in one plan type but not the other plan types.

A user-defined custom dimension may have members in one plan type but not the remaining plan types.

All members in the entity dimension must exist in all plan types.

All members in the accounts dimension must exist In all plan types.

All periods must exist in all plan types.

Security can be assigned to members of the Scenario dimension.

It allows the administrator to assign valid periods for data entry

It allows bottoms up or target planning

Exchange rate tables are tied to the Scenario dimension.

One member in the scenario dimension may be valid for Plan Type may be valid for Plan Type 8.

Number of years

Names of plan types

Number of plan types

Initialization of WFP orCapEx Planning modules

Weekly distribution spread

Year Dimension Name

Default Currency

With Financial Reporting, create a book for each store that contains a P&L for each store and use the book to distribute the reports to store managers via email.

With Financial Reporting, create a store P&L and use batch bursting to distribute the report to store managers via email.

With Web Analysis,create an income statement that store managers can log in and access.

Within Smart View Report Designer, use the Cascade feature to generate and distribute each store income statement via email.

Create a Planning P&L Data form and use email notification to send to store managers.

At least one member in the Scenario dimension

At least one member In the Version dimension

At least one member in the Period dimension

At least one member in the Account dimension

At least one member in the Entity- dimension

If security has been assigned for a Custom dimension, at least one member in the user-defined custom dimension

Aliases are supported for attribute members.

Consolidation properties are supported for attribute members.

Hierarchies are supported for attribute dimensions.

Only Text attributes are supported.

Text, Boolean, Numeric, and Date attributes are supported.

Copy data values from one dimensional intersection to another dimensional intersection.

Copy planning unit annotations.

Copy supporting detail.

Copy cell text.

Copy account annotations.

~

^

Stored

Dynamic Calc

Dynamic Calc and Store

Custom menus can provide links to data forms, Business Rules, URLs, and Planning preferences.

Custom menus require Java scripting knowledge to create.

You can assign security to custom menus so that only specific users or groups can see the custom menu.

Custom menus are assigned to data forms only.

Custom menus are limited to a single list of tasks; you cannot group them into sub categories.

1, 4, 5

1, 2, 3

2,3,4,5

1,2,3,5

1, 2,3,4,5

Esscmd

Calc Script

Business Rule Sequence

MaxL

Business Rule Macro

You cannot build a data form with these two columns, hour columns will display: Actual >2010, Actual >2011, Budget->2010 and Budget >2011

Use Segments on the data form to create the asymmetric columns.

Use User Variables on the data form to create the asymmetric columns.

Use a composite data form to meet this requirement.

Use data suppression on the data form.

For Weekly Distribution options 445, 454, 544, the quarterly values are treated as if they are divided into 13 weeks and the weeks are distributed via a pattern you specify.

The only valid weekly distribution options are 445, 454, and 544.

If you select the 4-5-4 Weekly distribution option, Planning treats the first month in the quarter as if it has 4 weeks, the second month as If it has 5 weeks, and the third month as if it has 4 weeks.

If you choose weekly distribution for Custom-based time periods. Planning will not distribute the data values across base periods.

Weekly distribution determines how data entered into summary periods should spread to its base periods.

Planning Web Client

EAS

EPMA

DRM

Outline Load Utility

Dimension Editor for Planning

Shared Services

Exchange Rates Definition

Planning Utilities

Create and Manage Database Options

Create Data Sources

Using DATAEXPORT within the FIX statement of a calc script allows you to export specific data sets from anEssbase database.

DATAEXPORT only exports level zero data.

DATAEXPORT only exports to flat files.

DATAEXPORT only exports entire data blocks.

DATAEXPORT is faster thanEssbase Report.

Planning supports hierarchies and aliases for attribute dimensions.

Planning supports all attribute types (for example.Boolean, Date, Text).

Planning supports varying attributes (where an attribute can vary over one or more other dimensions).

Attribute dimensions can be assigned to dense dimensions.

Attribute dimensions may only be assigned to one base dimension.

Block Storage OptionEssbase database

Aggregate Storage Option Essbase database

Relational database

XOLAP database

Open a data form and submit data.

enter supporting detail and cell text.

Run business rules.

Enter planning unit annotations.

Perform workflow tasks.

for preparing, reviewing, and approving data.

for calculating and storing currency plan data.

or assigning security to plan data.

for reporting and analyzing plan data.

made up of Scenario, Entity, and Account.

2, 3, 6

2, 3, 5

1,2,3,5

1, 2,3,4,5

2, 3

1, 2, 3,4,5,6

FIX (Budget, 0LEVMBRS (Market,0)) "Marketing expense" = "Marketing expense "->Corporate * ("Marketing expense" Actual / "Marketing expense" -> Actual -> TotalMarket); ENDFIX

FIX (Budget, (3LEVMBRS (Market, 0) ) ) "Marketing expense" = "Marketing expense"->Corporate * ("Marketing expense"/"Marketing expense" -> TotalMarket) ; ENDFIX

FIX (Budget, (3LEVMBRS (Market, 0) ) --- "Marketing expense" = "Marketing expense"->Corporate * ("Marketing expense Actual ->FY10 / "Marketing expense" -> Actual ->FY10 TotalMarket); ENDFIX

FIX (OLEVMBRS (Market, 0) ) "Marketing expense" = "Marketing expense"~>Corporate * (^Marketing expense Actual ->FY10 / "Marketing expense" -> Actual ->FY10 TotalMarlket); ENDFIX

Sparse dimensions in Page and POV, Dense dimensions in Rows and Columns

Sparse dimensions in Rows and Columns, Dense dimensions in Page and POV

Sparse dimensions in Page and Columns, Dense dimensions in Rows and POV

Sparse dimensions in Page and Rows, Dense dimensions in POV and Columns

The layout of sparse and dense dimensions has no impact on form performance; only the number cells on a data form impacts form performance.

Data may not exist for the combination of dense members so you have to create the block before calculating the data value for the block.

Data may not exist for the combination of sparse members so you have to create the block before calculating the data value for the block.

Data may not exist for the combination of dense members so you have to create the block before block loading data to the block.

Data may not exist for the combination of sparse members so you have to create the block before loading data value to the block.

Is a prebuilt plan type focused on capital expense relatedplanning

Provides complete out-of-the-box functionality forcapex planning including dimensions, data forms, business rules and security

Can be initialized within an existing Planning application

Can be created as a stand-alone application

Because planning limits an application to three plan types,Capex Planning must be the third plan type.

Form Management>>Display tab

Form Management>> Options tab

Preferences>>Database Settings tab

Preferences>> Display Options tab

This change can only be made by the Planning Administrator.

ABC

BCD

ACD

ABCD

Attribute dimension

Varying attribute dimension

Smart List

Free Form Text

Alternate hierarchy

You must delete members one by one.

You must delete a reference to a member from all data forms before deleting it from the dimension.

In a data form definition, you selected @IDescendants(IT) for the entity dimension in the page section. The IT member will remain but 2 of its 10 cost centers are being removed. You must remove the reference to "IT" in this data form.

You should back up all data for the deleted entity members; after a member is deleted, the data is not retained.

A database refresh is required after deleting members from the Entity dimension.

You can only add custom attributes to user-defined custom dimensions.

You assign valid plan types for the user-defined custom dimension at the dimension level.

You assign data types for the user-defined custom dimension at the dimension level.

You cannot: assign security for user-defined custom dimensions.

You can easily delete a user-defined custom dimension in Planning but you cannot delete an Entity dimension.

Reduce the number of rows and columns displayed in the data form.

Upgrade the client machine's operating system processing speed and RAM.

In the data form definition, remove the option to display alias.

Reduce the number of page dimensions used on the Web form

Tune the index and data caches inEssbase.

Block size = 40 * 17 * 2

Block size = 40 * 17 * 2 * 8

Block size = 50 * 17 * 5 * 8

Block size = 50 * 17 * 5

Block size = 100 * 500 * 8

Planning

EPMA

ODI

LCM

Calculation Manager

EAS

FR Studio

Grid Spreader processes on the client whereas Mass Allocate processes on the server.

Mass Allocate generates and runs a business rule behind the scenes, allowing members not displayed on the form to be updated.

Both M-3CG Allocate and Grid Spreader require special roles in Shared Services.

Grid Spreader gives users a "preview" to the spread result before saving whereas Mass Allocate will automatically save results to the server.

Both Mass Allocate and Grid Spreader support relational spread.

EPM Workspace

Excel Add-in

Smart ViewEssbase Provider

Smart View Planning Provider

Planning ADM Driver for FR

Delete member from a sparse dimension.

Delete member from a dense dimension.

Renaming a member.

Renaming an alias.

Submitting data / deleting data frequently.

1, 2,3,4,5

1,3,4,5

1, 4, 5

2, 3

3

2

Potential Blocks = 40 * 17*2

Potential Blocks = 40* 17*2*8

Potential Blocks = 100 * 500

Potential Blocks = 100 * 500 * 8

Potential Blocks = 100 * 550

Potential Blocks = 100 * 550 * 8

Run on Save

@CALCMODE function

Run time prompts

Can be run over the web

Substitution Variables

Custom Defined Functions

Multiple currencies are required.

Currency rates must be kept in a separate database.

Sales are planned by product and channel, and salary expenses are planned by position.

Security is applied to the Entity dimension but can differ for users for accounts "sales" and "expenses".

You have decided to implement the Capital Expense planning module in addition to PSL budgeting.

Data cannot be shared across the Organization dimension.

If you decide to implement EPMA, all Planning applications must be f PMA-deployed applications.

EPMA-deployed applications may either use EAS Business Rules or Calculation Manager in 11.1.1.3.

You can create Planning, TM,Essbase, and FDM applications in FPMA.

Data can be shared from a Planning application to an FM application within EPMA.

EPMA can be used by end users to manage and update member properties such as hierarchies and aliases

In the Dimension Library, you can maintain one full dimension (for example. Account) but filter portions of the dimension for different applications (for example, Revenue accounts. Balance Sheet)

Administrator for theCapEx application

Administrator for the Planning Server

Provisioning Manager for theCapEx application

Planning Calculation Manager for theCapEx application

Dimension Editor for theCapEx dimensions

Application Manager inEssbase for the CapEx dimensions

Supporting detail

Planning unit annotations

Cell text

Free form text (if defined by your Planning administrator)

Smart Lists (if defined by your Planning administrator)

Attach a document to a data form from Workspace (if enabled by your Planning administrator)

Financial Reporting Annotations in a Financial Reporting document (against the Planning application)

January's value

March's value

The total of January + February + March

The average of January + February + March

1, 2,3,4,5

1,2,3,5

1, 2,3,5,6

1, 2, 3,4,5,6

Planning will build in @XREF calculations in a calc script by default to share data between plan types.

A replicated partition could be created to replicate data from the sales plan type to the summary plan type and this would be done if we wanted to store the sales data in the summary plan type

A transparent partition and @XREF calculations could have performance issues for retrievals because data is not stored; it is dynamically calculated.

A calc export script on the source database with the DATAEXPORT command could be used to export data out of the revenue plan type and calc import script on the target database with the DATAIMPORT command could be used to import the data file to the summary plan type.

To disable the building of @XREF, update the HSP Properties file for the application before you click Create during the application creation process.

1, 2, 3

3, 2, 1

2, 3, 1

3, 1, 2

The business rule has not been assigned to the data form.

The business rule was created for another plan type.

The valid locations have not been defined for the business rule.

The valid locations have not been defined for the data form.

The Validate and Launch privileges have not been granted for the business rule.

The Validate and Launch privileges have not been granted for the data form.

Define Product Status as a Smart List.

Define Product Status as a Separate Dimension

Define Product Status as an Attribute.

Define Product Status as a Varying Attribute.

Define Product Status as an alternate hierarchy in the Product dimension.

Members defined on the data form

Planning Metadata security

Business Rules security access privileges

Essbase security filters

Business Rules Basic User Role

Run a business rule to change the employee's status.

Change the employee's status on a data form using the Smart List drop down.

Change the employee's status on a data form using the free form text measure.

Change the employee status attribute association in the Employee dimension.

Delete the employee from Workforce Planning.

The user doesn't have the Launch Business Rules role in Shared Services.

The user hasn't been assigned Validate and Launch Privileges in EAS.

The location for the Business Rule hasn't been defined.

The user hasn't been assigned access to the Business Rule in the Planning Web client.

1, 2, 3, 4, 5, 6, 7

1, 2, 3, 5, 6, 7

1, 2, 3, 6

1, 2, 3, 4, 6, 7

1, 2, 3, 4, 6

You can assign a custom attribute value to a shared member.

You can define a member formula for a shared member.

You can assign security rights to a shared member.

There is no limit to the number of shared members that you can create for the base member.

Shared members may be defined for Accounts and Entity dimensions only.

Anyone with write access to the planning unit

Anyone with write access to the planning application

Anyone with read or write access to the planning unit

The owner of the planning unit

The administrator

Essbase data block size decreases.

The member is not available for process management.

Retrieval performance could be slower when referencing the parent entity member.

Data cannot be input to the parent in target versions.

Accounts, Time, remaining sparse, remaining dense, Two-Pass

Time, Accounts, remaining dense, remaining sparse, Two-Pass

Accounts, Time, remaining dense, remaining sparse, Two-Pass

Sparse, Accounts, Time, remaining dense, Two-Pass