Search Results accounting_method_code




Overview
Explore in AI Chat

Overview

The XLA_ACCTG_METHODS_FVL view in the APPS schema is a foundational data dictionary object within the Subledger Accounting (XLA) module of Oracle E-Business Suite 12.1.1 and 12.2.2. It presents a joined, user-facing representation of the accounting methods that govern how subledger transactions are converted into General Ledger journal entries. The "FVL" suffix denotes a "Foreign-key Validation" or "Full Validation" listing view, and it is typically attached to descriptive or key flexfield reference fields so that lookup-enabled, language-translated accounting method values can be selected in forms and reports without directly querying the underlying base tables. For consultants and developers searching on accounting_method_code, this view is the primary source for resolving the code into its descriptive name, its accounting method type meaning, and its associated chart of accounts contexts.

Underlying Base Objects

Per the documented ETRM metadata, the view is defined over four referenced objects: XLA_ACCTG_METHODS_B (a synonym, or base table, holding the core accounting method definition), XLA_ACCTG_METHODS_TL (the translated table supplying language-specific name and description), XLA_LOOKUPS (a view supplying the meaning of the accounting method type), and FND_ID_FLEX_STRUCTURES_V (a view resolving the key flexfield structures). The join logic is significant: XLA_ACCTG_METHODS_B is joined to XLA_ACCTG_METHODS_TL on both ACCOUNTING_METHOD_CODE and ACCOUNTING_METHOD_TYPE_CODE, restricted by the session language via USERENV('LANG'). The type code is joined to XLA_LOOKUPS where the lookup type equals XLA_OWNER_TYPE. Both chart-of-accounts identifiers are outer-joined (indicated by the (+) operator) to FND_ID_FLEX_STRUCTURES_V on ID_FLEX_NUM, with ID_FLEX_CODE = 'GL#' and APPLICATION_ID = 101, meaning flexible or missing COA definitions do not suppress the returned row.

Key Columns

The view exposes a stable set of columns used throughout XLA configuration and reporting:

Common Use Cases and Queries

The view is most frequently used to translate an internal accounting method code into something meaningful, to validate enabled methods for a given subledger, or to feed integrations and concurrent programs. A typical query resolves a code to its descriptive attributes:

  • Listing active methods: SELECT accounting_method_code, name, transaction_coa_name, accounting_coa_name FROM xla_acctg_methods_fvl WHERE enabled_flag = 'Y' ORDER BY name;
  • Resolving a specific code: SELECT name, description, accounting_method_type_dsp FROM xla_acctg_methods_fvl WHERE accounting_method_code = :code;
  • Filtering by subledger type: SELECT accounting_method_code, name FROM xla_acctg_methods_fvl WHERE accounting_method_type_code = 'PAYABLES';

Because the view is language-aware and pre-joins the flexfield validation structures, it should be preferred over direct queries to XLA_ACCTG_METHODS_B wherever human-readable output is required.