Search Results std_ft_completion_time




Overview

The view IGS_PS_VER_HIST belongs to the Oracle E-Business Suite Student System (IGS) product family. It is a historical versioning view that exposes course version records together with their history tracking columns, allowing course catalogue changes to be audited over time. Within the ETRM metadata for Oracle EBS 12.1.1 and 12.2.2, this object is classified as part of the IGS - Student System (Obsolete) module. The designation "Obsolete" indicates that the object is retained for backward compatibility or for reference purposes but is not part of the strategic, supported data model. As documented, the object is identified as a view rather than a base table, and the implementation/DBA metadata explicitly states: "Not implemented in this database." Consequently, in environments where the view has not been deployed, queries against it will fail unless the underlying base objects are present.

Underlying Base Objects

The ETRM metadata lists no formally documented referenced base objects for IGS_PS_VER_HIST, so the definitive dependency chain must be inferred from the view definition. The view text selects columns qualified by the alias TAB, indicating that it is defined over a single underlying table or inline view that carries the base course-version attributes. The view exposes its own ROWID as ROW_ID via TAB.ROWID, a common pattern in Oracle EBS historical views where the row identity of the source record is preserved. Because no base objects are documented in ETRM, DBAs and developers should validate the actual dependency using ALL_DEPENDENCIES and ALL_VIEWS in the target instance before relying on the view for reporting or integration. Where the view is not implemented, the historical information it would present is typically available directly from the underlying course version table in the IGS schema.

Key Columns

The view returns a comprehensive set of course version attributes. History-specific columns include HIST_START_DT, HIST_END_DT, and HIST_WHO, which record the effective period and the actor responsible for each historical version. Core identity columns are COURSE_CD, VERSION_NUMBER, COURSE_STATUS, TITLE, SHORT_TITLE, and ABBREVIATION. Academic and administrative attributes include START_DT, REVIEW_DT, EXPIRY_DT, END_DT, COURSE_TYPE, RESPONSIBLE_ORG_UNIT_CD, RESPONSIBLE_OU_START_DT, OU_DESCRIPTION, GOVT_SPECIAL_COURSE_TYPE, and GSCT_DESCRIPTION. Flags and controls include SUPP_EXAM_PERMITTED_IND, GENERIC_COURSE_IND, GRADUATE_STUDENTS_IND, COUNT_INTRMSN_IN_TIME_IND, and INTRMSN_ALLOWED_IND. Quantitative fields include CONTACT_HOURS, CREDIT_POINTS_REQUIRED, GOVT_COURSE_LOAD, STD_ANNUAL_LOAD, ANNUAL_INSTRUCTION_TIME, COURSE_TOTAL_EFTSU, STD_FT_COMPLETION_TIME, STD_PT_COMPLETION_TIME, and MAX_INTRMSN_DURATION. Additional controls cover admission limits, submission percentages, and financial aid indicators.

Common Use Cases and Queries

Typical usage centers on course catalogue auditing and point-in-time reporting. A common pattern retrieves the current and prior version of a course:

  • Audit trail: SELECT COURSE_CD, VERSION_NUMBER, HIST_START_DT, HIST_WHO, COURSE_STATUS FROM IGS_PS_VER_HIST WHERE COURSE_CD = :course ORDER BY HIST_START_DT DESC;
  • Effective-dated slice: SELECT COURSE_CD, VERSION_NUMBER, TITLE FROM IGS_PS_VER_HIST WHERE SYSDATE BETWEEN HIST_START_DT AND NVL(HIST_END_DT, SYSDATE);
  • Change comparison joining the view to itself on COURSE_CD and comparing VERSION_NUMBER values to detect attribute drift.

Because the object is documented as not implemented and belongs to an obsolete module, these queries should be validated against the actual schema. Where the view is unavailable, equivalent history can be extracted from the IGS course version base table using its date-effective columns.