Results for “prog_outcome_program_code”

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

Overview

IGSBV_PERSON_HOLDS is a read-only Oracle EBS view belonging to the IGS – Student System product family. It exposes encumbrance (hold) records placed against an applicant, student, or other person of interest within the institution. Typical holds include overdue parking fines, unpaid tuition or fees, and failure to return library materials. The view is a reporting and integration facade: it flattens the raw encumbrance table into descriptive, human-readable columns by joining to the trading community party table and the encumbrance type lookup table. As the view definition carries the WITH READ ONLY clause, it is intended strictly for query, extraction, and downstream reporting rather than for transactional insert, update, or delete operations.

In the 12.1.1 and 12.2.2 releases, the IGS product line is flagged as obsolete; the metadata records that the object is "Not implemented in this database." This means the view and its base objects may be absent or unsupported in a given installation, and its continued use should be validated against the specific environment before relying on it.

Underlying Base Objects

The view is defined over three base objects joined by equi-join predicates:

• IGS_PE_PERS_ENCUMB (aliased PEN) — the driving table holding the person encumbrance (hold) records, including type, start date, expiry date, comments, and authorising details.
• HZ_PARTIES (aliased HP) — joined on PEN.PERSON_ID = HP.PARTY_ID to retrieve the party number for the held person.
• IGS_FI_ENCMB_TYPE_ALL (aliased ENT) — joined on PEN.ENCUMBRANCE_TYPE = ENT.ENCUMBRANCE_TYPE to resolve the descriptive hold type name.

The metadata lists no separately documented referenced base objects, so the relationship model above is taken directly from the exposed view text.

Key Columns

• PERSON_ID / PERSON_NUMBER — Internal party identifier and the external party number for the person carrying the hold.
• HOLD_TYPE / HOLD_TYPE_DESCRIPTION — Encumbrance type code and its decoded description (e.g. parking fine, unpaid fees).
• EFFECTIVE_START_DATE — Derived from START_DT; the date the hold takes effect.
• EXPIRY_DATE — Derived from EXPIRY_DT; the date the hold lapses. This is the column most frequently used to filter active versus historical holds.
• NOTES — Free-text comments captured against the hold.
• PROG_OUTCOME_PROGRAM_CODE / PROG_OUTCOME_SEQUENCE_NUMBER / CALENDAR_TYPE — Contextual attributes linking the hold to a program outcome and calendar type.
• SEQUENCE_NUMBER — Ordering key within a person's holds.
• AUTHORIZING_PERSON_ID / AUTH_RESP_ID — The authorising individual and responsibility.
• EXTERNAL_REFERENCE — Optional cross-reference to an external system.
• CREATED_BY, CREATION_DATE, LAST_UPDATED_BY, LAST_UPDATE_DATE — Standard EBS audit columns.

Common Use Cases and Queries

Typical scenarios include a registrar dashboard of active holds, a finance check before enrolment, or an extract feeding an identity or library system. Because EXPIRY_DATE drives whether a hold is currently in force, queries frequently test it against the current date.

Active holds for a person:

• SELECT person_number, hold_type_description, effective_start_date, expiry_date, notes FROM igsbv_person_holds WHERE person_id = :p_person_id AND (expiry_date IS NULL OR expiry_date >= TRUNC(SYSDATE)) ORDER BY effective_start_date;

All holds expiring within a given window:

• SELECT person_number, hold_type_description, expiry_date FROM igsbv_person_holds WHERE expiry_date BETWEEN :p_from AND :p_to ORDER BY expiry_date;

Hold counts by type for a reporting period:

• SELECT hold_type_description, COUNT(*) FROM igsbv_person_holds WHERE effective_start_date <= TRUNC(SYSDATE) GROUP BY hold_type_description;

Given the obsolete status of the IGS module, any production query should be regression-tested against the target 12.1.1 or 12.2.2 environment before deployment.