Search Results igr_i_appl_int




Overview
Explore in AI Chat

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:

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.