Last updated on SEPTEMBER 20, 2017
Applies to:Oracle Order Management - Version 12.1.1 to 12.2.4 [Release 12.1 to 12.2]
Information in this document applies to any platform.
*** Updated 3-24-2015 ***
Customer is "make to order" so orders on hold or entered status must NOT be
scheduled - to avoid producing orders that may not materialize until later
(or never). 90% of customers require "ship complete", so ship sets default
from customer master.
Current functionality defaults ship set from customer master as desired, but
then on Save, lines are scheduled and thus visible to production prior to
booking of order (as confirmation of details) or release of credit check
failure hold. Production then sees the order immediately and begins
The workaround is to MANUALLY remove the ship set (and any scheduled dates)
on such orders - there is a great potential for error with this process.
Support File Enhancement request: <Bug 4241385> - ship set lines are scheduled when saved.
The fix is included in 12.1.3 and higher.
A new system parameter "OM:Auto Schedule Sets" is provided through this patch.
The value of the system parameter decides whether lines that are being added to a ship/arrival set will be scheduled automatically or not.
If the value of the system parameter "OM:Auto Schedule Sets" is set to "No",
lines that are part of a ship/arrival set need not necessarily be scheduled.
However, at any given point of time, all the lines in a ship/arrival set, will be either scheduled or unscheduled.
Instead, if the value of the system parameter "OM:Auto Schedule Sets" is set to "Yes" or not set at all, the existing behaviour, where "lines that are part of a ship/arrival set" need to be scheduled", will be retained.
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