Search Results outcome_comment_code




Overview

IGS.IGS_AS_AIO_INTERFACE is a transient staging table owned by the IGS (Student Systems / Academic Administration) schema in Oracle E-Business Suite Release 12.1.1 and 12.2.2. It serves as the inbound interface for Assessment Item Outcome records, designed primarily to import assessment item grades and related outcome details that have been entered into Oracle Web ADI (Web Applications Desktop Integrator) spreadsheets. Once uploaded, the rows are validated and processed by an import concurrent program that writes the accepted grades into the permanent assessment tables and returns any failures by populating the ERROR_CODE column.

From a modeling perspective, the heuristic Data Vault classification of this object is standalone, determined from its foreign key structure. This classification is a modeling suggestion rather than a prescriptive definition: the table does not decompose into a hub, link, or satellite pattern because its only documented foreign key is a reference to a parent assessment item rather than a complete integration key set. It should therefore be treated as a batch-oriented interface/staging entity rather than a conformed dimension or fact source.

Key Information Stored

The table stores one row per assessment item outcome to be imported, keyed by a batch. The most significant columns are:

The remaining documented columns include additional process attributes such as LOCATION_CD, UNIT_CLASS, WAIVED_FLAG, PENALTY_APPLIED_FLAG, OVERRIDE_DUE_DT, DUE_DT, SUBMITTED_DATE, UOO_ID, plus ATTRIBUTE_CATEGORY and thirty Attribute DFF columns (ATTRIBUTE1–ATTRIBUTE30) supporting descriptive flexfield capture.

Common Use Cases and Queries

Typical use cases center on monitoring and troubleshooting Web ADI grade uploads. A common query retrieves all failed rows in a batch, which is useful before re-submitting corrected spreadsheets:

  • SELECT person_number, unit_cd, ass_id, grade, outcome_comment_code, error_code FROM igs.igs_as_aio_interface WHERE batch_date = :p_batch AND error_code IS NOT NULL;
  • SELECT user_id, batch_date, COUNT(*) FROM igs.igs_as_aio_interface GROUP BY user_id, batch_date; to summarize upload volumes per user and batch.
  • SELECT ass_id, mark, grade FROM igs.igs_as_aio_interface WHERE outcome_comment_code = :p_code; to audit usage of a specific outcome comment code from lookups before it is retired.

Because the interface tablespace is APPS_TS_INTERFACE, rows are normally purged after successful import; retained rows indicate incomplete or failed processing.

Related Objects

  • IGS.IGS_AS_ASSESSMNT_ITM_ALL — parent assessment item master; joined on igs_as_aio_interface.ass_id = igs_as_assessmnt_itm_all.ass_id.
  • IGS_AS_AIO_INTERFACE_NI — non-unique index on USER_ID and BATCH_DATE.
  • FND lookup valuesets for OUTCOME_COMMENT_CODE and ASSESSMENT_TYPE.
  • The Assessment Item Outcome import concurrent program and its validation logic, which consumes these rows and populates ERROR_CODE.
  • Permanent assessment outcome tables in the IGS schema that receive validated rows after import.