Results for “igs_pr_cs_schdl”

42 results




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

Overview

IGS_PR_CS_SCHDL is a table within the Oracle E-Business Suite IGS (Student System) product family, documented as obsolete in ETRM 12.1.1 / 12.2.2. Its ETRM description states that it "Maintains the schedule of Class Standing," indicating that the table stores the effective-dated rules that determine how a student's class standing (for example, freshman, sophomore, junior, senior, or equivalent progression classifications) is assigned over time. In the Oracle EBS higher-education data model, such schedule tables act as the configuration backbone for progression and academic-standing calculations, linking a course type to a validity window during which the standing rules apply.

The ETRM metadata offers a heuristic Data Vault classification of "hub-leaning," mined from the foreign-key structure. Taken as a modeling suggestion rather than a normative statement, this implies the table behaves primarily as a durable key-bearing entity centered on a single surrogate identifier, with downstream references fanning out to dependent detail tables. The schedule's business keys are captured through unique indexes rather than being embedded in the primary key, reinforcing the hub-like character of the identifier column.

Key Information Stored

The documented physical schema comprises ten columns owned by the IGS schema. The most important are:

The distinction between the surrogate key (IGS_PR_CS_SCHDL_ID) and the business-key candidates (IGS_PR_CS_SCHDL_U1 on the surrogate itself, and IGS_PR_CS_SCHDL_U2 on START_DT plus COURSE_TYPE) is significant: integrations that resolve a schedule by natural key must query on the date and course-type pair rather than assuming the ID.

Common Use Cases and Queries

Typical reporting use cases include identifying the active class-standing schedule for a given course type on a given date, auditing the history of schedule changes, and validating overlaps or gaps in effective dating. A sample pattern follows:

  • Resolve the schedule in effect: SELECT igs_pr_cs_schdl_id, start_dt, end_dt FROM igs_pr_cs_schdl WHERE course_type = :course_type AND TRUNC(SYSDATE) BETWEEN start_dt AND NVL(end_dt, TRUNC(SYSDATE)+1);
  • Detect overlapping windows per course type by self-joining on COURSE_TYPE where START_DT of one row falls between the START_DT and END_DT of another.
  • Trace downstream usage by joining to IGS_PR_CSS_CLASS_STD on IGS_PR_CS_SCHDL_ID to see the standing values generated under each schedule.
  • Audit recently modified schedules using LAST_UPDATE_DATE and LAST_UPDATED_BY.

Because the table is flagged as obsolete and "not implemented in this database" in the ETRM excerpt, these queries should be treated as reference patterns; production environments on 12.1.1 or 12.2.2 may not contain the object.

Related Objects

  • IGS_PS_TYPE_ALL — referenced by IGS_PR_CS_SCHDL.COURSE_TYPE; the parent definition of course types used in the schedule.
  • IGF_AP_PR_PRG_TYPE — holds a foreign key column IGS_PR_CS_SCHDL_ID that references this table, linking the schedule to program-type progression configuration.
  • IGS_PR_CSS_CLASS_STD — the class-standing detail table referencing IGS_PR_CS_SCHDL.IGS_PR_CS_SCHDL_ID, capturing the standing values derived under each schedule.
  • IGS_PR_CS_SCHDL_PK / IGS_PR_CS_SCHDL_U1 / IGS_PR_CS_SCHDL_U2 — the primary key and unique indexes that enforce identity and business-key integrity.