Results for “deficiency_in_prep”

20 results




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

Overview

IGS_AD_PS_APPL_INST_SV is an Oracle E-Business Suite (EBS) secure view owned by the APPS schema and delivered as part of the IGS – Student System product family. In EBS 12.1.1 and 12.2.2 it serves as the read-access layer over the admissions application instance table, exposing institution-level application data while enforcing the row-level security policies defined by the product. The view is registered in ETRM with a status of VALID and its stated purpose is to secure the SELECT operation on the underlying admissions data.

The "SV" suffix denotes "secure view," a standard Oracle Student System design pattern in which a base table (typically suffixed _ALL) is protected by a security view that resolves organization and installation access through the product's security framework. Direct access to the base table is discouraged; applications, concurrent programs, and reporting tools are expected to query the secure view so that the user's organization context is applied automatically.

Because the view surfaces admissions application data end to end — including decision, financial aid intent, and academic preparation attributes — it is commonly used in student admissions reporting, integration extracts, and downstream analytics. The user search term finaid_apply_date maps directly to the FINAID_APPLY_DATE column, which is one of the flagship columns exposed by this view.

Underlying Base Objects

The view is defined over IGS_AD_PS_APPL_INST_ALL, the base admissions application instance table. The documented view text projects a selected subset of the base columns and aliases them, for example TAB.FINAID_APPLY_DATE FINAID_APPLY_DATE, TAB.PERSON_ID PERSON_ID, and TAB.APPLY_FOR_FINAID APPLY_FOR_FINAID. The ROWID of the base row is exposed as ROW_ID, enabling consumers to join back to the base table when required.

Notably, the documented definition does not reference FND_ORG_SECURITY predicates explicitly in the excerpt; the securing behavior in Oracle Student System secure views is normally implemented via the product's organization access views or the institution-level security model that governs ORG_ID. The view also exposes two columns, ATHLETIC_GPA and ATHLETIC_ELIGIBILITY_STATUS_ID, as NULL, indicating that these attributes are reserved or retired and are retained only for interface compatibility with consumers expecting the legacy column list.

Key Columns

Common Use Cases and Queries

Typical uses include admissions pipelines reporting, financial aid intent analysis, and integration extracts transmitted to downstream student systems. A minimal query retrieving financial aid application timing is:

SELECT person_id,
       admission_appl_number,
       program_id,
       apply_for_finaid,
       finaid_apply_date
FROM   apps.igs_ad_ps_appl_inst_sv
WHERE  finaid_apply_date IS NOT NULL
ORDER  BY finaid_apply_date DESC;

To correlate financial aid intent with admissions decisions:

SELECT s.person_id,
       s.admission_appl_number,
       s.decision_date,
       s.finaid_apply_date,
       s.predicted_gpa
FROM   apps.igs_ad_ps_appl_inst_sv s
WHERE  s.apply_for_finaid = 'Y'
AND    s.decision_date >= SYSDATE - 365;

Because the view returns the base ROWID as ROW_ID, consumers may join back to IGS_AD_PS_APPL_INST_ALL for columns not projected here. Queries should always be issued against the secure view rather than the base table so that organization security and the product's access rules remain enforced.