Search Results hz_person




Overview
Explore in AI Chat

Overview

IGS.IGS_HE_BATCH_INT is an Oracle E-Business Suite table owned by the IGS (Student System / Higher Education) product schema. Its display name, "Import HESA Student Data Batch," identifies its purpose: it stores the batch definitions used by the HESA (Higher Education Statistics Agency) import student details process. Each row represents a single batch run used to group and stage HESA student data during import.

The table is registered in FND Design Data as IGS.IGS_HE_BATCH_INT with a status of VALID, and resides in the APPS_TS_TX_DATA tablespace with a PCT Free of 10. Its lifecycle is active and its scope is public. It is classified under two business entity categories: IGS_STUDENT_PROGRAM and HZ_PERSON, the latter aligning with the "hz_person" search term because HESA student records ultimately resolve to Oracle Trading Community Architecture (TCA) person records.

From a Data Vault modeling perspective, the heuristic classification for this object is standalone, mined from its foreign-key structure. In practice this suggests the table behaves as an independent batch-control or reference entity with no outbound foreign keys to other hubs or links. The primary key, IGS_HE_BATCH_INT_PK on BATCH_ID, functions as a surrogate key that uniquely identifies each batch.

Key Information Stored

The documented physical schema is intentionally narrow, containing only two columns. Despite its small footprint, these columns carry the essential batch-identification information required to drive the HESA import process.

  • BATCH_ID (NUMBER, length 15, mandatory): the batch identifier. It is a sequence-generated number and serves as the surrogate primary key of the table, enforced by the unique index IGS_HE_BATCH_INT_PK in the APPS_TS_TX_IDX tablespace. Because it is the sole unique index, BATCH_ID is the only documented business-key candidate as well as the physical surrogate key.
  • DESCRIPTION (VARCHAR2, length 80): a batch description. This provides a human-readable label that lets users and reports identify the purpose, period, or scope of an individual batch, and is the principal descriptive attribute carried on the row.

The metadata documents no additional columns beyond these two. Readers should note that this object is a control or header table: the substantive HESA student detail records are held in associated detail tables that reference BATCH_ID, while this table supplies only the batch identity and label.

Common Use Cases and Queries

The table is most often queried to list existing batches, to resolve a batch identifier into a meaningful description for reporting, or to drive the HESA import process by selecting a target batch. The canonical query documented by ETRM is:

  • SELECT BATCH_ID, DESCRIPTION FROM IGS.IGS_HE_BATCH_INT;

Typical operational and reporting patterns include:

  • Retrieving a single batch by its surrogate key — WHERE BATCH_ID = :batch_id — to confirm the target of a HESA import run.
  • Filtering batches by description text using a LIKE predicate to locate batches for a given academic period or reporting year.
  • Populating LOVs and lookup lists in HESA import forms by returning BATCH_ID as the value and DESCRIPTION as the displayed label.
  • Joining to HESA student detail tables on BATCH_ID to reconcile staged student counts against each defined batch.
  • Auditing which batches exist within a reporting cycle, ordered by BATCH_ID to reflect sequence-generated run order.

Related Objects

The ETRM metadata records no outbound dependencies: IGS.IGS_HE_BATCH_INT does not reference any database object. It is referenced by APPS.IGS_HE_BATCH_INT, which conventionally denotes the APPS-layer synonym or view through which the table is accessed in a multi-org or secured EBS environment.

Because the documented foreign-key set is limited, related objects beyond the APPS synonym are inferred from functional context. The substantial relationships are with the HESA import detail tables that carry BATCH_ID as a foreign key back to this batch header, and with the TCA person structures underlying the HZ_PERSON business entity category. The IGS_HE_BATCH_INT_PK index on BATCH_ID is the join key used in each of these relationships. Analysts should consult the IGS schema for the corresponding HESA detail and staging tables, since the provided metadata enumerates only the APPS reference and does not list those dependent tables explicitly.