Results for “igs_as_gaa_sub_hist”

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

Overview

IGS_AS_GAA_SUB_HIST is a transactional history table within the Oracle E-Business Suite Student System (IGS) module, which is classified as obsolete in Oracle EBS 12.1.1 and 12.2.2. The table records the submission history of Grades and Attendance (GAA) activity for unit sections, preserving a point-in-time audit trail each time a grade or attendance submission is transmitted or processed for a given student, unit offering option, grading period, and submission type. Its role is fundamentally historical and evidentiary: rather than holding the current state of a submission, it captures discrete submission events keyed by the person, the unit offering option, the submission timestamp, and the submission category.

Under the heuristic Data Vault classification supplied in the metadata, this object is modeled as a link. That classification is consistent with its structure: the table sits at the intersection of two principal business entities — the party (student) and the unit offering option (section) — and its primary key is composed of foreign key references plus a descriptive discriminator and a date. It therefore behaves as an associative or intersection object recording the occurrence of a relationship event rather than as a hub of a single entity or a satellite of descriptive attributes.

Key Information Stored

The table is documented with eleven physical columns. The most significant are described below.

• PERSON_ID — Identifies the student (party) for whom the submission was made. It forms part of the composite primary key and carries a foreign key to HZ_PARTIES.
• UOO_ID — Identifies the unit offering option (the specific section offering) to which the submission relates. It is also part of the composite primary key and references IGS_PS_UNIT_OFR_OPT_ALL.
• SUBMITTED_DATE — The date and time the submission was made. It is a constituent of the primary key, allowing multiple submission events to be tracked per person and section over time.
• SUBMISSION_TYPE — Classifies the nature of the submission (for example, the category of grades or attendance data transmitted) and completes the composite primary key.
• GRADING_PERIOD_CD — Identifies the grading period associated with the submission, providing the academic timeframe context.
• SUBMISSION_STATUS — Records the outcome or state of the submission event (such as submitted, accepted, or rejected), which is the primary field used to determine whether a submission succeeded.
• CREATED_BY, CREATION_DATE, LAST_UPDATED_BY, LAST_UPDATE_DATE, LAST_UPDATE_LOGIN — Standard Oracle EBS WHO-column audit attributes recording the user and timestamps of insert and last modification.

The surrogate primary key is defined as IGS_AS_GAA_SUB_HIST_PK, composed of PERSON_ID, SUBMITTED_DATE, UOO_ID, and SUBMISSION_TYPE. Because the key embeds a natural business date and a type discriminator alongside the entity references, there is no separate system-generated surrogate identifier; the primary key is itself a composite business key drawn from the two foreign entities plus the event attributes.

Common Use Cases and Queries

Because the table records submission events, its principal reporting uses are audit reconstruction, compliance evidence, and reconciliation of grades and attendance submissions against the sections and students they concern. Typical patterns include retrieving the complete submission history for a person across a grading period, or isolating failed submissions by status for remediation.

A representative query returns the submission trail for a student:

• SELECT person_id, uoo_id, submitted_date, submission_type, submission_status, grading_period_cd FROM igs_as_gaa_sub_hist WHERE person_id = :p_person_id ORDER BY submitted_date DESC;

Another common pattern filters by status to support exception reporting and re-submission processing:

• SELECT uoo_id, submission_type, grading_period_cd, submission_status FROM igs_as_gaa_sub_hist WHERE submission_status = :p_status AND submitted_date BETWEEN :p_start AND :p_end;

Where duplicate or repeated submissions must be detected, the composite key of PERSON_ID, SUBMITTED_DATE, UOO_ID, and SUBMISSION_TYPE supports aggregation and distinct counting. Note that the metadata states the table is not implemented in the reference database, so coverage in any given Oracle EBS 12.1.1 or 12.2.2 instance should be verified before reliance.

Related Objects

The documented relationships center on the two foreign dependencies embedded in the primary key, supplemented by the unit offering entity that carries the section context.

• HZ_PARTIES — Referenced via IGS_AS_GAA_SUB_HIST.PERSON_ID; supplies the party identity of the student associated with each submission event.
• IGS_PS_UNIT_OFR_OPT_ALL — Referenced via IGS_AS_GAA_SUB_HIST.UOO_ID; supplies the unit offering option (section) descriptor for the submission.
• IGS_AS_GAA_SUB_HIST_PK — The primary key constraint spanning PERSON_ID, SUBMITTED_DATE, UOO_ID, and SUBMISSION_TYPE, which enforces uniqueness of each submission event.

The table itself, IGS_AS_GAA_SUB_HIST, serves as the dependent side of both foreign keys, meaning its rows cannot exist without a corresponding party and unit offering option. Query design should therefore join to HZ_PARTIES and IGS_PS_UNIT_OFR_OPT_ALL to resolve student names and section identifiers, since this table stores only the identifiers and the submission event attributes. As the object is designated obsolete within the Oracle EBS Student System, consumers should treat it as a legacy audit structure and confirm current implementation status in the target environment before building reporting or integration logic upon it.