Results for “xla_event_class_attrs_u1”

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

Overview

XLA.XLA_EVENT_CLASS_ATTRS is a configuration table in the Oracle E-Business Suite Subledger Accounting (XLA) schema. It defines the processing attributes associated with each subledger event class, keyed by the owning application, the entity code, and the event class code. In the Oracle EBS 12.1.1 and 12.2.2 architectures, this table sits at the foundation of the accounting engine: the Create Accounting program consults these attribute rows to determine which accounting entry types are permitted for a given event class, which general ledger journal category is used for the transfer, and how accounted and entered amounts must be derived. Access to the object is restricted to standard Oracle Applications programs; it is documented as Oracle Internal Use Only.

From a Data Vault modeling perspective, the mined heuristic classification for this object is standalone. It therefore does not participate in a classic hub–link–satellite graph within the ETRM dependency structure, and can be modeled as an independent reference or configuration entity rather than as a link between other business keys. The physical storage resides in the APPS_TS_TX_DATA tablespace, with its unique index in APPS_TS_TX_IDX.

Key Information Stored

The table contains 17 documented columns. The primary key, XLA_EVENT_CLASS_ATTRS_PK, is a composite surrogate-business key comprising APPLICATION_ID, ENTITY_CODE, and EVENT_CLASS_CODE. A secondary unique index, XLA_EVENT_CLASS_ATTRS_U1, extends this key set with ZD_EDITION_NAME in the 12.2.2 edition-aware schema, making it the documented business-key candidate for edition-scoped lookups. The most significant columns are:

• APPLICATION_ID — Internal numeric identifier of the owning application (for example, Payables or Receivables).
• ENTITY_CODE — The subledger entity code, such as AP_INVOICES, that scopes the event class.
• EVENT_CLASS_CODE — The event class being configured, such as INVOICE_VALIDATED or PAYMENT_CREATED.
• EVENT_CLASS_GROUP_CODE — Grouping code used to cluster related event classes for processing.
• JE_CATEGORY_NAME — The General Ledger transfer category assigned to the resulting journal entries.
• REPORTING_VIEW_NAME — The table or view name used for reporting on the event class.
• ALLOW_ACTUALS_FLAG — Indicates whether actual entries are permitted for the event class.
• ALLOW_BUDGETS_FLAG — Indicates whether budget entries are permitted.
• ALLOW_ENCUMBRANCE_FLAG — Indicates whether encumbrance entries are permitted.
• CALCULATE_ACCTD_AMTS_FLAG — Controls whether the accounting program calculates accounted amounts.
• CALCULATE_G_L_AMTS_FLAG — Controls whether General Ledger amounts are calculated.
• ZD_EDITION_NAME — Edition identifier supporting the 12.2.2 online patching (editioning) model.
• CREATION_DATE, CREATED_BY, LAST_UPDATE_DATE, LAST_UPDATED_BY, LAST_UPDATE_LOGIN — Standard WHO audit columns referencing FND_USER and FND_LOGINS.

Common Use Cases and Queries

Typical diagnostic and reporting scenarios include verifying that an event class is configured to allow actuals, budgets, or encumbrances before troubleshooting create-accounting errors, and determining which GL journal category a subledger event class will produce. A representative query joins the attributes for a known entity:

• SELECT event_class_code, je_category_name, allow_actuals_flag, allow_budgets_flag, allow_encumbrance_flag, calculate_acctd_amts_flag FROM xla_event_class_attrs WHERE application_id = :app_id AND entity_code = :entity_code;
• Use the U1 business key (application_id, entity_code, event_class_code, zd_edition_name) to resolve the correct edition-scoped configuration row in 12.2.2 environments.
• Join to XLA_EVENTS on application_id and event_class_code to enumerate the attributes governing each accounting event processed by Create Accounting.

Because the object is flagged Oracle Internal Use Only, custom queries should be read-only and executed outside the concurrent processing window where possible.

Related Objects

The following objects are the most significant references and dependents:

• XLA_EVENTS — Joins on APPLICATION_ID and EVENT_CLASS_CODE; each accounting event maps to its governing attribute row.
• XLA_EVENT_TYPES — Defines the event types that instantiate the event classes configured here.
• XLA_ENTITIES — Supplies the ENTITY_CODE context shared across XLA configuration tables.
• XLA_EVENT_CLASSES — The parent event class definition referenced by EVENT_CLASS_CODE.
• FND_APPLICATION — Resolves APPLICATION_ID to the owning application name.
• GL_JE_CATEGORIES — Matches JE_CATEGORY_NAME to the General Ledger transfer category.
• FND_USER and FND_LOGINS — Referenced by the WHO audit columns for user and login tracking.