---
schema_version: "1"
id: 9cd2636550e5e3b09eb0d34eb58d460afe0c61ccb1f849ff3e9289ade2724562
title: Cross-Plan Dependencies
collection: admin
version: current
locale: en-us
portal_url: https://docs.salesforce.com/admin/current/en-us/ind/264-0-0/dro_cross_plan_dependencies.md
canonical_url: https://help.salesforce.com/s/articleView?id=ind.dro_cross_plan_dependencies.htm&release=264.0.0&type=5
source_site: help.salesforce.com
content_type: documentation
content_hash: bad1155b73f8a5bcb0794f8ae2b75614ad22b96b8fb33a80732dd083522f262b
description: Cross-plan dependencies establish connections between steps in different fulfillment plans that are part of related orders. Use cross-plan dependencies when a step in one order's fulfillment plan relies on the completion of a step in a different order's fulfillment plan.
products:
  - Revenue Cloud
release: "264"
---
# Cross-Plan Dependencies

Cross-plan dependencies establish connections between steps in different fulfillment plans that are part of related orders. Use cross-plan dependencies when a step in one order's fulfillment plan relies on the completion of a step in a different order's fulfillment plan.

### Required Editions

<table class="slds-table slds-table_bordered slds-max-medium-table_stacked slds-m-bottom_small edition"><colgroup><col style="width:100%"></colgroup><tbody><tr class=""><td class="slds-cell-wrap" style="vertical-align:top;">Available in: <strong>Enterprise</strong>, <strong>Unlimited</strong>, and <strong>Developer</strong> Editions</td></tr></tbody></table>

For example, consider a scenario where the fulfillment plan for Product A contains a platform service activation step. The platform is provisioned as a part of the fulfillment plan for Product B. The two products are part of independent order fulfillment plans belonging to separate orders. Use cross-plan dependencies to make sure that the platform service activation step starts only after the platform provisioning step is complete.

## Fulfillment Plan Design

Prerequisites:

- Provide a unique Orchestration Group Key for Dynamic Revenue Orchestrator (DRO) to group related orders. The Orchestration Group Key points to an attribute defined under the Sales Transaction node.
- To establish ‌fulfillment plans that are grouped based on Orchestration Group Key, map context definitions to the Orchestration Group Key attribute. See [Create Custom Context Definitions for Order Orchestration](https://help.salesforce.com/s/articleView?id=ind.dro_steps_to_create_a_custom_context_definition.htm&language=en_US&type=5).

To design the fulfillment plan:

- In the Fulfillment Workspace, select Cross Plan scope while defining the dependency. See [Set Dependencies Between Fulfillment Steps](https://help.salesforce.com/s/articleView?id=ind.dro_set_dependencies_between_fulfillment_steps.htm&language=en_US&type=5).
- Organize fulfillment steps so that dependent steps in one plan wait for the steps they rely on in another plan to complete.
- Avoid bidirectional dependencies, where one plan is dependent on a second plan that, in turn, depends on the first. If you set up bidirectional dependencies, DRO doesn’t generate dependencies.

## Orchestration

During the fulfillment process:

- Access dependencies from the real-time plan view and open the related plans or steps to take action.
- Review steps that have cross-plan dependencies within the fulfillment plan. See [Monitor Decomposition During Fulfillment](https://help.salesforce.com/s/articleView?id=ind.dro_monitor_decomposition_during_fulfillment.htm&language=en_US&type=5).
- Submit orders in a specific sequence, so that orders with dependent steps are submitted later. For example, to activate a service before billing the customer, first submit the order with the Activate Service step, and then submit the order with the Bill Customer step.
- Take actions such as marking a step as complete and accessing plan and step dependencies from the External Dependencies tab. See [Orchestration Plan Actions and Information](https://help.salesforce.com/s/articleView?id=ind.dro_fulfillment_plan_actions_and_information.htm&language=en_US&type=5).

#### See Also

- [Import a Fulfillment Step Definition Group](https://help.salesforce.com/s/articleView?id=ind.dro_import_a_fulfillment_step_definition_group.htm&release=264.0.0&type=5 "To help scale your fulfillment plans, and ensure consistency across plans, you can import your existing fulfillment step definition groups directly from a fulfillment workspace.")
- [Set Dependencies Between Fulfillment Steps](https://help.salesforce.com/s/articleView?id=ind.dro_set_dependencies_between_fulfillment_steps.htm&release=264.0.0&type=5 "Connect fulfillment step definitions to create a dependency between them. When an order is submitted, the steps run in the order that you define.")