---
sourceDocument: Australia Sales and Order Management
sourceDocumentLink: https://servicenow-prod.fluidtopics.net/r/de-DE/order-management

 Release :

    - australia

ft:locale :

    - de-DE

ft:publication_title :

    - Australia Sales and Order Management

ft:clusterId :

    - omgmt

bundleId :

    - omgmt

workflow :

    - Customer and Industry


---

# Specification relationships and decomposition

# Create specification relationships, quantity mapping, and decomposition rules for Order Management {#ariaid-title1}

* Freigeben Version: Australia
* 
* Aktualisiert 12. März 2026
* 
* ![](https://www.servicenow.com/docs/portal-asset/ico-clock) 5 Minuten Lesedauer

Create the specification relationships and optional decomposition rules that define the associations between the product, service, and resource specifications for a product that you offer. These relationships impact how an
order is fulfilled for a customer.

## Vorbereitungen

Role required: sn_prd_pm.product_catalog_manager

## Warum und wann dieser Vorgang ausgeführt wird

Specification relationships define the relationships and associations between the product, service, and resource specifications. They designate how an order that contains the source specification is decomposed, fulfilled, and delivered to the customer. For example, if you have a product that you deliver through a service specification, you can designate that it is composed of three unique service specifications (product, service, or resource).  
Hinweis:  
The target product, service, or resource specification you select in the Target Specification field can be in any state, including a Draft state. The selected specification does not have to be published before selecting it in this field.

You can also select the characteristic options of the quantity characteristic for the specification relationship to provide the quantity of the target specifications. The order decomposition process refers to the mapped quantity
to decompose the order for the source specification and creates the required number of domain orders for the target specification.

If the quantity characteristic has a number as a characteristic option, the decomposition process refers to the characteristic option and creates the number of domain orders for the target specification.  
Optionally, you can create decomposition rules for the selected source and target specification relationships. The specification relationships can have product, service, or resource specifications as the source specifications.  
Hinweis:  
To learn more, see the following:

* [Order quantity support in Order Management](https://servicenow-prod.fluidtopics.net/FsGSo4G0Eb7erjqlB8i6fw "Learn how you can support and fulfill your customer orders for multiple instances of a product or service. You can create multiple domain orders that equal the order quantity for each instance of the product or service. This way, you can efficiently decompose and manage the fulfillment of your customer orders.")
* [Order decomposition](https://servicenow-prod.fluidtopics.net/jZsVFIhd4Y6I7WLtFdzjHg "Order decomposition is the process of breaking down an approved customer or service order into a set of smaller, manageable domain orders for fulfillment. This process is driven by definitions in the product catalog to ensure that all necessary components are provisioned correctly. Learn about the decomposition process for customer and service order and their differences.")
{#order-mgt-specification-rels__ul_htz_xmf_jsb}

## Prozedur

1. Open CSM Configurable Workspace.
2. Navigate to ListSpecifications and select a specification type.
   * Product Specifications
   * Service Specifications
   * Resource Specifications

   {#order-mgt-specification-rels__choices_qkd_rl1_kfc}  
   A list of specification records is displayed.
3. Select a record you want to modify.
4. Navigate to the Specification Relationships tab.
5. Select New.
6. On the form, fill in the fields.  
   {#order-mgt-specification-rels__table_ytw_wcr_4nb__entry__2}

   | Field | Description |
   |-|-|
   | Source specification | Product, service, or resource specification that you create the relationship from. For example, the source specification could be a product specification for an SD-WAN. |
   | Target type | Type of specification: * Product Specification * Service Specification * Resource Specification {#order-mgt-specification-rels__ul_lnm_lv5_1gc} |
   | Target specification | Specification that you create the relationship to. For example, the target specification could be a service specification for an SD-WAN. Hinweis: The target product, service, or resource specification you select can be in any state, including a Draft state. The selected specification does not have to be published before selecting it in this field. |
   | Mandatory | Option that designates if the relationship between the selected source and target specifications is mandatory and should always exist when a customer orders the product. * If selected, the target specification is always included with the source specification. During the ordering process,you must select the characteristics and characteristic values for the target specification. For example, if you are defining an SD-WAN Service Package, you designate that the SD-WAN Edge Device and SD-WAN Controller target specifications are mandatory. * If cleared, it is an optional target specification and is only included with the product if the customer selected it during the ordering process. For example, if you designate that the SD-WAN Security specification is optional, it's included in an ordered SD-WAN Service Package only if the customer selected it during the ordering process. {#order-mgt-specification-rels__ul_c4s_4xl_s4b} |
   | Relationship type | Type of relationship that designates how an order that contains the source specification decomposes for fulfillment after you receive and approve it. Composed of :   Source specification that is composed of the selected target specification. An order that contains the source specification and characteristics decompose into a single service order. Realized as :   Source specification that is realized as the selected target specification. Bundles :   Source specification bundles as the selected target specification. An order that contains the source specification and characteristics decompose into unique order line items for each of the target specifications bundled from that parent product specification. Requires :   Source specification that requires the selected target specification. To enable the delivery of the promised services in the specification, an order that contains the source specification and characteristics also requires the target resource specification. |
   | Order | Enter a numeric value that represents the order in which this relationship is applied, if there is more than one relationship. |
   | Minimum quantity | Required minimum number of specifications for an order. |
   | Default quantity | Default quantity if there is no selected amount. |
   | Maximum quantity | Maximum quantity of specifications. |
   | Quantity characteristic | Source specification characteristic that is used for quantity mapping. The quantity characteristic is supported only for a specification relationship in a product specification. |
   [Tabelle : 1. Specification Relationship form]

   {#order-mgt-specification-rels__table_ytw_wcr_4nb}
7. Select Save.

## Nächste Maßnahme

Optionally, create decomposition rules for selected specification relationships that have a product, service, or resource specification as the source specification. For more information, see: [52513233b2239858d2ee37aa2fbffeb853f20350.dita](https://servicenow-prod.fluidtopics.net/oDNMqUOltE~HeDVHNGHx5w#order-mgt-create-decomposition-rules "Define an optional decomposition rule that excludes the service specification when a customer does not select a specific option. You can create optional decomposition rules for specification relationships that have a product specification that you define as the source specification.").

## Create decomposition rules for specification relationships {#ariaid-title2}

Define an optional decomposition rule that excludes the service specification when a customer does not select a specific option. You can create optional decomposition rules for specification relationships that have a product
specification that you define as the source specification.

### Vorbereitungen

Role required: sn_prd_pm.product_catalog_manager

### Warum und wann dieser Vorgang ausgeführt wird

Decomposition rules enable you to exclude certain associated specifications when a product is decomposed during the ordering process. For example, an SD-WAN Edge device product specification contains different characteristic options, including routing and optional WAN optimization, as defined in its specification relationship. You can define a decomposition rule that excludes the service specification when a customer does not select an option. An example is WAN optimization. When the order is fulfilled, a service order does not generate for WAN optimization.  
Hinweis:  
Decomposition rules are only valid for a product specification. If you create attribute propagation maps, the following message appears when you try to create a decomposition rule that depends on a previously defined attribute-mapping rule:

The decomposition rule record (rule ID) will have dependency on the Attribute mapping rule (rule id). Update this record to avoid dependency on the attribute mapping rule.

To learn more about attribute mapping, see [9eb6eb97c8a4daf06b9117a49715bfe59b35d310.dita](https://servicenow-prod.fluidtopics.net/84jvi4jxFO8j_7AIDMwDhw "By defining attribute-mapping rules between two specifications in the product catalog, your fulfillment agents can access all relevant characteristic values in your product, service, and resource orders.").

Also, starting with the August 2025 release, fulfillment rules and how they're configured can be controlled by the
sn_prd_pm.enable_fulfillment_rules_with_condition_builder system property.

### Prozedur

1. In the CSM Configurable Workspace, select the List ![]() view.
2. Navigate to SpecificationsProduct Specifications and select the product specification to update.
3. In the Specification Relationships tab, select the Service Specification for which decomposition rules are to be set.  
   The Details tab with the Specification Relationship form opens.  
   Hinweis:  
   You can only create decomposition rules for specification relationships that have a product specification as the source specification.
4. Navigate to the Decomposition Rule tab.
5. In the Available columns section, select the characteristics that the customer does not order to trigger the exclusion rule.  
   For example, if you select a routing characteristic for an SD-WAN product, the exclusion rule triggers if the customer does not order a routing characteristic.
6. In the Conditions section, use the condition builder to select one or more conditions using the characteristic options for the characteristics selected in step 5, to trigger the exclusion rule.
7. Select Save.
{#order-mgt-create-decomposition-rules__steps_k1j_rwz_s4b}