Results for “final_mandatory_type_code”

50+ results




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

Overview

IGS_AS_SUAAI_OUHIST is a history (audit) table within the Oracle E-Business Suite Student System (IGS) product family. It records the historical progression of student assessment item outcomes — specifically the grading schema, mark, grade, outcome date, and outcome comment associated with each assessment attempt item. The base (current-state) table for this history table is IGS_AS_SU_ATMPT_ITM, meaning that as outcome values change on the base record, prior versions are preserved here rather than overwritten.

Because the object is owned by the IGS schema and validated in the ETRM 12.1.1 / 12.2.2 repository, it is a supported, queryable artifact used for institutional assessment and grading reporting. Per the heuristic Data Vault classification derived from its foreign-key structure, this table is best modeled as a link — it connects multiple business entities (the student attempt item, the assessment item group, and the assessment definition) while carrying the temporal history attributes themselves. Analysts should treat this as a relationship/history bridge rather than a pure descriptive satellite.

Key Information Stored

The table exposes 30 documented columns. The most operationally significant are the identity and business-key columns and the tracked outcome attributes.

The primary key is the composite unique index IGS_AS_SUAAI_OUHIST_PK on (PERSON_ID, COURSE_CD, UOO_ID, ASS_ID, CREATION_DT, HIST_START_DT). This composite is itself the business-key candidate — there is no separate surrogate key column documented, so the natural key doubles as the row identity and must include HIST_START_DT to disambiguate successive versions.

Common Use Cases and Queries

Typical use is point-in-time reconstruction of a student's assessment outcome, change auditing, and grade-appeal investigation. A frequent pattern joins the history to the base table and to the assessment item group to trace how a mark or grade evolved.

  • Reconstructing the outcome as of a date: filter on HIST_START_DT <= :as_of AND (HIST_END_DT IS NULL OR HIST_END_DT > :as_of) for a given PERSON_ID and ASS_ID.
  • Auditing grade changes: order by HIST_START_DT and compare GRADE/MARK between consecutive rows for the same attempt item.
  • Reporting by grading schema: aggregate MARK by GRADING_SCHEMA_CD and GS_VERSION_NUMBER to validate grading configuration usage.
  • Penalty and waiver analysis: count rows where PENALTY_APPLIED_FLAG or WAIVED_FLAG is set.
  • Group-level roll-ups: join SUA_ASS_ITEM_GROUP_ID to IGS_AS_SUA_AI_GROUP for assessment-group reporting.

Related Objects

  • IGS_AS_SU_ATMPT_ITM — the base table; joined on PERSON_ID, COURSE_CD, UOO_ID, ASS_ID, CREATION_DT. This is the current-state counterpart.
  • IGS_AS_SUA_AI_GROUP — referenced via SUA_ASS_ITEM_GROUP_ID; defines the assessment item group.
  • IGS_AS_SUAAI_OUHIST_PK — the primary key/unique index enforcing row identity.
  • IGS_AS_SU_ATMPT — the parent student attempt entity providing broader attempt context.
  • IGS_AS_ASSESSMENT — defines the assessment referenced by ASS_ID.
  • IGS_EN_STUDENT / Person tables — resolve PERSON_ID to student biographical detail.

Because the history is event-versioned rather than status-flagged, consumers should always constrain on the HIST_START_DT/HIST_END_DT window to avoid double-counting multiple versions of the same outcome.