"Maximum Increment = -100" Workaround To Force Document Approval Routing Upon Amount/Total Decrease Does Not Work For Contract Purchase Agreements (Doc ID 2865792.1)

Last updated on NOVEMBER 08, 2024

Applies to:

Symptoms

Attempting to setup auto-approval tolerances for Global Blanket Agreements and Contract Purchase Agreement with AME or Position Hierarchies approval routing so that the document is forced into reapproval when AMOUNT_AGREED is decreased following the workaround recommendation of <Note 728789.1> How to force a PO Through The Approval Hierarchy When Re-approving With a Lower Document Total does not work as expected.

When setting the CO_AGREEMENTS tolerance HEADER_AMOUNT_AGREED with maximum_increment = -100, only Global Blanket Purchase Agreements are routed for approval with amount agreed decrement changes (even for change as low as 0.1).

That setting does not affect Contract Purchase Agreements which are automatically approved when amount agreed is decremented.

Steps to reproduce:

 1. Set change order tolerances for BPAs/CPAs as suggested in advised in <Note 728789.1>

    Important: "Maximum Increment" can only be set to negative values via sql update statement as per above <Note 728789.1> also <Note 2122419.1>

 2. Perform a change against a Blanket Agreements (BPA) reducing the amount agreed.
 3. Upon submission of the change, BPA is routed for approval.
 4. Perform a change against a Contract Purchase Agreement (CPA) reducing the amount agreed
 5. Upon submission of the change, CPA is auto approved and is NOT routed for further approval

Cause

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