Purpose General Ledger Balance Set Use Case Owner: Soon TanTypical Use Case: General Ledger Balance SetStyle: Fact Source Key Parameters CompanyLedger_ID (Created)PRUProject_IDAccount_ID Sample Exec Response SEQ Dates Measures Codes SQL
Purpose Provides Fact Data Use Case Owner: Soon TanTypical Use Case: General Ledger BalanceStyle: Fact Source Key Parameters CompanyLedger_ID (Created)PRUProject_IDAccount_ID Sample Exec Response SEQ Dates Measures Codes SQL
Purpose Details Use Case Owner: Soon TanTypical Use Case: General LedgerStyle: Details Source Key Parameters CompanyLedger_ID (Created)Account_IDPRUPROJECT_ID Sample Exec Response SEQ Dates Codes SQL
Purpose Provides Management Account Structure Use Case Owner: Soon TanTypical Use Case: Financial Account StructureStyle: Detail Source Key Parameters CompanyAccount Code Sample Exec Response Level 1 Heading Grouping 1 Grouping 2 Leaf Account SQL
Purpose The get.myview stored procedure API allows Power Applications to interact with the DataWarehouse by performing SELECT queries on specified DataMart views. The results are returned as a JSON array. Security Parameters Required Optional Typical Use URL HTTP Header: cURL Example: PowerBI: PowerShell
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-srv-prd.database.windows.netDataMart_Endpoint: bmt_dwh_db_glDataMart_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