Search Results outcome_dt




Overview

The IGS_AS_STD_UNT_ATMPT_OTCM_H_V view belongs to the Oracle Student System (IGS) product within Oracle E-Business Suite, and resides in the APPS schema. Its purpose is to merge student unit attempt outcome history records with the current student unit attempt outcome details, allowing outcome information to be evaluated across time up to the present day. Each row returned by the view represents the complete set of column values valid for a defined effective period, with the historical start and end dating carried alongside the outcome itself.

In Oracle EBS 12.1.1 and 12.2.2 the view is a reporting and integration construct rather than a transactional object. It is marked VALID in the ETRM repository and is not itself maintained by forms; instead it exposes grade, version, and finalisation information for a student's attempt at a unit so that downstream reports, extracts, and interfaces can retrieve outcome data at any point in its history. Because it combines historical rows with the current outcome record, it is particularly useful where a business process must reconstruct what the outcome was on a specific date.

Underlying Base Objects

The ETRM metadata records no explicitly documented referenced base objects, and the owner is listed as APPS. The view text, however, shows that the definition is built on the student unit attempt outcome history entity, aliased SUAOH1, together with the current student unit attempt outcome entity, aliased SUAO1. The two sources are combined so that each historical entry is enriched with the corresponding current value.

A notable characteristic of the view is its use of the server-side function IGS_AU_GEN_003.AUDP_GET_SUAOH_COL, which is invoked repeatedly to resolve individual columns such as GRADING_SCHEMA_CD, VERSION_NUMBER, GRADE, S_GRADE_CREATION_METHOD_TYPE, and FINALISED_OUTCOME_IND. The NVL and SUBSTR constructs wrapping these calls indicate a fallback strategy: the historical value is preferred, the audit API value is used if the history is null, and the current outcome value is used as the final default. This layering ensures that a value is always returned even when the history row is incomplete.

Key Columns

  • PERSON_ID — identifies the student to whom the unit attempt outcome belongs.
  • COURSE_CD, UNIT_CD, CAL_TYPE, CI_SEQUENCE_NUMBER — the academic context of the attempt, including the course, unit, calendar type, and calendar instance sequence.
  • OUTCOME_DT — the outcome date, the primary time reference for the outcome record and the column most frequently used to anchor historical queries.
  • HIST_START_DT, HIST_END_DT — the effective dating boundaries of the historical entry.
  • HIST_WHO — the user or process responsible for creating the historical record.
  • GRADING_SCHEMA_CD, GRADE, VERSION_NUMBER — the grading framework, the awarded grade, and the version of the outcome record.
  • S_GRADE_CREATION_METHOD_TYPE — indicates how the grade was generated.
  • FINALISED_OUTCOME_IND — flags whether the outcome has been finalised.

Common Use Cases and Queries

Typical uses include point-in-time grade reporting, audit reconstruction of historical outcomes, and extracts feeding transcripts or progression checks. Because OUTCOME_DT and the history dating columns are exposed directly, a common pattern is to filter by person and by a date range.

For example, to retrieve all outcome history for a student ordered by outcome date:

  • SELECT person_id, course_cd, unit_cd, outcome_dt, hist_start_dt, hist_end_dt, grade, finalised_outcome_ind FROM apps.igs_as_std_unt_atmpt_otcm_h_v WHERE person_id = :p_person_id ORDER BY outcome_dt, hist_start_dt;

To obtain the outcome in effect on a specific date, the enquiry constrains OUTCOME_DT and the history interval so that only the row covering the required point in time is returned. Because the view can be expensive when it invokes the audit API per row, most implementations restrict the query by person, unit, or calendar instance before applying date predicates.