Results for “student_confirmed_indicator”

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

Overview

The IGSBV_STUDENT_PROGRAM_ATTEMPTS view is a read-only reporting object in the Oracle E-Business Suite Student System (IGS) product. It is owned by the APPS schema and is documented as VALID in ETRM for both the 12.1.1 and 12.2.2 releases. The view presents a consolidated, denormalized record of a student's attempt at studying a particular course offered by the university, combining the student course attempt record with party identification and course version data.

The object functions as a business-facing view rather than a transactional entity: it is created with the WITH READ ONLY clause, meaning DML against it is not permitted and concurrency locks are not applied. Its principal role is to support operational reporting, inquiry screens, and downstream integration extracts that require a single row per student course attempt, resolved against the person's party record and the course version definition. Because the view carries the "_BV" naming convention, it is intended for presentation and reporting consumption rather than as a source of record.

Underlying Base Objects

The view text is defined over three base objects:

• IGS_EN_STDNT_PS_ATT_ALL (aliased SCA) — the student course attempt table, which supplies the majority of the columns including status, progression, commencement, discontinuation, and completion attributes.
• HZ_PARTIES (aliased HP) — the Trading Community Architecture party table, joined on SCA.PERSON_ID = HP.PARTY_ID to supply the party number.
• IGS_PS_VER_ALL (aliased PSV) — the course version table, joined on SCA.COURSE_CD = PSV.COURSE_CD AND SCA.VERSION_NUMBER = PSV.VERSION_NUMBER to supply the course version title.

The _ALL suffix on the two IGS tables indicates that the join resolves against the multi-org (business unit) enabled base tables, so the view respects installation-level organization security where that is enforced on the underlying objects.

Key Columns

Because the user search term was discontinued_date, the most relevant column is DISCONTINUED_DT, which records the date on which the student's attempt at the course was discontinued. It is complemented by DISCONTINUATION_REASON_CD, which carries the coded reason for the discontinuation, and by LAPSED_DT, which reflects a lapse rather than a formal discontinuation. These three attributes together let reporting distinguish a deliberate withdrawal from a passive lapse.

• COMMENCEMENT_DT — the date the student commenced the course attempt.
• COURSE_ATTEMPT_STATUS, PROGRESSION_STATUS — coded statuses resolved to meanings at runtime via the lookup references embedded in the view text.
• ATTENDANCE_MODE, ATTENDANCE_TYPE, LOCATION_CD — attendance and delivery attributes, with derived counterparts DERIVED_ATT_MODE and DERIVED_ATT_TYPE.
• DERIVED_COMPLETION_YR, DERIVED_COMPLETION_PERD, NOMINATED_COMPLETION_YR, NOMINATED_COMPLETION_PERD — expected and nominated completion periods.
• PARTY_NUMBER, TITLE — student identification data from HZ_PARTIES.
• Audit columns CREATED_BY, CREATION_DATE, LAST_UPDATED_BY, LAST_UPDATE_DATE, and LOGICAL_DELETE_DT.

Common Use Cases and Queries

Typical usage centres on identifying students whose course attempts have been discontinued within a reporting window, and on reconciling discontinued attempts against the discontinuation reason for retention and progression analysis.

To list discontinued attempts for a given period:

• SELECT PERSON_ID, COURSE_CD, VERSION_NUMBER, COMMENCEMENT_DT, DISCONTINUED_DT, DISCONTINUATION_REASON_CD FROM APPS.IGSBV_STUDENT_PROGRAM_ATTEMPTS WHERE DISCONTINUED_DT BETWEEN :start_date AND :end_date ORDER BY DISCONTINUED_DT;

To count discontinued attempts by reason:

• SELECT DISCONTINUATION_REASON_CD, COUNT(*) FROM APPS.IGSBV_STUDENT_PROGRAM_ATTEMPTS WHERE DISCONTINUED_DT IS NOT NULL GROUP BY DISCONTINUATION_REASON_CD;

Because the view is read-only and resolves lookups and party data at query time, queries should be filtered by PERSON_ID, COURSE_CD, or date predicates to avoid full scans across the underlying _ALL tables. Note that the view documentation does not enumerate base objects separately; the relationships above are taken from the view text itself.