My Oracle Support Banner

Schedule Arrival Date Behaviour When Doing Multiple Reschedule Actions (Doc ID 2913652.1)

Last updated on FEBRUARY 10, 2023

Applies to:

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

Goal

Scenario

1. Create a sales order line with demand class 'Spare Parts ' and schedule it -> since there is enough supply, the Customer Request date can be fulfilled;
Schedule arrival date = 03-Nov-2022.

2. Change the demand class to 'Stock' -> Allocated supply is not sufficient, so the sales order line automatically gets rescheduled when saved, the Schedule Ship and Arrival dates are pushed out to reflect the "new" availability;
Schedule arrival date = 19-Dec-2022.

So far this works as expected.
The issue is when:

3. The demand class is switched BACK to 'Spare Parts '' -> the availability goes up again, as there is more supply allocated to this demand class.
However this doesn't happen; Schedule arrival date = 19-Dec-2022

The expected behavior would be the same as in 2., meaning the line should be rescheduled, to adjust to the "new" available supply.

Order Management sent to ATP - REQUEST ARRIVAL DATE 19-DEC-22 - not the original request arrival date of 03-NOV-22 and that is why we did not see the line rescheduled to an earlier date.
Why did Order Management send a date for December?

In ATP session file it is displayed that Order Management sent a request date of 19-DEC-22

Call_ATP_No_Commit: p_atp_rec.requested_arrival_date : 19-DEC-22 

Solution

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
Goal
Solution
References


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