Search Results igs_as_su_stmptout




Overview
Explore in AI Chat

Overview

IGS_AS_SU_STMPTOUT is a multi-organization view owned by the APPS schema in the Oracle E-Business Suite Student System (IGS) product. It presents student unit attempt outcome records — the graded results a student receives for a specific unit attempt within a teaching period. The view exposes the outcome data in a security-enabled, operating-unit-aware form, making it the standard reference object for reporting and integration when outcome information must be filtered by organization.

Within the EBS architecture, multi-org views are defined over a base table and include the ORG_ID column so that the application can apply operating unit security through the Multi-Org Access Control (MOAC) mechanism. In ETRM 12.2.2 the view is registered as VALID with the APPS owner. The view's role is to serve as the query surface for student unit attempt outcome data in forms, concurrent programs, and custom reports, preserving the full attribute set of the underlying record while enabling client-level (operating unit) partitioning. Version applicability spans 12.1.1 and 12.2.2, where its definition and column set remain consistent with the IGS data model.

Underlying Base Objects

The ETRM metadata for this view lists no separately documented referenced base objects, and the available documentation excerpt does not retain the FROM clause of the view definition. The view text captured in the implementation/DBA data is an explicit column projection: every column is selected from an alias named TAB, with the first column exposed as TAB.ROWID ROW_ID. This pattern is characteristic of a view defined over a single base table, aliased TAB, rather than a join.

By the naming convention and column set, the base object is the student unit attempt outcome table in the IGS Student System schema, from which the view carries forward the outcome key, grade, mark, grading schema, and audit columns. Because only the base table's ORG_ID column is surfaced, the view functions as the multi-org projection of that table; any row visible through the view satisfies the operating unit predicate applied by MOAC at runtime. The ROW_ID column derived from ROWID allows the view to support updatable, row-addressable operations in the associated maintenance form.

Key Columns

The view exposes the complete outcome record. The principal columns include:

Common Use Cases and Queries

The view is typically used to report or extract finalized and provisional outcomes for students within an operating unit, to feed academic history and transcript processes, and to drive interfaces that export marks to external systems. A representative query retrieves finalized outcomes for a unit attempt:

  • SELECT person_id, course_cd, unit_cd, ci_sequence_number, grade, mark, grading_schema_cd, outcome_dt FROM igs_as_su_stmptout WHERE org_id = :p_org_id AND finalised_outcome_ind = 'Y' AND grading_period_cd = :p_period;
  • SELECT person_id, unit_cd, translated_grade, translated_dt FROM igs_as_su_stmptout WHERE org_id = :p_org_id AND translated_grading_schema_ccd IS NOT NULL ORDER BY translated_dt;
  • SELECT person_id, unit_cd, incom_default_grade FROM igs_as_su_stmptout WHERE incom_deadline_date < SYSDATE AND incom_default_grade IS NOT NULL;

Because the view is a MOAC-enabled projection of the base outcome table, customers should always constrain queries by ORG_ID (or rely on the active organization context) to avoid returning data across operating units. Additional filtering on FINALISED_OUTCOME_IND, GRADING_PERIOD_CD, and the calendar context columns is recommended for performance and correctness.