Search Results igs_as_due_dt_sumry

Overview

The IGS_AS_DUE_DT_SUMRY table is a Student System (IGS) object within Oracle E-Business Suite that stores summarized assessment due-date information. It consolidates counts related to assignment submissions, overdue items, and approved extensions across defined time buckets, allowing institutions to track assessment deadlines and submission behavior without aggregating the full detail set of assessment records on demand. The table resides in the IGS schema, is marked VALID under both 12.1.1 and 12.2.2 documentation, and is described in the ETRM as representing an "assessment due dates summary." It is populated largely through concurrent-program processing rather than through direct end-user data entry, which is evidenced by the presence of the standard Oracle request columns (REQUEST_ID, PROGRAM_APPLICATION_ID, PROGRAM_ID, PROGRAM_UPDATE_DATE).

From a Data Vault modeling perspective, the mined heuristic classification for this object is standalone. Because no parent hub or link dependency is asserted through the documented foreign keys and the summary row is keyed on its own surrogate identifier, the object is best treated as a self-contained snapshot or aggregate record rather than a hub, link, or satellite in a conventional Data Vault construct. Practitioners modeling this table downstream should therefore model it as a fact-like or snapshot entity keyed by its surrogate, with a degenerate reference to the assessment item.

Key Information Stored

The documented physical schema for 12.1.1 lists 26 columns. The most significant, grouped by purpose, are:

• AT_ID — the surrogate primary key, enforced through IGS_AS_DUE_DT_SUMRY_PK and the unique index IGS_AS_DUE_DT_SUMRY_U1. It is the single-column business-key candidate for the table.
• ASS_ID — the assessment identifier; this column carries the only documented foreign key, referencing IGS_AS_ASSESSMNT_ITM_ALL.
• SESSION_ID, UNIT_CD, VERSION_NUMBER — identify the academic session, unit (course/module), and version to which the summary pertains.
• CAL_TYPE, CI_SEQUENCE_NUMBER, UNIT_MODE — describe the calendar type, calendar-instance sequence, and mode of delivery associated with the unit offering.
• OWNER_ORG_UNIT_CD, OWNER_OU_START_DT — the owning organization unit and its effective start date, supporting reporting by faculty or department.
• WEEK_ENDING_DT — the reporting period endpoint against which the due-date counts are bucketed.
• BASE_COUNT — the base population count of assessments due in the period.
• EXPECTED_OVERDUE_COUNT — assessments past due relative to expectations.
• ONE_WEEK_EXTENSION_COUNT, TWO_WEEK_EXTENSION_COUNT, THREE_WEEK_PLUS_EXTNSN_COUNT — distribution of approved extensions by duration band.
• RECEIVED_COUNT — submissions actually received in the period.
• Audit and program columns — LAST_UPDATE_DATE, CREATED_BY, CREATION_DATE, LAST_UPDATED_BY, REQUEST_ID, PROGRAM_APPLICATION_ID, PROGRAM_ID, PROGRAM_UPDATE_DATE.

Common Use Cases and Queries

The table typically supports deadline-compliance reporting, extension analytics, and submission-trend dashboards. A representative query aggregates counts per unit and week:

• SELECT unit_cd, week_ending_dt, SUM(base_count), SUM(received_count) FROM igs_as_due_dt_sumry WHERE session_id = :p_session GROUP BY unit_cd, week_ending_dt;
• To profile extensions by band: SELECT unit_cd, SUM(one_week_extension_count), SUM(two_week_extension_count), SUM(three_week_plus_extnsn_count) FROM igs_as_due_dt_sumry GROUP BY unit_cd;
• To identify overdue hotspots: filter expected_overdue_count > received_count by OWNER_ORG_UNIT_CD.

Because the data is populated by concurrent programs, refresh timing must be verified via REQUEST_ID and PROGRAM_UPDATE_DATE before relying on it for real-time reporting. Joining to IGS_AS_ASSESSMNT_ITM_ALL on ASS_ID retrieves full assessment context where required.

Related Objects

The following objects are most relevant to this table:

• IGS_AS_ASSESSMNT_ITM_ALL — referenced through ASS_ID; the primary assessment item definition.
• IGS_AS_ASSR1020_TMP_PK — a documented primary key constraint sharing AT_ID, suggesting a related temporary staging structure used during the summary build process.
• IGS_AS_DUE_DT_SUMRY_PK / IGS_AS_DUE_DT_SUMRY_U1 — the primary key constraint and unique index on AT_ID.
• Standard Oracle request and program tables (FND_CONCURRENT_REQUESTS, FND_PROGRAM) — joined via REQUEST_ID and PROGRAM_ID for run-history and lineage.
• IGS academic session and unit tables — joined via SESSION_ID and UNIT_CD to resolve institutional context for reporting.