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>

Supplier.PurchaseOrderline

Purpose The Supplier Purchase Order Line Fact TableDesigned to display detailed quantitative data related to purchase orders from suppliers. This table integrates with various dimension tables to provide comprehensive insights into purchase order lines, including project associations, supplier details, and order statuses. The primary purpose is to support procurement tracking, cost analysis, and supplier management … Read more

Project.PurchaseOrderline

Purpose The Supplier Purchase Order Line Fact TableDesigned to display detailed quantitative data related to purchase orders from suppliers. This table integrates with various dimension tables to provide comprehensive insights into purchase order lines, including project associations, supplier details, and order statuses. The primary purpose is to support procurement tracking, cost analysis, and supplier management … Read more

Supplier.Details

Purpose The Common View for Supplier Details, excluding dates or measures, acts as a unified and reliable source for data on business suppliers. It is accessible to different departments and systems across the organisation. This view supports integration with fact tables for reporting and analysis and provides a limited set of dimension attributes. Use Case … Read more

Project.ActivityDetails

Purpose [FACT_PROJ_ACTIVITY_INFO_OL] unique based on ACTIVITY_SEQ, CONTROL_CATEGORY_KEY This table plans to be unique for ACTIVITY_SEQ only Use Case Owner: Martyn ColeTypical Use Case: Provide details for ACTIVITY_SEQ and Sub Project IDStyle: Dimension, Dimension i.e. Single row per ACTIVITY_SEQ Source Key Parameters CompanyProjectCustomerActivitySeq Sample Exec Response SEQ Dates Measures Codes SQL

Customer.Details

Purpose The Customer Details view serves as a unified source for basic business customer information, accessible across departments for consistent reporting and analysis. It excludes transactional data (like dates or measures) and provides a limited set of dimensional attributes, designed for integration with fact tables in reporting scenarios. Use Case Owner: Data EngineeringTypical Use Case: … Read more

Employee.LeaveEntitlement

Purpose The Employee Leave Entitlement fact table is designed to display quantitative data related to employees. This table integrates with dimension tables, such as employee_details_plus, to provide detailed insights into various aspects of employee performance, compensation, and other metrics. The primary purpose is to support data-driven decision-making across the organisation. Use Case Owner: Sam Jopson-WhiteTypical … Read more