Results for “sub_us_version_number”

12 results




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

Overview

IGS_PS_OF_UNT_SET_RL is a relationship table within the Oracle E-Business Suite Student System (IGS) product. It defines and constrains the permissible structural relationships between two unit sets associated with a program offering. In Oracle Student System terminology, a unit set represents a grouping of units (courses) that a student must complete, and multiple unit sets can be nested, for example a parent or "superior" set that contains subordinate or "subordinate" sets. IGS_PS_OF_UNT_SET_RL records which superior-to-subordinate unit set pairings are valid within a specific program version, thereby governing and restricting the parent/child relationships among the unit sets that a student may select. Without an entry in this table, no parent/child linkage is permitted between the two unit sets.

The table is owned by the IGS schema and is reported as VALID in the documented environment. Based on the heuristic Data Vault classification mined from its foreign key structure, this object is best modeled as a link table. It resolves a many-to-many relationship between parent and child unit set definitions rather than storing descriptive attributes, which is characteristic of link entities in a Data Vault model.

Key Information Stored

Although the physical schema documents twelve columns, the following are the most significant for understanding and querying the table:

The primary key, IGS_PS_OF_UNT_SET_RL_PK, is defined over all seven business columns (COURSE_CD, CRV_VERSION_NUMBER, CAL_TYPE, SUP_UNIT_SET_CD, SUP_US_VERSION_NUMBER, SUB_UNIT_SET_CD, SUB_US_VERSION_NUMBER). A unique index IGS_PS_OF_UNT_SET_RL_U1 covers the same column set, confirming that this composite of program, calendar, and both unit set identifiers plus their versions constitutes the business-key candidate uniquely identifying each permissible pairing.

Common Use Cases and Queries

Typical uses include validating whether a proposed parent/child unit set combination is permitted, reporting the hierarchy of unit sets within a program version, and driving eligibility checks during student unit set selection.

A query to retrieve all subordinate unit sets of a given superior unit set:

  • SELECT SUB_UNIT_SET_CD, SUB_US_VERSION_NUMBER FROM IGS_PS_OF_UNT_SET_RL WHERE COURSE_CD = :course AND CRV_VERSION_NUMBER = :ver AND CAL_TYPE = :cal AND SUP_UNIT_SET_CD = :sup AND SUP_US_VERSION_NUMBER = :sup_ver;

A validation query confirming a specific parent/child pairing exists:

  • SELECT COUNT(*) FROM IGS_PS_OF_UNT_SET_RL WHERE COURSE_CD = :course AND CRV_VERSION_NUMBER = :ver AND CAL_TYPE = :cal AND SUP_UNIT_SET_CD = :sup AND SUB_UNIT_SET_CD = :sub;

Reporting use cases include generating a full relationship matrix per program version and auditing orphaned or misconfigured unit set hierarchies.

Related Objects

The table carries foreign keys to the unit set offering definitions, meaning its integrity depends on the following:

  • IGS_PS_OFR_UNIT_SET — Referenced twice: once via (COURSE_CD, CRV_VERSION_NUMBER, CAL_TYPE, SUP_UNIT_SET_CD, SUP_US_VERSION_NUMBER) for the superior unit set, and once via (COURSE_CD, CRV_VERSION_NUMBER, CAL_TYPE, SUB_UNIT_SET_CD, SUB_US_VERSION_NUMBER) for the subordinate unit set.
  • IGS_PS_OF_UNT_SET_RL_PK / IGS_PS_OF_UNT_SET_RL_U1 — The primary key and unique index enforcing uniqueness of each superior/subordinate pairing.

Because both foreign keys resolve to the same parent table, IGS_PS_OFR_UNIT_SET must be joined twice (typically with aliases for superior and subordinate) in reporting queries that resolve unit set names and descriptions. Applications selecting unit sets for a student consult this table to enforce the permitted hierarchy.