Issue

In the context of the CRM transformation, we must define the role of the standard Opportunity object in the renewal process. Should a Renewal Quote be linked to an Opportunity? If so, should this linkage be manual, automated, or should the Opportunity be bypassed entirely? The decision must ensure consistency across the Sales process, maintain accurate pipeline reporting, and maximize user adoption. 

In the current system, Opportunities are only used to manage the new/growth business. Opportunities are sometimes created for renewals if the deal is considered as a growth business.

Recommendation

Recommended Option: Option C (Opportunity is Not Used for Renewal Quotes)

Given that the demand forecast is handled by an external tool, and the internal Salesforce pipeline is explicitly reserved for "New Business" only, forcing the creation of a Renewal Opportunity would introduce unnecessary process complexity and actively pollute the "New Business" pipeline. The Sales Agreement object (part of Manufacturing Cloud) is specifically designed to handle and track recurring revenue commitments. We recommend leveraging the Sales Agreement as the primary container for renewal tracking and linking the Renewal Quote directly to the Sales Agreement or Account, bypassing the Opportunity entirely. This minimizes user steps, reduces data volume, and aligns perfectly with the defined forecasting scope.

Background & Context

• Current State:
  • New business: Managed via Opportunities and Quote process is followed if a quote is required
  • Renewals: Typically managed via Quotes only, without Opportunities.
  • Spot sales: Managed as exceptions, not standardized.
  • Recurring business: Managed outside Salesforce (in SAP).
• Strategic Goal: Standardize and harmonize the global Sales processes within Salesforce and significantly improve the efficiency of the Sales team. This is intended to increase revenue and reduce the time required to close a deal.

• To-Be Architectural State:

  • The project introduces Manufacturing Cloud for Sales and Revenue Cloud (CPQ). 

  • Sales Agreements of Manufacturing Cloud are intended to handle recurring revenue commitments and tracking.

  • Forecasting Scope: The Salesforce Opportunity pipeline will be strictly limited to "New Business" deals; primary demand forecasting is handled by an external tool.

Assumptions

• Forecasting Tool:

  • Business relies on an external system for demand forecasting.

• CRM Pipeline Scope:

  • The standard Salesforce Opportunity object will be used exclusively for New Business sales pipeline tracking and reporting. Renewal/recurring revenue must not appear in this Sales pipeline.

• Sales Agreement Focus:

  • The Sales Agreement will be utilized as the source of truth and management tool for recurring revenue commitments and consumption (as per Manufacturing Cloud design)

• Revenue Cloud/CPQ Integration:

  • It is technically feasible for the CPQ/Revenue Cloud quoting process to be successfully triggered and completed by linking the Renewal Quote to the Sales Agreement or Account record, bypassing the Opportunity object. (This must be confirmed with the Revenue Cloud team).

• Change management:
  • Change management and user adoption are critical for success.

Constraints

The validity of the recommended approach is constrained by the following factors:

• Forecasting Tool Constraint: This decision is invalidated if business decides to retire the external forecasting tool and mandate the use of the Salesforce Opportunity pipeline for all revenue (New, Renewal and Recurring).

• CPQ Technical Constraint: The decision is dependent on the confirmed technical ability of the Revenue Cloud/CPQ module to successfully generate and manage a Renewal Quote without a parent Opportunity record. If this technical dependency fails, the decision must be revisited to use Option 2 or 4.

• Manufacturing Cloud Functionality Constraint: The decision assumes that all required renewal data and metrics can be tracked and managed directly on the Sales Agreement object, as designed by Manufacturing Cloud.

Impacts

Business Rules

• Opportunity Creation Prohibition for Renewal:

  • Sales users are prohibited from manually creating an Opportunity record for any renewal-related transaction.

• Renewal Quote Linkage:

  • All Renewal Quotes must maintain a mandatory lookup relationship to the Sales Agreement and/or to the Account (Customer) record from which they originated.

• System Automation:

  • The system must be configured to prevent the auto-generation of an Opportunity during the Renewal Quote process, even if standard CPQ/Revenue Cloud settings default to this behavior. 

  • The creation of a Sales Agreement must not automatically trigger the creation of an Opportunity.

Options considered

List the options (viable options or alternatives) you considered. These often require a longer explanation with diagrams, or references to other documents (links are best, but attachments are also possible). Use enough detail to adequately explain what you considered so that a project or business stakeholder reviewing this decision will not come back and ask "did you think about...?"; this leads to loss of credibility and questioning of other decisions. This section also helps ensure that you considered enough suitable alternatives rather than just copy/pasting SAP's recommendations.

Option A: Opportunity is mandatory for renewal with manual creation

The user is responsible for manually creating a Renewal Opportunity before initiating the Renewal Quote process.

Option B: Opportunity is mandatory for renewal with automatic creation

The Opportunity is mandatory, but automated workflow creates the Renewal Opportunity in the background when the user initiates the Renewal Quote.

Option C: No Opportunity usage for renewal

The Opportunity object is bypassed entirely for renewals. The Renewal Quote and subsequent renewal booking are linked directly to the Account or the Sales Agreement.

Option D: Opportunity is mandatory for renewal and Sales Agreement-Driven

The Renewal Opportunity is mandatory but is created and managed directly through the renewal logic embedded within the Sales Agreement object (leveraging Manufacturing Cloud capabilities)

Evaluation

Outline why you selected a position. The best format could be a pro/con table (sample below), but is up to you as the author. You must consider complexity, feasibility, cost/effort to implement, but also ongoing operational impact and cost. You must consider the program principles and explain any deviations in detail. This is probably as important as the decision itself.

Category	Option A: Opportunity is mandatory for renewal with manual creation	Option B: Opportunity is mandatory for renewal with automatic creation	Option C: No Opportunity usage for renewal	Option D: Opportunity is mandatory for renewal and Sales Agreement-Driven
User Experience (UX)	Poor. High administrative burden; violates goal of improving efficiency.	Good. Automation simplifies the process for the user.	Excellent. Simplest path; users only interact with the Sales Agreement/Quote.	Good. Seamless, leveraging Sales Agreement renewal capabilities.
Forecasting Alignment	Low. Pollutes the "New Business" pipeline, violating the scope.	Low. Violates the "New Business Only" pipeline scope.	High. Adheres perfectly to the "New Business Only" pipeline scope.	Low. Still creates an Opportunity record, potentially polluting the pipeline.
Salesforce Architecture	Standard. Uses base SF objects;	Custom Logic. Use standard Salesforce objects but Require custom automation to handle the mandatory linkage.	Clean & Focused. Aligns with Manufacturing Cloud design.	Complex Logic. Heavily relies on bespoke logic triggered by Sales Agreement status changes.
Full activation SF Standard Features	High. Uses standard Opportunity/Quote objects fully, all the Sales Cloud features are available	High. Uses standard Opportunity/Quote objects fully, all the Sales Cloud features are available	Moderate. The access to standard Sales Cloud features (see detailed table below) will be impacted for renewal sales.	High. Leverages both Manufacturing and Sales Cloud features extensively.
Integrations	Standard Link. Interfaces rely on the standard Opportunity ID, which is always present.	Standard Link. Interfaces rely on the standard Opportunity ID, which is always present.	Extra effort. Interfaces must be configured to prioritize the Quotes or Sales Agreement ID for renewal transactions.	Standard Link. Interfaces rely on the standard Opportunity ID, which is always present.
Data Volumes	High. Creates an extra Opportunity record for every single renewal, increasing data volume significantly.	High. Creates an extra Opportunity record for every single renewal, increasing data volume significantly.	Low. Avoids creating redundant Opportunity records, keeping data volumes focused on New Business and Agreements.	High. Creates an extra Opportunity record for every single renewal.
Industry Best Practices	Deviation. Requires manual steps, leading to data quality issues (not best practice).	Consistent. Follows the best practice of the quote process in Salesforce.	Aligned. Best practice is to leverage industry-specific tools (Manufacturing Cloud) for their intended purpose (recurring revenue management).	Aligned, but Complex. Follows best practice but introduces complex synchronization logic between objects.
Development Cost	Zero. No automation required.	Moderate. Requires custom automation (Flow/Apex).	Low-Moderate. Requires confirmation that CPQ can function without the Opportunity link; may need custom quote link logic.	Moderate. Requires custom logic/Flows triggered by Sales Agreement status changes.
Data Integrity	Low. High risk of users forgetting the manual step.	High. Automation ensures data consistency.	High. Renewal/Recurring data lives natively where it belongs: the Sales Agreement.	High. Data linkage is strong.
Adoption/Compliance	Low. Users will resist the extra administrative burden.	High. Process feels seamless and logical to the user.	High. Process is simple and aligns with the defined scope.	Medium. Simple for renewals, but inconsistent with new business flow.

 Impact on Sales Cloud features:

See also

Insert links and references to other documents which are relevant when trying to understand this decision and its implications. Other decisions are often impacted, so it's good to list them here with links. Attachments are also possible but dangerous as they are static documents and not updated by their authors.

Change log