Search Results igr_is_i_lines_n1

Overview

The IGS.IGR_IS_I_LINES table is a core data structure within the Oracle E-Business Suite (EBS) 12.1.1 and 12.2.2, specifically for the Institutional Grants and Research (IGS) product family. Its documented purpose is to store academic interests for the Self Service Inquiry functionality. This table acts as a detail or line-level table, capturing specific program, unit set, or product category preferences associated with a broader inquiry instance. It is integral to managing prospective student or applicant interest data captured through self-service channels, enabling institutions to track and analyze academic program inquiries.

Key Information Stored

The table's primary key is INQ_LINES_ID, a system-generated sequence number uniquely identifying each interest line. The INQ_INQ_ID column links the line to its parent inquiry header. The PREFERENCE column allows for ranking multiple interests. Notably, the INQ_PROG_CODE_ID and INQ_UNIT_SET_CODE_ID columns are documented as obsolete, indicating a potential data model evolution where academic interests are now primarily defined using the Inventory module's product categories. The PRODUCT_CATEGORY_ID and PRODUCT_CATEGORY_SET_ID columns form a foreign key relationship to the Inventory tables (MTL_CATEGORIES_B, MTL_CATEGORY_SETS_B), representing the modern method for classifying academic programs or areas of interest. Standard WHO columns (CREATED_BY, CREATION_DATE, etc.) and concurrent program tracking columns (REQUEST_ID, PROGRAM_ID, etc.) are also present for audit and processing control.

Common Use Cases and Queries

A primary use case is reporting on inquiry trends by academic interest. Analysts can join this table to the parent inquiry header and Inventory category tables to determine which programs or product categories are generating the most prospective interest. Another critical use is data validation and cleanup, particularly for the obsolete columns. Common SQL patterns include retrieving all interest lines for a specific inquiry or summarizing preferences by category.

• Retrieve interest lines for a specific inquiry: SELECT * FROM igs.igr_is_i_lines WHERE inq_inq_id = <inquiry_id> ORDER BY preference;
• Join to Inventory categories to report on interests: SELECT i.inq_inq_id, i.preference, cat.concatenated_segments FROM igs.igr_is_i_lines i, mtl_categories_kfv cat WHERE i.product_category_id = cat.category_id;
• Identify records still using obsolete program codes: SELECT inq_lines_id FROM igs.igr_is_i_lines WHERE inq_prog_code_id IS NOT NULL;

Related Objects

The IGR_IS_I_LINES table has defined relationships with several other EBS objects, primarily through foreign key constraints. Its primary key (INQ_LINES_ID) is enforced by the unique index IGR_IS_I_LINES_PK. The table references external Inventory master data to resolve product category information.

• Primary Key: IGR_IS_I_LINES_PK index on column INQ_LINES_ID.
• Foreign Keys (Referencing):
  • PRODUCT_CATEGORY_ID → MTL_CATEGORIES_B.CATEGORY_ID
  • PRODUCT_CATEGORY_SET_ID → MTL_CATEGORY_SETS_B.CATEGORY_SET_ID
  • INQ_INQ_ID → [Parent Inquiry Header Table] (The specific parent table name is not fully documented in the provided excerpt, but the relationship is indicated.)
• Non-Unique Indexes: Several indexes (IGR_IS_I_LINES_N1 to N4) exist on foreign key columns (INQ_INQ_ID, INQ_PROG_CODE_ID, INQ_UNIT_SET_CODE_ID, PRODUCT_CATEGORY_ID) to optimize join performance.