Search Results igs_gr_lgcy_grd_int




Overview
Explore in AI Chat

Overview

IGS_GR_LGCY_GRD_INT is a staging interface table within the IGS (Student System) product schema of Oracle E-Business Suite, available in both 12.1.1 and 12.2.2. Its documented purpose is to store Graduation Legacy data, meaning it acts as a landing zone for historical or externally sourced graduation records that must be validated, transformed, and ultimately loaded into the operational graduation tables of the Student System. It is implemented as a physical table owned by the IGS schema with 53 documented columns.

The physical record is qualified as IGS.IGS_GR_LGCY_GRD_INT with primary key constraint IGS_GR_LGCY_GRD_INT_PK on the single column LEGACY_GR_INT_ID. From a Data Vault modeling perspective, the documented FK structure classifies this object as standalone, which suggests it is best modeled as an independent hub-like staging entity anchored on its own surrogate key, rather than as a link or satellite dependent on another parent. This classification is heuristic and mined from the FK structure, so it should be treated as a modeling suggestion rather than a hard constraint.

Key Information Stored

The table carries a surrogate primary key, LEGACY_GR_INT_ID, which uniquely identifies each interface row. The unique index IGS_GR_LGCY_GRD_INT_PK documents this column as the only business-key candidate. Beyond the key, the most significant columns fall into several groups:

Common Use Cases and Queries

The primary use case is bulk ingestion of legacy graduation records. Data is populated by an external loader or SQL*Loader process, IMPORT_STATUS is monitored, and validated rows are moved into the live graduation tables. A typical monitoring query selects unprocessed rows:

  • SELECT LEGACY_GR_INT_ID, PERSON_NUMBER, PROGRAM_CD, AWARD_CD, IMPORT_STATUS FROM IGS.IGS_GR_LGCY_GRD_INT WHERE IMPORT_STATUS = 'NEW';
  • SELECT BATCH_ID, COUNT(*) FROM IGS.IGS_GR_LGCY_GRD_INT GROUP BY BATCH_ID ORDER BY 1;
  • SELECT COUNT(*) FROM IGS.IGS_GR_LGCY_GRD_INT WHERE REQUEST_ID = :request_id;

Reconciliation reports match the interface count against the target graduation table, and error analysis queries filter by IMPORT_STATUS and the ATTRIBUTE columns used to carry loader diagnostics. Because the table records REQUEST_ID and PROGRAM_ID, concurrent program submissions can be traced and audited directly from the data.

Related Objects

Because the metadata classifies this object as standalone, no foreign key dependencies are documented. The principal relationships are therefore logical rather than enforced:

  • IGS_GR_GRADUANDS / graduation result tables — receive transformed rows keyed on PERSON_NUMBER, PROGRAM_CD, and AWARD_CD.
  • Import and validation concurrent programs — reference this table through REQUEST_ID and PROGRAM_ID.
  • Person and program reference data — PERSON_NUMBER, PROGRAM_CD, and AWARD_CD resolve against the relevant student and program tables during validation.
  • IGS_GR_LGCY_GRD_INT_PK — the unique index enforcing uniqueness of LEGACY_GR_INT_ID.
  • OA/IMPORT_STATUS lookup — governs the processing state transitions applied to each row.

Administrators should treat this table as transient staging data and purge or archive rows after successful transfer and reconciliation.