Search Results psb_constraint_sets_v




Overview
Explore in AI Chat

Overview

The view PSB_CONSTRAINT_SETS_V belongs to the PSB – Public Sector Budgeting product within Oracle E-Business Suite. In the ETRM 12.1.1 and 12.2.2 documentation, PSB is explicitly flagged as Obsolete, meaning that the product and its underlying schema objects are no longer implemented in current database instances and are retained only for historical reference and backward-compatible metadata purposes.

The view exists to expose constraint entity sets — records classified with an ENTITY_TYPE of 'CONSTRAINT' — from the base entity-set storage. These constraint sets define the thresholds and grouping used during budget constraint validation, determining whether budget entries fall within defined limits. Despite its obsolescence, understanding the view remains relevant for legacy reporting, data migration assessments, and audit of historical budgeting configurations. In ETRM 12.2.2, the documented owner is blank and no referenced base objects are formally documented, and the implementation note confirms the object is "Not implemented in this database."

Underlying Base Objects

The view text selects directly from a single base table, PSB_ENTITY_SET, applying the filter predicate WHERE ENTITY_TYPE = 'CONSTRAINT'. The PSB_ENTITY_SET table stores multiple classes of entity sets, and the view narrows that population to constraint-type records only, so downstream consumers do not need to repeat the entity-type filter.

Although the ETRM metadata lists no formally documented referenced base objects for the 12.2.2 release, the view's own DDL identifies PSB_ENTITY_SET as its sole source. The view additionally selects ROWID, which is surfaced under the column alias ROW_ID. Note that the SELECT list and the documented column list are not perfectly aligned: the query selects ENTITY_SET_ID while the column listing shows CONSTRAINT_SET_ID, an inconsistency typical of legacy metadata.

Key Columns

  • ROW_ID – The physical ROWID of the underlying PSB_ENTITY_SET row, useful for direct row addressing.
  • CONSTRAINT_SET_ID (selected as ENTITY_SET_ID) – The primary identifier for the constraint set.
  • NAME / DESCRIPTION – The user-facing label and narrative for the constraint set.
  • CONSTRAINT_THRESHOLD – The numeric threshold applied when validating budgets against the constraint set; this is the column most frequently searched by users.
  • BUDGET_GROUP_ID – Links the constraint set to its associated budget group.
  • SET_OF_BOOKS_ID – The ledger/book context in which the constraint set operates.
  • DATA_EXTRACT_ID – Identifier tying the record to a data extraction process.
  • ATTRIBUTE1–ATTRIBUTE10, CONTEXT – Descriptive flexfield segments and the context value.
  • Audit columns – LAST_UPDATE_DATE, LAST_UPDATED_BY, CREATED_BY, CREATION_DATE, and LAST_UPDATE_LOGIN.

Common Use Cases and Queries

Typical usage centers on reviewing or migrating legacy budget constraint thresholds. A representative query retrieves sets by ledger and threshold:

  • SELECT constraint_set_id, name, constraint_threshold, set_of_books_id FROM psb_constraint_sets_v WHERE set_of_books_id = :p_sob;
  • SELECT name, constraint_threshold FROM psb_constraint_sets_v WHERE constraint_threshold > :p_value ORDER BY constraint_threshold;
  • SELECT c.constraint_set_id, c.name FROM psb_constraint_sets_v c WHERE c.budget_group_id = :p_group;

Because the product is obsolete, these queries are principally relevant to historical data analysis and migration discovery rather than active production reporting.