Search Results xla_tab_acct_type_srcs




Overview
Explore in AI Chat

Overview

The XLA.XLA_TAB_ACCT_TYPE_SRCS table is a Subledger Accounting (XLA) configuration table in Oracle E-Business Suite 12.1.1 and 12.2.2. It stores Transaction Account Type Sources, which define the set of source assignments that feed a given account type for a particular application. In the Subledger Accounting architecture, this table acts as the bridge between an accounting event's application context and the specific transaction sources used to derive accounting attribute balances, ultimately driving journal line creation. It is a setup/definition table populated during the configuration of accounting methods rather than a high-volume transactional table.

From a data-modeling perspective, the ETRM metadata classifies this object heuristically as standalone, meaning it exhibits no outbound foreign key dependencies within the documented FK structure. In Data Vault terms, this suggests a hub-like reference entity rather than a link or satellite: it holds an enumerated set of account-type-to-source mappings keyed by business codes, with descriptive/audit attributes carried inline.

Key Information Stored

The table is defined in the XLA schema and contains 11 documented columns. Its structure separates a composite surrogate primary key from a business-key candidate:

The unique index XLA_TAB_ACCT_TYPE_SRCS_U1 extends the primary key with ZD_EDITION_NAME, making it the business-key candidate that guarantees uniqueness across editions.

Common Use Cases and Queries

Consultants and developers query this table when diagnosing why a particular account type is or is not being sourced during subledger accounting. Typical scenarios include resolving missing journal lines, auditing accounting method setup after a patch or clone, and validating configuration migrations between environments.

SELECT application_id,
       account_type_code,
       source_application_id,
       source_type_code,
       source_code
FROM   xla.xla_tab_acct_type_srcs
WHERE  application_id = :app_id
AND    account_type_code = :acct_type;

For 12.2.x, filtering on ZD_EDITION_NAME may be necessary to isolate the active edition. Comparison queries across environments or between 12.1.1 and 12.2.2 help identify configuration drift.

Related Objects

Because the table is classified as standalone with no documented FK edges, relationships are logical rather than enforced: