Results for “keying_time”

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

Overview

The IGS_AS_INS_GRD_ENTRY table belongs to the IGS (Student System) product family within Oracle E-Business Suite, and is documented as obsolete in the ETRM reference for releases 12.1.1 and 12.2.2. Its documented purpose is to hold temporary information about grade entries — a transient staging structure used during the capture, validation, or import of student grade records before they are committed to permanent academic records. The table resides in the IGS schema and is documented with 23 columns in the 12.1.1 physical schema. ETRM notes that the object is not implemented in this database, meaning it is a legacy or deprecated artifact that may appear in older installations but should not be relied upon in current deployments.

From a modeling perspective, the ETRM heuristic classification of this object is satellite-leaning. This classification is inferred from its foreign key structure, where the table predominantly carries descriptive, time-stamped attributes tied to a parent business entity rather than behaving as a hub (a list of unique business keys) or a link (an association between hubs). Practically, this suggests the table functions as a temporary descriptive container attached to a grading context.

Key Information Stored

The primary key forms the anchor of the record. Two PK definitions are documented: IGS_AS_GRD_ENTRY_TMP_PK and IGS_AS_INS_GRD_ENTRY_PK, both composed of KEYING_WHO, KEYING_TIME, and STUDENT_SEQUENCE. A unique index, IGS_AS_INS_GRD_ENTRY_U1, mirrors the same three columns (KEYING_TIME, KEYING_WHO, STUDENT_SEQUENCE), confirming this triplet as the effective business key rather than a single surrogate column. The KEYING_TIME column — the term the user searched on — records the timestamp at which the grade entry was keyed, while KEYING_WHO captures the operator or process responsible for the entry.

Among the remaining columns, the most significant include:

• PERSON_ID and NAME — identify the student associated with the grade entry.
• COURSE_CD, UNIT_CD, and VERSION_NUMBER — describe the academic unit being graded.
• CAL_TYPE and CI_SEQUENCE_NUMBER — denote the calendar type and calendar instance context.
• MARK, GRADE, GRADING_SCHEMA_CD, and GS_VERSION_NUMBER — capture the assessed result and the grading scheme against which it was evaluated.
• SPECIFIED_GRADE_IND — flags whether the grade was explicitly specified.
• Audit columns CREATED_BY, CREATION_DATE, LAST_UPDATED_BY, LAST_UPDATE_DATE, and LAST_UPDATE_LOGIN — provide standard Oracle who-did-what tracking.

Common Use Cases and Queries

Because the table stores temporary grade-entry data, typical usage centers on auditing the grade-capture workflow and reconciling staged entries before they are promoted to permanent records. A common pattern groups entries by operator and time window to verify batch uploads. For example:

SELECT keying_who, COUNT(*), MIN(keying_time), MAX(keying_time)
FROM   igs_as_ins_grd_entry
GROUP  BY keying_who;

Another frequent scenario validates that every staged row resolves to a valid grading scheme before transfer:

SELECT e.student_sequence, e.mark, e.grade
FROM   igs_as_ins_grd_entry e
WHERE  NOT EXISTS (SELECT 1 FROM igs_as_grd_sch_grade g
                   WHERE g.grading_schema_cd = e.grading_schema_cd);

Reporting use cases include reconciliation of grade disputes by student, monitoring of data-entry productivity via KEYING_TIME and KEYING_WHO, and pre-load quality checks on MARK and GRADE values.

Related Objects

The documented foreign key joins IGS_AS_INS_GRD_ENTRY.GRADING_SCHEMA_CD and IGS_AS_INS_GRD_ENTRY.GS_VERSION_NUMBER and GRADE to the IGS_AS_GRD_SCH_GRADE table, which holds the authoritative definition of valid grades within a grading schema. This is the most significant dependency, as it enforces that temporary entries reference legitimate grade values. Related objects within the IGS academic-records model include the grading schema header tables, the student/unit registration structures referenced indirectly by PERSON_ID and UNIT_CD, and the permanent grade tables to which staged entries are ultimately transferred. Given the object's obsolete status, DBAs should treat any remaining dependency as a legacy integration point and migrate functionality to the supported successor objects defined in the current IGS data model.