XLA Entity ID Mappings
Description:
Shows the column link between table xla_transaction_entities and subledger source tables such as and AP invoice_id or AR customer_trx_id, used when writing queries linking GL to subledger such as the GL Account Analysis report www.enginatics.com/reports/gl-account-analysis/
Parameters
Used tables
xla_entity_id_mappings, 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 Entity ID Mappings 17-Jun-2019 114024.xlsx
Report SQL
www.enginatics.com/reports/xla-entity-id-mappings/
Blitz Report™ import options
Case Study & Technical Analysis: XLA Entity ID Mappings Report
Executive Summary
The XLA Entity ID Mappings report is a crucial technical reference and debugging tool for Oracle Subledger Accounting (SLA). It provides a detailed listing of how the generic source_id_int_N columns in SLA tables (xla_transaction_entities) map to the primary key columns of various original subledger source tables (e.g., Accounts Payable invoices, Accounts Receivable transactions). This report is indispensable for technical consultants, developers, and advanced functional analysts to understand the complex linkages between General Ledger entries and their originating subledger transactions, debug accounting flows, and build custom reports that trace financial data from the GL back to its source.
Business Challenge
Oracle Subledger Accounting (SLA) is designed to create a flexible bridge between subledger transactions and the General Ledger. However, understanding the technical data model, particularly how transactions are linked across modules, can be a significant challenge:
- Opaque Data Linkages: The
xla_transaction_entitiestable uses genericsource_id_int_Ncolumns to store primary keys of source subledger transactions. Without clear mappings, it’s difficult to know which specific column (e.g.,invoice_id,customer_trx_id) from which subledger table corresponds tosource_id_int_1for a given SLA entity. - Debugging GL Reconciliations: When performing GL reconciliation or investigating why a specific GL entry was created, tracing it back to the original subledger transaction requires precise knowledge of these ID mappings. Manual investigation is time-consuming and error-prone.
- Custom Reporting Development: Building custom reports that join GL data (via SLA) back to original subledger details (e.g., an Account Analysis report that drills down to AP invoice lines) critically depends on knowing these
entity_idmappings. - System Understanding: For new technical staff or during system upgrades, understanding the SLA data model and how it links various subledgers to the GL is fundamental but can be a steep learning curve.
The Solution
This report offers a powerful, consolidated, and transparent solution for deciphering SLA entity ID mappings, bringing clarity to complex financial data flows.
- Clear ID Mapping Reference: It provides a detailed list showing the column names and table names in the source subledgers that correspond to the generic
source_id_int_Ncolumns inxla_transaction_entitiesfor each application and entity type. This serves as a vital technical reference. - Accelerated Debugging: For technical analysts, the report is invaluable for quickly identifying the correct join conditions to link SLA data back to original subledger transactions, dramatically speeding up the diagnosis of accounting errors or data flow issues.
- Streamlined Custom Report Development: Developers can use this report as a blueprint for writing efficient SQL queries that join GL/SLA data to specific subledger details, enabling the creation of powerful drill-down reports.
- Enhanced System Understanding: By clarifying the underlying data model, the report significantly improves the understanding of how SLA processes transactions from various Oracle modules, benefiting system maintenance and upgrades.
Technical Architecture (High Level)
The report queries core Oracle Subledger Accounting (XLA) and FND tables that store entity ID mapping definitions.
- Primary Tables Involved:
xla_entity_id_mappings(the central table storing the mappings between generic SLA source ID columns and specific subledger table columns).fnd_application_vl(for application names, providing context).
- Logical Relationships: The report directly selects from
xla_entity_id_mappings. This table contains records for eachapplication_id,entity_code, andsource_id_int_Ncolumn, specifying thesource_table_nameandsource_column_nameto which it corresponds. Thefnd_application_vltable is joined to translate theapplication_idinto a user-friendly application name (e.g., ‘Payables’, ‘Receivables’, ‘Projects’).
Parameters & Filtering
No Explicit Parameters: The README.md indicates no specific parameters for this report. This implies that, by design, it provides a comprehensive dump of all configured XLA entity ID mappings across all applications and entity types within the system. This is advantageous for a complete, unfiltered technical reference.
Performance & Optimization
As a configuration and meta-data report, it is highly optimized for efficient retrieval of setup data.
- Low Data Volume: The
xla_entity_id_mappingstable is a setup table with a relatively small number of rows compared to transactional tables, ensuring fast query execution. - Direct Table Access: The report directly accesses the core definition tables within Oracle SLA, minimizing complex joins to transactional data.
FAQ
1. What is the main purpose of xla_entity_id_mappings?
Its main purpose is to define the technical blueprint for how Oracle’s Subledger Accounting (SLA) module links its generic source_id_int_N columns (which contain primary keys from subledger transactions) to the actual, specific primary key columns in the original subledger tables. This mapping is crucial for tracing transactions through SLA.
2. How does this report help when creating custom GL Account Analysis reports?
When you want to drill down from a GL account balance to the original subledger transaction (e.g., an AP invoice number), you need to join through SLA. This report tells you precisely which columns in xla_distribution_links or xla_transaction_entities map to the primary keys of your desired subledger tables, providing the exact join conditions needed for your custom queries.
3. Is it possible for different subledgers to use the same source_id_int_N column for different purposes?
Yes. The meaning of source_id_int_1 (or 2, 3, etc.) is dependent on the application_id and entity_code. This is precisely why xla_entity_id_mappings exists – to provide this context-sensitive mapping. For example, source_id_int_1 might map to AP_INVOICE_ID for Payables transactions but to CUSTOMER_TRX_ID for Receivables transactions.
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