Search Results igs_as_aio_interface

Overview

The IGS_AS_AIO_INTERFACE table is a staging and interface table within the Oracle E-Business Suite IGS – Student System product. Its documented purpose in release 12.1.1 and 12.2.2 is to serve as the Assessment Item Outcome Interface Table, primarily used to import assessment item grade details captured through Oracle Web ADI (Web Applications Desktop Integrator) spreadsheet-based entry.

In the standard assessment grading workflow, instructors or administrators frequently enter large volumes of student grades through Web ADI rather than online forms. Those spreadsheets are uploaded into this interface table, validated, and subsequently processed by concurrent programs that create or update the corresponding assessment outcome records in the base assessment tables. The interface table therefore acts as a controlled staging area that decouples user data entry from the final transactional writes, enabling validation, error reporting, and correction before commit.

From a data modeling perspective, the heuristic Data Vault classification mined from the foreign key structure identifies this table as standalone. This suggests that, unlike a typical satellite or link table, IGS_AS_AIO_INTERFACE does not participate in an interlocking hub-and-link constellation through declared FKs — its only documented foreign key relationship is a reference to the assessment item definition. It is best modeled as a transient staging entity rather than a subject-oriented Data Vault structure.

Key Information Stored

The table contains 51 documented columns in release 12.1.1, reflecting both the business data being imported and the standard Oracle interface/audit scaffolding. The most significant columns are:

• ASS_ID – The assessment item identifier; the sole documented foreign key, referencing IGS_AS_ASSESSMNT_ITM_ALL. This anchors the imported grade to the correct assessment item.
• PERSON_NUMBER and ANONYMOUS_ID – Identify the student whose grade is being imported. PERSON_NUMBER is the standard HR/Student Systems person identifier; ANONYMOUS_ID supports anonymous marking scenarios.
• COURSE_CD, UNIT_CD, CAL_TYPE, CI_SEQUENCE_NUMBER, UNIT_CLASS, LOCATION_CD – The academic delivery context identifying the course, unit, calendar type, version sequence, class, and location.
• ALTERNATE_CODE – Alternate assessment item reference used for reconciliation.
• GRADE and MARK – The actual outcome being imported, recorded as a grade code and/or a numeric mark.
• ASSESSMENT_TYPE – Classifies the assessment for validation and routing.
• OUTCOME_COMMENT_CODE and REFERENCE – Supporting outcome commentary and a free-reference field.
• WAIVED_FLAG, PENALTY_APPLIED_FLAG – Flags controlling special handling of the outcome.
• DUE_DT, OVERRIDE_DUE_DT, SUBMITTED_DATE – Dates governing lateness and submission tracking.
• UOO_ID – Identifier linking to the unit occurrence offering.
• ERROR_CODE and CONTEXT – Reserved for the interface validation/processing program to flag rows that fail validation and to carry processing context.

Standard audit and descriptive flexfield columns (CREATED_BY, CREATION_DATE, LAST_UPDATED_BY, LAST_UPDATE_DATE, LAST_UPDATE_LOGIN, ATTRIBUTE_CATEGORY, ATTRIBUTE1 through ATTRIBUTE20) are present, as is USER_ID and BATCH_DATE for batch identification.

The documented metadata does not identify a single-column surrogate primary key; the table is used as a row-based staging structure, so uniqueness is effectively enforced by the combination of business attributes (person, assessment item, and context) rather than a documented surrogate key.

Common Use Cases and Queries

Typical use cases include monitoring pending Web ADI uploads, diagnosing rows that failed validation, and auditing the source of imported grades before processing. A common diagnostic query retrieves all rows flagged with an error for a batch:

SELECT person_number, ass_id, grade, mark, error_code, context
FROM   igs_as_aio_interface
WHERE  batch_date = :p_batch_date
AND    error_code IS NOT NULL;

Another common pattern reconciles imported marks against the assessment item master:

SELECT i.person_number, i.grade, i.mark, a.name
FROM   igs_as_aio_interface i,
       igs_as_assessmnt_itm_all a
WHERE  i.ass_id = a.ass_id
AND    i.user_id = :p_user_id;

Reporting scenarios include grade import volume by batch, exception rate analysis (rows with ERROR_CODE), and lateness analysis using SUBMITTED_DATE against DUE_DT. Because the table is transient, purge procedures typically run after successful processing.

Related Objects

• IGS_AS_ASSESSMNT_ITM_ALL – Referenced by the foreign key IGS_AS_AIO_INTERFACE.ASS_ID on the ASS_ID column; the assessment item master against which imported outcomes are validated and posted.
• IGS_AS_AIO_IFACE_PROC (processing program) – The concurrent program/PLSQL process that reads interface rows, validates them, posts valid outcomes, and writes ERROR_CODE for rejected rows.
• IGS_AS_ASSESSMNT_OUTCOMES – The base outcome table to which validated interface rows are ultimately written during processing.
• IGS_AS_STUDENT_UNITS / UNIT occurrence tables – Related via UNIT_CD, CAL_TYPE, CI_SEQUENCE_NUMBER, and UOO_ID to resolve the student unit occurrence.
• HZ_PERSON / HR person structures – Referenced conceptually through PERSON_NUMBER to identify the student.

Together these objects form the Web ADI grading import pipeline: data entry, staging, validation, and final posting into the Student System assessment outcome model.