Over the past 20 days, Data Engineering has continued the staged delivery of the Common Data Model (CDM) transition into the new IFS-aligned architecture, while also addressing operational stability, identity governance, and historical reporting resilience.
IFS Part 1 – Initial Core Delivery Complete
The first complete editions of the IFS-aligned Part 1 CDM views have now been delivered covering:
project_core_details_IFSproject_meta_codes_IFSproject_meta_dates_IFSinvoice_core_details_IFSinvoice_meta_codes_IFSinvoice_meta_dates_IFSbusopp_core_details_IFSbusopp_meta_codes_IFSbusopp_meta_dates_IFS
These represent the first structured implementation of the new IFS Cloud-aligned Core_Details, Meta_Codes, and Meta_Dates model and establish the baseline contract for future IFS regional integration and reporting validation.
The implementation follows the standardised CDM separation principles:
- Core_Details → business identity and descriptive context
- Meta_Codes → coded classifications and relationships
- Meta_Dates → effective, lifecycle, and operational dates
This delivery forms the initial foundation for ERP Cloud reporting compatibility ahead of broader migration activities.
Order Domain – Extended Commercial Model
The following Order domain views were introduced:
order_core_details_IFSorder_meta_codes_IFSorder_meta_dates_IFS
This first edition introduces support for both:
- traditional Customer Orders
- Sales Contracts
within a unified Order domain structure.
To support this enhancement, the OBJECT_SEQ logic has been revised to incorporate the combined commercial identity while retaining the outward-facing business terminology of Order for downstream reporting compatibility.
This establishes a more robust commercial contract model without forcing report redesign or terminology changes across consuming solutions.
Supplier Invoice & Purchase Order Views Reintroduced
The following supplier item views have been revived from the earlier 2025-04 edition and now formally versioned with the UKS suffix:
supplier_item_codes_invoice_UKSsupplier_item_codes_purchaseorder_UKSsupplier_item_dates_invoice_UKSsupplier_item_dates_purchaseorder_UKSsupplier_item_values_invoice_UKSsupplier_item_values_purchaseorder_UKS
These views are now available for DEV consumption and validation.
In parallel, preparations have been made for:
- catalogue visibility
- Attribute Lineage integration
- metadata exposure through KnowHow and lineage tooling
This supports improved discoverability and governance ahead of broader operational adoption.
Employee Domain Corrections & Enhancements
employee_meta_dates_UKS
Corrections and enhancements were applied to improve employment date consistency and object integrity:
- Corrected
OBJECT_SEQhandling forEMP_NO - Included additional JOB-related date attributes
- Improved alignment between employment and assignment timeline logic
This reduces ambiguity across employee-related historised reporting and improves downstream identity correlation.
Identity Bridge Framework – Initial Release
The first identity bridge views have now been introduced:
identity_bridge_info_entraidentity_bridge_info_knownas_GLOidentity_bridge_info_payroll_UKSidentity_bridge_info_personid_UKSidentity_bridge_info_knownas_entra
These views establish the initial bridge-layer architecture for:
- canonical identity resolution
- payroll linkage
- known-as alias handling
- Entra identity association
- person identifier cross-referencing
This work supports the broader Person and Employee domain redesign and provides a governed identity reference layer for future reporting and security models.
Known-As Identity Register – Bronze Layer Delivery
The following tables were introduced to support the creation of the “Known-As Identity Register”:
identity_knownas_entraidentity_knownas_entra_deleted
These datasets are intended for Bronze-level ingestion and downstream Dataflow processing.
The solution provides a structured mechanism for:
- tracking identity aliases
- managing deleted or historic identity mappings
- supporting canonical identity survivorship rules
- improving enterprise-wide identity reconciliation
This capability is expected to become foundational for future Person-domain governance.
Project Item Value Extensions
The following views were enhanced:
project_item_values_costproject_item_values_revenueemployee_meta_dates
Additional extended logic has now been introduced into the compiled (cvw) layer to improve handling of delayed historical refreshes.
The enhancement ensures that where historised records have not yet fully propagated through the archive process, the current operational snapshot can still be surfaced appropriately within reporting outputs.
This improves resilience during delayed refresh periods while preserving the integrity of the historised model.
The issue was further compounded during a period of slower history processing associated with Python/processing changes within the Fabric environment, which has now been reviewed and stabilised.
Summary
The period has primarily focused on:
- foundational IFS Cloud CDM delivery
- strengthening identity governance
- extending commercial modelling capability
- improving historical reporting resilience
- preparing metadata visibility and lineage integration
- stabilising historised vs operational-state reporting behaviour
Collectively, these changes continue the transition toward a governed, scalable, and Cloud-aligned reporting architecture while maintaining compatibility with existing operational reporting requirements.