BDA Cube View Editor

Application Summary

The BDA Cube View Editor attaches run-on-save Data Management Sequences to Cube Views in a code-free manner.

BDA Cube View Editor Overview

The BDA Cube View Editor attaches one (or many) Data Management Sequences to Cube Views so that they may run on save.

Optional use of Windows Communication Function (Wcf) parameters allow focused calculations to fire only for changed data, thus significantly reducing calculation scope and consequently improved performance.

The typical practice of encapsulating a Cube View within a Dashboard to capture a Save event is no longer necessary as they now have their own configurable one.

Setup and Installation

The installation process for all BDA Solutions is the same: download the install zip file from Partner Place, import, and run the BDA_FW_Dashboard_Setup dashboard using the purchased product keys. The zip file contains all BDA Solutions; the keys unlock the purchased Solutions.

See the BDA Installation Solution Guide SV1.0.0 for more information.

BDA Cube View Editor Solution

Functionality Overview

There are five general functional areas:

1) Available Cube Views

2) Available Data Management Sequences

3) Assign, unassign, assigned Sequence order, and assignment status confirmation.

4) Assigned Data Management Sequences

5) Sequence Run Method select box

Graphical user interface, application Description automatically generated

Available Cube Views

Cube Views listed by Cube View Group. Assigning a Data Management Sequence will move the Cube View from the Not Currently In Use list to In Use. Only that Cube View is moved; unassigned Cube Views in the Cube View Group remain.

Available Data Management Sequences

Data Management Steps must be assigned to a Data Management Sequence for assignment.

Data Management Sequence order

More than one Data Management Sequence can be assigned. Sequences, once added, can be removed.

If there are multiple Sequences, their order can be changed.

Assigned Data Management Sequences

Lists the assigned Data Management Sequences.

Sequence Run Method

There are five run methods that control how many times and by what dimension when the Data Management Sequence is triggered on data change.

Method	Impact
Entity	The default method executes the Data Management Sequence for each impacted Entity.
Entity + Scenario	Executes the Data Management Sequence for each impacted Entity and Scenario combination.
Entity + Time Period	Executes the Data Management Sequence for each impacted Entity and Period combination.
Entity + Scenario + Time Period	Executes the Data Management Sequence for each impacted Entity, Scenario, and Period combination.
Run Once	Primarily used for consolidations/aggregations. No matter how many changes are made in Cube View, this Data Management Sequence runs once per save.

Using Cube View Editor

Calculation

To illustrate the focused calculation functionality, consider an overtime expense that is 20% of base pay. In GolfStream, that is A#50210 and A#50200. Its simple calculation is as follows:

Text Description automatically generated with medium confidence

Cube View

Consider a Cube View that shows all of 2011’s periods in the Scenario BudgetV7:

A picture containing table Description automatically generated

The below shows the row definition for South Houston; Houston’s differs only in the Entity.

Base	Overtime

The POV sets all dimensions save Entity, Time, and Account:

A picture containing table Description automatically generated

To allow the Cube View Editor to dynamically identify changed cells, Entity and Time must be specified as Windows Communication Foundation (Wcf) parameters.

Wcf

Dimension	Parameter Key	Parameter Value
Cube	WcfCb	\|!WcfCb!\|
Entity	WcfE	\|!WcfE!\|
Scenario	WcfS	\|!WcfS!\|
Time	WcfT	\|!WcfT!\|
Account	WcfA	\|!WcfA!\|
Flow	WcfF	\|!WcfF!\|
Origin	WcfO	\|!WcfO!\|
Intercompany	WcfIC	\|!WcfIC!\|
UD1	WcfU1	\|!WcfU1!\|
UD2	WcfU2	\|!WcfU2!\|
UD3	WcfU3	\|!WcfU3!\|
UD4	WcfU4	\|!WcfU4!\|
UD5	WcfU5	\|!WcfU5!\|
UD6	WcfU6	\|!WcfU6!\|
UD7	WcfU7	\|!WcfU7!\|
UD8	WcfU8	\|!WcfU8!\|

If the BDA Task Editor is in use the parameters from the combo boxes can also be used instead of the Wcf parameters. The parameter names would be named _Param_cbx_BDA_FW_X where X is the dimension letter. For example, instead of WcfU1 for the U1 dimension the POV filter could be referenced by _Param_cbx_BDA_FW_U1.

Note: Non-Data Unit dimensions can be passed to Finance Business Rules using the Parameters Business Rule property in the Data Management Step:

Graphical user interface, application Description automatically generated

Data Management Step

In this example, Entity and Time are substituted with Wcf parameters:

Graphical user interface, application Description automatically generated

Note that this approach of calculating Time on a per-member basis may cause time-dependent calculations to be incorrect because it calculates just the impacted Periods.

Data Management Sequence

In this example, the Data Management Sequence has one Step:

Graphical user interface, application Description automatically generated

Cube View Editor

In the Cube View Editor Solution, the Data Management Sequence Cube_View_Editor is assigned to the Cube View BDA_FW_Cube_View_Editor:

Graphical user interface Description automatically generated

Data Explorer

Entering information – in this case across two Entities – and then clicking on Save fires the Data Management Sequence.

Input by Entity

Table Description automatically generated

Result

Table Description automatically generated

Input by Time

Table Description automatically generated

Result

Graphical user interface Description automatically generated with medium confidence

Excel

Cube View Editor’s calculation functionality extends to Excel and the OneStream Spreadsheet. Embedded Cube Views behave similarly to Cube Views in Data Explorer.

Entering data and then clicking Submit both sends the data and triggers the calculation.