Search Results igs_rc_i_appl_all




Overview
Explore in AI Chat

Overview

The table IGS_RC_I_APPL_ALL is a core data object within the Oracle E-Business Suite (EBS) Student System (IGS), specifically in the Recruitment module. It serves as the master table for storing records of enquiry applications made to an educational institution. An enquiry application represents a prospective student's formal request for information, which can vary in scope and detail—from general institutional information to specific queries about a faculty, program, or ancillary services like accommodation. As an "_ALL" table, it is designed to support a multi-org architecture, meaning it contains data for multiple operating units and requires a security predicate (typically using ORG_ID) for correct querying in a multi-org environment. Its primary role is to track the initial point of contact in the student recruitment lifecycle, linking a person's interest to subsequent application and admission processes.

Key Information Stored

The table's structure is centered on identifying the enquirer and the nature of their enquiry. The primary key is a composite of PERSON_ID and ENQUIRY_APPL_NUMBER, uniquely identifying each enquiry record for an individual. Key descriptive columns include various foreign key references that categorize the enquiry. These include EDU_GOAL_ID, HOW_KNOWUS_ID, and WHO_INFLUENCED_ID, which link to code lookup tables (IGS_AD_CODE_CLASSES) to standardize data on educational goals, referral sources, and influencers. Critical academic context is stored via INQ_ENTRY_LEVEL_ID (linking to IGS_RC_I_ENTRY_LVLS) and admission/ academic calendar identifiers (ADM_CAL_TYPE, ADM_CI_SEQUENCE_NUMBER, ACAD_CAL_TYPE, ACAD_CI_SEQUENCE_NUMBER linking to IGS_CA_INST_REL). The table also integrates with the Oracle Trading Community Architecture (TCA) via PARTY_ID and PERSON_ID links to HZ_PARTIES, and with the CRM module via SALES_LEAD_ID linked to AS_SALES_LEADS.

Common Use Cases and Queries

This table is fundamental for recruitment analytics and operational reporting. Common use cases include analyzing enquiry sources to measure marketing campaign effectiveness, tracking conversion rates from enquiry to formal application, and managing prospect communications. A typical query might join to TCA to retrieve prospect details and to code lookup tables to categorize enquiries. For example, to generate a list of enquiries for a specific academic intake, one might query: SELECT appl.person_id, appl.enquiry_appl_number, parties.party_name, levels.entry_level_code FROM igs_rc_i_appl_all appl JOIN hz_parties parties ON appl.person_id = parties.party_id JOIN igs_rc_i_entry_lvls levels ON appl.inq_entry_level_id = levels.entry_level_id WHERE appl.adm_cal_type = '&ADM_CAL_TYPE' AND appl.adm_ci_sequence_number = &CI_SEQ_NUM; Data from this table often feeds reports on enquiry volumes, prospect demographics, and lead quality assessment.

Related Objects

Based on the provided foreign key metadata, IGS_RC_I_APPL_ALL has extensive relationships with other EBS objects:

  • Parent Tables (Foreign Key References):
    • IGS_AD_CODE_CLASSES: For lookup values (EDU_GOAL_ID, HOW_KNOWUS_ID, WHO_INFLUENCED_ID).
    • IGS_RC_I_ENTRY_LVLS: For the enquiry's intended entry level (INQ_ENTRY_LEVEL_ID).
    • IGS_CA_INST_REL: For academic calendar instances (ADM_CAL_TYPE, ADM_CI_SEQUENCE_NUMBER, ACAD_CAL_TYPE, ACAD_CI_SEQUENCE_NUMBER).
    • HZ_PARTIES: For person/party information (PERSON_ID, REGISTERING_PERSON_ID, PARTY_ID).
    • AS_SALES_LEADS: For integrated CRM lead management (SALES_LEAD_ID).
  • Child Tables (Referenced by):

These relationships position IGS_RC_I_APPL_ALL as a central hub connecting recruitment activities to foundational EBS modules like TCA, Calendar, and CRM.