Search Results igs_rc_is_i_lines_pk




Overview

The table IGS_RC_IS_I_LINES is a core data object within the Oracle E-Business Suite Student System (IGS). It functions as a detail table designed to store specific academic interests submitted by prospective students or other inquirers through the Self Service Inquiry functionality. Its primary role is to capture and persist the detailed program or unit set preferences associated with a broader inquiry, enabling institutions to track and analyze prospective student interests for recruitment, advising, and program planning purposes. The table is integral to the inquiry management workflow within the Student System.

Key Information Stored

While the full column list is not detailed in the provided metadata, the documented foreign key relationships and primary key define its critical structure. The central identifier is INQ_LINES_ID, which serves as the primary key for each unique interest line. Each record is linked to a parent inquiry via the INQ_INQ_ID foreign key, associating the interest with a specific inquiry session or applicant. The substantive academic data is stored through references to the AS_INTEREST_CODES_B table: INQ_PROG_CODE_ID links to a specific program of interest, and INQ_UNIT_SET_CODE_ID links to a specific unit set or course of study interest. This design allows a single inquiry to contain multiple lines detailing various academic interests.

Common Use Cases and Queries

A primary use case is generating reports on inquiry trends by academic program or unit set. Administrators can analyze which programs attract the most inquiries to inform marketing efforts. Another key scenario is during the inquiry-to-application conversion process, where captured interests can pre-populate application forms or guide admissions counselor interactions. A typical query would join this table to the parent inquiry and interest code descriptions to produce a readable report.

SELECT i.inq_inq_id,
       ic_prog.meaning AS program_interest,
       ic_uset.meaning AS unit_set_interest
FROM igs_rc_is_i_lines i,
     as_interest_codes_b ic_prog,
     as_interest_codes_b ic_uset
WHERE i.inq_prog_code_id = ic_prog.interest_code_id(+)
AND   i.inq_unit_set_code_id = ic_uset.interest_code_id(+)
AND   i.inq_inq_id = :p_inquiry_id;

Related Objects

The table maintains defined relationships with several key objects, primarily through foreign key constraints. The central relationship is with the parent inquiry header table, IGS_RC_IS_INQUIRY, via the column INQ_INQ_ID. For resolving the academic interest codes, it references the AS_INTEREST_CODES_B table twice: once for program interests (INQ_PROG_CODE_ID) and once for unit set interests (INQ_UNIT_SET_CODE_ID). This structure indicates that IGS_RC_IS_I_LINES is a child table dependent on IGS_RC_IS_INQUIRY and relies on AS_INTEREST_CODES_B for its validated code values.

  • Primary Key: IGS_RC_IS_I_LINES_PK (Column: INQ_LINES_ID)
  • Foreign Key (to IGS_RC_IS_INQUIRY): IGS_RC_IS_I_LINES.INQ_INQ_ID → IGS_RC_IS_INQUIRY
  • Foreign Key (to AS_INTEREST_CODES_B for Program): IGS_RC_IS_I_LINES.INQ_PROG_CODE_ID → AS_INTEREST_CODES_B
  • Foreign Key (to AS_INTEREST_CODES_B for Unit Set): IGS_RC_IS_I_LINES.INQ_UNIT_SET_CODE_ID → AS_INTEREST_CODES_B