Search Results igs_in_enquiry_appl




Overview
Explore in AI Chat

Overview

The IGS_IN_ENQUIRY_APPL view resides in the APPS schema in Oracle E-Business Suite and belongs to the IGS — Student System product family. In the documented ETRM metadata for both 12.1.1 and 12.2.2 it carries a status of Obsolete. Despite that designation, the object remains present in the database with a VALID status and exposes a full column list, which is characteristic of legacy Enrollment/Admissions (Oracle Student System) inquiry-application captures that were later superseded by newer data models but retained for backward compatibility and historical reporting.

The view presents enquiry-application header information: the person making or associated with the enquiry, the enquiry/application number, academic and admissions calendar references, enquiry status and source, registration party, indicative mailing dates, free-text comments, descriptive flexfield attributes, and standard Oracle WHO columns. It is an ORG_ID-striped view, meaning it applies a multi-org security predicate against IGS_IN_ENQUIRY_APPL_ALL, returning only rows belonging to the operating unit implied by the session's CLIENT_INFO context.

Underlying Base Objects

The view is defined over a single documented base table:

  • IGS_IN_ENQUIRY_APPL_ALL — the multi-org base table holding all enquiry-application records across operating units.

The view does not itself store data; it projects the columns of the base table and appends the pseudo-column ROW_ID (derived from A.ROWID). The multi-org filter is implemented with a character-based comparison on USERENV('CLIENT_INFO'):

WHERE NVL(A.ORG_ID, NVL(TO_NUMBER(DECODE(SUBSTRB(USERENV('CLIENT_INFO'),1,1),' ',NULL,SUBSTRB(USERENV('CLIENT_INFO'),1,10))), -99)) = NVL(TO_NUMBER(DECODE(SUBSTRB(USERENV('CLIENT_INFO'),1,1),' ',NULL,SUBSTRB(USERENV('CLIENT_INFO'),1,10))), -99)

This is the classic pre-12.2 multi-org rule. Because the ETRM metadata documents no additional referenced base objects, all functional meaning is carried by IGS_IN_ENQUIRY_APPL_ALL.

Key Columns

Common Use Cases and Queries

Because the view is documented as obsolete, new development should avoid it; however, existing reports, extracts, and integrations that reference LAST_PROCESS_DT commonly query it to measure enquiry aging. A representative query follows:

SELECT enquiry_appl_number, person_id, enquiry_status, enquiry_dt, last_process_dt, org_id FROM apps.igs_in_enquiry_appl;

A more practical aging query:

SELECT person_id, enquiry_appl_number, last_process_dt, TRUNC(SYSDATE) - TRUNC(last_process_dt) AS days_since_process FROM apps.igs_in_enquiry_appl WHERE last_process_dt IS NOT NULL ORDER BY last_process_dt;

Typical uses include pipeline/dashboard reporting on admissions enquiries, identifying records not touched within an SLA window (often triggered from the LAST_PROCESS_DT value the user searched for), and historical reconciliation of enrolment or admissions proposals. Where multi-org security context is not initialized for the session, an ORG_ID predicate should be added explicitly, since the view's predicate relies on CLIENT_INFO.