Account Dimension Relations

Account Dimension Relations are a critical component of the Municipal Financial Management System that define and control which dimension combinations are allowed for specific G/L accounts, ensuring data integrity and proper financial classification.

Purpose and Benefits

Account Dimension Relations provide:

  • Data Integrity: Prevent invalid account-dimension combinations

  • Business Rule Enforcement: Ensure compliance with organizational policies

  • Financial Control: Maintain proper segregation of financial activities

  • Audit Trail: Clear documentation of allowed financial relationships

Understanding Account Dimension Relations

Core Concept

Account Dimension Relations define valid combinations of:

  • G/L Accounts: Specific chart of accounts entries

  • Dimension 1 (Departments): Organizational units that can use the account

  • Dimension 2 (Projects): Projects that can charge to the account

  • Time Periods: When these relationships are valid

Business Applications

  • Budget Control: Ensure spending occurs only in approved account-department combinations

  • Project Management: Control which projects can use specific accounts

  • Compliance: Enforce regulatory or policy requirements

  • Cost Center Management: Prevent cross-departmental account misuse

Setting Up Account Dimension Relations

Accessing the Setup

  1. Primary Navigation: Go to Account Dimension Relation page

  2. From Department Setup: Click Account Dimension Relation action

  3. From Project Setup: Click Account Dimension Relation action

  4. Usage Category: Listed under Administration for easy access

Creating Relations

Basic Setup Process

  1. Navigate to Account Dimension Relation

    • Open the Account Dimension Relation page

    • Click New to create a new relation

  2. Define Account Information

    • Account No.: Select the G/L Account from the chart of accounts

    • System automatically populates Account Name

  3. Set Dimension Codes

    • Dimension 1 Code: Select department that can use this account

    • Dimension 2 Code: Select project (optional)

    • System automatically populates dimension names

  4. Configure Time Periods

    • Open from Date: When this relation becomes effective

    • Closed from Date: When this relation expires (optional)

Required Fields

Account No.

  • Purpose: The G/L account being controlled

  • Validation: Must exist in G/L Account table

  • Impact: Triggers automatic population of Account Name

Dimension 1 Code

  • Purpose: Department authorized to use this account

  • Source: Global Dimension 1 values (departments)

  • Requirement: Cannot be blank

  • Validation: Automatically populates Dimension 1 Name

Optional Fields

Dimension 2 Code

  • Purpose: Specific project authorized for this account-department combination

  • Source: Global Dimension 2 values (projects)

  • Usage: Leave blank to allow all projects, specify for project-specific control

  • Validation: Automatically populates Dimension 2 Name

Date Controls

  • Open from Date: Effective start date for the relation

  • Closed from Date: End date for the relation (for historical or temporary restrictions)

Real-Time Monitoring and Analysis

Financial Information Display

The Account Dimension Relations page provides real-time financial data for each relation:

Net Change

  • Definition: Transaction amounts for the current filter period

  • Calculation: Sum of G/L Entry amounts for the account-dimension combination

  • Usage: Monitor activity levels for each relation

Balance

  • Definition: Account balance up to the filter date

  • Calculation: Cumulative G/L Entry amounts through the upper limit of date filter

  • Usage: Track running balances by dimension combination

Budget

  • Definition: Budgeted amounts for the account-dimension combination

  • Source: G/L Budget Entry table with matching filters

  • Usage: Compare planned vs. actual spending

Filter Capabilities

Date Filter

  • Purpose: Specify time period for analysis

  • Impact: Affects Net Change and Budget calculations

  • Usage: Set to current month, quarter, or year for monitoring

Budget Name Filter

  • Purpose: Select which budget to display

  • Source: G/L Budget Name table

  • Usage: Compare against different budget scenarios

Using Relations for Financial Control

Budget Enforcement

  • Setup: Create relations only for valid account-department combinations

  • Benefit: Prevents posting to unauthorized combinations

  • Monitoring: Use financial displays to track budget performance

Project Control

  • Setup: Define which projects can use specific accounts

  • Application: Ensure project costs are coded to appropriate accounts

  • Analysis: Monitor project spending by account category

Time-Based Control

  • Temporary Access: Use date controls for temporary account access

  • Historical Tracking: Maintain records of past valid combinations

  • Future Planning: Set up relations for future periods

Integration with Other Modules

Department Setup Integration

  • Access: Relations accessible directly from Department Setup

  • Filtering: Pre-filtered by selected department

  • Maintenance: Modify department relations efficiently

Project Setup Integration

  • Access: Relations accessible from Project Setup

  • Filtering: Pre-filtered by selected project

  • Control: Manage project account access centrally

Budget System Integration

  • Budget Display: Real-time budget amounts in relations view

  • Variance Analysis: Compare budget vs. actual by relation

  • Planning: Use relations to structure budget allocation

G/L Account Integration

  • Account Validation: Ensures only valid accounts are used

  • Chart of Accounts: Integrates with standard account structure

  • Financial Reporting: Relations support detailed financial analysis

Reporting and Analysis

Standard Analysis

  • Relation Overview: See all valid combinations at a glance

  • Financial Summary: Real-time financial data for each relation

  • Exception Reporting: Identify unusual activity patterns

Custom Reporting

  • Export Capabilities: Export relation data for external analysis

  • Filter Combinations: Create specific views for different purposes

  • Trend Analysis: Monitor changes in account usage patterns

Best Practices

Setup Practices

  • Complete Configuration: Define relations for all active account-department combinations

  • Forward Planning: Set up relations before they're needed

  • Documentation: Maintain clear records of why relations exist

  • Regular Review: Periodically review and update relations

Control Practices

  • Principle of Least Privilege: Only create relations that are truly needed

  • Segregation of Duties: Ensure appropriate separation of financial responsibilities

  • Exception Handling: Have clear procedures for handling relation violations

  • Approval Process: Require approval for new or modified relations

Maintenance Practices

  • Regular Cleanup: Remove expired or unused relations

  • Date Management: Use date controls effectively for temporary access

  • Change Control: Document all changes to relations

  • Testing: Test new relations before putting them into production

Monitoring Practices

  • Regular Review: Monitor financial activity in relations

  • Variance Investigation: Investigate unusual patterns or amounts

  • Budget Tracking: Use budget displays for ongoing financial control

  • Exception Reporting: Identify and investigate relation violations

Advanced Features

Time-Based Relations

  • Seasonal Accounts: Set up relations for seasonal activities

  • Project Phases: Control account access by project phase

  • Budget Periods: Align relations with budget cycles

Hierarchical Control

  • Field Class Relations: Control at field class level for broader access

  • Department Inheritance: Use field class relations for department groups

  • Project Categories: Group projects for relation management

Exception Handling

  • Emergency Access: Procedures for urgent relation needs

  • Temporary Relations: Short-term access for special circumstances

  • Override Procedures: Controlled methods for bypassing relations

Troubleshooting

Common Issues

Issue: Cannot post to account-department combination

  • Solution: Check if Account Dimension Relation exists for the combination

  • Verify date ranges are current and valid

  • Ensure relation is not closed

Issue: Financial amounts not showing in relations

  • Solution: Verify transactions were posted with correct dimensions

  • Check date filters match transaction dates

  • Ensure account numbers match exactly

Issue: Budget amounts not displaying

  • Solution: Verify budget entries include the correct dimension codes

  • Check Budget Name Filter matches budget setup

  • Ensure budget period aligns with date filter

Issue: Relations not enforcing posting restrictions

  • Solution: This feature may require additional customization

  • Check with system administrator about enforcement mechanisms

  • Verify system configuration for relation validation

Data Validation

Regular Checks

  1. Completeness: Ensure all active account-department combinations have relations

  2. Accuracy: Verify financial amounts match expectations

  3. Currency: Check that relations are current and not expired

  4. Consistency: Ensure similar accounts have similar relation patterns

Troubleshooting Steps

  1. Identify Issue: Clearly define the problem

  2. Check Configuration: Verify relation setup is correct

  3. Validate Data: Ensure underlying data is accurate

  4. Test Solution: Verify fix resolves the issue

  5. Document Resolution: Record solution for future reference

Account Dimension Relations provide essential financial control and data integrity for the Municipal Financial Management System, ensuring that financial transactions occur only through approved organizational pathways.