Results for “enquiry_source_type”

49 results




Overview
Explore in AI Chat

AI-generated from documented ETRM metadata — verify critical details on the linked pages.

Overview

The view IGS_IN_APPL_CHAR_TYP_V belongs to the IGS – Student System product family within Oracle E-Business Suite. In the ETRM metadata for both release 12.1.1 and 12.2.2, this object is explicitly flagged as Obsolete, and its documented description is "Inquiries application characteristics type – Obsolete." The view was originally designed to present inquiry (enquiry) application characteristic type information associated with applicants and their enquiries, exposing descriptive characteristics attached to an enquiry application record.

Functionally, the view acts as a reporting and integration surface that joins an enquiry-application characteristic fact table to its lookup/definition table and to the parent enquiry-application header. It is a denormalized read-only construct intended for inquiry screens, concurrent reports, and downstream interfaces that need to resolve the raw characteristic type code into a human-readable description alongside enquiry-level contextual attributes. Because the object is obsolete and "Not implemented in this database," it should be treated as historical metadata rather than an active runtime dependency in current implementations.

Underlying Base Objects

The view text documented in the ETRM metadata defines the view over three base tables, joined on two key relationships:

  • IGS_IN_APPL_CHAR_TYP (aliased ICT) – the primary driving table holding the application/inquiry characteristic type assignment for a person and enquiry application number.
  • IGS_IN_ENQ_CHAR_TYPE (aliased ECT) – the characteristic type definition/lookup table providing the DESCRIPTION text for each characteristic type code.
  • IGS_IN_ENQUIRY_APPL (aliased EAP) – the enquiry application header supplying enquiry date and source type.

The join predicates are defined as: ICT.ENQUIRY_CHARACTERISTIC_TYPE = ECT.ENQUIRY_CHARACTERISTIC_TYPE, plus a composite join on ICT.PERSON_ID = EAP.PERSON_ID and ICT.ENQUIRY_APPL_NUMBER = EAP.ENQUIRY_APPL_NUMBER. The documented ETRM metadata records no separately listed referenced base objects, though the view text itself makes the three-table dependency explicit. All three tables carry the IGS_IN_ prefix, consolidating the "Inquiries" sub-domain of the Student System.

Key Columns

The view projects the following columns, which together identify an enquiry characteristic assignment and its context:

  • ROW_ID – the ROWID of the underlying IGS_IN_APPL_CHAR_TYP row, useful for identifying the physical record.
  • PERSON_ID – the identifier of the person (applicant/prospect) associated with the enquiry.
  • ENQUIRY_APPL_NUMBER – the enquiry application number linking the characteristic to a specific enquiry application.
  • ENQUIRY_DT – the date the enquiry was recorded, sourced from the enquiry application header.
  • ENQUIRY_SOURCE_TYPE – the source or channel through which the enquiry originated.
  • ENQUIRY_CHARACTERISTIC_TYPE – the coded value identifying the characteristic type.
  • DESCRIPTION – the decoded, user-facing description of the characteristic type from the lookup table.
  • CREATED_BY, CREATION_DATE, LAST_UPDATED_BY, LAST_UPDATE_DATE, LAST_UPDATE_LOGIN – standard EBS WHO columns providing audit and concurrency information.

Common Use Cases and Queries

The view supports enquiry analysis and characteristic reporting. A typical report would list enquiry characteristics per person with their descriptions:

  • Enquiry characteristic listings filtered by PERSON_ID or ENQUIRY_APPL_NUMBER.
  • Analysis of enquiry volumes by ENQUIRY_SOURCE_TYPE and characteristic type.
  • Data extracts for downstream CRM or admissions interfaces requiring decoded characteristic descriptions.

Sample query:

SELECT person_id, enquiry_appl_number, enquiry_dt, enquiry_source_type, description
FROM igs_in_appl_char_typ_v
WHERE person_id = :p_person_id
ORDER BY enquiry_dt DESC;

Given the obsolete designation and the note "Not implemented in this database," implementations on 12.1.1 and 12.2.2 should not rely on this view remaining available; equivalent functionality must be sourced from supported Student System objects.