Search Results info_type_id




Overview
Explore in AI Chat

Overview

The IGS.IGR_I_A_ITYPE table is a core data structure within the Oracle E-Business Suite (EBS) 12.1.1 and 12.2.2, specifically belonging to the IGS (iGrants) product family. Its primary function is to manage and store the association between an individual's enquiry or application and the specific types of information requested as part of that process. The table acts as a junction or intersection entity, linking an enquiry to one or more information types. This design enables the system to track precisely what data or documentation is required for a given application, supporting structured data collection and workflow management in modules related to student admissions, grants, or other enquiry-based processes.

Key Information Stored

The table's columns are designed to establish this critical link and maintain standard audit trails. The key data elements stored are:

  • PERSON_ID (NUMBER): A unique identifier for the person who submitted the enquiry or application.
  • ENQUIRY_APPL_NUMBER (NUMBER): A number that uniquely identifies the specific enquiry or application made by the person.
  • INFO_TYPE_ID (NUMBER): A foreign key that links to a package item table, defining the specific type of information (e.g., transcript, reference letter, test score) requested for the associated enquiry. This is the column central to the user's search.
  • Standard WHO Columns (CREATED_BY, CREATION_DATE, LAST_UPDATED_BY, LAST_UPDATE_DATE, LAST_UPDATE_LOGIN): These mandatory audit columns track the user and timestamp for the creation and last update of each record, adhering to Oracle EBS conventions.

The primary key (IGR_I_A_ITYPE_PK) is a composite key on PERSON_ID, ENQUIRY_APPL_NUMBER, and INFO_TYPE_ID, ensuring a unique combination of person, application, and information type. A non-unique index (IGR_I_A_ITYPE_N1) on INFO_TYPE_ID facilitates efficient queries to find all enquiries requesting a particular type of information.

Common Use Cases and Queries

This table is essential for reporting and operational processes related to application completeness and data requests. A common use case is generating a checklist of pending information items for a specific applicant or for all applicants to a particular program. Administrators can query this table to determine what supplementary materials are outstanding. A typical reporting query would join this table to person and enquiry header tables to produce a meaningful list.

Sample Query: Retrieve all information types requested for a specific application.

SELECT it.info_type_id, pit.item_description -- Assuming pit is the package item table
FROM igs.igr_i_a_itype it
JOIN <package_item_table> pit ON it.info_type_id = pit.item_id
WHERE it.person_id = 12345
AND it.enquiry_appl_number = 1001;

Sample Query: Find all applications that require a specific information type (e.g., INFO_TYPE_ID = 505).

SELECT it.person_id, it.enquiry_appl_number, e.enquiry_date
FROM igs.igr_i_a_itype it
JOIN igs.igr_i_enquiry e ON it.person_id = e.person_id AND it.enquiry_appl_number = e.enquiry_appl_number
WHERE it.info_type_id = 505;

Related Objects

Based on the provided metadata, the table's primary relationships are inferred through foreign keys. The INFO_TYPE_ID column is documented as a foreign key to a Package Item table (exact name not specified in the excerpt), which is the master reference for valid information types. The PERSON_ID and ENQUIRY_APPL_NUMBER columns logically foreign key to a core enquiry or application header table, such as IGR_I_ENQUIRY, to obtain details about the applicant and the enquiry itself. The dependency information shows the table is referenced by an APPS synonym named IGR_I_A_ITYPE, which is the standard access point for all application code within the EBS environment, ensuring a consistent public interface. Direct references from other tables or views are not listed in the provided excerpt.