Search Results rule_check_ind




Overview
Explore in AI Chat

Overview

IGS_PR_STDNT_PS_ATT_V is an Oracle E-Business Suite view owned by the APPS schema within the IGS (Student System) product family. In release 12.1.1 and 12.2.2 it exposes student course attempt and attendance data drawn from the IGS_PR_STDNT_PS_ATT entity, joined to the party table to resolve the human-readable party number. The view presents one row per student course attempt, identified by the base table ROWID, and carries the full range of progression, attendance, completion, and administrative attributes that the Student System maintains for a learner's enrolment record.

Its principal role is to provide a denormalised, read-only projection of the persisted student attempt record for reporting, extract, and integration purposes. Because it surfaces both the recorded attendance values (ATTENDANCE_MODE, ATTENDANCE_TYPE) and the values derived by the progression rules engine (DERIVED_ATT_MODE, DERIVED_ATT_TYPE), the view is particularly relevant to queries that search on derived_att_mode. Callers can compare the derived attendance mode produced by rule processing against the attendance mode held on the record, which supports audit, reconciliation, and downstream reporting of student progression outcomes.

Underlying Base Objects

The documented view text references two source objects:

  • IGS_PR_STDNT_PS_ATT (aliased ESPA) — the principal base table holding student course attempt, attendance, and progression data. Every column in the view derives from this table with the exception of the party number.
  • HZ_PARTIES (aliased PE) — the trading community party table, joined on PERSON_ID to resolve PARTY_NUMBER. This supplies the PERSON_NUMBER column exposed as a human-readable student identifier.

The view makes no use of aggregation, DISTINCT, or set operators; it is a straightforward select-with-join. This means row counts correspond one-to-one with qualifying rows in the attempt table, and the ROW_ID column (ESPA.ROWID) can be used to map a view row back to its physical attempt record. No additional base objects are documented in the ETRM metadata, and no materialised or snapshot variants are implied.

Key Columns

Common Use Cases and Queries

Typical usage includes reporting the derived attendance mode for a student population, comparing derived against recorded attendance to detect rule-processing discrepancies, and extracting attempt data for a given course or calendar type. A representative query filtering on the derived attendance mode is:

  • SELECT person_number, course_cd, version_number, cal_type, attendance_mode, derived_att_mode, derived_att_type, course_attempt_status FROM igs_pr_stdnt_ps_att_v WHERE derived_att_mode = 'FT' AND logical_delete_dt IS NULL;
  • Reporting full-time versus part-time derived attendance by course: SELECT course_cd, derived_att_mode, COUNT(*) FROM igs_pr_stdnt_ps_att_v GROUP BY course_cd, derived_att_mode;
  • Reconciling recorded and derived values: SELECT person_number, course_cd, attendance_mode, derived_att_mode FROM igs_pr_stdnt_ps_att_v WHERE attendance_mode <> derived_att_mode;
  • Extracting progression status for a calendar type: SELECT person_number, progression_status, course_rqrmnt_complete_ind FROM igs_pr_stdnt_ps_att_v WHERE cal_type = 'STD' AND provisional_ind = 'N';

Because LOGICAL_DELETE_DT is exposed, queries should generally exclude logically deleted rows unless historical records are explicitly required.