Search Results igs_in_enquiry_appl_all




Overview
Explore in AI Chat

Overview

The IGS_IN_ENQUIRY_APPL_ALL table is a core data entity within the Oracle E-Business Suite Student System (IGS) module. It is designed to store comprehensive records of enquiry applications made to an educational institution. These enquiries can pertain to various levels of academic interest and diverse information types, such as inquiries about specific faculties, programs, or ancillary services like accommodation. The table's structure supports a multi-organization architecture, as indicated by the '_ALL' suffix, meaning it stores data for all operating units with appropriate security via the ORG_ID column. Notably, the official ETRM documentation marks this table as "Obsolete," indicating it is part of a legacy data model that may have been superseded by newer functionality in releases 12.1.1 and 12.2.2, though it remains present in the database schema.

Key Information Stored

The table's primary purpose is to link an enquiry to a person and capture the context of the enquiry. While a full column list is not provided in the excerpt, the foreign key relationships reveal critical data points. The central column is PERSON_ID, which links the enquiry to a party in the Trading Community Architecture (HZ_PARTIES). Additional person-centric links include REGISTERING_PERSON_ID and PARTY_ID. The table captures the academic intent through INQ_ENTRY_LEVEL_ID (linked to entry levels) and INQ_ENTRY_STAT_ID (linked to entry statuses). It also stores metadata about the enquiry's origin via codes for the enquirer's educational goal (EDU_GOAL_ID), how they learned about the institution (HOW_KNOWUS_ID), and who influenced their decision (WHO_INFLUENCED_ID). Standard Oracle EBS columns like CREATION_DATE, LAST_UPDATE_DATE, CREATED_BY, and LAST_UPDATED_BY are also expected for auditing.

Common Use Cases and Queries

Primary use cases involve analyzing prospect engagement and the enquiry pipeline for reporting and operational follow-up. Common queries would join to person and code tables to produce meaningful reports. For instance, to generate a list of recent enquiries with person details and entry-level information, a query might join to HZ_PARTIES and the relevant code tables. Another typical scenario is tracking enquiry sources by joining on the HOW_KNOWUS_ID to analyze marketing campaign effectiveness. As the table is marked obsolete, direct operational use in new developments is discouraged; integration or data extraction for migration to a successor entity would be a more likely modern use case. Sample SQL to extract key enquiry data would follow this pattern:

  • SELECT enq.enquiry_id, hp.party_name, hp.email_address, ace.entry_level_code, stat.entry_stat_code, enq.creation_date
  • FROM igs.igs_in_enquiry_appl_all enq,
  • hz_parties hp,
  • igs_ad_i_entry_lvls ace,
  • igs_ad_i_entry_stats stat
  • WHERE enq.person_id = hp.party_id
  • AND enq.inq_entry_level_id = ace.entry_level_id(+)
  • AND enq.inq_entry_stat_id = stat.entry_stat_id(+)
  • AND enq.org_id = :p_org_id;

Related Objects

The table maintains defined foreign key relationships with several other entities, primarily within the IGS module and the Trading Community Architecture. These relationships are crucial for data integrity and constructing joins in reports.

  • HZ_PARTIES: Linked via PERSON_ID, REGISTERING_PERSON_ID, and PARTY_ID. This provides all demographic and contact information for the enquirer and related parties.
  • IGS_AD_CODE_CLASSES: Linked via EDU_GOAL_ID, HOW_KNOWUS_ID, and WHO_INFLUENCED_ID. This table stores the lookup codes for these specific classification types.
  • IGS_AD_I_ENTRY_LVLS: Linked via INQ_ENTRY_LEVEL_ID. This table defines the academic entry levels (e.g., Undergraduate, Graduate) the enquirer is interested in.
  • IGS_AD_I_ENTRY_STATS: Linked via INQ_ENTRY_STAT_ID. This table defines the possible entry statuses associated with the enquiry.