Search Results xla_source_params




Overview
Explore in AI Chat

Overview

XLA_SOURCE_PARAMS is a table in the XLA schema owned by the Subledger Accounting (XLA) product within Oracle E-Business Suite 12.1.1 and 12.2.2. It stores all parameters used in the PL/SQL function that generates values for a user-defined source. In the Subledger Accounting architecture, sources represent the individual pieces of data captured on subledger transactions — such as amounts, quantities, dates, and descriptive attributes — that are subsequently mapped to accounting rules and journal line definitions. When a source is not supplied by a seeded subledger view but instead is derived through a user-defined PL/SQL function, that function requires input arguments. XLA_SOURCE_PARAMS is the repository in which those arguments are registered and configured, allowing XLA to invoke the function correctly during accounting generation and to pass the appropriate constant values or referenced source values.

The heuristic Data Vault classification mined from the foreign key structure is standalone, meaning the table holds no outgoing FK dependencies that would place it in a hub, link, or satellite role. In modeling terms, it is best treated as a configuration or reference table whose rows are defined per source and consumed at runtime by the Subledger Accounting engine rather than as a transactional fact.

Key Information Stored

The table contains sixteen documented columns. The most significant are described below, distinguishing the surrogate key from business-key candidates.

Two unique indexes act as business-key candidates: XLA_SOURCE_PARAMS_U1 (SOURCE_PARAM_ID, ZD_EDITION_NAME) and XLA_SOURCE_PARAMS_U2 (APPLICATION_ID, SOURCE_TYPE_CODE, SOURCE_CODE, USER_SEQUENCE, ZD_EDITION_NAME). The U2 key enforces that parameter sequence positions are unique within a given source, which is the natural business identifier.

Common Use Cases and Queries

Typical scenarios include auditing the configuration of user-defined sources, migrating source definitions between environments, and diagnosing accounting failures caused by mismatched or missing function arguments. A simple query lists all parameters for a source:

SELECT SOURCE_CODE, USER_SEQUENCE, PARAMETER_TYPE_CODE,
       CONSTANT_VALUE, REF_SOURCE_CODE
FROM   XLA.XLA_SOURCE_PARAMS
WHERE  APPLICATION_ID = :app_id
AND    SOURCE_TYPE_CODE = :type
AND    SOURCE_CODE = :code
ORDER BY USER_SEQUENCE;

A join to seeded source definitions helps validate that each referenced source actually exists, and joining to XLA_SOURCES on APPLICATION_ID, SOURCE_TYPE_CODE, and SOURCE_CODE confirms ownership. Reporting against this table is frequently used in implementation cutover checklists.

Related Objects

  • XLA_SOURCES — joined on APPLICATION_ID, SOURCE_TYPE_CODE, SOURCE_CODE; the parent source definition.
  • XLA_SOURCE_PARAMS self-join — REF_SOURCE_APPLICATION_ID, REF_SOURCE_TYPE_CODE, REF_SOURCE_CODE resolve to other source rows.
  • XLA_SOURCE_ASSIGNS — associates sources with subledger applications and transaction entities.
  • XLA_LEDGER_OPTIONS and XLA_EVENTS — downstream consumers that drive source extraction during accounting.
  • FND_APPLICATION — resolves APPLICATION_ID and REF_SOURCE_APPLICATION_ID to application names.