Search Results up_header_id




Overview
Explore in AI Chat

Overview

IGS.IGS_AD_UP_HEADER is a transactional table in the Oracle E-Business Suite IGS (Intelligent Grants System / Student Systems) schema that stores header-level information for unit placements within the academic admissions and placement model. Unit placement headers capture the scoring definitions and thresholds applied when a student's prior learning, admissions test, or unit-level assessment is evaluated against a defined test segment. In Oracle EBS 12.1.1 and 12.2.2, the table resides in the APPS_TS_TX_DATA tablespace with a PCT Free of 10, and its primary key index IGS_AD_UP_HEADER_U1 is a NONUNIQUE normal index on UP_HEADER_ID stored in APPS_TS_TX_IDX. The table is registered under FND Design Data as IGS.IGS_AD_UP_HEADER and carries a VALID status.

From a Data Vault modeling perspective, the ETRM relationship metadata classifies this object heuristically as standalone, with no downstream link dependencies inferred beyond its parent and child relationships. It may be modeled as a hub or reference entity anchored on the UP_HEADER_ID surrogate, given that business keys are not documented as unique.

Key Information Stored

The table contains eleven documented columns. The most operationally significant are:

  • UP_HEADER_ID (NUMBER(15)) — the surrogate primary key and unique identifier for each unit placement header record.
  • ADMISSION_TEST_TYPE (VARCHAR2(30)) — the admission test type associated with the placement header.
  • TEST_SEGMENT_ID (NUMBER(15)) — foreign key indicating the test segment against which scoring applies.
  • DEFINITION_LEVEL (VARCHAR2) — the definition level that governs the interpretation of the scoring rules.
  • MIN_SCORE (NUMBER) — the minimum acceptable score for the placement.
  • MAX_SCORE (NUMBER) — the maximum acceptable score for the placement.
  • The five standard Who columns — CREATED_BY, CREATION_DATE, LAST_UPDATED_BY, LAST_UPDATE_DATE, and LAST_UPDATE_LOGIN — which provide audit and concurrency tracking.

The documented NONUNIQUE index on UP_HEADER_ID effectively serves as the primary key enforcement path, and no separate unique business-key index is defined, so business-key candidates are limited to combinations of ADMISSION_TEST_TYPE, TEST_SEGMENT_ID, and DEFINITION_LEVEL.

Common Use Cases and Queries

Typical applications include validating admissions placement rules, reporting minimum and maximum admissible scores per test segment, and joining headers to detail rows for a complete placement picture. A standard header lookup uses the primary key:

SELECT UP_HEADER_ID, ADMISSION_TEST_TYPE, TEST_SEGMENT_ID,
       DEFINITION_LEVEL, MIN_SCORE, MAX_SCORE
FROM   IGS.IGS_AD_UP_HEADER
WHERE  UP_HEADER_ID = :p_up_header_id;

Analysts frequently aggregate score ranges per segment:

SELECT TEST_SEGMENT_ID, COUNT(*), MIN(MIN_SCORE), MAX(MAX_SCORE)
FROM   IGS.IGS_AD_UP_HEADER
GROUP BY TEST_SEGMENT_ID;

Audit reporting that surfaces recently modified placement definitions uses the Who columns, and drill-down reports join IGS_AD_UP_DETAIL on UP_HEADER_ID to present placement line detail alongside header scoring bands.

Related Objects

IGS_AD_UP_HEADER participates in a small but tightly coupled relationship set:

  • IGS.IGS_AD_UP_DETAIL — the primary child table; joined on UP_HEADER_ID → IGS_AD_UP_DETAIL.UP_HEADER_ID, holding detail-level placement rows.
  • IGS.IGS_AD_TEST_SEGMENTS — parented via TEST_SEGMENT_ID → IGS_AD_TEST_SEGMENTS, supplying the test segment definitions referenced by the header.
  • APPS.IGS_AD_UP_HEADER — the APPS-layer synonym or view through which applications and reports typically query the base table.

No additional database objects are documented as being referenced by IGS_AD_UP_HEADER beyond IGS_AD_TEST_SEGMENTS, and no other tables besides IGS_AD_UP_DETAIL are documented as referencing it. This makes the object a compact, well-scoped component of the IGS admissions data model.