Search Results igs_he_batch_int_pk

Overview

The IGS_HE_BATCH_INT table is a legacy Student System (IGS) object that stores batch definitions for the HESA (Higher Education Statistics Agency) import student details process. HESA is the statutory body responsible for collecting student data from UK higher education institutions, and the IGS_HE_BATCH_INT table was used to define and track the control-level batches through which student detail records were staged and subsequently imported into the Oracle Student System (OSS). Each row represents a logical batch processed by the HESA import routine, providing the descriptive context against which incoming student records could be grouped and validated.

The object belongs to the IGS — Student System (Obsolete) product line. As the product designation indicates, the IGS Student System is no longer supported in Oracle EBS 12.1.1 or 12.2.2, and the ETRM documentation explicitly notes that this table is not implemented in the current database. It therefore persists only as a historical catalog artifact for reference by institutions that migrated off the legacy student system.

From a Data Vault modeling perspective, the metadata classifies this object heuristically as standalone. Based on the mined FK structure, no parent or subordinate relationships are present, which suggests it should be modeled as a hub containing the batch business concept, with the descriptive attribute carried as a satellite. Because no foreign keys were detected, no link table is warranted in the vault model.

Key Information Stored

The documented physical schema for this table in ETRM 12.1.1 is intentionally minimal — only two columns are recorded. The two columns documented are:

• BATCH_ID — The surrogate primary key and sole column in the unique index IGS_HE_BATCH_INT_PK. This identifier uniquely distinguishes each batch definition and serves both as the technical row identifier and the business-key candidate in this degenerate two-column design.
• DESCRIPTION — A free-text label describing the batch, used to identify the batch purpose (for example, a term, year, or HESA return cycle) during the import process.

Because no additional columns are documented, the table should be understood as a lightweight lookup rather than a wide transactional entity. The primary key IGS_HE_BATCH_INT_PK on BATCH_ID is the only unique index (business-key candidate) recorded, confirming that the batch identifier is the single referential anchor for the object.

Common Use Cases and Queries

In the legacy Student System, this table was typically referenced when diagnosing how a given HESA import run was scoped. Even though the table is obsolete, historical reporting and audit queries may still be required where archival exports exist. Typical patterns include:

• Batch enumeration — listing all defined batches with their descriptions for a given institution:
  SELECT batch_id, description FROM igs_he_batch_int ORDER BY batch_id;
• Batch lookup by identifier — resolving a batch referenced in a downstream interface error log:
  SELECT description FROM igs_he_batch_int WHERE batch_id = :p_batch_id;
• Reconciliation reporting — joining batch definitions to staging tables to verify completeness of imported student details by batch.

Because the table is documented as standalone with no FK relationships, joins must be inferred from application logic rather than enforced referential constraints. Any query written against this object should be treated as read-only and confined to archival or migration-validation contexts.

Related Objects

The metadata records no foreign-key relationships for IGS_HE_BATCH_INT, reinforcing the standalone Data Vault classification. Consequently, the following related objects are the ones most commonly associated with the HESA import process by convention rather than by documented constraint:

• IGS_HE_BATCH_INT_PK — the unique index enforcing the primary key on BATCH_ID.
• HESA student-detail staging tables (e.g., IGS_HE_STUDENT_INT and its sibling interface tables) — populated and grouped by BATCH_ID.
• The HESA import concurrent program definition in the IGS module, which consumes the batch definitions.
• IGS interface error and log tables that record batch-level validation outcomes.
• Institutions' archival extracts of the IGS student tables used for migration to supported products.

Given the obsoleted status, integrators should confirm physical presence before relying on this object in any 12.1.1 or 12.2.2 environment.