Search Results igr_i_appl_pk

Overview

The IGR_I_APPL_ALL table is a core data object within the Oracle E-Business Suite (EBS) Student System (IGS) module, specifically in versions 12.1.1 and 12.2.2. It serves as the master transactional table for storing records related to enquiry applications made to an educational institution. As documented, an enquiry application can be made at varying levels and for diverse information types, such as inquiries about a specific faculty, program, or accommodation. This table is fundamental to managing the prospective student or enquirer lifecycle before formal application or admission processes begin, acting as a system of record for initial contact and interest capture.

Key Information Stored

The table's structure is designed to capture comprehensive details about each enquiry. The primary key is a composite of PERSON_ID and ENQUIRY_APPL_NUMBER, uniquely identifying each enquiry record for an individual. Critical foreign key columns link this data to other central EBS entities. The PARTY_ID column references the HZ_PARTIES table in Oracle Trading Community Architecture (TCA), associating the enquiry with a standardized party record. The SALES_LEAD_ID column links to the AS_SALES_LEADS table in the Oracle CRM module, enabling integration between student enquiries and marketing or sales lead management processes. Additional columns, implied by the table's purpose, would typically store data such as enquiry date, information type requested, source of the enquiry, status, and the institution-specific context managed by the "_ALL" suffix convention.

Common Use Cases and Queries

This table is central to reporting and operational processes concerning prospective student engagement. Common use cases include generating enquiry source effectiveness reports, tracking conversion rates from enquiry to application, and managing communications with enquirers. A typical query might join IGR_I_APPL_ALL with HZ_PARTIES to create a list of enquirers with their contact details, filtered by a specific date range or information type. For example: SELECT hzp.party_name, iaa.enquiry_appl_number, iaa.creation_date FROM igs.igr_i_appl_all iaa, hz_parties hzp WHERE iaa.party_id = hzp.party_id AND iaa.creation_date > SYSDATE - 30;. Another critical pattern involves joining with AS_SALES_LEADS to analyze the lead pipeline originating from student enquiries.

Related Objects

• HZ_PARTIES: This is a foundational Trading Community Architecture table. The relationship is established via the foreign key from IGR_I_APPL_ALL.PARTY_ID to HZ_PARTIES.PARTY_ID. This join is essential for retrieving the enquirer's standardized name, contact information, and other party attributes.
• AS_SALES_LEADS: A table from the Oracle CRM module. The foreign key IGR_I_APPL_ALL.SALES_LEAD_ID references AS_SALES_LEADS, linking an institutional enquiry to a formal sales or marketing lead record for tracking and follow-up activities.
• IGR_I_APPL_PK: The primary key constraint on the composite columns (PERSON_ID, ENQUIRY_APPL_NUMBER), which ensures the uniqueness of each enquiry application record.