Search Results basis_for_admission_code




Overview
Explore in AI Chat

Overview

APPS.IGSFV_AD_ADM_PS_APPL is a Business Intelligence System (BIS) view owned by the APPS schema in Oracle E-Business Suite, registered under FND Design Data reference IGS.IGSFV_AD_ADM_PS_APPL. It is part of the Oracle Student System (formerly Oracle iLearning/Student Information) product family, delivered within the IGS application. The view presents admission application program information — specifically the linkage between a person, their admission application, and the academic program offering patterns to which they are applying or from which they are transferring.

The object is a denormalized, presentation-layer view intended to support reporting and integration scenarios where consumers need person, application, and program context in a single flattened structure. As a BIS view, it is not a table for transactional maintenance; it exposes read-only, query-optimized data. The view status is VALID, indicating it is compiled and available in the E-Business Suite instance. Its design purpose is to simplify retrieval of admission application program attributes without requiring the consumer to reconstruct the underlying entity relationships.

Underlying Base Objects

The ETRM metadata for this object documents no referenced base objects at the view definition level. In practice, a view of this shape is defined over Oracle Student System admission and party tables, most centrally the admission application base tables (such as IGS_AD_APPL and its program/offering-pattern children) joined to HZ_PARTIES for person identity attributes. The PERSON_ID column is documented explicitly as a foreign key to HZ_PARTIES, confirming a join to the Trading Community Architecture (TCA) party model.

Because the view is a read-only BI construct, no DML is supported against it. Any structural change to the underlying admission application tables can affect the view; consumers should treat the column list as the stable contract rather than relying on internal join logic.

Key Columns

Common Use Cases and Queries

Typical scenarios include identifying applicants transferring from one program to another, producing admissions extracts, and joining person identity to program context for reporting.

Retrieve transfer applications for a given person:

SELECT person_number, person_name, admission_application_number,
       nominated_program_code, transfer_program_code
FROM   apps.igsfv_ad_adm_ps_appl
WHERE  person_id = :p_person_id;

List all transfers into a target program:

SELECT nominated_program_code, transfer_program_code, COUNT(*) transfers
FROM   apps.igsfv_ad_adm_ps_appl
WHERE  transfer_program_code IS NOT NULL
GROUP  BY nominated_program_code, transfer_program_code;

Report admission basis with ranking for a recruitment centre:

SELECT person_number, admission_application_number,
       basis_for_admission_type_desc, program_rank_set
FROM   apps.igsfv_ad_adm_ps_appl
WHERE  program_rank_schedule = :schedule;

Reports and integrations should apply the standard APPS view access pattern and observe WHO audit columns for change-tracking extracts.