Release 90

by

This release introduces structural improvements across Project Roles, Employee Codes, ReportingUnit, and Order Stage lifecycle tracking.

🔹 Project Roles – Structural Refactor

Project Roles have been removed as a META_TYPE from Project.meta_codes.

Instead:

  • Regional role logic has been separated into dedicated role views per region.
  • Role assignment logic is now contained within a single, controlled location.
  • Roles are reapplied via new collated views (cvw) as part of project.meta_codes.
  • A dedicated cvw for project role meta_codes has also been introduced.

Why this matters

This isolates regional and conditional role logic away from generic metadata structures, reducing complexity and making future changes safer and more maintainable.

Cleaner separation. Better governance. Less checksum risk.

🔹 Employee.meta_codes – Safe Code Standardisation

employee.meta_codes has been updated to standardise non-numeric lookup values.

Where lookup values are non-numeric:

  • code_value now stores a HASH version.
  • The original value is preserved in meta_value (DESC).

Purpose

  • Removes spaces and spurious characters from codes.
  • Prevents accidental collisions.
  • Ensures consistency across joins and downstream consumption.
  • Keeps identifiers simple and safe.

This aligns with the broader identifier discipline being progressively enforced across domains.

🔹 New Domain – ReportingUnit

A new DataMart domain, ReportingUnit, has been introduced.

This domain manages financial reporting structures related to:

  • PRU
  • Cost Centres

These have sufficient depth and interdependency to warrant their own neutral domain rather than being embedded within other views.

First View Delivered

reportingunit_item_values_budget

  • Delivers BP2 (Total Order Intake Budget)
  • Standardised to DataMart value conventions
  • Structured for reuse in reporting and analytics

This creates a clean foundation for financial alignment across Sales, Projects, and Reporting.

🔹 Order Stage Lifecycle Tracking

New view:

order_item_dates_stage

This bridges the historical gap in order line stage tracking previously encompassed within Customer.OrderLine Status.

Key improvement:

  • Supports multiple stage transitions within a single 24-hour window.
  • Provides a proper lifecycle timeline structure.
  • Enables robust stage gate and conversion analysis.

This strengthens operational reporting and removes ambiguity caused by snapshot-only behaviour.

Leave a Comment