Search Results effective_start_dt




Overview
Explore in AI Chat

Overview

The IGS_PS_ANL_LOAD_U_LN table is a data entity within the Oracle E-Business Suite Student System (IGS), now marked as obsolete. Its core function is to establish a relationship between an academic unit and an annual load figure for the purpose of calculating Equivalent Full-Time Student Unit (EFTSU) values. This linkage is essential for workload and funding calculations in higher education institutions. For instance, a specific unit version (e.g., "Introduction to Physics 101") can be associated with the standard annual load defined for the first year of a particular program version, thereby determining its proportional contribution to a student's yearly load. The table's design indicates it is a child entity, storing detailed unit-level assignments that roll up to a parent annual load definition.

Key Information Stored

The table's structure centers on identifying both the parent annual load and the specific unit being linked. Its primary key is a composite of columns that uniquely identify each association. The critical columns are the foreign key components referencing the parent annual load—COURSE_CD (program code), CRV_VERSION_NUMBER (program version), YR_NUM (the program year number), and EFFECTIVE_START_DT (the load's effective date)—and the columns identifying the unit: UNIT_CD (unit code) and UV_VERSION_NUMBER (unit version). A crucial piece of implementation metadata states this table was "Not implemented in this database," suggesting it may exist in the data dictionary as a definition but was not populated or actively used in standard deployments of the referenced EBS versions.

Common Use Cases and Queries

The primary use case is generating reports or feeding calculations for student load, funding, and enrollment reporting based on EFTSU. A typical query would join this table to the unit and annual load master tables to list all units associated with a program's annual load. For example, to audit units linked to the first year of a specific program version, one might use a SQL pattern such as:

  • SELECT alul.unit_cd, alul.uv_version_number, al.course_cd, al.yr_num FROM igs_ps_anl_load_u_ln alul JOIN igs_ps_anl_load al ON alul.course_cd = al.course_cd AND alul.crv_version_number = al.crv_version_number AND alul.yr_num = al.yr_num AND alul.effective_start_dt = al.effective_start_dt WHERE al.course_cd = 'BSC-CHEM' AND al.yr_num = 1;

Given its "not implemented" status, operational use in EBS 12.1.1 or 12.2.2 is unlikely. Its main utility would be for reference during data analysis or system customization to understand the intended data model for load calculation.

Related Objects

This table has defined foreign key relationships with two core master tables in the Student System, as per the provided metadata:

  • IGS_PS_ANL_LOAD: This is the parent table defining the annual load figure. The join is performed on the composite key: (COURSE_CD, CRV_VERSION_NUMBER, YR_NUM, EFFECTIVE_START_DT).
  • IGS_PS_UNIT_VER_ALL: This table stores version-specific details for academic units. The relationship is established via the unit's identifying columns: (UNIT_CD, UV_VERSION_NUMBER).

These relationships position IGS_PS_ANL_LOAD_U_LN as a junction table that resolves the many-to-many relationship between annual load definitions and unit versions.