Results for “xla_transaction_entities_u1”

AI-generated from documented ETRM metadata — verify critical details on the linked pages.

Overview

XLA.XLA_TRANSACTION_ENTITIES is the central reference table within the Oracle E-Business Suite Subledger Accounting (XLA) schema. It stores one row for every subledger document or transaction that is submitted to the accounting engine for event creation, journal generation, and posting. Because Subledger Accounting is the common accounting hub that sits between feeder systems such as Payables, Receivables, Assets, Cost Management, and Projects and the General Ledger, this table functions as the master registry of accounting-relevant source documents. Each entry represents an "entity" — a discrete business transaction, such as an invoice, a payment, a receipt, or an inventory movement — for which accounting events are subsequently recorded in XLA_EVENTS and journal entries in the XLA distribution tables.

From a Data Vault modeling perspective, the metadata classifies this object heuristically as standalone. This suggests treating it as an independent hub-like structure keyed on a business identifier, rather than as a classic link table joining multiple hubs. The classification is a modeling suggestion only; the physical object is a standard relational table owned by the XLA schema with FND Design Data registered as XLA.XLA_TRANSACTION_ENTITIES.

Key Information Stored

The table contains 30 documented columns. The most operationally significant are:

• ENTITY_ID (NUMBER) — The surrogate identifier for the transaction entity. It is the single-column primary key (XLA_TRANSACTION_ENTITIES_PK).
• APPLICATION_ID (NUMBER) — The internal identifier of the application that owns the entity. It participates with ENTITY_ID in the unique composite index XLA_TRANSACTION_ENTITIES_U1, making (ENTITY_ID, APPLICATION_ID) the documented business-key candidate.
• ENTITY_CODE (VARCHAR2) — The application-defined code that classifies the entity type (for example, invoice, payment, or receipt).
• LEGAL_ENTITY_ID (NUMBER) — References FV_LEGAL_ENTITIES and determines the legal entity under whose books the transaction is accounted.
• TRANSACTION_NUMBER — The human-readable source document number for reporting and reconciliation.
• LEDGER_ID — The ledger to which the entity's accounting entries are directed.
• VALUATION_METHOD — Distinguishes the valuation approach applied to the entity.
• SOURCE_APPLICATION_ID — Identifies the originating application, which may differ from the processing application.
• SOURCE_ID_INT_1 through SOURCE_ID_INT_4 and SOURCE_ID_CHAR_1 through SOURCE_ID_CHAR_4 — Flexible source identifiers that hold the source document's key values.
• SECURITY_ID_INT_1 through SECURITY_ID_INT_3 and SECURITY_ID_CHAR_1 through SECURITY_ID_CHAR_3 — Flexible security identifiers used for data access control at the entity level.
• Standard WHO columns (CREATION_DATE, CREATED_BY, LAST_UPDATE_DATE, LAST_UPDATED_BY, LAST_UPDATE_LOGIN) — Audit tracking on every row.

Upgrade-related columns (UPG_BATCH_ID, UPG_SOURCE_APPLICATION_ID, UPG_VALID_FLAG) support migration processing, with UPG_BATCH_ID referencing XLA_UPG_BATCHES.

Common Use Cases and Queries

Typical reporting and diagnostic scenarios include tracing a source document into Subledger Accounting, identifying the ledger or legal entity for an entity, and auditing upgrade batches. A representative query joins the entity to its events:

SELECT te.entity_id, te.application_id, te.entity_code,
       te.transaction_number, te.ledger_id, te.legal_entity_id
FROM   xla.xla_transaction_entities te
WHERE  te.entity_code = :entity_code
AND    te.ledger_id = :ledger_id;

The function-based index XLA_TRANSACTION_ENTITIES_N1 on NVL-wrapped SOURCE_ID columns enables lookups even when source keys are null, supporting reconciliation of documents lacking a populated identifier. A second common pattern correlates entities with their accounting events and distributions to produce a subledger-to-GL audit trail. Data-access security queries filter on the SECURITY_ID columns, and upgrade validation queries filter on UPG_VALID_FLAG.

Related Objects

• XLA_EVENTS — Child table holding accounting events for each transaction entity, joined on ENTITY_ID and APPLICATION_ID.
• XLA_AE_HEADERS and XLA_AE_LINES — The resulting subledger journal headers and lines.
• FV_LEGAL_ENTITIES — Referenced by LEGAL_ENTITY_ID to resolve the legal entity.
• XLA_UPG_BATCHES — Referenced by UPG_BATCH_ID for upgrade processing.
• FND_APPLICATION_VL — Joined on APPLICATION_ID to obtain the application name.
• GL_LEDGERS — Joined on LEDGER_ID to resolve the ledger name.