Search Results xla_acctg_methods_b




Overview
Explore in AI Chat

Overview

The XLA_ACCTG_METHODS_B table resides in the XLA schema, which is the foundation of Oracle Subledger Accounting (SLA). It stores Subledger Accounting Methods (SLAM), the configuration objects that define how subledger transactions are transformed into accounting entries, and which accounting rules, journal line types, and mapping sets are applied. A SLAM is therefore the central policy object that determines the accounting treatment of transactions across all subledgers, including Payables, Receivables, Assets, and Payroll.

Subledger Accounting Methods delivered by Oracle development are not chart of accounts specific; they are seeded as generic templates. An enabled SLAM must be assigned to one or more ledgers before it can be driven by transactions. The table stores both the method definition and its ledger assignment scope, and in the 12.2.2 documented schema it contains 11 columns.

From a heuristic Data Vault modeling perspective, XLA_ACCTG_METHODS_B behaves as a standalone construct. The relationship classification supplied with the object metadata is standalone, meaning it does not participate in a documented foreign-key dependency to another parent hub. In a Data Vault representation it would most naturally be treated as a hub keyed on the accounting method business key, with descriptive attributes such as enablement and chart of accounts identifiers carried on a satellite.

Key Information Stored

The primary key of the table is XLA_ACCTG_METHODS_B_PK, defined on the composite of ACCOUNTING_METHOD_TYPE_CODE and ACCOUNTING_METHOD_CODE. A second unique index, XLA_ACCTG_METHODS_B_U1, extends this business key with ZD_EDITION_NAME, reflecting the edition-based redefinition (EBR) architecture introduced in EBS 12.2. The most significant columns are:

  • ACCOUNTING_METHOD_TYPE_CODE — classifies the method type; part of the primary key and business key.
  • ACCOUNTING_METHOD_CODE — the unique short name of the Subledger Accounting Method; part of the primary key and business key.
  • TRANSACTION_COA_ID — the chart of accounts identifier associated with the transaction side of the method.
  • ACCOUNTING_COA_ID — the chart of accounts identifier associated with the accounting side of the method.
  • ENABLED_FLAG — indicates whether the method is enabled for use and available for ledger assignment.
  • ZD_EDITION_NAME — the edition identifier supporting EBR, and a component of the unique business-key index.
  • CREATION_DATE, CREATED_BY — standard audit columns capturing who created the method and when.
  • LAST_UPDATE_DATE, LAST_UPDATED_BY, LAST_UPDATE_LOGIN — standard audit columns capturing the most recent modification and the login under which it occurred.

The surrogate primary key columns are ACCOUNTING_METHOD_TYPE_CODE and ACCOUNTING_METHOD_CODE; the business-key candidate is the combination of those two plus ZD_EDITION_NAME.

Common Use Cases and Queries

The most common reporting requirement is to list enabled Subledger Accounting Methods along with their ledger assignments, and to audit which ledgers use which method. A typical query pattern joins this table to its translation table and to the ledger assignment objects:

  • Listing enabled methods: SELECT accounting_method_code, accounting_method_type_code, enabled_flag FROM xla_acctg_methods_b WHERE enabled_flag = 'Y';
  • Retrieving the base method name for a given code from the corresponding translation table (XLA_ACCTG_METHODS_TL) using ACCOUNTING_METHOD_CODE as the join key.
  • Determining which ledger uses a given SLAM by joining assignment tables on the same method code and type.
  • Auditing method creation and changes using CREATION_DATE, CREATED_BY, LAST_UPDATE_DATE, and LAST_UPDATED_BY.
  • Resolving chart of accounts context through TRANSACTION_COA_ID and ACCOUNTING_COA_ID against the accounting chart of accounts.

Because the table is edition-aware, queries in a 12.2 environment should filter or join on ZD_EDITION_NAME to avoid returning multiple editions of the same method.

Related Objects

The following objects are significant in the context of Subledger Accounting Methods, joining on the documented key columns:

Together these objects complete the chain from method definition, through ledger assignment and rule application, to the creation of subledger journal entries.