Search Results initial_name




Overview
Explore in AI Chat

Overview

IGS_PR_DISPLAY_V is a reporting and display view within the Oracle E-Business Suite IGS (Student System) product family, which is documented as obsolete in the ETRM reference for EBS 12.1.1 and 12.2.2. The view consolidates person-level attributes from the IGS_PE_PERSON entity and exposes them under a stable, denormalized column set intended for display and integration purposes rather than for transactional processing. Its name, incorporating "DISPLAY," indicates that it was designed to present formatted person names and derived indicators for user-facing screens, reports, and downstream integrations, sparing the calling application from repeating multi-column concatenation logic and functional lookups.

In addition to the columns physically present on the person record, the view computes several presentation-oriented derivations at query time by invoking PL/SQL functions in the IGS namespace. These include student and encumbered indicators resolved through IGS_EN_GEN_007.ENRP_GET_STUDENT_IND and IGS_EN_GEN_003.ENRP_GET_ENCMBRD_IND, and name-formatting operations resolved through IGS_GE_GEN_002.GENP_GET_INITIALS. The view therefore behaves partly as a data projection and partly as a formatting layer. Because the functions are packaged PL/SQL executed per row, performance is closely tied to the context in which the view is queried, and the view is best used for bounded result sets rather than large unbounded scans.

Underlying Base Objects

The view text defines a single documented base object: IGS_PE_PERSON, aliased as PE. No other base tables are documented in the ETRM metadata. The view is a straightforward projection over that table with no joins, no aggregation, and no set operators. All relational filtering and row identity are inherited directly from IGS_PE_PERSON, keyed by PERSON_ID.

The ETRM record for this view states that it is "Not implemented in this database" in the captured environment. In EBS 12.1.1 and 12.2.2 this typically reflects an environment where the obsolete IGS Student System modules were never installed, or where the object is absent because the relevant product license or patch level is not present. In environments where the product is installed, the view resides in the IGS schema and is subject to the standard EBS editioning and synonym conventions. The metadata lists no referenced base objects beyond the view text, so consumers should treat IGS_PE_PERSON as the authoritative dependency.

Key Columns

  • PERSON_ID — Primary identifier inherited from IGS_PE_PERSON; used for joins to other person-referencing views.
  • STAFF_MEMBER_IND — Identifies records that represent staff members.
  • STUDENT_IND — Derived at runtime via ENRP_GET_STUDENT_IND; the first character of the function result.
  • ENCUMBERED_IND — Derived via ENRP_GET_ENCMBRD_IND; the first character of the function result.
  • DECEASED_IND — Deceased status indicator carried from the base record.
  • SURNAME, GIVEN_NAMES, PREFERRED_GIVEN_NAME — Core name components used as building blocks for the formatted columns.
  • SEX, TITLE, SALUTATION, BIRTH_DT — Demographic attributes.
  • ORACLE_USERNAME, EMAIL_ADDR — Identity and contact attributes used for account and notification integrations.
  • ARCHIVE_EXCLUSION_IND, ARCHIVE_DT, PURGE_EXCLUSION_IND, PURGE_DT — Retention and archival control attributes.
  • FULL_NAME — GIVEN_NAMES concatenated with SURNAME.
  • PREFERRED_NAME — Preferred given name, or the first token of the given names, followed by surname.
  • TITLE_NAME — Title, given names, and surname combined.
  • INITIAL_NAME — Initials derived through GENP_GET_INITIALS, concatenated with surname.
  • INITIAL_LAST_NAME — Surname followed by initials.
  • CONTEXT_BLOCK_NAME — Reserved display column name retained from the view definition.

Common Use Cases and Queries

Typical usage centers on person lookup, directory-style displays, and integration extracts that require formatted names and derived student or staff classification. A basic query selects a single person by identifier and returns the formatted presentation columns:

  • SELECT person_id, full_name, preferred_name, initial_name FROM igs_pr_display_v WHERE person_id = :p_person_id;
  • SELECT person_id, student_ind, staff_member_ind, email_addr FROM igs_pr_display_v WHERE student_ind = 'Y';
  • SELECT person_id, surname, given_names, title_name FROM igs_pr_display_v WHERE UPPER(surname) LIKE :p_prefix || '%';

Because student and encumbered indicators are resolved by PL/SQL calls, predicates on those columns are evaluated after row retrieval and cannot be used for indexed access on the base table. Queries should therefore constrain the result set using indexed base columns such as PERSON_ID or SURNAME wherever possible and apply derivations as output projections. Joins to institutional enrollment or course views should use PERSON_ID as the linking key.

Given the obsolete status of the IGS Student System, new development should not depend on this view. Existing reports and integrations that reference it should be reviewed against current certified Student System objects, with preference given to successor person-attribute views that avoid per-row PL/SQL formatting calls.