My Oracle Support Banner

FA: SCM: OM: Why is the Change Order Not Generating Orchestration Message For Downstream Fulfilment System? (Doc ID 2695893.1)

Last updated on MARCH 28, 2024

Applies to:

Oracle Fusion Order Management Cloud Service - Version 11.13.20.04.0 and later
Information in this document applies to any platform.

Symptoms

On : 11.13.20.04.0 version, Order Management Setup

Why is the Change Order Not Generating Orchestration Message For Downstream Fulfillment System?

Whenever the order is revised or there is an Update, Cancel or Apply Hold the orchestration process is not sending the request to the downstream fulfillment system,  instead the lines gets stuck in Change Pending with an error as below.

Service getCompensationPatternForStep in the Product Services API failed for orchestration process 3000000xxxxxxxx. (DOO-2685659) Details: A failure occurred in one of the Product Services API. A Product Service is
an orchestration API that runs when another Oracle Fusion application calls the orchestration API.

The issue can be reproduced at will with the following steps:

1. Sales Order XXX is created with two lines and Line EFF value as 100.
2. Save and Submit. The messages are sent to downstream fulfillment system and then accepted by the same.  Order moves to Processing status.
3. Revise the order to update the fulfill Line EFF value from 100 to 150. This EFF is part of the compensation pattern.
4. Submit the revision.

 

Changes

 

Cause

To view full details, sign in with your My Oracle Support account.

Don't have a My Oracle Support account? Click to get started!

In this Document
Symptoms
Changes
Cause
Solution
References


My Oracle Support provides customers with access to over a million knowledge articles and a vibrant support community of peers and Oracle experts.