Search Results learn_source_id

Overview

IGS.IGS_AD_INQ_APPL_INT is an interface table in the Oracle E-Business Suite Student System (IGS) schema, residing in the APPS_TS_INTERFACE tablespace. It holds admission inquiry instance interface records and is documented as Obsolete in the ETRM 12.1.1/12.2.2 repository. As an interface object, its purpose is to stage inbound admission inquiry data prior to validation, matching, and migration into the corresponding base application tables. The table carries the standard FND Design Data identifier IGS.IGS_AD_INQ_APPL_INT.

The physical schema documents 56 columns and a primary key constraint, IGS_AD_INQ_APPL_INT_PK, defined on INTERFACE_INQ_APPL_ID. A unique index, IGS_AD_INQ_APPL_INT_U1, is also defined on INTERFACE_INQ_APPL_ID, confirming that this column serves as both the surrogate primary key and the sole documented business-key candidate. Heuristic Data Vault classification mined from the foreign-key structure is standalone; from a modeling perspective, this suggests the table functions less as a conventional hub-and-satellite pair and more as an isolated staging entity with no documented parent/child link relationships inside the IGS model.

Key Information Stored

The columns below represent the most operationally significant attributes of the interface record:

• INTERFACE_INQ_APPL_ID — the unique identifier for each interface row; mandatory and populated at insert time. Documented as both the primary key and the unique-index key.
• INTERFACE_ID — the interface batch or run identifier linking the row to a processing instance.
• ENQUIRY_APPL_NUMBER — the inquiry application number carried from the source system.
• ACAD_CAL_TYPE / ACAD_CI_SEQUENCE_NUMBER — academic calendar type and its sequence number for the inquiry.
• ADM_CAL_TYPE / ADM_CI_SEQUENCE_NUMBER — admission calendar type and sequence number.
• INQUIRY_STATUS — inquiry status value such as 'MAILED' or 'INQUIRED'.
• INQUIRY_DT — date on which the inquiry was made.
• INQUIRY_SOURCE_TYPE — origin of the inquiry, for example 'Web Inquiry'.
• INQUIRY_ENTRY_STATUS_ID — inquiry status category (first time freshman, transfer, new graduate).
• INQUIRY_ENTRY_LEVEL_ID — inquiry entry level (first year, second year, junior, senior); this is the column referenced by the user search term.
• REGISTERING_PERSON_ID — person identifier of the party registering the inquiry.
• DUP_PERSON_ID / DUP_ENQUIRY_APPL_NUMBER — duplicate detection fields used during matching.
• STATUS / MATCH_IND / ERROR_CODE — processing outcome flags set by the interface program.
• LAST_PROCESS_DT — timestamp of the last processing attempt.
• ATTRIBUTE1–ATTRIBUTE20 — the standard EBS descriptive flexfield (DFF) segment set.
• CREATED_BY, CREATION_DATE, LAST_UPDATED_BY, LAST_UPDATE_DATE, LAST_UPDATE_LOGIN, REQUEST_ID, PROGRAM_APPLICATION_ID, PROGRAM_ID, PROGRAM_UPDATE_DATE — standard who-columns and concurrent request audit columns.

Common Use Cases and Queries

Because the table is marked obsolete, its principal use is historical troubleshooting and audit review of previously loaded admission inquiry batches. A typical pattern is to retrieve rows still failed or unmatched after an interface run:

• Locate rows by interface run: SELECT * FROM IGS.IGS_AD_INQ_APPL_INT WHERE INTERFACE_ID = :p_interface_id.
• Identify unprocessed or error rows: SELECT INTERFACE_INQ_APPL_ID, ENQUIRY_APPL_NUMBER, STATUS, ERROR_CODE FROM IGS.IGS_AD_INQ_APPL_INT WHERE STATUS <> 'PROCESSED'.
• Duplicate investigation: SELECT ENQUIRY_APPL_NUMBER, DUP_ENQUIRY_APPL_NUMBER, MATCH_IND FROM IGS.IGS_AD_INQ_APPL_INT WHERE MATCH_IND = 'Y'.
• Reporting by entry level and source: group by INQUIRY_ENTRY_LEVEL_ID, INQUIRY_ENTRY_STATUS_ID, and INQUIRY_SOURCE_TYPE to reconcile inquiry volumes against the base admissions tables.
• Audit lookups filtering on LAST_PROCESS_DT or REQUEST_ID to attribute loads to a specific concurrent request.

Related Objects

The documented relationship data classifies this object as standalone, exposing no explicit foreign-key dependencies to other IGS tables. As a result, joins are conventionally made through shared value keys rather than enforced constraints. Objects commonly associated with this interface table include:

• IGS_AD_INQ_APPL (base admission inquiry application) — the destination record, linked through ENQUIRY_APPL_NUMBER and, indirectly, INTERFACE_INQ_APPL_ID.
• IGS_AD_INQ_APPL_INT base keys written by the interface program identified by INTERFACE_ID.
• Calendar reference data — ACAD_CAL_TYPE and ADM_CAL_TYPE resolve against academic and admission calendar setup tables.
• Inquiry entry level and status validation sets — INQUIRY_ENTRY_LEVEL_ID and INQUIRY_ENTRY_STATUS_ID resolve against IGS lookup tables.
• Person / party tables — REGISTERING_PERSON_ID and DUP_PERSON_ID reference person identifiers in the TCA and IGS person models.
• Source and influence lookups — LEARN_SOURCE_ID, INFLUENCE_SOURCE_ID, and INQUIRY_SCHOOL_OF_INTEREST_ID resolve to inquiry source configuration tables.
• FND_CONCURRENT_REQUESTS — joined via REQUEST_ID for concurrent program attribution.
• IGS_AD_INQ_APPL_INT_PK / U1 — the primary key and unique index that constrain INTERFACE_INQ_APPL_ID.

Because the table is obsolete, functional maintenance and new integrations should be directed to its successor interface objects in the current IGS admission data model.