Release 88

Scope: 72 changes (Collation alterations)
Theme: Regional collation & preparation for IFS Cloud integration

Overview

This release delivers the final architectural step to support regionalisation and future IFS Cloud integration (with IFS Cloud treated as a logical “region”).

A new collation layer (cvw views) has been introduced to assemble regional child sources into unified domain views.
These cvw views catalogue which underlying sources belong together (whether from standard mvw or the new mdm), making get.myview mandatory for correct resolution.
The catalogue is now the only system that “knows” how regional fragments combine.

This change:

  • Reduces collation errors in the reporting layer
  • Enables controlled retirement of legacy regional views
  • Provides a scalable pattern for additional regions and IFS Cloud

New cvw (Collation) Views Created

Business Opportunity

  • BusOpp.Core_Details – 4 components
  • BusOpp.Meta_Codes – 4 components
  • BusOpp.Meta_Dates – 4 components
  • BusOpp.Item_Values_lines – 4 components

Project

  • Project.Core_Details – 4 components
  • Project.Meta_Codes – 4 components
  • Project.Meta_Dates – 4 components
  • Project.Item_Values (cost, revenue, expenses, forecast, contingency) – 5 (multiple component items)
  • Project.Item_Values_cost – 3 components
  • Project.Item_Values_revenue – 3 components

Customer & Feedback

  • Feedback.Meta_Satisfaction – 3 components
  • Customer.Core_Details – 4 components

Regionalisation of mvw Views

Existing mvw views that are directly sourced from Apps10 (UK-only) have been renamed with a regional suffix:

Format:
<ViewName>_<REGION>

Example regions:
UKS, APC, NA, CAD, USD, EUR
(Regions are capitalised and accessed as versions via get.myview.)

This establishes a consistent regional naming pattern and prepares the platform for non-UK sources and IFS Cloud.


BusOpp.Core_Details Enhancements

These views were reviewed specifically to support the Order Pipeline Dashboard:

  • Where data is sourced from MP8, the Create Date is now derived from the FY/Period in the filename
  • Source System has been improved from a simple filename to a structured JSON array for better traceability

General Ledger Updates

8 views affected across:

  • GeneralLedger.Item_Values_#version#
  • GeneralLedger.Meta_Codes_#version#
  • GeneralLedger.Meta_Dates_#version#

Changes:

  • Codes are now sourced correctly at ledger line level (rather than from Ledger.Core_Details)
  • Inclusion of a Period Budget view set to complement:
    • Balance
    • Transaction
      datasets

This improves semantic accuracy and financial reporting alignment.


Data Quality Fixes

  • global_item_values_co2factor
    • Capitalisation error on ID resolved

Summary

This release completes the structural work needed to:

  • Support regional data sources
  • Prepare for IFS Cloud integration
  • Eliminate fragile collation logic in reports
  • Enforce get.myview as the correct access path
  • Enable staged retirement of legacy regional views

It is a foundational architectural release rather than a visible functional change, but it materially reduces risk and improves long-term scalability.

Leave a Comment