Results for “xtr_source_types”

AI-generated from documented ETRM metadata — verify critical details on the linked pages.

Overview

XTR_SOURCE_TYPES is a Treasury (XTR) module reference table in Oracle E-Business Suite 12.1.1 and 12.2.2. It stores the set of internal Oracle E-Business applications and source systems that may be designated as the origin of financial instruments used for derivative and hedge accounting. Each row defines a valid "source type" that downstream hedge policies and hedge relationships can reference, ensuring that only recognized internal sources are eligible for hedge accounting treatment under the Treasury derivative and hedging framework.

The table functions as a controlled lookup or enumeration of source definitions rather than a transactional table. Rows are typically seeded or configured during implementation and changed infrequently. From a dimensional modeling perspective, the metadata's heuristic Data Vault classification is hub-leaning: SOURCE_TYPE_ID behaves as a durable business key that receives foreign-key references from multiple dependent tables. This classification is offered as a modeling suggestion; the physical table itself is a standard EBS reference entity with audit columns.

Key Information Stored

The documented physical schema contains eleven columns. The most significant are:

• SOURCE_TYPE_ID — The surrogate primary key, enforced by the XTR_SOURCE_TYPES_PK constraint. It is the value propagated to foreign-key columns in dependent tables.
• SOURCE_CODE — The business-facing code identifying the internal Oracle application or source system. Together with SUB_SOURCE_CODE this forms the principal business-key candidate.
• SUB_SOURCE_CODE — A secondary qualifier that narrows the source to a specific subsystem, ledger, or process within the parent source code.
• INSTRUMENT_ITEM_CATEGORY — The item category used to classify instruments originating from this source, supporting valuation and categorization logic.
• INSTRUMENT_ITEM_FLAG — A flag indicating whether the source participates in instrument item processing, effectively an eligibility or enablement indicator.
• CREATED_BY, CREATION_DATE, LAST_UPDATED_BY, LAST_UPDATE_DATE, LAST_UPDATE_LOGIN — Standard EBS audit columns recording who created and last modified each row and when.
• ZD_EDITION_NAME — The editioning column used by the EBS online patching (adop) infrastructure in 12.2.x; it is absent or non-functional in 12.1.1.

The surrogate key SOURCE_TYPE_ID is purely technical, while SOURCE_CODE and SUB_SOURCE_CODE carry the business meaning. Any unique index on the code pair, if present, would represent the true business key.

Common Use Cases and Queries

Typical use cases include validating and reporting which sources are available for hedge accounting, and joining configuration data to hedge policies and relationships. A basic lookup query resembles:

• SELECT source_type_id, source_code, sub_source_code, instrument_item_category FROM xtr_source_types ORDER BY source_code;
• Joining to dependent transaction tables: SELECT h.hedge_policy_id, s.source_code FROM xtr_hedge_policies h, xtr_source_types s WHERE h.source_type_id = s.source_type_id;
• Reporting enabled sources only: filter on instrument_item_flag to list sources participating in instrument processing.
• Setup validation: confirm no orphaned references by counting dependent rows per source type.

Because the table is small and static, queries are inexpensive and are frequently embedded in concurrent programs, discovery reports, and Treasury setup listings.

Related Objects

The following objects reference XTR_SOURCE_TYPES via the documented foreign keys and are the most significant dependents:

• XTR_HEDGE_POLICIES — references this table through XTR_HEDGE_POLICIES.SOURCE_TYPE_ID. A hedge policy is scoped to a specific source type.
• XTR_HEDGE_RELATIONSHIPS — references this table through XTR_HEDGE_RELATIONSHIPS.SOURCE_TYPE_ID. Each hedge relationship records the source type that originated the hedged instrument.

These two foreign-key relationships establish XTR_SOURCE_TYPES as an upstream reference entity within the Treasury hedge accounting data model. Changes to source type definitions propagate in meaning to all hedge policies and relationships that reference them, so maintenance should be performed with care during implementation and any post-production configuration wave.