Search Results course_rank_schedule




Overview
Explore in AI Chat

Overview

IGS_AD_PS_APPL is an Oracle E-Business Suite view owned by the APPS schema in the IGS (Student System) product family. It is a multi-organization (ORG_ID) secured view that exposes admission application data for students within the Oracle Student System. The view presents a filtered, single-organization perspective of admissions records, allowing end users and concurrent programs to query only the application rows belonging to the organization currently set in their session context. In EBS 12.1.1 and 12.2.2, this view functions primarily as a reporting and integration access point over the admissions application data model, rather than as a storage object. Its status is VALID, and it is maintained as part of the standard APPS-tier view definitions shipped with the Student System module.

Underlying Base Objects

The view is defined over a single documented base object: IGS_AD_PS_APPL_ALL, which serves as the multi-organization table that physically stores admission application records across all operating units. IGS_AD_PS_APPL applies a WHERE clause that filters rows from IGS_AD_PS_APPL_ALL so that only records matching the operating unit derived from the session's client information are returned. The filtering logic uses USERENV('CLIENT_INFO') combined with NVL and DECODE constructs to extract the ORG_ID from the client context; rows are matched when the organization identifier in the base table equals the session-derived organization, with -99 used as a fallback. This pattern is the standard Multi-Org view implementation used throughout EBS Release 12, ensuring that queries against the view are automatically restricted to the user's organization without requiring the caller to add an ORG_ID predicate manually.

Key Columns

Common Use Cases and Queries

The view is commonly used for admissions reporting, applicant tracking, integration extracts, and validation of Multi-Org security behavior. It is also useful when diagnosing why records are not visible to a user, since visibility depends entirely on the session ORG_ID. A typical query retrieves applicant applications for the current organization:

  • SELECT ADMISSION_APPL_NUMBER, PERSON_ID, NOMINATED_COURSE_CD, ADMISSION_CD, CREATION_DATE FROM APPS.IGS_AD_PS_APPL WHERE PERSON_ID = :person_id ORDER BY CREATION_DATE DESC;
  • SELECT ORG_ID, COUNT(*) FROM APPS.IGS_AD_PS_APPL GROUP BY ORG_ID;
  • SELECT a.PERSON_ID, a.ADMISSION_APPL_NUMBER, a.REQ_FOR_ADV_STANDING_IND FROM APPS.IGS_AD_PS_APPL a WHERE a.REQ_FOR_RECONSIDERATION_IND = 'Y';

Because the view enforces organization filtering automatically, callers should set the correct operating unit in the session (for example via MO_GLOBAL or the standard Multi-Org initialization) before executing queries, otherwise the ORG_ID predicate resolves to the fallback value and may return no rows.