Search Results we_note_text




Overview

IGS_SS_ADM_APPL is an online admission application view within the Oracle EBS Student System (IGS) module. It presents all admission applications received through online channels, consolidating applicant, calendar, admissions, and personal data into a single queryable object. In the ETRM metadata for release 12.2.2, the view carries the description "An Admission Application Online View which stores all admission applications received online," and is classified under the IGS - Student System product line, which is now marked Obsolete. The implementation record states that the view is "Not implemented in this database," indicating that in the documented environment the object is registered in the ETRM but not physically deployed.

The view's role is primarily informational and integration-oriented. Rather than acting as a transactional interface, it exposes a denormalized projection of admission application data suited to reporting, downstream extraction, and legacy coexistence scenarios. It is most commonly referenced when administrators, migration teams, or legacy integrations need to retrieve online-submitted application records with their associated academic and admission calendar context.

Underlying Base Objects

The view text confirms a single underlying base object: IGS_SS_ADM_APPL_ALL. The SELECT statement aliases this table as TAB and projects its columns alongside a ROWID expression, exposed as ROW_ID, and ORG_ID for multi-organization filtering. No other referenced base objects are documented in the ETRM metadata.

The _ALL suffix on the underlying table is significant: it signals that the base table is partitioned by operating unit or organization, and the view preserves the ORG_ID column so that consumers can apply the appropriate organization security predicate. Because the view text reads directly from IGS_SS_ADM_APPL_ALL with no joins, filters, or aggregations, its row count and column semantics mirror the base table exactly, making it a thin, read-only presentation layer rather than a derived or transformed object.

Key Columns

The view exposes a broad set of admission and applicant attributes. The most important include:

Common Use Cases and Queries

Typical usage centers on locating applications by calendar context, person, or status. For example, to identify applications tied to a specific academic calendar sequence:

  • SELECT ss_adm_appl_id, person_id, acad_cal_type, acad_cal_seq_number, appl_status FROM igs_ss_adm_appl WHERE acad_cal_seq_number = :seq AND org_id = :org;
  • SELECT person_id, appl_submit_date, appl_status FROM igs_ss_adm_appl WHERE appl_submit_date >= :from_date ORDER BY appl_submit_date DESC;
  • Reporting extracts joining PERSON_ID to person and applicant tables for admission dashboards.

Because the object is documented as obsolete in 12.1.1/12.2.2, these queries should be regarded as legacy patterns; new development should target supported Student System structures.