Search Results igs_as_sua_h_v




Overview
Explore in AI Chat

Overview

IGS_AS_SUA_H_V is a public APPS view within the IGS (Student System) product family of Oracle E-Business Suite, valid in both 12.1.1 and 12.2.2. Its purpose is to present a consolidated, time-sliced picture of a student's unit attempt by merging records from the student unit attempt history table (the historical, period-stamped snapshots of a row's values) with the corresponding current student unit attempt record. Each row in the view represents the full set of column values that applied to a given student unit attempt during a defined time period, extending forward to the present day. This makes the view the principal reporting and integration interface for anyone needing to reconstruct "what the record looked like then" versus "what it looks like now," and it is the object surfaced when users search for the ENROLLED_DT-related attribute commonly referenced in enrollment override discussions, including the term override_enrolled_cp.

Underlying Base Objects

The view text selects primarily from SUAH1, an alias for the student unit attempt history entity, with correlated fallback to SUA1, the current student unit attempt record. Although the ETRM metadata does not enumerate formal base objects, the SQL reveals these two drivers along with the following function dependencies:

  • IGS_AU_GEN_003.AUDP_GET_SUAH_COL — retrieves the historical value of a named column for a person, course, history end date, and unit offering option.
  • IGS_GE_DATE.IGSDATE — converts the retrieved string value into a valid date for the date-typed columns.

The pattern is a per-column NVL: if the history row carries a value, it is used; otherwise the function looks up the prior historical value, and finally the current SUA row supplies the value. This layering is what allows a single view to expose a continuous timeline without materialising a separate table.

h4>Key Columns

The projection is dominated by identifiers, versioning, and status/date pairs:

Common Use Cases and Queries

Typical scenarios include point-in-time enrollment audits, status-change trend analysis, and reconciliation feeds into downstream student records systems. A representative query reconstructing the enrollment timeline for a student is:

SELECT person_id, course_cd, unit_cd, version_number, hist_start_dt, hist_end_dt, enrolled_dt, unit_attempt_status, rule_waived_dt FROM apps.igs_as_sua_h_v WHERE person_id = :p_person_id AND course_cd = :p_course ORDER BY hist_start_dt;

Reporting tools frequently join this view to IGS_PS_STD_UNIT_ATTEMPT_ALL and IGS_EN_STDNT_ENROLMENTS_ALL on PERSON_ID and UNIT_CD to enrich the historical slice with current enrolments. Because the view invokes PL/SQL functions per row, performance tuning should favour restricted PERSON_ID or HIST_END_DT predicates over full scans.