Results for “crs_attempt_status”

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

Overview

The view APPS.IGS_EN_STDNT_PS_ATT_V is a student course attempt and attendance view within the Oracle E-Business Suite Student System (formerly Oracle Student System / OSS) module. It consolidates enrollment attendance records held in the base table IGS_EN_STDNT_PS_ATT and enriches them with person identifiers, lookup-driven flags, and fee category details. The view exposes the course attempt status of a student placement or attendance record through the COURSE_ATTEMPT_STATUS column, which is the principal attribute sought by the search term crs_attempt_status. Its role in EBS reporting and integration is to provide a single, denormalized source for querying student course attempts together with attendance mode/type, calendar type, location, and associated fee classification, without requiring report authors to reconstruct the join logic manually.

Underlying Base Objects

The view is defined over four referenced objects:

• IGS_EN_STDNT_PS_ATT (aliased IGS) — the primary student placement/attendance base table supplying the majority of columns.
• IGS_PE_PERSON_BASE_V (aliased PEV) — a person base view joined on PERSON_ID to supply PERSON_NUMBER.
• IGS_LOOKUPS_VIEW (aliased LKUP) — the lookup join restricted to LOOKUP_TYPE = 'CRS_ATTEMPT_STATUS', which decodes the attempt status and returns the FEE_ASS_IND indicator.
• IGS_FI_FEE_CAT (aliased FCAT) — the fee category table, outer-joined on FEE_CAT to return CURRENCY_CD.

The attempt status join is written as (IGS.COURSE_ATTEMPT_STATUS = LKUP.LOOKUP_CODE OR IGS.COURSE_ATTEMPT_STATUS IS NULL), so rows with a null status are still returned, matched against the lookup set for the CRS_ATTEMPT_STATUS lookup type. The FEE_CAT join is an outer join (FCAT.FEE_CAT(+)), meaning fee currency is populated only where a matching fee category exists.

Key Columns

• ROW_ID — the ROWID of the base attendance row, useful for unambiguous row identification.
• PERSON_ID / PERSON_NUMBER — the internal person identifier and the externally meaningful person number.
• COURSE_CD, VERSION_NUMBER — the course code and version for the attempt.
• CAL_TYPE — the calendar type under which the attendance is recorded.
• LOCATION_CD, ATTENDANCE_MODE, ATTENDANCE_TYPE — delivery location and attendance classification.
• COURSE_ATTEMPT_STATUS — the attempt status code (the crs_attempt_status sought by users), decodable against lookup type CRS_ATTEMPT_STATUS.
• FEE_ASS_IND — the fee assessment indicator derived from the status lookup.
• FEE_CAT / CURRENCY_CD — the fee category and its associated currency.
• Audit columns CREATED_BY, CREATION_DATE, LAST_UPDATED_BY, LAST_UPDATE_DATE, LAST_UPDATE_LOGIN.

Common Use Cases and Queries

Typical uses include enrollment reporting, attempt-status monitoring, fee assessment analysis, and integration extracts. A representative query filtering on attempt status is:

• SELECT person_number, course_cd, course_attempt_status FROM apps.igs_en_stdnt_ps_att_v WHERE course_attempt_status = 'ENROLLED';
• SELECT person_id, course_cd, fee_cat, currency_cd, fee_ass_ind FROM apps.igs_en_stdnt_ps_att_v WHERE fee_ass_ind = 'Y';
• SELECT course_attempt_status, COUNT(*) FROM apps.igs_en_stdnt_ps_att_v GROUP BY course_attempt_status;

Because the view resolves the lookup and person joins internally, it is well suited to ad-hoc SQL, BI Publisher data templates, and inbound/outbound integration where course attempt and attendance detail must be retrieved in a single pass.