Search Results igs_ad_inq_char_int

Overview

IGS_AD_INQ_CHAR_INT is a table in the IGS schema (IGS – Student System) within Oracle E-Business Suite. Per the ETRM documentation, it holds admission inquiry characteristics interface records. The object is documented as Obsolete in both Release 12.1.1 and 12.2.2, meaning Oracle no longer supports or extends its functionality. Its status is VALID at the database level (the object still exists in the data dictionary), but it must be treated as a legacy stub retained for backward compatibility rather than an active integration point.

The table carries a documented physical schema of 17 columns and a single-column primary key, IGS_AD_INQ_CHAR_INT_PK, defined on INTERFACE_INQ_CHAR_ID. A unique index, IGS_AD_INQ_CHAR_INT_U1, also exists on INTERFACE_INQ_CHAR_ID. No foreign keys are documented, and the heuristic Data Vault classification mined from the key structure is standalone. As a modeling suggestion, this suggests the table behaves as a self-contained staging or interface structure rather than forming part of an integrated hub, link, or satellite constellation; the surrogate INTERFACE_INQ_CHAR_ID serves as the sole unique identifier without declarative referential ties to other IGS tables.

Key Information Stored

The documented columns fall into three functional groups: identification, matching/processing control, and standard EBS audit/program context.

• INTERFACE_INQ_CHAR_ID – Surrogate primary key (IGS_AD_INQ_CHAR_INT_PK) and the unique business-key candidate (IGS_AD_INQ_CHAR_INT_U1). Uniquely identifies each interface row.
• INTERFACE_INQ_APPL_ID – Identifier linking the characteristic row to the parent admission inquiry/application interface record.
• INQUIRY_CHARACTERISTIC_TYPE – Classifies the kind of inquiry characteristic being staged or transmitted.
• DUP_INQUIRY_APPL_NUMBER and DUP_PERSON_ID – Duplicate-detection attributes capturing a candidate inquiry application number and person identifier for matching purposes.
• STATUS – Processing state of the interface row (for example, whether it has been staged, processed, or rejected).
• MATCH_IND – Match indicator flagging whether the inquiry characteristic was matched against an existing record.
• ERROR_CODE – Error condition recorded when interface processing fails.
• Audit and concurrency columns – CREATED_BY, CREATION_DATE, LAST_UPDATED_BY, LAST_UPDATE_DATE, and LAST_UPDATE_LOGIN provide standard who/when auditing.
• Program context columns – REQUEST_ID, PROGRAM_APPLICATION_ID, PROGRAM_ID, and PROGRAM_UPDATE_DATE identify the concurrent request and program that last touched the row, enabling lineage and troubleshooting.

Common Use Cases and Queries

Because the table is obsolete, practical use is limited to remediation, archival, and historical reporting. Typical scenarios include identifying orphaned interface rows, quantifying unprocessed or errored records before decommissioning, and confirming whether any live process still writes to the object.

• Inspect unprocessed rows: SELECT INTERFACE_INQ_CHAR_ID, INTERFACE_INQ_APPL_ID, INQUIRY_CHARACTERISTIC_TYPE, STATUS, ERROR_CODE FROM IGS.IGS_AD_INQ_CHAR_INT WHERE STATUS IS NULL OR ERROR_CODE IS NOT NULL;
• Trace the originating concurrent program: SELECT REQUEST_ID, PROGRAM_ID, PROGRAM_APPLICATION_ID, PROGRAM_UPDATE_DATE, COUNT(*) FROM IGS.IGS_AD_INQ_CHAR_INT GROUP BY REQUEST_ID, PROGRAM_ID, PROGRAM_APPLICATION_ID, PROGRAM_UPDATE_DATE ORDER BY PROGRAM_UPDATE_DATE DESC;
• Review duplicate-detection activity:SELECT INTERFACE_INQ_CHAR_ID, DUP_INQUIRY_APPL_NUMBER, DUP_PERSON_ID, MATCH_IND FROM IGS.IGS_AD_INQ_CHAR_INT WHERE MATCH_IND = 'Y';
• Assess row age to decide on purge eligibility using CREATION_DATE and LAST_UPDATE_DATE.

No seeded concurrent program or API should be assumed operational; queries are best run read-only for audit and migration planning.

Related Objects

The documented metadata records no foreign keys and a standalone classification, so related objects must be inferred from naming conventions and column semantics rather than declarative constraints.

• IGS_AD_INQ_APPL (or the admission inquiry/application interface table) – conceptually linked via INTERFACE_INQ_APPL_ID to the parent inquiry record.
• IGS_AD_INQ_CHAR – the base (non-interface) admission inquiry characteristics table from which this interface table derives its name and structure.
• HZ_PARTIES / HZ_PERSON_PROFILES – for interpretation of DUP_PERSON_ID when resolving duplicate person matches.
• FND_CONCURRENT_REQUESTS – joined via REQUEST_ID to identify the concurrent request that populated the interface rows.
• FND_APPLICATION and FND_PROGRAM – joined via PROGRAM_APPLICATION_ID and PROGRAM_ID to resolve the owning program.
• FND_USER – joined via CREATED_BY and LAST_UPDATED_BY for auditor identification.

These joins are inferential and should be validated against the actual deployment before reliance, given the object's obsolete status.