Search Results igs_ad_inq_prg_int

Overview

The IGS_AD_INQ_PRG_INT table belongs to the IGS (Student System) product family within Oracle E-Business Suite. It is documented as an interface table that holds admission inquiry program interface records, and the ETRM metadata explicitly marks it as Obsolete and Not implemented in this database in both Oracle EBS 12.1.1 and 12.2.2. This means the object exists in the historical data model definition and dictionary but is not instantiated as a live, populated table in the certified release. Its purpose historically was to stage incoming admission inquiry program data — typically program codes and program preferences tied to an applicant's inquiry — before validation and transfer into the base admission inquiry tables.

Because the table is a staging/interface object, it carries a combination of transactional attributes (status, error codes, match indicators) and standard Oracle who-columns and request identifiers used by concurrent interface processes. The heuristic Data Vault classification mined from the FK structure is standalone, meaning the table is not modeled as a hub, link, or satellite in the current relationship graph — it participates only in limited foreign-key associations and is not a core business entity within the Student System data model. This classification should be read as a modeling suggestion rather than a definitive statement about the object's historical design.

Key Information Stored

The documented physical schema (ETRM 12.1.1) defines 17 columns owned by the IGS schema. The most significant columns are:

• INTERFACE_INQ_PRG_ID — The surrogate primary key, defined by constraint IGS_AD_INQ_PRG_INT_PK. A unique index, IGS_AD_INQ_PRG_INT_U1, also exists on this column, making it the single documented business-key candidate for the table.
• INTERFACE_INQ_APPL_ID — Links each interface program row back to the corresponding admission inquiry application staging record.
• PROGRAM_CODE_ID — Identifies the academic program code, and is the only documented foreign key target, referencing FV_DMS_CODE_DEFINITIONS_ALL.
• PROGRAM_PREFERENCE — Enumerates the applicant's stated preference ordering for the program.
• DUP_INQ_PROG_PREF_ID — Supports duplicate detection against existing inquiry program preference records.
• STATUS and MATCH_IND — Track processing state and whether the staged row matched an existing record during validation.
• ERROR_CODE — Captures validation failures for rejected interface rows.
• REQUEST_ID, PROGRAM_APPLICATION_ID, PROGRAM_ID, PROGRAM_UPDATE_DATE — Identify the concurrent request and the executable that processed the row.
• CREATED_BY, CREATION_DATE, LAST_UPDATED_BY, LAST_UPDATE_DATE, LAST_UPDATE_LOGIN — Standard Oracle audit columns.

Common Use Cases and Queries

In environments where the interface was active, the primary use case was auditing staged admission inquiry program data before transfer to base tables. Typical patterns included reconciling interface rows to their source requests, identifying rejected rows by error code, and confirming program preference ordering per inquiry.

• Rows staged by a specific concurrent request: SELECT * FROM IGS_AD_INQ_PRG_INT WHERE REQUEST_ID = :request_id;
• Rejected interface rows: SELECT INTERFACE_INQ_PRG_ID, PROGRAM_CODE_ID, ERROR_CODE FROM IGS_AD_INQ_PRG_INT WHERE STATUS = 'ERROR';
• Preference ordering for a given inquiry application: SELECT INTERFACE_INQ_APPL_ID, PROGRAM_CODE_ID, PROGRAM_PREFERENCE FROM IGS_AD_INQ_PRG_INT ORDER BY INTERFACE_INQ_APPL_ID, PROGRAM_PREFERENCE;
• Duplicate screening against existing preferences via DUP_INQ_PROG_PREF_ID and MATCH_IND.

Because the object is obsolete and not implemented, these queries are relevant only to legacy or historical reference models.

Related Objects

FK relationship data identifies a small number of associated objects:

• FV_DMS_CODE_DEFINITIONS_ALL — Referenced by IGS_AD_INQ_PRG_INT.PROGRAM_CODE_ID; joins yield program code descriptions.
• IGS_AD_INQ_PRUNT_INT — References this table via INTERFACE_INQ_PRG_ID, forming the sibling interface dependency.
• IGS_AD_INQ_PRG_INT_PK / IGS_AD_INQ_PRG_INT_U1 — The primary key constraint and unique index enforcing identity on INTERFACE_INQ_PRG_ID.

These constitute the full documented relationship footprint; the table is otherwise standalone within the IGS staging layer.