GL Account Analysis 11g – Oracle EBS SQL Report

Oracle E-Business Suite SQL report from the Enginatics Library powered by Blitz Report™.

Overview

Backwards compatible version (for 11g databases) of the detail GL transaction report with one line per transaction including all segments and subledger data, with amounts in both transaction currency and ledger currency.

Report Parameters

Ledger, Period, Period From, Period To, Posted Date From, Posted Date To, Journal Source, Journal Category, Batch, Journal, Journal Line, Account Type, Hierarchy Segment, Hierarchy Name, Concatenated Segments, GL_SEGMENT1, GL_SEGMENT1 From, GL_SEGMENT1 To, GL_SEGMENT2, GL_SEGMENT2 From, GL_SEGMENT2 To, GL_SEGMENT3, GL_SEGMENT3 From, GL_SEGMENT3 To, GL_SEGMENT4, GL_SEGMENT4 From, GL_SEGMENT4 To, GL_SEGMENT5, GL_SEGMENT5 From, GL_SEGMENT5 To, GL_SEGMENT6, GL_SEGMENT6 From, GL_SEGMENT6 To, GL_SEGMENT7, GL_SEGMENT7 From, GL_SEGMENT7 To, GL_SEGMENT8, GL_SEGMENT8 From, GL_SEGMENT8 To, GL_SEGMENT9, GL_SEGMENT9 From, GL_SEGMENT9 To, GL_SEGMENT10, GL_SEGMENT10 From, GL_SEGMENT10 To, Status, Transaction Currency, Revaluation Currency, Revaluation Conversion Type, Balance Type, Budget Name, Encumbrance Type, Show Segments with Descriptions

Oracle EBS Tables Used

ra_rules, ra_customer_trx_lines_all, hz_cust_accounts, hz_parties, gl_je_sources_vl, gl_je_categories_vl, xla_event_types_tl, gl_daily_conversion_types, gl_budget_versions, gl_encumbrance_types, fa_additions_b, fa_transaction_headers, fa_deprn_detail, po_headers_all, ap_suppliers, hz_cust_site_uses_all, ap_supplier_sites_all, pa_projects_all, pa_tasks, gl_ledgers, gl_periods, gl_je_batches, gl_je_headers, gl_je_lines, gl_import_references, xla_ae_lines, xla_ae_headers, xla_events, xla_transaction_entities, fnd_id_flex_segments, fnd_flex_values, gl_code_combinations_kfv, fnd_flex_value_norm_hierarchy, ap_invoices_all, ap_invoice_distributions_all, ap_checks_all, ar_adjustments_all, ar_cash_receipts_all, pa_draft_revenues_all, pa_agreements_all, pa_expenditure_items_all, pa_expenditures_all, pa_expenditure_types, per_all_people_f, rcv_transactions

Report Categories

Enginatics

Running This SQL Without Blitz Report

Some Oracle EBS SQL reports in this library require functions from the utility package xxen_util. Install it before running the SQL directly against your Oracle EBS database.

Download & Import Options

Resource Link
Excel Example Output None
Blitz Report™ XML Import GL_Account_Analysis_11g.xml
Full SQL on Enginatics www.enginatics.com/reports/gl-account-analysis-11g/

GL Account Analysis 11g - Case Study & Technical Analysis

Executive Summary

The GL Account Analysis 11g report is a specialized version of the standard General Ledger account analysis tool, optimized for Oracle E-Business Suite environments running on Oracle Database 11g. It provides a detailed, transaction-level view of GL activity, linking journal entries back to their subledger sources (AP, AR, PO, etc.). This report ensures that organizations on older database versions can still access high-performance, granular financial data without compatibility issues.

Business Challenge

Financial analysis often requires drilling down from a GL balance to the individual transactions that comprise it.

Solution

The GL Account Analysis 11g report bridges the gap between the General Ledger and subledgers, providing a unified view of financial transactions. It is specifically engineered to perform efficiently on the 11g optimizer.

Key Features:

Technical Architecture

The report uses a “star” query approach or optimized joins starting from GL_JE_LINES and XLA_AE_LINES to fetch subledger details.

Key Tables and Views

Core Logic

  1. GL Selection: Selects journal lines from GL_JE_LINES based on the period and account filters.
  2. SLA Linkage: Joins to GL_IMPORT_REFERENCES and then XLA_AE_LINES to find the subledger entry.
  3. Source Identification: Uses the ENTITY_CODE and SOURCE_ID_INT_1 from XLA_TRANSACTION_ENTITIES to determine the source system (e.g., ‘AP_INVOICES’).
  4. Conditional Joins: Dynamically joins to the appropriate subledger tables (e.g., if Source is AP, join to AP_INVOICES_ALL) to retrieve document numbers, dates, and descriptions.
  5. 11g Optimization: May use specific optimizer hints (like /*+ LEADING(gl) USE_NL(xla) */) to ensure the execution plan remains efficient on the older database engine.

Business Impact

© 2026 Enginatics