Search Results xla_entity_types_b




Overview
Explore in AI Chat

Overview

The XLA_ENTITY_TYPES_B table is a core master data table within the Oracle E-Business Suite Subledger Accounting (XLA) architecture. It serves as the definitive repository for all event entity definitions. An event entity is a fundamental concept in Subledger Accounting that represents a business object or transaction type, such as an Invoice, Payment, or Journal, for which accounting events can be raised. The table's primary role is to define and group related event classes, establishing the foundational framework upon which the entire event-based accounting model is built. By centralizing entity definitions, it enables the consistent processing, validation, and accounting of transactions across all subledger applications.

Key Information Stored

The table stores the essential attributes that define an event entity. While the full column list is proprietary, the documented primary key structure reveals the most critical fields. The combination of APPLICATION_ID and ENTITY_CODE uniquely identifies each entity record. The APPLICATION_ID links the entity to its originating Oracle EBS product module (e.g., Payables, Receivables). The ENTITY_CODE is the internal identifier for the business object, such as 'AP_INVOICES' or 'AR_CASH_RECEIPTS'. Other typical columns in this and related _B/_TL tables would include columns for the enabled status, creation and update dates, and translated names (ENTITY_NAME) for multilingual support, though these are not explicitly detailed in the provided excerpt.

Common Use Cases and Queries

This table is primarily referenced for setup verification, troubleshooting, and reporting on the Subledger Accounting framework. Common scenarios include validating that an entity is registered and active for a given application, or generating a list of all entities available within the system. A typical query would join with the corresponding _TL table to retrieve user-friendly names.

  • List all active entities for a specific application:
    SELECT et.entity_code, etl.entity_name
    FROM xla_entity_types_b et, xla_entity_types_tl etl
    WHERE et.application_id = 200 -- e.g., Payables
    AND et.enabled_flag = 'Y'
    AND et.entity_code = etl.entity_code
    AND etl.language = USERENV('LANG');
  • Verify entity setup for transaction processing: This query is often a first step in diagnosing why accounting events are not being generated for a specific transaction type.

Related Objects

The XLA_ENTITY_TYPES_B table has defined relationships with several other key Subledger Accounting tables via its primary key. The most significant relationships include:

  • XLA_EVENT_CLASSES_B: Event classes are grouped under a specific event entity. The relationship is typically established via APPLICATION_ID and ENTITY_CODE.
  • XLA_EVENT_TYPES_B: Event types are associated with an event class and, by extension, its parent entity. The link is propagated through the event class definition.
  • XLA_TRANSACTION_ENTITIES: This table stores instances of the entities defined in XLA_ENTITY_TYPES_B (e.g., a specific invoice). It references the entity definition using APPLICATION_ID and ENTITY_CODE.
  • XLA_ENTITY_TYPES_TL: The corresponding translation table that stores the user-facing name (ENTITY_NAME) for each ENTITY_CODE and APPLICATION_ID combination in multiple languages.