Search Results igs_au_gen_003




Overview
Explore in AI Chat

Overview

The view APPS.IGS_AS_SUA_H_V belongs to the Oracle E-Business Suite Student Systems (IGS) product family, specifically the Student Unit Attempt (SUA) area of the Advanced Standing and student records module. It exposes the historical (versioned) record of a student's unit attempt — the enrollment of a person into a course unit within a teaching period. The suffix _H_V denotes a historical view, in which each row carries HIST_START_DT and HIST_END_DT columns that describe the effective dating of the record, enabling point-in-time reporting of a student's unit attempt status.

Its principal architectural characteristic is that it is not a simple projection of a single table. The view text shows a layered resolution strategy: for each column, it first attempts to read the value held on the historical row (SUAH1), and where that is null it falls back to the call to Igs_Au_Gen_003.audp_get_suah_col, and finally to the current record in SUA1. Because this view references the package function Igs_Au_Gen_003, users searching for that identifier are typically investigating how the view derives columns that are not physically stored on the history row. In Oracle EBS 12.1.1 and 12.2.2 the view resides in the APPS schema and is queried by the Student/Advanced Standing forms, concurrent programs, and reporting extracts.

Underlying Base Objects

The ETRM metadata for this object documents no explicitly listed base tables; the referenced objects must be read from the view text itself. The aliases used are:

  • SUAH1 — the Student Unit Attempt history table (IGS_AS_SUA_H or its equivalent historical entity), supplying the primary historical columns such as person_id, course_cd, unit_cd, cal_type, ci_sequence_number, hist_start_dt, hist_end_dt, hist_who, uoo_id and dcnt_reason_cd.
  • SUA1 — the current Student Unit Attempt record, used as the fallback source for values not retained on the history row.
  • Igs_Au_Gen_003.audp_get_suah_col — a packaged function that resolves a named column value for a given person_id, course_cd, hist_end_dt and uoo_id. It sits between the history row and the current row in the resolution chain.
  • IGS_GE_DATE.IGSDATE — a date conversion utility used to convert the string returned by the package function into a proper date value.
  • hz.party_number — the trading community party number, joined from the HZ party model for the person.

The package call is the reason this view cannot be treated as a static snapshot; it performs runtime lookups, which has performance implications for large extracts.

Key Columns

Common Use Cases and Queries

Typical usage is retrospective reporting on a student's unit attempt at a given point in time, and reconciliation of history rows against current records. A representative query:

  • SELECT person_id, course_cd, unit_cd, version_number, hist_start_dt, hist_end_dt, unit_attempt_status FROM apps.igs_as_sua_h_v WHERE person_id = :p_person AND hist_end_dt >= :p_effective_date;
  • Point-in-time audit: filter by HIST_START_DT <= :as_at and HIST_END_DT >= :as_at to reconstruct the record as it stood on that date.
  • Investigating the igs_au_gen_003 dependency: compare NVL-resolved columns against the underlying history and current tables to determine which layer supplied each value.

Because each row invokes packaged PL/SQL, extracts should restrict the driving set with PERSON_ID, COURSE_CD or date predicates before projecting the derived columns.