Search Results xla_acctg_methods_b_u1

Overview

XLA.XLA_ACCTG_METHODS_B is a core configuration table in the Oracle E-Business Suite Subledger Accounting (SLA) architecture, owned by the XLA schema. It stores the accounting method definitions that drive how subledger transactions from Payables, Receivables, Assets, and other source applications are transformed into accounting entries for a given ledger. Each row associates an accounting method type with an accounting method code and defines the chart of accounts mapping between the transaction and the resulting accounting. This object is the base (non-translated) table; the corresponding translation table is XLA_ACCTG_METHODS_TL, while XLA_ACCTG_METHODS_VL exposes the denormalized view.

From a Data Vault modeling perspective, the metadata classifies this object as standalone, and the business keys are the composite (ACCOUNTING_METHOD_TYPE_CODE, ACCOUNTING_METHOD_CODE). This suggests treating the object as a hub-like reference entity — a configuration master rather than a transactional link or a slowly changing satellite.

Oracle explicitly flags this as Oracle Internal Use Only; direct DML is unsupported and access should occur through standard SLA setup forms or the public APIs.

Key Information Stored

The primary unique index, XLA_ACCTG_METHODS_B_U1, enforces uniqueness on ACCOUNTING_METHOD_TYPE_CODE and ACCOUNTING_METHOD_CODE (with ZD_EDITION_NAME in the 12.2.2 physical schema). The most important columns are:

• ACCOUNTING_METHOD_TYPE_CODE — Classifies the method type; part of the composite business key and unique index.
• ACCOUNTING_METHOD_CODE — The user-defined method code (30 characters); the second half of the composite business key.
• TRANSACTION_COA_ID — The chart of accounts of the source transaction.
• ACCOUNTING_COA_ID — The chart of accounts for which accounting is generated.
• ENABLED_FLAG — Internal flag indicating whether the method may be assigned to ledgers.
• CREATION_DATE / CREATED_BY — Standard WHO audit columns recording when and by whom the row was created (FK to FND_USER.USER_ID).
• LAST_UPDATE_DATE / LAST_UPDATED_BY / LAST_UPDATE_LOGIN — Standard WHO audit columns for the last change, with LAST_UPDATE_LOGIN referencing FND_LOGINS.LOGIN_ID.
• ZD_EDITION_NAME — Editioning column present in the 12.2.2 physical schema, supporting online patching (ADOP).

Common Use Cases and Queries

Typical usage includes validating which accounting methods are enabled, confirming COA mappings, and reconciling ledger assignments. Because the object predates the editioning changes, 12.1.1 and 12.2.2 queries differ slightly.

SELECT ACCOUNTING_METHOD_TYPE_CODE, ACCOUNTING_METHOD_CODE,
       TRANSACTION_COA_ID, ACCOUNTING_COA_ID, ENABLED_FLAG
FROM   XLA.XLA_ACCTG_METHODS_B
WHERE  ENABLED_FLAG = 'Y';

To find the method assigned to a ledger, join to XLA_LEDGERS (or the SLA ledger setup) via ACCOUNTING_METHOD_TYPE_CODE and ACCOUNTING_METHOD_CODE. Reporting use cases include auditing method-to-ledger coverage, checking for disabled methods still referenced, and validating that the transaction and accounting COA IDs align with the ledger's chart of accounts.

Related Objects

• XLA_ACCTG_METHODS_TL — Translation table holding the method name/description keyed by the same business key.
• XLA_ACCTG_METHODS_VL — Denormalized view joining base and translated rows.
• XLA_LEDGERS — Ledgers reference the accounting method via type and code.
• XLA_ACCTG_METHOD_RULES — Rule definitions that consume an accounting method.
• XLA_ACCT_METHOD_TYPES_B — Parent table for the accounting method type code.
• FND_USER — Referenced by CREATED_BY and LAST_UPDATED_BY.
• FND_LOGINS — Referenced by LAST_UPDATE_LOGIN.

All access should be read-only and is documented as Oracle Internal Use Only; customization should rely on supported SLA setup and APIs.