Results for “xla_entity_types_b”

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

Overview

The XLA_ENTITY_TYPES_B table is a core setup table within the Subledger Accounting (XLA) product of Oracle E-Business Suite, present in both release 12.1.1 and 12.2.2. It stores the event entity definitions used by the Subledger Accounting engine to group event classes into logical business objects. An event entity is the highest-level categorization in the ETRM (Event Transaction and Relationship Model) hierarchy: an entity represents a business object such as an invoice, a payment, or a journal entry, and each entity owns one or more event classes that in turn own the event types Subledger Accounting processes. Without entries in this table, the Create Accounting program cannot resolve which event classes belong to a given source object.

The metadata classifies the object heuristically as a standalone Data Vault entity, meaning it exhibits no mined foreign-key dependencies on other tables. As a modeling suggestion, this positions XLA_ENTITY_TYPES_B as a reference or lookup dimension rather than a hub, link, or satellite within a Data Vault representation. It functions as registration and control metadata for the accounting engine, and its rows are typically seeded by subledger application patches rather than created by end users.

Key Information Stored

The table contains 10 documented columns. The most significant are:

• APPLICATION_ID — Identifies the owning subledger application, such as Payables, Receivables, or Assets. Together with ENTITY_CODE it forms the primary key XLA_ENTITY_TYPES_B_PK.
• ENTITY_CODE — The short internal identifier for the event entity (for example, an invoice or payment entity code). This is the value referenced by child event class and event type records.
• ENABLED_FLAG — Indicates whether the entity is active and therefore eligible for event capture and accounting.
• ENABLE_GAPLESS_EVENTS_FLAG — Controls whether events for the entity must be numbered without gaps, supporting audit and sequencing requirements.
• ZD_EDITION_NAME — The edition identifier supporting the Edition-Based Redefinition (EBR) model introduced in 12.2. It participates in the unique index XLA_ENTITY_TYPES_B_U1 (APPLICATION_ID, ENTITY_CODE, ZD_EDITION_NAME) and the primary key, distinguishing rows across editions.
• CREATION_DATE, CREATED_BY, LAST_UPDATE_DATE, LAST_UPDATED_BY, LAST_UPDATE_LOGIN — Standard WHO audit columns recording insert and update provenance.

The surrogate primary key is XLA_ENTITY_TYPES_B_PK on (APPLICATION_ID, ENTITY_CODE), while XLA_ENTITY_TYPES_B_U1 extends that combination with ZD_EDITION_NAME and serves as the business-key candidate under EBR.

Common Use Cases and Queries

Typical usage centers on configuration validation and troubleshooting accounting failures. Developers confirm which entities are enabled for a given subledger, and analysts join entity codes to event classes when tracing why an accounting event was not created.

• Listing enabled entities for a subledger: SELECT entity_code, enabled_flag FROM xla_entity_types_b WHERE application_id = :app_id AND enabled_flag = 'Y';
• Detecting gapless-event configuration: SELECT entity_code, enable_gapless_events_flag FROM xla_entity_types_b WHERE application_id = :app_id;
• Resolving application identity: join APPLICATION_ID to FND_APPLICATION to obtain the application short name for reporting.
• Tracing event hierarchy: join to XLA_EVENT_CLASSES_B on APPLICATION_ID and ENTITY_CODE to enumerate the event classes belonging to each entity.

Related Objects

Because the metadata describes this object as standalone, relationships flow outward to dependent ETRM tables rather than through enforced foreign keys.

• XLA_EVENT_CLASSES_B — child table joined on APPLICATION_ID and ENTITY_CODE; each event class belongs to exactly one entity.
• XLA_EVENT_TYPES_B — descendant of event classes, ultimately traceable to the entity through the class.
• XLA_EVENTS — runtime event records whose entity context is validated against this table.
• XLA_EVENT_CLASSES_TL and XLA_ENTITY_TYPES_TL — translation tables supplying user-facing names.
• FND_APPLICATION — reference table for resolving APPLICATION_ID to an application name.
• XLA_ACCOUNTING_PROGRAMS and the Create Accounting concurrent program — consume entity configuration when processing events.