Search Results inq_unit_set_code




Overview
Explore in AI Chat

Overview

The IGS_AD_INQ_UNIT_SETS table is a core reference table within the Oracle E-Business Suite (EBS) 12.1.1 and 12.2.2, specifically for the IGS (Oracle Student Management) product family. It functions as a master repository for inquiry unit set codes. In the context of student administration, a unit set typically refers to a collection or grouping of academic units (courses or subjects). This table stores the valid codes and definitions for these groupings as they pertain to the inquiry process, which is often a preliminary stage in the student admissions lifecycle. Its primary role is to ensure data integrity and provide a controlled list of unit set codes that can be associated with prospective student inquiries, enabling consistent reporting and process flows within the admissions module.

Key Information Stored

The table's structure is designed to store both the code definitions and standard audit information. The key columns are:

  • INQ_UNIT_SET_CODE_ID: A system-generated, unique numeric identifier serving as the primary key for the record.
  • INQ_UNIT_SET_CODE: A unique 30-character alphanumeric code that identifies the specific inquiry unit set, as referenced by the user's search term.
  • DESCRIPTION: A 240-character text field providing the full name or explanation of the inquiry unit set code.
  • CLOSED_IND: A flag indicating whether the code is active or closed for further use, supporting data retention without active application.
  • Standard WHO Columns (CREATED_BY, CREATION_DATE, LAST_UPDATED_BY, LAST_UPDATE_DATE, LAST_UPDATE_LOGIN): These columns track the user and timestamp for the creation and last update of each row, adhering to Oracle EBS auditing standards.

Common Use Cases and Queries

This table is primarily used in two contexts: maintenance and reference. Administrators use front-end forms to maintain the list of valid codes. For reporting and data extraction, common SQL patterns include fetching all active codes for a dropdown list in a custom inquiry form or report. A typical query to retrieve all active inquiry unit set codes would be:

SELECT INQ_UNIT_SET_CODE, DESCRIPTION
FROM IGS.IGS_AD_INQ_UNIT_SETS
WHERE NVL(CLOSED_IND, 'N') = 'N'
ORDER BY INQ_UNIT_SET_CODE;

Another common use case is to join this table with other inquiry-related transactional tables (not listed in the provided dependencies but logically inferred) to generate reports analyzing prospective student interests by academic unit set. The unique indexes on INQ_UNIT_SET_CODE_ID and INQ_UNIT_SET_CODE ensure performance and integrity for these lookups.

Related Objects

Based on the provided ETRM metadata, the direct dependency information is limited. The documentation states that the table "IGS.IGS_AD_INQ_UNIT_SETS is referenced by" an object named "IGS_AD_INQ_UNIT_SETS" within the APPS schema. This strongly indicates the existence of a public synonym (APPS.IGS_AD_INQ_UNIT_SETS) pointing to this IGS-owned table, which is a standard EBS architecture practice for granting access. Furthermore, it implies the existence of at least one database object, such as a view, package, or trigger, that references this table to enforce business logic or present data. In a full IGS implementation, one would expect this table to be referenced by transactional tables storing individual student inquiry records, where the INQ_UNIT_SET_CODE would serve as a foreign key.