Search Results gl_transfer_mode_code




Overview

XLA_ACCT_LINE_TYPES_FVL is a validation view owned by the APPS schema within the Subledger Accounting (XLA) product of Oracle E-Business Suite, available in releases 12.1.1 and 12.2.2. It presents a denormalized, human-readable representation of the accounting line types defined for each subledger application and event class. Underlying records in the base tables store coded values and language-independent identifiers; this view resolves those codes into descriptive names by joining lookup views, translation tables, and application references. Its role is primarily reporting and integration: it allows developers, functional analysts, and integration teams to inspect how accounting line types are configured without decoding internal codes manually. The view exposes the accounting class code and its display meaning, which is why it surfaces frequently in queries searching for the "xla_accounting_class" concept.

Underlying Base Objects

Per the documented ETRM metadata, the view is defined over a fixed set of base objects: XLA_ACCT_LINE_TYPES_B (a synonym to the base table) supplies the core configuration columns and ROWID; XLA_ACCT_LINE_TYPES_TL provides the translated name and description for the line type. XLA_EVENT_CLASSES_TL supplies the event class name via a join on application, context, entity, and event class codes. XLA_APPLICATIONS_XVL resolves the application identifier into an application name. FND_ID_FLEX_STRUCTURES_V resolves TRANSACTION_COA_ID into a chart of accounts name. Multiple aliases of XLA_LOOKUPS (L, L1, L2, L3, L4) resolve the accounting line type, merge duplicate, accounting class, rounding class, and business class codes into their display meanings. GL_ENCUMBRANCE_TYPES supplies the encumbrance type description. The view is therefore a read-only projection whose column set mirrors the base table plus descriptive translations.

Key Columns

Common Use Cases and Queries

Typical uses include auditing accounting line type setup, validating that the correct accounting class is assigned before go-live, and feeding configuration extracts into integration tooling. A representative query lists enabled line types and their accounting classes for a given application:

SELECT application_name, event_class_name, accounting_line_type_dsp, accounting_class_dsp, enabled_flag FROM apps.xla_acct_line_types_fvl WHERE application_id = 200 AND enabled_flag = 'Y';

Another common pattern resolves the accounting class for a specific line type, directly addressing the "xla_accounting_class" search intent:

SELECT accounting_line_type_code, accounting_class_code, accounting_class_dsp FROM apps.xla_acct_line_types_fvl WHERE event_class_code = 'INVOICES';

Because the view performs all lookup and translation joins internally, queries against it avoid the multi-table resolution logic otherwise required against XLA_ACCT_LINE_TYPES_B and XLA_LOOKUPS, making it well suited to ad hoc reporting and diagnostic queries in both 12.1.1 and 12.2.2 environments.