BDA Data Explorer
Application Summary
The BDA Data Explorer browses Cube data in a wizard-driven, code-free interface via simplified member filters.
BDA Data Explorer Overview
The BDA Data Explorer browses Cube data using Member Script filters either manually entered or created via a member filter wizard.
The filtering process can be a single year, e.g., T#2011, or a fully defined tuple from Cube to UD8. Adding dimensions to the member filter adds specificity to the result set. More than one year can be selected by using the year filter selector; all periods in a year are returned.
A Base member filter operation is implied for all upper level members, e.g., U1#Top selects all of that member’s level zero descendants, U1#Mfg all of that member’s level zero descendants, etc.
Clicking on a result record returns member filter, XFGetCell, and XFSetCell definitions.
Developers, administrators, and – potentially – selected FP&A superusers, can browse all Cube data in all Cubes. Note that Workflow, Entity, and Cube Access security does not apply; access to this utility must therefore be tightly controlled.
No more than 5,000 records can be returned.
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 Data Explorer
OneStream Cube data is stored in a series of tables and is presented to the user via a Cube metaphor. Data Explorer eschews that format and instead shows Cube data in table form that can be browsed, filtered, exported, copied, and cleared.
The Data Explorer dashboard
Display Options
Ticking and unticking the option boxes impacts what is displayed in the results pane. All or some or none of the options may be used. However, the results may be difficult to understand, e.g., selecting only Status obfuscates the location of data:
In typical usage, either Name or Description will be selected with Value no matter the other display options.
Note that there are no dependencies, e.g., Description does not depend on Name.
Name
Name returns: PartitionID, Cube, Entity, Cons, Scenario, Time, View, Account, Flow, Origin, IC, UD1, UD2, UD3, UD4, UD5, UD6, UD7, UD8.
Description
Description returns: PartitionID, CubeD, EntityD, ConsD, ScenarioD, TimeD, ViewD, AccountD, FlowD, OriginD, ICD, UD1D, UD2D, UD3D, UD4D, UD5D, UD6D, UD7D, UD8D
ID
ID returns: PartitionID, CubeId, EntityId, ConsId, ScenarioId, TimeId, ViewId, AccountId, FlowId, OriginId, ICId, UD1Id, UD2Id, UD3Id, UD4Id, UD5Id, UD6Id, UD7Id, UD8Id
Status
Status returns: PartitionID, M1Status, M2Status, M3Status, M4Status, M5Status, M6Status, M7Status, M8Status, M9Status, M10Status, M11Status, M12Status
Value
Value returns: PartitionID, M1Value, M2Value, M3Value, M4Value, M5Value, M6Value, M7Value, M8Value, M9Value, M10Value, M11Value, M12Value
Consolidated Data
Consolidated Data returns consolidated data points; no additional columns are returned.
Compact View
Compact View compresses columns.
Standard
Compact
Memberscript Filter
The Memberscript filter, in concert with the Year Selector, defines the data range.
Given the Cube-centric nature of this Solution, a Cube name must always be defined, e.g., Cb#Houston.
Additional dimension filters act as either single member filters for base level members or as implicit .Base hierarchy methods for upper level ones. As an example, Cb#Houston:U1#Eng will return U1#Eng data in the Houston Cube. Cb#Houston:U1#Mfg will return U1#Dist, U1#Eng, U1#Logistics, etc.
The filter is manually entered.
Period Selector
Queries require both a defined Cube and a selected (or an explicitly defined Memberscript) year.
The multi-select nature of the year filter allows multiple year selects.
A Memberscript Time definition supports one year; that explicit definition can work in concert with the multiselector to return more than one year.
Execute
The Run button triggers the query.
Results
Query results are displayed in a standard OneStream TableView.
TableViews support filtering, grouping, and exporting.
No more than 5,000 records can be retrieved.
Filtering and Grouping
Member Filters
Filtering can be performed through unique results or via freeform queries.
Grouping
By dragging field names to the Results TableView header, items can be grouped by any of the visible fields.
Filtering by Flow and then grouping by U1 shows the following hierarchical groupings. Note that MatMgt is expanded.
Exporting
Data Explorer supports four export formats: Excel XML, csv, text (tab), and HTML:
Using Excel XML – likely the most commonly used format – right clicking on a row and selecting Export->To Excel XML launches the export process. Note that no more than 5,000 rows can be exported.
Once exported, right click on the filename and select Open With->Excel:
The export is automatically in Excel filter mode:
Administration Tasks
As noted in the Overview section of this document, access to this Solution must be tightly controlled because of its wide data scope.
Once installed, there are no settings.
Data Structures
This Solution uses three tables: BDA_FW_Solution_Keys, BDA_FW_Task_EditHistory, and BDA_FW_Task_Status.
BDA_FW_Solution_Keys
Solution key(s) for the relevant BDA Solutions.
Sample Data
Table Schema
BDA_FW_Task_EditHistory
Tasks in Task Editor with 10 generations of audit.
Sample Data
Table Schema
BDA_FW_Task_Status
Tracks completed task status when feature is in use
Sample Data
Task Schema
