Search Results igs_ps_pat_study_unt_n1

Overview

The IGS_PS_PAT_STUDY_UNT table is a core entity within the Oracle E-Business Suite (EBS) 12.1.1 and 12.2.2 Student Management (Campus Solutions) module. It defines the specific academic units (subjects) that constitute a pattern of study for a given period within a program. A pattern of study is a predefined academic plan, and this table details the unit enrollments planned for each period (e.g., semester) of that pattern. Crucially, as noted in the ETRM, this entity describes a logical relationship to a unit and has no direct physical link to a specific unit offering instance. This design accommodates incomplete data scenarios, such as when a calendar instance is not yet defined, allowing for the planning of academic structures ahead of operational scheduling.

Key Information Stored

The table stores the structural details of planned unit enrollments within an academic pattern. Its primary key is a composite of identifiers linking it to the parent pattern period: COURSE_CD, VERSION_NUMBER, CAL_TYPE, POS_SEQUENCE_NUMBER, and POSP_SEQUENCE_NUMBER, with SEQUENCE_NUMBER uniquely identifying each unit row within that period. The core academic data includes UNIT_CD, which specifies the unit code for pre-enrollment. The UNIT_LOCATION_CD field is critical for operational scheduling, as it indicates the preferred location for the unit offering to be used during the pre-enrollment process. The UNIT_CLASS column defines the class type (e.g., lecture, tutorial) for the planned unit. These columns are supported by non-unique indexes (IGS_PS_PAT_STUDY_UNT_N1, N2, N3) to optimize queries filtering on unit class, location, and code, respectively.

Common Use Cases and Queries

A primary use case is the generation of pre-enrollment recommendations for students following a specific study pattern. Administrators or batch processes query this table to determine which units a cohort should be enrolled in for an upcoming academic period. The UNIT_LOCATION_CD is particularly significant in this context; when specified, the pre-enrollment engine uses it to select the correct unit offering option from available schedules. A typical reporting query would join this table to its parent pattern and unit master to list all planned units.

• Sample Query: Retrieving all units for a specific program pattern period, including location.
  SELECT unt.unit_cd, unt.unit_location_cd, unt.unit_class, unt.sequence_number
FROM igs.igs_ps_pat_study_unt unt
WHERE unt.course_cd = 'BSC001'
AND unt.version_number = 1
AND unt.cal_type = 'SEMESTER'
AND unt.pos_sequence_number = 1
AND unt.posp_sequence_number = 1
ORDER BY unt.sequence_number;

Related Objects

The IGS_PS_PAT_STUDY_UNT table sits within a well-defined hierarchy and has established foreign key relationships, as documented in the ETRM metadata.

• Parent Table: IGS_PS_PAT_STUDY_PRD, referenced via (COURSE_CD, VERSION_NUMBER, CAL_TYPE, POS_SEQUENCE_NUMBER, POSP_SEQUENCE_NUMBER). This defines the pattern of study period to which these units belong.
• Reference Tables:
  • IGS_PS_UNIT: Referenced via UNIT_CD. This provides the master definition and validation for the academic unit code.
  • IGS_AD_LOCATION_ALL: Referenced via UNIT_LOCATION_CD. This validates and provides details for the specified campus or delivery location.
  • IGS_AS_UNIT_CLASS_ALL: Referenced via UNIT_CLASS. This validates the class type associated with the planned unit.