Results for “igs_as_gpc_programs”

44 results




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

Overview

The IGS_AS_GPC_PROGRAMS table belongs to the Oracle EBS Student System (IGS) product family, historically used by higher-education institutions to manage academic records. Within the ETRM documentation it is classified as an Obsolete object under the IGS module and is explicitly noted as Not implemented in this database for the 12.1.1 baseline, meaning it exists in the physical schema for legacy or partial installations but is not active in all environments. Functionally, the table stores grading period cohort programme details, associating a grading period with a specific course and course version.

From a Data Vault modeling perspective, the metadata classifies this table as satellite-leaning. This heuristic suggests the object behaves primarily as a descriptive satellite attached to one or more parent hubs or links — most notably the course/version hub relationship that resolves through IGS_PS_VER_ALL. The surrogate key GPC_PROGRAM_ID anchors the row, while the business attributes describe cohort-to-grading-period combinations.

Key Information Stored

The table exposes nine documented columns. The most significant are summarised below:

  • GPC_PROGRAM_ID — the surrogate primary key defined by IGS_AS_GPC_PROGRAMS_PK and mirrored in unique index IGS_AS_GPC_PROGRAMS_U1. It uniquely identifies each grading period cohort programme record.
  • GRADING_PERIOD_CD — the grading period code that groups assessments, results, and cohorts within an academic cycle. Part of the business-key candidate.
  • COURSE_CD — the course code identifying which academic course the cohort programme pertains to. Also part of the business-key candidate and a foreign key column.
  • COURSE_VERSION_NUMBER — the specific version of the course, allowing multiple revisions of the same course to coexist. Completes the business-key candidate and the composite foreign key.
  • CREATED_BY, CREATION_DATE, LAST_UPDATED_BY, LAST_UPDATE_DATE, LAST_UPDATE_LOGIN — standard Oracle EBS WHO audit columns tracking row creation and modification.

The unique index IGS_AS_GPC_PROGRAMS_U2 on (GRADING_PERIOD_CD, COURSE_CD, COURSE_VERSION_NUMBER) is the practical business key, ensuring no duplicate cohort programme exists for a given grading period and course version.

Common Use Cases and Queries

Typical usages revolve around academic reporting, cohort definition, and grading configuration. Analysts commonly join this table to IGS_PS_VER_ALL to resolve course descriptors, producing reports of which cohorts are tied to which grading periods and versions.

A representative query pattern is:

  • List all cohort programmes for a grading period: SELECT gpc_program_id, course_cd, course_version_number FROM igs_as_gpc_programs WHERE grading_period_cd = :p_period;
  • Join to course version details: SELECT g.*, v.course_title FROM igs_as_gpc_programs g, igs_ps_ver_all v WHERE g.course_cd = v.course_cd AND g.course_version_number = v.course_version_number;
  • Audit recent changes using the WHO columns: SELECT * FROM igs_as_gpc_programs WHERE last_update_date > SYSDATE - 7;

Given the obsolete classification, the table is more relevant for historical data migrations, data vault modelling exercises, and legacy reporting than for new transactional development.

Related Objects

The ETRM metadata identifies the following key relationships:

  • IGS_PS_VER_ALL — referenced via the composite foreign key on COURSE_CD and COURSE_VERSION_NUMBER; the primary parent providing course version context.
  • IGS_AS_GPC_PROGRAMS_PK / _U1 / _U2 — the primary and unique indexes enforcing row identity and business-key integrity.

In broader IGS deployments, grading period cohort data links logically with grading period definitions, assessment cohorts, and student result tables. Downstream views and reports in the Student System that enumerate cohort grading configurations typically depend on this table as a source. Where implementations migrate to newer releases, the equivalent functionality is generally superseded by successor structures, reinforcing the obsolete status recorded in ETRM.