Results for “igs_en_stdnt_ps_att_sv”

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

Overview

The IGS_EN_STDNT_PS_ATT_SV view is a secured database view owned by the APPS schema within the IGS (Student System) product family in Oracle E-Business Suite. Its documented purpose is to expose the secured rows of the student program attempt table, filtering the underlying data so that only records permitted by the institution's security model are visible to the querying user. This security layer is a common pattern in the Student System, where row-level access to applicant and student data must be constrained by organizational and functional privileges.

Because it restricts rows at the database tier rather than in the application tier, the view is the preferred object for reporting, integration, and downstream extracts. It returns the same logical attributes as the base table while inheriting the security predicate defined by the product, which ensures consistency between the application forms and any external consumers of the data. In EBS 12.1.1 and 12.2.2 the view is registered in ETRM with STATUS = VALID, indicating the compiled definition matches the current database state.

Underlying Base Objects

The view text selects from a single base object, IGS_EN_STDNT_PS_ATT_ALL, which is the multi-organization table storing student program attempt records. Each attempt represents a student's enrollment in a program version for a specific calendar instance, tracking confirmation, status, progression, and completion attributes.

ETRM documents no additional referenced objects for this view. Operationally, however, the security filter that distinguishes the _SV view from unrestricted access relies on the Student System security framework, typically realized through security functions and organization (ORG_ID) predicates applied when the view is accessed through the standard APIs. The view therefore functions as the read-only, guarded projection of the base table, retaining the ROWID as ROW_ID to allow row identification.

Key Columns

• ROW_ID — the ROWID of the base row, used for direct row identification.
• ORG_ID — the operating unit / organization owning the attempt, central to multi-org and security filtering.
• PERSON_ID — the student or applicant party identifier.
• COURSE_CD, VERSION_NUMBER — the program (course) code and version attempt under way.
• CAL_TYPE, LOCATION_CD, ATTENDANCE_MODE, ATTENDANCE_TYPE — calendar, delivery location, and attendance classification.
• COURSE_ATTEMPT_STATUS, PROGRESSION_STATUS — the attempt's overall status and the student's progression outcome.
• COMMENCEMENT_DT, DISCONTINUED_DT, LAPSED_DT, LAST_DATE_OF_ATTENDANCE — key dates for lifecycle tracking.
• DISCONTINUATION_REASON_CD, DROPPED_BY — reason and actor for withdrawal.
• PROVISIONAL_IND, ADVANCED_STANDING_IND, STUDENT_CONFIRMED_IND — indicator flags governing confirmations and standing.
• KEY_PROGRAM, PRIMARY_PROGRAM_TYPE — identifies the primary or key program for the student.
• ATTRIBUTE_CATEGORY and ATTRIBUTE1–20 — descriptor flexfield columns for institution-specific data.
• CREATED_BY, CREATION_DATE, LAST_UPDATED_BY, LAST_UPDATE_DATE — audit columns.

Common Use Cases and Queries

Typical uses include extracting confirmed student attempts for a given organization, reporting progression and discontinuation trends, and feeding downstream student-record or funding interfaces. The following query lists active program attempts for an organization, ordered by commencement:

SELECT person_id, course_cd, version_number, cal_type,
       course_attempt_status, progression_status, commencement_dt
  FROM igs_en_stdnt_ps_att_sv
 WHERE org_id = :p_org_id
   AND student_confirmed_ind = 'Y'
   AND logical_delete_dt IS NULL
 ORDER BY commencement_dt;

To reconcile secured rows against the base table, compare counts by organization:

SELECT a.org_id, COUNT(*) base_rows, COUNT(s.row_id) secured_rows
  FROM igs_en_stdnt_ps_att_all a,
       igs_en_stdnt_ps_att_sv s
 WHERE a.rowid = s.row_id (+)
 GROUP BY a.org_id;

Because the view enforces accessibility, it should be preferred over direct queries against the base table in reports and integrations, ensuring that consumers see only the records their responsibility permits.