Last updated on JULY 19, 2017
Applies to:Oracle Order Management - Version 12.1.3 and later
Information in this document applies to any platform.
On : 12.1.3 version, Scheduling and Sourcing
We have a situation with an internal order line that has a schedule ship date in the past.
Running the schedule orders concurrent program (SCHORD) in the mode "Reschdule using Request Date" doesn't adjust the scheduled ship date to the current availability.
Expectation is that the order line would use ATP info and make the scheduled ship date current.
ATP Data Collections runs dailing in Production.
The order in Production is now shipped, but customer has the same order 5281540 in Dev instance that was cloned on January 19th.
The issue can be reproduced at will with the following steps:
1. Order Management Responsibility
2. Run 'Schedule Orders Program' with parameters:
order_number_low = 5281540
order_number_high = 5281540
sch_mode = RESCHEDULE_RD
3. Results: line 59.4 still has no current SSD updated:
CREATE DATE REQUEST DATE SCHED DATE
13-JAN-14_19:11:47 30-DEC-13_23:59:00 24-DEC-13_23:59:00
4. ATP Availability pop-up on the line shows a different 'available date' (March 10 2014)
Sign In with your My Oracle Support account
Don't have a My Oracle Support account? Click to get started
Million Knowledge Articles and hundreds of Community platforms