My Oracle Support Banner

R11i/12: PO: Active Encumbrance Exists/ Incorrect encumbered amount In PO Distributions - List Of Code Fixes (Doc ID 1208403.1)

Last updated on JULY 13, 2021

Applies to:

Oracle Purchasing - Version 11.5.10.2 to 12.1.3 [Release 11.5 to 12.1]
Information in this document applies to any platform.

Details

This document is a primary note which consolidates all the code fixes done in the problem category "Active encumbrance exists/ Incorrect encumbered amount for Purchasing documents / Discrepancy with Funds Inquiry" listing all the symptoms,release versions, bugs,root cause for the issue,appropriate patches and relevant file versions. This document will be updated with all these details whenever a new code fix is done in this problem category.

Actions

Whenever you get an issue related to the problem category 'Active Encumbrance exists/ Encumbrance not relieved for purchasing documents / Incorrect encumbered amount for purchase orders',  please try to match your issue with the symptoms listed in this document and get the relevant bug and patch specified against each symptom to resolve that issue. If the symptoms mentioned in this document do not match with your issue, please log a Service request with Oracle Support.

S.NoReported Release VersionSymptomsBug numberBug DescriptionRoot CausePatch numberFixed file version / File version upgraded by the patch suggestedBehavior after patch application
1 12.1 and above Return to Vendor of over-received purchase order quantity leads to negative active encumbrance when the purchase order is set to accrue at receipt with Expense destination. This happens because Encumbrance gets reinstated for the over-received qty when Return to Vendor is done for that overreceipt

e.g:
a) Enter a expense po line with quantity 10
b) Receive and deliver quantity 5.
c) Receive and deliver quantity 15 leading to overreceipt of extra qty 10.
d) Return the second receipt (qty of 15) to vendor.

  - Encumbrance should get reinstated only for qty 5 whereas it got reinstated for qty 15. Hence PO distribution's active encumbrance amount shows -5.00. But it should have been +5.00
<Bug.10209325> ENCUMBRANCE ACCOUNTING ON OVER RECEIPT RETURN CREATES NEGATIVE BALANCE This is due to the wrong sign of variable l_source_doc_quantity in PROCEDURE Get_Quantity() in
RCVVRUTB.pls
<Patch.10209325:R12.BOM.C> RCVVRUTB.pls - 120.10.12010000.6

Encumbrance reversal (or Reinstating the encumbrance) for Return to Vendor against over-received purchase order qty will happen for the correct amount in case of Expense destination PO set to accrue at receipt
2 12.0.6, 12.1 Purchase Order Summary Form shows active encumbrance even after encumbrance has been reversed on account of delivery of receipt to Inventory


<Bug.9258930>

ACTIVE ENCUM EXISTS ON PO SUMMARY&ENCUMBRANCE DETAIL REP AFTER RECEIVE&DELIVEY




 FUNCTION Get_encumReversalAmt still had a condition to check that MTA.gl_batch_id <> -1 which doesnot hold good post R12 as this column is no more relevant as Costing no more transfers data to GL directly.


<Patch.9258930:R12.BOM.A> for R12
<Patch.9555948:R12.PO.B> for 12.1

RCVGUTLB.pls - 120.9.12000000.3 for R12
RCVGUTLB.pls - 120.10.12010000.3 for 12.1


Purchase Order Summary Form shows no active encumbrance after encumbrance has been reversed by delivery of receipt to Inventory


3 12.0.6 Encumbrance reversal happening multiple times @ 3 times the PO price on doing Return to vendor for Inventory destination PO receipts


<Bug.8914459>

WHEN RETURNING AN INVENTORY ITEM IN ENCUMBRANCE INSTANCE ACCOUNTING IS WRONG


The journal for inventory enc reversal is missing the join to the accounting line type 15 causing number of record return as many accounting as there are in MTA


<Patch.8914459:R12.BOM.A>



cstxlaaad.ldt - 120.22.12000000.33



Encumbrance reversal gets created correctly for Return transactions done against inventory destination Pos


4 12.0.4 Value % and Price for a milestone pay item was allowed to change even if the document is in reserved state. It posts wrong encumbrance entries to GL


<Bug.8534044>

ENG : WHEN CHANGING AMOUNT FOR PAY ITEM, ITS BUDGET IS NOT CHANGED ACCORDINGLY


Code limitation in file PoShipmentsRenderCmd.java



<Patch 8545471:R12.PO.A>

PoShipmentsRenderCmd.java - 120.83.12000000.15

change of rate or UOM for a pay item is not allowed to if the document is in reserved status


5 12.0.6, 12.1 When invoice is matched to a 11i upgraded PO that is finally closed in R12, encumbrance amount is relieved equal to invoice distribution amount. This should consider PO exchange rate



<Bug.8474761>


SLA STATUS RETURNED WRONGLY TO AP



If there are multiple lines passed to XLA and not all of them fail with XLA_NO_JOURNAL error, PSA passes the status wrongly to AP

Patch 9037877:R12.PSA.A for R12 &
Patch 9037877:R12.PSA.B for 12.1

psavbcxb.pls - 120.31.12000000.16 for R12 & psavbcxb.pls - 120.34.12010000.13 for 12.1


PO Encumbrance will get relieved for the correct amount considering the PO price and PO exchange rate


6 11.5.10.2

While attempting to unreserve a blanket release which is overbilled and the corresponding invoice is not validated, it creates incorrect encumbrance entries resulting in discrepancies with funds inquiry screen


<Bug.8346783>

POXPOERL : UNRESERVE AN OVERBILLED RELEASE RESULTS IN ENCUMBRANCE DESCRIPENCY


Code limitation in file POXVDCKB.pls


<Patch 8791241> (PRC Roll up 12)


POXVDCKB.pls - 115.83.11510.56

System will not allow unreserving the release which is overbilled when the corresponding invoice is not validated


7 11.5.10.2 Incorrect encumbered amount gets created on the PR which has a corresponding autocreated PO that is partially received and cancelled. This incorrect commitment encumbrance gets created when the PR is autocreated to PO for the 2nd time


<Bug.7620333>

INCORRECT ENCUMBRANCE WHEN SUBMIT PO CREATED FROM PR

Code limitation in file POXENC1B.pls


<Patch.7620333>

POXENC1B.pls - 115.54.11510.8


Encumbered amount will get calculated correctly for the PR which has a corresponding PO


8 12 & 12.1 PO encumbrance gets reversed incorrectly when the invoice is validated. This happens when the PO currency is different from functional currency. This leads to incorrect active encumbrance on the PO <Bug.7592825> PSA API RETURNS INCORRECT PO REVERSE ENCUMBRANCE AMOUNT Reversal Encumbrance amount calculation on PO did not consider the exchange rate due to code limitation <Patch.7592825:R12.PSA.A> for R12 & <Patch.8940136:R12.PSA.B> for 12.1 psavapbb.pls-120.42.12000000.16 for R12 & psavapbb.pls-120.49.12010000.11 for 12.1 PO encumbrance will get reversed for the correct amount even if the PO currency differs from the functional currency
9 11.5.10.2 Incorrect Encumbrance amount creation on the backing Requisiton distributions during the Cancel action of an auto created PO


<Bug.7335825>

TWO SIDE-EFFECTS ISSUES ON PO AND REQ AFTER PATCH 6877385


Code limitation in file POXENC1B.pls



<Patch 7335825>


[POXCOC1B.pls 115.43.11510.6
POXCOC1S.pls 115.20.11510.2
POXCOPEB.pls 115.7.11510.2
POXENC1B.pls 115.54.11510.4
POXVDCOB.pls 115.29.11510.8
POXWPA9B.pls 115.8

New Validation changes for GL period in Purchasing: If the profile option "PO:Validate GL Period" is set to Yes only then
the GL period will be validated to be in "Open" or "future enterable" status.

10 12.0.4 PO encumbrance gets reversed incorrectly when the invoice is validated for Pos set to accrue at period end


<Bug.7227109>

PO REVERSED ENCUMBERED AMOUNT CALCULATION NEEDS TO BE FIXED.


Code limitation in file psavapbb.pls


<Patch.7229803:R12.PSA.A
PO encumbrance gets reversed correctly when invoice is validated



11 12.0.4 PO encumbrance gets reversed incorrectly when the invoice having tax distributions is validated for POs set to accrue at period end. This issue is applicable only for upgraded Pos



<Bug.7225570>

PO REVERSED ENCUMBERED AMOUNT CALCULATION NEEDS TO BE FIXED.


CURSOR upgraded_po_enc_rev_cur in function Get_PO_Reversed_Encumb_Amount of package AP_UTILITIES_PKG was wrongly considering tax distributions that are encumbered already in 11i for calculation



<Patch 7225570:R12.AP.A>

aputilsb.pls - 120.29.12000000.8



PO encumbrance gets reversed correctly when invoice having tax distribution is validated


12 12.0.6

Encumbrance Detailed report shows incorrect amount for billed POs set to accrue at period end


<Bug.7004208>

FIX FOR CORRECTING THE LOGIC IN PSA_AP_BC_PVT.GET_PO_REVERSED


For Pos set to accrue at period end which are billed, Encumbrance Detailed report shows incorrect amount

<Patch 7004208:R12.PSA.A> for R12 &
<Patch 7004208:R12.PSA.B> for 12.1

psavapbb.pls - 120.42.12000000.6 for R12 & psavapbb.pls - 120.49.12010000.4 for 12.1

Encumbrance Detailed Report will show the amount correctly for Pos set to accrue at period end which are billed

13 11.5.10.2 Whenever iproc requisitions have multiple distributions (even in 1 requisition
line), cancelling its autocreated PO line creates the incorrect distribution
in the requisitions resulting in wrong encumbrance amounts.

<Bug.6877385> CANCELLED PO ($1000), BUT PO/REQ ENC $700 REMAINS FOR BILLED QTY

During the PO Encumbrance Preprocessing, in Procedure 'get_backing_doc_amts' we are not calculating the Closed Quantity/Amount on the Backing Requisitions for Cancel Action.Assuming that the Cancel Code might have created a New Requisition Line.

<Patch 7335825>

POXENC1B.pls 115.54.11510.7

Cancel action with recreate demand creates Encumbrances properly for the Backing Requisitions.

14 12 Encumbrance reversal does not happen in SLA for Internal Requisition raised with Expense destination. This leads to Active encumbrance for the internal requisition and results in incorrect funds availability <Bug.6624738> CST: INTERNAL ORDER TO EXPENSE NOT RELIEVING THE ENCUMBRANCE ENTRY Code limitation in file cstxlaaad.ldt <Patch.6624738:R12.BOM.A> cstxlaaad.ldt - 120.22.12000000.13 Encumbrance reversal will get created in SLA for Internal Requisition raised with Expense destination
15 11.5.10.2 When a Partially billed/Received Release/PO having backing requisitions is first unreserved and then cancelled without canceling the backing requsition then cancel action gets the encumbrance data for requisition into inconsistent state.

<Bug.6508988> INCORRECT ENCUMBRANCE DATA ON REQUISITIONS

After the cancel action is selected from control action we check the document copy with the archival copy to determine whether to carry on the control action. There is no check based on the encumbrance state.

<Patch.6508988>

POXDOCRB.pls 115.23.11510.7

cancel action is not allowed for a document po/release when in unreserved state.

16 11.5.10.2 PO Unreserve is allowed when invoice is in an unvalidated state, this Results in Encumbrance Discrepancy if the PO quantity is modified. <Bug.6373808> FEDERAL SYS ALLOWS TO UNRESERVE A PO WITH UNVALIDATED INVOICES AT PO HEADER

Unreserve action was always successful from the Approval window, as submission check was being skipped

<Patch.6373808> POXAPAPC.pld 115.156.11510.18

Before the fix,
1. Create a Purchase Order with Quantity Ordered = 10 and unit price = 1 and
approve the Purchase Order.
2. Create an invoice matching quantity of 15 to the above purchase order but
do not validate the invoice.
3. Unreserve the PO and increase the quantity from 10 to 20 and approve the
Purchase Order again.
4. Approve the invoice.
5. Run Program-Create Journals and Payables Accounting Process.
The above sequence results in an encumbrance discrepancy of 5 (Quantity
over-billed).
During the amendment of the PO, only the quantity of five (20-15) quantity is
encumbered with the assumption that the over-billed invoice is approved.
However, when the invoice is approved, the entire billed quantity is
relieved, since the current PO quantity is greater than the billed amount.
In this case, the following results:
PO Qty = 20
Invoiced qty = 15
Encumbered Amt = 15
The remaining quantity of five is not encumbered and when eventually billed,
canceled or finally closed, will drive the encumbered amount negative

After fix, unreserve action on invalidated invoice is not allowed thereby avoiding the above explained
corruption on the encumbrance amount.
17 11.5.10.2 Function : 'Duplicate Record' (shiift+F6) also copies the Encumbered_amount to the new Distribution.

<Bug.6343213> "SHIFT+F6" CAUSES ENCUMBERED_AMOUNT TO BE COPIED IN PO_DISTRIBUTIONS_ALL

Issue is because of not nulling out the encumbered_amount after calling duplicate_record.

<Patch.6343213> POXPODIS.pld 115.152.11510.27

'Duplicate Record' (shiift+F6) will not copy the Encumbered_amount to the new Distribution.

18 11.5.10.2 Finally close of PO/Release was allowed even when an invoice/debit memo was not validated Unreserve was allowed on PO/Release with debit memo that has not been validated

<Bug.5109231> FCLOSE A PO BEFORE INV IS VALIDATED, DOES NOT RELIEVE PROJECT COMMITM--SR 29210

Unreserve/Finally Close Action on a Document was allowed, even when there are some unvalidated debit memos and/or Invoices related to that document.

<Patch.5109231>

POXPOSCS.pls - 115.3.11510.2
POXPOSCB.pls - 115.10.11510.2
POXPOACB.pls - 115.32.11510.9
POXVDCKB.pls - 115.83.11510.19
poccc.lpc - 115.23.11510.2

Final close actoin will not be allowed if there is an unvalidated inovice.

19 11.5.10.2 Encumbrance for the requisition gets created incorrectly in GL when the corresponding autocreated purchase order price is changed. The encumbered amount is also incorrect for the backing requisition. Encumbered amount on the PO and encumbrance entries for the PO are correct. This behavior only occurs on database 10G. <Bug.5646565> Incorrect FC on PO - FC Doesn't Consider Updated Amount The credit created for the backing requisition is using the purchase distribution amount (when the amount is changed on the PO manually) instead of the original requisition amount due to code limitation <Patch.5646565> POXENC1B.pls - 115.54.11510.3
POXCOC2S.pls - 115.6.11510.2
POXCOC2B.pls - 115.7.11510.2
Encumbrance for the backing requisition will get created correctly when the price is changed on the autocreated PO

Contacts

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
Details
Actions
Contacts
References

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