Search Results second_percentage

Overview

The IGS_ST_UNT_LOAD_APPO table is a core data object within the Oracle E-Business Suite (EBS) Student Management System, specifically under the IGS (iGrants) schema. Its primary function is to store detailed rules for apportioning the academic load of a specific unit of study across different teaching periods within a defined load calendar. This table enables precise control over how a unit's contribution to a student's full-time equivalent (FTE) load is distributed. For instance, it can define that 75% of a unit's load is attributed to Semester 1 and 25% to Semester 2, overriding any standard apportionment rules. This granular management is critical for accurate government reporting, funding calculations, and academic planning in institutions with complex teaching calendars.

Key Information Stored

The table's structure is designed to uniquely identify a unit, its version, and the teaching and load calendar context, then record the apportionment percentages. Key columns include:

• DLA_CAL_TYPE & CI_SEQUENCE_NUMBER: Together, these identify the specific load calendar instance (e.g., "ACADEMIC_YEAR", instance 2024) to which the load is being contributed.
• UNIT_CD & VERSION_NUMBER: Identify the precise unit and its version for which the load apportionment is defined.
• TEACH_CAL_TYPE: The teaching calendar (e.g., "SEMESTER_1") within which the specified percentage applies.
• PERCENTAGE: The primary proportion of the unit's load (as a percentage) contributed to the load calendar instance identified by DLA_CAL_TYPE and CI_SEQUENCE_NUMBER for this teaching period.
• SECOND_PERCENTAGE: Used in scenarios where a single teaching period relates to two instances of the same load calendar type, storing the percentage for the second instance.

The unique index (IGS_ST_UNT_LOAD_APPO_U1) enforces that the combination of these five identifier columns is unique, preventing duplicate apportionment rules.

Common Use Cases and Queries

A primary use case is generating reports for regulatory compliance, where the institution must demonstrate how student load is distributed across defined reporting periods. Administrators may also query this table to audit or override standard load calculations for specific units. A common query pattern involves joining to the unit offering and default load apportionment tables to see unit-specific rules against defaults. For example, to find all load apportionments for a specific load calendar type (such as one referenced by the user's search term "dla_cal_type"):

• SELECT unit_cd, version_number, teach_cal_type, percentage
  FROM igs.igs_st_unt_load_appo
  WHERE dla_cal_type = :p_load_cal_type
  AND ci_sequence_number = :p_sequence_num
  ORDER BY unit_cd, teach_cal_type;

Another critical reporting use case is calculating the total effective load for a unit across all related teaching periods by summing the PERCENTAGE values for a given UNIT_CD, VERSION_NUMBER, DLA_CAL_TYPE, and CI_SEQUENCE_NUMBER.

Related Objects

The IGS_ST_UNT_LOAD_APPO table is centrally linked within the load apportionment and unit definition structures. As per the provided metadata, its documented foreign key relationships are:

• References IGS_ST_DFT_LOAD_APPO via DLA_CAL_TYPE: This links the unit-specific apportionment rule to a broader default load apportionment definition for a calendar type, ensuring the unit rule exists within a valid overarching load calendar framework.
• References IGS_PS_UNIT_OFR via UNIT_CD: This ensures that any unit code with a defined load apportionment is a valid, offered unit within the system, maintaining referential integrity with the unit catalog.

The table's primary key (IGS_ST_UNT_LOAD_APPO_PK) is itself referenced by other application objects (not listed in the excerpt but implied by its status) such as forms, reports, and PL/SQL APIs that create, update, or delete unit load apportionment data.