CPQ-Specialist Salesforce Certified CPQ Specialist (SU24) Questions and Answers

 Requirement Overview:

Understand what impacts the number of query rows returned when using Lookup Rules in Salesforce CPQ.

 Factors:

C. Total Number of Quote Lines: Each Quote Line triggers a lookup, increasing the number of query rows.

D. Total Number of Fields on the Lookup Object: More fields on the object result in larger query rows.

E. Total Number of Lookup Queries: Multiple lookup queries executed during the Quote Line processing impact the total rows returned.

 Steps to Validate:

Analyze the Lookup Rule configuration and test its behavior with varying Quote Line counts, field sizes, and query numbers.

 Requirement Overview:

Show or hide price-related data in the Quote PDF based on the Primary Checkbox field value.

 Solution Details:

The Conditional Print Field on Template Sections enables dynamic visibility.

Add the Primary Checkbox as a reference in the Conditional Print Field for the section containing price-related columns.

 Steps to Configure:

Navigate to the Quote Template.

Locate the section containing price-related data.

Set the Conditional Print Field to reference the Primary Checkbox.

 Validation:

Generate PDFs with the Primary checkbox set to both True and False and confirm the expected visibility of pricing data.

 Requirement Overview:

When renewing Contracts with Premier Support, it must automatically be replaced with Premier Pro.

 Solution:

The Renewal Product field on the Product record allows admins to specify a replacement Product for renewals.

 Steps to Configure:

Navigate to the Premier Support Product record.

Populate the Renewal Product field with Premier Pro.

Save and test the renewal process to confirm Premier Pro replaces Premier Support on the Quote.

 Validation:

Ensure all renewal Quotes replace Premier Support with Premier Pro automatically.

 Requirement Overview:

The Require Approved Quote setting prevents certain records from being created without an approved Quote.

 Solution Details:

When this setting is enabled, Salesforce CPQ blocks the creation of Order records unless the associated Quote has been approved.

 Validation:

Test by attempting to create an Order from an unapproved Quote and confirming that the system blocks the action.

 Issue Analysis:

Products not syncing to Opportunity Products is usually caused by specific CPQ conditions or rules.

 Reasons for Failure:

B: Products with an Effective Quantity of zero are excluded from syncing.

C: Validation Rules on the Opportunity Product object may silently block the sync process if they are not met.

D: Products with a price of zero do not sync by default.

 Why Other Options Are Incorrect:

A: Missing Price Book Entries prevent quoting entirely, not syncing issues.

E: The Exclude from Opportunity checkbox applies to the Product Option, not the syncing process.

 Salesforce CPQ Reference:

CPQ guidelines for syncing Quote Lines to Opportunity Products ​.

 Requirement Overview:

Universal Containers wants to update the Quantity of a specific Product in the Quote Line Editor via a Price Rule.

The Price Rule should target only this specific Product.

 Key Mechanism:

Use a Price Condition on the Price Rule to evaluate a Quote Line field that uniquely identifies the Product (e.g., Product Code or Product Name).

 Steps to Configure:

Navigate to the Price Rule.

Add a Price Condition:

Field: Select a field from the Quote Line that identifies the Product.

Operator: Equals.

Value: Enter the unique value (e.g., Product Code or Name).

Configure the Price Action to update the Quantity field.

 Validation:

Test the rule by adding the specific Product to a Quote and confirming that the rule updates its Quantity as expected.

 Potential Causes:

Component Checkbox: Products marked as Components are typically excluded from being directly selectable in the Product Selection screen unless part of a bundle .

Search Filter: Custom Search Filters on the Add Products button limit the display of products based on criteria such as product attributes or field values.

 Excluded Reasons:

Hidden Checkbox: This is generally used to hide products from the Quote Line Editor, not the Product Selection screen.

Custom Action Condition: While these can limit the Add Products button's visibility, they do not directly affect individual product visibility.

 Salesforce CPQ Reference Points:

Documentation on Product Selection Behavior and Search Filters confirms these behaviors ​.

 Requirement:

Ensure the Warranty Period from the Product is correctly transferred to the Asset record.

 Solution:

Create a twin field on the Quote Line because:

The Quote Line stores product-specific information during quoting.

When the Quote is contracted, the twin field ensures the value is passed to the Order Product and then to the Asset record.

 Why Other Options Are Incorrect:

A: The Product Option is used within bundles and does not directly transfer to the Asset.

B: The Order Product receives data from the Quote Line, so the twin field must originate there.

C: The Opportunity Product is not involved in the CPQ twin field data flow.

 Salesforce CPQ Reference:

Twin fields and their data flow from Quote Line to Asset are detailed in CPQ Field Mapping Documentation ​.

 Requirement:

Ensure the price of Tiny Boxes ($0.005) is handled with proper decimal precision.

 Solution:

Adjust the Unit Price Scale to 3 in the Pricing and Calculation Package Settings, enabling Salesforce CPQ to handle prices up to three decimal places.

 Why Other Options Are Incorrect:

A: Field-level precision on Quote Line does not control pricing precision.

C: The Product record's Unit Price Scale cannot override global settings.

D: Price Rules are unnecessary for simple decimal precision adjustments.

 Salesforce CPQ Reference:

Decimal precision configuration is described in CPQ Pricing Settings ​.

 Requirement:

Sales reps need to identify Product Options linked to Quote Lines in the Quote Line Editor.

 Solution:

Enabling Visualize Product Hierarchy organizes Quote Lines based on their position within the bundle, displaying the parent-child relationship.

 Why Other Options Are Incorrect:

A: The Product Option Drawer enables detail viewing but does not organize Quote Lines.

B: Preserve Bundle Structure applies to output documents, not the Line Editor.

D: Keep Bundle Together affects grouping but not hierarchy visualization.

 Salesforce CPQ Reference:

Hierarchy settings are covered in the Quote Line Editor Configuration documentation ​.

 Field Location and API Name:

The custom text field Additional_Text__c resides on the Quote object.

In Salesforce CPQ, the correct syntax to reference fields in HTML templates is to use the merge field syntax appropriate to the object.

 Syntax Explanation:

{!quote.Additional_Text__c} directly references the field from the Quote object in a format recognized by the CPQ document generation engine.

Alternative options such as {ISBQQ__Quote__r.Additional_Text__c} reference lookup relationships and do not apply here.

 Salesforce CPQ Reference:

As per the Quote Template Content documentation, use the merge fields directly associated with the object being utilized in the template ​.

 Requirement:

Use fixed pricing for quantity tiers without additional discounts.

 Solution Steps:

B: Marking the product as Non-Discountable prevents additional discounts.

D: Set the Pricing Method to Block to define fixed prices per quantity tier.

E: Create Block Pricing records to define fixed prices for each quantity tier (e.g., 1-5 licenses = $1,000).

 Why Other Options Are Incorrect:

A: Fixed Price is not suitable for tiered pricing.

C: Slab Discount Schedules are not used for block pricing.

 Salesforce CPQ Reference:

Tiered and Block Pricing setups are detailed in Pricing Configuration ​.

 Requirement Overview:

Admin needs to generate one Asset record for each unit of the Product upon contracting.

 Solution Details:

The Asset Conversion field determines how Salesforce CPQ creates Asset records from Quote Lines.

Setting Asset Conversion to One per Unit ensures that for each quantity of the Product, a corresponding Asset is created.

 Steps to Configure:

Navigate to the Product record.

Locate the Asset Conversion picklist and select One per Unit.

Save and test the configuration by creating a Quote, contracting it, and verifying the Asset creation.

 Requirement Overview:

Northern Trail Outfitters wants future renewals to be reflected in the Opportunity pipeline as soon as a Contract is created.

 Solution Details:

The Renewal Quoted checkbox ensures that the renewal Opportunity is created and linked to the pipeline when the Contract is generated.

 Steps to Automate:

Use a Process Builder or Flow to automatically set the Renewal Quoted checkbox on the Contract upon creation.

 Validation:

Test the process by creating a new Contract and verifying that the renewal Opportunity is added to the pipeline.

 Requirement:

Ensure that quotes are recalculated with current information prior to approval without reopening the Quote Line Editor.

 Solution:

Option A: Adding or modifying a field in the Calculating Fields Field Set automatically triggers recalculation for quotes.

Option C: Including the Calculate button on the quote layout provides users with a manual option to trigger recalculation before approval.

 Why Other Options Are Incorrect:

B and D: These require additional customization (e.g., creating a custom Lightning button or Flow) and are not standard CPQ features.

 Salesforce CPQ Reference:

The Calculating Fields Field Set and Calculate Button functionalities are well-documented as standard CPQ tools ​.

 Subscription Term and List Price:

Subscription Product A has a Subscription Term of 6 months with a List Price of $100.

When added to a Quote with a Term of 12 months, the List Price is prorated to account for the longer term.

 Proration and Ranged Discount Schedule:

A Ranged Discount Schedule applies discounts based on quantity, volume, or term thresholds.

For the 12-month term, the price is prorated to $200 (2 times the List Price for 6 months).

The Discount Schedule applies a 25% discount to the prorated price, reducing it to $150.

 Regular Price Calculation:

The Regular Price reflects the discounted value after applying the Discount Schedule:Regular Price=200×(1−0.25)=150×0.5=75\text{Regular Price} = 200 \times (1 - 0.25) = 150 \times 0.5 = 75Regular Price=200×(1−0.25)=150×0.5=75.

 Key Salesforce CPQ Reference Points:

Ranged Discount Schedules modify the List Price based on configured thresholds .

Subscription Pricing Logic ensures correct proration for products with terms different from the Quote Term .

 Requirement:

Ensure the Support SKU is available only in USD and EUR.

 Expected Behavior:

USD: The product is available and uses the Pricebook Entry's List Price.

EUR: The product is available and uses the Pricebook Entry's List Price.

GBP: The product is unavailable due to the absence of a Pricebook Entry in GBP.

 Why Other Options Are Incorrect:

A & D: These imply product unavailability in all currencies, which contradicts the configuration.

B: GBP would not add the product with a zero List Price due to Pricebook Entry restrictions.

 Salesforce CPQ Reference:

Multi-currency behavior and product availability are documented under CPQ Pricing and Product Management ​.

 Scenario Overview:

The Custom value for the Condition Met field allows for complex logical operations using a mix of AND/OR across multiple Price Conditions.

 Use Case:

When a Price Rule has three or more conditions and requires specific combinations of AND and OR logic, the Custom option is required.

 Implementation:

Navigate to the Price Rule.

Set Condition Met to Custom.

Specify the logic (e.g., (Condition 1 AND Condition 2) OR Condition 3).

 Validation:This ensures Salesforce CPQ evaluates the Price Rule as intended, supporting mixed logical conditions.

 Requirement Overview:

Maintenance Feature: At least one Product Option must be selected.

Support Feature: At least one and no more than two Product Options must be selected.

 Key Configurations:

Min Options = 1: Ensures users select at least one option.

Max Options = 2: Ensures users cannot select more than two options.

 Steps to Configure:

Navigate to the Feature Record for Maintenance and set Min Options = 1.

Navigate to the Feature Record for Support and set Min Options = 1 and Max Options = 2.

 Validation:

Test the bundle in the Quote Line Editor and verify the selection behavior for both Features.

 Issue Context:

The custom field is not being updated by the Price Rule even after enabling triggers in the CPQ Package Settings.

 Root Cause:

After creating new fields or updates, the Post Install Script must be executed to register custom fields in the Calculator Referenced Fields list.

 Solution Steps:

Navigate to Setup > Installed Packages > Salesforce CPQ.

Locate the Post Install Scripts section and click Run.

Test the Price Rule again to verify that the custom field is updated correctly.

 Salesforce CPQ Documentation Reference:

Custom fields must be registered with the calculator for the Price Rule engine to interact with them properly​​.

 Requirement Overview:

Universal Containers wants to aggregate the quantities of all Product Options in Feature A to determine the Discount Tier.

 Key Configuration:

Assign the Discount Schedule to the Product Feature itself.

Enable the Cross Orders checkbox to aggregate quantities across multiple orders or contracts.

 Steps to Configure:

Navigate to the Product Feature record for Feature A.

Set the Discount Schedule field to the appropriate Discount Schedule.

On the Discount Schedule, check the Cross Orders box.

 Validation:

Add multiple Product Options from Feature A to a Quote and verify that their quantities are aggregated for discount calculation.

Requirement:

Prevent users from reconfiguring a bundle after its initial configuration.

Solution:

Set Configuration Type to Allowed to permit configuration during initial setup.

Set Configuration Event to Add to allow configuration only when the product is added, blocking reconfiguration later.

Why Other Options Are Incorrect:

A: Disabled blocks all configuration, including initial setup.

B: Configuration Event = Always allows continuous reconfiguration.

D: Reconfigure Line Custom Action is unrelated to this requirement.

Salesforce CPQ Reference:

Configuration Type and Event settings are documented in Bundle Configuration ​.

 Issue Context:

A Contract could not be created from an Order for a new customer.

 Troubleshooting Steps:

A. Confirm Order Product Activation:

Contracts can only be generated for activated Order Products.

C. Check Apex Jobs:

Errors in the contracting process are logged in Apex Jobs. Review these logs for potential issues.

E. Ensure Subscription-Based Order Product:

Contracts require at least one subscription-based Product on the Order.

 Validation:

Verify that all conditions are met and retest the Contract creation process.

 Scenario:

A tiered pricing structure requires different amounts to be applied based on the quantity purchased.

 Solution:

Use a Discount Schedule with:

Type = Slab: Ensures different price amounts are applied for each tier.

Discount Unit = Amount: Specifies fixed dollar values for each tier.

 Why Other Options are Incorrect:

A, B: Block pricing is unsuitable because the requirement is tier-based, not fixed blocks.

C: Range type does not handle tiered pricing accurately.

 Salesforce CPQ Reference:

Discount Schedules with Slab type are detailed in CPQ Discounting Guidelines ​.

 Dynamic Features:

A Dynamic Feature allows administrators to automatically update or populate Product Options for a bundle based on defined rules and conditions.

 Filter Product Rules:

Applying a Filter Product Rule ensures that only relevant or newly available products appear as options for the bundle. This reduces manual maintenance while keeping the bundle dynamic.

 Salesforce CPQ Reference:

Dynamic Features and Filter Product Rules are part of advanced bundling techniques documented under Product Configuration ​.

 Considerations for Authorizing Calculation Service:

The Calculation Service must be authorized by a user who has sufficient privileges and stable permissions.

 Solution Steps:

Option B: Use a non-human admin user (e.g., an integration user) to authorize the Calculation Service. This ensures consistent access and avoids disruptions due to personnel changes.

Option C: Place the user at the top of the Role Hierarchy to ensure full visibility and access across relevant objects.

 Salesforce CPQ Reference:

Proper user configuration for the Calculation Service is outlined in the CPQ Authorization Guidelines ​.

 Requirement:

Sell a non-renewable support SKU in 1-month increments, with the ability to cancel before the agreed end date.

 Solution:

SubscriptionType = One-Time: Ensures the product is treated as a one-time charge, not renewable.

SubscriptionTerm = Number of Months: Allows the quote to define the length of the support agreement.

 Why Other Options Are Incorrect:

A and C: These configurations do not align with the requirement to sell support in defined monthly increments.

D: Marking the product as Renewable contradicts the requirement that the product is non-renewable.

 Salesforce CPQ Reference:

SubscriptionType and SubscriptionTerm fields are detailed in the Subscription Products configuration guide ​.

 Unsegmented Product Setup:

By setting the Default Pricing Table to Standard, the product appears unsegmented when first added to a quote.

This allows users to manually segment the product later if necessary.

 Default Pricing Table Configuration:

The Standard table ensures that pricing is applied uniformly across the quote without segmentation.

 Salesforce CPQ Reference:

This behavior is defined in the Price Dimension Configuration Guidelines in CPQ documentation .

Business Requirement Context:

Universal Containers needs the ability to split Orders by the Start Dates of the Quote Lines.

Each Order generated will correspond to a unique Start Date.

Key Salesforce CPQ Features:

Order By Field: This field on the Quote allows CPQ specialists to specify the criteria for splitting orders. By selecting the SBQQ__StartDate__c field, orders will be created based on the Start Dates of Quote Lines.

Ordered Checkbox: Setting this to True ensures that the Quote Lines are converted into Orders during the ordering process.

Step-by-Step Configuration:

Navigate to the Quote in Salesforce CPQ.

Locate the Order By picklist field and set its value to SBQQ__StartDate__c. This ensures Quote Lines are grouped by their Start Dates for Order generation.

Check the Ordered checkbox on the Quote to mark it ready for Order generation.

Expected Outcome:

When the Orders are generated, CPQ will create separate Order records for each unique Start Date present in the Quote Lines.

Validation and Testing:

Create a Quote with multiple Quote Lines having different Start Dates.

Process the Quote through the Ordering process to verify separate Orders are created for each Start Date.

References:

This approach is aligned with Salesforce CPQ’s guidelines for managing multi-start date Orders and can be verified under "Guidelines for Splitting Orders" in the official Salesforce CPQ documentation​.

 Requirement Overview:

Prevent bundles from being reconfigured in Renewal Quotes while allowing configuration during new or amendment Quotes.

 Solution:

Use a Custom Action Condition to control when the Reconfigure Line action is available.

Set the condition to exclude Renewal Quotes (SBQQ__Type__c != "Renewal").

 Steps to Configure:

Navigate to the Custom Action Condition related to the Reconfigure Line action.

Set the condition criteria to ensure the action is only available for non-Renewal Quotes.

 Validation:

Test by creating Renewal, New, and Amendment Quotes and verifying the Reconfigure Line action behaves as expected.

 Requirement:

Maintenance and Support products must display in separate sections during configuration.

Support products should appear above Maintenance products.

 Solution:

Product Features are used to organize Product Options into sections.

The Number field on Product Features determines the order in which the sections appear.

Support should have a lower Number value to appear above Maintenance.

 Salesforce CPQ Reference:

The Product Features Configuration Guidelines explain how to use features and their ordering mechanisms ​.

 Scenario Overview:

A Product Rule triggers the addition of the Conference Pass Product when a related Product is selected.

 Key Trigger Mechanism:

Product Rules with an Action to add products execute as soon as the user selects a Product on the Quote.

 Steps to Verify:

Navigate to the Product Rule for the Conference Pass.

Ensure the Evaluation Event is set to fire On Initialization or Selection.

 Salesforce CPQ Reference:

Product Rules are typically triggered based on user actions such as adding Products or configuring attributes​​.

 Behavior Explanation:

The Price Rule fails to apply correctly because formula fields used in Price Conditions are not natively supported for the first evaluation cycle.

The system requires additional recalculation to fetch and calculate the correct formula-derived value.

 Root Cause:

Price Rule evaluation relies on static field values at runtime. When formula fields are used, their values may not be immediately available due to dependency on intermediate calculations.

 Salesforce CPQ Reference:

Salesforce documentation discourages the use of formula fields in Price Conditions for real-time calculations and recommends using static fields or Lookup Queries for consistent behavior ​.

 Requirement Overview:

Ensure that the Contract Name field is visible to users when initiating an Amendment.

 Key Configuration:

The Active Contract Lookup Field Set on the Contract object determines which fields appear when selecting a Contract for an Amendment.

 Steps to Configure:

Navigate to the Field Set named Active Contract Lookup on the Contract Object.

Add the custom Contract Name field to the Field Set.

 Validation:

Test the Amendment process to confirm that the Contract Name field is visible.

 Requirement Overview:

Warranty pricing should be based on the discounted prices of hardware products.

 Solution Details:

The Percent of Total Base field determines the pricing basis for Percent of Total Products.

To ensure the price reflects discounted values, set the Percent of Total Base to Net Price.

 Steps to Configure:

Navigate to the Warranty Product record.

Update the Percent of Total Base field to Net Price.

Save and test the configuration by adding hardware products and the Warranty to a Quote.

 Validation:

The Warranty price should now calculate as 10% of the discounted prices of hardware products​​.

 Simplification Method:

By adding the PDF as a required Additional Document in the Quote Template, Salesforce CPQ ensures the PDF is automatically included with each generated Quote.

 Steps to Configure:

Navigate to the Quote Template.

Add the PDF file under the Additional Documents section.

Mark it as required for automatic inclusion.

 Salesforce CPQ Reference:

The Additional Documents feature simplifies document management in Quote Templates ​.

 Requirement Overview:

Assign generated Approval requests to the user's direct manager.

 Solution:

Salesforce CPQ's Advanced Approvals package includes the setting Next Automated Approver Determined By, which allows Approvals to be routed automatically to the user's manager.

 Steps to Configure:

Navigate to the Approval Process.

Set Next Automated Approver Determined By to Manager.

Save and test the Approval process to ensure it correctly assigns to the manager.

 Scenario:

Contracts are not being generated for activated Orders containing subscription-based products.

 Why Debug Logs?

Debug Logs capture real-time system activity, including Apex triggers and CPQ package processes.

They provide detailed error messages and can identify issues such as missing triggers, misconfigured objects, or dependency errors.

 Steps to Investigate:

Enable Debug Logs in Salesforce Setup for the affected user or system process.

Perform the action that generates the error (e.g., activating the Order).

Review the logs for errors related to Contract generation.

This question is a duplicate of Question No. 54, and the verified answer remains consistent.

 Issue Context:

Lookup Price Rules rely on the SBQQ__LookupObject__c field to reference the target object (e.g., Rental Rates).

If this API name is inaccurate or incorrectly input, the rule will fail to retrieve the desired value.

 Review Steps:

Go to the Price Rule record.

Check the SBQQ__LookupObject__c field. Confirm the API Name of the Rental Rates object is accurate.

Example: Ensure the API name matches exactly (e.g., Rental_Rates__c).

 Additional Checks:

Verify the Lookup Queries. Ensure the filter conditions correctly target a valid record on the referenced object.

 Salesforce Documentation Reference:This behavior follows Salesforce CPQ's guidelines on Lookup Price Rules configuration​​.

 Cause Analysis:

Hidden = TRUE: Products marked as hidden do not appear in the Opportunity Line Item after saving the Quote.

Component = TRUE: Products flagged as components are part of a bundle and are not directly added as standalone Opportunity Line Items.

 Key Settings:

These configurations are commonly used for internal or auxiliary products within a bundle or restricted products.

 Salesforce CPQ Reference:

The behavior is explained under Product Configuration and Quote Mapping ​.

 Scenario Overview:

A Configuration Attribute displays a picklist with more values than the corresponding field on the Quote Line, which is restricted to a predefined set.

 Behavior:

When a user selects a value that is not in the Quote Line field’s restricted picklist, Salesforce CPQ prevents saving and displays an error.

 Validation:

The Quote Line enforces the picklist restriction, ensuring data integrity across the configuration and Quote Line Editor.

 Requirement Overview:

Universal Containers wants the Shipping Plus product to appear at the top of the Product Selection list.

 Key Configuration:

The Sort Order field determines the sequence of Products in Product Selection.

Products with lower numerical Sort Order values appear at the top.

 Steps to Configure:

Navigate to the Product Record for Shipping Plus.

Set the Sort Order field to the lowest available value (e.g., 1).

Save and test the configuration in the Product Selection screen.

 Validation:

Ensure that Shipping Plus appears at the top of the Product Selection list.

 Issue Context:

Users encounter a warning when searching Campaign records in the Quote Line Editor.

 Root Cause:

For Lookup fields to work correctly in Salesforce CPQ's Quote Line Editor, a Twin Field must exist on the target object (Campaign) with the same API name as the Quote Line lookup field.

 Solution Steps:

Create a custom field on the Campaign Object with the same API name as the lookup field on the Quote Line Object.

Ensure the field types match (e.g., both are Lookup fields or Text fields).

 Validation:

Test the functionality by searching for Campaign records in the Quote Line Editor. The warning message should no longer appear.

 Salesforce CPQ Documentation Reference:

This is a common configuration for CPQ Lookup fields in the Quote Line Editor​​.

 Requirement:

Set Product A’s price back to its List Price ($300) for a business unit account while ignoring parent account contracted pricing.

 Solution Steps:

Option B: Create a new contracted price record for Product A at $300 for the business unit account.

Option D: Mark the Ignore Parent Contracted Prices checkbox as TRUE on the business unit account to override inherited contracted pricing.

 Why Other Options Are Incorrect:

A: This would affect all contracted prices under the parent account, which is not the desired behavior.

C: Creating a new contracted price with Ignore Parent Contracted Prices set to TRUE is redundant; the account-level setting (D) achieves this.

 Salesforce CPQ Reference:

Contracted Pricing functionality, including parent-child account handling, is outlined in CPQ Pricing Guidelines ​.

Comprehensive Detailed Step-by-Step Explanation with all Salesforce CPQ References

To split orders based on product family when creating orders from quotes in Salesforce CPQ, the following steps must be followed:

Enable the Allow Multiple Orders Setting

Navigate to Setup > Installed Packages and locate Salesforce CPQ.

Click Configure, then go to the Orders tab in the CPQ package settings.

Check the Allow Multiple Orders option. This allows multiple orders to be created from a single quote.

This setting ensures that products can be grouped and split into separate orders based on specific criteria like Product Family​​.

Set the Order By Field to Product Family

From the object management settings for Quotes, edit the Order By field.

Add "Product Family" as a picklist value if it is not already available.

On the Quote, select Product Family in the Order By field.

Save your changes. When creating an order, Salesforce CPQ will group quote lines into separate orders based on the Product Family​​.

Process for Creating Orders

On the quote, select the Ordered checkbox.

Salesforce CPQ will automatically split the quote into multiple orders, grouping quote lines by the Product Family value​.

Notes and Considerations

If some quote lines do not have a value for the field used in the Order By, they will be grouped into one order.

This functionality is available in Salesforce CPQ editions starting from Summer ’16​​.

By following these steps, administrators can ensure that similar products are automatically separated into different orders based on their product family.

 Requirement Overview:

Control the visibility of fields in the Quote Line Editor.

 Solution:

The Edit Lines Field Set Name special field on the Quote object references the field set used to control which Quote Line fields are visible in the editor.

 Steps to Configure:

Navigate to the Field Set on the Quote Line object.

Add or remove fields from the field set referenced in the Edit Lines Field Set Name field.

 Validation:

Test the Quote Line Editor to ensure only the configured fields are visible.

 Requirement Overview:

Reference specific Error Condition records in the Advanced Condition field of a Product Rule.

 Solution:

Use the Index field value from the Error Condition record in the Advanced Condition formula.

 Example:

If the Index field value is 1 for a specific Error Condition, reference it as 1 in the Advanced Condition (e.g., 1 AND 2).

 Requirement:

Provide 80 products for general access while restricting access to 20 special products for a specific user group.

 Solution:

Two Price Books:

General Access Price Book: Includes only the 80 products available to all users.

Special Access Price Book: Includes all 100 products for users with elevated access.

Guided Selling: Dynamically assigns the appropriate Price Book based on user access level, ensuring visibility is controlled.

 Salesforce CPQ Reference:

The Price Book strategy with Guided Selling is detailed in the Product and Price Configuration guidelines ​.

 Scenario Overview:

List Unit Price: Product A's standard price is $150.

Contracted Price: CK has a contracted price of $100 for Product A.

Discretionary Discount: CK negotiated a 10% discretionary discount for this deal.

 Price Calculation:

List Unit Price remains the standard price of $150.

Regular Unit Price applies the contracted price of $100.

Customer Unit Price: After applying the 10% discretionary discount on the contracted price,Customer Unit Price=100−(100×0.1)=90\text{Customer Unit Price} = 100 - (100 \times 0.1) = 90Customer Unit Price=100−(100×0.1)=90.

Net Unit Price matches the Customer Unit Price for the 10 units being purchased, which is $90.

 Salesforce CPQ Reference:

Salesforce CPQ Contracted Price logic ensures negotiated prices override the List Price, and additional discretionary discounts apply as expected ​.

 Requirement:

Amend an active contract and adjust prices for subscriptions and assets based on new discounts.

 Solution:

Use the Amend Contract process.

Adjust prices for subscriptions or assets directly by modifying the Net Price or Price field.

Use the Refresh Prices button to apply changes to the amended contract.

 Why Other Options are Incorrect:

A: Cloning Quote Lines is unnecessary and inefficient for contract amendments.

B: Changing the contract status to Draft is not supported in standard CPQ.

D: Creating a new Price Book is not required for this use case.

 Salesforce CPQ Reference:

The Amendments Process is extensively documented in CPQ Subscription Management ​.

Amendment Functionality:

Amendments are used to modify existing contracts by adjusting quantities, discounts, or adding products while maintaining contract continuity.

Supported Scenarios:

A: Quantity changes with new discounts can be applied during amendments.

C: New products can be added and aligned with the contract’s existing term (co-terminated).

Salesforce CPQ Reference:

Amendments are extensively documented under Contract and Subscription Management ​.

Requirement:

Implement a price change for Product A when its quantity exceeds 10.

Solution:

Price Conditions:

Verify that the product is Product A.

Check that the quantity of Product A exceeds 10 using a Summary Variable.

Price Action:

Inject the value $50 into the Unit Price field for Product A.

Why Other Options Are Incorrect:

B, C, D: These options involve unnecessary actions, such as injecting values into the Quantity field, which is unrelated to the requirement.

Salesforce CPQ Reference:

Configuring Price Rules with Conditions and Actions for specific scenarios ​.

 Requirement:

Calculate the prorate multiplier when a subscription product’s End Date differs from the Quote’s End Date.

 Solution:

CPQ uses the Quote Line date (specific to the subscription product) to calculate the prorate multiplier. This ensures alignment with the subscription term.

 Why Other Options Are Incorrect:

A & D: Earliest or latest dates do not determine prorate multipliers.

B: The Quote date applies to the Quote as a whole, not individual subscription products.

 Salesforce CPQ Reference:

Prorate multiplier calculations are outlined in Subscription Management Guidelines ​.

The order of precedence for evaluating subscription dates is as follows

(1) Quote Line,

(2) Quote Line Group, and

(3) Quote

https://help.salesforce.com/s/articleView?id=000383503 &type=1

 Requirement:

Allow users to generate output documents in Microsoft Word format.

 Solution:

The Allow Output Format Change checkbox in User Settings enables users to select alternative formats like Microsoft Word during document generation.

 Why Other Options Are Incorrect:

A: The checkbox is user-specific, not template-specific.

C: Creating a second template is unnecessary when users can dynamically change the format.

D: Template Sections do not control output formats.

 Salesforce CPQ Reference:

Configuring user settings for document generation is detailed in CPQ Quote Templates Documentation ​.

Background Context:When amending a contract in Salesforce CPQ, issues with net pricing arise if the amendment impacts existing subscription products. Subscription products often rely on Discount Schedules for calculating discounts, especially when quantity changes. The "Cross Order" field on Discount Schedules ensures discounts account for cumulative quantities across multiple orders or contracts.

Problem Analysis:

The reported issue involves incorrect net pricing specifically when the quantity of existing products is adjusted during contract amendments.

This aligns with the functionality of Discount Schedules, where the total quantity determines the discount applied. Without "Cross Order" enabled, Salesforce CPQ considers only the current order's quantities rather than aggregating across orders.

Root Cause Identification:

Discount Schedule and Cross Order:If the Discount Schedule associated with these products does not have "Cross Order" enabled, any amendments won't consider cumulative quantities. Instead, the system recalculates based on only the new or adjusted quantities, leading to incorrect net pricing.

Supporting Evidence:

Salesforce documentation highlights that Cross Order must be selected in the Discount Schedule for accurate discount calculations across multiple orders or contracts. Otherwise, amendments operate in isolation​​.

The feature ensures that ongoing contracts retain accurate pricing based on total historical quantities.

Recommended Resolution:

Navigate to the Discount Schedule associated with the affected products.

Verify and enable the Cross Order checkbox:

Go to Setup > Discount Schedules.

Locate the relevant Discount Schedule.

Edit the schedule and enable Cross Order.

Test the functionality by amending the contract and verifying the net pricing calculations.

Preventative Actions:

For all subscription-based products relying on Discount Schedules, ensure Cross Order is enabled during initial configuration.

Provide training to Salesforce CPQ admins to understand the implications of Discount Schedule settings on pricing.

By following these steps and verifying the Discount Schedule configuration, the issue can be resolved, ensuring consistent and accurate net pricing during contract amendments.