Search Results igs_ps_usec_rpt_cond




Overview

IGS_PS_USEC_RPT_COND is a table in the IGS (Student System) schema of Oracle E-Business Suite, documented as VALID in both release 12.1.1 and 12.2.2. It models the repeat conditions attached to a unit section offering option — that is, the rules that govern whether a student may repeat a unit of study, how many times, and under what constraints. The table is part of the academic structure and enrollment configuration layer of Oracle Student System, sitting downstream of the unit offering option definition and feeding enrollment, progression, and funding evaluation logic.

The ETRM metadata classifies this object heuristically as satellite-leaning within a Data Vault modeling suggestion. This is consistent with its physical shape: the table carries a single foreign key to the parent unit offering option and holds a set of descriptive, mostly flag- and threshold-based attributes, rather than acting as a hub of business keys or a link resolving many-to-many relationships. The child relationship to IGS_PS_UNIT_OFR_OPT_ALL is a classic parent-to-satellite dependency, and the business-key uniqueness on UOO_ID reinforces that a unit offering option carries one governing repeat-condition record.

Key Information Stored

The table is documented with 14 columns. The most significant are:

The distinction between the surrogate key and the UOO_ID business key is important: integrations should treat UOO_ID as the stable business identifier and the surrogate as internal only.

Common Use Cases and Queries

Typical scenarios include validating whether a re-enrollment of a student into a unit section complies with institutional repeat policy, reporting on units with unlimited or high repeat allowances, and reconciling funding-eligible repeats against funded enrollment records. Because the table is keyed to the unit offering option, the most common query pattern joins upward to the offering option hierarchy.

A representative query retrieves all repeat conditions for a given offering option:

  • SELECT r.UNIT_SECTION_REPT_CONDITION_ID, r.UOO_ID, r.REPEATABLE_IND, r.MAX_REPEATS_FOR_CREDIT, r.MAX_REPEATS_FOR_FUNDING FROM IGS.IGS_PS_USEC_RPT_COND r WHERE r.UOO_ID = :uoo_id;
  • SELECT r.UOO_ID, r.SAME_TEACHING_PERIOD, r.SAME_TEACH_PERIOD_REPEATS, r.MAX_REPEAT_CREDIT_POINTS FROM IGS.IGS_PS_USEC_RPT_COND r WHERE r.REPEATABLE_IND = 'Y';

Reports that expose repeat policy by unit, teaching period, or funding category typically drive the join from IGS_PS_UNIT_OFR_OPT_ALL to this table on UOO_ID. Audit-oriented extracts filter on LAST_UPDATE_DATE to capture configuration changes over time.

Related Objects

The following objects are the most significant to consider when querying or extending this table:

  • IGS_PS_UNIT_OFR_OPT_ALL — the parent table, joined on UOO_ID = IGS_PS_UNIT_OFR_OPT_ALL.UOO_ID. This is the only documented foreign key relationship and is the mandatory join path.
  • IGS_PS_USEC_RPT_COND_PK — the primary key constraint/index on UNIT_SECTION_REPT_CONDITION_ID.
  • IGS_PS_USEC_RPT_COND_U1 — the unique index on UNIT_SECTION_REPT_CONDITION_ID.
  • IGS_PS_USEC_RPT_COND_U2 — the unique index on UOO_ID that enforces the business key.
  • Downstream enrollment and progression objects that consume repeat policy at enrollment time, including student unit attempt and enrollment configuration entities in the IGS schema.

The seed documentation referenced in the metadata (PS201_Enhancments_Nov03_PS_3045069_CS_DP2.doc) is marked obsolete, so current behavior should be validated against the live 12.1.1 or 12.2.2 dictionary rather than the historical design document.