Results for “igs_en_stdnt_ps_att_v”

13 results




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

Overview

IGS_EN_STDNT_PS_ATT_V is a seeded Oracle E-Business Suite view owned by the APPS schema within the IGS (Student System) product family. It presents detailed information about a student's attempt against a specific program structure, consolidating student identity, attendance mode and type, and the current course attempt status into a single queryable object. Because it joins several validated base entities, the view is intended for reporting, inquiry, and integration scenarios where a denormalized, read-only projection of student program-structure attempts is required.

The view is documented as VALID and is available under both EBS 12.1.1 and 12.2.2; its column set and view text are identical across these releases. It exposes eighteen columns, including standard WHO audit attributes inherited from the underlying attempt table, and is typically consumed by custom concurrent programs, OBIEE/BI Publisher extracts, and interface queries.

Underlying Base Objects

Although the ETRM metadata lists no referenced base objects, the view text documents its composition. It is defined over four sources:

The join to the lookup is effectively a left join because the predicate permits COURSE_ATTEMPT_STATUS to be NULL; the fee category join is explicitly an outer join (+).

Key Columns

  • PERSON_ID / PERSON_NUMBER — the internal person identifier and the external person number for the student.
  • COURSE_CD, VERSION_NUMBER — the course and its version attempted.
  • CAL_TYPE, LOCATION_CD — the calendar type and delivery location of the attempt.
  • ATTENDANCE_MODE, ATTENDANCE_TYPE — how the student attends (e.g., full-time/part-time) and the attendance classification.
  • COURSE_ATTEMPT_STATUS — the attempt outcome/state, validated against the CRS_ATTEMPT_STATUS lookup.
  • FEE_ASS_IND, FEE_CAT, CURRENCY_CD — fee assessment indicator, fee category, and the currency associated with that category.
  • ROW_ID and WHO columns — ROW_ID (from IGS ROWID) plus CREATED_BY, CREATION_DATE, LAST_UPDATED_BY, LAST_UPDATE_DATE, and LAST_UPDATE_LOGIN.

Common Use Cases and Queries

Typical uses include attendance reporting by program structure, fee-category analysis, and integration extracts for downstream systems. A basic listing follows:

  • SELECT person_number, course_cd, version_number, attendance_type, course_attempt_status, fee_cat, currency_cd FROM igs_en_stdnt_ps_att_v WHERE person_id = :p_person_id;
  • SELECT course_attempt_status, COUNT(*) FROM igs_en_stdnt_ps_att_v GROUP BY course_attempt_status;
  • SELECT fee_cat, currency_cd, COUNT(*) FROM igs_en_stdnt_ps_att_v WHERE fee_ass_ind = 'Y' GROUP BY fee_cat, currency_cd;

Because CURRENCY_CD originates from an outer join, it may be NULL where no fee category match exists; consumers should anticipate this. As a view, it carries no independent storage and inherits the security and performance characteristics of its base objects.