BDA Stage Data Explorer
Application Summary
The BDA Stage Data Explorer browses Stage data by Workflow Import Children or Data Sources.
BDA Stage Data Explorer Overview
The BDA Stage Data Explorer browses Stage data in a code-free interface by Workflow Import Children as well as Fixed and Delimited text files, SQL Connectors, and Data Management Export Sequences Data Source types.
Multiple Data Sources/Workflows can be selected and, so long as their scope is different, their output is merged into a single table view. Overlapping Workflow Import Children and their Data Sources can be simultaneously selected but will not result in a doubled record count.
Developers, administrators, and – potentially – selected FP&A superusers, can browse Stage data. Note that Workflow, Entity, and Cube Access security does not apply; Access to this utility must 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 Stage Data Explorer
OneStream Stage Data is stored in 24 tables and views that drive core Stage data, audit history, Stage metadata, and more. Stitching these normalized tables for review in a denormalized fashion requires an understanding of table layout, purpose, and common fields, creating custom SQL to perform these transformations, and a user interface.
The BDA Stage Data Explorer presents Stage Data in a code-free Dashboard with selectors for Scenario, Time, and Data Source.
The Stage Data Explorer Dashboard
Scenario
To explore the data, select a Scenario:
Period
Select a Period, which can either be by year or individual period :
Sources
One or many Sources may be selected. Where their Scenario and Period values match, they will be displayed together, identified by the Source field.
When Workflow Import Children coincide with Data Sources, e.g., Houston.Import and HoustonActual, Stage data is not replicated.
Browse Stage Data
Load and Transformed Data and Metadata
Stage data is presented in a fully denormalized fashion, showing source and target values. These are the result of whatever Transformation Rule is associated with the Data Source/Workflow Import Profile Child.
| Field name | Purpose |
|---|---|
| RawAmount | Source data value |
| ConvertedAmount | Transformed data value |
| Source | Workflow/Data Source |
| Source Entity | Source dimension value |
| Target Entity | Target dimension value |
| Source Time | Source dimension value |
| Target Time | Target dimension value |
| Source Account | Source dimension value |
| Target Account | Target dimension value |
| Source Flow | Source dimension value |
| Target Flow | Target dimension value |
| Source ICP | Source dimension value |
| Target ICP | Target dimension value |
| Source U1 | Source dimension value |
| Target U1 | Target dimension value |
| Source U2 | Source dimension value |
| Target U2 | Target dimension value |
| Source U3 | Source dimension value |
| Target U3 | Target dimension value |
| Source U4 | Source dimension value |
| Target U4 | Target dimension value |
| Source U5 | Source dimension value |
| Target U5 | Target dimension value |
| Source U6 | Source dimension value |
| Target U6 | Target dimension value |
| Source U7 | Source dimension value |
| Target U7 | Target dimension value |
| Source U8 | Source dimension value |
| Target U8 | Target dimension value |
| Fs | Sign flip |
Time Ranges
The Period combobox displays all periods in Stage data across all Data Sources, potentially resulting in queries that return no data, e.g., Valencia.Import does not contain 2010M1 data (it does contain 2010M12), resulting in a null result set:
A full year retrieve pulls – up to the 5,000 record limit – all months in that year.
Filtering and Grouping
Field 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 Target Entity and the grouping by Target Account creates the following result set:
Export
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
