What this view is for Busopp.item_values_lines provides the numeric values associated with business opportunities. If: then item_values_lines tells you how much. This is the view where pipeline value lives. A note on “lines” in the CDM For convinience, in the Common Data Model (CDM), the term lines is used as a version indicator. For opportunities, … Read more
What this view is for Busopp.meta_dates provides the key lifecycle and timing dates for business opportunities. If core_details tells you what the opportunity is and meta_codes tells you how it should be categorised, meta_dates tells you when important things happened (or are expected to happen). This view is essential for understanding pipeline flow, forecasting, and … Read more
What this view is for Busopp.meta_codes provides the categorisation and contextual labels for business opportunities. If core_details tells you what the opportunity is, meta_codes tells you how it should be grouped, classified or interpreted. This is where things like type, category, region, ownership and other descriptive attributes live. Level of detail (grain) This view is … Read more
What this view is for Busopp.core_details is the starting point for all sales pipeline reporting. It represents a single business opportunity in its simplest, most recognisable form and provides the identity and linkage needed to explore the rest of the pipeline. If you’re asking “what opportunities do we have, and how do they connect to … Read more
The Sales Pipeline DataMarts are designed to help you move confidently from opportunities, through orders, and on to invoices — without having to relearn the data model each time. The most important thing to remember is this: these views are meant to be combined. Once you understand the pattern, building modular, reusable reporting becomes much … Read more
The meta_codes, meta_dates (and any derived meta_values) views are intentionally long and thin. This structure: That said, long thin tables aren’t always the easiest shape to work with directly in a reporting tool. Shaping meta data into a report-friendly form Once you’ve applied some basic filtering (for example, keeping only the code or date types … Read more
Version: 1.0Owner: Regional Finance DirectorPrepared by: Data Engineering 1. Purpose The purpose of this report is to provide clear and consistent visibility of margin performance across all active projects, comparing the originally approved bid margin with the latest forecast outturn margin. The report will support financial oversight, early risk identification, and commercial performance management at project, PRU, and regional levels. 2. Objectives 3. … Read more
Across our Business Opportunity data marts, we request information in five broad categories. These allow us to report pipeline health, opportunity quality, value, customer context, and alignment with programmes and sales structures. 1. Core Identifiers These are essential keys that allow us to uniquely link and track opportunities across systems. These form the backbone for … Read more
Purpose This view supports financial control and transparency by standardising balance-level data for consistent reporting and reconciliation. It helps finance and business leaders understand balance movements, inter-company positions, and the relationship between projects, programmes, and cost centres. Use Case Suggested dashboard insights: Source Integration with Dimension / Reference Tables Joins used (per SQL): (none in … Read more
Purpose This view provides a clear and consistent way to analyse individual General Ledger transactions across the organisation. It breaks each posting down into structured attributes — such as journal, project, programme, or inter-company activity — so that financial movements can be explored, reconciled, and connected to operational detail. Use Case Suggested dashboard insights: Source … Read more