My Oracle Support Banner

Why are Changes To Promised Date & Need By Date Triggering Re-Approval? (Doc ID 1294049.1)

Last updated on JANUARY 29, 2022

Applies to:

Oracle Purchasing - Version 12.0.6 and later
Oracle iSupplier Portal - Version 12.1.3 to 12.1.3 [Release 12.1]
Information in this document applies to any platform.


The Auto-Approval Tolerances for Orders for Need-By Date and Promised Date are setup for 365 days. However, when changing the Promised Date or Need By Date on a Purchase Order (PO) it is still causing the PO to require reapproval.

It is expected with the tolerance set to 365 days that if modifying the need by or promise date within that year range the PO would not require re-approval.

The issue can be reproduced at will with the following steps:

1. Nav. Setup > Tolerances and Routings > Change Order
2. Under Auto-Approval Tolerances for Orders set up the following tolerances:

  • Need-By Date (CO_S_NEED_BY_DATE_T) = 365
  • Promised Date (CO_S_PROMISED_DATE_T) = 365


This is illustrated in the following screenshot:


3. Navigate to Purchase Orders > Purchase Orders
4. As preparer create a PO and submit it for approval.
5. As approver open the approval notification and approve the PO.
6. Then as preparer requery the PO in the PO summary and change either the Promised or Need-By date within the defined tolerances.
7. After saving the changes the following message pops up, after which the PO revision is increased and the PO requires reapproval:



 This is illustrated in the following screenshot:



Why does the PO require reapproval, even though the changes are within the defined tolerances? It is expected that the purchase order does not require reapproval.


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

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