Search Results lower_enr_load_range




Overview
Explore in AI Chat

Overview

IGS_EN_ATD_TYPE_LOAD is a reporting view in the Oracle E-Business Suite (EBS) 12.1.1 and 12.2.2 environments, owned by the APPS schema and located within the Student Systems / Student Records product family (the IGS_ prefix denotes the Oracle Student System module). The view exposes attendance type and enrollment load configuration data, expressing the relationship between a calendar type, an attendance type, and the permitted enrollment load ranges defined for that combination.

Functionally, the view acts as a multi-tenant, organization-secured presentation layer over its base table. Its principal role is to deliver enrollment load range definitions to forms, concurrent programs, and integration interfaces while automatically filtering records by the organization context of the active session. The column frequently located by users, LOWER_ENR_LOAD_RANGE, represents the lower bound of the enrollment load range associated with a given attendance type. Together with its counterpart UPPER_ENR_LOAD_RANGE, it defines the band of enrollment load that maps to a specific attendance type for a given calendar type and organization.

Underlying Base Objects

The ETRM metadata documents the view as being defined over the table IGS_EN_ATD_TYPE_LOAD_ALL. This _ALL suffix follows the standard Oracle EBS multi-organization naming convention: the _ALL table stores records for every organization, while the view applies an organization filter so that the current session sees only rows matching its operating unit context.

The organization filter is implemented through the Oracle Application Object Library security mechanism. The view uses the USERENV('CLIENT_INFO') function to retrieve the organization identifier set by the EBS application when a session connects, decoding the first one or two characters of that information. The predicate compares the row's ORG_ID against this session value, and applies a default sentinel value of -99 when no organization context can be resolved. This construct is the classic "Org ID" row-level security pattern found in Oracle Applications views. No additional base objects beyond IGS_EN_ATD_TYPE_LOAD_ALL are documented in the ETRM metadata supplied.

Key Columns

  • ROW_ID – the ROWID of the underlying base-table row, exposed under the alias ROW_ID for use by Oracle Forms and other tools requiring a unique physical row identifier.
  • ORG_ID – the operating unit (organization) identifier that partitions the data; this column drives the security predicate applied by the view.
  • CAL_TYPE – the calendar type classification to which the attendance type and load range definition applies (for example, academic or teaching calendar categories).
  • ATTENDANCE_TYPE – the attendance type code (such as full-time or part-time) associated with the enrollment load band.
  • LOWER_ENR_LOAD_RANGE – the lower boundary of the enrollment load range, the column users most commonly search when defining or validating load thresholds.
  • UPPER_ENR_LOAD_RANGE – the upper boundary of the enrollment load range; together with the lower bound it defines the inclusive load band for the attendance type.
  • DEFAULT_EFTSU – the default effective full-time student units value associated with the attendance type and load configuration.
  • CREATED_BY, CREATION_DATE, LAST_UPDATED_BY, LAST_UPDATE_DATE, LAST_UPDATE_LOGIN – standard Oracle Applications audit columns recording who created and last modified each row and when.

Common Use Cases and Queries

The view is typically queried to inspect or validate enrollment load thresholds by organization, calendar type, and attendance type. A representative query retrieving the load ranges for a specific attendance type is:

SELECT cal_type, attendance_type, lower_enr_load_range, upper_enr_load_range, default_eftsu
FROM apps.igs_en_atd_type_load
WHERE attendance_type = :p_attendance_type
ORDER BY cal_type, lower_enr_load_range;

Because the view enforces organizational security through the session's client information, queries executed from within an EBS session automatically return only the rows for the current operating unit. Reports and interfaces that need to reconcile enrollment load bands with student enrollment records join this view to enrollment and attendance tables on the attendance type and calendar type. A further use case is configuration auditing: comparing lower and upper load range boundaries across attendance types to detect gaps or overlaps in the defined bands.

For integration and diagnostics, querying the view is often preferred over the base table because it mirrors exactly the rows that the application itself will see for a given organization, ensuring that the security predicate is honored consistently.