Salesforce CPQ-Specialist - Salesforce Certified CPQ Specialist (SP25)

ï‚· Requirement Overview:

Admin needs to enable Additional Discounts at both the Quote and Group levels in the Line Editor.

ï‚· Solution Steps:

For the Quote Object:

Navigate to Setup > Object Manager > Quote.

Locate the Line Editor Field Set.

Add the Additional Disc. (%) field to the field set.

For the Quote Line Group Object:

Navigate to Setup > Object Manager > Quote Line Group.

Locate the Line Editor Field Set.

Add the Additional Disc. (%) field to the field set.

ï‚· Testing:

Open the Quote Line Editor and confirm the visibility of the Additional Discount fields at both levels.

ï‚· 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:

Certain products should only be available as part of a bundle, not sold separately.

ï‚· Solution:

Setting the Component checkbox to TRUE on the Product ensures it is only available as a component within a bundle.

ï‚· Why Other Options are Incorrect:

A: Removing Price Book Entries restricts pricing but does not limit availability.

B: Configuration Event field is unrelated to this functionality.

D: Product Rules are not required for this basic configuration.

ï‚· Salesforce CPQ Reference:

The Component checkbox functionality is documented under Product Configuration in CPQ ​.

ï‚· 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.

ï‚· Issue:

The validation error message appears immediately after a user sets a specific value in the Configuration Attribute, even before saving.

ï‚· Solution:

Setting Apply Immediately to False ensures that changes in Configuration Attributes do not trigger immediate validations. Instead, validations occur only upon clicking Save.

ï‚· Why Other Options Are Incorrect:

A: Evaluation Action does not exist as a field for Product Rule Error Conditions.

C: Changing the Apply Immediately field for Product Options does not affect the Configuration Attribute's behavior.

D: Setting Evaluation Event to Save applies to the rule's scope but does not address Configuration Attribute settings.

ï‚· Salesforce CPQ Reference:

Configuration Attribute Settings are explained in CPQ Configuration Attribute documentation ​.

ï‚· Issue:

Quote Lines on Quote A are grouped incorrectly in the output document.

ï‚· Possible Causes:

C: Quote Line Groups: Existing Quote Line Groups on the Quote override the Group Field setting in the template.

D: Group Field in Template Section: The Group Field value in the Line Items template section may cause unexpected grouping.

ï‚· Why Other Options Are Incorrect:

A: The Modified By field has no impact on template grouping.

B: Configuration Attributes like location affect product selection, not grouping in Quote templates.

ï‚· Salesforce CPQ Reference:

Grouping behavior is explained in the Quote Templates and Line Item Configuration documentation ​.

ï‚· Requirement:

Users must view and select product options by scrolling on a single page.

ï‚· Solution Details:

Setting the Option Layout to Sections groups options into expandable/collapsible sections.

This creates a scrollable view without navigating multiple pages.

ï‚· Steps to Update:

Go to the parent Product Record.

Update the Option Layout field to Sections.

 Validation:Test the configuration in the Quote Line Editor. Options should now appear grouped by sections​​.

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.

ï‚· Scenario:

Apply a regional multiplier to the pricebook price and subsequently apply discounts.

ï‚· Solution:

The Customer Price field stores the post-regional multiplier price, enabling further discounting.

ï‚· Why Other Options Are Incorrect:

A: Special Price is used for manual overrides, not automated calculations.

B: Partner Price is unrelated to the customer's pricing structure.

D: List Price remains constant and does not reflect discounts or multipliers.

ï‚· Salesforce CPQ Reference:

Price Rules and field updates are detailed in CPQ Pricing Logic Guidelines ​.