Search Results program_preference

Overview

IGS.IGS_AD_INQ_PRG_INT is an Oracle E-Business Suite interface table in the IGS (Student Systems / Higher Education) schema. It holds admission inquiry program interface records — that is, staging rows describing the academic program preferences a prospective applicant has expressed during an admission inquiry. The table acts as a transient landing zone where externally sourced or bulk-loaded inquiry program data is validated, matched against existing records, and then either imported into the base inquiry tables or rejected. It is created in the APPS_TS_INTERFACE tablespace, carries an FND Design Data registration of IGS.IGS_AD_INQ_PRG_INT, and is marked VALID.

Because it stores staged, mutable rows rather than durable master data, the metadata's heuristic Data Vault classification of standalone is appropriate as a modeling suggestion: the table is not a true hub, link, or satellite, but behaves as a processing or staging construct. Its only structural anchor is the surrogate primary key IGS_AD_INQ_PRG_INT_PK, and its single foreign key points outward to FV_DMS_CODE_DEFINITIONS_ALL, reflecting lookup-driven decoding of program codes.

Key Information Stored

The table exposes 17 documented columns. The most significant are:

• INTERFACE_INQ_PRG_ID — NUMBER(15), mandatory surrogate primary key and the business-key candidate backed by the unique index IGS_AD_INQ_PRG_INT_U1. It uniquely identifies each staged row.
• INTERFACE_INQ_APPL_ID — NUMBER(15), the interface inquiry application identifier, grouping program preference rows into a parent inquiry application.
• PROGRAM_CODE_ID — NUMBER(15), the inquired program code (for example BA or BS). This is the FK column joining to FV_DMS_CODE_DEFINITIONS_ALL.
• PROGRAM_PREFERENCE — NUMBER(15), the ordinal preference of the program (1, 2, 3), indicating the applicant's ranked choice. This is the column most relevant to the search term "program_preference".
• DUP_INQ_PROG_PREF_ID — NUMBER(15), identifier used to detect or resolve duplicate program preference entries.
• STATUS — VARCHAR2, the processing state of the row (1 Completed, 2 Pending, 3 Error, 4 Warning).
• MATCH_IND — VARCHAR2, the match outcome flag, e.g. 18 match used import values, 19 match retained existing values, 20 requires review, 21 reviewed/import, 22 reviewed/no import, 11 no match.
• ERROR_CODE — VARCHAR2(30), populated when validation or import fails.
• Standard WHO and concurrent columns — CREATED_BY, CREATION_DATE, LAST_UPDATED_BY, LAST_UPDATE_DATE, LAST_UPDATE_LOGIN, plus REQUEST_ID, PROGRAM_APPLICATION_ID, PROGRAM_ID, and PROGRAM_UPDATE_DATE, which tie each row to the concurrent request that produced it.

Common Use Cases and Queries

Typical scenarios include monitoring import progress, diagnosing errors, and reviewing duplicate or unmatched preferences before commit. A common pattern filters pending or errored rows for a concurrent request:

• SELECT INTERFACE_INQ_PRG_ID, INTERFACE_INQ_APPL_ID, PROGRAM_CODE_ID, PROGRAM_PREFERENCE, STATUS, ERROR_CODE FROM IGS.IGS_AD_INQ_PRG_INT WHERE STATUS IN ('2','3');
• To inspect ranked preferences per application: filter on PROGRAM_PREFERENCE and order by INTERFACE_INQ_APPL_ID, PROGRAM_PREFERENCE.
• To trace a batch, join REQUEST_ID to FND_CONCURRENT_REQUESTS.
• To review match decisions, group by MATCH_IND and STATUS for reconciliation reporting.

Related Objects

The documented relationships identify the following significant dependents and references:

• FV_DMS_CODE_DEFINITIONS_ALL — referenced via PROGRAM_CODE_ID; decodes program codes.
• IGS_AD_INQ_PRUNT_INT — references this table through INTERFACE_INQ_PRG_ID, forming the child interface rows associated with each program preference record.
• IGS_AD_INQ_PRG_INT_PK / IGS_AD_INQ_PRG_INT_U1 — the primary key constraint and the unique index on INTERFACE_INQ_PRG_ID that enforce row uniqueness.
• FND_CONCURRENT_REQUESTS — joined on REQUEST_ID to correlate staged rows with the concurrent program run.