Search Results xla_tab_acct_type_srcs_pk

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:

• Primary Key (XLA_TAB_ACCT_TYPE_SRCS_PK): composed of APPLICATION_ID, ACCOUNT_TYPE_CODE, SOURCE_APPLICATION_ID, SOURCE_TYPE_CODE, and SOURCE_CODE.
• APPLICATION_ID: the owning application (e.g., Payables, Receivables) whose account types are being sourced.
• ACCOUNT_TYPE_CODE: identifies the target account type (for example, liability, expense, or asset) receiving the source assignment.
• SOURCE_APPLICATION_ID: the application that owns the referenced source, which may differ from the owning application.
• SOURCE_TYPE_CODE: classifies the source category used in the mapping.
• SOURCE_CODE: the specific source identifier mapped to the account type.
• Audit columns: CREATION_DATE, CREATED_BY, LAST_UPDATE_DATE, LAST_UPDATED_BY, and LAST_UPDATE_LOGIN capture standard WHO information.
• ZD_EDITION_NAME: the editioning column introduced in 12.2.x to support Online Patching (ADOP) and Edition-Based Redefinition.

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:

• XLA_ACCOUNTING_METHODS / XLA_ACCT_TYPE_SOURCES: reference the same account-type and source codes that define accounting method behavior. Join on APPLICATION_ID and ACCOUNT_TYPE_CODE.
• XLA_SOURCES_B / XLA_SOURCES_TL: resolve SOURCE_CODE and SOURCE_TYPE_CODE to source names. Join on SOURCE_APPLICATION_ID and SOURCE_CODE.
• XLA_APPL_INSTALLATIONS: validates APPLICATION_ID and SOURCE_APPLICATION_ID as installed applications.
• FND_APPLICATION / FND_APPLICATION_TL: resolves application IDs to names for reporting.
• FND_ID_FLEX_STRUCTURES: supports downstream account derivation logic tied to these mappings.