Results for “auth_resp_name”

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

Overview

IGSFV_PERSON_HOLDS is a read-only view owned by the APPS schema within the IGS - Student System product of Oracle E-Business Suite. It presents the holds, or encumbrances, placed against an applicant or student record, such as overdue parking fines, unpaid fees, or failure to return library books. The view consolidates data from the encumbrance base table with supplementary descriptive and party information, projecting a denormalized result set that is convenient for reporting, inquiry screens, and integration extracts. The view is defined with the WITH READ ONLY clause, so it supports query access only; all maintenance of hold records must be performed against the underlying base tables.

The object is marked VALID and is available in EBS 12.1.1 and 12.2.2 environments. Because it lives in the APPS schema, it is typically queried through the standard Oracle EBS responsibility and security model rather than being accessed directly by end users. The column alias AUTH_RESP_NAME, which maps to the authorizing responsibility name, is directly relevant to the user search term "auth_resp_name".

Underlying Base Objects

The view is defined over the following documented base objects:

• IGS_PE_PERS_ENCUMB (aliased PEN) — the primary table holding person encumbrance/hold records.
• HZ_PARTIES (aliased HP1) — supplies the held person's party number; joined on PEN.PERSON_ID = HP1.PARTY_ID.
• IGS_FI_ENCMB_TYPE_ALL (aliased ENT) — provides the hold type description; joined on PEN.ENCUMBRANCE_TYPE = ENT.ENCUMBRANCE_TYPE.
• HZ_PARTIES (aliased HP2) — supplies the authorizing person's party number; outer-joined on PEN.AUTHORISING_PERSON_ID = HP2.PARTY_ID (+).
• IGS_CA_INST_ALL (aliased CA) — supplies the term alternate code; outer-joined on calendar type and sequence number.
• FND_RESPONSIBILITY_VL (aliased R) — supplies the authorizing responsibility name; outer-joined on PEN.AUTH_RESP_ID = R.RESPONSIBILITY_ID (+).

The outer joins ensure that hold rows are retained even when the authorizing person, calendar instance, or authorizing responsibility is not populated.

Key Columns

• PERSON_ID / PERSON_NUMBER — the party identifier and party number of the held applicant or student.
• HOLD_TYPE / HOLD_TYPE_DESCRIPTION — the encumbrance type code and its descriptive meaning.
• EFFECTIVE_START_DATE / EXPIRY_DATE — the validity window of the hold.
• NOTES — free-text comments recorded against the hold.
• PROG_OUTCOME_PROGRAM_CODE / PROG_OUTCOME_SEQUENCE_NUMBER — program outcome context for the hold.
• CALENDAR_TYPE / SEQUENCE_NUMBER / TERM — the academic calendar context and its alternate code.
• AUTHORIZING_PERSON_ID / AUTHORIZING_PERSON_NUMBER — the party who authorized the hold.
• AUTH_RESP_ID / AUTH_RESP_NAME — the authorizing responsibility identifier and name.
• CREATED_BY, CREATION_DATE, LAST_UPDATED_BY, LAST_UPDATE_DATE — standard audit columns.
• _LA:EXTERNAL_REFERENCE — a descriptive flexfield external reference column sourced from lookup values.

Common Use Cases and Queries

Typical uses include student hold inquiry reports, fee-collection follow-up, and interfaces that export active holds to downstream systems. A common filter is by authorizing responsibility name, matching the "auth_resp_name" search:

• Listing all holds for a given responsibility — WHERE AUTH_RESP_NAME = :resp_name.
• Identifying active holds by date — WHERE TRUNC(SYSDATE) BETWEEN EFFECTIVE_START_DATE AND NVL(EXPIRY_DATE, SYSDATE).
• Reporting holds by type or term for a population of students.

Sample query:

SELECT PERSON_NUMBER, HOLD_TYPE_DESCRIPTION, EFFECTIVE_START_DATE, EXPIRY_DATE, AUTH_RESP_NAME, NOTES FROM APPS.IGSFV_PERSON_HOLDS WHERE AUTH_RESP_NAME = :resp_name AND TRUNC(SYSDATE) BETWEEN EFFECTIVE_START_DATE AND NVL(EXPIRY_DATE, SYSDATE);

Because the view is read-only and exposed in APPS, it is well suited to ad hoc reporting and integration extracts without risk of modifying student hold data.