Search Results voluntary_flag

Overview

The IGSBV_STDNT_PRG_INTERMISSIONS view is a read-only business view (BV) object within the Oracle E-Business Suite Student System (IGS) product family. It is owned by the APPS schema and carries a VALID status in both the 12.1.1 and 12.2.2 releases of Oracle EBS. The view is designed to expose intermission information associated with a student's program attempt — that is, periods during which a learner has formally paused, suspended, or otherwise interrupted their registered program of study. Intermissions are distinct from withdrawals: they represent a temporary leave of absence, and the view therefore captures not only the temporal boundaries of the pause but also institutional approvals, voluntary versus involuntary classification, and the anticipated academic impact measured in credit points and terms.

Within the IGS architecture, this view serves as a reporting and integration façade over the underlying intermission entity. It flattens person identity attributes and intermission detail into a single denormalised projection, allowing downstream reports, self-service pages, and integration extracts to access intermission data without joining to the person registry directly.

Underlying Base Objects

The documented view text shows the definition is constructed from two sources joined on the party identifier:

• IGS_EN_STDNT_PS_INTM (aliased SCI) — the core student program intermission table. This supplies all intermission-specific attributes: course code, intermission type, start and end dates, voluntary indicator, approval status, comments, institution name, maximum credit points, maximum terms, anticipated credit points, approver, audit columns, logical delete date, and the conditional return flag.
• HZ_PARTIES (aliased HP) — the Oracle Trading Community Architecture (TCA) party registry. The join condition SCI.PERSON_ID = HP.PARTY_ID supplies the party number and party name, giving the intermission record a human-readable identity context.

The view is declared WITH READ ONLY, confirming it is intended strictly for query and reporting purposes; no DML is permitted against it. The ETRM metadata for 12.2.2 does not enumerate further referenced base objects beyond these two, and no additional documented dependencies exist.

Key Columns

• PERSON_IDENTIFIER / PERSON_NUMBER / PERSON_NAME — the student's party identifier, human-readable party number, and full name sourced from HZ_PARTIES.
• PROGRAM_CODE — the course or program code against which the intermission applies (COURSE_CD in the base table).
• INTERMISSION_TYPE — the classification of the intermission.
• START_DATE / END_DATE — the effective period of the intermission.
• VOLUNTARY_FLAG and its lookup description VOLUNTARY_FLAG_DESC — whether the intermission was student-initiated, resolved against IGS_LOOKUP_VALUES (YES_NO).
• APPROVED_FLAG and APPROVED_FLAG_DESC — approval status of the intermission, likewise resolved through IGS_LOOKUP_VALUES.
• INSTITUTION_NAME — the institution associated with the intermission.
• MAXIMUM_CREDIT_POINTS / MAXIMUM_TERMS — the caps applied to the intermission.
• ANTICIPATED_CREDIT_POINTS — the credit points the student is expected to attain or retain in connection with the intermission; this is the column most commonly targeted by academic progress and credit-planning queries.
• APPROVER_PERSON_IDENTIFIER, CREATED_BY / CREATION_DATE, LAST_UPDATED_BY / LAST_UPDATE_DATE — audit and approver traceability.
• LOGICAL_DELETE_DATE — soft-delete marker; records with a populated value should generally be excluded from current-state reporting.
• COND_RETURN_FLAG — indicator of a conditional return arrangement.

Common Use Cases and Queries

Typical uses include student academic progress reporting, intermission register listings for registrar offices, and extracts feeding credit-point forecasting. The ANTICIPATED_CREDIT_POINTS column is frequently requested where institutions assess the credit impact of a leave of absence.

Listing active intermissions for a student:

SELECT person_number, person_name, program_code,
       intermission_type, start_date, end_date,
       approved_flag_desc, anticipated_credit_points
FROM   apps.igsbv_stdnt_prg_intermissions
WHERE  person_number = :p_party_number
AND    logical_delete_date IS NULL;

Aggregating anticipated credit points by program:

SELECT program_code,
       SUM(anticipated_credit_points) AS total_anticipated_credits
FROM   apps.igsbv_stdnt_prg_intermissions
WHERE  approved_flag = 'Y'
AND    logical_delete_date IS NULL
GROUP  BY program_code;

Because the view is read-only and already resolves the YES_NO lookup meanings, it is well suited to ad-hoc reporting and to views layered in a custom reporting schema.