Issue

R12: Posting Reversal Journal in Primary Ledger not Creating the Reversal Journal in Secondary Ledger [ID 428196.1] Modified 17-FEB-2012 Type PROBLEM Status PUBLISHED

Applies to:
Oracle General Ledger - Version: 12.0 to 12.1.3 - Release: 12.0 to 12.1 Oracle General Ledger - Version: 12.0.0 to 12.1.3 [Release: 12.0 to 12.1] Information in this document applies to any platform. GLPPOS - Posting

Symptoms
The posting of a Reversal Journal in Primary Ledger does not create the corresponding Reversal in the Secondary Ledger. Consider a setup with a Primary Ledger and a Secondary Ledger 1- Create Manual Journal in the Primary Ledger. 2- Post the journals created in step 1 in the Primary Ledger. 3- The GL posting will create a journal in the Secondary Ledger for the journal posted in step 2. 4- Reverse the posted journal in step 2 in the Primary Ledger. 5- Post the reversal journal created in step 4 in the Primary Ledger. 6- The GL posting did not create a journal for the reversal journal, which was posted in step 5 in the Pimary Ledger.

Cause
Expected behavior in R12 versions R12.1.2 and prior versions of apps. The Secondary Ledger Journal must be reversed manually. The reason this is handled manually is because when users reverse a journal in a non-ADB ledger, users need to specify a period, but because the primary ledger and secondary ledger could use different calendars, the periods may not be the same. Users need to reverse journals in the secondary ledger manually to be able to select the reversal period. Enhancement Request/Bug 5686912 GL POSTING DIDN'T CREATE A REVERSED MANUAL JOURNAL IN SECONDARY LEGER was logged for this issue.

Solution
This ER (Enhacemnt Request) is implemented and included in 12.1.3 To implement the solution in previous verions of R12, please execute the following steps: 1. Please download Patch 9776694 that is appropriate for your version of application, review the readme and pre-requisites.

For Release 12.0: Patch 9776694:R12.GL.A For 12.1.1 and 12.1.2: Patch 9776694:R12.GL.B

2. Ensure that you have taken a backup of your system before applying the recommended patch. 3. Apply the patches in a test environment. 4. In addition to applying the patch, there is a new checkbox for 'Synchronize Reversals between Primary and Secondary Ledger(s)' in Accounting Setup Manager under the Journal Processing Tab. This must be checked. 5. Bounce apache. 6. Retest the issue. 7. Migrate the solution as appropriate to other environments.

Note: This patch works only for manual journals. Manual reversal in the Primary Ledger triggers reversal of the corresponding journal in the Secondary Ledger if the option "Synchronize Reversals between Primary and Secondary Ledger(s)" is selected in the Accounting Setup Manager. But, if journals coming from the subledgers are manually reversed in the primary ledger, the corresponding journals will not be reversed in the secondary ledger even if the option "Synchronize Reversals between Primary and Secondary Ledger(s)" is selected in the Accounting Setup Manager. This happens when the journals in each Ledger are directly created by the subledger and not by converting the primary into the secondary.

Patch Read Me

Abstract Enhanc: Journal reversal in primary will trigger reversal in secondary ledger also Update 9776694 Product General Ledger Release R12 Platform Linux x86 Built SEP-17-2010 17:09:08 Instructions Instructions For Applying This Patch Preparation Tasks The tasks in this section can be completed without taking any Applications services or users offline. There are no tasks to be performed in this section. Pre-install Tasks You must shut down all Application tier services before performing the tasks in this section. There are no tasks to be performed in this section. Apply The Patch There are no tasks to be performed in this section. Post-install Tasks You must complete the tasks in this section before starting up Application tier services. There are no tasks to be performed in this section. Finishing Tasks You may complete the tasks in this section at any time after the update, without taking any services or users offline. There are no tasks to be performed in this section. Additional Information

There are no tasks to be performed in this section.

Description
a) Description 1. Problem Description :- When a journal entry is posted in the primary ledger, the journal is posted in the secondary ledger also due to the dual posting feature of Release 12. But, when the journal is reversed in the primary ledger , the reversal occurs in the primary ledger alone. 2. Solution Description :- When in Accounting setup maneger "Synchronize Reversals between Primary and Secondary Ledger(s)" option is enabled for the primary ledger then journal reversed in the primary ledger will trigger reversal of the respective journal in the secondary ledger also. 3. Fixed File Names and versions :forms/US/GLXJEENT.fmb 120.83.12010000.21 include/glprev.h 120.7.12010000.3 java/asflow/ledger/server/GLLedgersAMImpl.java 120.18.12010000.5 java/asflow/ledger/server/GLLedgersEO.xml 120.15.12010000.3 java/asflow/ledger/server/GLLedgersEOImpl.java 120.59.12010000.4 java/asflow/ledger/server/GLLedgersVO.xml 120.17.12010000.3 java/asflow/ledger/server/GLLedgersVORowImpl.java 120.22.12010000.3 java/asflow/ledger/webui/GLASFlowLedgerLedgerOptionsCO.java 120.9.12010000.6 mds/asflow/ledger/webui/GL_ASF_LEDGER_LEDGER_OPTIONS_PG.xml 120.5.12010000.3 patch/115/import/US/b5686912.ldt 120.0.12010000.2 patch/115/import/US/b9539435.ldt 120.0.12010000.3 patch/115/import/US/glbksreg.ldt 120.10.12010000.5 patch/115/import/US/glgvwreg.ldt 120.16.12010000.13 patch/115/odf/glbks.odf 120.13.12010000.5 patch/115/odf/glgvw.odf 120.24.12010000.14 patch/115/sql/glistldb.pls 120.99.12010000.7 patch/115/sql/glistlds.pls 120.37.12010000.4 src/mje/glparv.opc 120.14.12010000.5 src/mje/glprev.lpc 120.27.12010000.7 src/mje/glprma.opc 120.1.12010000.4 src/post/glpcsl.lpc 120.9.12010000.11 src/post/glpmai.opc 120.24.12010000.1 include/glppos.h 120.7.12010000.2 b) Pre requisite patches included with this patch: None c) Pre-requisite or Co-requisite which are NOT included with this patch: None d) Patch Applicable for versions : Oracle Applications Release R 12.1.1, 12.1.2 e) Dependent Applications : f) Patch applicable only when a particular application installed:

g) Successful patch installation checks : Make sure that the version of file $GL_TOP is same as stated above.