Results for “igs_he_ucas_imp_err”

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

Overview

The IGS_HE_UCAS_IMP_ERR table is a Student System (IGS) object in Oracle E-Business Suite, owned by the IGS schema and marked VALID in both release 12.1.1 and 12.2.2. Its documented purpose is to store the errors encountered during import of HESA student details to OSS (the Oracle Student System). HESA (Higher Education Statistics Agency) returns and UCAS admissions data are loaded into the Student System through interface and staging routines; when a record fails validation or transformation during that load, the exception is written to this table rather than aborting the entire batch. The table therefore functions as an operational error log for the higher-education import pipeline.

The ETRM metadata classifies this object heuristically as standalone under the Data Vault model, with no documented foreign-key relationships to other tables. As a modeling suggestion, the standalone classification implies the table is best treated as an independent error/audit record set rather than as a hub, link, or satellite within a Data Vault. This is consistent with an error-logging table, whose rows are addressed by their own surrogate key and whose links to parent import batches are maintained implicitly through value columns rather than enforced referential constraints. Because the physical schema in 12.1.1 documents 10 columns and a single-column primary key, the object is narrow and purpose-built.

Key Information Stored

The table's documented physical schema in release 12.1.1 comprises 10 columns:

• ERROR_INTERFACE_ID — the surrogate primary key, enforced by the IGS_HE_UCAS_IMP_ERR_PK unique index. This single column is both the table's primary key and its only documented business-key candidate in the unique-index list.
• BATCH_ID — identifies the import batch or run that produced the error, allowing all failures from one load to be grouped and reviewed together.
• INTERFACE_HESA_ID — the identifier of the individual HESA interface record that failed, linking the error back to the specific student detail being imported.
• ERROR_CODE — coded classification of the failure, suitable for filtering, counting, and summarization in reports.
• ERROR_TEXT — descriptive message explaining the failure, typically the message surfaced to the user or written to the log.
• CREATED_BY, CREATION_DATE — standard Oracle EBS WHO columns recording the user and timestamp when the error row was inserted.
• LAST_UPDATED_BY, LAST_UPDATE_DATE, LAST_UPDATE_LOGIN — standard audit columns recording the last modification context.

Notably absent are descriptive student attributes such as names or identifiers; the table carries only keys, codes, text, and audit columns, keeping the error log compact and referential in nature.

Common Use Cases and Queries

Typical use cases center on diagnosing and reporting on failed HESA/UCAS imports into OSS.

• List all errors for a given batch: SELECT error_interface_id, interface_hesa_id, error_code, error_text FROM igs.igs_he_ucas_imp_err WHERE batch_id = :p_batch_id ORDER BY error_interface_id;
• Frequency analysis of failure reasons: SELECT error_code, COUNT(*) FROM igs.igs_he_ucas_imp_err GROUP BY error_code ORDER BY 2 DESC;
• Trend by load date: SELECT TRUNC(creation_date), COUNT(*) FROM igs.igs_he_ucas_imp_err GROUP BY TRUNC(creation_date) ORDER BY 1;
• Audit of who loaded the failing records: SELECT created_by, COUNT(*) FROM igs.igs_he_ucas_imp_err GROUP BY created_by;
• Join to the parent import/interface record on the interface key to retrieve the source student detail, and to the batch to retrieve run-level context.

Related Objects

The metadata documents no foreign keys for IGS_HE_UCAS_IMP_ERR, and no relationship data beyond the standalone classification. The most significant associated objects are therefore inferred from the value columns and the IGS import architecture:

• IGS_HE_UCAS_IMP — the primary HESA/UCAS import/staging table, joined on INTERFACE_HESA_ID.
• HESA/UCAS batch control tables in the IGS schema — joined on BATCH_ID.
• IGS_HE_UCAS_IMP_ERR_PK — the unique index on ERROR_INTERFACE_ID.
• OSS interface concurrent programs — the loaders that populate this table on failure.
• Standard EBS WHO columns and generic interface-error reporting views that reference IGS error logs for consolidated exception reporting.