D365 F&O: Custom Operating Unit Types (Division, Region, Zone)

Problem Statement

1. Limited Hierarchy Options: Standard D365 F&O does not provide Division, Region, or Zone as built-in operating unit types
2. Dimensional Reporting Gaps: Cannot easily report on geographic or divisional profitability without workarounds
3. Transaction Dimensioning: Cannot use custom organizational structures in financial dimension hierarchies
4. Data Integration Issues: No native Excel or DMF support for importing/exporting custom organizational structures
5. Workaround Overhead: Forced to create redundant dimensions, duplicate hierarchies, or implement complex customizations

• A multi-division enterprise wants to report divisional P&L
• A geographic company needs regional performance analysis
• A zone-based distributor requires zone-level transaction tracking
• Without native support, all of this requires complex customizations and workarounds

Solution Overview

1. Division - For organizational division structures
2. Operating Region - For geographic region organization
3. Zone - For zone-based operations

• Enum Extension - Extends OMOperatingUnitType with new values
• Data Entities - Enable Excel add-in and DMF integration
• Staging Tables - Support bulk import/export operations
• Menu Items - Provide user interface access
• Dimension Views - Make custom types available in Chart of Accounts

Architecture & Components

Enum Extension (OMOperatingUnitType)
        ↓
Data Entities (Fox_OMDivisionEntity, Fox_OMOperatingRegionEntity, Fox_OMZoneEntity)
        ↓
Staging Tables (Fox_OMDivisionStaging, Fox_OMOperatingRegionStaging, FoxOMZoneStaging)
        ↓
Menu Items (Fox_OMDivision, Fox_OMOperatingRegion, Fox_OMZone)
        ↓
Dimension Views (Fox_DimAttributeOMDivisionView, Fox_DimAttributeOMOperatingRegionView, Fox_DimAttributeOMZoneView)

"Custom operating unit types extend D365 F&O's organizational capabilities without disrupting standard functionality."

Step 1: Enum Extension - Define Operating Unit Types

Creating the Enum Extension

• Consistency across the system
• Proper multilingual support (labels stored in label files)
• Alignment with standard D365 terminology

Step 2: Data Entities - Enable Excel and DMF Integration

• Excel add-in functionality for end-user access
• Data Management Framework (DMF) bulk import/export
• OData API access for integrations
• Change tracking for incremental updates

Creating Data Entities in Visual Studio

1. Name: Fox_OMDivisionEntity
2. Primary Data Source: OMOperatingUnit table
3. In Properties:
   • Label: @SYS40992 (Division label)
   • IsPublic: Yes
   • DataManagementEnabled: Yes
   • DataManagementStagingTable: Fox_OMDivisionStaging
   • PublicCollectionName: Divisions
   • PublicEntityName: Division

Adding Methods to Fox_OMDivisionEntity

x++Copy
/// <summary>
/// Registers this entity with the Office menu items system
/// Makes it available in Excel add-in and on the OMOperatingUnit form
/// </summary>
[SubscribesTo(classStr(OMOperatingUnitEntityDelegates), delegateStr(OMOperatingUnitEntityDelegates, registerOperatingUnitEntities))]
public static void registerDivisionEntity(List _entityList)
{
    _entityList.addEnd(tableStr(Fox_OMDivisionEntity));
}

• Uses the SubscribesTo attribute to subscribe to the registerOperatingUnitEntities delegate
• When OMOperatingUnit form initializes, this method is automatically called
• Adds the Division entity to the list of available Office menu items
• Users can then access the entity via Excel add-in without any additional configuration

x++Copy
/// <summary>
/// Change tracking query for DMF incremental updates
/// Identifies changed Division operating units since last export
/// </summary>
/// <returns>Query that represents Division data sources</returns>
public static Query defaultCTQuery()
{
    Query q = new Query();

    // Root data source: DirPartyTable (party master records)
    QueryBuildDataSource dirPartyQBDS = q.addDataSource(tableNum(DirPartyTable));
    dirPartyQBDS = DirPartyBaseEntity::addChangeTrackingDataSourcesForDirPartyChildren(dirPartyQBDS);

    // Add postal address change tracking
    LogisticsPostalAddressBaseEntity::addChangeTrackingDataSourcesForAddressBase(
        dirPartyQBDS, 
        fieldNum(DirPartyTable, PrimaryAddressLocation), 
        false
    );

    // Join to OMOperatingUnit and filter by Division type
    QueryBuildDataSource qbdOMOperatingUnit = dirPartyQBDS.addDataSource(tableNum(OMOperatingUnit));
    qbdOMOperatingUnit.addLink(fieldNum(DirPartyTable, PartyNumber), fieldNum(OMOperatingUnit, PartyNumber));
    
    // CRITICAL: Filter to only Division type operating units
    qbdOMOperatingUnit.addRange(fieldNum(OMOperatingUnit, OMOperatingUnitType))
        .value(queryValue(OMOperatingUnitType::OMDivision));

    // Add DUNS number tracking (standard for operating units)
    QueryBuildDataSource qbdDunNumber = qbdOMOperatingUnit.addDataSource(tableNum(DirDunsNumber));
    qbdDunNumber.addLink(fieldNum(OMOperatingUnit, DunsNumberRecId), fieldNum(DirDunsNumber, RecId));

    return q;
}

• Only exports changed records since last run
• Significantly reduces export file size
• Improves performance for large datasets
• Essential for high-frequency data synchronization

Operating Region Entity

• Label: @SYS109262 (Region label)
• DataManagementStagingTable: Fox_OMOperatingRegionStaging
• PublicCollectionName: Regions
• PublicEntityName: Region

• registerOperatingRegionEntity() - Same pattern as Division, but registers Fox_OMOperatingRegionEntity
• defaultCTQuery() - Same structure as Division, but change the range filter:

  x++Copy
  qbdOMOperatingUnit.addRange(fieldNum(OMOperatingUnit, OMOperatingUnitType))
      .value(queryValue(OMOperatingUnitType::OMOperatingRegion));

Zone Entity

• Label: @WAX:FieldZone (Zone label)
• DataManagementStagingTable: Fox_OMZoneStaging
• PublicCollectionName: Zones
• PublicEntityName: Zone

• registerZoneEntity() - Same pattern as Division, but registers Fox_OMZoneEntity
• defaultCTQuery() - Same structure as Division, but change the range filter:

  x++Copy
  qbdOMOperatingUnit.addRange(fieldNum(OMOperatingUnit, OMOperatingUnitType))
      .value(queryValue(OMOperatingUnitType::OMZone));

Data Entity Configuration Summary

• SubscribesTo Delegate: Registers entity in Office menus automatically
• defaultCTQuery(): Enables change tracking for efficient DMF operations
• DataManagementEnabled: Allows bulk import/export
• DataManagementStagingTable: Links to corresponding staging table
• PublicCollectionName/EntityName: OData naming for API access
• IsPublic: Yes (makes visible in Data Management workspace)

Step 3: Staging Tables - DMF Support

Adding Staging Tables methods

1. Name: Fox_OMDivisionStaging
2. In Properties:
   • TableGroup: Staging
   • SaveDataPerCompany: No (shared across all companies)
   • PrimaryIndex: StagingIdx
   • ReplacementKey: StagingIdx

mapDivisionStaging() Method

x++Copy
/// <summary>
/// Maps Division staging records to operating units
/// Validates data and transfers to OMOperatingUnit on successful validation
/// </summary>
public static void mapDivisionStaging()
{
    Fox_OMDivisionStaging staging;
    OMOperatingUnit operatingUnit;
    
    // Select unprocessed records
    select forUpdate staging
        where staging.IsProcessed == NoYes::No;
    
    while (staging)
    {
        // Create new operating unit
        operatingUnit.clear();
        operatingUnit.OMOperatingUnitNumber = staging.OMOperatingUnitNumber;
        operatingUnit.Name = staging.Name;
        operatingUnit.OMOperatingUnitType = OMDivision;
        operatingUnit.insert();
        
        // Mark as processed
        staging.IsProcessed = NoYes::Yes;
        staging.TransferStatus = TransferStatus::Successful;
        staging.update();
        
        next staging;
    }
}

1. DMF validates staging table records
2. mapDivisionStaging() executes on marked records
3. Data transfers to OMOperatingUnit with OMDivision type
4. Staging records marked as "Processed" and "Successful"

Operating Region Staging Table

• TableGroup: Staging
• SaveDataPerCompany: No
• Add same fields: OMOperatingUnitNumber, Name, IsProcessed, TransferStatus

x++Copy
operatingUnit.OMOperatingUnitType = OMOperatingRegion;  // Instead of OMDivision

Zone Staging Table

• TableGroup: Staging
• SaveDataPerCompany: No
• Add same fields: OMOperatingUnitNumber, Name, IsProcessed, TransferStatus

x++Copy
operatingUnit.OMOperatingUnitType = OMZone;  // Instead of OMDivision

Staging Table Configuration Summary

• TableGroup: Must be "Staging" (indicates DMF staging table)
• SaveDataPerCompany: No (shared across all companies)
• PrimaryIndex/ReplacementKey: StagingIdx (standard DMF pattern)

1. User imports CSV/Excel data using Data Management workspace
2. Data loads into staging tables (Fox_OMDivisionStaging, Fox_OMOperatingRegionStaging, Fox_OMZoneStaging)
3. User reviews data in staging forms for corrections
4. Mapping execution calls mapDivisionStaging(), mapOperatingRegionStaging(), mapZoneStaging()
5. Data validates against business rules
6. Valid records transfer to OMOperatingUnit with correct type
7. Staging records marked as "Processed" for audit trail

• ✓ Separation of concerns (Division/Region/Zone can be imported separately)
• ✓ Audit trail maintained in staging tables
• ✓ Data validation before production insert
• ✓ Rollback capability if errors detected

Step 4: Menu Items - User Interface Access

Creating Menu Items

1. Name: Fox_OMDivision
2. In Properties:
   • Label: @SYS40992 (Division label)
   • Object: OMOperatingUnit (the form to open)
   • EnumParameter: OMDivision (from your enum extension)
   • EnumTypeParameter: OMOperatingUnitType (the enum type)
   • MaintainUserLicense: Enterprise
   • ViewUserLicense: Universal

How the Menu Item Works:

• EnumParameter value filters records in OMOperatingUnit form to show only Division type
• MaintainUserLicense determines who can create/edit Divisions
• ViewUserLicense determines who can view Divisions (usually broader)
• When user clicks "Division" menu item, D365 opens OMOperatingUnit form pre-filtered to Division type

Operating Region Menu Item

• Label: @SYS109262 (Region label)
• EnumParameter: OMOperatingRegion (instead of OMDivision)

Zone Menu Item

• Label: @WAX:FieldZone (Zone label)
• EnumParameter: OMZone (instead of OMDivision)

Menu Item Integration in Navigation

1. Navigate to View → Application Explorer
2. Search for Organization Administration menu
3. Right-click → Edit → Add Menu Items
4. Add Fox_OMDivision, Fox_OMOperatingRegion, Fox_OMZone

Organization Administration
├─ Setup
│  ├─ Organization
│  │  ├─ Division [Fox_OMDivision]
│  │  ├─ Operating Region [Fox_OMOperatingRegion]
│  │  └─ Zone [Fox_OMZone]

• ✓ Intuitive user interface with separate menus for each level
• ✓ Licensing enforces data modification restrictions
• ✓ Seamless integration with OMOperatingUnit form
• ✓ No custom forms required - reuses standard D365 forms
• ✓ Single form with enum filtering = minimal maintenance

Step 5: Dimension Views - Financial Dimensioning

Creating Dimension Views in Visual Studio

1. Name: Fox_DimAttributeOMDivisionView
2. Primary Data Source: OMOperatingUnit
3. In Properties:
   • Label: @SYS40992 (Division label)
   • SingularLabel: @SYS40992
   • TitleField1: OMOperatingUnitNumber
   • TitleField2: Name

Dimension View Data Sources Configuration

1. Add OMOperatingUnit as primary data source
2. Add DirPartyTable as related data source
   • Relation: Join on RecId
   • Purpose: Retrieves organization name for display
3. Add a Range Filter on OMOperatingUnit:
   • Field: OMOperatingUnitType
   • Value: OMDivision (your custom enum value)
   • Purpose: Only shows Division type units

registerDimensionEnabledTypeIdentifier() Method

x++Copy
/// <summary>
/// Registers this view as a dimension-enabled type
/// Makes Division operating units available in Chart of Accounts structure
/// </summary>
[SubscribesTo(classstr(DimensionEnabledType), delegatestr(DimensionEnabledType, registerDimensionEnabledTypeIdentifiersDelegate))]
public static void registerDimensionEnabledTypeIdentifier(DimensionIEnabledType _dimensionEnabledType)
{
    _dimensionEnabledType.registerViewIdentifier(tablestr(Fox_DimAttributeOMDivisionView));
}

• Subscribes to the registerDimensionEnabledTypeIdentifiersDelegate on application startup
• Registers the view as a dimension-enabled type
• D365 automatically makes this view available when configuring account structures
• Users can then add Division as a segment in Chart of Accounts without any additional setup

• ✓ Automatic discovery by D365 framework
• ✓ No manual configuration needed
• ✓ Works with all standard accounting features
• ✓ Enables transaction-level dimensioning

Add View Fields

Add Indexes for Performance

• Field: Value (OMOperatingUnitNumber)
• Purpose: Fast code lookup when users type a dimension value
• AllowDuplicates: No

• Field: Name
• Purpose: Fast lookup by organization name in dropdowns
• AllowDuplicates: Yes

Operating Region Dimension View

• Label: @SYS109262
• Range Filter: Set OMOperatingUnitType = OMOperatingRegion

• registerDimensionEnabledTypeIdentifier() - Same pattern, register Fox_DimAttributeOMOperatingRegionView
• Fields: Key, Value, Name (same as Division)
• Indexes: ValueIdx, NameIdx (same as Division)

Zone Dimension View

• Label: @WAX:FieldZone
• Range Filter: Set OMOperatingUnitType = OMZone

• registerDimensionEnabledTypeIdentifier() - Same pattern, register Fox_DimAttributeOMZoneView
• Fields: Key, Value, Name (same as Division)
• Indexes: ValueIdx, NameIdx (same as Division)

Dimension Views Summary

1. Each view registers itself on application startup
2. D365 discovers all dimension-enabled views automatically
3. Users can add Division/Region/Zone to Chart of Accounts structures
4. Journal entries can then use Division, Region, Zone codes as dimension values
5. Dimension values are looked up using the view fields (Value, Name)
6. Indexes ensure fast performance even with large datasets

• ValueIdx ensures fast code lookup (typical user entry path)
• NameIdx ensures fast name lookup (dropdown searches)
• Both indexes optimized for the specific enum type
• No cross-table scans needed for dimension lookups

Deployment & Configuration

Build the Solution

Creating Operating Units

1. Click New
2. Enter the operating unit name (e.g., "Sales Division", "North America", "East Zone")
3. Enter the operating unit number (e.g., "DIV-001", "REG-NA", "ZONE-E")
4. Configure address and party information
5. Save the record

Configuring Financial Dimensions

1. Click New
2. Add a segment:
   • Select Fox_DimAttributeOMDivisionView (or Region/Zone)
   • The view will appear in the dropdown automatically
3. Define account structure rules
4. Activate the structure

Benefits & Business Value

Organizational Flexibility

• Structure organizations exactly as needed without artificial constraints
• Support complex geographic hierarchies or divisional models
• Enable matrix organizations with multiple dimension options

Financial Reporting

• Multi-level organizational reporting by Division, Region, or Zone
• Flexible cost center and profit center analysis
• Geographic performance tracking

Operational Efficiency

• Native Excel bulk operations via add-in
• Standard DMF framework for data integration
• No custom workarounds or redundant dimensions

System Consistency

• Uses standard D365 patterns and conventions
• Integrates seamlessly with existing organization hierarchy
• Maintains data integrity and audit trails

Conclusion