You are here:
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.
Did this article solve your issue?
Let us know so we can improve!
