Results for “adm_ci_end_dt”

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

Overview

IGS_AD_PS_APPL_INST_APLSUMR_V is an Oracle E-Business Suite (EBS) database view owned by the APPS schema within the IGS (Student System) product family. As documented in the ETRM metadata for releases 12.1.1 and 12.2.2, the view presents a consolidated admission application summary derived from the base tables IGS_AD_APPL and IGS_AD_PS_APPL_INST. Its principal functional role is to supply the data block behind the Admission Application Summary region of the ADMF3000 form, the Admissions application maintenance screen used by institutions to review applicant choices, preferences, and admission outcomes.

Because it flattens applicant-level and program-instance-level attributes into a single queryable structure, the view also serves as a convenient reporting and integration source. It exposes derived columns such as concatenated calendar alternate codes, descriptive course titles, and decoded admission process categories, allowing downstream reports and interfaces to consume pre-resolved values rather than re-implementing lookup logic.

Underlying Base Objects

The ETRM documentation identifies two referenced base objects: IGS_AD_APPL and IGS_AD_PS_APPL_INST. The alias AAV in the view text corresponds to the applicant admission application record (IGS_AD_APPL), while ACAI corresponds to the admission program instance record (IGS_AD_PS_APPL_INST). The join is therefore one application to many nominated course preferences, keyed on person, admission application number, and choice.

The view text additionally references several supporting objects through scalar subqueries and joins, including IGS_CA_INST (calendar instances, aliased separately for original academic, overridden admission, and future academic/admission calendars), IGS_PS_VER (program version titles), and a lookup table joined via LKUP to resolve admission category meanings. The metadata notes no other documented base objects, so these subordinate references are best treated as ancillary lookups rather than primary driving tables.

Key Columns

• PERSON_ID, ADMISSION_APPL_NUMBER – Identifies the applicant and the specific admission application.
• CHOICE_NUMBER, PREFERENCE_NUMBER, SEQUENCE_NUMBER – Ordering attributes for applicant choices and program-instance lines.
• COURSE_CD, CRV_VERSION_NUMBER, NOMINATED_COURSE_CD – The nominated program and version, with a decoded course title supplied via IGS_PS_VER.
• ACAD_CAL_TYPE, ACAD_CI_SEQUENCE_NUMBER, ACAD_CI_START_DT, ACAD_CI_END_DT – Academic calendar instance context and its effective dates.
• ADM_CAL_TYPE, ADM_CI_SEQUENCE_NUMBER – Admission calendar, with NVL logic falling back to the application-level values when the program instance does not override them.
• FUTURE_ACAD_CAL_TYPE, FUTURE_ACAD_CI_SEQUENCE_NUMBER, FUTURE_ADM_CAL_TYPE, FUTURE_ADM_CI_SEQUENCE_NUMBER – Forward-looking calendar attributes; the view exposes FUTURE_ADM_CI_SEQUENCE_NUMBER directly and resolves the future calendars to alternate codes.
• ADMISSION_PROCESS_CAT / ADMISSION_CAT, S_ADMISSION_PROCESS_TYPE – Decoded admission process category presented as concatenated category and lookup meaning.
• ADM_APPL_STATUS, ADM_OUTCOME_STATUS, ADM_OFFER_RESP_STATUS – Application, outcome, and offer-response status indicators.
• APPL_DT – Application date.
• CREATED_BY, CREATION_DATE, LAST_UPDATED_BY, LAST_UPDATE_DATE, LAST_UPDATE_LOGIN – Standard audit columns inherited from the program-instance record.

Note: the user search term future_adm_ci_sequence_number maps directly to the exposed column FUTURE_ADM_CI_SEQUENCE_NUMBER, which stores the sequence number of the future admission calendar instance and is used alongside FUTURE_ADM_CAL_TYPE and the derived future alternate code.

Common Use Cases and Queries

Typical uses include admissions dashboards, applicant tracking extracts, and reconciliation of choices against calendar instances. The following sample returns the application summary for a given person:

• SELECT person_id, admission_appl_number, choice_number, nominated_course_cd, adm_appl_status, adm_outcome_status FROM igs_ad_ps_appl_inst_aplsumr_v WHERE person_id = :p_person_id ORDER BY choice_number;
• SELECT admission_appl_number, future_adm_cal_type, future_adm_ci_sequence_number, future_acad_cal_type FROM igs_ad_ps_appl_inst_aplsumr_v WHERE future_adm_ci_sequence_number IS NOT NULL;
• SELECT admission_process_cat, COUNT(*) FROM igs_ad_ps_appl_inst_aplsumr_v GROUP BY admission_process_cat;

All queries should be issued against the APPS schema or a synonym with appropriate grants, as the view is defined in APPS and relies on the caller having select privileges on the underlying IGS tables.