Table of Contents
As finance professionals, we know that strong data organisation and analysis are key to good corporate performance management (CPM). OneStream is a top enterprise finance platform that stands out because it combines planning, budgeting, reporting, and consolidating finances in a single step. At the heart of OneStream’s architecture is its multidimensional cube structure, which supports exactly 18 OneStream dimensions. Because it is based on Extensible Dimensionality, this design lets businesses change their financial models while keeping the framework the same and scalable.
In this post, I’ll break down the 18 OneStream dimensions, drawing from official documentation and best practices. Understanding these core OneStream dimensions can transform how you handle complex financial data, whether you’re implementing the platform for the first time or optimizing an existing setup. Let’s dive in!
OneStream dimensions act like folders for organizing business data. Each dimension contains members (e.g., specific accounts or entities) that represent slices of your organization’s information. The platform categorizes these OneStream dimensions into:
• System-Defined (Fixed, Non-Editable): These are built-in and cannot be modified in purpose, ensuring consistency across applications (e.g., Origin and View).
• Configurable (Editable): These can be changed to meet the needs of your business (for example, Account, Entity).
• User-Defined: These are eight flexible dimensions (UD1# to UD8#) that you can name and organise based on your needs, like products, customers, or projects.
Every OneStream cube – a multidimensional structure for storing, calculating, translating, and consolidating data—incorporates all 18 OneStream dimensions. This fixed count makes it possible for dimensions to grow or shrink depending on situations, cubes, or reporting needs, all without changing the model itself.
Extensible Dimensionality is a game-changer for working with OneStream dimensions: it lets you add detail to dimensions (e.g., breaking out sub-accounts) for specific entities or scenarios, while keeping summary views simple. This adaptability lets different business units work together on a single platform, breaking down barriers and making things run more smoothly.
OneStream dimensions are referenced using tokens (e.g., A# for Account members). Below, I’ll list and explain each one, grouped by category for clarity. Note that while the total is fixed at 18, user-defined OneStream dimensions offer the most customization.
System-Defined Dimensions (Fixed)
These provide foundational structure and cannot be edited.
Configurable Dimensions (Editable)
These have predefined purposes but allow customization of members and hierarchies.
User-Defined Dimensions
These eight dimensions (UD1# to UD8#) are fully customizable and have no predefined purposes. Organizations often label them based on needs, such as:
11-18. User Defined 1 to 8 (U1# to U8#): Examples include:
By default, some implementations assign Flow to UD1, Intercompany to UD2, and Consolidation to UD3, but you can rename or reassign them. They support stored or dynamic calculations and are extensible for detailed breakdowns.
Category | Dimensions | Key Use Cases |
System-Defined | Origin (O#), View (V#) | Data sourcing, reporting views |
Configurable | Entity (E#), Scenario (S#), Account (A#), Flow (F#), Intercompany (I#), Time (T#), Consolidation (C#), Parent (P#) | Organizational structure, time-based analysis, consolidations |
User-Defined | UD1# to UD8# | Custom attributes like products, customers, or projects |
18 OneStream dimensions models offer unmatched flexibility without added complexity.
For example, a multinational company can use the Entity and Intercompany dimensions for global consolidations while extending user-defined dimensions for region-specific details—all within the same cube.
The 18 OneStream dimensions of OneStream enable finance leaders to create agile, future-proof models that align with their strategic goals. If you’re looking into CPM solutions or already using OneStream, fully utilizing these dimensions can lead to transformative results.
Jay Ghediya
Senior Software Engineer
Results-driven Senior Software Engineer with expertise in JavaScript/TypeScript across front-end and back-end. Experienced in delivering high-performance solutions in Fintech, Healthcare, Education, Task Management, and ERP, with a strong focus on aligning technical excellence with business needs.
Get free consultation and let us know your project idea to turn
it into an amazing digital product.