Results for “igs_ad_appl”

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

Overview

IGS_AD_APPL is an Oracle E-Business Suite view owned by the APPS schema in the IGS (Student System) product family. It is a secure, business-group–filtered projection over the admissions application entity and serves as the primary reporting and integration surface for applicant data in EBS 12.1.1 and 12.2.2. The view is documented as VALID and is delivered with the Student System module.

Its principal design objective is multi-org security. The view does not expose the base table directly; instead it applies a WHERE clause against ORG_ID derived from the session's CLIENT_INFO value, using the standard EBS operator-leveloption pattern: NVL(TAB.ORG_ID, NVL(TO_NUMBER(DECODE(SUBSTRB(USERENV('CLIENT_INFO'),1,1),' ',NULL,SUBSTRB(USERENV('CLIENT_INFO'),1,10))),-99)). Because the user's search term was choice_number, it is relevant that CHOICE_NUMBER is one of the columns surfaced by this view; it represents the applicant's preference ordering among applications and is a recognised admissions reporting attribute.

Underlying Base Objects

The view is defined exclusively over IGS_AD_APPL_ALL, the multi-org base table that stores admissions applications. The documented view text selects from that table using the alias TAB and performs no joins, unions, or sub-queries; it is therefore a single-table, row-preserving view. ROW_ID is exposed as TAB.ROWID, allowing the view to be used for updatable/row-identified operations in Forms and OAF pages.

ETRM documentation records no other referenced base objects. Because IGS_AD_APPL_ALL is the multi-org (_ALL) variant, the view inherits both the ORG_ID column and the associated operating-unit partitioning of admissions data, which the view's security predicate then enforces at query time.

Key Columns

• ROW_ID — the base-table ROWID, exposed for record identification and locking.
• ORG_ID — operating unit; drives the view's security filter.
• CHOICE_NUMBER — the applicant's preference/priority number for the application, the attribute of interest in the originating search.
• PERSON_ID — the applicant's party/person identifier, the join key to person and party tables.
• ADMISSION_APPL_NUMBER and APPLICATION_ID / ALT_APPL_ID — the business-facing application number and internal/surrogate keys.
• APPL_DT — the application date.
• ACAD_CAL_TYPE and ADM_CAL_TYPE — academic and admissions calendar types.
• ACAD_CI_SEQUENCE_NUMBER and ADM_CI_SEQUENCE_NUMBER — calendar instance sequence numbers.
• ADMISSION_CAT, S_ADMISSION_PROCESS_TYPE, ADM_APPL_STATUS, ADM_FEE_STATUS, TAC_APPL_IND — admissions category, process type, application status, fee status, and TAC application indicator.
• SPCL_GRP_1, SPCL_GRP_2, COMMON_APP, APPLICATION_TYPE, ROUTEB_PREF — special-group flags, common-application indicator, application type, and route B preference.
• APPL_FEE_AMT — application fee amount.
• CREATED_BY, CREATION_DATE, LAST_UPDATED_BY, LAST_UPDATE_DATE, LAST_UPDATE_LOGIN, REQUEST_ID, PROGRAM_APPLICATION_ID, PROGRAM_ID, PROGRAM_UPDATE_DATE — standard EBS WHO columns and concurrent-program audit context.

Common Use Cases and Queries

Typical applications include admissions dashboards, preference/choice reporting, fee-status monitoring, and secure integrations that must respect operating-unit context. Because the view applies ORG_ID security automatically, callers should not add their own ORG_ID predicate when operator-level security is intended.

Sample query listing applications with their choice ordering for a session:

• SELECT application_id, admission_appl_number, person_id, choice_number, adm_apply_status, appl_dt
• FROM apps.igs_ad_appl
• ORDER BY person_id, choice_number;

A secondary example counts applications by choice number within the current operating unit:

• SELECT choice_number, COUNT(*) applications
• FROM apps.igs_ad_appl
• WHERE adm_apply_status = 'ACTIVE'
• GROUP BY choice_number ORDER BY choice_number;

For cross-operating-unit or diagnostic reports, the base table IGS_AD_APPL_ALL must be queried directly with an explicit ORG_ID filter, since the view's CLIENT_INFO predicate will otherwise restrict results to the session's current organization.