Search Results igs_ss_su_selection

Overview

The Oracle EBS view IGS_SS_SU_SELECTION belongs to the IGS — Student System product family, which is documented in ETRM as obsolete. The view presents student unit selections: the records that capture which units (subjects) a student has enrolled in or attempted within a given academic calendar and version. It is defined over the base table IGS_SS_SU_SELECTION_ALL and applies an Oracle Multi-Org (Operating Unit) filter in its predicate. Because the object is a reporting-style view rather than a transactional form block, its role is principally read-oriented — supporting queries, extraction, and integration of enrolment data. It should be noted that the ETRM metadata records this view as Not implemented in this database, meaning that in the documented 12.2.2 environment the underlying tables are not present, and the object is retained only as historical metadata. Where the object is implemented in a live 12.1.1 or 12.2.2 instance, it exposes student enrolment lines for operational and analytical reporting.

Underlying Base Objects

The view is defined as a filtered projection of IGS_SS_SU_SELECTION_ALL, which holds the multi-org-enabled master records. The ETRM metadata lists no additional referenced base objects, and all columns in the view are drawn directly from that single table without joins to other IGS tables in the view text. The distinguishing behaviour is the Org ID predicate, which compares the row's ORG_ID against the operating unit resolved from the session's USERENV('CLIENT_INFO') value. The expression applies NVL(..., -99) on both sides of the comparison, so rows with a null or unresolvable operating unit are matched to the same default sentinel value, preserving visibility of records that are not operating-unit specific. This pattern — a “_ALL” table paired with a secured view — is the standard Oracle Multi-Org reporting convention.

Key Columns

• ROW_ID — the ROWID of the underlying row, used by Oracle Forms for row identification and locking.
• USEC_SU_SELECTION_ID — primary identifier for the student unit selection record.
• PERSON_ID — the student/party identifier for whom the selection is made.
• UNIT_CD, VERSION_NUMBER, CAL_TYPE, CI_SEQUENCE_NUMBER — the unit, version, calendar type, and calendar instance sequence identifying the offering selected.
• LOCATION_CD, UNIT_CLASS, UOO_ID, COURSE_CD — delivery location, class, unit offering option, and parent course.
• CALL_NUMBER — the section/call number identifying the specific teaching instance of the unit; this is a frequent filter in enrolment reporting and is the term users most often search for against this view.
• ENROLLED_DT, ENROLLED_CP, GRADING_SCHEMA_CD, UNIT_ATTEMPT_STATUS — enrolment date, credit points, grading scheme, and attempt status.
• CREATED_BY, CREATION_DATE, LAST_UPDATED_BY, LAST_UPDATE_DATE, LAST_UPDATE_LOGIN — standard WHO audit columns.
• ORG_ID — the operating unit that drives the view's multi-org security predicate.

Common Use Cases and Queries

Typical use is reporting or extraction of student unit selections, often locating a specific class section by call number. A representative query is:

SELECT person_id, unit_cd, version_number, cal_type,
       call_number, enrolled_dt, enrolled_cp,
       unit_attempt_status, org_id
FROM   igs_ss_su_selection
WHERE  call_number = :p_call_number;

Because the view enforces operating-unit security, queries return only rows visible to the session's client information. Analysts building joins usually link PERSON_ID to party/student views, and unit identifiers to the corresponding IGS unit and course tables. Where the object is not implemented — as recorded in the ETRM metadata for this database — the view returns no data and the query will fail with an invalid object error, so its presence should be verified before use.