ATP Scheduling Results Are Wrong - GOP Plan Has Reservation Lines With ORDER_TYPE-100 That Appear Incorrect
Last updated on MARCH 08, 2017
Applies to:Oracle Global Order Promising - Version 22.214.171.124 and later
Information in this document applies to any platform.
126.96.36.199 or higher
Order was requested to ship on 05-FEB-16.
Due to item availability it had Schedule Ship Date calculated as 11-FEB-16. It was on a ship set so all lines had the same date.
Yesterday the order was fully reserved and ready to ship
Today we have decreased the quantity on line 5.1 from 80 down to 40.
The reservation for 40 remained, but now the entire order was rescheduled to 25-FEB-16.
This is not acceptable as the order is fully reserved, ready to ship and already overdue.
Reservations for inventory and hard reservations for ATO discrete jobs are both ignored when pegging is calculated, producing invalid ATP results.
The customer run DC and ATP 24x7 plan every 2 hours
We see that in MSC_DEMANDS we have records for same sales_order_line_id with origination -100 and 30
-- my understanding is that these -100 records should be removed during ATP plan run.
-- the sales order was not rescheduled and these lines persist after each plan run.
orig / using assembly_demand Date
-100 / 2/15/2016 9:02
30 / 2/25/2016 23:59
The ATP inquiry and /scheduling uses the sales order line information with origination -100
-- therefore we see sales order demand in bucket 15-FEB for 496 - because qty - 192 is having -100 line with date of 15-FEB
The ATP plan results show data per the origination - 30 - 25-FEB for these sales order lines
See file - sup-review_Requested_data_2.xlsx
Order is not rescheduled out
shipping on time is compromised
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