Search Results psbbv_constraint_sets

Overview

The PSBBV_CONSTRAINT_SETS view is a read-only database object within the Public Sector Budgeting (PSB) module of Oracle E-Business Suite. Its role is to expose the definition and descriptive attributes of constraint entity sets that drive budget validation and control logic in public sector budgeting scenarios. The view filters the underlying entity set repository to surface only those records whose entity type is 'CONSTRAINT', presenting each as a named constraint set with an associated threshold value and identity attributes.

In the context of Oracle EBS 12.1.1 and 12.2.2, this object is documented as part of the PSB module, which is flagged as obsolete in the ETRM metadata. Accordingly, PSBBV_CONSTRAINT_SETS is delivered for backward compatibility and for reporting against legacy public sector budgeting configuration data. It is not documented as implemented in the reference database and lists no referenced base objects in the metadata, meaning it should be treated primarily as a metadata artifact for environments where the PSB schema still exists and is populated. Where present, it functions as a reporting and integration surface for administrators and developers who need to query constraint set definitions without directly accessing the base table.

Underlying Base Objects

The view text selects exclusively from PSB_ENTITY_SET, filtered by the predicate ENTITY_TYPE = 'CONSTRAINT'. The documented ETRM metadata for the view lists no referenced base objects, and the object is recorded as "Not implemented in this database." This indicates that PSBBV_CONSTRAINT_SETS is a thin projection over PSB_ENTITY_SET, where a single underlying row maps directly to one row returned by the view. No joins, aggregations, or unions are involved, so row cardinality is preserved from source to view.

Because PSB_ENTITY_SET stores multiple entity types within the same physical structure, the ENTITY_TYPE discriminator is the key mechanism by which the view isolates constraint-related definitions from other entity set categories. This design pattern is consistent with other PSB reporting views that expose type-specific subsets of shared configuration tables without duplicating storage.

Key Columns

The view exposes the following named columns, which reconcile to the underlying PSB_ENTITY_SET attributes:

• CONSTRAINT_SET_NAME — the display name of the constraint set, derived from PES.NAME.
• DESCRIPTION — free-text description of the constraint set, derived from PES.DESCRIPTION.
• CONSTRAINT_THRESHOLD — the numeric threshold associated with the constraint set, taken directly from PES.CONSTRAINT_THRESHOLD.
• CONSTRAINT_SET_ID — the identifier of the constraint set, carried from PES.ENTITY_SET_ID.
• LAST_UPDATE_DATE — timestamp of the most recent modification.
• LAST_UPDATED_BY — the user identifier responsible for the most recent modification.
• CREATED_BY — the user identifier that created the record.
• CREATION_DATE — timestamp of record creation.

The final four columns are standard Oracle EBS audit columns, supporting change tracking and data lineage analysis. Note that the column alias CONSTRAINT_SET_NAME corresponds to the base column NAME in the underlying table.

Common Use Cases and Queries

Typical use cases include auditing the configured constraint sets that influence budget validation, reconciling constraint thresholds across entities, and extracting configuration for migration, reporting, or comparison against newer budgeting solutions that superseded the PSB module.

Because the view is read-only, only SELECT statements are applicable. A basic query is:

• SELECT CONSTRAINT_SET_NAME, CONSTRAINT_THRESHOLD FROM PSBBV_CONSTRAINT_SETS ORDER BY CONSTRAINT_SET_NAME;
• SELECT CONSTRAINT_SET_ID, DESCRIPTION, LAST_UPDATE_DATE, LAST_UPDATED_BY FROM PSBBV_CONSTRAINT_SETS WHERE CONSTRAINT_THRESHOLD IS NOT NULL;

Administrators performing change audits can join the view to FND_USER on the CREATED_BY or LAST_UPDATED_BY columns to resolve user names. Because the object is marked obsolete, its use should generally be limited to legacy support and historical reporting rather than new functional development.