A Revenue Cloud user story for a Subscription-based Company Looking to replace their legacy system states "As a pricing Manager, bulk discounts will include previously purchased quantities for pricing calculations on the quote in order to reward loyal customers.What should be included in the design of this solution?
Answer(s): B,E
The requirement:"Bulk discounts include previously purchased quantities for pricing calculations."This refers to cross-order discounting, where historical quantities affect pricing on the new quote.To support this:B Contracts, Subscriptions and Assets should be populated with historical dataCPQ reads existing Subscriptions/Assets to determine previously purchased quantities.Historical install base must be migrated for correct discounting.E Discount schedules with Cross Orders checkedSalesforce CPQ includes an OOTB feature:Discount Schedule Cross Orders = TRUEThis allows the quantity tiers to consider historical purchases.Incorrect options:A Custom Action unnecessary unless data is external (not indicated here).C Summary variables cannot aggregate off-contract historical quantities.D Migrating invoices is not required for quantity-based pricing.Thus, the validated answers are B and E.
Universal Containers is Preparing to go live with salesforce CPQ however sales management has stated that they would recurring revenue captured on opportunity line item object to reference within existing pipelinereports.Annual revenue is currently captured in the field ARR c on the SBQQ QuoteLine c Object.Which is the most efficient solution.
Answer(s): C
Universal Containers wants:ARR__c on Opportunity Line Item (Opportunity Product)But ARR is currently on SBQQ__QuoteLine__cThey want ARR captured in pipeline reports without adding automation.Salesforce CPQ Behavior:During Quote Opportunity sync, CPQ automatically maps fields only if:The same API name exists on both objectsThe field types matchThe field-level security is correctIf these conditions are met, CPQ automatically handles field synchronization.Therefore:C. Create ARR__c on Opportunity Line Item with matching field configurationThis leverages native CPQ field mapping, requires zero automation, and is the recommended Salesforce approach.Why the other options are incorrect:OptionWhy IncorrectA . Price Rule to copy valuePrice rules do not run on Opportunity Products; rules run only on Quote Line Editor.B . FlowExtra overhead and maintenance--unnecessary when CPQ already supports native field sync.D . Cross-object formulaOpportunity Line Item cannot reference Quote Line fields (different object trees). Salesforce prevents this.Thus, C is the only correct and efficient solution.
A Salesforce CPQ implementation suffers from poor performance. The Revenue Cloud Consultant has implemented 90 active price rules Supporting complex pricing requirements. what tactics can a Revenue Cloud Consultant Consider to reduce the number of price rules to improve performance in this area?
Answer(s): B,C
Salesforce CPQ performance can degrade with:Too many price rulesSequential calculator complexityRecursion90 rules is high, so optimization is needed.B . Implement Lookup Price RulesLookup Price Rules reduce:Rule countCondition logicMaintenance complexityA lookup table collapses many price rules into one rule, significantly improving performance.C . Use Quote Calculator Plugin (QCP)QCP replaces multiple price rules with:A single JS moduleFaster calculationsMore flexible logicImproved performance, especially with:Complex mathMulti-stage calculationsExternal data lookupsQCP is the recommended performance strategy when price rules become too heavy.Why the other options are incorrect:OptionWhy IncorrectA . Request increased limitsSalesforce does not increase CPQ calculator limits via support.D . Apex triggers instead of price rulesNot allowed; quote line editor uses client-side calculator, not Apex.E . Replace rules with nested bundlesDoes not solve pricing logic complexity and may worsen configuration performance.Thus, B and C are correct.
Universal containers recently migrated legacy contracts and subscriptions into salesforce in order to facilitate amendments and renewals in CPQ .however ,sales user sure getting the `attempt to de- reference a null object' error when amending the legacy contract. what is the most likely cause for the error?
Error:"Attempt to de-reference a null object" while amending migrated contracts/subscriptions.This is the classic CPQ issue when legacy contract/subscription data is missing required fields.Subscription Start / End DatesQuantityPrice fieldsBilling FrequencyTermAmendment-related fields (AmendmentStartDate, etc.)Subscription ProductRelated Order ProductRelated Asset (if asset-based)During amendment, CPQ expects:Missing or incorrectly populated fields cause CPQ code to attempt to reference null values null pointer exception.Thus:C. Required fields are missing or incorrectly populatedWhy the other options are incorrect:OptionWhy IncorrectA . Migrated contracts cannot be amendedFalse. Salesforce explicitly supports amendments on migrated data if fields are populated correctly.B . Asset-based renewal requiredNot required--CPQ supports quote-based and asset-based renewal models.D . Missing lookup to source Quote LineNot required for legacy subscriptions; CPQ amendments work without source quote lines.Thus C is the only valid root cause.
Which corrective action should an admin take after noticing an error on a posted invoice?
Answer(s): A
Post your Comments and Discuss Salesforce AP-223 exam prep with other Community members:
Our website is free, but we have to fight against AI bots and content theft. We're sorry for the inconvenience caused by these security measures. You can access the rest of the AP-223 content, but please register or login to continue.