Solution Architecture

Release 35

by

Alterations BussOpp Validation exercise for Live Order Intake Report busopp.details_plus & busopp_value (202409) Resource resource.activity, further removal of references to ‘Job’ Customer Orderline customer_orderline, further alignment with customer.orderline with regard to Target date Notes Files sql/svw/project/project_customerinvoice.sql (DEV) and sql/svw/project/project_customerinvoice.sql (PRD) are different.Files sql/svw/project/202406/project_customerinvoice_202406.sql (DEV) and sql/svw/project/202406/project_customerinvoice_202406.sql (PRD) are different.Files sql/svw/customer/customer_orderline.sql (DEV) and sql/svw/customer/customer_orderline.sql (PRD) are … Read more

Release 34

by

Additions employee_details_plus (202409) ADD Person.USER_ID (Windows Login)ADD User.UPN_EMAIL (Primary/Service Principle Email)Sourced EMAIL _ADDRESSS from User Associated Tickets and Actions myBMT | Employee Email Address (bmt-dwh-uks-app-my.azurewebsites.net)Change Request Register – Update data warehouse feed to include the users “identity” and “office” location information. (sharepoint.com) busopp_details_plus (202409) Change source to ifs.FACT_BUSINESS_OPP_OL$Include [CF$_PRU_VALUE] as PRU busopp_value (202409) Change source … Read more

Release 33

by

Alterations customer.invoice (beta version test release)Change of Information Source to QFACT_BMT_DWH_INVOICE_TAB_IAS$ and QFACT_BMT_CUST_ORD_INV_HE_IAS$ (for Ready to Send and Invoice Sent) employee.details_plus (beta version test release)ADD WORK_LOCATION_DESCRIPTIONEMPLOYEE_STATUS_CODE IN (1,7,8) (keeps Employee Category for Secondment visible) Addition busopp.details_202409Change source to ifs.FACT_BUSINESS_OPP_OL$Include [CF$_PRU_VALUE] as PRU Notes Files sql/svw/customer/customer_invoice.sql (DEV) and sql/svw/customer/customer_invoice.sql (PRD) are differentFiles sql/svw/employee/employee_details_plus.sql (DEV) and sql/svw/employee/employee_details_plus.sql (PRD) are differentFile sql/svw/busopp/202409 found in DEV but not … Read more

Infrastructure.ChangeRequest

by

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

Use Case: API vs CSV

by

When comparing the integration of CSV files and APIs with the DataWarehouse, several factors impact data integrity, including data accuracy, consistency, security, and the ability to handle large datasets. Below are some key comparisons and potential risks associated with each method: 1. Data Accuracy and Consistency CSV Integration: API Integration: 2. Data Security CSV Integration: … Read more

Cont.upsert_bulk_meta_fields

by

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

by

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

Release 32

by

Alterations project_expenses update to code comment history Notes Files sql/svw/project/project_expenses.sql (DEV) and sql/svw/project/project_expenses.sql (PRD) are different

get.myhistory

by

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>