Search Results expected_overdue_count
Overview
The IGS.IGS_AS_DUE_DT_SUMRY table is a summarization structure within the Oracle E-Business Suite Student Systems (IGS) schema, which supports the assessment and examination tracking functionality of the Oracle Student System. The table aggregates assessment due date information, capturing the timing and status of student assessment submissions against defined deadlines. Its name—"Due Date Summary"—indicates that it stores pre-computed counts rather than transactional detail, providing a consolidated view of assessment submission behavior by attempt, assessment, and reporting period.
The table is owned by the IGS schema and resides in the APPS_TS_TX_DATA tablespace, which is characteristic of transactional data objects in EBS 12.1.1 and 12.2.2. The documented metadata classifies this object heuristically as standalone within the Data Vault modeling framework, meaning it is not identified as a hub, link, or satellite by the mining heuristics. In practice, the table functions as a satellite-like aggregate attached to the assessment attempt lifecycle, since its grain is defined by AT_ID (attempt identifier) and the assessment identifier ASS_ID.
Key Information Stored
The table contains 26 documented columns. The most significant are summarized below.
- AT_ID – Attempt identifier; the primary key column and the column behind the unique index IGS_AS_DUE_DT_SUMRY_U1. It links each summary row to a specific student assessment attempt.
- SESSION_ID – Identifies the session within the selected examination calendar.
- ASS_ID – Assessment identifier; a foreign key to IGS_AS_ASSESSMNT_ITM_ALL, defining which assessment item the due date summary belongs to.
- UNIT_CD, VERSION_NUMBER, UNIT_MODE – Describe the unit and version under which the assessment is delivered.
- CAL_TYPE, CI_SEQUENCE_NUMBER – Calendar type and calendar instance sequence number, supporting calendar-based reporting.
- OWNER_ORG_UNIT_CD, OWNER_OU_START_DT – Owning organization unit code and its start date, used for organizational rollups.
- WEEK_ENDING_DT – Week ending date; the reporting anchor column. This is the column referenced by the search term "week_ending_dt" and defines the weekly reporting bucket for the summary counts.
- BASE_COUNT – Base count of attempts in the period.
- EXPECTED_OVERDUE_COUNT – Count of assessments expected to be overdue.
- ONE_WEEK_EXTENSION_COUNT, TWO_WEEK_EXTENSION_COUNT, THREE_WEEK_PLUS_EXTNSN_COUNT – Counts of extensions granted at each duration tier.
- RECEIVED_COUNT – Count of assessments received.
- LAST_UPDATE_DATE, CREATED_BY, CREATION_DATE – Standard WHO audit columns.
- REQUEST_ID, PROGRAM_ID, PROGRAM_APPLICATION_ID, PROGRAM_UPDATE_DATE – Concurrent program tracking columns identifying the last program that populated the summary row.
The surrogate primary key is AT_ID, while the unique index IGS_AS_DUE_DT_SUMRY_U1 on AT_ID serves as the business-key candidate constraining one summary row per attempt.
Common Use Cases and Queries
The primary use case is reporting on assessment submission timeliness. Academic administrators query the table to determine, for a given week ending date, how many assessments were received versus overdue, and how many extensions were granted.
A typical query groups by WEEK_ENDING_DT to produce a weekly trend:
SELECT WEEK_ENDING_DT, SUM(BASE_COUNT), SUM(RECEIVED_COUNT), SUM(EXPECTED_OVERDUE_COUNT) FROM IGS.IGS_AS_DUE_DT_SUMRY GROUP BY WEEK_ENDING_DT ORDER BY WEEK_ENDING_DT;
Another common pattern filters by assessment and session to review a specific assessment's performance:
SELECT AT_ID, UNIT_CD, WEEK_ENDING_DT, RECEIVED_COUNT, ONE_WEEK_EXTENSION_COUNT FROM IGS.IGS_AS_DUE_DT_SUMRY WHERE ASS_ID = :ass_id AND SESSION_ID = :session_id;
Because the table is populated by concurrent programs (evidenced by REQUEST_ID and PROGRAM_UPDATE_DATE), reports should account for the last refresh time. The extension count columns also support institutional policy analysis on extension frequency.
Related Objects
The most significant relationship is the foreign key from ASS_ID to IGS.IGS_AS_ASSESSMNT_ITM_ALL, the assessment item master. This join allows the summary counts to be enriched with assessment definitions. Other objects that logically participate in the same domain include the attempt table represented by AT_ID, from which the summary grain is derived, and the calendar/session structures referenced by SESSION_ID and CAL_TYPE. The unique index IGS_AS_DUE_DT_SUMRY_U1 enforces the one-row-per-attempt rule, and the concurrent program identified by PROGRAM_ID is the routine that refreshes the summary. Reporting views and Discoverer workbooks in the Student Systems module frequently join this table to IGS_AS_ASSESSMNT_ITM_ALL to present overdue and extension metrics to academic staff.
-
TABLE: IGS.IGS_AS_DUE_DT_SUMRY
12.1.1
owner:IGS, object_type:TABLE, fnd_design_data:IGS.IGS_AS_DUE_DT_SUMRY, object_name:IGS_AS_DUE_DT_SUMRY, status:VALID,
-
APPS.IGS_AS_DUE_DT_SUMRY_PKG SQL Statements
12.1.1
-
PACKAGE BODY: APPS.IGS_AS_DUE_DT_SUMRY_PKG
12.1.1
-
eTRM - IGS Tables and Views
12.1.1
description: Holds applicant whose records are wrongly available . It is recommended that such applicant records are deleted from the system . It synchronizes with UCAS view 'ivStarW'. ,