Salesforce Sales-Admn-202 - Salesforce Certified CPQ Administrator

ï‚· Requirement Overview:

A product must be priced as 10% of the total fixed-priced products on the Quote.

ï‚· Solution Details:

Option A:

Setting the Pricing Method to Percent of Total ensures the price is calculated as a percentage of the total value of other products.

The Subscription Pricing is left blank since it is not a subscription product.

Option D:

Set the Pricing Method to List and Subscription Pricing to Percent of Total to achieve the same result with flexibility for subscription-based products.

ï‚· Requirement Overview:

A user must have the ability to approve any approval request, regardless of who the request is assigned to.

ï‚· Solution:

Granting the Modify All Data permission provides administrative privileges across all Salesforce objects, including the ability to approve any approval request in Advanced Approvals.

ï‚· Steps to Configure:

Navigate to the user’s Profile or Permission Set.

Add the Modify All Data permission.

Save and test the user’s ability to approve any request.

ï‚· Validation:

Confirm the user can approve approval requests without assignment restrictions.

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

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.

ï‚· Requirement:

Ensure the correct Distributor Discount is applied to Quote Lines based on the distributor's Discount_Level__c field value.

ï‚· Solution:

Configurator Scoped Price Rule:

A Price Condition checks whether the SBQQ__Quote__r.Distributor__c field is populated.

If the field is blank, the rule does not execute.

Price Action:

Injects the value of the Discount_Level__c field from the Distributor account into the Quote Line's SBQQ__DistributorDiscount__c field.

ï‚· Why Option A is Correct:

Configurator Scope ensures the rule is evaluated during configuration, applying discounts dynamically as the Quote is edited.

ï‚· Why Option B is Incorrect:

Calculator Scoped Price Rules execute during calculations (not configuration), which may result in delayed discount updates.

ï‚· Salesforce CPQ Reference:

Price Rules and their scopes are documented in the CPQ Pricing Logic Configuration ​.

ï‚· Scenario:

A subscription product does not appear in the Product Selection screen during search.

ï‚· Possible Causes:

A: The Active checkbox must be TRUE for the product to appear.

D: The product requires a Pricebook Entry in the corresponding Quote’s Pricebook.

E: If the Component checkbox is TRUE, the product is treated as a bundle component, not standalone, and will not appear in search results.

ï‚· Why Other Options Are Incorrect:

B: Cost records are unrelated to product visibility.

C: The Optional checkbox determines bundling behavior, not search visibility.

ï‚· Salesforce CPQ Reference:

Product visibility settings are detailed in CPQ Product Selection Configuration ​.

ï‚· Requirement Overview:

Product A must always be included in the bundle.

Product B should be included by default but can be removed by the user.

ï‚· Key Configurations:

Required = FALSE: This ensures that Product B is not mandatory and can be removed by the user.

Selected = TRUE: This includes Product B by default when the bundle is added to the Quote.

ï‚· Steps to Configure:

Navigate to the Product Option record for Product B.

Set Required to FALSE.

Set Selected to TRUE.

Save and test the behavior by adding the bundle to a Quote.

ï‚· Validation:

Product B should be pre-selected in the Quote Line Editor but can be deselected by the user.

This setup ensures flexibility for Product B while ensuring Product A remains mandatory​​.

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

When amending a contract in Salesforce CPQ, the net pricing of products can sometimes appear incorrect, especially when quantities are adjusted on existing subscriptions. The "Revised Quantity" field on the Subscription record is used during amendments to reflect the updated quantity of a subscription product after the amendment. If this field is set incorrectly or unexpectedly (e.g., manually or via automation), it can override the expected quantity and cause discrepancies in pricing calculations, especially for existing products. This aligns with the scenario where the issue only occurs when quantities are adjusted on existing products. Option B (Price Rule firing On Calculate) could affect pricing but typically wouldn’t target only existing products or cause quantity-specific issues unless explicitly designed to do so. Option C (Price Rule firing Before Calculate) might alter pricing but wouldn’t directly tie to quantity adjustments on amendments. Option D (Discount Schedule with Cross Order unselected) affects pricing tiers but isn’t directly related to amendment quantity adjustments. Per Salesforce CPQ documentation, the "Revised Quantity" field is a key factor in amendment scenarios impacting pricing consistency.

ï‚· Requirement:

Automatically apply a 25% discount to a specific Product Option within a bundle.

ï‚· Solution:

Option C: The Discounted by Package field ensures that the Product Option inherits discounts applied to the bundle as a whole.

Option D: A Price Rule specifically targeting this Product Option can enforce the 25% discount when it is added to the bundle.

ï‚· Why Other Options Are Incorrect:

A: The Option Discount (%) field on the Product Feature applies discounts to all options, not just a specific one.

B: The Option Discount (%) field on the Product Option does not dynamically apply discounts based on specific scenarios.

ï‚· Salesforce CPQ Reference:

Configuration and discounting for bundles and Product Options are documented under Bundle Pricing Configuration Guidelines ​.