Search Results igs_ps_unit

Overview

The IGS_PS_UNIT table is a core master data object within the Oracle E-Business Suite Student System (IGS). It serves as the primary repository for the high-level definition of an academic unit offered by an institution. In this context, a "unit" typically represents a discrete subject, course, or module that forms part of a larger program of study (e.g., "Introduction to Economics 101"). The table stores the fundamental code and attributes that identify the unit, acting as a parent record for more detailed version-specific information. Its primary role is to establish a unique identifier for a unit, which is then referenced extensively across the student lifecycle for enrollment, fee assessment, program requirements, and academic planning.

Key Information Stored

While the provided ETRM excerpt does not list all columns, it definitively identifies the primary key. The central and most critical column is UNIT_CD, which is the unique code allocated to the university unit and serves as the table's primary key (IGS_PS_UNIT_PK). This code is the fundamental identifier used throughout the application to reference the unit. Based on standard patterns for master tables in the Student System, other columns likely include descriptive fields such as a title, an effective status indicator (e.g., ACTIVE, INACTIVE), and audit columns for who created the record and when. The table's structure is designed to ensure each unit has a single, unique identifier that persists across different versions or offerings of that unit over time.

Common Use Cases and Queries

This table is central to numerous academic and administrative processes. Common use cases include validating unit codes during student enrollment, defining program structures and prerequisites, and configuring fee schedules. Reporting often involves joining IGS_PS_UNIT to related tables to analyze unit offerings, enrollment trends, or financial data. A fundamental query pattern retrieves active units or validates a unit code's existence.

• Basic Unit Lookup: SELECT unit_cd FROM igs.igs_ps_unit WHERE unit_cd = '&UNIT_CODE';
• Joining to Version Details: A critical query joins to the related version table (IGS_PS_UNIT_VER_ALL) to get specific offering details like title and credit points: SELECT u.unit_cd, uv.version_number, uv.title FROM igs.igs_ps_unit u, igs.igs_ps_unit_ver_all uv WHERE u.unit_cd = uv.unit_cd AND u.unit_cd = 'MATH101';

Related Objects

The IGS_PS_UNIT table has extensive relationships, as evidenced by its foreign key constraints. It is a parent table to several key entities. The most direct relationship is with IGS_PS_UNIT_VER_ALL, which stores multiple versions (e.g., 2024-1, 2024-2) for a single unit code. Other critical dependencies include financial objects like IGS_FI_FEE_AS_RATE and IGS_FI_UNIT_FEE_TRG for fee assessment, and academic planning objects like IGS_PS_PAT_STUDY_UNT (study pattern units) and IGS_PE_UNT_REQUIRMNT (unit requirements). The table is also referenced in student progression (IGS_PR_STDNT_PR_UNIT) and personal unit exclusions (IGS_PE_PERS_UNT_EXCL), highlighting its integral role across the Student System's functional modules.