Search Results igs_ad_up_header




Overview
Explore in AI Chat

Overview

IGS_AD_UP_HEADER is a transactional table in the IGS (Student System) product family of Oracle E-Business Suite, documented as VALID in both release 12.1.1 and 12.2.2. The ETRM description states that the table "holds unit placement header details." Within the Oracle Student System data model, unit placement records capture the outcome of admission or placement testing — specifically the scores an applicant or student achieves against a defined test segment. IGS_AD_UP_HEADER supplies the header-level record for that scoring activity, while its dependent table supplies the per-unit or per-line detail.

Under the heuristic Data Vault classification mined from the foreign key structure, IGS_AD_UP_HEADER is assessed as standalone. This classification is a modeling suggestion rather than a physical constraint: the table's only recorded outbound foreign key targets IGS_AD_TEST_SEGMENTS, and its inbound dependency from IGS_AD_UP_DETAIL is a child-to-parent relationship. In Data Vault terms, a standalone assessment suggests this object can be treated as a hub-like anchor keyed on UP_HEADER_ID, with descriptive attributes such as score bounds and definition level carried as satellite context. Implementers building a warehouse layer should treat this as guidance and confirm against the actual business grain before finalizing the model.

Key Information Stored

The documented physical schema for 12.1.1 lists eleven columns. The most significant are:

  • UP_HEADER_ID — the surrogate primary key, enforced by the unique index IGS_AD_UP_HEADER_U1. This is a system-generated identifier with no business meaning and should be used exclusively for joins.
  • ADMISSION_TEST_TYPE — classifies the admission test associated with the placement header. This is a strong business-key candidate because placement rules typically vary by test type.
  • TEST_SEGMENT_ID — the only documented outbound foreign key, referencing IGS_AD_TEST_SEGMENTS. It identifies which segment of the test the header pertains to.
  • DEFINITION_LEVEL — the level at which the placement definition applies, governing the scope of the header record.
  • MIN_SCORE and MAX_SCORE — the acceptable or achievable score band for the placement, the core business payload of the row.
  • CREATED_BY, CREATION_DATE, LAST_UPDATED_BY, LAST_UPDATE_DATE, LAST_UPDATE_LOGIN — the standard Oracle EBS audit columns, populated by the application's WHO columns convention and used for change tracking and data lineage.

No unique index other than the primary key is documented, so no natural business key is enforced at the database level. Any de-duplication logic must therefore be derived from the combination of ADMISSION_TEST_TYPE, TEST_SEGMENT_ID, and DEFINITION_LEVEL.

Common Use Cases and Queries

The primary scenario is reporting on placement score thresholds. Administrators and admissions staff query the header to determine the minimum and maximum acceptable scores for a given test segment, and then reconcile those bounds against actual outcomes stored in the detail table. A typical join pattern is:

  • Join IGS_AD_UP_HEADER to IGS_AD_TEST_SEGMENTS on TEST_SEGMENT_ID to resolve segment descriptions alongside score bounds.
  • Join IGS_AD_UP_HEADER to IGS_AD_UP_DETAIL on UP_HEADER_ID to compare header-level thresholds against line-level results.
  • Filter on ADMISSION_TEST_TYPE and DEFINITION_LEVEL to isolate the rule set applicable to a specific admission cycle.

Common reporting outputs include score-range validation reports, placement rule configuration extracts, and audit queries using LAST_UPDATE_DATE to identify recently modified placement definitions. Because the table is low-volume configuration-style data rather than high-volume transaction data, queries rarely require partition pruning or heavy indexing beyond the primary key.

Related Objects

  • IGS_AD_UP_DETAIL — the principal dependent table. It references IGS_AD_UP_HEADER through the UP_HEADER_ID column, forming the header-to-line relationship. Any query reconciling placement totals must join on this column.
  • IGS_AD_TEST_SEGMENTS — the parent of the only documented outbound foreign key. IGS_AD_UP_HEADER.TEST_SEGMENT_ID resolves to this table, providing test segment definitions.
  • IGS_AD_UP_HEADER_U1 — the unique index enforcing the UP_HEADER_ID primary key; referenced by all dependent foreign keys.
  • IGS schema objects generally — the surrounding admissions (IGS_AD_*) tables used for test definition, applicant records, and score capture, which supply context when building end-to-end placement reports.

Because the documented relationship footprint is narrow, integration work should verify actual constraints in the target instance rather than relying solely on the ETRM listing.