Search Results xla_transaction_entities




Overview
Explore in AI Chat

Overview

The XLA_TRANSACTION_ENTITIES table is a core repository within the Oracle E-Business Suite Subledger Accounting (XLA) architecture. It serves as the master definition table for all subledger transactions or documents that are candidates for accounting. Every transaction from a source subledger module—such as Payables (AP), Receivables (AR), or Assets (FA)—must be registered as a unique entity in this table before accounting events can be generated for it. The table acts as a critical junction, linking the original transaction identifier from its source module to the accounting events and journal entries created in Subledger Accounting.

Key Information Stored

The table's primary function is to store metadata that uniquely identifies a transaction and its context for the accounting engine. While the full column list is extensive, the most critical fields include:

  • ENTITY_ID: The surrogate primary key (PK) for the entity record, uniquely identifying the transaction within SLA.
  • APPLICATION_ID: Identifies the source EBS product (e.g., 200 for Payables, 222 for Receivables).
  • ENTITY_CODE: A code representing the specific transaction type or document class within the source application (e.g., 'AP_INVOICES', 'AR_INVOICES').
  • TRANSACTION_NUMBER: The original transaction identifier from the source module, such as an invoice number.
  • SOURCE_ID_INT_1 and other SOURCE_ID columns: Typically store the key identifiers from the source transaction table (e.g., the AP_INVOICES_ALL.INVOICE_ID), enabling traceability back to the original record.
  • LEDGER_ID: The ledger for which accounting is performed.
  • PROCESS_STATUS_CODE: Indicates the current accounting status (e.g., 'U' for unprocessed, 'P' for processed).

Common Use Cases and Queries

This table is central for troubleshooting accounting issues, auditing the flow of transactions into the general ledger, and building custom reports. A common scenario is tracing a subledger journal entry back to its source transaction. A typical diagnostic query joins XLA_TRANSACTION_ENTITIES to the event and header tables:

SELECT xte.entity_code,
xte.transaction_number,
xah.accounting_entry_status_code,
xah.je_category_name
FROM xla_transaction_entities xte,
xla_ae_headers xah
WHERE xte.application_id = xah.application_id
AND xte.entity_id = xah.entity_id
AND xte.transaction_number = 'INV12345';

Another frequent use is identifying transactions pending accounting processing by filtering on PROCESS_STATUS_CODE = 'U' for a specific ledger and application.

Related Objects

XLA_TRANSACTION_ENTITIES has a primary key relationship with several fundamental Subledger Accounting tables. The ENTITY_ID column is a foreign key in:

  • XLA_EVENTS: Stores the accounting events created for the entity. Join on ENTITY_ID and APPLICATION_ID.
  • XLA_AE_HEADERS: Stores the accounting journal entry headers. Join on ENTITY_ID and APPLICATION_ID.
  • XLA_AE_LINES: Typically accessed via XLA_AE_HEADERS, it ultimately links journal lines back to the source entity.

To trace back to the original source module transaction, developers must join the SOURCE_ID_INT_1 (and related) columns to the key columns of the source transaction table, such as AP_INVOICES_ALL.INVOICE_ID, based on the APPLICATION_ID and ENTITY_CODE.