Results for “igs_as_su_stmptout_all”

50+ results




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

Overview

The IGS.IGS_AS_SU_STMPTOUT_ALL table is a core component of the Oracle E-Business Suite Student System (IGS) product family, which forms the academic records backbone in Oracle EBS 12.1.1 and 12.2.2. The table records the outcome of a student unit attempt, expressed as a mark or grade, and is specifically engaged when the default or calculated mark for a unit attempt is overridden by an administrator or academic officer. It therefore serves as the authoritative persistence point for manual and finalised assessment outcomes, distinct from the automated grading records stored elsewhere in the Student System schema.

The object resides in the IGS schema and is documented as VALID within the ETRM repository. Its physical definition includes 62 columns, with a composite primary key named IGS_AS_SU_STMPTOUT_ALL_PK. In Data Vault modeling terms, the heuristic classification of this table is satellite-leaning: it captures descriptive, time-variant attribute history (marks, grades, override indicators, and comments) around a stable business key, rather than representing a standalone hub of identities or a pure associative link. Modelers adopting a Data Vault or raw-vault layering should treat it accordingly and anchor it to the parent student-unit-attempt entity.

Key Information Stored

The table’s primary key is composite, comprising PERSON_ID, COURSE_CD, UOO_ID, OUTCOME_DT, and GRADING_PERIOD_CD. This business-key candidate uniquely identifies a student’s outcome for a given unit offering occurrence within a specific grading period and outcome date. Of the 62 documented columns, the most operationally significant include:

Standard EBS WHO columns (CREATED_BY, CREATION_DATE, LAST_UPDATED_BY, LAST_UPDATE_DATE), concurrency fields (REQUEST_ID, PROGRAM_ID, PROGRAM_APPLICATION_ID), the ORG_ID multi-tenant discriminator, and 20 generic ATTRIBUTE columns complete the definition. These attributes are exposed for client-specific extensibility.

Common Use Cases and Queries

Typical reporting scenarios include producing finalised grade lists by grading period, auditing manual overrides, and reconciling translated versus original marks. A representative query retrieves finalised overridden outcomes for a student:

SELECT person_id, course_cd, uoo_id, grade, mark, outcome_dt
FROM   igs.igs_as_su_stmptout_all
WHERE  person_id = :p_person_id
AND    manual_override_flag = 'Y'
AND    finalised_outcome_ind = 'Y'
ORDER BY outcome_dt DESC;

For institutional reporting, aggregation by GRADING_PERIOD_CD and COURSE_CD supports grade distribution analysis, while joins to the parent attempt table reconcile outcome records against enrolment history. Extract and integration routines frequently filter on LAST_UPDATE_DATE to drive incremental feeds into data warehouses.

Related Objects

The primary referential relationship is to the student unit attempt entity:

  • IGS_EN_SU_ATTEMPT_ALL — the parent attempt table, joined on PERSON_ID, COURSE_CD, and UOO_ID; this is the documented foreign key target and the principal dependency.

Beyond the documented FK, related Student System objects that typically reference or depend on this table include grading schema and grade lookup views, academic history and transcript generation processes (IGS_AS_* assessment tables), and the unit offering structures (IGS_PS_*) that supply UOO_ID context. Curriculum and calendar objects supplying GRADING_PERIOD_CD and CAL_TYPE complete the join path for full-context reporting. Because the table is satellite-leaning, warehouse models generally align it to the attempt hub using the composite business key described above.