Julian.Kellett Scope: Updates to Common Data Model (CDM) and project-specific viewsTotal File Changes: 34 🔄 Summary of Key Changes ✅ Stabilised Views for 202409 Reporting These views are now stable and finalised for the 202409 reporting cycle, helping to prevent reuse issues in future CDM deployments. 🛠️ Updated PRUs for Project Views CAD Region Updates: USD … Read more
📝 Description This view provides a structured metadata representation of Business Opportunities (BusOpp), transforming source data into a JSON-like attribute-value format. It supports consistent reporting and simplifies analytics by organising attributes under clear META_TYPE categories like OPPORTUNITY, STATUS, and SALES. 🎯 Purpose ✅ Use Cases 🧱 Structure Each row in the view corresponds to a … Read more
Verb Meaning (Simple) Behaviour SQL/Data Analogy Use Case GET “Tell me about this.” Retrieves a resource or field SELECT * FROM table WHERE id = x Viewing a project status or employee detail POST “Here’s a new thing.” Creates a new resource INSERT INTO table … New project added, first metadata entry PUT “Replace the … Read more
Summary of Changes by View 1. project_details_plus_USD & project_details_plus_CAD Status Logic Updated Project Manager Email Added 2. project_details_plus_CAD & project_details_USD Column Name Adjustment 3. project_details_plus_APC, customer_details_APC, project_details_APC PRU Code Mapping Enhancement 4. global_company & global_company_202409 Expanded Source 5. global_organisation & global_organisation_202409 Same as Above 6. employee_item_codes_absence, employee_item_dates_absence, employee_item_values_absence Minor Logic Refinements 7. dates_DIM_DATE_202409 Performance Optimisation … Read more
Purpose This playbook guides the phased migration from existing DataMart views (202409) to CDM-standard views, including core, meta (dates, codes, values), and item tables. It supports the transition to IFS Cloud and ensures a consistent, scalable data model across all domains. MVP Scope Domains required for MVP: Phased Delivery Approach Phase 1: Live Data Seeding … Read more
🔍 When working with Oracle databases, it’s often helpful to retrieve the SQL definition of a view — especially when reverse engineering or documenting logic for reporting and data pipelines. ✅ View Definitions via USER_VIEWS If you own the view or have access to it within your schema, you can use the following query: 💡 … Read more
🆕 What’s New New Project View (Item 207) Added project_details_plus_APC to complete the set for regional project reporting. Improved Date Views (Items 20–21, 27–30, 204–205) Programme ID Enhancements (Items 206, 208) Integrated clearer programme identification fields from MIS80 into global organisation views, allowing for cross regional identification. 🔂Development/Improvements for cdm Notes The following files were … Read more
Project Description This initiative aims to integrate Business Opportunity Pipeline data from SharePoint Lists and Deltek Vision sources into the central Data Warehouse. The primary objective is to enable consistent, automated global reporting ahead of the GMIS ERP rollout across the APAC, NA, and EU regions. The integration will align with the existing Business Opportunity … Read more
🎯 Purpose This framework ensures that values in complex metadata structures (e.g. project earned value, invoice accounting, or employee attributes) are verified for presence even when using incremental loads. It protects against stale data persistence or silent value loss, using metadata-driven auditing. 🧩 Problem Context In many CDM views, values are upserted using procedures like … Read more
🎯 Objective To proactively expire or flag metadata rows that are no longer present in the source data even if their values haven’t changed, avoiding persistence of stale or misleading data. 1. 🏗 Recommended Table Extension Add these optional columns to any table using patch_upsert or put_update: 2. 📥 Staging Input Table – stage.project_values_current Your … Read more