PO Approved With Earliest And Latest Ship Dates In The Past (Doc ID 3021236.1)

Last updated on MAY 09, 2024

Applies to:

Symptoms

Both the API and MFCS UI, allows the PO to be approved even when the Earliest Ship Date and the Latest Ship Date is in the past.



STEPS
-----------------------
The issue can be reproduced at will with the following steps:
1. Select a PO with the Not Before Date, Not after Date, Earliest Ship Date, Latest Ship Date in the past and the status is 'W'. The PO should not have been approved earlier.
2. Use the update PO header API to update the status of the PO. Observe there is an error with the dates.
3. Update the Dates (Not before date, Not after date and End of week date only. Do not update the earliest ship date and latest ship date) and the status through the API. Order Approved with the earliest ship date and latest ship date in the past.
4. Find a similar PO in the MFCS UI, update the dates and try to approve. Unlike in the API, Estimated In Stock Date being in the past causes error in the UI. Once that is updated, observe that the PO is approved without changes to the Earliest and Latest Ship dates.

Also, if the PO details are updated using the API, the earliest ship date and latest ship date are validated and it says they are in the past. The same validation is not triggered when the PO Details are updated in the UI (example, ordered qty changed).

Cause

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