The sales team at Universal Containers (UC) has received customer feedback that numerous lines on a typical Quote make it difficult to understand how the total amount breaks down across the various types of Products: Hardware, Software, and Professional Services. UC uses Quote Templates to generate Quote Documents.
Which solution would allow customers to see separate tables and subtotals organized by Product Family?
Requirement Overview:
Universal Containers wants to show Quote Line items grouped by Product Family with subtotals for each family in Quote Documents.
Solution Details:
Salesforce CPQ allows grouping of Line Items in Quote Templates.
Setting SBQQ__ProductFamily__c as the Group field organizes the Quote Lines into separate sections for each Product Family.
Configuration Steps:
Navigate to the Quote Template.
Create a new Line Items Section.
In the Grouping field, set SBQQ__ProductFamily__c.
Save and test the template by generating a Quote Document.
Validation:
Confirm that the generated document displays separate tables for Hardware, Software, and Professional Services, with subtotals for each group.
An admin has set the Group ReW on one of the Quote templates. On output documents on Quote A, Quote Lmes appear to be grouped incorrertfy.
What are two explanations for this grouping?
Choose 2 answers
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 .
Universal Containers sells a nonrenewable subscription Product that is priced on a yearly basis.
Which Subscription field values should the admin set to meet this requirement?
Requirement Overview:
A nonrenewable subscription Product priced annually.
Key Field Configurations:
Subscription Term = 12: Specifies an annual subscription.
Subscription Type = One-Time: Indicates that the Product is nonrenewable.
Subscription Pricing = Fixed Price: Defines a flat annual price.
Steps to Configure:
Navigate to the Product record.
Update the fields as specified above.
Save and test by adding the Product to a Quote.
Validation:
Confirm the subscription term and pricing are applied correctly and the product does not renew automatically.
What is the correct order of data import to load Products and Product bundles in CPQ?
In Salesforce CPQ, importing data for products and bundles requires a specific order to ensure referential integrity, as certain objects depend on others being present. The correct sequence starts with the Product (the parent record), followed by Product Features (defining sections or categories within the bundle), Product Options (specific selectable items under features), Option Constraints (rules governing option selections), and finally Configuration Attributes (additional settings for dynamic configuration). Option A reflects this hierarchical dependency accurately. Option B includes unrelated objects like Product Action and Error Conditions, which pertain to rules rather than bundle structure. Option C starts with Product Option before Product, which violates dependency rules since options require a parent product. Option D begins with Product Features before Product, which is incorrect as features need a product to associate with. Salesforce CPQ documentation emphasizes this order for successful data imports.
An Admin wants to generate one Asset record for each Quantity of a new Product. Currently, zero Asset records are generated for this Product when included on Quotes that are Contracted.
Which setting should the Admin change to meet the business requirement?
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.
Frank Hernandez
14 days agoEdward Green
1 month agoGary Martin
1 month agoBundle Configurations Wilson
2 months agoProduct Selection Taylor
17 days agoPricing Williams
1 month agoRonald Clark
3 months agoKaren Cooper
2 months agoBetty Thomas
2 months agoLinda Young
2 months agoMichelle Roberts
3 months agoAshley Adams
2 months agoHeike
3 months agoVeronique
3 months agoChandra
4 months agoShad
4 months agoViki
4 months agoIn
5 months agoAnglea
5 months agoHui
5 months agoCarlee
5 months agoJustine
6 months agoDeeann
6 months agoKenia
6 months agoVernell
6 months agoSalena
6 months agoMa
7 months agoDonette
7 months agoMarshall
7 months agoHenriette
7 months agoEugene
8 months agoFelix
8 months agoKeshia
8 months agoRenea
8 months agoKeneth
9 months agoKristin
9 months agoReena
9 months agoWinfred
9 months agoLuke
10 months agoVeronique
10 months agoLai
10 months ago