You are here:
Considerations for Ramp Deals
This topic details known considerations and limitations for the Ramp Deals feature.
Required Editions
| Available in: Lightning Experience |
| Available in: Enterprise, Unlimited, and Developer Editions of Agentforce Revenue Management with the Revenue Cloud Growth, Revenue Cloud Advanced, and the Revenue Cloud Billing licenses. |
Ramp Deals for Lines
- Transaction Management supports ramp deals for term-defined products. You can’t use bundle products.
- You can't renew a ramp deal before its end date.
- You can't create a price-only amendment for a ramp deal.
- You can configure up to 10 ramp segments per-transaction line.
- Uneven subscription terms round to full years—remaining months go in the last segment with prorated pricing.
- Transaction lines require start and end dates.
- No gaps or overlaps between segment start and end dates.
- In an initial sale, you can edit the start date of the first annual ramp segment.
- After you configure and save ramp segments on a transaction line, you can't change the start and end dates of the transaction line.
- When you create an amendment transaction, you can't add or delete ramp deals.
- In an amendment transaction, the Ramp Deal window shows the changes in the total price of the transaction.
- Generated quote PDFs that include ramp deals don't show any difference between the ramped transaction lines and other transaction lines.
Ramp Deals for Groups
- Transaction Management doesn't create ramps for all products in group ramp segments.
Instead, it creates a separate asset for each quote line item for these products:
- Products with One Time and Evergreen product selling models.
- Bundled products where the root product has the One Time or Evergreen product selling model.
- Bundled products with a default One Time or Evergreen child product that use Proportional quantity scaling.
- Derived pricing products aren't supported—their prices don't calculate correctly if you add them to a ramp deal for groups.
- With only Ramp Deals for Groups enabled (Multiple Ramp Schedules off), create only 1 ramp schedule per transaction. The ramp schedule is implicit—the entire transaction is part of a single ramp schedule.
- When Multiple Ramp Schedules Per Transaction is turned on, you can create up to 10 ramp schedule groups in a quote or order.
- You can create up to 12 group ramp segments in a ramp schedule.
- After converting a group into a ramp segment within a schedule, you can clone the ramp segment to add more segments. You can't convert any other group within the schedule into a ramp segment.
- When you turn on Multiple Ramp Schedules Per Transaction, you can't add non-ramped groups within ramp schedule groups.
- You can't create a group ramp schedule for groups that contain child groups.
- You can't create nested groups in group ramp segments.
- You can't apply renewal price uplifts tied to the Consumer Price Index (CPI) to ramped products.
- You can't create ramp deals for groups and ramp deals for lines in the same quote or order.
Product Configuration in Ramp Deals
- For line-level ramps, configuration stays consistent across all ramp segments.
- For group-level ramps, most configuration changes you make in a ramp segment apply
to the current and subsequent segments. Previous segments remain unchanged to preserve
data integrity.
- Root or component quantity updates apply only to the current segment and don't propagate to other segments.
- If you include or exclude a child product within a bundle in one segment that changes also propagates to all subsequent segments. If you remove a child product from a segment while it remains included in previous segments, you can't add it back again in subsequent segments—this prevents gaps in the ramp schedule.
- Attribute changes made to a child product propagate only to the subsequent segments where that child product is included.
- Configuration rules override your manual ramp segment configurations and evaluate for each segment.
- Configuration rules don't recognize quote or order groups. Rules that add standalone products to a ramp segment don't automatically ramp them or add them to subsequent segments. However, this behavior doesn't affect child products of a ramped parent product. When a rule adds a child product to an previously ramped parent, it also ramps the child product and adds it to subsequent segments.
- You can't ramp parent-bundled products that contain a default One Time or Evergreen child product with the Proportional quantity scaling method.
Amend, Renew, and Cancel Ramped Assets
- With Ramp Deals for Groups enabled, amending, or canceling ramped assets automatically creates groups.
- Single Ramp Schedule (Groups ON, Multiple OFF): Amend multiple ramped assets in a single transaction only if the start and end dates of all their asset state period (ASP) records match. Don't add or delete ramp segments during amendments.
- Multiple Ramp Schedules (Groups ON, Multiple ON): Amend multiple ramped and non-ramped assets in one transaction, even if their ASP start and end dates don't match. Transaction Management groups assets into a ramp schedule when the asset lifecycle and all ASP dates match. Don't add or delete segments for existing assets. However, you can create group ramp schedules on amendment, renewal, and cancellation quotes or orders to generate other ramp deals.
- You can't change the start and end dates of auto-generated segments. To make structural changes, create a separate amendment.
- During the renewal of a ramped asset, the price uplift from the final segment becomes the renewal uplift.
- You can't use these capabilities when amending, renewing, or canceling ramped assets: lot-based renewal, asset transfer, early renewal (except via the dedicated early renewal flow), and rolling back the most recent amendment.
Dynamic Revenue Orchestrator (DRO) and Ramp Deals
- Turn on the rampDealForQocal setting in your org and make sure that your order line items include ramp and segment identifiers.
- For amend, renew, and cancel orders. DRO applies the same order action to all segments, even if a specific segment hasn't changed. DRO applies order line item actions to fulfillment order lines and processes them.
- DRO skips Staged Assetize steps in ramp order fulfillment plans and assetizes all segments at plan completion.
Did this article solve your issue?
Let us know so we can improve!
