Cube Term |
Definition |
|
A team member's role determines their access to functionality within the instance. The role is set, and the Owner maintains permissions. Team Member Types are defined as:
|
|
|
Cube’s web-based tool allows team members to create and manage dimensions and data sources and perform team management activities. See the Cube Portal overview. |
|
|
A record of team member activities and underlying details. |
|
|
Data from ERP, CRM, HRIS, Spreadsheets, or other sources which have been connected or published to Cube. Learn how to update Source Data. |
|
|
User-defined grouping of items such as regions, products, or departments. Dimensions are how one can “slice and dice” different data sets. Individual items are known as Dimension Members. Learn more about Dimensions. |
|
|
Cube Value |
A Cube Value refers to a piece of financial or operational data with associated metadata describing its precise cross-sections in an OLAP cube. Cube Values can only live at the intersection of lowest-level dimensions |
|
Rollup Value |
When calculating a value that summarizes multiple lowest-level dimensions (i.e., a value at a parent level), we call these values “rollups” They are not the lowest-level, granular Cube Values. Instead, they are summary values. We do not store these values in our database. They are calculated upon request, just in time. |
|
Chart of Accounts (COA) |
A chart of accounts is your company's formal structure of all dimensions in a hierarchy. A chart of accounts always includes the Account dimensions a company uses to categorize financial data. It often also includes other top-level dimensions like Departments to categorize data further. |
Types of Dimensions & Dimension-Related Terms |
|
|
Dimension Member |
A node or item which is part of a larger grouping of dimensions (i.e., the “Revenue” Account in the Account dimension). |
|
Parent |
A Dimension Member has one or more sub-members or “children” who roll up to it in a hierarchy. |
|
Leaf |
A child (non-parent / non-rollup) dimension member. |
|
Hierarchy |
The levels in which a dimension is stored / used. For example, Accounts receivable roll up to Current Assets, which roll up to total assets, which roll up to the Balance Sheet. Example: Account Balance Sheet Assets Current Assets Accounts Receivable |
|
Account |
A type of dimension which can refer to: General Ledger accounts such as Revenue, Expenses, etc. Custom Operational metrics or Drivers such as “Sales per Rep” or “Headcount” Formula or calculation accounts such as Gross Profit (Revenue - COGS), and Gross Margin (Gross Profit / Revenue) |
|
Department |
A top-level dimension is used to differentiate between functional units. |
|
A dimension that refers to the version of data being reviewed Examples: “Actuals”, “Budget”, “Forecast”, “Base Case”, “High Case” |
|
|
The unit of measure of financial periods, such as day, week, month, quarter, and year. Cube defaults to storing values in months, quarters, and years. |
|
|
Custom groupings of dimension members may differ from the hierarchy defined within the top-level dimension (for example, defining certain Accounts as “Fixed” vs. “Variable” expenses). |
|
|
Source Dimensions |
When you connect a third-party system to Cube, that system often already has a way to represent dimensions and classify information. We import that third-party system’s classification system as “source dimensions” with your hierarchy and structure. When you see the term “dimension,” it always refer to Cube dimensions from the company’s chart of accounts (i.e. the dimensions we use in our OLAP cube to analyze the data) When you see the term “source dimension,” it always refer to dimensions that we’ve imported from an external source that are unique to that external source (i.e., not the dimensions we use in our OLAP Cube) |
Comments
0 comments
Article is closed for comments.