Search Results business_class_name

Overview

APPS.XLA_ACCT_LINE_TYPES_FVL is a supplementary view owned by the APPS schema and defined under the Subledger Accounting architecture (product short name XLA). Its FND Design Data reference is XLA.XLA_ACCT_LINE_TYPES_FVL, confirming it belongs to the XLA application definition. The view carries a status of VALID in both Oracle EBS 12.1.1 and 12.2.2. It is explicitly documented as a "supplementary view used to simplify forms coding," meaning it exists primarily to support the Subledger Accounting setup forms rather than as a public reporting interface. Oracle's documentation issues an explicit warning that querying or altering data through this view is not recommended, because its definition may change dramatically in subsequent minor or major releases.

The view exposes accounting line type definitions together with denormalized descriptive values — display names, event class names, application names, chart of accounts names, and lookup-derived display strings such as ACCOUNTING_CLASS_DSP. This makes it a convenient read-only source for identifying the accounting class, rounding class, merge duplicate behavior, and natural side associated with each subledger accounting line type.

Underlying Base Objects

The documented query text shows that XLA_ACCT_LINE_TYPES_FVL is defined over the following base objects:

• XLA_ACCT_LINE_TYPES_B — the base table holding accounting line type definitions, each row keyed by APPLICATION_ID, AMB_CONTEXT_CODE, ENTITY_CODE, EVENT_CLASS_CODE, and ACCOUNTING_LINE_TYPE_CODE.
• XLA_ACCT_LINE_TYPES_TL — the translation table supplying language-dependent NAME and DESCRIPTION values.
• XLA_APPLICATIONS_XVL — provides APPLICATION_NAME for the owning application.
• XLA_EVENT_CLASSES_TL — supplies EVENT_CLASS_NAME.
• FND_ID_FLEX_STRUCTURES_V — supplies TRANSACTION_COA_NAME for the transaction chart of accounts.
• GL_ENCUMBRANCE_TYPES — supplies ENCUMBRANCE_TYPE for encumbrance-enabled line types.
• XLA_LOOKUPS — resolves code values into display strings, notably ACCOUNTING_CLASS_DSP, ROUNDING_CLASS_DSP, and MERGE_DUPLICATE_DSP.

Because the view joins translation tables, it returns descriptions in the session's language, which is a principal reason it is used by forms rather than by high-volume extracts.

Key Columns

• APPLICATION_ID / APPLICATION_NAME — owning subledger application.
• AMB_CONTEXT_CODE, ENTITY_CODE, EVENT_CLASS_CODE / EVENT_CLASS_NAME — the accounting method context under which the line type is defined.
• ACCOUNTING_LINE_TYPE_CODE / ACCOUNTING_LINE_TYPE_DSP — the internal code and its display value.
• ACCOUNTING_CLASS_CODE / ACCOUNTING_CLASS_DSP — the accounting class (for example, asset, liability, revenue, expense), with the display form most commonly sought by users searching on "accounting_class_dsp".
• ROUNDING_CLASS_CODE / ROUNDING_CLASS_DSP — rounding behavior applied during journal line creation.
• MERGE_DUPLICATE_CODE / MERGE_DUPLICATE_DSP — duplicate line merge policy.
• NATURAL_SIDE_CODE, SWITCH_SIDE_FLAG, GAIN_OR_LOSS_FLAG — define debit/credit orientation and gain/loss handling.
• GL_TRANSFER_MODE_CODE, ACCOUNTING_ENTRY_TYPE_CODE — control how lines transfer to General Ledger.
• TRANSACTION_COA_ID / TRANSACTION_COA_NAME — chart of accounts associated with the transaction.
• MPA_OPTION_CODE, ENCUMBRANCE_TYPE_ID / ENCUMBRANCE_TYPE — multi-period accounting and encumbrance settings.
• ENABLED_FLAG and the standard WHO columns (CREATION_DATE, CREATED_BY, LAST_UPDATE_DATE, LAST_UPDATED_BY, LAST_UPDATE_LOGIN).

Common Use Cases and Queries

Typical uses include diagnosing why a subledger transaction generated a particular journal line classification, confirming the accounting class assigned to a line type, and verifying rounding or merge settings during implementation. Queries should remain read-only.

List line types with their accounting classes for an application and event class:

• SELECT accounting_line_type_code, accounting_line_type_dsp, accounting_class_dsp, rounding_class_dsp, enabled_flag FROM apps.xla_acct_line_types_fvl WHERE application_id = 222 AND event_class_code = 'ADJUSTMENT' ORDER BY accounting_line_type_code;

Search by display description where users only know the descriptive text:

• SELECT application_name, event_class_name, accounting_line_type_dsp, accounting_class_dsp FROM apps.xla_acct_line_types_fvl WHERE accounting_class_dsp IN ('Revenue', 'Expense') AND enabled_flag = 'Y';

Because the view depends on XLA_LOOKUPS and _TL tables, results reflect the current language and lookup configuration. For high-volume or integration extracts, Oracle's own guidance is to query the underlying XLA_ACCT_LINE_TYPES_B and associated lookup tables directly, so that custom code is insulated from changes to this convenience view.