Search Results xla_tab_acct_type_srcs_u1

Overview

XLA.XLA_TAB_ACCT_TYPE_SRCS is a reference and configuration table in the Oracle E-Business Suite Subledger Accounting (XLA) schema. It maps transaction account types to the source transactions that feed them, allowing the Subledger Accounting engine to determine which source application, source type, and source code combination contributes values to a given account type during journal entry creation. The object resides in the APPS_TS_TX_DATA tablespace with a PCT Free of 10 and is owned by the XLA schema. Oracle classifies the object with a VALID status and explicitly restricts access to standard Oracle Applications programs through the standard "Oracle Internal Use Only" designation.

From a data modeling perspective, the heuristic Data Vault classification of this object is standalone. The mined dependency information indicates that XLA_TAB_ACCT_TYPE_SRCS does not reference any other database object, and its structure is best understood as a reference or lookup table rather than a hub, link, or satellite in a strict Data Vault sense. It is a control table that anchors the relationship between account types and their permitted sources.

Key Information Stored

The table is composed of 11 documented columns. The most significant are as follows:

• APPLICATION_ID (NUMBER(15), mandatory) — The application identifier that owns the account type definition.
• ACCOUNT_TYPE_CODE (VARCHAR2(30), mandatory) — The transaction account type code being mapped.
• SOURCE_APPLICATION_ID (NUMBER(15), mandatory) — The application identifier of the contributing source.
• SOURCE_TYPE_CODE (VARCHAR2, mandatory) — The type of source that supplies the account type.
• SOURCE_CODE (VARCHAR2(30), mandatory) — The specific source code within the source type.
• CREATION_DATE, CREATED_BY, LAST_UPDATE_DATE, LAST_UPDATED_BY, LAST_UPDATE_LOGIN — Standard WHO columns capturing audit and accountability information, with CREATED_BY and LAST_UPDATED_BY referencing FND_USER.USER_ID and LAST_UPDATE_LOGIN referencing FND_LOGINS.LOGIN_ID.
• ZD_EDITION_NAME — The editioning column present in the 12.2.2 physical schema and included in the unique index.

The surrogate/business primary key is documented as XLA_TAB_ACCT_TYPE_SRCS_PK, comprising APPLICATION_ID, ACCOUNT_TYPE_CODE, SOURCE_APPLICATION_ID, SOURCE_TYPE_CODE, and SOURCE_CODE. The unique index XLA_TAB_ACCT_TYPE_SRCS_U1 mirrors these business-key columns (with ZD_EDITION_NAME added in the 12.2.2 editioning model). A non-unique index, XLA_TAB_ACCT_TYPE_SRCS_N1, exists to support lookups by SOURCE_APPLICATION_ID, SOURCE_TYPE_CODE, and SOURCE_CODE.

Common Use Cases and Queries

This table is typically queried to understand which sources are authorized to populate a given account type, to validate configuration integrity, and to troubleshoot Subledger Accounting journal line generation. A representative query retrieves all mappings for a specific account type:

• SELECT * FROM XLA.XLA_TAB_ACCT_TYPE_SRCS WHERE ACCOUNT_TYPE_CODE = :p_account_type;
• SELECT ACCOUNT_TYPE_CODE, SOURCE_TYPE_CODE, SOURCE_CODE FROM XLA.XLA_TAB_ACCT_TYPE_SRCS WHERE SOURCE_APPLICATION_ID = :p_app_id;

Reporting scenarios commonly include configuration audit extracts that list permitted account-type/source combinations, and diagnostic queries that verify whether an unexpected account type is being populated by an unintended source. Because the table is a control object, queries should normally be read-only and executed against a cloned or reporting instance, given the Oracle restriction on direct access.

Related Objects

The following objects are the most significant references and dependencies associated with this table:

• XLA_ACCOUNT_TYPE_SRCS — The transactional counterpart holding similar source definitions.
• XLA_ACCOUNTING_OPTIONS — Subledger accounting configuration that consults account type/source mappings.
• FND_USER — Referenced by CREATED_BY and LAST_UPDATED_BY.
• FND_LOGINS — Referenced by LAST_UPDATE_LOGIN.
• XLA_TRANSACTION_ENTITIES — Source transaction entities processed by the accounting engine.
• XLA_EVENTS — Events generated against sources defined in this table.
• XLA_AE_HEADERS and XLA_AE_LINES — The resulting subledger journal entries.
• XLA_ACCT_TYPE_SRCS_VL — A potential multilingual view exposing account type/source mappings.

Join keys should use APPLICATION_ID, ACCOUNT_TYPE_CODE, SOURCE_APPLICATION_ID, SOURCE_TYPE_CODE, and SOURCE_CODE consistently to align this mapping table with downstream Subledger Accounting data.