---
schema_version: "1"
id: d2c2ac6799b5aec4eb4b5bb3865913fdf3fd96b2e423d3884f84bc6a89ceb34e
title: Define Technical Product Attribute Scope
collection: admin
version: current
locale: en-us
portal_url: https://docs.salesforce.com/admin/current/en-us/ind/264-0-0/dro_define_technical_attribute_scope.md
canonical_url: https://help.salesforce.com/s/articleView?id=ind.dro_define_technical_attribute_scope.htm&release=264.0.0&type=5
source_site: help.salesforce.com
content_type: documentation
content_hash: a99974a490bb1561a4180f398d90d1f60de799201915dd4f6aff3435bc8ad3dd
description: Use technical product attribute scopes to define the role of product attributes in decomposition and assetization. The scope determines whether attribute changes trigger fulfillment or supplemental actions on decomposed line items, or impact fulfillment assets. Defining these scopes at design time optimizes orchestration by processing only relevant updates and keeping asset data lean.
products:
  - Revenue Cloud
release: "264"
---
# Define Technical Product Attribute Scope

Use technical product attribute scopes to define the role of product attributes in decomposition and assetization. The scope determines whether attribute changes trigger fulfillment or supplemental actions on decomposed line items, or impact fulfillment assets. Defining these scopes at design time optimizes orchestration by processing only relevant updates and keeping asset data lean.

### 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: Both Salesforce Classic (not available in all orgs) and Lightning Experience</td></tr><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="d94372e69">User Permissions
              Needed</th>
          </tr>
        </thead>
        <tbody>
          <tr class="">
            <td data-label="User Permissions Needed" class="slds-cell-wrap" style="vertical-align:top;" headers="d94372e69 ">To define how a product decomposes:</td>

            <td class="slds-cell-wrap" style="vertical-align:top;" headers="d94372e69 ">
              <p>Fulfillment Designer</p>
              <p>OR</p>
              <p style="margin-bottom:0;">DRO Admin User</p>
            </td>

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

Dynamic Revenue Orchestrator provides these three predefined opt-out scopes.

  
| SCOPE NAME | ACTION | EFFECT |
| --- | --- | --- |
| Decomposition Action Opt-Out Scope | It determines if an attribute influences fulfillment actions during order decomposition. | Use the new product attribute scope to prevent technical attribute changes from affecting fulfillment line actions. When you define an attribute with this scope, technical values don’t influence fulfillment actions during order decomposition. |
| Supplemental Action Opt-Out Scope | It determines if an attribute influences supplemental actions during order decomposition. | Use the new product attribute scope to prevent technical attribute updates from affecting supplemental actions. When you define an attribute with this scope, technical changes don’t influence supplemental actions during order decomposition. |
| Assetization Opt-Out Scope | It determines if an attribute value a part of the fulfillment assets. | If you define an attribute with this scope, the attribute is excluded from the fulfillment asset. |

Define a product attribute mapped scope to associate one of the opt-out scopes to a product attribute. Note these considerations while creating product attribute mapped scopes.

- Create a decomposition action opt-out mapped scope for a product attribute before you create an assetization opt-out mapped scope.
- Delete the assetization action opt-out mapped scope for a product attribute before you delete the associated decomposition opt out mapped scope.
- Create and delete the supplemental action opt-out scope independent of the other two scopes.
- A product attribute can have only one mapped scope record per scope, allowing a maximum of three records—one for each predefined opt-out scope.

To create a product attribute mapped scope, perform these steps:

1. From the App Launcher, find and select **Dynamic Revenue Orchestrator**.
2. From the app navigation menu, select **Product Attribute Mapped Scopes**.
3. Click **New**.
4. Select **Associated Product Attribute** from the **Product Attribute Definition** or **Product Classification Definition** dropdown list.
5. Select a scope from the **Product Attribute Scope** dropdown list.
6. Save your work.
    
    ![Creation of a new product attribute scope.](https://sf-zdocs-cdn-prod.zoominsoftware.com/tdta-ind-revenue-264-0-0-production-enus/91ca99c6-d5c8-4986-b961-c6b7801e0d0d/revenue/images/dro/dro_products_attribute_mapped_scope.png)