Results for “xtr_settlement_categories_v”

16 results




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

Overview

XTR_SETTLEMENT_CATEGORIES_V is a reporting view owned by the APPS schema in the Oracle E-Business Suite Treasury (XTR) module. It exposes a simplified, read-oriented projection of settlement category definitions used by Treasury to classify and group settlement activity. The view presents two columns — SETTLEMENT_CATEGORY and DESCRIPTION — drawn from the underlying settlement category base object, providing a stable interface for concurrent programs, Oracle Reports, Oracle Discoverer workbooks, and custom integrations that need to enumerate valid settlement categories without querying the base table directly.

Because the view is documented as VALID in the ETRM metadata for release 12.2.2, it is a supported object for the Treasury product family. Settlement categories play a role in Treasury settlement processing, where cash flows, deal settlements, and payment instructions are grouped for reporting, netting, and reconciliation. The view therefore functions as a lightweight lookup surface, isolating consumers from the physical storage of the settlement category definitions.

Underlying Base Objects

The view is defined over a single referenced base object: XTR_SETTLEMENT_CATEGORIES, resolved at runtime through the synonym XTR_SETTLEMENT_CATEGORIES. The documented view text is a straightforward projection:

  • SELECT SETTLEMENT_CATEGORY, DESCRIPTION FROM XTR_SETTLEMENT_CATEGORIES

No joins, filters, or aggregation are applied in the view text. Consequently, XTR_SETTLEMENT_CATEGORIES_V does not transform or enrich the underlying data; it simply surfaces the two exposed attributes of every row present in XTR_SETTLEMENT_CATEGORIES. The relationship between the view and its base object is therefore one-to-one. The synonym points to the APPS-owned base table, consistent with standard EBS naming conventions where XTR objects reside in the APPS schema. Because the view contains no WHERE clause, it returns all defined settlement categories, including any that may be inactive or otherwise system-maintained, so consumers should not assume that every returned row represents an active selection available at transaction entry.

Key Columns

  • SETTLEMENT_CATEGORY — The identifier (code) for the settlement category. This is the primary lookup value used to group or classify settlement-related records. It is typically referenced by foreign key relationships in other Treasury entities that require a settlement category assignment.
  • DESCRIPTION — The descriptive text associated with the settlement category. This is the user-facing label presented in list of values (LOV) prompts, reports, and inquiry screens.

Both columns retain the data types and lengths of their base-table counterparts. No derived columns, flags, or status indicators are exposed by this view, which is a relevant limitation when a consumer needs to determine whether a category remains usable.

Common Use Cases and Queries

The most frequent use is populating a selection list or validating a user-supplied code. A simple enumeration query returns every category:

  • SELECT settlement_category, description FROM apps.xtr_settlement_categories_v ORDER BY settlement_category;

A filtered lookup retrieves the description for a specific code supplied by an interface or report parameter:

  • SELECT description FROM apps.xtr_settlement_categories_v WHERE settlement_category = :p_settlement_category;

For integration scenarios, the view is commonly joined to settlement or deal tables on the settlement category code to produce user-readable output, avoiding hard-coded decode logic in reports. Typical consumers include Treasury concurrent programs, custom Oracle Reports, and inbound interfaces that must verify a settlement category exists before loading settlement data. Because the view exposes only two columns and applies no filtering, it is well suited to cached lookup patterns; however, implementations requiring active/inactive status must query the base table XTR_SETTLEMENT_CATEGORIES directly, since that information is not available through this view.