ReportingUnit.item_values_budget provides the budgeted order intake value at Reporting Unit (PRU) level, structured as an item-values dataset so it can be joined consistently with other CDM-style domains (actuals, forecasts, pipeline, etc.). It is sourced from sales.order_intake_budget, which is derived from the Finance-controlled budget workbook in SharePoint, and then reshaped into the standard OBJECT + ITEM … Read more
Order.item_dates_stage captures the order lifecycle timeline as a status-history “item” table. Each row represents a single lifecycle event (a status entry) for an order, with the event date carried as a meta-date value and the event details stored as JSON metadata. Use it when you need to answer questions like: Grain and keys This is … Read more
What this is MP8 and MP9 are regional “Opportunity & Order Intake” extracts used to provide sales pipeline and win/loss visibility where the opportunity lifecycle is not yet fully represented in IFS (or where we need historic continuity). This logic standardises the two extracts into a single, report-ready shape that aligns to our BusOpp-style reporting … Read more
The MP8 and MP9 import process is used to bring regional opportunity and order-intake information from Finance spreadsheets into the Data Warehouse in a consistent and repeatable way. What this process is for This process ensures that: It is primarily used where opportunities exist in regional or pre-IFS systems and are not yet fully represented … Read more
What this view is for Project.meta_dates provides the date-based and lifecycle attributes for projects. Where Project.core_details defines what a project is,and Project.meta_codes defines how a project is classified,Project.meta_dates defines when things happen in the life of a project. If you’re asking “when did this project start?”, “when is it due to finish?”, or “when did … Read more
What this view is for Project.meta_codes provides the categorical and classification attributes for projects. Where Project.core_details defines what a project is,Project.meta_codes defines how a project is described and grouped. If you’re asking “what type of project is this?”, “which programme does it belong to?”, or “how should this project be categorised?” — this is where … Read more
What this view is for Project.core_details is the starting point for all project-based reporting. Where: This view defines the project as a business object and provides the identity and links needed to relate delivery activity back to opportunities, orders, customers and ultimately invoicing. If you’re asking “what projects are we running, for whom, and how … Read more
Purpose evw.project_core_export_meta is a serverless-friendly export view that prepares Project objects for downstream document-style consumers (e.g. Cosmos DB, AI/ML pipelines, Graph preparation), without relying on unsupported Synapse On-Demand constructs such as stacked / correlated FOR JSON queries. It combines: This view is designed as a Stage-1 export: it yields tabular rows with embedded JSON strings … Read more
This template is designed to work as a reusable starting point for Sales Pipeline reporting across Busopp, Order and Invoice, using consistent datamart views and a parameter-driven connection pattern. The template can open and run “out of the box” if default values are provided (or if you enter the parameters when prompted). What you get … Read more
The Sales Pipeline is modelled as three connected domains, each representing a different stage in the commercial lifecycle. They are not duplicates of the same data.They are different truths at different moments in time. Understanding how they relate is the key to building accurate, trustworthy reporting. The three domains at a glance Think of the … Read more