Search Results igr_i_appl_int_pk

Overview

The IGR_I_APPL_INT table resides in the IGS (Student System) schema and is documented within Oracle E-Business Suite 12.1.1 and 12.2.2 as the staging interface for admission inquiry instance records. Its functional purpose, per ETRM documentation, is to hold admission inquiry instance interface records — that is, rows that capture inquiries from prospective applicants (or related parties) prior to validation, matching, and migration into the operational admissions and recruiting tables. It is therefore a transient inbound object, typically loaded from external prospect feeds, self-service entry, or integration pipelines, and subsequently consumed by concurrent programs that validate and post the records.

From a heuristic Data Vault perspective, the mined foreign-key structure suggests classification as a link entity: the table's primary key and FK relationships connect distinct business entities such as parties, sales leads, and inquiry types, rather than storing descriptive attributes alone. This classification is a modeling suggestion only, derived from the documented FK topology, and should not be treated as a prescriptive design directive.

Key Information Stored

The physical schema documented in ETRM spans 61 columns. The most significant are:

• INTERFACE_INQ_APPL_ID — the surrogate primary key, enforced by unique index IGR_I_APPL_INT_PK and the business-key candidate for row-level identification.
• INTERFACE_ID and INTERFACE_RUN_ID — correlate rows to a specific batch or interface run.
• SALES_LEAD_ID — FK reference to AS_SALES_LEADS, linking the inquiry to the CRM recruiting lead.
• REGISTERING_PERSON_ID — FK reference to HZ_PARTIES, identifying the registering party.
• PERSON_ID — the person associated with the inquiry.
• INQUIRY_TYPE_ID — a documented FK reference (external target) that classifies the inquiry.
• ENQUIRY_APPL_NUMBER and INQUIRY_DT — the external inquiry reference and its date.
• INQUIRY_STATUS, INQUIRY_ENTRY_STATUS_ID, and INQUIRY_ENTRY_LEVEL_ID — workflow state for the incoming record.
• MATCH_IND, STATUS, ERROR_CODE, and ERROR_TEXT — processing outcomes and diagnostics.
• ADM_CAL_TYPE, ADM_CI_SEQUENCE_NUMBER, ACAD_CAL_TYPE, and ACAD_CI_SEQUENCE_NUMBER — calendar and term context for the inquiry.
• Standard WHO/audit columns (CREATED_BY, CREATION_DATE, LAST_UPDATED_BY, LAST_UPDATE_DATE) and the ATTRIBUTE1..20 descriptive flexfield segment columns are present.

Common Use Cases and Queries

Typical uses center on reconciliation, exception handling, and audit reporting. Analysts often query rows pending match or errored during posting:

• Identify failed interface rows: SELECT INTERFACE_INQ_APPL_ID, ERROR_CODE, ERROR_TEXT FROM IGR_I_APPL_INT WHERE ERROR_CODE IS NOT NULL;
• Review a batch: SELECT * FROM IGR_I_APPL_INT WHERE INTERFACE_RUN_ID = :run_id;
• Match processing status: SELECT MATCH_IND, COUNT(*) FROM IGR_I_APPL_INT GROUP BY MATCH_IND;
• Join to party data via REGISTERING_PERSON_ID, and to sales leads via SALES_LEAD_ID, to trace inquiry provenance.

Related Objects

• HZ_PARTIES — joined via REGISTERING_PERSON_ID to resolve the registering party.
• AS_SALES_LEADS — joined via SALES_LEAD_ID for the CRM recruiting lead.
• INQUIRY_TYPE_ID reference — the inquiry-type lookup controlling classification.
• IGR_I_APPL_INT_PK — the unique index enforcing the primary key.
• Admissions concurrent programs and the recruiting integration APIs that populate this interface and then post validated rows into the operational inquiry tables.