My Oracle Support Banner

Missing Accounting Entries Or Incorrect Accounting Entries in Procure To Pay Flow - List Of Code Fixes (Doc ID 1174420.1)

Last updated on SEPTEMBER 20, 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 "Missing or Incorrect Accounting entries in Procure to pay flow". It includes the issues in the following areas.

 This document lists all the symptoms,release versions, bugs,root cause for the issue,appropriate patches and relevant file versions. This primary note will be maintained upto date by keep on adding the new code fixes whenever it is fixed by Development in this problem category.

Actions

Whenever you get an issue related to the problem category 'Missing or Incorrect Accounting entries in Procure to Pay flow', please try to match your issue with the symptoms listed in this document and get the relevant bug and apply the patch specified against each symptom to resolve that issue.Please go through the Read me of the patch before applying it and it is always recommended to apply the patch in TEST instance first and do the testing before applying it in Production instance. If the symptoms mentioned in this document do not match with your issue, please log a Service request with Oracle Support.

Issues related to Actual Journal

S.NoReported Release VersionSymptomsBug NumberBug AbstractRoot CausePatch NumberFixed file version / File version upgraded by the patch suggestedBehavior after Patch application
1 12.1 & above Receiving Inspection account gets hit with an incorrect amount for LCM enabled PO receipts when purchase order UOM (Source doc UOM) is different from primary UOM <Bug.10128529> SYSTEM GENERATE WRONG ACCOUNT WHEN WE NOT USED PRIMARY UOM As per the intended design, Receiving Inspection account gets hit at source doc quantity * unit landed cost when a LCM enabled PO is received where unit landed cost is calculated based on primary UOM. But when the PO UOM which is otherwise called as Source document UOM is different from the primary UOM, the amount at which Receiving Inspection account gets hit should be arrived by multiplying unit landed cost with received quantity in primary UOM. Due to code limitation in file RCVVACCB.pls, this amount was calculated by multiplying unit landed cost which is based on primary UOM with the received quantity in source doc UOM resulting in incorrect accounting. <Patch.10128529:R12.PO.B> RCVVACCB.pls - 120.11.12010000.7 Receiving Inspection account will get hit with a correct amount which is calculated by multiplying unit landed cost with received quantity in primary UOM when the source doc UOM is different from the primary UOM for LCM enabled PO receipt
2 12.1 When primary ledger is associated with secondary ledger where primary ledger has encumbrance based Sub-ledger Accounting Method (SLAM) and secondary ledger has non encumbrance related SLAM, actual accounting entries for deliver transaction get created twice in the secondary ledger <Bug.9245677> CODEFIX: DELIVERY TRANSACTION CREATES DOUBLE JOURNALS IN THE SECONDARY LED Additional actual accounting is created during funds check due to code limitation


<Patch.9245677:R12.XLA.B> xlaapeng.pkb -120.164.12010000.13
xlajeaex.pkb -120.87.12010000.6

Delivery transaction do not create double actual accounting in secondary
ledger.
3 12.1 When primary ledger is associated with Reporting ledger and when PO currency (Entered Currency ) is same as functional currency
(Primary Ledger Currency)with Match Invoice option = PO and when Receive and deliver happened in different dates, Receive and deliver calculation happened with different rate causing Receiving inspection to debit and credit with different values

<Bug.8623413>

RECEIVING INSPECTION ACCOUNT IS OUT-OF-BALANCE IN REPORTING LEDGER

Code limitation in the following files: cstcxla.odf,RCVVRUTB.pls and rvtii.lpc

<Patch.8623413:R12.BOM.C> & <Patch.8794668:R12.PO.B>

cstcxla.odf - 120.67.12010000.7
RCVVRUTB.pls - 120.10.12010000.4 & rvtii.lpc 120.19.12010000.16



Receiving Inspection a/c will not have any mismatch because of this issue

4 12.1 When encumbrance SLAM (Sub-Ledger Accounting Method) is used for Primary ledger and non encumbrance SLAM is used for secondary ledger, actual accounting for deliver transaction gets created two times in secondary ledger

<Bug.9245677>

CODEFIX: DELIVERY TRANSACTION CREATES DOUBLE JOURNALS IN THE SECONDARY LED

Delivery trx create double actual accounting in secondary ledger.Additional actual accounting is created during funds check

<Patch.9245677:R12.XLA.B>

xlaapeng.pkb - 120.164.12010000.13; xlajeaex.pkb - 120.87.12010000.6


Accounting will get created correctly in secondary ledger for deliver transaction

5 12.0.6 & 12.1 Duplicate Actual entries get created for Deliver / Correction / Return transactions / Internal order receipts in SLA in encumbrance enabled environment without any encumbrance reversal <Bug.8423174> RCA:ENCUMBRANCE ACCOUNTING EVENT PROCESSED WITH THE ACTUAL JOURNALS Un-Processed Budgetary events are processed along with the Non-Budgetary events , resulting in in-correct accounting in Costing during the Create Accounting process <Patch.8423174:R12.XLA.A> for R12 & <Patch.8423174:R12.XLA.B> for 12.1 xlaapeng.pkb - 120.147.12000000.43 for R12 & xlaapeng.pkb - 120.164.12010000.10 Actual entries will get created correctly without any duplication
6 11.5.10 Accruals/Receipt Accounting entries get created with an incorrect exchange rate for receipts created against blanket releases <Bug.8500117> RTP USES INCORRECT EXCHANGE RATE FOR BLANKET RELEASE RECEIPTS Currency conversion Date and Currency conversion Rate were not correct on the receiving transaction when Invoice Match Option was set to 'Receipt'. This occurs because the currency conversion date were being obtained from PO_DISTRIBUTIONS table while receiving rather than from the receipt date. <Patch.8612394> RCVPRETB.pls -115.87.11510.62 Receipt Accounting will get created with the correct exchange rate

 

Issues related to Encumbrance Journal

S.NoReported Release Version

SymptomsBug NumberBug AbstractRoot CausePatch NumberFixed file version / File version upgraded by the patch suggestedBehavior after Patch application
1 12.1 and above When Return to Vendor is done against over-received qty for a purchase order shipment which is set to accrue at receipt and having Expense destination, Encumbrance gets reinstated for the over-received qty

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.
<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 On a multiple line PO where some PO lines have funds and other have no funds where partial reservation happens, Reserve for Encumbrance(RFE) a/c gets created with incorrect amount in SLA for the PO reserve action

<Bug.9707064>

RESERVE FOR ENCUMBRANE IN SLA- INCORRECT FOR PO WHEN SOME LINES HAVE NO FUNDS

Prior to this patch, code wrongly passed FC and set that BC event as 'Processed' , when one or more distribution fails FC, that is why wrong unbalanced GL entries created

<Patch.9100984:R12.PSA.A> for R12 & <Patch.9100984:R12.PSA.B>

PSAXMLRB.pls -
120.49.12000000.21 for R12 & PSAXMLRB.pls - 120.63.12010000.8 for 12.1

Accounting entries for PO reserve action will get created correctly even in case of partial reservation of PO distributions

3 12.0.6 & 12.1 When invoice is matched to a 11i upgraded PO that is finally closed in R12, PO 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

4 12.0.6 Encumbrance entries are getting created 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 Inventory subledger 'mtl_transaction_accounts'

<Patch.8914459:R12.BOM.A> 

cstxlaaad.ldt - 120.22.12000000.33

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

5 12.0.6 & 12.1 Duplicate Actual entries get created for Deliver / Correction / Return transactions / Internal order receipts  in SLA in encumbrance enabled environment without any encumbrance reversal / Encumbrance reversal entries fail to get created in SLA for Deliver/Correct/Return transactions/internal order receipts

<Bug.8423174>

RCA:ENCUMBRANCE ACCOUNTING EVENT PROCESSED WITH THE ACTUAL JOURNALS

Un-Processed Budgetary events are processed along with the Non-Budgetary events , resulting in in-correct accounting in Costing during the Create Accounting process

<Patch.8423174:R12.XLA.A> for R12 & <Patch.8423174:R12.XLA.B> for 12.1

xlaapeng.pkb - 120.147.12000000.43 for R12 & xlaapeng.pkb - 120.164.12010000.10




Encumbrance reversal will get created correctly during the Create Accounting process for receiving transactions

6 12.0.6 & 12.1 1. When functional currency was different from entered currency, encumbrance reversal created by Period end accrual process was wrong

2. Period End Accrual doesn't create encumbrance reversal if the PO is currently Closed but was not closed at the last day of the period

3.  Period End Accrual doesn't create encumbrance reversal if there are mix of 11i POs and R12 POs

<Bug.7686922>

FP:12.0-12.2:RECEIPT ACCRUAL -PERIOD END PROGRAM MISSING BILLED AMOUNT

Code limitation in file CSTVRAPB.pls

<Patch.7661294:R12.BOM.A> for R12 & <Patch.9600743:R12.BOM.C>

CSTVRAPB.pls - 120.12.12000000.4 for R12 & CSTVRAPB.pls - 120.12.12010000.6 for 12.1


Encumbrance reversal will get created correctly during the period end accrual process

7 12 & 12.1 PO encumbrance gets reversed incorrectly when the invoice is validated. This happens when the PO currency is different from functional currency <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
8 12.0.6 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>

psavapbb.pls - 120.42.12000000.12

PO encumbrance gets reversed correctly when invoice is validated

9 12.0.6 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
10 11.5.10.2 In federal budgeting, accounting entries are not created for Correction against RECEIVE transaction

<Bug.8904447>

ON RECEIPT CORRECTIONS THE BUDGETARY ENTRIES TO GENERAL LEDGER INCORRECT.

The actual line CORRECT txn didn't populate TC code

<Patch.8904447>

RCVVRUTB.pls - 115.30.11510.17

Accounting entries will get created for Correction transaction in Federal Budgeting environment

11 11.5.10.2 Encumbrance reversal does not happen for internal requisitions with Expense destination when Periodic Average Costing (PAC) is used

<Bug.7031719>

SIMILAR TO 6927499 INTERNAL REQUISITION ENCUMBRANCE CANCEL REVERSAL BATCH

Encumbrance reversal accounting entries were not being generated by the Periodic distribution processor since total received quantity was counted for all receipts like perpetual costing method rather than computing total received quantity just before the current receipt transaction as PAC is used

<Patch.7031719>

CSTAPBRB.pls - 115.45.115100.25


Encumbrance reversal gets created correctly for internal requisition created for expense items when PAC is used

12 11.5.10.2 The encumbrance reversal amount has incorrect sign at PO receipt correction against expense destination. Receipt Correction Posting credit to encumbrance rather than debit. This issue primarily occurs when overreceipt is done and correction is done against that overreceived qty

<Bug.6683404>

ENCUMBRANCE INCORRECT AFTER CORRECTIONS MADE TO RECEIPTS

Code limitation in file RCVVRUTB.pls

<Patch.6683404>

RCVVRUTB.pls - 115.30.11510.15

Encumbrance reversal will get created for the correct amount when Correction is done

13 11.5.10.2 Encumbrance is getting reversed even though the encumbrance was not booked since requisition encumbrance was not enabled

<Bug.6475530>

INVENTORY GENERATES IR ENCUMB REVERSAL. REQ ENCUMB IS SET TO OFF IN FINANCIALS

Code was using purch_encumbrance_flag instead of req_encumbrance_flag while checking for encumbrance reversal

<Patch.7127049>

inltcp.lpc - 115.120.115100.41

Encumbrance is not reversed if requisition encumbrance is not enabled

14 11.5.10.2 The encumbrance journal was created with the PO currency code instead of the functional currency code when PO is created in foreign currency

<Bug.4153676>

JOURNAL IMPORT ERRORS WITH ECW1 EC10 FOR POS CREATED IN FOREIGN CURRENCY

Code limitation in file RCVVACCB.pls

<Patch.4153676>

RCVVACCB.pls - 115.17.11510.3

Journal import completes successfully as the encumbrance reversal gets created in functional currency

 

Issues related to Retroactive Adjustment Accounting

S.NoReported Release VersionSymptomsBug NumberBug AbstractRoot CausePatch NumberFixed file version / File version upgraded by the patch suggestedBehavior after Patch application
1 12.0.4 Retroactive price adjustment entries are incorrect for Po receipts done in organization which is using Periodic Average Costing (PAC). This issue happens when the Po price is revised to a lesser price

<Bug.9155316>

RETROACTIVE PRICE ADJUSTMENT ACCOUNT IS ERROR

Periodic Distribution Processor inserting absolute values for retro price adjustment .As a result negative adjustment are getting created with incorrect sign in Accounted columns

<Patch.9155316:R12.BOM.A>

CSTAPPRB.pls - 120.12.12000000.7

Retroactive price adjustment accounting will get created when the PO price is modified to a lesser price

2 11.5.10.2 Retroactive adjustment account entry created in receiving sub-ledger was not correct due to improper rounding

<Bug.6018660>

RECCEIPT JOURNAL AND AP INVOICE ARE NOT MATCHED IN THE RETROACTIVE PRICING

Code limitation in file RCVVACCB.pls

<Patch.6018660>

RCVVACCB.pls - 115.17.11510.5

Retroactive adjustment amount entry created in receiving sub-ledger is correct

3 11.5.10.2 Retroactive price adjustment entries do not get created on running the Retroactive price adjustment program after modifying the price of PO which is received

<Bug.5666210>

FP:11I10-12.0: RETROPRICE UPDATE NOT UPDATING DELIVERIES W/ QUALITY INSPECTION

Code limitation in file RCVVRAEB.pls

<Patch.5663575>

RCVVRAEB.pls - 115.17.11510.6

Retroactive price adjustment accounting will get created when the PO price is modified and when the Retroactive price adjustment program is run

4 11.5.10.2 Retroactive price adjustment entries do not get created for deliver/Return against delivery/Correction against delivery transactions created prior to upgrade to 11.5.10

<Bug.4373565>

RETROACTIVE PRICING NOT CREATING THE CORRECT ACCOUNTING

Code limitation in file RCVVRAEB.pls

<Patch.4373565>

RCVVRAEB.pls - 115.17.11510.4

Retroactive price adjustment accounting will get created for deliver/Return/Correction transaction

5 11.5.10.2 Retroactive price adjustment entries are incorrect for Po receipts done in organization which is using Periodic Average Costing (PAC) <Bug.10017419> BACKPORT:9155316:11.5.10.0:11.5.10.0:RETROACTIVE PRICE ADJUSTMENT ACCOUNT IS ERR Periodic Distribution Processor was inserting absolute values for retro price adjustment .As a result, negative adjustment are getting created with incorrect sign in Accounted columns <Patch.10017419> CSTAPPRB.pls -115.38.115100.13

Retroactive price adjustment accounting will get created in PAC distributions correctly

 

Issues related to Global Procurement Accounting

S.NoReported Release VersionSymptomsBug NumberBug AbstractRoot CausePatch NumberFixed file version / File version upgraded by the patch suggestedBehavior after Patch application
1 12.0.6 & 12.1 In Global Procurement scenario and when Periodic Average Costing (PAC) is used, accounting entries for PO receipts have null currency conversion rate or rate is defaulted as 1 even though currency conversion rate is defined between the functional currencies of Procuring and Requesting org. This issue occurs only for accounting generated in PAC distributions by PAC processor / In Global Procurement scenario, incorrect account is populated in PAC distributions when partial return to vendor transactions are performed

<Bug.9495449>

FP:12.0-12.1:RECEIVE TRANSACTION OF GLOBAL PROCUREMENT GET WRONG CURRENCY RATE

Code limitation in the following files: CSTPACQS.pls
CSTPACQB.pls & CSTAPRB.pls

<Patch.8684475:R12.BOM.A> for R12 and <Patch.8684475:R12.BOM.C> for 12.1 (Controlled release)

CSTPACQS.pls - 120.1.12000000.2 ,CSTPACQB.pls - 120.16.12000000.17 ,CSTAPRB.pls - 120.12.12000000.9 for R12 & CSTPACQS.pls -120.1. 12010000.2, CSTPACQB.pls - 120.22.12010000.10 ,CSTAPPRB.pls - 120.15.12010000.8 for 12.1

Accounting entries for PO receipts will get created correctly in PAC distributions in global procurement scenario



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
 Issues related to Actual Journal
 Issues related to Encumbrance Journal
 Issues related to Retroactive Adjustment Accounting
 Issues related to Global Procurement Accounting
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.