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): A,C
Universal containers recently migrated legacy contracts and subscriptions into salesforce in order to facilitate amendments and renewals in CPQ .however ,sales user share getting the `attempt to de- reference a null object' error when amending the legacy contract. what is the most likely cause for the error?
Answer(s): C
When Salesforce CPQ attempts to amend a contract, it relies on a very specific set of fields on:ContractSubscriptionAsset (for asset-based models)Quote Line (for amendment and renewal linkage)If mandatory amendment fields are missing, CPQ's amendment engine will throw errors -- most commonly:"Attempt to de-reference a null object"This happens because CPQ expects certain relationships and data points that do not exist in legacy- migrated records unless populated correctly.Why C is the correct answerWhen migrating historical Contracts and Subscriptions, CPQ requires certain fields to be populated, such as:AccountStartDateEndDateContract NumberPricebook2IdContracted = TRUEContractIdProduct2IdQuantityStartDateEndDateListPriceSalesPriceSubscriptionTypeStatus = ActiveTermStartDateTermEndDateMost importantly:OriginalContractedListPriceOriginalContractedSalesPriceOriginalQuantityOrderProductId (for order-based renewals)AssetId (required depending on renewal model)Contract Required FieldsSubscription Required FieldsIf any of these fields are missing or incorrectly mapped, the amendment engine fails.CPQ amendment logic does not require a source quote line for legacy migrations, nor does it block amendments on migrated data if all required fields are present.Thus C is the only answer consistent with CPQ documented behavior.Why the other answers are wrongA. Migrated contracts and subscriptions cannot be amended using Salesforce CPQIncorrect.Salesforce CPQ fully supports amendment of migrated contracts/subscriptions as long as the required data is populated.B . Amendment requires asset-based renewal methodIncorrect.Legacy migrations can use either:Contract-Based Renewal, orAsset-Based RenewalThere is no requirement to switch to asset-based renewal.D . Legacy data missing lookup to source quote lineIncorrect.A lookup to the original Quote Line (SBQQ__QuoteLine__c) is not required for amendments.It is only needed to support:Contracted pricing logic reuseCertain renewal pricing behaviorsSome reporting use casesMissing this field does not block amendments and does not cause this error.
A revenue cloud user story states "Sales users should have the ability to create new quotes with established rate cards and account specific discounts because current customers are entitled to the pricing that was originally negotiated'' .in addition to loading data to accounts, contracts, quotes what other object will need to absorb legacy data?
Answer(s): A
The user story states that sales users should inherit previously negotiated pricing when quoting for existing customers.In Salesforce CPQ, the object that stores account-specific negotiated prices is:Contracted Pricing (SBQQ__ContractedPrice__c)This object overrides standard list prices during quoting based on:AccountProductPricebookContract linkageTherefore, in addition to migrating Accounts, Contracts, and Quotes, the missing legacy pricing data must be loaded into Contracted Pricing.
What does the `safe harbor' slide at the beginning of every salesforce presentation means?
Answer(s): E
The Salesforce Safe Harbor statement exists to remind customers:They should only make scoping, planning, design, and purchasing decisions based on current, available functionality, not forward-looking statements or roadmap presentations.Salesforce does not guarantee:Release timingExact feature deliveryBackward compatibility
The order management plugin functionality allows the architect to override which of the following default package behavior in salesforce CPQ?
Answer(s): D
The Order Management Plugin (OrderPlugin2) in Salesforce CPQ allows architects to override the default behavior of CPQ when generating Orders from Quotes.According to CPQ developer documentation, the plugin can override:Order start dateOrder end date logic (in limited ways)Order product behaviorsThe key supported override is specifically:Setting the Order Start Date programmatically
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.