---
schema_version: "1"
id: 6adc3a110c646250162a788cb54f52ec1ee67cde96b533236cb53e976ea9ac25
title: Considerations to Decouple Decomposition and Orchestration Processes
collection: admin
version: current
locale: en-us
portal_url: https://docs.salesforce.com/admin/current/en-us/ind/264-0-0/comms_t_order_management_process_separation_considerations.md
canonical_url: https://help.salesforce.com/s/articleView?id=ind.comms_t_order_management_process_separation_considerations.htm&release=264.0.0&type=5
source_site: help.salesforce.com
content_type: documentation
content_hash: 9069784f96a414363064a7c492e234da2fdb7e54de04299e8b2b284efb34bc34
description: Note the following considerations while designing flows to decouple decomposition and orchestration processes.
products:
  - Industry Solutions
  - Cross Cloud
release: "264"
---
# Considerations to Decouple Decomposition and Orchestration Processes

Note the following considerations while designing flows to decouple decomposition and orchestration processes.

- You can’t raise a supplemental order if the superseded order is still in either DECOMPOSED or SUBMITTEDFORFULFILMENT status. Ensure the existing order has a fully generated and active orchestration plan before attempting an amendment. This prevents amend-on-amend errors.
- Automated rollback for decomposition is not supported. If plan composition fails after a decompose-only step, the order remains in DECOMPOSED status and requires a manual initiation of the composePlan API.
- For the transition from Freezing to Frozen, the XOMSetup → ProvisionallyAcceptedOrderAsyncJobsCnt setting controls the process flow:
    - 0: Synchronous processing. This is the default value.
    - 1: Single asynchronous job.
    - 2: Two separate asynchronous jobs - one for decomposition, one for plan update.
- If you use custom integration procedures, note the following changes in the SimpleDecompositionController starting Spring ‘26.
    - decomposeOrder: Supports both base and supplemental orders. Calling this interface only decomposes the order.
    - startOrchestrationPlan: Use this interface specifically to trigger the plan update once you are satisfied with the decomposition. Now, it automatically detects if the order is supplemental and updates the existing plan accordingly.