Search Results get_per_addr_for_corr




Overview
Explore in AI Chat

Overview

IGS_AD_RESI_LETTER_V is a pre-built Oracle E-Business Suite view owned by the APPS schema and shipped as part of the Student System (IGS) product family, specifically the Admissions (AD) module. The view presents a consolidated, letter-generation-oriented rowset for residency evaluation letters. It joins party and person data from the Trading Community Architecture (TCA) layer with residency classification and evaluation records, and it exposes additional derived values through stored function calls. Its principal role is to provide the data source for correspondence templates and reports that notify applicants or students of their residency status determination. Because residency affects fee assessment, the view is also a convenient read-only source for downstream reporting and integration logic that needs a single flat structure combining demographic, address, and residency attributes.

Underlying Base Objects

The documented view text defines the query over HZ_PARTIES (aliased hz), joined to a residency details source (aliased rdv) that supplies RECORD attributes such as residency class and status, and to academic calendar/calendar-instance sources (aliased aa and ci) that supply the academic calendar type and sequence. A persistent identifier group is referenced via the alias Persid. The ETRM metadata documents no referenced base objects, so the authoritative column lineage must be read from the view text itself. Notably, the view does not derive WH_UPDATE_DATE from a table; it projects TO_DATE(NULL) for that column, and it obtains the correspondence address and residency descriptive flexfield (DFF) values by calling functions in the IGS_CO_GEN_003 package rather than by direct joins.

Key Columns

Common Use Cases and Queries

The view is typically consumed by BI Publisher letter templates and by concurrent programs that print residency notification letters, filtered by residency class, status, or evaluation date. It is equally useful for ad hoc institutional reporting on residency determinations. The function call for correspondence address is the element that distinguishes this view from generic party views; reports use it to print the correct mailing address for the letter recipient.

  • Letter generation: SELECT party_id, party_name, residency_class_desc, residency_status_desc, evaluation_date FROM apps.igs_ad_resi_letter_v WHERE residency_class_cd = :p_class AND evaluation_date >= :p_from_date;
  • Correspondence detail: SELECT party_number, person_first_name, person_last_name, Igs_co_gen_003.get_per_addr_for_corr(party_id) corr_addr FROM apps.igs_ad_resi_letter_v WHERE party_id = :p_party_id;
  • Residency reporting: SELECT resid_cal_type, acad_cal_type, COUNT(*) FROM apps.igs_ad_resi_letter_v GROUP BY resid_cal_type, acad_cal_type;

Because the view performs function calls per row, queries should be filtered narrowly to avoid performance degradation on large party populations.