Project.Dates

Purpose: The purpose of this DataMart view is to provide a comprehensive timeline overview of a project’s key dates, from its creation to completion. It consolidates important project milestones such as planned and actual start and finish dates, delivery estimates, and project modifications. This view is designed to help stakeholders monitor project timelines, identify delays, … Read more

Employee.Employment

Purpose: The purpose of this DataMart view is to provide a clear snapshot of an employee’s current and historical employment status within a company. It captures essential details such as employment dates, employment type, and agreement, with a focus on determining whether an employee is currently active or not. This view is useful for HR … Read more

Customer.OrderlineValue

Purpose The Customer Order Line Value view provides a detailed financial overview of customer order lines, including key pricing and cost information, quantities, dates, and currency-based amounts. This view is specifically designed to facilitate reporting and analysis on the financial performance of individual order lines. It includes fields that capture gross and net amounts, tax-inclusive … Read more

Customer.OrderlineStatus

Purpose The Customer Order Line Status view provides detailed tracking of the operational state of each customer order line. It monitors statuses, user actions, and error messages for each line item within customer orders, offering insights into the progress and any potential issues in order line processing. This view is essential for maintaining transparency and … Read more

Customer.InvoiceValue

Purpose The Customer Invoice Value view provides detailed financial information on customer invoices, including gross, VAT, and net amounts across multiple currencies. This view is focused on delivering a comprehensive breakdown of financial values, allowing for detailed reporting and analysis of invoice data. Use Case Owner: Soon TanTypical Use Case: Designed for financial reporting and … Read more

Customer.InvoiceStatus

Purpose The Customer Invoice Status view provides insight into the operational state of customer invoices by tracking statuses and reporting errors. This view is intended for monitoring the life-cycle and status changes of invoices, including entry dates, user actions, and error messages. It supports operational reporting by offering visibility into any issues or errors that … Read more

Infrastructure.ChangeRequest

Purpose Designed to display the output from the SharePoint List Change Request The myHistory version of the request is designed to evaluate the effectiveness of the change management process. Use Case Owner: Simon WillmoreTypical Use Case: Change Management Dashboard presents key metrics such as the number of open and closed change requestsStyle: Fact Dashboards Utilising … Read more

Cont.upsert_bulk_meta_fields

The procedure [cont].[upsert_bulk_meta_fields] is a SQL Server stored procedure designed for bulk upsert operations on metadata fields from source tables into a target metadata table. The procedure accepts various parameters to define the source and target tables, as well as the metadata structure, and supports batch processing. Key Steps in the Procedure: Purpose: The procedure … Read more

Cont.upsert_bulk_entity

The SQL stored procedure [cont].[upsert_bulk_entity] is designed to handle the bulk insertion or updating (upserting) of entity data from a source table into a target entity table. Here’s a summary of the key steps involved: Overall, this procedure is designed to efficiently manage the bulk upsertion of entity data from a specified source to a … Read more

get.myhistory

Stored Procedure Summary Purpose: This stored procedure, [get].[myhistory], is designed to retrieve historical views from a data mart for use in PowerBI analysis. It is flexible and allows users to specify various parameters to customise the view that is returned. Key Features: Typical Use Example Usage: PowerBI: Parameters:History_Host: bmt-dwh-uks-syn-prd-ondemand.sql.azuresynapse.netHistory_Endpoint: BMTDWHGLDBDataMart_Token: <my_token>