Results for “derived_completion_yr”

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

Overview

The view APPS.IGS_EN_STDNT_PS_ATT is a seeded Oracle E-Business Suite database object belonging to the IGS — Student System product family. Its documented purpose is to present student attempt data for a given specific program structure. In practice, the view consolidates enrollment attempt records that describe how a student is progressing through a program, including the course attempted, the calendar and location context, attendance attributes, progression and completion indicators, and administrative handling flags. It is a reporting and integration surface that exposes these attempt records in a denormalized, ORG_ID-secured form suitable for operational reporting, extracts, and downstream interfaces.

The view is defined with the standard multi-org security predicate: it filters rows from the underlying _ALL table by matching ORG_ID against the value decoded from the session's USERENV('CLIENT_INFO'). This means queries executed under an operating unit context return only the attempt data relevant to that organization, which is consistent with the multi-org architecture used across Oracle EBS 12.1.1 and 12.2.2.

Underlying Base Objects

The documented view definition selects from IGS_EN_STDNT_PS_ATT_ALL, the multi-org base table that holds the physical attempt records. The view exposes a ROWID alias (ROW_ID) as its first column and then projects the full set of descriptive, status, and who-columns from that table. No other base objects are documented in the ETRM metadata, so the view should be understood as a secured projection over this single attempt table rather than as a join of multiple entities.

Because the base table carries the _ALL suffix, the view is the recommended access path for multi-org-aware queries. Direct queries against the _ALL table would bypass the operating-unit filtering that the view enforces.

Key Columns

• ORG_ID — Operating unit identifier; drives the multi-org security predicate.
• PERSON_ID — The student (person) associated with the attempt.
• COURSE_CD, VERSION_NUMBER — The course attempted and its version.
• CAL_TYPE, CATALOG_CAL_TYPE, CATALOG_SEQ_NUM, COMMENCEMENT_DT — Calendar and catalog context plus the attempt commencement date.
• COURSE_ATTEMPT_STATUS, PROGRESSION_STATUS — The attempt's status and the student's progression outcome.
• ATTENDANCE_MODE, ATTENDANCE_TYPE, DERIVED_ATT_TYPE, DERIVED_ATT_MODE — Attendance classification fields, including derived values.
• KEY_PROGRAM — The column referenced in the user's search; identifies the key program associated with the student's program attempt.
• PROGRAM_ID, PROGRAM_APPLICATION_ID, PRIMARY_PROGRAM_TYPE, PRIMARY_PROG_TYPE_SOURCE — Program identity and its primary type attribution.
• DERIVED_COMPLETION_YR, DERIVED_COMPLETION_PERD, NOMINATED_COMPLETION_YR, NOMINATED_COMPLETION_PERD, OVERRIDE_CMPL_DT, MANUAL_OVR_CMPL_DT_IND — Completion tracking, including derived, nominated, and manually overridden values.
• STUDENT_CONFIRMED_IND, ADVANCED_STANDING_IND, COURSE_RQRMNT_COMPLETE_IND, PUBLISH_OUTCOMES_IND — Indicator flags for confirmation, advanced standing, requirement satisfaction, and outcome publication.
• DISCONTINUED_DT, DISCONTINUATION_REASON_CD, LAPSED_DT, LOGICAL_DELETE_DT, LAST_DATE_OF_ATTENDANCE — Lifecycle and termination-related dates.
• CREATED_BY, CREATION_DATE, LAST_UPDATED_BY, LAST_UPDATE_DATE, LAST_UPDATE_LOGIN, REQUEST_ID — Standard audit and concurrent-request columns.
• ATTRIBUTE1 … ATTRIBUTE20, ATTRIBUTE_CATEGORY — Descriptive flexfield segments available for client-specific extension.

Common Use Cases and Queries

This view is typically used to report on student attempts per program structure, to feed completion and progression tracking, and to support extracts that require operating-unit isolation. A basic attempt listing for a person can be retrieved as follows:

• SELECT person_id, course_cd, version_number, key_program, course_attempt_status, progression_status FROM igs_en_stdnt_ps_att WHERE person_id = :p_person_id;
• SELECT program_id, key_program, COUNT(*) FROM igs_en_stdnt_ps_att GROUP BY program_id, key_program;
• SELECT person_id, commencement_dt, derived_completion_yr, nominated_completion_perd FROM igs_en_stdnt_ps_att WHERE course_attempt_status = 'ACTIVE';
• SELECT * FROM igs_en_stdnt_ps_att WHERE key_program IS NOT NULL AND org_id = :p_org_id;

Because ORG_ID filtering is enforced by the view itself, callers should still set the correct operating unit context before querying. Queries joining to student or program base tables should reference this view by PERSON_ID and PROGRAM_ID to avoid duplicating the multi-org predicate.