Results for “xtr_settlement_categories”

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

Overview

XTR_SETTLEMENT_CATEGORIES is a reference (setup) table in the Oracle E-Business Suite Treasury module (XTR). It stores the configurable categories used to organize and classify settlement actions within Treasury. Settlement actions in ETRM encompass the payment, receipt, and netting instructions generated from treasury transactions such as deals, foreign exchange contracts, and debt instruments. By grouping these actions into user-defined categories, Treasury users gain a mechanism for routing, reporting, and defaulting settlement behavior consistently across counterparties and parties.

The table resides in the XTR schema and is marked VALID in the documented ETRM 12.2.2 environment, with an equivalent presence in 12.1.1. The documented physical schema is intentionally small: two columns only. Its Data Vault classification, mined heuristically from the foreign-key structure, is hub-leaning. In Data Vault modeling terms this suggests the table functions primarily as a hub — a stable list of unique business concepts (settlement categories) that is referenced by other tables rather than acting as a transactional link or a descriptive satellite. The absence of inbound foreign keys pointing to satellite-style attribute tables reinforces this interpretation.

Key Information Stored

The documented column set for XTR_SETTLEMENT_CATEGORIES comprises two columns:

• SETTLEMENT_CATEGORY — the primary business identifier for each settlement category. It is the single column forming the primary key constraint XTR_SETTLEMENT_CATEGORIES_PK and therefore serves as the business-key candidate and unique identifier for every row. Category values defined here are the ones selected by users when configuring settlement defaults.
• DESCRIPTION — the descriptive label associated with each settlement category, providing the human-readable name displayed in Treasury setup and transaction forms.

Because the table contains only these two columns, there is no separate meaningless surrogate key in the documented schema; the primary key itself is the business key. SETTLEMENT_CATEGORY consequently acts as both the unique index column and the value propagated into dependent foreign-key columns. No additional attributes such as enabled flags, dates, or category types are documented, so any implementation-specific extensions should be verified against the actual database.

Common Use Cases and Queries

Settlement categories are most commonly queried to support setup validation, defaulting logic, and Treasury reporting. A typical lookup joins the category to its consumers to confirm which parties use a given category:

• Listing all defined categories with their descriptions for setup review or a valueset definition.
• Identifying parties whose default settlement category is a specific value.
• Detecting orphaned or unused categories by left-joining to dependent tables.
• Reporting transaction settlement activity grouped by category.

Representative SQL patterns include:

SELECT settlement_category, description FROM xtr.xtr_settlement_categories ORDER BY settlement_category;

SELECT p.party_id, p.settlement_default_category, c.description FROM xtr.xtr_party_info p, xtr.xtr_settlement_categories c WHERE p.settlement_default_category = c.settlement_category;

SELECT c.settlement_category, c.description, COUNT(p.party_id) FROM xtr.xtr_settlement_categories c LEFT JOIN xtr.xtr_party_info p ON p.settlement_default_category = c.settlement_category GROUP BY c.settlement_category, c.description;

Related Objects

The documented foreign-key relationships show two tables referencing XTR_SETTLEMENT_CATEGORIES, both using the SETTLEMENT_DEFAULT_CATEGORY column:

• XTR_PARTY_INFO — references XTR_SETTLEMENT_CATEGORIES via XTR_PARTY_INFO.SETTLEMENT_DEFAULT_CATEGORY, storing the default settlement category for a given party.
• XTR_PARTY_DEFAULTS — references XTR_SETTLEMENT_CATEGORIES via XTR_PARTY_DEFAULTS.SETTLEMENT_DEFAULT_CATEGORY, defining default settlement configuration at the party-defaults level.

These two dependents are the principal consumers of the hub. Additional Treasury objects that generate or process settlement actions (deal and settlement instruction tables) logically depend on the category concept, but the documented FK evidence supplied here identifies XTR_PARTY_INFO and XTR_PARTY_DEFAULTS as the authoritative referencing tables. When joining, always use SETTLEMENT_CATEGORY to SETTLEMENT_DEFAULT_CATEGORY to preserve referential integrity.