Search Results third_party_merge

Overview

The view APPS.XLA_EVENT_CLASS_ATTRS_FVL is a foundation-level reporting and integration object within the Oracle E-Business Suite Subledger Accounting (XLA) architecture. It belongs to the family of "FVL" (Flex Value List) views that expose descriptive, translatable attribute data for subledger event configuration. The view presents the accounting attributes associated with each event class defined across subledger applications, joined to their translated names, owning application, accounting entity, event class group, and the corresponding General Ledger journal category.

Its primary role is to provide a user-friendly, denormalized read model over the underlying XLA event class configuration tables. Instead of querying several base tables individually and performing language-sensitive joins, implementers and report developers can query this single view to retrieve event class metadata enriched with descriptive names in the session's language. Because it resolves translated name columns via USERENV('LANG'), the view returns text in the runtime language of the querying session, making it suitable for both multilingual reporting and integration payloads.

A defining characteristic of this view is an explicit filter: the ENTITY_CODE column excludes the values 'MANUAL' and 'THIRD_PARTY_MERGE'. This directly addresses the search term associated with this object — third_party_merge. Any query against this view will never return the THIRD_PARTY_MERGE entity, which represents the specialized accounting entity used by the third-party merge processing flow. Consumers requiring visibility of that entity must query the base tables rather than this view.

Underlying Base Objects

The view is defined over six documented base objects, joined on application, entity, event class, and event class group identifiers, with language conditions applied to each translation table.

• XLA_EVENT_CLASS_ATTRS (synonym) — the driving table, aliased ACTG, supplying the core event class attribute configuration rows, ROWID, audit columns, and the entity/event class keys.
• XLA_EVENT_CLASSES_TL (synonym) — aliased TL, supplying the translated NAME for the event class, joined on application, entity code, event class code, and language.
• XLA_ENTITY_TYPES_TL (synonym) — aliased ETL, supplying the translated entity name, joined on application, entity code, and language.
• XLA_EVENT_CLASS_GRPS_TL (synonym) — aliased GTL, supplying the translated event class group name, joined on application, event class group code, and language.
• GL_JE_CATEGORIES (synonym) — aliased J, supplying the user-facing journal category name (USER_JE_CATEGORY_NAME), joined on journal category name.
• XLA_APPLICATIONS_XVL (view) — aliased X, supplying the owning application name, joined on APPLICATION_ID.

All translation joins enforce LANGUAGE = USERENV('LANG'), ensuring a single language-consistent row per configuration entry.

Key Columns

• ROW_ID — the ROWID of the parent XLA_EVENT_CLASS_ATTRS row, useful for identifying the underlying configuration record.
• APPLICATION_ID / APPLICATION_NAME — the owning subledger application, shown in both numeric and descriptive form.
• ENTITY_CODE / ENTITY_NAME — the accounting entity to which the event class belongs. Note that MANUAL and THIRD_PARTY_MERGE rows are filtered out.
• EVENT_CLASS_CODE / EVENT_CLASS_NAME — the event class identifier and its translated display name.
• EVENT_CLASS_GROUP_CODE / EVENT_CLASS_GROUP_NAME — the grouping to which the event class is assigned, with translated name.
• JE_CATEGORY_NAME / USER_JE_CATEGORY_NAME — the GL journal category used for accounting, in internal and user-display form.
• REPORTING_VIEW_NAME — the accounting reporting view associated with the event class.
• ALLOW_ACTUALS_FLAG, ALLOW_BUDGETS_FLAG, ALLOW_ENCUMBRANCE_FLAG — flags governing whether the event class supports actual, budget, and encumbrance balances.
• CALCULATE_ACCTD_AMTS_FLAG, CALCULATE_G_L_AMTS_FLAG — flags controlling whether accounted amounts and General Ledger amounts are calculated.
• CREATION_DATE, CREATED_BY, LAST_UPDATE_DATE, LAST_UPDATED_BY, LAST_UPDATE_LOGIN — standard audit columns.

Common Use Cases and Queries

Typical scenarios include enumerating the event classes available for a subledger application, mapping event classes to GL journal categories, and validating configuration flags before building accounting reports.

List event classes for a given application:

SELECT event_class_code, event_class_name, entity_name, je_category_name
FROM   apps.xla_event_class_attrs_fvl
WHERE  application_id = 200
ORDER  BY event_class_name;

Find event classes permitted to post actuals and their GL categories:

SELECT application_name, event_class_name, user_je_category_name,
       calculate_acctd_amts_flag, calculate_g_l_amts_flag
FROM   apps.xla_event_class_attrs_fvl
WHERE  allow_actuals_flag = 'Y';

Retrieve event class groups and their member event classes:

SELECT event_class_group_name, event_class_name, reporting_view_name
FROM   apps.xla_event_class_attrs_fvl
ORDER  BY event_class_group_name, event_class_name;

Because the view systematically omits MANUAL and THIRD_PARTY_MERGE entities, any analysis targeting third-party merge accounting must bypass this view and query XLA_EVENT_CLASS_ATTRS directly, applying an appropriate entity filter.