Search Results reason_for_request

Overview

IGS_EN_SPL_PERM_H_V is a seeded Oracle E-Business Suite view owned by the APPS schema and shipped as part of the IGS — Student System product family (the Student Information System/Student Records modules). As its description states, the view contains the history of special permission request transactions. A "special permission" (often abbreviated SPL or SPL_PERM) is the workflow by which a student requests instructor or departmental authorization to enroll in a class that would otherwise be restricted — for example, a unit that requires consent, has a prerequisite waiver, or is closed to the student's program.

The view exposes the historical audit trail of these requests: each time a special permission request is created, approved, denied, or otherwise modified, a historical row is written. The _H_V suffix denotes a history view (the "_H_" segment) presented for query and reporting. Because enrollment and permission data are date-effective and audited, the history view is the authoritative source for point-in-time reporting — determining what the status of a request was on a given date, which instructor acted, and what the student submitted.

The view is not a transactional entry point. It is consumed by inquiry pages, concurrent reporting programs, and downstream integration extracts that need a flattened, denormalized picture of special permission activity. It is commonly joined to other IGS views for student, unit, and instructor context.

Underlying Base Objects

The documented view text confirms the view is defined over two principal aliased sources: a history table (aliased SPH1) and a current/version snapshot (aliased SPV1), plus a lookup (LKV). While the ETRM "referenced base objects" list is empty in the supplied metadata, the SELECT list and aliases allow the following to be inferred from documented facts:

• SPH1 — the special permission request history table (columns prefixed SPL_PERM_REQUEST_H_ID, HIST_START_DT, HIST_END_DT, HIST_WHO). The _H_ID and HIST_* columns are the signature of a date-tracked history (audit) table.
• SPV1 — the special permission request version table (columns such as SPL_PERM_REQUEST_ID, STUDENT_PERSON_ID, INSTRUCTOR_PERSON_ID, UNIT_CD, VERSION_NUMBER, UNIT_CLASS, CALL_NUMBER, TITLE, UOO_ID).
• LKV — a lookup view supplying the descriptive MEANING for the coded transaction/status.

The view further calls institutional API functions: IGS_AU_GEN_003.ENRP_GET_SPH_COL (retrieves a history column value effective at the row's HIST_END_DT) and IGS_GE_DATE.IGSDATE (a date-normalization function). The NVL/SUBSTR nesting means each attribute resolves from the history table first, falling back to the version row, then truncated to its display length (for example, 1 character for status flags, 300 for free-text reasons).

Key Columns

• SPL_PERM_REQUEST_H_ID / SPL_PERM_REQUEST_ID — primary history and parent request identifiers.
• HIST_START_DT, HIST_END_DT, HIST_WHO — the effective dating window and the user who made the historical change.
• STUDENT_PERSON_ID, INSTRUCTOR_PERSON_ID, UOO_ID — the parties and unit-offering occurrence involved.
• UNIT_CD, VERSION_NUMBER, UNIT_CLASS, CALL_NUMBER, TITLE — teaching unit identity. CALL_NUMBER is the human-readable class-section reference students use; it is the key the user searched on.
• DATE_SUBMISSION, APPROVAL_STATUS, TRANSACTION_TYPE, AUDIT_THE_COURSE — request lifecycle attributes.
• REASON_FOR_REQUEST, STUDENT_MORE_INFO, INSTRUCTOR_MORE_INFO, INSTRUCTOR_DENY_INFO — narrative text (truncated to 300).
• MEANING, REQUEST_TYPE, and the standard CREATED_BY/CREATION_DATE/LAST_UPDATE* audit columns.

Common Use Cases and Queries

Typical uses include auditing who approved or denied a special permission, reproducing point-in-time status, and tracking activity by call number.

SELECT call_number, unit_cd, student_person_id,
       approval_status, hist_start_dt, hist_end_dt, meaning
FROM   apps.igs_en_spl_perm_h_v
WHERE  call_number = '12345'
ORDER  BY hist_start_dt;

Reporting all history for a specific request, or counting approvals by term, follows the same pattern using SPL_PERM_REQUEST_ID and HIST_END_DT range predicates.