Search Results external_reference_desc




Overview
Explore in AI Chat

Overview

IGS_PE_PERS_ENCUMB_V is a seeded Oracle E-Business Suite view owned by the APPS schema and defined in the IGS (Student System / Student Records) product family. It presents person-level encumbrance records held against students and related parties, enriched with human-readable person numbers, responsibility names, and lookup descriptions. Encumbrances in this context represent administrative holds — such as financial, academic, or disciplinary restrictions — that prevent a person from performing certain transactions, for example registration or graduation.

The view is the primary reporting interface for the underlying IGS_PE_PERS_ENCUMB table. Rather than exposing raw foreign keys and codes, it resolves them to meaningful values, which makes it suitable for concurrent programs, BI Publisher reports, OAF-based pages, and inbound/outbound integrations that need to interpret encumbrance data without duplicating join logic. The view is read-only by convention; DML against it is not supported because it is a multi-table join involving outer joins and a lookup table.

Underlying Base Objects

The view is defined over five objects:

The metadata record lists no separately documented referenced base objects, so the join semantics above are taken directly from the published view text.

Key Columns

  • ROWID — the row identifier of the underlying IGS_PE_PERS_ENCUMB row, useful for drill-through.
  • PERSON_ID — internal identifier of the encumbered person.
  • PERSON_NUMBER (from P1) — the user-facing person number.
  • ENCUMBRANCE_TYPE, CAL_TYPE, SEQUENCE_NUMBER — classification and ordering attributes of the encumbrance.
  • START_DT, EXPIRY_DT — effective period of the hold.
  • AUTHORISING_PERSON_ID and the corresponding PERSON_NUMBER (from P2) — who raised the encumbrance.
  • AUTH_RESP_ID / AUTH_RESP_NAME — the responsibility under which it was raised.
  • COMMENTS — free-text explanation.
  • SPO_COURSE_CD, SPO_SEQUENCE_NUMBER — reference to the associated student program offering record.
  • EXTERNAL_REFERENCE / EXTERNAL_REFERENCE_DESC — the code and its decoded meaning from the PE_EXT_REF lookup.
  • CREATED_BY, CREATION_DATE, LAST_UPDATED_BY, LAST_UPDATE_DATE, LAST_UPDATE_LOGIN — standard WHO audit columns.

Common Use Cases and Queries

Typical scenarios include listing active holds for a student, auditing who raised encumbrances, and filtering by external reference type where encumbrances originate from an external system.

Active encumbrances for a person:

  • SELECT person_number, encumbrance_type, start_dt, expiry_dt, external_reference_desc
  • FROM apps.igs_pe_pers_encumb_v
  • WHERE person_id = :p_person_id
  • AND (expiry_dt IS NULL OR expiry_dt >= TRUNC(SYSDATE));

Encumbrances by external reference of interest (the term the user searched, pe_ext_ref):

  • SELECT person_number, encumbrance_type, external_reference, external_reference_desc, comments
  • FROM apps.igs_pe_pers_encumb_v
  • WHERE external_reference IS NOT NULL
  • ORDER BY person_number, start_dt DESC;

Audit of authorising responsibility:

  • SELECT person_number, auth_resp_name, comments, creation_date
  • FROM apps.igs_pe_pers_encumb_v
  • WHERE auth_resp_id = :p_resp_id;

Because the lookups and responsibilities are outer-joined, rows with missing references remain visible and should be handled with NVL where appropriate.