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 pattern.
Affected Views
Opportunity Details
- BusOpp.Core_Details NA
- BusOpp.Core_Details EUR
Opportunity Value
- BusOpp.Item_Values NA
- BusOpp.Item_Values EUR
Why it exists
- Continuity of reporting: preserves pre-Cloud / regional pipeline history that may not be available (or may be summarised) in migrated ERP data.
- Cross-region consistency: normalises different regional file extracts into a common set of identifiers, dates, measures, and descriptors so they can be reported consistently.
- Quick route to insight: provides a clean “best effort” opportunity dimension for segmentation (customer, market, PRU, status) without waiting for full ERP lifecycle integration.
What it outputs (in business terms)
Each row represents an opportunity (not a transaction line), enriched with:
- Who/where: Company, Customer, PRU, Market/District, Currency
- What: Opportunity description and opportunity type
- When: Start and closure-style dates (derived from the best available fields)
- How much: Opportunity value in local currency and a base (GBP) equivalent
- Status: Closed/confirmed state, won/lost status and a simplified stage narrative
- Provenance: A source tag showing whether the record came from MP8 or MP9 and which FY/period file it originated from
How opportunities are identified
Because MP8/MP9 are file-based and don’t always have a stable ERP key, a derived Opportunity Number is produced using:
- a reference id (if provided), plus
- a short hash of the project description
This creates a repeatable identifier that supports trending and deduplication across files.
How regions and currencies are determined
Company and currency are inferred from the source filename (e.g., UK → 1072 / GBP, USA → 5088 / USD, Canada → 5013 / CAD, etc.). This allows the same logic to be applied across regional submissions without bespoke per-file transformations.
How values are made comparable
Opportunity value is taken from Order Intake and then converted to a common base using corporate currency rates (GBP base) valid on (or near) the bid submission date. This enables both:
- local currency reporting, and
- base currency consolidation (for group-level reporting).
Difference between MP8 and MP9 behaviour
- MP8: keeps rows as supplied per file/period (useful for historic trending where the extract is treated as a snapshot series).
- MP9: selects the latest period per opportunity, giving a “current view” of the pipeline for that opportunity.
Scope note (as implemented here)
This final __myview example is currently filtered to Canada (5013) and USA (5088) only. That can be widened once we confirm quality and consistency for the other regions.
Key caveats (business-facing)
- Some fields are best-effort (e.g., region, programme identifiers, contact/rep ids) because MP extracts don’t always include stable master data keys.
- The opportunity identifier is derived, so changes to descriptions or reference ids can cause a new key.
- Stage/state values are simplified to support reporting, not to replicate a full ERP stage gate model.
Typical use cases
- Opportunity & Bidding reporting with pre-IFS Cloud day-1 history
- Regional pipeline consolidation (group view)
- Win/loss analysis and “what changed since last period” comparisons (where MP8 snapshots are retained)