Plan Type Artifacts

Plan types are used to store Planning application information in the Essbase database. A separate database stores data for each plan type in the application, and contains information relevant to that plan type to optimize application design, size, and performance. The default Planning plan types include Plan1, Plan2, and Plan3.

The Plan Types directory contains attribute dimensions, standard dimensions, data forms, rules files, calc scripts, substitution variables, and Calculation Manager rules artifacts.

Table 40. Plan Type Artifacts

ArtifactDescriptionLast Modified TimeLast Modified UserEditable on the File System?Dependencies

Attribute Dimensions[1]

A list of dimensions whose type enables analysis based on the attributes or qualities of dimension membersYesNoYes—XMLNone

Standard Dimensions*

A list of dimensions associated with a single plan typeYesNoYes—XMLAttribute Dimensions, if any
Data Forms

A grid display that enables users to enter data into the database from an interface such as a Web browser, and to view and analyze data or related text. Certain dimension member values are fixed, giving users a specific view into the data.

Data forms can include predefined data validation rules that help implement business policies and practices. Errors or warnings are generated on the data form if entered data violates a validation rule.

YesNoYes—XMLAssociated menus, user variables, business rules, and dimensions
Rules filesLogical expressions or formulas that are created within an application to produce a preferred set of resulting valuesYesNoNo (Yes—Oracle Essbase Administration Services)None
Calc ScriptsA set of commands that define how a database is consolidated or aggregated. A calculation script may also contain commands that specify allocation and other calculation rules separate from the consolidation process.YesNoYesNone
Substitution VariablesGlobal placeholders for information that changes regularlyNoNoNoNone

Calculation Manager Rules[2]

Objects that can contain templates and calculations that are grouped in components

Yes

Yes

Yes—XML

None

1 Only visible for Classic applications.

2 Only visible for Classic applications with Calculation Manager set as the calculation module.