Search Results inquiry_method_code




Overview
Explore in AI Chat

Overview

IGR_I_A_ITYPE_V is a reporting view in the Oracle E-Business Suite IGS (Student System) product family. It exposes the set of information types that were requested by a prospective applicant or lead during an inquiry or enquiry transaction. The view consolidates data from the IGS inquiry application tables with deliverable and sales-lead reference data, so that enquiry responses can be reported alongside the nature of the enquiry and the associated vehicle response (inquiry method).

Under ETRM 12.2.2 the object is documented as obsolete and is recorded as "Not implemented in this database." Its product classification is "IGS - Student System (Obsolete)," which indicates the view is retained as legacy metadata for reference only and is not expected to exist in a current 12.1.1 or 12.2.2 instance. The view is therefore relevant primarily for historical reporting, migration analysis, and understanding of the pre-existing enquiry model rather than for new development.

Underlying Base Objects

The view is defined over four referenced objects:

All joins are equi-joins across these four sources; the view performs no aggregation and simply projects the combined result set. No base tables are separately documented for the view in the supplied metadata beyond those visible in the view text.

Key Columns

Common Use Cases and Queries

Typical usage centres on analysing which information types prospective students requested and the method by which the inquiry was made. A representative query filters on the inquiry method code:

  • SELECT person_id, enquiry_app_number, enquiry_dt, inquiry_method_code, inquiry_method, package_item, description FROM igr_i_a_itype_v WHERE inquiry_method_code = :method_code;
  • SELECT enquiry_app_number, COUNT(*) FROM igr_i_a_itype_v GROUP BY enquiry_app_number;
  • SELECT package_item, inquiry_method, COUNT(*) FROM igr_i_a_itype_v GROUP BY package_item, inquiry_method ORDER BY 3 DESC;

Because the object is documented as obsolete and not implemented, any query against IGR_I_A_ITYPE_V should be validated against the actual database before being relied upon. Where it is absent, equivalent data must be sourced directly from the underlying enquiry, deliverable, and sales-lead objects.