---
schema_version: "1"
id: 29a3ee1db7985d347508ed42607d0d03bc1afd6f2be200e933665bdb5d6aa884
title: Requirements for Creating Orchestration Plan Context Mapping
collection: admin
version: current
locale: en-us
portal_url: https://docs.salesforce.com/admin/current/en-us/ind/264-0-0/dro_orchestrate_non_sales_transaction_mapping.md
canonical_url: https://help.salesforce.com/s/articleView?id=ind.dro_orchestrate_non_sales_transaction_mapping.htm&release=264.0.0&type=5
source_site: help.salesforce.com
content_type: documentation
content_hash: 500dc471541388274fa0bfff7bde66dc46cc0cf025c2b9d8e2b4e13e0fe9a217
description: Create an orchestration plan context mapping entry to connect the business data in an object to the orchestration logic within Dynamic Revenue Orchestrator (DRO) by using the orchestration type. DRO includes the Generic orchestration type to orchestrate non-sales transaction objects.
products:
  - Revenue Cloud
release: "264"
---
# Requirements for Creating Orchestration Plan Context Mapping

Create an orchestration plan context mapping entry to connect the business data in an object to the orchestration logic within Dynamic Revenue Orchestrator (DRO) by using the orchestration type. DRO includes the Generic orchestration type to orchestrate non-sales transaction objects.

### Required Editions

<table class="slds-table slds-table_bordered slds-max-medium-table_stacked slds-m-bottom_small edition"><colgroup><col></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>

<table class="slds-table slds-table_bordered slds-max-medium-table_stacked slds-m-bottom_small permission">
      <colgroup>
        <col style="width:50%">
        <col style="width:50%">
      </colgroup>
      <thead class="slds-text-title_caps ">
        <tr class="">
          <th scope="colgroup" class="slds-cell-wrap" colspan="2" style="text-align:center;vertical-align:top;" id="d148757e61">User Permissions Needed</th>
        </tr>
      </thead>
      <tbody>
        <tr class="">
          <td data-label="User Permissions Needed" class="slds-cell-wrap" style="vertical-align:top;" headers="d148757e61 ">To create the custom context definition:</td>

          <td class="slds-cell-wrap" style="vertical-align:top;" headers="d148757e61 ">DRO Admin User</td>

        </tr>
      </tbody>
    </table>

Keep these considerations in mind when creating a mapping.

- Create one mapping entry for a specific object for DRO to orchestrate.
- Map an orchestration type to only one context definition to maintain an exclusive relationship between the orchestration process and its logic.
- Use the same orchestration type while creating the mapping as the usage type of the orchestration components.

![The page used to create an Orchestration Plan Context Mapping entry.](https://sf-zdocs-cdn-prod.zoominsoftware.com/tdta-ind-revenue-264-0-0-production-enus/91ca99c6-d5c8-4986-b961-c6b7801e0d0d/revenue/images/dro/dro_orchestration_plan_mapping.png)

Create the Orchestration Plan Context Mapping entry using these fields:

  
| FIELD NAME | REQUIREMENT | DESCRIPTION |
| --- | --- | --- |
| Object Name | Mandatory | The API name of the object for orchestration. |
| Context Definition | Mandatory | The context definition to be used for the object. |
| Context Mapping | Mandatory | The name of the context mapping to apply. |
| Root Node Name | Mandatory | The node name that represents the root in the context definition. |
| Item Node Name | Optional | The node name that represents an item in the context definition. |
| Orchestration Type | Mandatory | Select `Generic` orchestration type. |