Results for “igs_as_gpc_unit_sets”

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

Overview

The IGS_AS_GPC_UNIT_SETS table belongs to the IGS (Student System) product family within Oracle E-Business Suite, and is documented as obsolete in both the 12.1.1 and 12.2.2 releases. Its purpose is to store grading period cohort unit set details, effectively linking grading periods to the unit sets that apply to a cohort. The table is part of the academic scheduling and grading infrastructure historically used by institutions running the Oracle Student System.

From a Data Vault modeling perspective, the FK structure mined from the metadata suggests this object is satellite-leaning. It carries descriptive attributes tied to a business key, rather than acting as a pure hub or a pure link. This classification is offered as a heuristic modeling suggestion rather than an authoritative designation. The table is noted as not implemented in the reference database, which is consistent with its obsolete status.

Key Information Stored

The table is owned by IGS and contains nine documented columns. The most important of these are:

• GPC_UNIT_SET_ID — surrogate primary key, enforced by IGS_AS_GPC_UNIT_SETS_PK and also covered by unique index IGS_AS_GPC_UNIT_SETS_U1.
• GRADING_PERIOD_CD — code identifying the grading period to which the unit set applies.
• UNIT_SET_CD — code identifying the unit set being associated with the grading period.
• UNIT_SET_VERSION_NUMBER — version number of the unit set, allowing multiple versions to coexist.
• CREATED_BY, CREATION_DATE — audit columns capturing who created the row and when.
• LAST_UPDATED_BY, LAST_UPDATE_DATE, LAST_UPDATE_LOGIN — audit columns capturing the most recent modification and the login context of that change.

The business-key candidate is captured by unique index IGS_AS_GPC_UNIT_SETS_U2, defined over the combination of GRADING_PERIOD_CD, UNIT_SET_CD, and UNIT_SET_VERSION_NUMBER (also referenced as the unique key IGS_AS_GPC_UNIT_SETS_UK). This confirms that the natural identity of a record is the grading period plus the specific unit set version, while GPC_UNIT_SET_ID serves only as the technical surrogate.

Common Use Cases and Queries

Because the table is obsolete, practical use cases are largely historical, migration-oriented, or analytical. Typical scenarios include reconstructing which unit sets were attached to particular grading periods for a cohort, validating data before migrating to a current student system, and auditing legacy grading configurations.

A representative query joining the table to its parent unit set definition would resemble:

• SELECT g.GRADING_PERIOD_CD, g.UNIT_SET_CD, g.UNIT_SET_VERSION_NUMBER, u.UNIT_SET_DESCRIPTION FROM IGS_AS_GPC_UNIT_SETS g, IGS_EN_UNIT_SET_ALL u WHERE g.UNIT_SET_CD = u.UNIT_SET_CD AND g.UNIT_SET_VERSION_NUMBER = u.UNIT_SET_VERSION_NUMBER;
• Filtering a single grading period: ... WHERE g.GRADING_PERIOD_CD = :grading_period_cd.
• Identifying duplicated or orphaned unit set references during data cleanup or reconciliation.

Reporting use cases focus on historical grading period coverage, version comparisons across unit sets, and dependency mapping prior to decommissioning the module.

Related Objects

The metadata documents a foreign key from this table to the unit set master. The significant related objects are:

• IGS_EN_UNIT_SET_ALL — referenced via UNIT_SET_CD and UNIT_SET_VERSION_NUMBER; the parent definition of each unit set version.
• IGS_AS_GPC_UNIT_SETS_PK — primary key constraint on GPC_UNIT_SET_ID.
• IGS_AS_GPC_UNIT_SETS_UK / _U2 — unique constraint enforcing the grading period plus unit set version business key.
• IGS_AS_GPC_UNIT_SETS_U1 — unique index on GPC_UNIT_SET_ID.

Because the module is obsolete and the table is not implemented in current databases, no further dependent views or APIs are documented in the supplied metadata. Any integration work should treat IGS_AS_GPC_UNIT_SETS and its relatives as legacy reference data only.