Search Results xla_entities

Overview

XLA_TRANSACTION_ENTITIES is the foundational registry table within the XLA (Subledger Accounting) schema in Oracle E-Business Suite releases 12.1.1 and 12.2.2. It stores one row for each subledger document or transaction that participates in the Subledger Accounting architecture, acting as the entry point through which every accounting event is linked to its originating transaction. Each record represents a unique subledger transaction identity — sourced from Payables, Receivables, Assets, Inventory, Cost Management, or any other application that creates accounting — and provides the anchor point for the downstream creation of accounting events, journal entries, and balances.

Because the table is self-contained with respect to its primary key and carries descriptive attributes about the transaction but does not itself resolve to more than one parent transaction, the heuristic Data Vault classification is standalone. It is helpful to note that XLA_TRANSACTION_ENTITIES is not modeled as a hub, link, or satellite; rather it serves as a root-level reference object from which other XLA tables derive their context.

Key Information Stored

The table contains 30 documented columns. The most significant include:

• ENTITY_ID — surrogate primary key, generated by the XLA_TRANSACTION_ENTITIES_PK sequence, uniquely identifying each subledger transaction entity. It is the column referenced throughout the SLA data model.
• APPLICATION_ID — the owning subledger application (e.g., 200 for Payables, 222 for Receivables, 140 for Assets) that originated the transaction. It combines with ENTITY_ID in the unique index XLA_TRANSACTION_ENTITIES_U1, forming the business-key candidate.
• ENTITY_CODE — the transaction type or entity classification within the source application, distinguishing, for example, an invoice from a payment or a journal batch from a journal line.
• LEGAL_ENTITY_ID — foreign key to FV_LEGAL_ENTITIES, associating the transaction with the legal entity for accounting and reporting purposes.
• LEDGER_ID — the ledger under which the transaction is accounted, critical for multi-ledger and secondary-ledger reporting.
• TRANSACTION_NUMBER — the human-readable document number of the source transaction, used extensively in reporting and drill-down queries.
• SOURCE_APPLICATION_ID — the application that supplied the source transaction identifiers, which may differ from the owning application in upgrade or consolidated scenarios.
• SOURCE_ID_INT_1 through SOURCE_ID_INT_4 and SOURCE_ID_CHAR_1 through SOURCE_ID_CHAR_4 — generic slots holding the source transaction's numeric and character identifiers (for example, invoice_id, line_id, or document numbers).
• SECURITY_ID_INT_1 through SECURITY_ID_INT_3 and SECURITY_ID_CHAR_1 through SECURITY_ID_CHAR_3 — security context values used for data access control in subledger inquiry and reporting.
• VALUATION_METHOD — the valuation approach used for the transaction entity.
• UPG_BATCH_ID and UPG_VALID_FLAG with UPG_SOURCE_APPLICATION_ID — upgrade-related columns indicating the migration batch and validation status of the record during the subledger accounting upgrade process.
• Standard audit columns — CREATION_DATE, CREATED_BY, LAST_UPDATE_DATE, LAST_UPDATED_BY, LAST_UPDATE_LOGIN — track record provenance.

Common Use Cases and Queries

The most frequent query against this table locates the accounting events and journal entries generated for a given source transaction. A typical pattern joins XLA_TRANSACTION_ENTITIES to XLA_EVENTS to retrieve event details:

• Drill-down from source document: SELECT entity_id, transaction_number, ledger_id FROM xla_transaction_entities WHERE application_id = 200 AND source_id_int_1 = :invoice_id;
• Retrieve journal entries: join entity_id to XLA_EVENTS and then to XLA_AE_HEADERS and XLA_AE_LINES to obtain the complete journal entry for the entity.
• Reporting by ledger and legal entity: filter on LEDGER_ID and LEGAL_ENTITY_ID to produce subledger accounting reports for a specific accounting period.
• Upgrade validation: query UPG_VALID_FLAG and UPG_BATCH_ID to verify entities migrated correctly during the SLA upgrade.
• Reconciliation and audit: compare transaction_number against source application tables to reconcile subledger transactions to their accounting.

Because the table is standalone, queries generally filter on ENTITY_ID, APPLICATION_ID, or the SOURCE_ID_* slots depending on what identifier the caller has available.

Related Objects

The following objects are most closely associated with XLA_TRANSACTION_ENTITIES:

• FV_LEGAL_ENTITIES — referenced via LEGAL_ENTITY_ID; provides legal entity context.
• XLA_UPG_BATCHES — referenced via UPG_BATCH_ID; tracks the upgrade batch for the entity.
• XLA_EVENTS — child table in the SLA model; joins on ENTITY_ID and APPLICATION_ID to return accounting events.
• XLA_AE_HEADERS — joins through XLA_EVENTS to deliver journal entry headers.
• XLA_AE_LINES — joins through XLA_AE_HEADERS to deliver detailed journal lines.
• XLA_DISTRIBUTION_LINKS — links accounting lines to their source distributions using ENTITY_ID.
• XLA_TRANSACTION_ENTITIES_U1 — unique index on (ENTITY_ID, APPLICATION_ID) enforcing the business-key candidate.
• XLA_TRANSACTION_ENTITIES_PK — primary key index on ENTITY_ID.

Collectively these objects form the backbone of the Subledger Accounting drill-down architecture, with XLA_TRANSACTION_ENTITIES as the originating anchor for every accounting transaction processed by the SLA engine.