Results for “igs_ad_appl_admappl_v”

AI-generated from documented ETRM metadata — verify critical details on the linked pages.

Overview

IGS_AD_APPL_ADMAPPL_V is a read-only database view owned by the APPS schema in the Oracle E-Business Suite Release 12.1.1 and 12.2.2 environments. It belongs to the IGS product family, commonly known as the Oracle Student System (formerly Oracle Student Administration), and specifically supports the Admissions module within that suite. The view is reported as VALID in the data dictionary and is intended purely for query, reporting, and integration access; no DML is supported because the object is a view derived from underlying base tables.

The principal function of this view is to present a reporting-friendly projection of admissions application data. It is defined as a view of the IGS_AD_APPL_ALL table, meaning the base application records originate from that table. However, the view does not simply reproduce the base table. It enriches each application row with joined data from the person/party model and from the calendar instance infrastructure, translating internal identifiers into human-readable alternate codes and supplying the start and end dates of the relevant calendar instances. This makes the view considerably more useful for operational reporting than the bare base table, because consumers can avoid writing the joins themselves.

Because both the academic calendar instance and the admission calendar instance are resolved within the view, it supports the dual-calendar logic that characterises admissions processing in the Student System. The combination of these two calendars defines the commencement period against which an application is assessed.

Underlying Base Objects

The ETRM metadata documents the view as being defined over IGS_AD_APPL_ALL, the core admissions application entity. The view text also references the person/party tables through joins on PERSON_ID and PARTY_NUMBER, and the calendar instance infrastructure twice (aliased CI1 and CI2) to resolve the academic and admission calendar instances respectively. Lookup values are drawn from the standard lookup mechanism to derive the admission process type description, and special group attributes are resolved against IGS_AD_CODE_CLASSES for classes SPECIAL_GROUP1 and SPECIAL_GROUP2. The documented metadata lists no formally enumerated base objects beyond IGS_AD_APPL_ALL, so the remaining references should be treated as implementation detail confirmed by the view text rather than as guaranteed documented dependencies.

Key Columns

• ROW_ID, PERSON_ID, PERSON_NUMBER — surrogate row identifier, internal person identifier, and the party number for the applicant.
• DSP_CONTEXT_BLOCK_NAME — a concatenated display name built from last name, title, and known-as or first name.
• ADMISSION_APPL_NUMBER, APPL_DT — the admissions application number and its submission date.
• ACAD_CAL_TYPE, ACAD_CI_SEQUENCE_NUMBER, ACAD_ALTERNATE_CODE, ACAD_CI_START_DT, ACAD_CI_END_DT — the academic calendar instance details.
• ADM_CAL_TYPE, ADM_CI_SEQUENCE_NUMBER, ADM_ALTERNATE_CODE, ADM_CI_START_DT, ADM_CI_END_DT — the admission calendar instance details.
• ADMISSION_CAT, S_ADMISSION_PROCESS_TYPE, ADM_PRC_TYPE_DESC — admission category, process type code, and its decoded meaning.
• ADM_APPL_STATUS, ADM_FEE_STATUS — application and fee status, each also exposed with a _DISPLAY alias.
• COMMENCEMENT_PERIOD, ADMISSION_PROCESS_CAT — concatenated derivations combining academic and admission alternate codes, and admission category with process meaning.
• TAC_APPL_IND, COMMON_APP — TAC application indicator and common application flag.
• SPCL_GRP_1 / SPCL_GRP_2 and their _NAME and _DESC companions — special group codes resolved against IGS_AD_CODE_CLASSES.

Common Use Cases and Queries

Typical consumers include admissions dashboards, applicant tracking extracts, and integration interfaces that must present calendar context without resolving foreign keys. A representative query retrieving applicant identity and admission calendar context is:

SELECT person_number, dsp_context_block_name, admission_appl_number, appl_dt, adm_alternate_code, adm_ci_start_dt, adm_ci_end_dt, adm_prc_type_desc, adm_apply_status_display FROM igs_ad_appl_admappl_v WHERE adm_cal_type = :p_cal_type AND adm_ci_sequence_number = :p_ci_seq;

Filtering by commencement period is equally common, for example WHERE commencement_period = :p_period, and special group analysis can be performed using the SPCL_GRP_1_NAME and SPCL_GRP_2_NAME columns. Because the view performs the joins internally, queries against it are usually lighter to write but should still be constrained by calendar type, sequence number, or application date to avoid full scans across the full admissions population.