PO Account Generator - List Of Code Fixes
(Doc ID 1270115.1)
Last updated on JULY 13, 2021
Applies to:Oracle Purchasing - Version 220.127.116.11 to 12.1.2 [Release 11.5 to 12.1]
Information in this document applies to any platform.
POXFRQAG - PO Requisition Account Generator Workflow
This document is a Primary code fix note which consolidates all the code fixes done in the problem category Purchasing Account Generator workflow, listing all the symptoms,release versions, bugs, root cause for the issue, appropriate patches and relevant file versions since January 2005. This document will be updated with all these details whenever a new code fix is done in this problem category.
Whenever you get an issue related to the problem category Purchasing Account Generator workflow, 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.
This list only includes issue specific to Purchasing Account Generator workflow, therefore if the symptom seen is due to the problem in underlying data on which the report depends, the bug may not be listed here. For these issues other relevant code fixes related to workflow can be checked.
If the symptoms mentioned in this document could not be matched with the issue at hand, please log a Service request with Oracle Support.
Table content to be modified yet.
|S.No||Reported Release Version||Symptoms||Bug number||Bug Description||Root Cause||Patch number||Fixed file version / File version upgraded by the patch suggested||Behavior after patch application|
|1||12.0.6||EDR shows active encumbrance even after encumbrance has been reversed on account of delivery of receipt to Inventory
||ACTIVE ENCUM EXISTS ON PO SUMMARY&ENCUMBRANCE DETAIL REP AFTER RECEIVE&DELIVEY
||Stmt 40 in 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 is 120.9.12010000.3 for 12.1
|EDR shows no active encumbrance after encumbrance has been reversed on account of delivery of receipt to Inventory
|2||12.0.6||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
||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
|3||12.0.4||PO encumbrance gets reversed incorrectly when the invoice is validated for Pos set to accrue at period end
||PO REVERSED ENCUMBERED AMOUNT CALCULATION NEEDS TO BE FIXED.
||Code limitation in file psavapbb.pls
||<Patch 7229803:R12.PSA.A >
||psavapbb.pls - 120.42.12000000.12
||PO encumbrance gets reversed correctly when invoice is validated
||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
||PO REVERSAL ENCUMBRANCE AMOUNT IS WRONGLY CALCULATED
||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
||aputilsb.pls - 120.29.12000000.8
||PO encumbrance gets reversed correctly when invoice having tax distribution is validated
||For Pos set to accrue at period end which are billed, Encumbrance Detailed report shows incorrect amount
||FIX FOR CORRECTING THE LOGIC IN PSA_AP_BC_PVT.GET_PO_REVERSED
||Only unencumbered amount from AP_UTILITIES_PKG.Get_PO_Reversed_Encumb_Amount is being
|<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
|6||18.104.22.168||Encumbrance Detail Report is not showing requisitions that are encumbered in GL have null quantity_delivered
||<Bug.6492476>||CAN UNRESERVE RECEIVED POS, CAUSE PO STUCK IN REQUIRE REAPPROVE STATUS
||Encumbrance Detail Report query Q_REQ_DTLS, nvl condition was not used with quantity_delivered. Due to this, the requisitions having NULL quantity_delivered were being filtered out of the report even if they have been encumbered.
||Encumbrance Detail Report is showing all the candidate requisitions.
|7||22.214.171.124||When a Partially billed/Received Release/PO having backing requisitions is first unreserved and then cancelled without canceling the backing requisition then cancel action gets the encumbrance data for requisition into inconsistent state.
||ENCUMBRANCE DETAIL REPORT IS NOT CORRECT
||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.
||Cancel action is not allowed for a document po/release when in unreserved state.
|8||126.96.36.199||Encumbrance Detail report was failing for the larger account ranges.
||FP:11I9-12:ENCUMBRANCE DETAIL REPORT ERR REP-1401:'R_BREAK_GROUPFORMATTRIGGER'
||Encumbrance Detail report executes properly for the larger account ranges
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