Search Results encumbered_ind




Overview
Explore in AI Chat

Overview

IGS_PE_PRSID_GRP_MEM_V is a seed-data view in the Oracle E-Business Suite (EBS) 12.1.1 / 12.2.2 environment, owned by the APPS schema and belonging to the Student Systems (IGS) product family. It presents person identifier group memberships — that is, the association between a person (student, applicant, or staff member) and a person identification group — enriched with core biographical attributes drawn from the person base view. The view is primarily consumed by Oracle Student System processes such as person identifier group maintenance, communications generation, and enrollment-related reporting.

The column alias BIRTH_DT in this view is the reason it typically surfaces in searches for "birth_dt". Callers frequently join or query this view to obtain a person's date of birth alongside group membership context, rather than querying the person base view directly. The view is also referenceable through Oracle EBS's standard reporting and integration layers (e.g., BI Publisher data models, concurrent programs, and OAF-based pages).

Underlying Base Objects

The view is defined over two base objects: IGS_PE_PERSON_BASE_V (aliased PE) and, depending on the union branch, either IGS_PE_PRSID_GRP_MEM_ALL (aliased GM) or IGS_PE_PERSID_GROUP_ALL (aliased GP). The ETRM metadata lists no additional documented base objects; the definition itself supplies the complete dependency set.

The view is constructed as a UNION ALL of two queries:

  • The first branch joins IGS_PE_PERSON_BASE_V to IGS_PE_PRSID_GRP_MEM_ALL on PERSON_ID, returning stored group membership rows with their actual START_DATE and END_DATE.
  • The second branch joins IGS_PE_PERSON_BASE_V to IGS_PE_PERSID_GROUP_ALL, but only for groups where FILE_NAME IS NOT NULL and where the person is a member according to the dynamic group function IGS_PE_DYNAMIC_PERSID_GROUP.DYN_PIG_MEMBER(GROUP_ID, PERSON_ID). For these dynamic memberships it substitutes SYSDATE as the start date and TO_DATE(NULL) as the end date.

The union therefore merges statically stored memberships with dynamically evaluated memberships, presenting them as a single logical population.

Key Columns

  • ROW_ID — the ROWID of the underlying person base row, retained for update/identification purposes.
  • GROUP_ID — identifier of the person identification group.
  • PERSON_ID, PERSON_NUMBER, FULL_NAME — core person identifiers and name.
  • SEX — the person's gender, aliased from PE.GENDER.
  • BIRTH_DT — the person's date of birth, aliased from PE.BIRTH_DATE; this is the column most commonly searched for in this view.
  • START_DATE, END_DATE — the effective period of the group membership; for dynamic memberships, start resolves to SYSDATE and end to NULL.
  • STUDENT_IND, STAFF_IND, ENCUMBERED_IND — flags derived from the IGS_EN_GEN_003 package functions, indicating student, staff, and encumbrance status respectively.
  • Standard audit columns CREATED_BY, CREATION_DATE, LAST_UPDATED_BY, LAST_UPDATE_DATE, and LAST_UPDATE_LOGIN.

Common Use Cases and Queries

Typical uses include retrieving birthday information for members of a given person identifier group (e.g., for communications or compliance reporting), auditing membership periods, and distinguishing static versus dynamic memberships.

Example — retrieve members of a group with their birth dates:

  • SELECT person_id, person_number, full_name, birth_dt, group_id, start_date, end_date
  • FROM apps.igs_pe_prsid_grp_mem_v
  • WHERE group_id = :p_group_id
  • ORDER BY full_name;

Example — filter by student status and date of birth range:

  • SELECT person_number, full_name, birth_dt, student_ind
  • FROM apps.igs_pe_prsid_grp_mem_v
  • WHERE student_ind = 'Y' AND birth_dt BETWEEN :from_dt AND :to_dt;

Because dynamic memberships return SYSDATE as START_DATE, queries that compare membership periods should account for the union branch when interpreting results.