Release 94

by

Summary of Impact

  • Reduced duplication across Project, Invoice, and Role structures
  • Introduced Person domain as a strategic identity foundation
  • Expanded Finance coverage with receivables and structured hierarchy
  • Improved data consistency and reporting reliability across key domains

🔧 Project Domain Enhancements

Project Meta Codes – Roles

  • Views updated:
    project_meta_codes_roles
    project_meta_codes_roles_UKS
  • What’s changed:
    Improved construction of project roles across UK sources. Logic now consolidates multiple inputs and removes duplication.
  • Key improvement:
    • Introduced ranking logic using ifs.QFACT_PROJECT_ROLE_ASSIGNM_OL
    • Ensures single role assignment per project/role, prioritising the most recent assignment
  • Outcome:
    Cleaner, de-duplicated role assignments with consistent precedence.

Project Meta Codes (Core View)

  • What’s changed:
    Removed project_meta_codes_roles from the main project_meta_codes view.
  • Why this matters:
    • Prevents unintended duplication in downstream reporting
    • Roles must now be accessed explicitly via dedicated views
  • Outcome:
    Improved stability and predictability of project metadata.

Project Manager Attribute – Reinstated

  • What changed:
    The Project Manager attribute has been reinstated within project_meta_codes.
  • Reason:
    Its removal (as part of the separation of project_meta_codes_roles) resulted in a report dependency failure where downstream reports were expecting this attribute within the core meta_codes view.
  • Approach taken:
    • Project Manager has been selectively reintroduced to project_meta_codes
    • Broader role structures remain accessible via project_meta_codes_roles
  • Outcome:
    • Restores compatibility with existing reports
    • Maintains overall design direction of separating detailed role structures
    • Provides a balanced approach between model integrity and operational continuity

Project Item Codes (UKS)

  • View added:
    project_item_codes_UKS
  • Purpose:
    Provides structured item-level codes associated with project cost and revenue activities.
  • Attributes included:
    • Activity No
    • Sub-Project ID
    • Cost Element (Control Category)
  • Design note:
    • No versioning required for item codes
    • Intended as a stable reference layer for financial attribution

👤 Person Domain (New)

Core Views

  • person_core_details
  • person_core_details_ROW
  • person_core_details_UKS
  • person_identity_bridge
  • What this introduces:
    A new Person domain representing a single, unified identity for each individual.
  • Key design principles:
    • Person_UID derived from Entra ID
    • No company classification (default = 9900)
    • Identity resolved via identity bridge logic
  • Capabilities:
    • Consolidates HR, organisational, and payroll attributes
    • Links to:
      • IFS Person identifiers
      • Payroll identifiers
      • Canonical email address (Entra-aligned)
  • Regional approach:
    • UKS: Collates all known IFS identifiers
    • RoW: Establishes a unified identity using email-based linkage
  • Outcome:
    Foundational step toward a globally consistent person identifier model.

Person Meta Codes

  • Views added:
    person_meta_codes
    person_meta_codes_UKS
  • Purpose:
    Provides a curated set of reusable people-related attributes and classifications.
  • Examples include:
    • Payroll
    • Department
    • Work location
    • Assignment details
  • Outcome:
    Standardised and reusable attributes for reporting and analytics across the organisation.

🧾 Invoice Domain Update

Invoice Meta Codes

  • What’s changed:
    Removed dependency on FACT_CUSTOMER_INVOICE_OL.
  • New source:
    • ifs.QFACT_BMT_DWH_INVOICE_TAB_IAS
  • Impact:
    • Eliminates duplication previously caused by transactional joins
    • Some legacy meta codes may no longer be available
  • Outcome:
    More controlled and reliable invoice metadata.

📊 Business Opportunities (APC)

busopp_details_plus_APC

  • Change applied:
    Updated pipeline status mapping:
    • 'Bid in Client Assessment' → Confirmed (was Unconfirmed)
    • 'Opportunity in Bidding' → Unconfirmed (corrected from incorrect mapping)
  • Outcome:
    Improved alignment of pipeline status with business interpretation.

💰 Finance Domain Expansion

Accounts Receivable – Item Values (Receipts)

  • View added:
    accountsreceivable_item_values_reciepts_UKS
  • Purpose:
    Introduces customer payment (cash receipt) tracking into the data model.
  • Context:
    • Complements existing General Ledger structures
    • Aligns with Accounts Receivable processes
  • Outcome:
    Enables visibility of cash inflows, supporting financial reconciliation and reporting.

Finance Domain Structure

The finance domain aligns to a structured hierarchy:

  • Finance Organisation
    • Chart of Accounts
    • Cost Centres
    • Currencies
    • Foreign Exchange
  • Accounts Payable
    • Purchase Orders
    • Purchase Invoices
  • Accounts Receivable
    • Sales Orders
    • Sales Invoices
  • General Ledger
    • Transactions
    • Budgets
    • Balances
    • Forecasts
    • Journals
    • Consolidation
  • Additional Areas
    • Fixed Assets
    • Cash Management
  • Outcome:
    Establishes a clear financial domain model to support scalable reporting and future expansion.

Leave a Comment