Revenue Cloud Advanced : Amending Ramped Assets Fails with Amendment Date or Multi-Year Term Error

Review the applicable cause below and complete the related steps.

Cause 1: Amendment date is earlier than the latest Asset State Period segment start date

The amendment date must be the same as or later than the start date of the latest Asset State Period segment for the asset being amended.

1. Open the ramped Asset record.
2. Go to the Related tab.
3. Open the related Asset State Periods.
4. Identify the Asset State Period with the latest Start Date for the asset being amended.
5. On the amendment quote, set the amendment date to the same date as, or later than, the latest Asset State Period Start Date.
6. Save the amendment quote.
7. Re-run the amendment.

If the business requirement is to amend an earlier period, review whether later amendments must be handled first. For ramped assets, the amendment date must not be earlier than the start date of an upcoming amendment or renewal.

Cause 2: Multiple ramped assets are amended together with mismatched Asset State Period dates

When Multiple Ramp Schedules is turned off, all ramped assets amended in the same transaction must use matching Asset State Period dates.

1. From Setup, go to Revenue Settings.
2. Open Transaction Management Settings.
3. Review the Ramp Deals for Groups in Quotes and Orders setting.
4. Review the Multiple Ramp Schedules setting.
5. If Multiple Ramp Schedules is turned off, confirm that the Start Date and End Date values on all Asset State Period records match across the assets being amended in the same transaction.
6. If the Asset State Period dates do not match, amend the assets in separate transactions, one ramp schedule at a time.
7. If the business process requires amending ramped and non-ramped assets together, or amending assets with different ramp schedules together, enable Multiple Ramp Schedules.
8. Confirm that Ramp Deals for Groups in Quotes and Orders is also enabled.
9. Save the setting changes.
10. Reproduce the amendment.

Cause 3: Migrated Asset State Period or Asset Action Source records are missing required fields

For migrated ramped assets, the related asset records must include the required lifecycle, ramp, and pricing information needed by Transaction Management.

The Segment Identifier and Ramp Identifier fields on Asset State Period are system-populated and are not directly editable. These values are populated by Transaction Management when the ramp schedule is created through supported processes.

If migrated records were created through direct data load or direct DML and the ramp metadata is missing, recreate the asset chain using the supported migration sequence so the system can populate the required ramp metadata.

1. Review the migrated asset data.
2. Confirm that the asset chain was created in the supported sequence, such as:
   • Asset
   • Asset Action
   • Asset State Period
   • Asset Action Source
   • Asset Relationship
3. On each migrated Asset Action Source record, confirm that the following fields are populated:
   • List Price
   • Net Unit Price
   • End Date
   • Period Boundary
   • Price Book Entry ID
4. On each migrated Asset record, confirm that Has Lifecycle Management is set to True.
5. Confirm that Lifecycle Start Date and Lifecycle End Date are populated.
6. Confirm that lifecycle dates use the expected DateTime format.
7. On each Asset Action record, confirm that Category Enum is populated.
8. Confirm that the applicable total amount field is populated, even if the value is 0. Depending on the transaction type, this may include:
   • Total Initial Sale Amount
   • Total Renewals Amount
   • Total Cancellations Amount
   • Total Upsells Amount
   • Total Downsells Amount
9. Correct any missing data.
10. Re-run the amendment.

Cause 4: Amendment works in one sandbox but fails in another

If the amendment works in one sandbox but fails in another, compare the Transaction Management, product, and customization settings between the environments.

1. In each sandbox, go to Setup.
2. Open Revenue Settings.
3. Open Transaction Management Settings.
4. Compare the following settings between the working and failing sandbox:
   • Ramp Deals for Groups in Quotes and Orders
   • Multiple Ramp Schedules
5. Go to Setup > Object Manager > Product.
6. Compare the ramp-related product configuration between sandboxes, including:
   • Term length
   • Segment count
   • Selling model
   • Subscription or ramp-related fields
7. Compare active product validation rules between the environments.
8. Compare active pricing rules between the environments.
9. Compare any custom quote calculation logic or Quote Calculator Plugin code between the environments, if applicable.
10. If a validation rule or customization enforces a specific multi-year term in one environment, either update the amendment data to meet that requirement or align the customization with the working environment.
11. Save any required changes.
12. Reproduce the amendment.

Verification:

After completing the applicable resolution steps:

1. Open the amendment quote for the previously failing ramped asset.
2. Confirm that the amendment date is the same as or later than the latest Asset State Period start date.
3. Confirm that all ramped assets amended in the same transaction have compatible Asset State Period dates, or that Multiple Ramp Schedules is enabled when required.
4. Save the amendment quote.
5. Confirm that the amendment completes without either of the following errors:
   • “We couldn't amend the asset because the amendment date provided is earlier than the start date of an upcoming amendment or renewal.”
   • “Amendment Error: Can Only Sell Multi-Year Deal with a 3-Year Term.”

If the amendment quote saves successfully and the ramped asset is amended as expected, the issue is resolved.