Search Results enquiry_dt




Overview
Explore in AI Chat

Overview

IGS_IN_APPL_CHAR_TYP_V is a supplementary Oracle E-Business Suite view owned by the APPS schema, delivered as part of the Student System (IGS) product family and registered under FND Design Data IGS.IGS_IN_APPL_CHAR_TYP_V. It exposes enquiry application characteristic type information, joining enquiry application header data with characteristic type definitions so that enquiry records can be reported with their associated descriptive characteristics in a single, denormalized result set. The view is described in the ETRM metadata as a "supplementary view used to simplify forms coding," a classification that explains both its purpose and its limitations: it exists primarily to support Oracle Forms-based enquiry screens rather than to serve as a stable integration interface. Oracle explicitly warns that querying or altering data through this view is not recommended, because its column list and underlying query text may change dramatically in subsequent minor or major releases. Consequently, the view is best regarded as a read-only convenience layer for enquiry and characteristic reporting, not as a contract for external systems.

Underlying Base Objects

The view is defined over three APPS base objects: IGS_IN_APPL_CHAR_TYP, IGS_IN_ENQUIRY_APPL, and IGS_IN_ENQ_CHAR_TYPE. These tables supply, respectively, the application characteristic type assignment, the enquiry application header (including person and enquiry date context), and the enquiry characteristic type definition. The view presents no documented dependency as being referenced by any other database object, confirming that it sits at the top of its dependency chain and is purely a consumer of the underlying tables. Because the view is a join across these three sources, its rows reflect only enquiry applications that have a matching characteristic type record; character type rows without an associated enquiry application, or enquiry applications without characteristic assignments, do not appear. This behaviour is important when the view is used for counting or completeness checks, since the result set is an intersection rather than a full outer join of the base data.

Key Columns

  • ROW_ID (ROWID, length 10) — the pseudo-column row identifier for each view row.
  • PERSON_ID (NUMBER, 15) — identifies the person associated with the enquiry application.
  • ENQUIRY_APPL_NUMBER (NUMBER) — the enquiry application number.
  • ENQUIRY_DT (DATE) — the date of the enquiry, which is the column most frequently referenced in ad hoc searches such as "enquiry_dt."
  • ENQUIRY_SOURCE_TYPE (VARCHAR2, 10) — the source from which the enquiry originated.
  • ENQUIRY_CHARACTERISTIC_TYPE (VARCHAR2, 10) — the characteristic type code assigned to the enquiry.
  • DESCRIPTION (VARCHAR2, 60) — the descriptive text for the characteristic type, useful for reporting without a secondary lookup.
  • CREATED_BY, CREATION_DATE, LAST_UPDATED_BY, LAST_UPDATE_DATE, LAST_UPDATE_LOGIN — standard EBS audit columns tracking record creation and amendment.

Common Use Cases and Queries

Typical usage is enquiry reporting: listing enquiries by date range, source, or characteristic type, and joining PERSON_ID to PER_PERSON_ALL or HZ_PARTIES for applicant detail. A representative query filtering on the enquiry date is:

SELECT enquiry_appl_number, person_id, enquiry_dt, enquiry_source_type, enquiry_characteristic_type, description FROM apps.igs_in_appl_char_typ_v WHERE enquiry_dt BETWEEN :start_date AND :end_date ORDER BY enquiry_dt;

Because of the documented instability warning, developers should treat the view as suitable only for display and analysis, avoid DML through it, and consider building custom queries directly against the base tables where a durable integration interface is required. All access should respect the standard EBS security and MOAC conventions applied to the underlying enquiry tables.