Compatibility Notes

Casabase Cube supports many of the multidimensional modeling concepts used by Oracle Essbase and Oracle Cloud EPM, including dimensions, hierarchies, shared members, aggregation operators, dynamic member formulas, two-pass calculations, and solve order.

However, Casabase Cube is not an Essbase runtime and does not reproduce every Essbase feature or behavior.

This page identifies known compatibility differences that can affect applications migrated from Oracle Essbase or Oracle Cloud EPM.

Review these items when evaluating or performing a migration.

Aggregation Operators

Casabase Cube supports a defined set of aggregation operators.

During migration, unsupported aggregation operators are automatically converted to a supported operator.

Standard Dimensions

For standard dimensions, Casabase Cube supports the following aggregation operators:

Operator	Behavior
`+`	Addition
`-`	Subtraction
`~`	No aggregation

If a member in a standard dimension uses another aggregation operator, Casabase Cube automatically converts the operator to:

For example:

Essbase aggregation operator
        │
        ├── +  →  +
        ├── -  →  -
        ├── ~  →  ~
        └── Other  →  ~

Review members using other Essbase aggregation operators after migration to determine whether additional modeling or formula changes are required.

Attribute Dimensions

For attribute dimensions, Casabase Cube supports the following aggregation operator:

If an attribute-dimension member uses another aggregation operator, Casabase Cube automatically converts the operator to:

Conceptually:

Attribute Dimension
        │
        ├── +  →  +
        └── Other  →  +

This differs from standard dimensions, where unsupported operators are converted to ~.

Dynamic Member Formulas

Casabase Cube supports dynamic member formulas, but there are several important compatibility differences when migrating formulas from Oracle Essbase or Cloud EPM.

Formulas on the Time Dimension

Dynamic member formulas on the dimension tagged as the time dimension are not supported.

The time dimension is typically the:

Period

dimension.

For example, if Period is the cube’s time dimension:

Period
├── YearTotal
├── Q1
├── Q2
├── Q3
└── Q4

dynamic member formulas defined directly on members of that dimension are not supported.

This restriction applies specifically to formulas attached to members of the dimension designated as the cube’s time dimension.

Formulas on other dimensions can still reference time members and use supported time-navigation functionality.

See Time Navigation for supported time-aware formula behavior.

Formulas That Create Data

Dynamic member formulas that result in data creation are not supported.

Casabase Cube dynamic member formulas are evaluated as part of query-time calculation. They are intended to calculate values from the cube’s existing data and multidimensional context rather than create new stored data.

When migrating an Essbase or Cloud EPM application, review formulas whose behavior depends on creating data rather than dynamically calculating a query result.

These formulas may require a different implementation in Casabase Cube.

Formulas on Stored Members

Casabase Cube does not support dynamic member formulas on members configured as stored-data members.

A member marked as:

storeData

is treated as a stored member rather than a dynamic calculated member.

If an Oracle Essbase or Cloud EPM outline contains a member formula associated with a stored-data member, Casabase Cube removes the formula from that member during migration.

Conceptually:

Essbase / Cloud EPM Member
        │
        ├── storeData = false
        │       │
        │       └── Formula can be migrated
        │
        └── storeData = true
                │
                └── Member formula removed

The member itself is still migrated. Only the unsupported formula association is removed.

Migration Notification

When an Essbase outline is imported using:

IMPORT_ESSBASE_OTL

Casabase Cube notifies the user when member formulas are removed because they are associated with stored-data members.

Review these notifications after importing an outline.

They identify formulas that require evaluation before the migrated cube is considered functionally equivalent to the source application.

Member Functions

Casabase Cube supports the member functions explicitly documented in the Formulas section of this documentation.

Member functions that are not explicitly listed in the Casabase Cube documentation are not supported.

Do not assume that an Essbase member function is supported simply because its syntax is accepted or because a similarly named function exists in Oracle Essbase.

In addition, successful formula parsing does not prove that a construct is executable by the query engine. VALIDATE_FORMULA is a syntax check. Representative migrated formulas should also be tested with real cube queries.

When reviewing formulas during migration:

Identify the member functions used by the source application.
Compare them with the functions documented by Casabase Cube.
Review formulas containing functions that are not documented as supported.
Rewrite the formula using supported Casabase Cube functionality where an equivalent implementation is available.

See:

Migration Behavior Summary

Essbase / Cloud EPM Feature	Casabase Cube Behavior
Standard-dimension `+` aggregation	Supported
Standard-dimension `-` aggregation	Supported
Standard-dimension `~` aggregation	Supported
Other standard-dimension aggregation operators	Converted to `~`
Attribute-dimension `+` aggregation	Supported
Other attribute-dimension aggregation operators	Converted to `+`
Dynamic formulas on the time dimension	Not supported
Dynamic formulas that result in data creation	Not supported
Dynamic formulas on stored-data members	Formula removed during migration
Supported documented member functions	Supported
Undocumented member functions	Not supported

Review Migration Messages

Migration messages should be reviewed after importing an Oracle Essbase or Cloud EPM outline.

In particular, review notifications from:

IMPORT_ESSBASE_OTL

for formulas that were removed from stored-data members.

A successful outline import means that Casabase Cube was able to create the migrated multidimensional structure. It does not necessarily mean that every source-system behavior has a direct Casabase Cube equivalent.

Compatibility messages should therefore be treated as part of the migration review process.

Validate the Migrated Cube

After migration, validate important analytical behavior against the source application.

Pay particular attention to:

Members whose aggregation operators were converted
Dynamic member formulas
Stored members that contained formulas in the source outline
Formulas using Essbase member functions
Time-related calculations
Key financial or operational calculations

A useful validation approach is:

Source Essbase / Cloud EPM Result
              │
              ▼
       Known Test POV
              │
              ▼
       Casabase Cube Result
              │
              ▼
           Compare

Use representative POVs that exercise the application’s important hierarchies, formulas, and aggregation behavior.

Compatibility vs. Functional Equivalence

A migrated cube does not need to reproduce the internal implementation of Essbase in order to produce the required business result.

In some cases:

Essbase Implementation
        │
        ▼
Different Casabase Cube Implementation
        │
        ▼
Equivalent Business Result

is preferable to attempting to reproduce an Essbase-specific implementation pattern.

When a source feature is not directly supported, determine whether the underlying business requirement can be implemented using supported Casabase Cube modeling, formula, or Snowflake capabilities.

The objective of migration should be functional equivalence of the required analytical behavior, rather than one-to-one reproduction of every Essbase implementation detail.