Results for “igs_ad_appl_v”

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

Overview

IGS_AD_APPL_V is a seeded Oracle E-Business Suite view owned by the APPS schema and delivered with the IGS (Student System) product family. The view presents a denormalized, reporting-oriented projection of admission applications, joining the base application record to person identity data and to two decoded special group classifications. Its purpose is to provide a single, readable source for admission application inquiries, concurrent program extracts, Oracle Discoverer or OBIEE reporting, and downstream integrations that must resolve the code identifiers stored on the application into descriptive values without requiring the caller to join the code classes manually.

In ETRM 12.1.1 and 12.2.2 the object is documented as VALID and listed among the IGS implementation data dictionary entries, alongside its verbatim view text and column inventory.

Underlying Base Objects

The view text documents four referenced objects:

• IGS_AD_APPL — the driving application table, aliased A, holding admission application records. All non-decoded columns originate here.
• IGS_PE_PERSON_BASE_V — a person base view, aliased P, supplying PERSON_NUMBER. It is joined on PERSON_ID with an inner join, so applications without a resolvable person row are excluded.
• IGS_AD_CODE_CLASSES CC1 and IGS_AD_CODE_CLASSES CC2 — the same code classes table joined twice, once for each special group. Both joins are outer (+) and are further restricted by class: CC1.CLASS(+) = 'SPECIAL_GROUP1' and CC2.CLASS(+) = 'SPECIAL_GROUP2'. The application's SPCL_GRP_1 and SPCL_GRP_2 columns match CC1.CODE_ID and CC2.CODE_ID respectively.

Because both code lookups are outer joins, every application row is retained even when either special group is null or unresolvable; the decode columns simply return null in that case. The ETRM metadata records no separately documented base objects beyond those embedded in the view text.

Key Columns

• ROW_ID — unique row identifier for the application record.
• PERSON_ID / PERSON_NUMBER — internal party identifier and the external-facing person number from the person base view.
• ADMISSION_APPL_NUMBER, APPLICATION_ID, ALT_APPL_ID — the admission application number and related application identifiers.
• APPL_DT, ACAD_CAL_TYPE, ACAD_CI_SEQUENCE_NUMBER — application date and the academic calendar and calendar instance against which the application is placed.
• ADMISSION_CAT, S_ADMISSION_PROCESS_TYPE, ADM_APPL_STATUS, ADM_FEE_STATUS — admission category, process type, and status indicators for the application and its fee.
• SPCL_GRP_1 / SPCL_GRP_1_DESC — decoded NAME and DESCRIPTION of the first special group, sourced from CC1 for class 'SPECIAL_GROUP1'.
• SPCL_GRP_2 / SPCL_GRP_2_DESC — the equivalent decode for the second special group, class 'SPECIAL_GROUP2'.
• COMMON_APP, TAC_APPL_IND, ROUTEB_PREF, CHOICE_NUMBER, APPLICATION_TYPE — admissions processing flags and preference/choice attributes.
• APPL_FEE_AMT — application fee amount.
• Audit columns — CREATED_BY, CREATION_DATE, LAST_UPDATED_BY, LAST_UPDATE_DATE, LAST_UPDATE_LOGIN, REQUEST_ID, PROGRAM_APPLICATION_ID, PROGRAM_ID, PROGRAM_UPDATE_DATE.

Common Use Cases and Queries

The view is typically consumed for applicant listings, special group reporting, and extract feeds. A frequent pattern is filtering by special group description, which is the reason users search for the SPCL_GRP_1 column:

• Listing applications grouped by special group: SELECT admission_appl_number, person_number, spcl_grp_1, spcl_grp_1_desc FROM igs_ad_appl_v ORDER BY spcl_grp_1_desc;
• Filtering a specific special group: SELECT admission_appl_number, person_number FROM igs_ad_appl_v WHERE spcl_grp_1 = '&code_id';
• Feeding a concurrent extract: SELECT person_number, adm_appl_status, appL_dt FROM igs_ad_appl_v WHERE appl_dt BETWEEN :from_date AND :to_date;

When writing against this view, note that SPCL_GRP_1 contains the code identifier rather than the description, so meaningful output generally pairs it with SPCL_GRP_1_DESC. Because the person join is inner, counts derived from the view may be lower than a count of IGS_AD_APPL alone where orphaned person references exist.