Search Results xla_sources_b_u1

Overview

XLA.XLA_SOURCES_B is the base (non-translated) definition table for accounting sources within the Subledger Accounting (XLA) architecture in Oracle E-Business Suite 12.1.1 and 12.2.2. An accounting source describes an attribute of a subledger transaction line — such as quantity, unit price, or a distribution amount — that can be carried into a journal entry line as a source value and referenced by account derivation rules, journal line definitions, and supporting reference assignments. Each row identifies a source by the application that owns it, a source type classifier, and a source code, and specifies how the value is obtained at accounting time. The table is owned by the XLA schema, resides in the APPS_TS_TX_DATA tablespace, and is designated Oracle Internal Use Only; it must be accessed through supported Subledger Accounting programs and views rather than by direct DML.

From a Data Vault modeling perspective, the dependency metadata classifies this object as satellite-leaning. This is a heuristic suggestion: the table attaches descriptive and control attributes to the business key formed by application, source type, and source code, which is consistent with satellite behavior rather than a hub or link. The real hub keys (application and source type) are represented as plain columns rather than enforced foreign keys, with the sole documented foreign key referencing FND_APPLICATION through VIEW_APPLICATION_ID.

Key Information Stored

The documented business key is the combination APPLICATION_ID, SOURCE_TYPE_CODE, and SOURCE_CODE, which also forms the primary key XLA_SOURCES_B_PK. A second unique index, XLA_SOURCES_B_U1, extends this combination with ZD_EDITION_NAME and is stored in the APPS_TS_TX_IDX tablespace; the ZD_EDITION_NAME column supports the editioning mechanism introduced in Release 12.2. The most significant columns include:

• APPLICATION_ID — internal identifier of the application that owns the source.
• SOURCE_TYPE_CODE and SOURCE_CODE — the classification and unique code that identify the source.
• DATATYPE_CODE — the data type of the value the source returns.
• PLSQL_FUNCTION_NAME — the PL/SQL function invoked for non-standard sources; not applicable to standard sources.
• FLEX_VALUE_SET_ID — flex value set used when the source draws on a value set.
• VISIBLE_FLAG — controls whether the source appears in the list of values presented to users.
• SUM_FLAG and ENABLED_FLAG — internal flags governing summarization and availability of the source.
• KEY_FLEXFIELD_FLAG, SEGMENT_CODE, FLEXFIELD_APPLICATION_ID, and ID_FLEX_CODE — identify key flexfield sources and the specific accounting flexfield qualifier or segment from which the value is taken.
• SOURCE_TABLE_NAME and SOURCE_COLUMN_NAME — the physical table and column from which the source value is retrieved.
• LOOKUP_TYPE — lookup defining the valid values for the source.
• CREATION_DATE, CREATED_BY, LAST_UPDATE_DATE, LAST_UPDATED_BY, and LAST_UPDATE_LOGIN — standard WHO audit columns.

Common Use Cases and Queries

Typical usage includes identifying which sources are available for a given application or source type, auditing the PL/SQL function or table column behind a custom source, and verifying visibility or summarization behavior when configuring journal line definitions. Queries should filter on the business key rather than attempting mass extraction, and should join to translation tables for user-facing source names.

SELECT application_id, source_type_code, source_code,
       datatype_code, plsql_function_name, visible_flag
FROM   xla.xla_sources_b
WHERE  application_id = :app_id
AND    enabled_flag = 'Y';

Related Objects

Documented relationships and dependent objects of significance include:

• FND_APPLICATION — joined on VIEW_APPLICATION_ID = APPLICATION_ID to resolve the application owning a source view.
• XLA_SOURCES_TL — the translation table holding language-specific source names and descriptions, joined on APPLICATION_ID, SOURCE_TYPE_CODE, and SOURCE_CODE.
• XLA_SOURCES_VL — the view combining base and translated rows for user-facing queries.
• XLA_LINE_DEFNS_B — journal line definitions that reference sources when the output is set to a source value.
• XLA_ACCOUNTING_RULES_B and XLA_ACCOUNTING_RULE_DETAILS — account derivation rules that consume source values.
• XLA_DESCRIPTIONS_B — supporting reference and description definitions that may draw on the same sources.
• Subledger Accounting program APIs in the XLA package — supported interfaces for reading source definitions rather than direct table access.