Search Results igs_ps_rsv_usec_pri




Overview
Explore in AI Chat

Overview

IGS_PS_RSV_USEC_PRI is a transactional configuration table within the Oracle E-Business Suite Student System (IGS) product family. It resides in the IGS schema and holds VALID status in Oracle EBS releases 12.1.1 and 12.2.2. Functionally, the table describes the priority definitions applied to reserved seating at the unit Section level. Reserved seating allows an institution to ring-fence a portion of a course section's capacity for a defined cohort — for example, a specific program, plan, or student group — and the priority rows defined here establish the ranking or ordering rules that govern how those reserved seats are allocated when demand exceeds supply.

The object operates as a child of the unit offering option structure and as a parent to the reserved seat usage profile. In Data Vault terms, the heuristic classification derived from the foreign key topology is satellite-leaning: the table carries descriptive priority attributes that hang off a parent business key (UOO_ID) rather than forming an independent hub or a pure many-to-many link. This classification should be treated as a modeling suggestion rather than a mandated design.

Key Information Stored

The documented physical schema contains nine columns. The most significant are:

The distinction between the surrogate key (RSV_USEC_PRI_ID) and the composite business key (UOO_ID, PRIORITY_VALUE) is important: integration and data-migration logic should resolve rows by the business key, while internal joins and child references use the surrogate.

Common Use Cases and Queries

Typical usage centres on capacity planning, enrolment eligibility, and reserved-seat allocation reporting. A common pattern retrieves all priorities configured for a given unit offering option:

  • Joining IGS_PS_RSV_USEC_PRI to IGS_PS_UNIT_OFR_OPT_ALL on UOO_ID to report priority definitions alongside the section's offering attributes.
  • Joining to IGS_PS_RSV_USEC_PRF on RSV_USEC_PRI_ID to expand a priority into its associated usage profiles, which is the standard route for reserved-seating eligibility reports.
  • Ordering result sets by PRIORITY_ORDER or PRIORITY_VALUE to reproduce the institutional allocation sequence used during enrolment processing.
  • Auditing configuration drift by comparing PRIORITY_VALUE and PRIORITY_ORDER across terms, using LAST_UPDATE_DATE and LAST_UPDATED_BY to identify recent changes.

Extracts should filter on UOO_ID for a target section and drive the join downward into IGS_PS_RSV_USEC_PRF to obtain the actual reservation profile detail.

Related Objects

The following objects are the most significant dependencies:

  • IGS_PS_UNIT_OFR_OPT_ALL — Parent table; joined on IGS_PS_RSV_USEC_PRI.UOO_ID. Supplies the unit offering option context.
  • IGS_PS_RSV_USEC_PRF — Child table referencing IGS_PS_RSV_USEC_PRI.RSV_USEC_PRI_ID; holds the reserved seat usage profiles that consume these priority definitions.
  • IGS_PS_RSV_USEC_PRI_PK — Primary key constraint on RSV_USEC_PRI_ID.
  • IGS_PS_RSV_USEC_PRI_U1 — Unique index on RSV_USEC_PRI_ID.
  • IGS_PS_RSV_USEC_PRI_U2 — Unique index on UOO_ID and PRIORITY_VALUE, defining the composite business key.

Together these objects form the reserved-seating priority chain: unit offering option, priority definition, and usage profile. Query and integration design should preserve that hierarchy and respect the documented uniqueness constraints when inserting or updating configuration data.