Search Results xla_acctg_methods_vl




Overview
Explore in AI Chat

Overview

The view XLA_ACCTG_METHODS_VL is an Oracle E-Business Suite (EBS) Subledger Accounting (XLA) dictionary view owned by the APPS schema. It exposes translated accounting method definitions maintained by the Subledger Accounting application. In Oracle EBS 12.1.1 and 12.2.2, Subledger Accounting methods determine how subledger transactions are converted into accounting entries, governing the mapping of transaction attributes to the General Ledger chart of accounts, the derivation rules applied, and the creation of journal entries. This view consolidates the definitional data held in the base tables and joins it to the translation table so that the NAME and DESCRIPTION columns are returned in the session language of the querying user.

The object is a "VL" (view language) view, meaning it presents the single-row-per-entity descriptive columns resolved against the user's current language environment. It is read-only and is intended for reporting, integration, and inquiry purposes rather than for direct data maintenance. Because it derives language from USERENV('LANG'), the output for the same accounting method can differ between users or sessions set to different languages.

Underlying Base Objects

The documented view text selects from two base objects, both exposed in APPS through synonyms:

  • XLA_ACCTG_METHODS_B — the base table holding the language-independent accounting method definition, including method codes, type codes, chart of accounts references, enablement, and audit columns.
  • XLA_ACCTG_METHODS_TL — the translation table holding the language-dependent NAME and DESCRIPTION values, keyed by accounting method code, accounting method type code, and LANGUAGE.

The two are joined on ACCOUNTING_METHOD_CODE and ACCOUNTING_METHOD_TYPE_CODE, with the translation restricted to the session language via T.LANGUAGE = USERENV('LANG'). This structure follows the standard Oracle translation (TL) pattern in which descriptive attributes are separated from the transactional base.

Key Columns

  • ROW_ID — the ROWID of the underlying base row in XLA_ACCTG_METHODS_B, useful for direct correlation to the base table.
  • ACCOUNTING_METHOD_TYPE_CODE — identifies the accounting method type category to which the method belongs.
  • ACCOUNTING_METHOD_CODE — the unique internal code that identifies the accounting method definition.
  • NAME — the translated display name of the accounting method.
  • DESCRIPTION — the translated description of the accounting method.
  • TRANSACTION_COA_ID — the chart of accounts identifier associated with the transaction side of the definition.
  • ACCOUNTING_COA_ID — the chart of accounts identifier used for the resulting accounting entries.
  • ENABLED_FLAG — indicates whether the accounting method is currently active and available for use.
  • CREATION_DATE, CREATED_BY, LAST_UPDATE_DATE, LAST_UPDATED_BY, LAST_UPDATE_LOGIN — standard audit columns recording who created and last modified the definition.

Common Use Cases and Queries

Typical uses include validating which accounting methods are active, confirming the chart of accounts mapping applied to each method, and joining to Subledger Accounting setup tables to trace application accounting definitions. The following query lists all enabled accounting methods along with their translated names:

SELECT accounting_method_type_code,
       accounting_method_code,
       name,
       description,
       enabled_flag
FROM   xla_acctg_methods_vl
WHERE  enabled_flag = 'Y'
ORDER BY name;

To inspect the chart of accounts configuration for a specific method, the view can be filtered by method code:

SELECT accounting_method_code,
       name,
       transaction_coa_id,
       accounting_coa_id
FROM   xla_acctg_methods_vl
WHERE  accounting_method_code = :method_code;

Because NAME and DESCRIPTION depend on USERENV('LANG'), reports intended for a specific locale should ensure the session language is set appropriately before querying, or join the base tables directly when language-independent behavior is required.