Search Results inquiry_characteristic_type

Overview

IGS.IGS_AD_INQ_CHAR_INT is an interface table in the Oracle E-Business Suite IGS (Intelligent Grants/Student Systems) schema. As documented in the ETRM metadata, it holds admission inquiry characteristic interface records and is explicitly flagged as Obsolete. Its naming and column structure indicate it was designed as a staging area for inbound data loads — most likely via SQL*Loader or a concurrent program — that populate admission inquiry characteristic data before a validation and import process moves validated rows into the corresponding production admission tables.

The object carries a status of VALID in the data dictionary despite its obsolete functional designation, meaning the physical table and its unique index remain intact in supported releases such as 12.1.1 and 12.2.2. Based on the heuristic Data Vault classification mined from its FK structure, this table is best modeled as a standalone object. It has no documented foreign key dependencies to other tables, consistent with an interface table that receives flat, denormalized input from external sources and resolves its relationships only during the import process. In practice, it functions as a satellite-like staging structure: the natural business key is the interface record itself, which is then reconciled against existing application data.

Key Information Stored

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

• INTERFACE_INQ_CHAR_ID — A unique identifier assigned to each row of the interface table. This column is the documented primary key (IGS_AD_INQ_CHAR_INT_PK) and is also the business-key candidate enforced by unique index IGS_AD_INQ_CHAR_INT_U1. It must be populated at insert time.
• INTERFACE_INQ_APPL_ID — Interface Inquiry Application Identifier, linking the staged characteristic row to the inquiry application it qualifies.
• INQUIRY_CHARACTERISTIC_TYPE — The characteristic type code for the inquiry (VARCHAR2(30)). This is the column most frequently targeted in searches and drives the semantics of each staged row.
• DUP_INQUIRY_APPL_NUMBER and DUP_PERSON_ID — Duplicate detection fields retained during matching, recording the inquiry application number and person identifier identified as potential duplicates.
• STATUS — Processing state of the record: 1='Completed', 2='Pending', 3='Error', 4='Warning'.
• MATCH_IND — Outcome of the matching logic, ranging from 18 ('match occurred and used import values') through 22 ('match reviewed and do not import') to 11 ('no match').
• ERROR_CODE — Error code captured when validation fails.
• INTERFACE_INQ_APPL_ID alongside audit columns CREATED_BY, CREATION_DATE, LAST_UPDATED_BY, LAST_UPDATE_DATE, and LAST_UPDATE_LOGIN, plus the concurrent-manager columns REQUEST_ID, PROGRAM_APPLICATION_ID, PROGRAM_ID, and PROGRAM_UPDATE_DATE.

The surrogate key (INTERFACE_INQ_CHAR_ID) identifies a staging row; the business-key candidate in the unique index prevents duplicate interface records from being loaded twice.

Common Use Cases and Queries

Because the table is documented as obsolete, new development should avoid it; however, operational and reconciliation queries remain useful on legacy instances. A typical diagnostic query retrieves pending or errored rows for review:

• SELECT INTERFACE_INQ_CHAR_ID, INTERFACE_INQ_APPL_ID, INQUIRY_CHARACTERISTIC_TYPE, STATUS, MATCH_IND, ERROR_CODE FROM IGS.IGS_AD_INQ_CHAR_INT WHERE STATUS IN ('2','3') ORDER BY INTERFACE_INQ_CHAR_ID;
• Match-outcome reporting: ... WHERE MATCH_IND = '20' isolates records requiring review before import.
• Duplicate analysis: group by DUP_PERSON_ID or DUP_INQUIRY_APPL_NUMBER to identify repeated applicants.
• Concurrent program traceability: filter on REQUEST_ID or PROGRAM_ID to inspect the load run that inserted the rows.
• Characteristic-type profiling: SELECT INQUIRY_CHARACTERISTIC_TYPE, COUNT(*) FROM IGS.IGS_AD_INQ_CHAR_INT GROUP BY INQUIRY_CHARACTERISTIC_TYPE;

Related Objects

The documented relationship data classifies this object as standalone with no FK dependencies, so joins must be inferred rather than declared. The most significant associated objects are:

• IGS_AD_INQ_CHAR_INT_PK — Primary key constraint on INTERFACE_INQ_CHAR_ID.
• IGS_AD_INQ_CHAR_INT_U1 — Unique index on INTERFACE_INQ_CHAR_ID, enforcing the business key.
• IGS_AD_INQUIRIES / IGS_AD_INQ_APPLICATIONS — Production admission inquiry tables targeted by the import, joined on INTERFACE_INQ_APPL_ID against the application identifier.
• IGS_AD_INQ_CHARACTERISTICS — Destination for validated INQUIRY_CHARACTERISTIC_TYPE rows (name inferred from the column domain).
• FND_CONCURRENT_REQUESTS — Joined on REQUEST_ID to trace the loading concurrent program.
• HZ_PARTIES / HZ_PERSON_PROFILES — Joined on DUP_PERSON_ID for duplicate person resolution.

These associations reflect the import lifecycle rather than formal referential constraints, consistent with the standalone classification recorded in the metadata.