Study guide
4.1 Dimension Concepts & Dimension Values
Microsoft Dynamics 365 Business Central Functional Consultant MB-800
Track your progress as you read
Finished sections get a check mark.
1 Chapter 1: Company Creation & Data Migration
1.1 Creating Companies & Assisted Setup Wizards 1.2 Configuration Packages & RapidStart Worksheets 1.3 Opening Balances & Data Migration Strategies
2 Chapter 2: Security, Profiles & Auditing
2.1 Users, User Setup & Role Center Profiles 2.2 Permission Sets & Security Group Management 2.3 Security Filters, Change Log & Security Auditing
3 Chapter 3: Core System Configuration, Number Series & Copilot
3.1 Company Information, Number Series & Job Queues 3.2 Report Layout Management & Copilot AI Capabilities
4 Chapter 4: Dimensions Architecture & Governance
4.1 Dimension Concepts & Dimension Values 4.2 Global Dimensions vs Shortcut Dimensions 4.3 Default Dimensions, Combinations & Priorities
5 Chapter 5: Workflows & Approvals
5.1 Native Workflow Templates & Approval Hierarchy 5.2 Workflow User Groups & Notification Configuration
6 Chapter 6: Financial Setup, Periods & Currencies
6.1 General Ledger Setup & Accounting Periods 6.2 Payment Terms, Payment Methods & Deferrals 6.3 Multi-Currency Setup & Exchange Rates
7 Chapter 7: Chart of Accounts, Categories & Allocations
7.1 Chart of Accounts Structure & G/L Account Cards 7.2 Account Categories, Subcategories & Financial Reporting 7.3 General Ledger Allocation Accounts & Sharing
8 Chapter 8: Posting Groups & Posting Setup
8.1 Specific Posting Groups: Customer, Vendor, Bank & Inventory 8.2 General Posting Groups & General Posting Setup Matrix 8.3 Inventory Posting Setup & Alternative Posting Groups
9 Chapter 9: General Journals & Recurring Methods
9.1 Bank Account Cards & Posting Setup 9.2 General Journal Templates, Batches & Number Series 9.3 Recurring General Journals & Allocation Methods
10 Chapter 10: Accounts Payable & Accounts Receivable Setup
10.1 Purchases & Payables Setup & Vendor Master 10.2 Sales & Receivables Setup & Customer Master 10.3 Payment Journals, Cash Receipts & Payment Registration Setup
11 Chapter 11: Fixed Assets Setup & Depreciation Books
11.1 Fixed Asset Setup, Classes & Depreciation Books 11.2 Fixed Asset Cards, Main/Component Assets & Depreciation Methods
12 Chapter 12: Inventory Setup, Costing & Locations
12.1 Inventory Setup, Item Types, Categories & Variants 12.2 Costing Methods (FIFO, LIFO, Average, Standard) & Ledger Architecture 12.3 Locations, Transfer Routes & Stockkeeping Units (SKUs)
13 Chapter 13: Logistics Master Data, Pricing & Discounts
13.1 Shipping Agents, Locations & Vendor Lead Times 13.2 Sales Prices, Purchase Prices & Price Lists 13.3 Line Discounts, Invoice Discounts & Thresholds
14 Chapter 14: User Interface, Views, Inspection & Excel
14.1 Personalization, Profile Customization & Designer 14.2 Searching, Advanced Filters, Saved Views & Page Inspection 14.3 Edit in Excel, OneDrive & Data Analysis Mode
15 Chapter 15: Purchase & Sales Order Execution
15.1 Purchase Orders, Receiving, Over-Receipt & Undo 15.2 Purchase Invoicing, Recurring Lines & Blanket Orders 15.3 Sales Quotes, Availability Checks & Order Conversion 15.4 Sales Shipping, Invoicing, Undo & Blanket Orders
16 Chapter 16: Invoices, Credit Memos & Document Corrections
16.1 Direct Invoices, Credit Memos & Document Reopening 16.2 Correct, Cancel & Corrective Credit Memo Procedures 16.3 Combined Shipments/Receipts & Prepayment Workflows
17 Chapter 17: Cash Management, Bank Reconciliation & Ledger Applications
17.1 Processing Payment Journals & Cash Receipt Registrations 17.2 Applying, Unapplying & Reversing Customer/Vendor Entries 17.3 Bank Account Reconciliation & Statement Matching Rules
18 Chapter 18: Operational Adjustments, Inventory & Asset Accounting
18.1 Exchange Rate Adjustments & Dimension Corrections 18.2 Inventory Adjustments, Transfers & Physical Counting 18.3 Fixed Asset Acquisitions, Depreciation Runs & Disposals
4.1 Dimension Concepts & Dimension Values
Key Takeaways Explain This Topic AI
Dimensions provide a multi-dimensional analysis framework in Business Central that tags transactions with operational parameters, eliminating the need for rigid, bloated segmented charts of accounts.
Dimension Values support five structural types: Standard (posting allowed), Heading (organizational header), Total (rollup via formula), Begin-Total (starts indented group), and End-Total (terminates group and sums values).
The Indent Dimension Values automated routine calculates hierarchy indentation and automatically populates totaling formulas for all End-Total lines based on their matching Begin-Total brackets.
Enterprise multi-entity consolidation utilizes Consolidation Code and Map-to Dimension Value fields to automatically translate subsidiary dimensions into standardized parent reporting dimensions.
Dimension Translations allow multinational organizations to localize dimension names and value descriptions across multiple user client languages without duplicating dimensional structures.
Last updated: September 2026
4.1 Dimension Concepts & Dimension Values
Exam Focus: The MB-800 exam tests your ability to design and implement dimensions and dimension values, establish hierarchical rollups, execute the Indent Dimension Values function, configure totaling filters, map subsidiary dimensions for consolidation, and configure translations. Understanding how dimensions flow across ledgers without cluttering the Chart of Accounts is fundamental to Business Central financial consulting.
In modern enterprise resource planning (ERP) systems, financial reporting requires analyzing operational performance across multiple perspectives—such as operating department, geographic region, customer segment, or project code. Historically, legacy accounting packages achieved this through segmented account numbers, leading to unwieldy charts of accounts. Microsoft Dynamics 365 Business Central solves this challenge through its Dimensional Analysis Architecture .
1. Dimensional Analysis Architecture vs. Segmented Chart of Accounts
In older legacy accounting architectures, tracking operational segments required building account strings that concatenated natural accounts with organizational sub-codes. For example: Legacy Segmented Account Structure:
Natural Account (6100) - Department (10) - Project (200) - Area (EU) -> 6100-10-200-EU
If an enterprise operated 300 natural general ledger accounts across 15 departments, 40 projects, and 5 geographic regions, maintaining this rigid segmented structure required creating and maintaining up to: Total Accounts = 300 × 15 × 40 × 5 = 900 , 000 individual G/L accounts \text{Total Accounts} = 300 \times 15 \times 40 \times 5 = 900,000 \text{ individual G/L accounts} Total Accounts = 300 × 15 × 40 × 5 = 900 , 000 individual G/L accounts
This combinatorial explosion created severe administrative overhead, corrupted trial balance reporting, and made adding a new project or department an arduous IT project.
The Business Central Dimensional Model
Dynamics 365 Business Central separates the natural account from its operational attributes :
The Chart of Accounts contains only pure natural accounts (e.g., 61100 Travel Expenses , 40100 Product Sales , 10100 Operating Checking ).
Operational, geographic, and managerial classifications are defined independently as Dimensions (e.g., DEPARTMENT , PROJECT , CUSTOMERGROUP , AREA ).
When transactions occur on documents or journals, dimensional tags are assigned to transaction lines. Upon posting, these tags flow directly into underlying ledger tables:
- Table 17 G/L Entry
- Table 21 Cust. Ledger Entry
- Table 25 Vendor Ledger Entry
- Table 32 Item Ledger Entry
- Table 169 Job Ledger Entry (Project Ledger Entry)
Table 271 Bank Account Ledger Entry Dimensional Analysis Flow:
- Sales Invoice Line
- ├── G/L Account: 40100 (Product Sales)
- ├── Amount: $5,000.00
- └── Dimension Tags: [DEPT = SALES] [AREA = NA] [CUSTOMERGROUP = ENTERPRISE]
- │
- ▼ Posting Routine (Codeunit 80 / 12)
- Table 17: G/L Entry
- ├── Entry No.: 10452
- ├── G/L Account No.: 40100
- ├── Amount: -$5,000.00
- ├── Global Dimension 1 Code: SALES
- ├── Global Dimension 2 Code: NA
- └── Dimension Set ID: 4892 (Contains CUSTOMERGROUP = ENTERPRISE)
This architectural decoupling keeps the Chart of Accounts streamlined, allows dynamic ad-hoc slicing and dicing of financial statements, and permits adding new departments or projects instantly without altering general ledger account structures.
2. Setting Up Dimensions (Dimensions Page)
Dimensions represent the overarching categories used for tracking and analysis. To create and manage dimensions, navigate to the Dimensions page ( Page 560 ). UI Navigation Path:
Tell Me (Alt+Q) -> Dimensions -> Action Bar: New
Field Name Data Type / Constraint Functional Purpose & System Behavior
Code Code [20] The unique, immutable uppercase alphanumeric identifier for the dimension (e.g., DEPT , PROJECT , BUSINESSGROUP , TERRITORY ).
Name Text [30] The user-friendly descriptive name displayed on page lookups, cards, and reports (e.g., Department , Project Code , Customer Territory ).
Code Caption Text [80] Custom caption displayed in column headers when the dimension appears on document lines and ledger pages.
Filter Caption Text [80] Custom label displayed on report request pages and filtering panes when filtering by this dimension.
Description Text [100] Internal administrative documentation outlining governance rules and usage policies for the dimension.
Note
While Business Central allows creating an unlimited number of dimensions, best practices recommend limiting active operational dimensions to between 4 and 10. Excessive dimensions increase user data-entry overhead and can slow transaction processing if not strictly governed.
3. Dimension Values Architecture & Hierarchy
Once a Dimension is defined, consultants define its specific Dimension Values —the granular operational codes assigned to transactions. To access dimension values, select a dimension on the Dimensions page and choose Dimension Values ( Page 537 ). UI Navigation Path:
Tell Me (Alt+Q) -> Dimensions -> Select Record -> Related -> Dimension -> Dimension Values
Each Dimension Value record includes:
Dimension Value Code : Code [20] (e.g., ADM , PROD , SALES , MKTG ).
Name : Text [50] (e.g., Administration , Production , Sales & Marketing ).
Dimension Value Type : Determines structural behavior and posting eligibility.
Totaling : Filter expression defining rollup ranges.
Indentation : Visual indentation level calculated automatically.
Blocked : Boolean toggle preventing selection on new documents while preserving historical reporting.
Consolidation Code : Alternate code used during financial consolidation into a parent company.
The Five Dimension Value Types
Business Central provides five distinct Dimension Value Types that mirror the structural design of the Chart of Accounts:
Dimension Value Type Direct Posting Allowed? Requires Totaling Formula? UI Appearance Functional Role & Operational Behavior
Standard Yes No Normal text The standard operational posting value. Used directly on documents, journals, and master records. Carries historical ledger transactions.
Heading No No Bold text Non-posting organizational label used to group related dimension values in drop-down lists and financial report pickers.
Total No Yes Bold text Summary rollup value. Sums an explicit list or non-contiguous range of dimension values defined manually in the Totaling field (e.g., 100|120|150 ).
Begin-Total No No Normal text Marks the opening bracket of an indented hierarchical group of dimension values. Does not accept transactions.
End-Total No Yes Bold text Marks the closing bracket of an indented group. Totals all dimension values between the matching Begin-Total and End-Total .
The Indent Dimension Values Routine
To establish a clean visual hierarchy and automate totaling ranges:
Create a Begin-Total record (e.g., Code 100 , Name Commercial Operations ).
Create one or more Standard records (e.g., Code 110 Sales , Code 120 Marketing ).
Create an End-Total record (e.g., Code 199 , Name Total Commercial Operations ).
On the action bar, choose Actions > Functions > Indent Dimension Values . Indent Dimension Values Execution:
- [Action: Indent Dimension Values]
- │
- ├── 1. Evaluates matching Begin-Total and End-Total pairs
- ├── 2. Calculates nested Indentation levels (0 -> 1 -> 2)
- └── 3. Automatically populates End-Total Totaling field with range (e.g., '100..199')
Important
If you add, delete, or renumber dimension values within an existing group, Business Central does not dynamically update the Totaling field on the End-Total record. You must manually re-run the Indent Dimension Values action to recalculate indentation levels and update the totaling formulas.
4. Totaling Formulas & Rollup Logic in Financial Reporting
Totaling formulas on Total and End-Total dimension values use Business Central's native filter syntax to consolidate multiple operational centers into higher-level managerial reporting tiers:
Contiguous Range ( .. ): 1000..1999 includes all dimension value codes lexicographically between 1000 and 1999.
Union / Selection ( | ): 1100|1200|1500 sums specifically those three distinct operational codes.
Compound Combination: 1000..1500|1800..1900 sums both contiguous ranges into a single consolidated rollup.
Exclusion ( .. with <> ): 1000..1999&<>1500 includes all codes in the range except code 1500.
Impact on Downstream Reporting
These totaling rollups directly empower:
Financial Reports (Account Schedules): Row and column definitions can filter by Total or End-Total dimension codes, allowing executive summary reports (such as "Consolidated Commercial Expense") to display rolled-up balances without querying every child code individually.
Analysis Views: Multi-dimensional OLAP-style cubes aggregate transactional data using dimension totaling structures, accelerating high-volume data retrieval.
Chart of Accounts FlowFilters: Filtering the Chart of Accounts list by a Total dimension value aggregates Net Change and Balance at Date across all underlying operational centers.
5. Enterprise Capabilities: Consolidation Mapping & Translations
In complex, multinational environments, Business Central provides native mechanisms to handle cross-company rollups and multi-lingual user bases.
Multi-Company Consolidation Code Mapping
When consolidating decentralized subsidiary companies into a corporate holding entity, subsidiaries often operate localized dimension structures that differ from corporate reporting standards:
Scenario: Subsidiary A uses Department code SALES-DOM , while the corporate parent uses 100-COMM .
Solution: On Subsidiary A's SALES-DOM Dimension Value card, enter 100-COMM in the Consolidation Code field.
When the parent company runs the Import Consolidation from Database or Import Consolidation from File routine, Business Central automatically translates SALES-DOM into 100-COMM in the consolidated general ledger.
Similarly, the Map-to Dimension and Map-to Dimension Value fields in G/L Account mapping allow organizations to reclassify operational segments during intercompany data synchronization.
Multi-Language Dimension Translations
Global enterprises operating across different language regions require dimension names and value descriptions to display in each user's local language:
Open the Dimensions page, select the dimension, and choose Related > Dimension > Translations .
Select the Language Code (e.g., DEU for German, ESN for Spanish, FRA for French) and enter the localized translation for the dimension name.
Repeat the process on the Dimension Values page by choosing Related > Dimension Value > Translations .
When a user logs into Business Central with their client language set to French ( FRA ) in My Settings , the system dynamically renders the French captions on document lines, general journals, and financial reports, eliminating language barriers across international subsidiaries.
6. Common Implementation Pitfalls & Exam Traps
Pitfall 1: Attempting to Post to Begin-Total or End-Total Values. Users frequently attempt to select an End-Total value (e.g., Total Commercial ) on a journal line. Business Central immediately blocks posting with the error: "You cannot post to Dimension Value [Code] because Dimension Value Type is End-Total." Only Standard dimension values can receive postings.
Pitfall 2: Renumbering Values Without Re-Indenting. Adding a new sales department (e.g., 125 Marketing Digital ) between 100 and 199 without re-running Indent Dimension Values leaves the Totaling formula on 199 End-Total unchanged (e.g., still reading 110..120 ). Financial reports filtering on 199 will omit the new department's expenses.
Pitfall 3: Blocking a Dimension vs. Blocking a Dimension Value. Setting the Blocked toggle on the Dimension header blocks the entire dimension across all records globally. Setting Blocked on a specific Dimension Value prevents users from selecting only that specific obsolete code (e.g., a closed branch office) while allowing the rest of the dimension to function normally.
Pitfall 4: Deleting Historical Dimension Values. Deleting a dimension value that has historical ledger entries corrupts dimensional reporting and causes FlowFilter errors. Instead of deleting, consultants must set Blocked = Yes .