Search Results igs_ps_sch_int_all




Overview
Explore in AI Chat

Overview

IGS_PS_SCH_INT_ALL is an interface staging table in the Oracle E-Business Suite Student System (IGS) product family, owned by the IGS schema. As its ETRM description states, it "holds the interface objects for scheduler" — meaning it serves as the inbound repository for scheduling data imported from external sources (typically a legacy student information system, a departmental timetabling tool, or a flat-file batch feed) before that data is validated and propagated to the live scheduling tables in EBS.

The table is populated by a batch import process that writes a TRANSACTION_ID for each run, then validates each row and sets IMPORT_DONE_FLAG and ABORT_FLAG accordingly. Rows that pass validation become the basis for unit section occurrences, instructor assignments, facility bookings, and preference records. Any row that fails produces an ERROR_TEXT value. Because the interface layer sits between the external feed and the transactional scheduler, it is one of the highest-risk tables during student-system implementations and integration testing.

From a Data Vault modeling perspective, the FK structure suggests this table behaves as a hub-leaning entity: INT_OCCURS_ID is a distinct business key, and numerous dependent tables reference it. It can reasonably be modeled as a hub (occurrence) with satellites for the descriptive attributes, though this is a heuristic suggestion rather than a prescribed design.

Key Information Stored

Common Use Cases and Queries

The primary use case is post-import reconciliation: an integration specialist inspects staged rows to determine whether an external feed was interpreted correctly. A typical diagnostic query lists failed rows for a given run:

SELECT int_occurs_id, unit_cd, unit_section_occurrence_id, schedule_status, error_text, transaction_id
FROM igs.igs_ps_sch_int_all
WHERE import_done_flag = 'N' OR abort_flag = 'Y';

To verify that an occurrence reached the scheduler with the expected meeting pattern, developers join the interface row to its child facility and instructor rows on INT_OCCURS_ID:

SELECT i.unit_cd, i.start_time, i.end_time, i.monday, i.tuesday, f.building_code, f.room_code
FROM igs.igs_ps_sch_int_all i, igs.igs_ps_sch_faclt_all f
WHERE i.int_occurs_id = f.int_occurs_id;

Reporting uses include auditing which unit sections have TBA_STATUS flagged, quantifying scheduling conflicts, and measuring enrollment variance by comparing ENROLLMENT_MAXIMUM against ENROLLMENT_ACTUAL per building. During cutover, DBAs also purge completed interface runs by TRANSACTION_ID to keep the staging table from growing unboundedly.

Related Objects