Search Results xla_journal_entry_level_type

Overview

The view APPS.XLA_EVT_CLASS_ACCT_ATTRS_FVL is a denormalized, reporting-oriented interface into the Subledger Accounting (XLA) configuration that governs how accounting attributes are assigned to event classes. In Oracle E-Business Suite 12.1.1 and 12.2.2 it is owned by the APPS schema and is used primarily as a value-list and inquiry source rather than as a transactional table. Its core purpose is to expose the relationship between an event class, its accounting attribute, and the associated assignment metadata (owner, journal entry level, source, and assignment group) with all descriptive names resolved through joins to the appropriate XLA lookup and validation views.

For the search term accounting_attribute_name, this view is the recommended source: the column is populated from XLA_ACCT_ATTRIBUTES_VL.NAME, giving the translated display name of the accounting attribute associated with each event class configuration row. Because it resolves codes to meanings, it spares the developer from writing multiple joins to XLA_LOOKUPS and the underlying validation views.

Underlying Base Objects

The view is defined over four documented base objects:

• XLA_EVT_CLASS_ACCT_ATTRS (accessed via synonym) — the driving table holding the event-class-to-accounting-attribute assignments.
• XLA_ACCT_ATTRIBUTES_VL (view) — supplies the accounting attribute definition, including the translated NAME and the assignment/datatype codes.
• XLA_SOURCES_VL (view) — supplies the translated source name for the assignment.
• XLA_LOOKUPS (view) — joined four times to translate the assignment owner, journal entry level, source type, and assignment group codes into meanings.

The joins are keyed on SOURCE_APPLICATION_ID, SOURCE_CODE, SOURCE_TYPE_CODE, and ACCOUNTING_ATTRIBUTE_CODE. The lookup joins for XLA_OWNER_TYPE, XLA_JOURNAL_ENTRY_LEVEL_TYPE, and XLA_SOURCE_TYPE are inner joins, while the XLA_ACCT_ATTR_ASSGN_GROUP join is an outer join ((+)), reflecting that assignment group is optional on the base assignment row.

Key Columns

• APPLICATION_ID, EVENT_CLASS_CODE — identify the application and event class for which the accounting attribute is configured.
• ACCOUNTING_ATTRIBUTE_CODE / ACCOUNTING_ATTRIBUTE_NAME — the code and translated name of the accounting attribute.
• SOURCE_APPLICATION_ID, SOURCE_CODE, SOURCE_TYPE_CODE / SOURCE_NAME, SOURCE_TYPE_DSP — the source that provides the value.
• DEFAULT_FLAG — indicates whether this assignment is the default for the event class.
• ASSIGNMENT_OWNER_CODE / ASSIGNMENT_OWNER_DSP — who owns the assignment (lookup XLA_OWNER_TYPE).
• JOURNAL_ENTRY_LEVEL_CODE / JOURNAL_ENTRY_LEVEL_NAME — the journal entry level at which the attribute is applied.
• ASSIGNMENT_GROUP_CODE / ASSIGNMENT_GROUP_NAME — the optional assignment group.
• DATATYPE_CODE, ASSIGNMENT_REQUIRED_CODE, ASSIGNMENT_LEVEL_CODE — datatype and requirement semantics of the attribute.
• Audit columns (CREATION_DATE, CREATED_BY, LAST_UPDATE_DATE, etc.).

Common Use Cases and Queries

Typical uses include diagnostics of subledger accounting setups, building custom value lists of accounting attributes, and feeding integration/reporting extracts that must show the descriptive name rather than the internal code.

• Retrieve all accounting attributes for a given event class:

SELECT event_class_code, accounting_attribute_name, assignment_owner_dsp
FROM   apps.xla_evt_class_acct_attrs_fvl
WHERE  application_id = :p_appl_id
AND    event_class_code = :p_event_class;

• Locate the attribute configured as the default for a class:

SELECT accounting_attribute_code, accounting_attribute_name
FROM   apps.xla_evt_class_acct_attrs_fvl
WHERE  default_flag = 'Y'
AND    application_id = :p_appl_id;

The view is read-only and should not be used for inserts or updates; it is intended strictly for query and display.