Results for “ext_exception_id”

13 results




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

Overview

IGS_HE_EXT_RUN_EXCP is a logging and diagnostic table within the Oracle E-Business Suite IGS (Student System) module. Its documented purpose is to hold errors and exceptions encountered during HESA (Higher Education Statistics Agency) extract runs. HESA extracts are the periodic data submissions that UK higher-education institutions produce for statutory reporting, and any defect in the source data — an unresolvable person reference, a malformed course or unit identifier, or a missing version number — must be captured rather than silently dropped. This table serves that role: it is the exception ledger for a single extract run.

The ETRM metadata classifies IGS_HE_EXT_RUN_EXCP as satellite-leaning under a heuristic Data Vault model. In practical terms this is a defensible reading: the table's grain is one row per exception occurrence, its rows carry descriptive attributes rather than pure key relationships, and it is materially dependent on two upstream entities through foreign keys. It is not a hub or a link in the strict sense, because it introduces its own descriptive payload and a line-level location context.

The ETRM record notes that the table is "Not implemented in this database" in the sampled environment, and the IGS product is flagged Obsolete. Nonetheless, the object remains defined in the 12.1.1 physical schema with 16 columns, and the same definition persists through the 12.2.x code line for customers running legacy student systems. It should be treated as read-only reference data by integration and reporting teams.

Key Information Stored

The table is keyed by EXT_EXCEPTION_ID, which is both the primary key (IGS_HE_EXT_RUN_EXCP_PK) and the single documented business-key candidate exposed through the unique index IGS_HE_EXT_RUN_EXCP_U1. Because only one unique index is present and it is built on the same column as the primary key, there is no independent natural key in the schema; EXT_EXCEPTION_ID is a system-generated surrogate.

Common Use Cases and Queries

The principal use case is post-run triage: after a HESA extract completes, staff query the exception table to determine why records were rejected before resubmitting. A typical pattern joins exceptions back to the run and to the party:

SELECT e.EXT_EXCEPTION_ID, e.PERSON_NUMBER, e.COURSE_CD, e.CRV_VERSION_NUMBER,
       e.UNIT_CD, e.LINE_NUMBER, e.FIELD_NUMBER, e.EXCEPTION_REASON,
       p.PARTY_NAME
 FROM IGS_HE_EXT_RUN_EXCP e, IGS_HE_EXT_RUN_DTLS r, HZ_PARTIES p
 WHERE e.EXTRACT_RUN_ID = r.EXTRACT_RUN_ID
   AND e.PERSON_ID = p.PARTY_ID
   AND e.EXTRACT_RUN_ID = :run_id;

Aggregate reporting by EXCEPTION_REASON and by COURSE_CD identifies systemic data-quality problems — for example, a single course version generating a disproportionate share of exceptions — which is more useful to data owners than the individual rows. A LEFT JOIN from IGS_HE_EXT_RUN_DTLS to this table produces a run-quality scorecard showing which runs completed cleanly and which did not.

Because the table is not implemented in many environments and the product is obsolete, queries should be guarded by a data dictionary check against ALL_TAB_COLUMNS before being embedded in scheduled reports.

Related Objects

  • IGS_HE_EXT_RUN_DTLS — the parent extract run table, joined on EXTRACT_RUN_ID; supplies run-level context.
  • HZ_PARTIES — the Trading Community Architecture party table, joined on PERSON_ID = PARTY_ID for person detail.
  • IGS_HE_EXT_RUN_EXCP_PK — the primary key constraint on EXT_EXCEPTION_ID.
  • IGS_HE_EXT_RUN_EXCP_U1 — the unique index on EXT_EXCEPTION_ID.
  • HESA extract concurrent programs — the run-time processes that populate this table during execution.
  • IGS_HE_* sibling tables — related HESA extract objects following the same naming convention and run/exception pattern.