Search Results unit_set_preference

Overview

IGS.IGS_AD_INQ_UNT_INT is an Oracle E-Business Suite interface table owned by the IGS (Student Systems / Oracle Advanced Benefits academic) schema. It resides in the APPS_TS_INTERFACE tablespace, which is the standard staging area for inbound data loads and concurrent-program driven integrations. The table holds admission inquiry unit interface records, functioning as the transient landing zone where prospective-student "inquiry unit" selections are validated, matched, and ultimately transferred into the base admission inquiry unit tables during the admissions inquiry import process.

The table is documented as VALID in both the 12.1.1 and 12.2.2 releases, and its FND Design Data registration confirms it is part of the shipped IGS application object set rather than a custom extension. Because it carries the standard WHO columns and the concurrent-program columns (REQUEST_ID, PROGRAM_APPLICATION_ID, PROGRAM_ID, PROGRAM_UPDATE_DATE), it is clearly designed to be populated and consumed by a concurrent manager program rather than maintained manually.

From a Data Vault modeling perspective, the metadata's heuristic classification is standalone. This is a suggestion only: the table has no documented foreign keys to parent hubs, and behaves as a self-contained staging entity rather than a hub, link, or satellite in an enterprise integration bus.

Key Information Stored

The primary key is documented as a composite candidate in the unique index IGS_AD_INQ_UNT_INT_U1, backed by the single column INTERFACE_INQ_UNT_ID. Although the index is unique and named as a business-key candidate, the column itself functions as the surrogate identifier for each interface row and must be populated at insert time, typically from the source's parent identifier.

• INTERFACE_INQ_UNT_ID — Surrogate primary key. Unique identifier for each interface row; must be populated during insert.
• INTERFACE_INQ_APPL_ID — Links the unit row to its parent inquiry application interface row.
• UNIT_SET_CODE_ID — Reference to the unit set chosen by the applicant (for example English, History, or Biology).
• UNIT_SET_PREFERENCE — Numeric ranking of the unit set (1, 2, 3), enabling ordered preference capture.
• DUP_INQ_UNIT_SET_PREF_ID — Identifier used to detect duplicate unit-set preference entries during validation.
• STATUS — Processing state: 1 = Completed, 2 = Pending, 3 = Error, 4 = Warning.
• MATCH_IND — Match indicator showing whether the incoming row matched an existing unit set.
• ERROR_CODE — Error code assigned when validation fails.
• CREATED_BY, CREATION_DATE, LAST_UPDATED_BY, LAST_UPDATE_DATE, LAST_UPDATE_LOGIN — Standard WHO audit columns.
• REQUEST_ID, PROGRAM_APPLICATION_ID, PROGRAM_ID, PROGRAM_UPDATE_DATE — Concurrent-program provenance columns linking each row to the run that processed it.

Common Use Cases and Queries

The dominant use case is monitoring and troubleshooting the admissions inquiry unit import. Because errors and warnings are flagged in-row, support staff commonly query rows that failed validation and inspect the associated ERROR_CODE. The mandatory WHO and concurrent-program columns allow filtering by request, making it straightforward to isolate a single concurrent run.

• Find pending rows awaiting processing: filter on STATUS = 2.
• Report errors: filter on STATUS IN (3,4) and group by ERROR_CODE.
• Trace a run: filter by REQUEST_ID and join INTERFACE_INQ_APPL_ID back to the parent application interface table.
• Order preferences: sort by UNIT_SET_PREFERENCE within a UNIT_SET_CODE_ID grouping.
• Detect duplicates: isolate rows where DUP_INQ_UNIT_SET_PREF_ID is populated.

A representative query follows: SELECT INTERFACE_INQ_UNT_ID, UNIT_SET_CODE_ID, UNIT_SET_PREFERENCE, STATUS, ERROR_CODE FROM IGS.IGS_AD_INQ_UNT_INT WHERE STATUS = 3 ORDER BY CREATION_DATE DESC;. Reporting extracts typically join UNIT_SET_CODE_ID to the unit set code reference object to resolve the descriptive name.

Related Objects

The relationship metadata classifies the table as standalone, so no foreign keys are documented. The most significant logical dependencies are the parent inquiry application interface table, referenced through INTERFACE_INQ_APPL_ID, and the base admission inquiry unit tables that receive the corrected data after processing. The unit set code object referenced by UNIT_SET_CODE_ID supplies the descriptive values (English, History, Biology). Reference and lookup objects supply the STATUS and ERROR_CODE translations. The concurrent program definition associated with PROGRAM_APPLICATION_ID and PROGRAM_ID owns the import logic that reads and updates this table. Because all linkage is by column convention rather than enforced constraints, joins to these related objects should always be validated against the interface parent before promoting rows to production.