Stored Procedure Summary Purpose: The get.myview stored procedure is designed to generate and return a dynamic view of data based on user-defined parameters. It supports complex queries for PowerBI analysis by allowing users to specify various options such as data mart, view name, filtering conditions, and more. Key Features: Example Usage: PowerBI Parameters:DataMart_Host: bmt-dwh-uks-syn-prd-ondemand.sql.azuresynapse.netDataMart_Endpoint: dwh_silverDataMart_Token: … Read more
The whereClause in the GET.myView function specifies the filter criteria to apply to the DataMart. The syntax of a whereClause is similar to an SQL WHERE clause. Key Details: Additional Rules: Example of a whereClause: In this example, the LOAD_DATE > ‘2024-04-01’ comparison uses double single quotation marks (”) to escape the inner quotes.
Purpose The Common View for Resource Details, excluding dates or measures, acts as a unified and reliable source for data on project resources. 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
Purpose The Supplier Invoice (value) fact table is designed to display quantitative data related to invoices generated. This table integrates with dimension tables, such as supplier_details, to provide detailed insights into the financial aspects of projects, including invoicing, revenue, and billing trends. The primary purpose is to support financial analysis and reporting across the organisation. Use … Read more
Purpose Customer Invoice, provides high-level invoice details primarily focused on essential customer and financial information. It is structured to include invoice metadata, billing details, amounts, and various identifiers. The view originates from multiple snapshots and iterations, with each change tracked meticulously to support functionality and flexibility for different reporting and integration requirements. Use Case Owner: Soon … Read more
Purpose The Customer Order Line view provides essential details for individual order lines within customer orders. It serves as a granular component, detailing each line item’s specifics, such as quantity, pricing, revenue, dates, and relevant codes. Designed to align closely with the Customer Order view, this view enables precise tracking of each line item in … Read more
Purpose for Live order intake and Pipeline Review Business Opportunity Line Details Use Case Owner: Soon TanTypical Use Case: Live order intake and Pipeline ReviewStyle: Tailored Fact Based on mvw.busopp_details_plus DataMarts CompanyCustomerBusiness Opportunity Source From Where Sample Exec Response SQL
Purpose The Project Forecast fact table is designed to display projected data related to future project performance, including anticipated costs, revenues, timelines, and resource requirements. This table integrates with dimension tables, such as Project_Details, to provide detailed insights into future planning and strategic decision-making. The primary purpose is to support forecasting, budgeting, and proactive project … Read more
Purpose The Common View for Employee Details. It provides dimension attributes essential for data segmentation of Employee data. It is accessible to multiple departments and systems across the organisation. An extension of BusOpp.Details Use Case Owner: Martyn ColeTypical Use Case: It provides dimension attributes essential for data segmentationStyle: Dimension, meaning a single row per Business Opportunity No. Source … Read more
Purpose for Live order intake and Pipeline Review Single row (Summary Header) per Business Opportunity Use Case Owner: Soon TanTypical Use Case: Live order intake and Pipeline ReviewStyle: Tailored Fact Based on mvw.busopp_details_plus Source FROM WHERE src.[STATE] not in (‘Closed’,’Cancelled’) Parameters CompanyCustomerBusiness Opportunity Sample Exec Response SQL