Search Results context_block_name




Overview
Explore in AI Chat

Overview

IGS_AD_PS_APLCNTX_LKUP_V is a lookup view belonging to the IGS (Student System) product family within Oracle E-Business Suite. The view is documented as obsolete in the ETRM reference for both release 12.1.1 and 12.2.2, and the metadata explicitly states that it is not implemented in the database. Its documented purpose is to expose a flattened, form-friendly projection of the underlying application context data held in IGS_AD_PS_APPL_APLCNTX_V, specifically so that an Oracle Forms block requiring a context block name field could be driven from a view rather than the base object directly.

The naming convention reflects this design intent: the object is a lookup-oriented view (_LKUP_V) derived from a person, sex, application context view. Its role historically was to support admissions inquiry and application-context forms that needed a lightweight, read-only data source keyed on CONTEXT_BLOCK_NAME. Because the "context block name" attribute appears as a first-class column in the select list, the view was intended to serve Forms blocks that resolve their block context from the student system's application context framework.

Underlying Base Objects

Per the documented view text, the view is defined over a single base object:

  • IGS_AD_PS_APPL_APLCNTX_V — aliased as ACACV in the view definition; this is the admissions application context view that supplies person, application, course, sex, birth date, and audit columns.
  • FND_LOOKUP_VALUES — referenced only inside a scalar subquery used to translate the SEX code into its descriptive meaning via the HZ_GENDER lookup type, restricted to VIEW_APPLICATION_ID = 222, SECURITY_GROUP_ID = 0, and the session language.

No additional base tables are documented for this view in the ETRM metadata, and the "Referenced base objects" section records none. The dependence on IGS_AD_PS_APPL_APLCNTX_V makes the lookup view a thin wrapper, adding only the gender decodes and column renaming for form consumption.

Key Columns

Common Use Cases and Queries

Since the object is obsolete and not implemented, practical usage is limited to historical form logic or migration reference. A representative query follows the original select semantics:

  • Retrieving applicant context rows for a given person or application.
  • Resolving CONTEXT_BLOCK_NAME when building Forms blocks against applicant data.
  • Producing a localized gender label alongside the raw code for report output.

Example:

  • SELECT PERSON_ID, ADMISSION_APPL_NUMBER, CONTEXT_BLOCK_NAME, SEX, MEANING_SEX, BIRTH_DT FROM IGS_AD_PS_APLCNTX_LKUP_V WHERE PERSON_ID = :person_id;

Because the view is documented as not implemented and obsolete across 12.1.1 and 12.2.2, it should not be relied upon for new development; equivalent data should be sourced directly from IGS_AD_PS_APPL_APLCNTX_V.