Search Results rule_waived_dt




Overview
Explore in AI Chat

Overview

IGS_AD_PS_APLINSTUNT_UNITHST_V is a views-layer object in the Oracle E-Business Suite (EBS) 12.1.1 and 12.2.2 releases, owned by the APPS schema and defined in the IGS (Student System / Student Records) product family. The object draws from the Admissions and Student Records domain, specifically the applicant-instance-unit history entity. Its name follows the IGS convention: "AD" denotes the Admissions functional area, "PS" the person/student set of entities, "APLINSTUNT" the applicant instance unit, and "UNITHST_V" indicates that the view presents unit history records — the historical, date-versioned state of units attached to an applicant's nominated course.

The view is designed to expose the most current or authoritative value of a given unit-history column through a coalescing pattern. Rather than returning a single stored column, several projected attributes are derived by testing the history table's value and, where null, falling back first to a PL/SQL lookup function and then to a related instance-unit record. This makes the view suitable for reporting, integration extracts, and downstream views that require a non-null, resolved unit-history attribute without implementing the fallback logic themselves.

Underlying Base Objects

The ETRM documentation for this object records no explicitly documented base tables, so the following is derived from the view text itself. The primary source is the applicant-instance-unit history table, aliased ACAIUH1 in the definition. Its columns carry the ADM PS applicant-instance-unit identifier (adm_ps_appl_inst_unit_id) as the key, together with person_id, admission_appl_number, nominated_course_cd, acai_sequence_number, and unit_cd, plus the history columns hist_start_dt, hist_end_dt, and hist_who.

A secondary source, aliased ACAIU1, supplies the instance-unit values used at the final level of each NVL chain. A third dependency is the PL/SQL package IGS_AU_GEN_001, and in particular its function audp_get_acaiuh_col, which is invoked for every resolved attribute. The function receives the attribute name as a literal, the record key, and hist_end_dt, and returns the history value as a string; character results are passed through SUBSTR(…,1,10) and numeric results through TO_NUMBER before use. The view therefore depends on IGS_AU_GEN_001 being valid and on the key columns of the underlying history and instance-unit tables being consistently populated.

Key Columns

  • person_id — the person (applicant) identifier; a principal join key for student and admissions reporting.
  • admission_appl_number, nominated_course_cd, acai_sequence_number, unit_cd — the composite context identifying the application, nominated course, application-instance sequence, and unit.
  • hist_start_dt, hist_end_dt, hist_who — history framing columns giving the effective start and end dates and the user who created the history row.
  • uv_version_number (sup_uv_version_number) — the searched column; resolves the unit-version number from the history row, then from audp_get_acaiuh_col, then from ACAIU1.
  • cal_type, ci_sequence_number, location_cd, unit_class, unit_mode — additional unit attributes projected through the same three-level fallback pattern.

Note that, because audp_get_acaiuh_col is called per row for several columns, the view is not partition-pruning or index-friendly for high-volume scans; a filter on person_id, admission_appl_number, and nominated_course_cd is strongly recommended.

Common Use Cases and Queries

The view is typically used to obtain resolved unit-history attributes for a person without reimplementing the fallback logic. A representative query retrieving the version number and unit classification for one applicant is:

  • SELECT person_id, admission_appl_number, nominated_course_cd, unit_cd, uv_version_number, unit_class, hist_start_dt, hist_end_dt FROM apps.igs_ad_ps_aplinstunt_unithst_v WHERE person_id = :p_person_id AND admission_appl_number = :p_appl_no;
  • Integration extracts commonly select the view into a staging table keyed on the composite application/unit columns for downstream comparison.
  • Reporting joins the view to course and unit reference views to present resolved unit mode, class, and location alongside admission details.

Because the documented metadata is limited, developers should confirm column-level data types on the target instance and verify that IGS_AU_GEN_001 is valid before relying on the derived columns in a production interface.