XLA Distribution Links Summary
Description:
Summary of subledger distribution links for developers to understand which source_ids are populated for which subledger table sources. The link to subledger tables for different source_distribution_type values is described e.g. MOS Doc IDs for: AP 813968.1 https://support.oracle.com/CSP/main/article?cmd=show&type=NOT&id=813968.1 FA 2002464.1 https://support.oracle.com/CSP/main/article?cmd=show&type=NOT&id=2002464.1 PA 1274575.1 https://support.oracle.com/CSP/main/article?cmd=show&type=NOT&id=1274575.1
For GMF, there is AP and PO Accrual Reconciliation Report Debugging from OPM Financials 2114612.1 https://support.oracle.com/CSP/main/article?cmd=show&type=NOT&id=2114612.1 and Financials Troubleshooting Guide 1213193.1 https://support.oracle.com/CSP/main/article?cmd=show&type=NOT&id=1213193.1
How the gl_import_references tableis used in 11i vs R12 is described in notes 165327.1 and 130542.1 https://support.oracle.com/CSP/main/article?cmd=show&type=NOT&id=165327.1 https://support.oracle.com/CSP/main/article?cmd=show&type=NOT&id=130542.1
Parameters
Number Of History Days, Show Ledger and Period
Used tables
gl_ledgers, xla_ae_lines, xla_ae_headers, xla_transaction_entities, xla_distribution_links, fnd_application_vl
Categories
Dependencies
If you would like to try one of these Oracle EBS SQLs without having Blitz Report installed, note that some of the reports require functions from utility package xxen_util.
Example Report
XLA Distribution Links Summary 02-Oct-2024 131742.xlsx
Report SQL
www.enginatics.com/reports/xla-distribution-links-summary/
Blitz Report™ import options
XLA_Distribution_Links_Summary.xml
Case Study & Technical Analysis: XLA Distribution Links Summary Report
Executive Summary
The XLA Distribution Links Summary report is a critical technical analysis and reconciliation tool for Oracle Subledger Accounting (SLA). It provides a summarized view of how subledger transaction distributions are linked to their corresponding accounting entries in SLA and ultimately to the General Ledger. This report is indispensable for technical consultants, functional analysts, and auditors to understand the complex mapping of source IDs to subledger tables, debug accounting flows, reconcile subledger balances to the GL, and ensure the accuracy and traceability of financial entries originating from various Oracle modules.
Business Challenge
Oracle Subledger Accounting (SLA) is a powerful yet complex engine that generates accounting entries for transactions originating from various subledgers (e.g., Payables, Receivables, Projects, Inventory) before they are posted to the General Ledger. Understanding this linkage and flow is a significant challenge:
- Opaque Accounting Flows: It’s often difficult to trace a specific GL journal entry back to its original subledger transaction (e.g., a purchase order receipt, a sales invoice, a project expenditure). This lack of transparency complicates reconciliation and audit.
- Debugging Accounting Errors: When a GL balance is incorrect, or a transaction is accounted for unexpectedly, diagnosing the issue requires understanding how the SLA rules translated the subledger transaction into GL debits and credits. Identifying the exact
source_idandsource_distribution_typeis crucial but hard to do without specialized tools. - Reconciliation Difficulties: For reconciliation purposes, it’s essential to aggregate subledger data and compare it to GL balances. The complex linking within SLA can make this a daunting task, especially for custom accounting rules.
- Technical Understanding: For developers and technical analysts, understanding the
xla_distribution_linkstable and howsource_idcolumns relate to actual subledger tables (e.g.,AP_INVOICE_DISTRIBUTIONS_ALL,PA_EXPENDITURE_ITEMS_ALL) requires specific knowledge and tools.
The Solution
This report offers a powerful, summarized, and actionable solution for analyzing SLA distribution links, bringing transparency to subledger accounting flows.
- Clear Subledger-to-GL Mapping: It provides a summarized view of the crucial
xla_distribution_linkstable, detailing which subledger transaction IDs (source IDs) are populated for whichsource_distribution_typevalues. This demystifies how subledger entries become GL entries. - Accelerated Debugging: For technical users, the report is invaluable for quickly identifying how a particular subledger transaction has been accounted for, making it easier to debug incorrect GL postings or missing accounting entries.
- Reconciliation Support: By providing key linking information, the report assists finance teams in tracing and reconciling subledger activity to the General Ledger, improving the efficiency and accuracy of month-end close.
- Reference to MOS Notes: The
README.mdexplicitly references relevant Oracle Support (MOS) documents that describe the linkage to subledger tables for different source distribution types, which is an invaluable resource for technical understanding.
Technical Architecture (High Level)
The report queries core Oracle Subledger Accounting (XLA) and General Ledger tables to summarize distribution links.
- Primary Tables Involved:
xla_distribution_links(the central table for linking subledger transaction distributions to SLA accounting lines).xla_ae_linesandxla_ae_headers(for SLA accounting entry lines and headers).xla_transaction_entities(stores information about the subledger transactions that create accounting entries).gl_ledgers(for ledger context).fnd_application_vl(for application context, identifying the source module).
- Logical Relationships: The report aggregates and summarizes records from
xla_distribution_links. It links these toxla_ae_linesandxla_ae_headersto get the actual accounting entries. By usingxla_transaction_entities, it identifies the source application and subledger, and then presents thesource_idcolumns, indicating which transaction IDs are being linked from the original subledger tables. TheNumber Of History Daysparameter controls the timeframe of the data included.
Parameters & Filtering
The report offers focused parameters for targeted analysis of SLA distribution links:
- Number Of History Days: A crucial parameter that controls how far back in time the report retrieves data, allowing users to focus on recent accounting activity or a specific historical period.
- Show Ledger and Period: This parameter likely enables the display of the associated
Ledgername andPeriodfor the accounting entries, providing essential financial context.
Performance & Optimization
As a technical summary report querying complex SLA tables, it is optimized by limiting the historical data retrieved.
- History Day Limit: The
Number Of History Daysparameter is critical for performance. By restricting the data to a recent timeframe, the database can efficiently query the largexla_distribution_linkstable using date-based indexes. - Efficient Aggregation: The report provides a summary, implying efficient aggregation of data rather than returning every single distribution link, which would be a very large dataset.
- Indexed Joins: Queries leverage standard Oracle indexes on
application_id,ae_header_id,ae_line_num, andsource_distribution_typefor efficient data retrieval across SLA tables.
FAQ
1. What is the significance of source_id_int_1, source_id_int_2, etc., in the xla_distribution_links table?
These columns are generic foreign keys that store the primary key values from the original subledger transaction tables. For example, source_id_int_1 might store AP_INVOICE_DISTRIBUTION_ID for an Accounts Payable transaction, or PROJECT_EXPENDITURE_ITEM_ID for a Projects transaction. This report helps decipher which subledger table each combination of source IDs refers to.
2. How does this report assist in debugging GL reconciliation issues? If a GL balance is off, this report helps by showing the detailed linkages. You can see which subledger transactions contributed to which GL entries. If a transaction is missing or incorrectly linked, this report provides the technical details (source IDs, distribution types) needed to investigate the SLA setup or the source subledger transaction itself.
3. Why are Oracle Support (MOS) document IDs referenced in the description?
MOS documents often provide crucial technical details about Oracle EBS tables and their linkages, especially for complex modules like SLA. Referencing these IDs in the report description is invaluable for developers and support staff who need to understand the underlying data model and how specific source_id columns map to various subledger tables, aiding in advanced troubleshooting.
Oracle E-Business Suite Reporting Library
We provide an open source Oracle EBS SQLs as a part of operational and project implementation support toolkits for rapid Excel reports generation.
Blitz Report™ is based on Oracle EBS forms technology, and hence requires minimal training. There are no data or performance limitations since the output files are created directly from the database without going through intermediate file formats such as XML.
Blitz Report can be used as BI Publisher and Oracle Discoverer replacement tool. Standard Oracle BI Publisher and Discoverer reports can also be imported into Blitz Report for immediate output to Excel. Typically, reports can be created and version tracked within hours instead of days. The concurrent request output automatically opens upon completion without the need for re-formatting.
The Filters, Columns, Rows and Values fields are used to create and deliver the data in pivot table format with full drill down to details.

The Excel template upload functionality in Blitz Report allows users to create their own layouts by uploading an Excel template with additional sheets and charts, automatically refreshed when the report runs again. This allows to create custom dashboards and more advanced visualizations of report data.

You can download and use Blitz Report free of charge for your first 30 reports.
The installation and implementation process usually takes less than 1 hour; you can refer to our installation and user guides for specific details.
If you would like to optimize your Oracle EBS implementation and or operational reporting you can visit www.enginatics.com to review great ideas and example usage in blog. Or why not try for yourself in our demo environment.
Useful Links
Blitz Report™ – World’s fastest data upload and reporting for Oracle EBS
Oracle Discoverer replacement – importing worksheets into Blitz Report™
Blitz Report™ Questions & Answers
Supply Chain Hub by Blitz Report™
© 2025 Enginatics