Results for “igs_ad_unit_sets”

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

Overview

IGS_AD_UNIT_SETS is a table in the IGS (Student System) product schema of Oracle E-Business Suite, documented as VALID in both release 12.1.1 and 12.2.2 of ETRM. Its stated purpose is to hold desired unit set details — that is, the set of academic units (subjects, modules, or course components) that an applicant or student wishes to undertake as part of an admissions or program application record. The table therefore occupies a supporting, detail-level position within the admissions (AD) family of IGS objects, capturing the applicant's expressed unit preferences in ranked order alongside the parent application identifiers.

The metadata classifies this object heuristically as standalone under the Data Vault model mined from its foreign key structure. In modeling terms, this suggests the table behaves less like a pure hub or link and more like a standalone satellite-style container of descriptive attributes keyed by its own surrogate identifier, with no outgoing foreign keys defined to other objects.

Key Information Stored

The table contains 17 documented columns in the 12.1.1 physical schema. The most significant are:

• UNIT_SET_ID — the surrogate primary key, enforced by the constraint IGS_AD_UNIT_SETS_PK. This is the column users search for when locating the PK definition.
• PERSON_ID — identifies the person (applicant or student) to whom the unit set belongs.
• ADMISSION_APPL_NUMBER — the admissions application number linking the unit set to a specific application.
• PROGRAM_APPLICATION_ID and PROGRAM_ID — the program application and program context for the requested units.
• UNIT_SET_CD — the code identifying the unit set itself.
• NOMINATED_COURSE_CD — the course nominated by the applicant.
• SEQUENCE_NUMBER and RANK — ordering and preference attributes for the record.
• VERSION_NUMBER — supports versioned or superseded unit set records.
• Audit columns CREATED_BY, CREATION_DATE, LAST_UPDATED_BY, LAST_UPDATE_DATE, LAST_UPDATE_LOGIN, REQUEST_ID, and PROGRAM_UPDATE_DATE.

No unique business-key index is documented beyond the primary key, so UNIT_SET_ID is the only confirmed unique identifier.

Common Use Cases and Queries

Typical usage centers on retrieving an applicant's desired units for admission or program planning. A join to the admissions application and person context is common:

• Listing unit sets for a given application: SELECT unit_set_cd, rank, sequence_number FROM igs_ad_unit_sets WHERE admission_appl_number = :appl_no ORDER BY rank;
• Reporting nominated courses per person: SELECT person_id, nominated_course_cd, unit_set_cd FROM igs_ad_unit_sets WHERE person_id = :person_id;
• Audit and change tracking using LAST_UPDATE_DATE and LAST_UPDATED_BY.
• Resolving the primary key constraint IGS_AD_UNIT_SETS_PK against ALL_CONSTRAINTS for documentation or migration work.

Related Objects

Foreign key metadata shows two objects referencing this table, joined on UNIT_SET_ID:

• IGR_EPU_CATEGORY_UPG — references IGS_AD_UNIT_SETS via UNIT_SET_ID, linking unit sets to category upgrade records.
• IGS_AD_RECRUIT_INT — references IGS_AD_UNIT_SETS via UNIT_SET_ID, connecting unit sets to recruitment interface data.
• IGS_AD_UNIT_SETS_PK — the primary key constraint on UNIT_SET_ID, queryable in ALL_CONSTRAINTS and ALL_CONS_COLUMNS.

Because the table has no outgoing foreign keys, it acts as a referenced parent within the IGS admissions model, and any integration or reporting layer should treat UNIT_SET_ID as the stable join key.