Let's see how Dynamic Revenue Orchestrator (DRO) uses time-awareness to decompose a
multi-year ramp deal into fulfillment order line items (FOLIs) and Fulfillment Asset State
Period (FASP) records that align with each year's effective dates.
Required Editions
Available in: Enterprise, Unlimited, and Developer
Editions
Consider a commercial product, Sales Cloud, that decomposes into SC-Business or SC-Enterprise
based on the Business attribute, and Tenant and License Provisioning. This example uses the
Business attribute, so only SC-Business is created.
Example
The customer purchases Sales Cloud in a 3-year ramp deal that starts January 1, 2026, with
license quantities increasing each year.
Year 1: 100 licenses
Year 2: 200 licenses
Year 3: 300 licenses
Without time-awareness, decomposition produces a single configuration with no effective
start or end dates. Later amendments overwrite past or future data and leave the asset in
an inaccurate state.
With time-awareness enabled, DRO generates FOLIs mapped to each effective date range.
DRO generates these FOLIs for each technical product:
SC-Business: Three FOLIs for 100, 200, and 300 licenses, one per year.
License Provisioning: Three FOLIs that match the ramping quantities across the
timeline.
Tenant: Three FOLIs that maintain a quantity of 1 across all three years. Because Tenant
has account scope, its quantity stays at 1 regardless of the license ramp.
Each FOLI produces an Add action because no prior Fulfillment Asset or FASP records existed
for these technical products on this account.
Because the FOLIs are sliced by time, DRO creates FASP 1, FASP 2, and FASP 3 for each FA.
This structure prevents data overwrites and makes sure that the asset configuration that is
active at any point in time drives orchestration.
Did this article solve your issue?
Let us know so we can improve!
Loading
Salesforce Help | Article
Cookie Consent Manager
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.