Results for “igs_pr_s_ou_prg_conf”

38 results




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

Overview

IGS_PR_S_OU_PRG_CONF is a configuration table in the Oracle EBS Student System (IGS) product, which is documented as obsolete in the ETRM reference for releases 12.1.1 and 12.2.2. The table stores system configuration parameters scoped to a specific organizational unit. Its defining behaviour is inheritance-by-exception: when a row exists for a given organizational unit, that row overrides the system-wide defaults for that unit only; in the absence of a row, the global defaults apply. It is therefore a parameter-resolution object consulted during progression and appeals processing rather than a transactional or enrollment-bearing table.

From a Data Vault modeling perspective, the metadata's heuristic classification is satellite-leaning. This is a reasonable suggestion: the key structure (organizational unit plus effective start date) is naturally descriptive and time-bounded, so the table behaves like a satellite attached to an organizational-unit hub rather than a hub or link in its own right. Analysts building a dimensional or Data Vault representation should treat the organizational unit as the parent entity and the configuration attributes as dependent descriptive payload.

Key Information Stored

The documented physical schema under owner IGS defines 22 columns. The primary key is IGS_PR_S_OU_PRG_CONF_PK, comprising ORG_UNIT_CD and OU_START_DT. A unique index, IGS_PR_S_OU_PRG_CONF_U1, is defined on the same two columns, making this pair the business-key candidate: one configuration version per organizational unit per effective start date.

Common Use Cases and Queries

Typical usage centres on resolving which configuration governs a progression decision for a student at a given point in time. A common pattern joins the student's organizational context to the most recent configuration row effective on or before the transaction date.

  • Effective configuration lookup: select ORG_UNIT_CD, OU_START_DT, and the indicator columns where ORG_UNIT_CD equals the target unit and OU_START_DT is the maximum value not exceeding the current date.
  • Override audit: compare unit-level rows against global defaults to identify organizational units that deviate on OUTCOME_CHECK_TYPE or the calculation indicators.
  • Date alias resolution: join the six alias columns to IGS_CA_DA to translate them into concrete calendar dates for cutoff and penalty reporting.
  • Calendar linkage: join to IGS_PR_S_OU_PRG_CAL on ORG_UNIT_CD and OU_START_DT to retrieve the associated progression calendar entries.
  • Configuration history: order by OU_START_DT to reconstruct how a unit's rules changed over time.

Related Objects

  • IGS_CA_DA — referenced six times via APPEAL_CUTOFF_DT_ALIAS, END_BENEFIT_DT_ALIAS, SHOW_CAUSE_CUTOFF_DT_ALIAS, APPLY_END_DT_ALIAS, END_PENALTY_DT_ALIAS, and APPLY_START_DT_ALIAS; supplies the date definitions behind each alias.
  • IGS_PR_S_OU_PRG_CAL — the only documented child table, referencing this table through ORG_UNIT_CD and OU_START_DT; holds the progression calendar detail for the configured unit and effective period.
  • IGS_PR_S_OU_PRG_CONF_PK and IGS_PR_S_OU_PRG_CONF_U1 — the primary key constraint and unique index enforcing uniqueness of the organizational unit and start date pair.

Because the product is marked obsolete, implementations on 12.1.1 or 12.2.2 should confirm whether the table is populated in their environment; the ETRM record notes it is not implemented in some databases, in which case global defaults alone govern behaviour.