Loading

Revenue Cloud DRO: Order Activation Does Not Generate Orchestration Plan or Fulfillment Order Products

Publish Date: May 21, 2026
Description

This article explains why activating an order in Revenue Cloud Dynamic Revenue Orchestrator (DRO) silently produces no orchestration plan and no fulfillment order products, and how to resolve it.

 

After clicking Create Order from a quote and changing the order status to Activated, the expected decomposed line item (for example, a fulfillment order product such as "Qt Named License") is not created, and no error is surfaced in the UI.

 

In some orgs the same activation flow generates a plan for one quote (for example, a quote with fewer than 5 lines) but not another (for example, a quote with 60+ lines), indicating the submit-to-DRO automation, decomposition scope, or orchestration scenario does not apply to every product on the larger order.

 

Technical Background

 

DRO requires that the following prerequisites are met for successful orchestration plan generation:

 

1. The Submit Order action (submitOrder) is invoked on activation

2. The fulfillment workspace (FulfillmentWorkspace) is in an Active state

3. The products on the order map to a published orchestration scenario

4. The rampDealForQocal setting is enabled for ramp deals

 

If any of these prerequisites is missing for a given product, decomposition silently skips that product and no orchestration plan is composed.

 

Resolution

Cause 1: Submit Order Action is Not Invoked on Activation

 

Diagnosis Steps:

 

1. Navigate to Setup > Flows

2. Locate the record-triggered flow that submits orders to DRO on activation (typically named "Submit Order on Activation" or similar)

3. Verify the following:

   • Flow is Active

   • Entry criteria matches:

      • Order (Order) Status (Status) equals "Activated"

      • Order has at least one Order Product (OrderItem)

   • Flow calls the Submit Order (submitOrder) invocable action with:

      • fulfillmentAdapter set to "StandardOrder"

      • salesTransactionId set to the activated Order Id

Resolution:

 

If the flow is missing or inactive, create or activate it per "Automate order submission to DRO using record-triggered flows" in the DRO Basic Setup documentation.

 

Cause 2: Fulfillment Workspace is Not Active or Does Not Cover the Products on the Order

 

Diagnosis Steps:

 

1. From the App Launcher, open Fulfillment Workspaces

2. Open the workspace configured for the affected products

3. Verify:

   • Status is set to Active

   • Workspace is Published

4. Navigate to Setup > Fulfillment Designer > Orchestration Scenarios

5. Verify that every commercial product on the failing order is mapped to an orchestration scenario

6. Confirm the scenario specifies:

   • The product entity

   • The order action "Add" (or the action matching the order, such as Modify, Disconnect)

 

Resolution:

 

If the larger quote (60+ lines) contains products not present in the smaller quote, add or extend an orchestration scenario so every product on the order is covered.




Knowledge Article Number

005384994

 
Loading
Salesforce Help | Article