Results for “unit_attempt_status”

50+ results




Overview
Explore in AI Chat

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

Overview

The view IGS_AD_ADM_UNIT_STAT belongs to the IGS – Student System product family within Oracle E-Business Suite. In the ETRM repository for releases 12.1.1 and 12.2.2, this object is classified as Obsolete and its implementation status is explicitly recorded as "Not implemented in this database." This means the view is documented for historical and reference purposes but is not created or deployed in a standard EBS installation of the referenced releases. Its presence in the ETRM metadata reflects the legacy Oracle Student System data model, which predates the current Student Information System (SIS) architecture and was largely superseded during the EBS product consolidation cycles.

Conceptually, the view presents administrative unit status configuration records. It exposes the valid combinations of administrative unit status and unit attempt status used to classify the lifecycle state of a student's administrative unit — for example, whether a unit attempt is active, withdrawn, or completed for administrative reporting purposes. Such status codes drive progression evaluation, time-elapsed accounting, and official notification generation within the student records domain.

Underlying Base Objects

The view is defined over a single base object, IGS_AD_ADM_UNIT_STAT_ALL, which follows the standard Oracle multi-organization ("_ALL") naming pattern. No other referenced base objects are documented in the ETRM metadata. The dependency is a straightforward projection: the view selects a defined column list from the base table and applies a row-level security predicate in the WHERE clause. The use of a "_ALL" table indicates that the underlying data is partitioned by operating unit via the ORG_ID column, a common design in EBS modules supporting multiple business units.

The view text preserves the standard EBS bookkeeping columns (ROWID alias, audit columns) drawn directly from the base table, indicating that the view itself performs no joins, aggregation, or data transformation beyond organization-level filtering.

Key Columns

Common Use Cases and Queries

Where the view exists (for example, in legacy or upgraded environments), it would typically support validation and reporting of administrative unit statuses for a given operating unit. A representative query returns active status definitions for the current organization:

SELECT administrative_unit_status, unit_attempt_status, description
FROM igs_ad_adm_unit_stat
WHERE closed_ind = 'N';

Because the view enforces the Multi-Org predicate through USERENV('CLIENT_INFO'), queries must be executed in a session where the client information (operating unit context) is correctly initialized; otherwise the ORG_ID comparison resolves to -99 and no rows are returned. Administrators verifying progression or notification configuration would join this view to admission and progression tables to confirm that each status combination carries the intended EFFECTIVE_PROGRESSION_IND and SHOW_ON_OFFIC_NTFCTN_IND settings. Given the obsolete classification, implementers should confirm existence at runtime and prefer supported Student System objects for new development.