Search Results alternate_code




Overview
Explore in AI Chat

Overview

The IGS_AD_PS_APL_INST_CNTX_V view is a component of the Oracle E-Business Suite (EBS) Student System product family (IGS), delivered under the APPS schema with a status of VALID in both the 12.1.1 and 12.2.2 releases. Its documented purpose is to present the application instance context for a student's admissions application. Within the IGS admissions data model, an "admission application instance" represents a specific application made by a person to a course, location, attendance mode, and academic period. This view flattens and decorates that context into a denormalized, human-readable projection, resolving foreign-key identifiers into descriptive values through correlated subqueries and code-class lookups.

This object is used heavily in reporting and integration scenarios where an external or internal consumer needs a single-row, self-describing representation of an application instance — for instance, when rendering context blocks in a self-service page, generating correspondence, or extracting application data for downstream analytics. The view does not itself store data; it is a read-only construct over the IGS admissions tables and is therefore appropriate for SELECT-only access.

Underlying Base Objects

The ETRM metadata for this view documents no referenced base objects, and the object-type metadata lists no base tables. The view text, however, clearly joins the application-instance context table (aliased AAV), the application/course-application-instance table (aliased ACAI), the party table (P, i.e., HZ_PARTIES), the calendar-instance table (CI1, CI2), the course-version table (CRV), and the lookup table (LKUP, i.e., FND_LOOKUPS). Descriptive lookups against IGS_AD_CODE_CLASSES and IGS_EN_UNIT_SET are performed through scalar subqueries rather than joins, so they do not appear as directly referenced base objects. Because the metadata is limited, practitioners should treat the view as a dependent object on the IGS admissions and party tables and validate dependencies through USER_DEPENDENCIES or the ETRM dependency report in their specific installation.

Key Columns

Common Use Cases and Queries

The view supports applicant-context reporting, admissions correspondence, and data extracts. A frequent pattern is to filter by person or application number and select the descriptive goal and course fields:

  • Applicant context lookup — retrieve the display name, application number, and course for a given person.
  • Educational goal analysis — group applicants by EDU_GOAL_PRIOR_ENROLL to profile prior-education intent.
  • Period reporting — filter on COMMENCEMENT_PERIOD or ACAD_ALTERNATE_CODE to report applications per academic period.

A representative query is:

SELECT person_number,
       dsp_context_block_name,
       admission_appl_number,
       cgnbt_course_cd,
       edu_goal_prior_enroll,
       edu_goal_prior_enroll_desc,
       commencement_period
FROM   apps.igs_ad_ps_apl_inst_cntx_v
WHERE  edu_goal_prior_enroll_id IS NOT NULL
ORDER  BY person_last_name;

Because the view resolves codes through scalar subqueries and concatenations, performance for large extracts is best served by filtering on indexed identifier columns (person or application number) rather than on the decoded descriptive columns.