Search Results adm_alternate_code




Overview
Explore in AI Chat

Overview

IGS_AD_APPL_INST_MKDES_V is an APPS-owned, VALID database view within the IGS (Student System) product of Oracle E-Business Suite, applicable to release levels 12.1.1 and 12.2.2. The view consolidates admissions application instance data for a person and presents it alongside descriptive, code-resolved attributes. Its name and definition indicate it serves as a marketing/description ("MKDES") presentation layer — supplying a flattened, human-readable projection of admissions application records that joins structural admissions data with calendar relation information and lookup descriptions.

In EBS reporting and integration contexts, the view is typically consumed by concurrent programs, Oracle Reports, BI Publisher data templates, and custom SQL that require a comprehensive admissions application profile without re-implementing the multi-object join logic. Because it exposes decoded descriptions (admission category descriptions, basis-for-admission descriptions, lookup meanings), it reduces the need for downstream decode logic in report queries.

Underlying Base Objects

The view text references the following documented source objects:

The join predicates link APAIAV to CIAPV on four keys (ACAD_CAL_TYPE, ACAD_CI_SEQUENCE_NUMBER, ADM_CAL_TYPE, ADM_CI_SEQUENCE_NUMBER), and link the remaining descriptive objects on their respective coded values.

Key Columns

Common Use Cases and Queries

Typical scenarios include admissions reporting, applicant profile extracts, and integrations requiring decoded admission attributes. A representative query filtering on the alternate code column is:

  • SELECT adm.admission_appl_number, adm.person_id, adm.acad_alternate_code, adm.adm_alternate_code, adm.admission_cd_desc FROM apps.igs_ad_appl_inst_mkdes_v adm WHERE adm.adm_alternate_code = :p_alternate_code;

Other uses include listing applicants by admission process type using S_ADM_PRCS_TYPE_DESC, or extracting predicted GPA and entry qualification status for selection committees. Queries should still supply an appropriate academic calendar predicate, as the join resolves calendar context explicitly.