Results for “xla_event_types_tl”

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

Overview

XLA_EVENT_TYPES_TL is a translation (TL) table in the XLA schema, the foundation of Oracle Subledger Accounting (SLA) in Oracle E-Business Suite 12.1.1 and 12.2.2. It stores the language-specific, user-facing text associated with subledger event types — the business activities (for example, invoice creation, payment issuance, or receipt application) that Subledger Accounting uses to determine which accounting rules and journal line definitions are applied when generating subledger journal entries. Because Oracle EBS implements multi-language support through paired base and translation tables, XLA_EVENT_TYPES_TL holds the translated NAME and DESCRIPTION values while the underlying structural attributes of an event type reside in the corresponding base table. The table is registered in the ETRM repository with STATUS VALID under the XLA product.

Using the heuristic Data Vault classification mined from its foreign-key structure, this object is modeled as standalone. In Data Vault terms it behaves as a reference or descriptive satellite-like entity that is not joined through a dependent link to a parent hub within the mined relationship set. This classification should be treated as a modeling suggestion rather than a documented constraint, since the metadata reports no downstream foreign-key relationships.

Key Information Stored

The table is fully qualified as XLA.XLA_EVENT_TYPES_TL and contains 14 documented columns. The most important of these define the unique identity of each translated event type and carry the localized text.

• APPLICATION_ID — Identifies the owning application (subledger) that defines the event type; part of the primary key.
• ENTITY_CODE — The entity or transaction context to which the event type belongs; part of the primary key.
• EVENT_CLASS_CODE — The event class (for example, invoices, payments) that groups related event types; part of the primary key.
• EVENT_TYPE_CODE — The internal code that uniquely identifies the event type within its class; part of the primary key.
• LANGUAGE — The NLS language code for the translated row; part of the primary key and the reason this is a TL table.
• NAME — The translated display name shown to users in SLA setup and inquiry pages.
• DESCRIPTION — The translated descriptive text for the event type.
• SOURCE_LANG — Indicates the language of the source text, used by the translation framework.
• ZD_EDITION_NAME — The editioning column supporting Oracle's Edition-Based Redefinition (EBR) model.
• Audit columns — CREATION_DATE, CREATED_BY, LAST_UPDATE_DATE, LAST_UPDATED_BY, and LAST_UPDATE_LOGIN capture who created and last maintained the row.

The documented surrogate primary key is XLA_EVENT_TYPES_TL_PK on (APPLICATION_ID, ENTITY_CODE, EVENT_CLASS_CODE, EVENT_TYPE_CODE, LANGUAGE). Two unique indexes serve as business-key candidates: XLA_EVENT_TYPES_TL_U1 extends the PK columns with ZD_EDITION_NAME, and XLA_EVENT_TYPES_TL_U2 enforces uniqueness on (APPLICATION_ID, ENTITY_CODE, EVENT_CLASS_CODE, NAME, LANGUAGE, ZD_EDITION_NAME), guaranteeing that a translated event type name is unique within its class and language.

Common Use Cases and Queries

The primary use case is reporting and lookup of event type names in a user's own language. A typical query joins the table to itself or filters by LANGUAGE to avoid duplicate-language rows, for example:

• Retrieve localized event type names: SELECT event_type_code, name FROM xla_event_types_tl WHERE application_id = :app_id AND language = USERENV('LANG');
• List all translated types for a class: filter on ENTITY_CODE and EVENT_CLASS_CODE to enumerate the event types available to a given subledger entity.
• Audit translation completeness: compare row counts per LANGUAGE against the base event type table to detect missing translations.
• Reporting and extracts: provide human-readable labels in custom SLA diagnostics, accounting-rule documentation, and reconciliation reports.

Because the table is translation-only, queries should always constrain LANGUAGE to prevent returning multiple rows for the same event type.

Related Objects

Although the mined relationship data classifies this object as standalone, operational dependencies exist through shared key columns and the SLA data model. Significant related objects include:

• XLA_EVENT_TYPES_B — The base (non-translated) event type table; join on APPLICATION_ID, ENTITY_CODE, EVENT_CLASS_CODE, and EVENT_TYPE_CODE.
• XLA_EVENT_TYPES_VL / XLA_EVENT_TYPES_V — The translated views that combine base and TL rows using the same four key columns plus LANGUAGE.
• XLA_EVENT_CLASSES_TL — Store translated event class names; related via ENTITY_CODE and EVENT_CLASS_CODE.
• XLA_ENTITY_TYPES_TL — Provide translated entity type descriptions keyed by ENTITY_CODE and APPLICATION_ID.
• XLA_ACCOUNTING_EVENTS — Runtime accounting events reference event type codes for rule resolution.
• XLA_EVENT_TYPE_ACCOUNTS and XLA_AE_HEADERS — Consume event type identity when journal entries are created.