Search Results title_name




Overview
Explore in AI Chat

Overview

IGS_PR_DISPLAY_V is a supplementary view owned by the APPS schema in Oracle E-Business Suite, registered under FND Design Data as IGS.IGS_PR_DISPLAY_V. It belongs to the Student System (IGS) product family and is classified as a "display" view — a construct used internally to simplify Forms-based coding by flattening person and party data into a single row per person. The status of the object is VALID, and it is documented in ETRM for both 12.1.1 and 12.2.2.

Oracle explicitly warns that this is a supplementary view used to simplify forms coding and that querying or altering data through it is not recommended. The definition may change dramatically in subsequent minor or major releases, so any reporting or integration built directly on this view carries upgrade risk. The view is not referenced by any other database object, confirming its role as a terminal, presentation-layer construct rather than a shared integration point.

The user search term "staff_member_ind" corresponds directly to a column exposed by this view, indicating that the view is commonly inspected when determining whether a person record represents a staff member, a student, or both.

Underlying Base Objects

ETRM documents the following dependencies for IGS_PR_DISPLAY_V:

  • APPS.IGS_PE_PERSON — the primary person entity table supplying PERSON_ID and the core person attributes.
  • IGS_EN_GEN_003 — a generated (GEN) object contributing to the view definition.
  • IGS_EN_GEN_007 — a second generated object referenced by the view.
  • IGS_GE_GEN_002 — a general generated object referenced by the view.

The view derives its row identity from IGS_PE_PERSON and augments it with flags and derived name formats produced by the IGS generated objects. The generated objects are typically populated by the Student System's concurrent processes and hold the derived indicator values (staff, student, encumbered, deceased) and the concatenated name variants that the view surfaces. Because these are generated objects rather than pure base tables, the values they carry depend on the successful completion of the relevant IGS batch programs.

Key Columns

Common Use Cases and Queries

The most frequent use is identifying staff members or distinguishing staff from students for display and listing purposes. A representative query is:

  • SELECT person_id, staff_member_ind, student_ind, full_name FROM apps.igs_pr_display_v WHERE staff_member_ind = 'Y';
  • SELECT person_id, full_name, email_addr FROM apps.igs_pr_display_v WHERE student_ind = 'Y' AND staff_member_ind = 'Y';
  • SELECT person_id, oracle_username, email_addr FROM apps.igs_pr_display_v WHERE person_id = :person_id;

Because the view is a Forms simplification layer, reporting teams should generally reproduce its logic against IGS_PE_PERSON and the underlying IGS generated objects rather than depending on the view itself.