Results for “igs_pr_s_prg_conf”

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

Overview

IGS_PR_S_PRG_CONF is a configuration table in the Oracle EBS Student System (IGS) product family. The metadata classifies the product as IGS - Student System (Obsolete), and the table itself is documented as "not implemented in this database" within the current ETRM 12.1.1 extract. Its stated purpose is to describe system progression configuration information: these records act as the default settings for progression processing unless overridden for particular organizational units or course versions.

In an institutional context, progression configuration governs how the system interprets progression rules — when applications open and close, how appeals and show-cause periods are handled, which time-based counting rules apply, and whether weighted averages or grade point averages are calculated. Because these settings are system-wide defaults, the table sits at the top of a configuration hierarchy that downstream organizational and course-version records can selectively override.

The ETRM relationship metadata provides a heuristic Data Vault classification of satellite-leaning. This is a modeling suggestion rather than a physical design statement: the table holds descriptive configuration attributes keyed by a single surrogate control number, with no documented hub-like business key of its own and no link structure implied by its foreign keys. The date-alias columns reference a shared reference table rather than establishing independent entities, which reinforces the satellite interpretation.

Key Information Stored

The documented physical schema contains 23 columns. The primary key is IGS_PR_S_PRG_CONF_PK, defined on the single column S_CONTROL_NUM. A unique index, IGS_PR_S_PRG_CONF_U1, also exists on S_CONTROL_NUM, making it the documented business-key candidate in addition to its role as the surrogate identifier.

Seven columns store date-alias references, each pointing to IGS_CA_DA: APPLY_START_DT_ALIAS, APPLY_END_DT_ALIAS, EFFECTIVE_END_DT_ALIAS, APPEAL_CUTOFF_DT_ALIAS, END_BENEFIT_DT_ALIAS, END_PENALTY_DT_ALIAS, and SHOW_CAUSE_CUTOFF_DT_ALIAS. These aliases bind progression milestones to named date types defined elsewhere in the calendar/date infrastructure. A further alias, ENCUMB_END_DT_ALIAS, is documented in the column list.

Indicator columns control behavioral switches: SHOW_CAUSE_IND, APPEAL_IND, APPLY_BEFORE_SHOW_IND, and APPLY_BEFORE_APPEAL_IND govern sequencing and whether show-cause or appeal processing is active. Counting behavior is controlled by COUNT_SUS_IN_TIME_IND and COUNT_EXC_IN_TIME_IND, which determine whether suspended or excluded time is included in elapsed-time calculations.

Calculation flags CALCULATE_WAM_IND and CALCULATE_GPA_IND determine whether a weighted average mark and grade point average are computed. OUTCOME_CHECK_TYPE defines the type of outcome validation applied. Standard audit columns — CREATED_BY, CREATION_DATE, LAST_UPDATED_BY, LAST_UPDATE_DATE, and LAST_UPDATE_LOGIN — complete the schema.

Common Use Cases and Queries

The primary use case is retrieving the active progression defaults for a student administration implementation, typically as a baseline before resolving organizational or course-version overrides.

• Baseline configuration review: SELECT * FROM igs_pr_s_prg_conf; — since the table is documented as not implemented in the reference database, verify existence with SELECT * FROM all_tables WHERE table_name = 'IGS_PR_S_PRG_CONF'; before relying on it.
• Calculation-rule reporting: SELECT s_control_num, calculate_wam_ind, calculate_gpa_ind, outcome_check_type FROM igs_pr_s_prg_conf;
• Date-alias resolution: join each alias column to IGS_CA_DA to translate stored aliases into concrete date definitions, for example SELECT c.s_control_num, d.date_alias, d.description FROM igs_pr_s_prg_conf c, igs_ca_da d WHERE c.apply_start_dt_alias = d.date_alias;
• Calendar linkage: SELECT cal.* FROM igs_pr_s_prg_cal cal, igs_pr_s_prg_conf conf WHERE cal.s_control_num = conf.s_control_num; to identify which progression calendars consume a given configuration.

Because the record is a singleton-style default set, reporting is typically limited to confirming which flags and aliases are active rather than aggregating across many rows.

Related Objects

• IGS_PR_S_PRG_CAL — references IGS_PR_S_PRG_CONF through S_CONTROL_NUM. This is the principal dependent object, linking progression calendars to their governing configuration.
• IGS_CA_DA — the referenced date-alias table, joined via APPEAL_CUTOFF_DT_ALIAS, END_BENEFIT_DT_ALIAS, SHOW_CAUSE_CUTOFF_DT_ALIAS, EFFECTIVE_END_DT_ALIAS, APPLY_END_DT_ALIAS, END_PENALTY_DT_ALIAS, and APPLY_START_DT_ALIAS.

The reference table IGS_CA_DA supplies the semantic meaning of every progression date milestone, while IGS_PR_S_PRG_CAL consumes the configuration when scheduling progression calendar activity. Together these three objects define the documented dependency chain around IGS_PR_S_PRG_CONF. Given the obsolete classification of the IGS Student System in current EBS releases, implementations should treat this object as legacy and confirm its presence in their specific environment before designing queries or extensions around it.