{"id":40836,"date":"2025-09-03T03:10:48","date_gmt":"2025-09-03T08:40:48","guid":{"rendered":"https:\/\/www.solutionanalysts.com\/blog\/?p=40836"},"modified":"2025-09-03T03:16:52","modified_gmt":"2025-09-03T08:46:52","slug":"onestream-dimensions-for-finance","status":"publish","type":"post","link":"https:\/\/www.solutionanalysts.com\/blog\/onestream-dimensions-for-finance\/","title":{"rendered":"Unlocking the Power of OneStream Dimensions: Exploring the 18 Dimensions in Its Financial Model\u00a0"},"content":{"rendered":"

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.<\/span><\/p>\n

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!<\/span>\u00a0<\/span><\/p>\n

<\/span>What Are the OneStream Dimensions?<\/span><\/b>\u00a0<\/span><\/span><\/h2>\n

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:<\/span><\/p>\n

\u2022 System-Defined (Fixed, Non-Editable):<\/span><\/b> These are built-in and cannot be modified in purpose, ensuring consistency across applications (e.g., Origin and View).<\/span>\u00a0<\/span><\/p>\n

\u2022 Configurable (Editable):<\/span><\/b> These can be changed to meet the needs of your business (for example, Account, Entity).<\/span>\u00a0<\/span><\/p>\n

\u2022 User-Defined:<\/span><\/b> These are eight flexible dimensions (UD1# to UD8#) that you can name and organise based on your needs, like products, customers, or projects.<\/span>\u00a0<\/span><\/p>\n

Every OneStream cube – a multidimensional structure for storing, calculating, translating, and consolidating data\u2014incorporates 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.<\/span>\u00a0<\/span><\/p>\n

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.<\/span>\u00a0<\/span><\/p>\n

<\/span>The 18 OneStream Dimensions: A Comprehensive Breakdown<\/span><\/b>\u00a0<\/span><\/span><\/h2>\n

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.<\/span>\u00a0<\/span><\/p>\n

System-Defined Dimensions (Fixed)<\/span><\/b>\u00a0<\/span><\/p>\n

These provide foundational structure and cannot be edited.<\/span>\u00a0<\/span><\/p>\n

    \n
  1. Origin (O#):<\/span><\/b> Tracks the source of data, such as whether it’s imported, adjusted, or calculated. It is essential for audit trails and data integrity, helping trace entries back to their origins (for instance, manual journals versus automated loads).<\/span>\u00a0<\/span><\/li>\n
  2. View (V#):<\/span><\/b> Defines how data is viewed, such as Year-to-Date (YTD), Periodic, or annotations like footnotes and variances. It’s commonly used in reporting to switch between cumulative and incremental perspectives, including stored commentaries or attachments.<\/span>\u00a0<\/span><\/li>\n<\/ol>\n

    Configurable Dimensions (Editable)<\/span><\/b>\u00a0<\/span><\/p>\n

    These have predefined purposes but allow customization of members and hierarchies.<\/span>\u00a0<\/span><\/p>\n

      \n
    1. Entity (E#):<\/span><\/b> Represents organizational units, like subsidiaries, departments, or legal entities. It supports hierarchical structures for roll-ups and is key for consolidations across global operations.<\/span>\u00a0<\/span><\/li>\n
    2. Scenario (S#): <\/span><\/b>Differentiates data sets, such as Actual, Budget, Forecast, or What-If scenarios. It enables side-by-side comparisons and supports parent-child relationships for grouping (without consolidation).<\/span>\u00a0<\/span><\/li>\n
    3. Account (A#):<\/span><\/b> Structures your chart of accounts, including assets, liabilities, revenues, and expenses. It allows for dynamic calculations and is central to financial reporting.<\/span>\u00a0<\/span><\/li>\n
    4. Flow (F#)<\/span><\/b>: Captures movements in data, like opening balances, additions, disposals, or FX impacts. Often used for cash flow or balance sheet reconciliations, it’s customizable for specific tracking needs.<\/span>\u00a0<\/span><\/li>\n
    5. Intercompany (I#):<\/span><\/b> Manages transactions between entities, facilitating eliminations and matching. It’s crucial for accurate group reporting in multi-entity organizations.<\/span>\u00a0<\/span><\/li>\n
    6. Time (T#):<\/span><\/b> Handles periods like months, quarters, or years. It supports predefined (e.g., monthly\/weekly) or custom calendars, with options to vary descriptions by year or set custom start dates.<\/span>\u00a0<\/span><\/li>\n
    7. Consolidation (C#):<\/span><\/b> Supports aggregation and elimination processes, including members for local GAAP, IFRS adjustments, or parent adjustments. It’s vital for statutory consolidations.<\/span>\u00a0<\/span><\/li>\n
    8. Parent (P#):<\/span><\/b> Focuses on hierarchical relationships, often used for parent-child structures in consolidations or adjustments. It helps in modeling complex ownership scenarios.<\/span>\u00a0<\/span><\/li>\n<\/ol>\n

      User-Defined Dimensions<\/span><\/b>\u00a0<\/span><\/p>\n

      These eight dimensions (UD1# to UD8#) are fully customizable and have no predefined purposes. Organizations often label them based on needs, such as:<\/span><\/p>\n

      11-18. User Defined 1 to 8 (U1# to U8#): Examples include: <\/span><\/p>\n