Search Results event_class_group_code




Overview

XLA_EVENT_CLASS_ATTRS_FVL is an APPS-owned, VALID view within the Oracle E-Business Suite Subledger Accounting (XLA) module. It is a "flexfield value" style view that presents the event class attributes configured for each subledger application, entity, and event class, enriched with translated lookup names, general ledger journal category descriptions, and application names. Rather than exposing raw configuration identifiers, the view performs the language-sensitive joins required to return user-facing names, making it suitable for both reporting and integration layers that must display Subledger Accounting setup in a readable form.

In the context of a search for event_class_group_code, this view is particularly relevant because it exposes EVENT_CLASS_GROUP_CODE directly alongside its translated description, EVENT_CLASS_GROUP_NAME. That pairing allows users to both filter by the group code and display the group's meaning without additional joins. The view is documented in ETRM 12.2.2 and is also applicable to 12.1.1, since the underlying XLA event class and event class group tables exist in both releases.

Underlying Base Objects

The documented base objects referenced by XLA_EVENT_CLASS_ATTRS_FVL are:

Joins are keyed on APPLICATION_ID, ENTITY_CODE, EVENT_CLASS_CODE, and EVENT_CLASS_GROUP_CODE, with language-restricted joins (LANGUAGE = USERENV('LANG')) against each translated table. The view explicitly excludes ENTITY_CODE values of 'MANUAL' and 'THIRD_PARTY_MERGE'.

Key Columns

  • ROW_ID — the ROWID of the XLA_EVENT_CLASS_ATTRS row, used to uniquely identify a configured attribute set.
  • APPLICATION_ID / APPLICATION_NAME — the subledger application identifier and its display name.
  • ENTITY_CODE / ENTITY_NAME — the entity within the application (for example, transaction types) and its translated name.
  • EVENT_CLASS_CODE / EVENT_CLASS_NAME — the accounting event class and its translated description.
  • EVENT_CLASS_GROUP_CODE / EVENT_CLASS_GROUP_NAME — the grouping of event classes and its translated description; the code is the direct target of the user's search.
  • JE_CATEGORY_NAME / USER_JE_CATEGORY_NAME — the journal category code and its user-facing GL name.
  • ALLOW_ACTUALS_FLAG, ALLOW_BUDGETS_FLAG, ALLOW_ENCUMBRANCE_FLAG — indicators of which balance types the event class supports.
  • CALCULATE_ACCTD_AMTS_FLAG, CALCULATE_G_L_AMTS_FLAG — flags governing whether accounted and GL amounts are calculated.
  • REPORTING_VIEW_NAME — the reporting view associated with the event class.

Common Use Cases and Queries

Typical scenarios include reviewing Subledger Accounting event class configuration, diagnosing why a journal entry was created with a particular category, and reporting on which balance types an event class permits. A representative query filtering on the event class group code is:

SELECT application_name,
       entity_name,
       event_class_name,
       event_class_group_code,
       event_class_group_name,
       user_je_category_name
FROM   apps.xla_event_class_attrs_fvl
WHERE  event_class_group_code = :p_event_class_group_code
ORDER  BY application_name, entity_name, event_class_name;

Because the view already resolves translated names, no additional joins to the TL tables are required, and results are returned in the session's language. This makes it a convenient source for concurrent programs, BI Publisher reports, and integration extracts that need to present Subledger Accounting setup to end users.