Results for “encumbered_ind”

50+ results




Overview
Explore in AI Chat

AI-generated from documented ETRM metadata — verify critical details on the linked pages.

Overview

The IGS_PE_PRSID_GRP_MEM_V view is a reporting object within the Oracle E-Business Suite IGS (Student System) module, which is documented as obsolete in the ETRM reference for releases 12.1.1 and 12.2.2. The view presents a consolidated, denormalized snapshot of members belonging to person identification groups and personal identification groups, blending person biographical attributes with group membership records. Its principal role is to expose group membership data in a form suitable for reporting, inquiry, and integration, allowing developers and analysts to resolve group constituents without repeatedly joining the underlying membership and person tables themselves.

In the context of the user's search for "birth_dt", the view is significant because it exposes the person's birth date under the alias BIRTH_DT. This aliasing allows consumers to query a single, stable column name for age calculation, demographic reporting, and identification verification rather than resolving the native BIRTH_DATE column on the person base view.

Underlying Base Objects

According to the documented view text, no base objects are formally registered in the ETRM metadata; however, the definition references several concrete objects. The first branch of the UNION ALL joins IGS_PE_PERSON_BASE_V (aliased PE) to IGS_PE_PRSID_GRP_MEM_ALL (aliased GM) on PERSON_ID. This branch surfaces explicit person identification group members.

The second branch joins the same person base view to IGS_PE_PERSID_GROUP_ALL (aliased GP), applying the FILE_NAME IS NOT NULL filter and invoking the dynamic membership function IGS_PE_DYNAMIC_PERSID_GROUP.DYN_PIG_MEMBER(GROUP_ID, PERSON_ID). This resolves dynamically defined personal identification group members. Supporting package calls to IGS_EN_GEN_003 are used to derive the STUDENT_IND, STAFF_IND, and ENCUMBERED_IND flags. The use of ROWID as ROW_ID and SYSDATE/TO_DATE(NULL) in the second branch indicates a synthesized start date and null end date for dynamic members.

Key Columns

  • BIRTH_DT — the person's birth date, aliased from PE.BIRTH_DATE. This is the column implicated in the user's search.
  • ROW_ID — the ROWID of either the membership row (branch one) or the person row (branch two), useful for uniqueness and diagnostics.
  • GROUP_ID — identifier of the person or personal identification group to which the member belongs.
  • PERSON_ID — the unique person identifier linking to the person base view.
  • PERSON_NUMBER — the externally visible person identifier assigned by the institution.
  • FULL_NAME — the person's formatted full name.
  • SEX — the person's gender, aliased from PE.GENDER.
  • START_DATE / END_DATE — membership validity window; END_DATE is null for dynamic members.
  • STUDENT_IND / STAFF_IND / ENCUMBERED_IND — derived flags returned by IGS_EN_GEN_003 package functions indicating student, staff, and encumbrance status.
  • CREATED_BY, CREATION_DATE, LAST_UPDATED_BY, LAST_UPDATE_DATE, LAST_UPDATE_LOGIN — standard audit columns.

Common Use Cases and Queries

Typical usage includes roster reporting for identification groups, demographic analysis by birth date, and integration feeds that must resolve group membership together with person attributes. Because the view unifies static and dynamic membership, it is well suited to point-in-time queries.

Example query retrieving members with birth dates for a given group:

  • SELECT group_id, person_id, person_number, full_name, sex, birth_dt FROM igs_pe_prsid_grp_mem_v WHERE group_id = :p_group_id ORDER BY full_name;
  • SELECT person_id, full_name, birth_dt, student_ind, staff_ind, encumbered_ind FROM igs_pe_prsid_grp_mem_v WHERE active membership between start_date and end_date;
  • SELECT COUNT(*), TRUNC(MONTHS_BETWEEN(SYSDATE, birth_dt)/12) age FROM igs_pe_prsid_grp_mem_v GROUP BY TRUNC(MONTHS_BETWEEN(SYSDATE, birth_dt)/12);

Because the module is obsolete, implementers upgrading to later releases should confirm whether equivalent functionality has been replaced by successor person group views before relying on this object for long-term customizations.