My Oracle Support Banner

Issues with GL Transfer And Posting Of Accounting Entries In Procure To Pay Flow - List Of Code Fixes (Doc ID 1177053.1)

Last updated on MARCH 05, 2019

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 master note which consolidates all the code fixes done in the problem category "Issues with GL Transfer And Posting Of Accounting Entries In Procure To Pay Flow". It includes the issues related to Posting error,accounting entries not getting transferred to GL from SLA and Journal import errors.

Actions

Whenever you get an issue related to the problem category 'Issues with GL Transfer And Posting Of 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.

S.NoReported Release VersionSymptomsBug NumberBug AbstractRoot CausePatch NumberFixed file version / File version upgraded by the patch suggestedBehavior after Patch application
1 R12 & 12.1 Accounting entries for the source Cost Management get transferred to GL from SLA inspite of the option 'Transfer to GL' being set to No in Inventory > Organization parameters <Bug.10124492> TRANSACTIONS TRANSFERRED TO GL ALTHOUGH TRANSFER OPTION IS 'NONE' Code limitation in files xlaaptrn.pkb and xlajejex.pkb <Patch.10124492:R12.XLA.A> (Controlled Release) for R12 & and <Patch.10124492:R12.XLA.B> (Controlled Release) for 12.1 [xlaaptrn.pkb 120.61.12000000.30; xlajejex.pkb xlajejex.pkb 120.108.12000000.29
] for R12 & [xlaaptrn.pkb 120.63.12010000.23; xlajejex.pkb 120.112.12010000.21
] for 12.1



Accounting entries will not get transferred to GL from SLA when the 'Transfer to GL' option is set to No
2 R12.1 Journal entries can not be transferred to General ledger from SLA via request 'Transfer Journal Entries to GL' when the accounting profile option 'Allow transfer override' is set to No <Bug.9818008>

XLAGLTRN: JOURNAL ENTRIES NOT TRANSFERRED DUE TO ALLOW TRANSFER OVERRIDE = N

Code limitation in file xla120cp.ldt

<Patch.9818008:R12.XLA.B> (Controlled release)

xla120cp.ldt - 120.131.12010000.39

Standalone Transfer Journal Entries to GL always transfers the data to GL irrespective of the Accounting Program default and override options.

3 R12 & R12.1 While posting the subledger actual entries which have the category Receiving or Accrual or Purchase Invoices, Posting errors out with the message - Funds Reservation failure. Funds check should not happen in GL while posting the subledger entries

<Bug.9307142>

POSTING ENDING IN WARNING WITH "FUNDS RESERVATION FAIL" FOR ACTUAL ENTRIES BATCH

GL is forcing a funds check on Actual Batches that had already gone thru funds check for Payables and Costing

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

psaxlacb.pls - 120.0.12000000.3 for R12 & psaxlacb.pls - 120.0.12010000.3 for 12.1

Funds check will happen forcibly for encumbrance reversal and actual entries in SLA istelf and GL will not do any funds check while posting

4 R12 Transfer Journal entries to GL-Receiving or Cost Management program does not transfer the entries which are final accounted from SLA to GL

<Bug.9034353>

TRANSFER TO GL PROGRAM NOT PICKING ANY ENTRIES FINAL ACCOUNTED

Default value of Transfer To GL flag parameter in wrapper process Transfer Journal Entries to GL - Receiving and Transfer Journal Entries to GL - Cost Management is not as per Standard(SLA's) Transfer Journal Entries to GL

<Patch.9034353:R12.BOM.A> 

cstcp9034353.ldt - 120.0.12000000.1

Transfer Journal entries to GL-Receiving or Cost Management program will transfer the entries from SLA to GL if the entries are having the accounting_entry_status_code as F-Final in SLA

5 R12 Negative ledger id populated in GL tables for the source Cost Management <Bug.8691650> NEGATIVE LEDGER_ID IN GL WHEN JOURNAL IMPORT IS CANCELLED Code limitation in file xlaaptrn.pkb <Patch. 8417930:R12.XLA.A> xlaaptrn.pkb - 120.61.12000000.20

Ledger_id will get stamped correctly in GL tables on doing the Transfer to GL from subledger
6 R12 & R12.1 Transaction accounted in XLA and marked as transferred to GL but
actually not transferred to GL for material transactions such as PO delivery into inventory

<Bug.7628313>

FP:12.0-12.1:TRANSACTIONS ACCOUNTED IN XLA NOT ABLE TO TRANSFER TO GL

The accounting events of those transactions have a different event date than the accounting date due to which this issue happens

<Patch.8543110:R12.BOM.A> for R12 & <Patch.8915988:R12.BOM.C> for 12.1


CSTVXLAB.pls - 120.36.12000000.16 for R12 & CSTVXLAB.pls - 120.43.12010000.7 for 12.1 Transactions should get transferred to GL after create accounting process

7 R12 & 12.1 Various issues are identified in Transfer to GL so far ,the patch serves as a consolidated fix for all these issues. Fixes include rootcauses and enhanced debugging logic to solve GL transfer issues more effectively Example: Journal import errred but gl_transfer_status_code is marked as Y in XLA

<Bug.7512923>

RCA:CHANGES IN GL TRANSFER PACKAGE FOR VARIOUS ISSUES

Code limitation in file xlaaptrn.pkb

<Patch.7512923:R12.XLA.A> for R12 & <Patch.7512923:R12.XLA.B> for 12.1 (Controlled release)

[xlaaptrn.pkb - 120.61.12000000.13; xla120pf.ldt- 120.19.12000000.3] for R12 & [xla120pf.ldt - 120.19.12010000.4 ; xlaaptrn.pkb - 120.63.12010000.6 ] for 12.1


The profile option "SLA:Disable Journal import" is obsoleted and the GL transfer will happen effectively

8 R12 & R12.1 Pre-seeded Journal Line Types(JLT) for PO Delivery to Inventory event has the GL transfer mode as Detail where as the requirement to have the GL transfer mode as Summary

<Bug.7506072>

PRE-SEEDED JLT SETUP FOR SUMMARY TRANSFER TO GL FOR INVENTORY TRANSACTIONS

Code limitation in file cstxlaaad.ldt

<Patch.7506072:R12.BOM.A> for R12 & <Patch.8409628:R12.BOM.C> for 12.1

cstxlaaad.ldt - 120.22.12000000.27 for R12 & cstxlaaad.ldt - 120.32.12010000.13 for 12.1

Accounting entries for PO deliver transaction to Inventory destination will get transferred to GL from SLA in summary mode by default

9 R12 & R12.1 Journal import does not get spawned on submitting the Create Accounting-Receiving program to generate accounting entries for Purchase Order receipts

<Bug.7385683>

JOURNAL IMPORT NOT GETTING LAUNCHED AFTER CREATE ACCOUNTING

Security Context is not getting set correctly when the procedure accounting_program_document() is called directly to perform GL xfer from Create Accounting CP

<Patch.7385683:R12.XLA.A> for R12 & <Patch.7385683:R12.XLA.B> for R12.1 (Controlled release)

xlaapeng.pkb - 120.147.12000000.31 for R12& xlaapeng.pkb 120.164.12010000.4 for R12.1

Journal import gets launched on submitting the Create Accounting-Receiving program with "Transfer to GL" flag as Yes

10 R12 GL is doing funds check for actual entries too while posting the entries

<Bug.7011860>

TST1205.XB3.QA: FUND RESERVATION REQUIRIED FOR ACTUAL JOURNALS BEFORE POSTING

Code limitation in file xlaaptrn.pkb

<Patch.7011860:R12.XLA.A>

xlaaptrn.pkb - 120.61.12000000.8

GL is doing funds check for only encumbrance entries, which are not done by SLA

11 R12 After the patch 6636475, Transfer Journal Entries to GL is not being kicked off every time from Create Accounting

<Bug.6899103>

TRANSFER TO GL IS NOT BEING KICKED OFF EVERY TIME AFTER 6636475

Raising warning when the exception ORA-25228 occurs without checking Concurrent: Hold Requests profile option value

<Patch.6636475:R12.XLA.A>

xlaapeng.pkb - 120.147.12000000.15

Transfer Journal Entries to GL is being kicked off from Create Accounting

12 R12 Transfer Journal Entries to GL program is erring out

<Bug.6884941>

ST1:R: TRANSFER JOURNAL ENTRIES TO GL REQUEST IS COMPLETING IN ERROR

p_conc_request_id is getting defaulted with zero

<Patch.6884941:R12.XLA.A>

XLAGLTRN.xml - 120.0.12000000.8

Transfer Journal Entries to GL is completed successfully

13 R12 This patch consolidates critical fixes released by SLA product team over R12, RUP2,3,4 and one-offs after RUP4. Fixes include
- Create Accounting & GL transfer issues identified after R12.RUP2
- Create Accounting Engine and SLA report's performance issues
- Open Account Balances program changes (used by Trial Balance)
- Period Close performance issues



<Bug.6826219>

R12 : SLA CONSOLIDATED CRITICAL FIXES AS OF FEB 19, 2008


 Consolidated fix

<Patch.6826219:R12.XLA.A>

Consolidated fix fixing many file versions  
14 R12 Create Accounting is done in final mode with 'Transfer to GL' as Yes and Posting as 'Yes'. Accounting gets created in SLA and Journal import gets triggered. But the Journal import errors out with the exception EU02 - 'This journal entry is unbalanced and suspense posting is not allowed in this ledger'

<Bug.6767541>

UNBALANCED JOURNAL ENTRIES DUE TO DECIMAL ROUNDING

Code limitation in file xlajebal.pkb

<Patch.6884633:R12.XLA.A>

xlajebal.pkb - 120.153.12000000.11

If no rounding account is defined and suspense posting is not enabled, and if journal entry is unbalanced by rounded amounts, Journal import will not get triggered and data errors out in SLA itself

15 11.5.10.2 Journal import errors with ECW1 EC10 for POs created in foreign currency in encumbrance enabled environment

<Bug.4153676>

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

The encumbrance journal was created with the PO currency code instead of the functional currency code. Encumbrance journals should always be created in functional currency code

<Patch.4153676>

RCVVACCB.pls - 115.17.11510.3

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

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.