R12 Clarification Of Readme For Patch 7512923 (Doc ID 825032.1)

Last updated on MAY 29, 2013

Applies to:

Oracle General Ledger - Version: 12.0.0 to 12.0.4 - Release: 12.0 to 12.0
Information in this document applies to any platform.

Goal

To provide further clarification regarding the Readme information for <
Old Behavior:
a) SLA:Disable Journal import profile option was available to customer for usage.using this profile option would create reconciliation,drilldown and reporting issues.
b) Interface table used by Journal import processing was dropped, leaving debugging difficult.
c) There were only gl_sl_link_id and group_id column to tie back data between SlA and GL making reconciliation difficult.

New Behaviour:
a) Now SLA:Disable Journal import profile option is end dated to discourage usage of this profile.Transfer to Gl should always be followed by Journal Import for reconciliation and drilldown to work properly.
b) Interface tables used by Journal import processing are not dropped for debugging purposes.Memory usage would be more because xla_glt_xxx tables would be retained now.Customer should periodically drop such tables after period closures.  Alternatively Oracle may provide datafix to purge temporary tables.
c) After code changes,there are 6 more additional columns namely entity id, event id, ae header id, line num, acctd cr,acctd dr.They would be populated in gl_import_references during Journal import.

Section C states that the gl_import_references table is going to have 6 additional columns. After the patch was applied, the table does not have any additional columns.

Solution

Sign In with your My Oracle Support account

Don't have a My Oracle Support account? Click to get started

My Oracle Support provides customers with access to over a
Million Knowledge Articles and hundreds of Community platforms