Familiarize yourself with specific requirements for using the field and price amendments
feature to update asset details and adjust pricing effectively. Understanding these technical
mappings and supported fields makes sure that your amendments accurately reflect in asset state
periods (ASPs) and audit trails.
Required Editions
Available in: Lightning Experience
Available in: Enterprise, Unlimited, and Developer Editions of
Revenue Cloud where Transaction Management is enabled
Implementation Considerations
The Field Amendments feature supports
bundles, derived pricing products (DPPs), and usage-based products. Note these technical
requirements for field mapping and behavior.
Field Mapping Complexity: Mapping custom fields between order line items, assets, and
amendment quotes require context definition mappings.
Mapping Execution: The system applies mappings during order assetization to create or update
asset-related objects. This process also applies mappings when you create an amendment quote or
order.
Identification of Changes: The feature identifies field amendment differences by comparing
field values on the quote line item (QLI) or order item (OI) against the ASP.
ASP Versioning: ASPs created before the Winter '26 release show field value differences
between the Asset Action Source (AAS) and the ASP. This discrepancy results in the creation of
field amendment actions for line items even without manual changes.
Value Sourcing: During amend, renew, or cancel (ARC) actions, the transaction pulls field
values from the ASP record. However, the QLI Legal Entity field maps to and retrieves its value
from the AAS field for ARC actions. The system references non-custom field values, including
the start date, from the most recent AAS.
Pricing Constraints: The system doesn’t support setting a new list price, unit price, or
sales price as a field amendment.
Quote Line Distributions: The system doesn’t support amendments that update fields on the
Quote Line Item (QLI) distribution.
Supported Fields
The system supports specific fields for field-level
and price-only modifications.
Product Support: The Price Only Amendments feature works on bundles and usage-based
products.
Derived Pricing: The system supports price amendments for a derived pricing product (DPP)
when a contributing product's price changes. This process maintains existing behavior for DPPs.
Transaction Limits: Price amendments don’t apply to renewals or cancellations.
Did this article solve your issue?
Let us know so we can improve!
Loading
Salesforce Help | Article
Cookie Consent Manager
General Information
Required Cookies
Functional Cookies
Advertising Cookies
General Information
We use three kinds of cookies on our websites: required, functional, and advertising. You can choose whether functional and advertising cookies apply. Click on the different cookie categories to find out more about each category and to change the default settings.
Privacy Statement
Required Cookies
Always Active
Required cookies are necessary for basic website functionality. Some examples include: session cookies needed to transmit the website, authentication cookies, and security cookies.
Functional Cookies
Functional cookies enhance functions, performance, and services on the website. Some examples include: cookies used to analyze site traffic, cookies used for market research, and cookies used to display advertising that is not directed to a particular individual.
Advertising Cookies
Advertising cookies track activity across websites in order to understand a viewer’s interests, and direct them specific marketing. Some examples include: cookies used for remarketing, or interest-based advertising.