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 customers, projects and orders?” — this is where you begin.
Level of detail (grain)
- One row per business opportunity
- Each row represents a single opportunity within a company
- No duplication, no aggregation
This makes the view safe to count, filter and join without worrying about double-counting.
What you’ll find in this view
core_details focuses on identity and context, not metrics.
Typical content includes:
- Opportunity identifiers
- High-level descriptive fields
- Status and headline indicators
- Link keys to related domains (such as Project, Customer and future Orders)
All identifiers are aligned to support consistent joins and modular reporting.
How to join this view
Every row includes an OBJECT_SEQ field.
OBJECT_SEQ is a paired identifier that combines:
- Company identifier
- Opportunity identifier
It has been created specifically to simplify joins.
When joining to other Busopp views, always join on OBJECT_SEQ.
This:
- Prevents accidental cross-company joins
- Removes the need to manage composite keys manually
- Keeps joins consistent across the Sales Pipeline model
How this view is commonly used
Report writers typically use Busopp.core_details to:
- Count opportunities
- Filter pipeline by status or ownership
- Anchor joins to:
Busopp.meta_codesfor categorisationBusopp.meta_datesfor lifecycle analysisBusopp.item_values_linesfor pipeline value
- Link opportunities to Orders and Invoices downstream
It is rarely used on its own — it is the foundation other views build on.
What this view does not contain
By design, core_details does not include:
- Financial values
- Aggregated metrics
- Currency logic
- Detailed lifecycle dates
Those belong in the supporting views and are intentionally separated to keep this view stable and predictable.
Where this fits in a report build
A typical flow looks like:
- Start with Busopp.core_details to define the opportunity set
- Add meta_dates to understand lifecycle timing
- Add meta_codes to slice and group
- Bring in item_values_lines to analyse pipeline value
- Aggregate or shape further as required
If a report feels hard to reason about, it’s often worth checking whether this view was used as the starting anchor.
Key takeaway
Busopp.core_detailsgives you one clean row per opportunity and the keys needed to explore everything else.Start here, build outward, and the rest of the Sales Pipeline model will make sense naturally.