Explanation (150-250 words)
In Salesforce Billing, when an order product is activated, the system automatically creates a Billing Schedule Group (BSG) to manage all associated Billing Schedules (BSs). The BSG acts as the controlling record that connects multiple BSs generated for the same order product-whether from the initial order or from subsequent amendments.
When an amendment increases product quantity, Salesforce Billing does not create a new BSG; instead, it adds new BSs under the existing BSG. This design ensures that all billing activities for that product line- original or amended-are tracked within one consistent group.
Each Billing Schedule (BS) defines when and how much to bill, while the BSG provides a unified structure for reporting, synchronization, and downstream billing actions (e.g., invoicing, revenue recognition).
Thus, the persistence of the same BSG across amendments reflects correct and expected system behavior- ensuring billing continuity, preventing duplicate invoicing, and maintaining a single view of all schedules related to one order product.
Exact Extracts from Salesforce Revenue Cloud (Billing Implementation Guide):
* "A Billing Schedule Group (BSG) acts as a container for all Billing Schedules associated with the same order product. When amendments occur, Salesforce Billing generates new Billing Schedules under the existing Billing Schedule Group."
* "Billing Schedules define the timing and amounts to bill, while Billing Schedule Groups maintain continuity across amendments and changes." References (document/source names only; no URLs):
* Salesforce Billing Implementation Guide - Billing Schedules and Billing Schedule Groups
* Salesforce Billing Implementation Guide - Amendments and Schedule Regeneration
* Salesforce Revenue Cloud Data Model - Order Product to Billing Schedule Relationships

Comprehensive and Detailed Explanation From Exact Extract:
Salesforce Revenue Cloud introduces Change Orders as the standard mechanism for modifying activated orders.
From the Order Management section of Revenue Cloud documentation:
* "Assign the Place Change Order permission set to users who manage in-flight order changes."
* "Change Orders allow quantity increases or decreases after an order is activated." Superseded orders and supplemental orders serve different purposes and do not support general in-flight changes.
References:Revenue Lifecycle Management / Order Management Guide - Change Orders; Permission Set Definitions.

Comprehensive and Detailed Explanation From Exact Extract:
To manage assets in Revenue Cloud, two key requirements must be satisfied:
* The product must be marked as assetizable so that the system generates asset records after order activation.
* The createOrUpdateAssetFromOrder flow action (or the automated assetization engine) must run to actually create the asset records.
From Revenue Lifecycle Management documentation:
* "Only products configured as assetizable generate assets."
* "Asset management depends on successful assetization, which is performed via the createOrUpdateAssetFromOrder flow action or automated lifecycle processing." If assets are not generated, even a properly-permissioned user cannot view or manage them.
Why other options are incorrect:
* Customize Application is not required for asset visibility.
* Asset management does not require a CPQ Plus license; asset objects are part of standard RLM
/Revenue Cloud licensing, not CPQ Plus specifically.
References:Salesforce Revenue Lifecycle Management Implementation Guide - Assetizable Products; Assetization Process; createOrUpdateAssetFromOrder Action.

Explanation (150-250 words)
The Transaction Line Editor (TLE) in Salesforce Revenue Cloud provides a configurable grid interface for users to interact with Quote Line Items (QLIs). To display custom fields such as Estimated Delivery Date, administrators must explicitly add those fields to the Selected Fields list of the TLE component within the Quote Lightning Record Page.
This configuration determines which fields appear in the line editor and in what order. Adding fields to the Quote Line Item page layout (option C) does not affect TLE visibility because the TLE configuration operates independently of page layouts. Option B (enabling Instant Pricing) controls pricing recalculation frequency and is unrelated to UI field visibility.
Exact Extract from Salesforce CPQ Implementation Guide:
"To display a custom field in the Transaction Line Editor, add it as a selected field in the TLE component configuration on the record page where it appears." References:
Salesforce CPQ Implementation Guide - Transaction Line Editor Customization Salesforce Revenue Cloud Configuration Guide - TLE Field Selection and Layout Management Salesforce Solution Architect Handbook - Optimizing Line Editor User Experience

Exact Extracts from Salesforce Billing and Subscription Management Guides:
* "Monthly Recurring Revenue (MRR) represents the recurring portion of subscription revenue normalized to a monthly value."
* "For ramped deals, MRR should be calculated based on the currently active ramp period."
* "When a subscription includes quantity changes by period, MRR is (active period's quantity × list price) ÷ 12." Step-by-Step Reasoning:
* Current Date: January 15, 2026 # within Year 1 of the ramp (June 24 2025 - June 23 2026).
* Active Quantity: 20 units.
* List Price: $1,000 per year.
* MRR Formula:
* Why A is Correct:Uses current active ramp period only, not the entire 3-year term.
* Why Others Are Incorrect:
* B: Divides by total months (36) - incorrect for monthly normalization.
* C: Aggregates all ramp years, not just the current active one.
References :
* Salesforce Billing Implementation Guide - Recurring Revenue Metrics (MRR/ARR)
* Salesforce Subscription Management Implementation Guide - Ramp Deal Revenue Recognition and Active Period Logic