Release 72

by

This release documents updates to the Data Warehouse covering changes made since 30 June. It focuses on the continued rollout of CDM-aligned views and early implementation of Resource views.

🔁 Customer & Supplier Domains

customer_core_details

supplier_core_details

  • Updated to align with current CDM/CTE design patterns.
  • Follows the order outlined in the CDM Migration Playbook:
    • Project
    • Employee
    • Sales Hierarchy
      • Busopp (Business Opportunity)
      • Order
      • Invoice
    • Supplier & Customer
    • Resource & Person
    • Finance & General Ledger
    • Global (via MIS80), Dates, and Programme

👥 Employee Domain

employee_hours

  • Added: PERSON_ID and PRU_CODE
  • These fields were present in the current version but missing from the beta.

Absence-Related Views

employee_item_codes_absence
employee_item_dates_absence
employee_item_values_absence

  • Updated Source: Changed to use QFACT_BMT_ABSENCE_SUMMARY_IAS
  • Rationale: Avoids line duplication previously seen with QFACT_ABSENCE_LIMIT_OVERVI_OL.

employee_meta_codes

  • Enhancement: myBMT Code Generator updated to support a WHERE clause on the main table.
  • Condition Applied:
WHERE CAST(GETDATE() AS DATE) >= CAST(src.VALID_FROM AS DATE)
  AND CAST(GETDATE() AS DATE) < CAST(src.VALID_TO AS DATE)
  AND src.PRIMARY_JOB = 1

📁 Project Domain

project_item_codes_forecast
project_item_values_forecast

  • Newly Added: Forecast data now included in the project.item series.
  • Complements existing item views (Time, Expense, Cost, Revenue).

🔧 Resource Domain (Initial Release)

resource_item_codes_activity
resource_item_values_activity

  • Marks the beginning of the Resource view series.
  • Conceptual Model: A Resource represents an Employee on a Project.
  • Design Note: Due to the dual primary reference (e.g., COMPANY|EMP_NO|PROJECT_ID), a core_detail view may not be appropriate.

Leave a Comment