Last updated on JANUARY 27, 2017
Applies to:Oracle Fusion Distributed Order Orchestration - Version 126.96.36.199.1 and later
Information in this document applies to any platform.
NOTE: This note applies to Release 9 and lower, for later releases review - Using Webservices to Apply and Release Holds in Order Management (Doc ID 2227679.1)
When applying a hold to an existing orchestration order in Distributed Order Orchestration using the 'DooDecompOrderDetailSvcComposite/client_RequestHold' service the following behavior is observed:
1. A generic hold is defined which does not "hold" tasks in progress.
2. When the hold is applied using the above web service, it puts all tasks in progress on hold.
3. In the DOO workbench, the user has an option of specifying whether the tasks in progress are to be put on hold or not. However, the web service by default puts all such in progress tasks on hold.
The requirement is to "Not" hold in-progress tasks. The behavior through web service should be the same as observed via the Workbench.
Sign In with your My Oracle Support account
Don't have a My Oracle Support account? Click to get started
My Oracle Support provides customers with access to over a
Million Knowledge Articles and hundreds of Community platforms