Search Results xla_entity_id_mappings_pk

Overview

The XLA_ENTITY_ID_MAPPINGS table is a Subledger Accounting (XLA) repository object owned by the XLA schema. It stores the mapping between the primary key columns of an entity table and the corresponding columns of the event table, thereby enabling Subledger Accounting to associate accounting events with the specific transactional entities that generated them. The table holds one row for each entity, and supports a maximum of four primary key columns per entity. This design accommodates the composite keys commonly found in subledger entity tables such as Payables invoices, Receivables transactions, and Purchasing documents.

Within the Oracle E-Business Suite 12.1.1 and 12.2.2 data model, XLA_ENTITY_ID_MAPPINGS functions as a configuration and metadata reference object rather than a transactional table. Its rows are typically seeded or created during subledger application setup and are consumed by the Subledger Accounting program logic whenever entity identifiers must be resolved to event records. From a Data Vault modeling perspective, the heuristic classification is standalone, indicating that the table functions as an independent reference structure with no foreign-key dependencies to other hub, link, or satellite objects. It is best treated as a reference or lookup entity in a dimensional or Data Vault representation.

Key Information Stored

The table contains sixteen documented columns. The most significant are as follows:

• APPLICATION_ID — Identifies the owning subledger application, such as Payables or Receivables, using the standard EBS application identifier.
• ENTITY_CODE — The internal code that uniquely identifies the entity within the application, for example the invoice or transaction entity.
• TRANSACTION_ID_COL_NAME_1 through TRANSACTION_ID_COL_NAME_4 — Up to four column names that constitute the primary key of the entity table, mapping the entity identifier to the transaction identifier columns on the event table.
• SOURCE_ID_COL_NAME_1 through SOURCE_ID_COL_NAME_4 — Up to four column names that map the entity identifier to the source identifier columns, used for traceability back to the originating subledger source.
• ZD_EDITION_NAME — The edition identifier supporting Oracle’s edition-based redefinition strategy for online patching in Release 12.2.
• CREATION_DATE, CREATED_BY, LAST_UPDATE_DATE, LAST_UPDATED_BY, LAST_UPDATE_LOGIN — Standard EBS audit columns recording who created and last modified the mapping row and when.

The surrogate primary key is XLA_ENTITY_ID_MAPPINGS_PK, defined on the composite of APPLICATION_ID and ENTITY_CODE. A unique index, XLA_ENTITY_ID_MAPPINGS_U1, is defined on APPLICATION_ID, ENTITY_CODE, and ZD_EDITION_NAME, and represents the business-key candidate that enforces uniqueness across editioned rows.

Common Use Cases and Queries

The primary use case is resolving how Subledger Accounting derives transaction and source identifiers for a given entity during event creation and accounting processing. Developers and support analysts query this table when diagnosing why an accounting event failed to locate its source transaction, or when extending Subledger Accounting to support a custom entity.

A typical query retrieves the key column mappings for a specific entity:

• SELECT application_id, entity_code, transaction_id_col_name_1, transaction_id_col_name_2, source_id_col_name_1, source_id_col_name_2 FROM xla.xla_entity_id_mappings WHERE application_id = :app_id AND entity_code = :entity_code;

Reporting use cases include producing a catalog of all registered subledger entities and their associated key columns, validating that seeded mappings are complete after an upgrade or patch, and auditing custom entity registrations against Oracle-delivered definitions. Because the table is small and static, it is frequently joined to XLA_EVENTS and the underlying entity tables to trace an event back to its originating document.

Related Objects

Although the metadata classifies this table as standalone, it participates logically in the Subledger Accounting framework alongside the following objects:

• XLA_EVENTS — The transactional event table whose entity identifiers are resolved using the mappings defined here, joined by APPLICATION_ID and ENTITY_CODE.
• XLA_EVENT_TYPES — Defines the event types associated with each entity and application.
• XLA_ENTITY_TYPES — Describes the entity types registered for a subledger application.
• XLA_TRANSACTION_ENTITIES — Holds the transaction entities that reference the mapping to locate their primary key columns.
• XLA_AE_HEADERS and XLA_AE_LINES — The accounting entry tables generated from events, indirectly dependent on the correct entity mapping.
• FND_APPLICATION — Provides the application name and short name for the APPLICATION_ID column.
• XLA_LOOKUPS — Supplies lookup values referenced during entity and event configuration.