How to force a PO Through The Approval Hierarchy When Re-approving With a Lower Document Total
(Doc ID 728789.1)
Last updated on FEBRUARY 06, 2018
Applies to:Oracle Purchasing - Version 18.104.22.168 to 12.2.5 [Release 11.5 to 12.2]
Information in this document applies to any platform.
Check for relevance 13-Nov-2013
It is standard functionality that when re-approving a PO whose Document Total is less than originally approved that the PO does not pass through the Approval Hierarchy.
If the Document Total is greater than originally approved, then the PO MAY pass through the Approval Hierarchy.
The deciding factor is the value of a WF attribute within the PO Approval Workflow POAPPRV
The WF Attribute is:
'Change Order Header Purchase Order Total Tolerance' (Display Name)
CO_H_PO_TOTAL_T (Internal Name)
The seeded value is '0' so all PO's pass through the Approval Hierarchy where there has been an increase in the Document Total.
If the value was set to 10, then only those PO's whose Document Total had increased above 10% of the original would pass through the Approval Hierarchy.
The changes to a Purchasing Document are made by comparing the revised document with the previous approved archived revision.
When a document is archived is dependent on the 'Archive On' value set on the Document Type Setup form.
The options for this value are:
- Approve - The document is archived upon approval. This option is the default.
- Communicate - The document is archived upon communication. A document communicate action would be printing, faxing, or e-mail.
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