|
Status
|
Description
|
|
Planned
|
Initial state for a newly created opportunity. Editable by users with appropriate permissions.
|
|
Proposed
|
Opportunity has been submitted for review.
|
|
Approved
|
Opportunity has been reviewed and approved.
|
|
Closed
|
Opportunity has been closed — either fulfilled or expired. |
| Cancelled |
Opportunity has been cancelled and is no longer active.
|

|
Field
|
Required
|
Description
|
| Type |
Read-only
|
Indicates whether the record is a Risk or an Opportunity. The values are RISKS or OPPS. This field is set at creation and cannot be modified.
|
|
Opp Code
|
Read-only
|
A unique system-generated identifier for the opportunity. The code begins with the letter O, followed by the last digit of the fiscal year, followed by an alphanumeric sequence (e.g., O6A1B5 represents fiscal year ending in 6). Codes follow the pattern A1A1, A1A2, etc.
|
|
Category
|
Yes
|
A classification field used for reporting purposes. Options are: Assortment, Pricing, Distribution & Velocity, Terms, Promotion, Costs, and New Business. Category may also be configured with an optional second level of sub-categories (see below). Note: New Business has special business logic implications (see below).
|
|
Confidence
|
Yes
|
A forecasting indicator representing the likelihood that the opportunity will materialize. Options are: High, Medium, or Low. Used for reporting and forecast probability analysis.
|
|
Name
|
Yes
|
A user-defined label for the opportunity to make it easily identifiable and referenceable.
|
|
Description
|
No
|
An optional free-text field for providing additional context. Clicking the Description link opens an expandable text entry area.
|

Note: When Category is set to New Business, additional business logic is triggered within the Opportunity View page. This behavior is described separately in the New Business category documentation.|
Field
|
Required
|
Description
|
|
Customer
|
Yes
|
Single-select field. Can be a Customer at the planning level (C1) or a Customer entity (CX). The selected Customer must belong to the Customer's primary hierarchy.
|
|
Products
|
Yes
|
Multi-select field. Can include Products at the planning level (P1) or Product entities (PX). All selected Products must belong to the Product's primary hierarchy. Multiple Products can be added to a single opportunity.
|
|
Field
|
Required
|
Description
|
|
Internal Decision Date
|
Yes
|
The date by which an internal decision about whether the opportunity will materialize should be made.
|
|
Customer Decision Date
|
Yes
|
The date by which the opportunity should be confirmed with the Customer.
|
|
Activation Date
|
Yes
|
The date from which the opportunity is considered valid and active. This date also determines the start of the 12-month impact phasing in the Impact panel.
|


|
Field
|
Required
|
Description
|
|
Change
|
Yes*
|
The type of business change being modeled. Options are: Distribution, Pricing, Spend, and Costs. Note: Currently only Pricing should be used; the other types are planned to be removed in a future release.
|
|
From Date
|
Yes
|
The start date for the business change.
|
|
To Date
|
No
|
The end date for the business change. If left blank (No Expiry), the change is treated as open-ended.
|
|
Value Type
|
Read-only
|
Always pre-filled to Percentage. This field does not need to be modified.
|
|
Value
|
Yes*
|
The percentage value of the change. When Change = Pricing, this represents the modeled change to base prices (e.g., -20.00% indicates a 20% reduction in base price).
|
|
Comment
|
No
|
An optional free-text comment for additional context about the business change.
|

Business Rule — Regression Model Scope Restriction: The Regression model cannot be used if a Customer entity (CX) or Product entity (PX) is selected in the Info panel, as this model requires Base Retail prices which are only available when both the Customer and Product are at the planning level (C1 and P1).
|
Metric
|
Editable
|
Description
|
|
VOLUME %
|
Yes
|
The percentage-based representation of the Volume metric. Displays the proportional volume change.
|
|
VOLUME
|
Yes
|
Sell-In Volume (UOM0). Represents incremental volume associated with the opportunity.
|
|
GROSS REVENUE
|
No (Calculated)
|
Sell-In Gross Revenue = Volume × Base Price. When a Pricing change is defined in the Business Changes panel, the Base Price used here reflects the modeled percentage change (e.g., a -20% change applies 80% of Base Price), so the pricing change is incorporated directly into the Gross Revenue calculation. Automatically calculated; cannot be edited directly.
|
|
SPEND
|
Yes
|
Trade Spend associated with the opportunity. Phased independently of volume proportions.
|
|
NET REVENUE
|
No (Calculated)
|
Net Revenue = Gross Revenue − Spend. Automatically calculated based on the above two metrics.
|


|
Action
|
How To
|
|
Enter edit mode
|
Click the Pencil icon (top-right of the opportunity)
|
|
Discard changes
|
Click the Undo button (replaces pencil icon in edit mode)
|
|
Save changes
|
Click the Save button
|
|
Add a description
|
Click the Description link to expand the text area
|
|
Run price elasticity prediction
|
Set Change = Pricing in Business Changes, then click Predict
|
|
Populate impact from prediction
|
Click Calculate Predictive Impact in the Impact panel
|
| Re-phase volume manually |
Edit VOLUME % or VOLUME cells, then click Apply Volume Phasing
|
|
View cell comments
|
Click the Comment icon at the top-right of the Impact panel
|
|
Add a comment to a cell
|
Click the cell's comment indicator or open the comment pane
|
|
Advance workflow status
|
Use the workflow bar at the top of the page (role permissions required)
|