My Oracle Support Banner

FA: SCM: OM: Enhancement Request for Hold Functionality. (Doc ID 2731920.1)

Last updated on DECEMBER 06, 2020

Applies to:

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


This note describes business requirements to enhance existing Hold Functionality.

Use Case and Business Need:

  1. Allow orchestration to flow while on hold, and just prevent a specific task (ie. shipping). For example if we place a line on hold right as it is scheduling, it will allow sourcing, trans planning, PO/WO creation, but prevent the line from shipping (via ship confirm or ASN). This will allow us to manage our holds much more accurately.
  2. Allow for reschedules/revisions while on above hold. Be able to adjust dates or other data on the line, and have the line flow back through orchestration but still prevent ship and remain on hold.
  3. Further definition of drop-ship requirements: Desire is "No-Ship Hold" that allows sales order line and PO to remain changeable, but just prevents ASN. It does not place the PO on hold/freeze or SO line on hold, but is an indicator to cause ASN to fail when it is attempted.
    1. Drop-ship line is booked and PO is created.
    2. Line is placed on "No-Ship" hold that prevents ASN.
    3. OM change allowed (reschedule, ship method, etc...) and change flows to PO while still not allowing ASN the entire time.
    4. PO change allowed (price, buyer, etc...) and does not cause revisions to become out of sync between PO and OM.
    5. While making these changes, no ship hold remains constant (no new hold released or applied).
    6. When no ship hold is released, PO can do ASN.


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

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