Search Results constraint_set_id




Overview
Explore in AI Chat

Overview

APPS.PSBBV_CONSTRAINT_SETS is a Business Intelligence System (BIS) view owned by the APPS schema in Oracle E-Business Suite. It is registered in the application design repository under the FND Design Data identifier PSB.PSBBV_CONSTRAINT_SETS and holds a VALID status in both release 12.1.1 and 12.2.2. The view presents the definition of constraint sets used by Oracle Advanced Planning and Scheduling (APS) constraint-based planning functionality, exposing the core attributes of each constraint set in a flat, denormalized form suitable for reporting, discovery, and integration.

Rather than requiring report authors to navigate multiple base tables, PSBBV_CONSTRAINT_SETS aggregates the identifying, descriptive, and threshold attributes of constraint sets into a single queryable surface. The view is primarily read-only from the perspective of downstream consumers; it is intended for extraction and analysis rather than transactional manipulation.

Underlying Base Objects

The view is defined over base tables within the PSB schema family. The documented dependency identifies PSB_ENTITY_SET as a referenced object, which supplies the entity-set linkage used to scope which entities a constraint set applies to. No further base objects are documented in the ETRM metadata for this release, and the view is not referenced by any other database object—it sits at the top of the dependency chain as a leaf. Consequently, changes to PSB_ENTITY_SET or the underlying constraint definition tables propagate directly to the view, and the view should be treated as a read-only projection of that data. The view is not exposed through any documented public API or concurrency program; it is a repository object for analytical access.

Key Columns

  • CONSTRAINT_SET_ID (NUMBER(15)) — The unique, system-generated identifier for the constraint set. This is the primary key-like column and the value most frequently used in joins and lookups; the user's search for "constraint_set_id" corresponds directly to this attribute.
  • CONSTRAINT_SET_NAME (VARCHAR2(80)) — The user-facing name of the constraint set.
  • DESCRIPTION (VARCHAR2(240)) — Free-text description of the constraint set's purpose.
  • CONSTRAINT_THRESHOLD (NUMBER) — The severity threshold for the set. Any constraint assigned to the set whose severity exceeds this threshold raises a fatal error during planning.
  • LAST_UPDATE_DATE, LAST_UPDATED_BY, CREATION_DATE, CREATED_BY — Standard Who columns that provide audit lineage for the record.

Common Use Cases and Queries

Typical usage centers on auditing which constraint sets exist, their threshold settings, and their audit history. Analytical queries frequently filter on CONSTRAINT_THRESHOLD to isolate sets that will cause hard planning failures. A representative query is:

SELECT constraint_set_id,
       constraint_set_name,
       description,
       constraint_threshold,
       last_update_date
  FROM apps.psbbv_constraint_sets
 WHERE constraint_threshold > 0
 ORDER BY constraint_set_name;

A second common pattern joins the view to PSB_ENTITY_SET to determine the entities scoped by each set, using CONSTRAINT_SET_ID as the join key. Because the view carries no mandatory columns at the database level, application logic should always treat ID and name as populated by convention rather than constraint. All queries should be issued against APPS.PSBBV_CONSTRAINT_SETS directly, as the view encapsulates the schema details and shields callers from potential changes to the underlying PSB base tables.