Search Results igs_ps_sch_int

Overview

The IGS_PS_SCH_INT view is a component of the Oracle E-Business Suite Student System (IGS) module, which is documented as obsolete in Oracle EBS 12.1.1 and 12.2.2. The view functions as an integration staging interface for course schedule data, exposing a flat, denormalized projection of scheduling information used during data exchange between the Student System and external scheduling, timetabling, or legacy feeder systems. Its name reflects this purpose: "PS" denotes the Public Sector / Student System lineage, "SCH" references schedule, and "INT" signifies an integration or interface construct.

The view selects from IGS_PS_SCH_INT_ALL, applying the standard multi-organization row-level restriction pattern (ROW_ID plus ORG_ID). Because the object is not implemented in the current database as noted in the ETRM metadata, deploying or referencing it requires verification against the specific environment. In reporting terms, the view is typically queried during interface reconciliation, import validation, and error-diagnostic reporting. The prominent schedule_status column, which is the subject of the user's search, is central to these activities—it indicates the processing state of each schedule interface record, allowing administrators to isolate records that succeeded, failed, or remain pending.

Underlying Base Objects

According to the ETRM view text, IGS_PS_SCH_INT is defined exclusively over the base table IGS_PS_SCH_INT_ALL. The view is a simple projection with no joins, unions, or aggregations; every column is drawn directly from the underlying table using the TAB alias. No additional referenced base objects are documented. This one-to-one relationship means the view inherits the table's partitioning by ORG_ID and its integration lifecycle columns, including CREATED_BY, CREATION_DATE, LAST_UPDATED_BY, LAST_UPDATE_DATE, and LAST_UPDATE_LOGIN, which support audit and interface purge routines.

Key Columns

The view exposes a broad set of scheduling and interface attributes. The most operationally significant columns include:

• SCHEDULE_STATUS — the processing/validation state of the integration record, used to drive error handling.
• ERROR_TEXT — descriptive message populated when validation fails.
• TRANSACTION_TYPE / TRANSACTION_ID — identify the nature and identity of the inbound transaction.
• ABORT_FLAG / IMPORT_DONE_FLAG — flags indicating whether processing was aborted or completed.
• UNIT_CD, VERSION_NUMBER, UNIT_TITLE — the academic unit being scheduled.
• UNIT_SECTION_OCCURRENCE_ID / UOO_ID / OCCURRENCE_IDENTIFIER — keys linking the row to a specific occurrence.
• Day-of-week markers (MONDAY through SUNDAY), START_TIME, END_TIME — the meeting pattern.
• ENROLLMENT_MAXIMUM / ENROLLMENT_ACTUAL — capacity and load figures.
• INSTRUCTOR_ID, SURNAME, GIVEN_NAMES, MIDDLE_NAME — instructor identity attributes.
• Building, room, and location fields — both dedicated and preferred assignments, with accompanying IDs.
• ORG_ID — the multi-organization discriminator applied by the view logic.

Common Use Cases and Queries

Typical usage centers on monitoring interface health and resolving failed records. The schedule_status column is the principal filter. A representative diagnostic query follows:

• SELECT schedule_status, transaction_id, unit_cd, error_text FROM igs_ps_sch_int WHERE org_id = :p_org_id AND schedule_status = :p_status;
• SELECT unit_cd, occurrence_identifier, monday, start_time, end_time, building_code, room_code FROM igs_ps_sch_int WHERE import_done_flag = 'Y' AND abort_flag = 'N';
• SELECT COUNT(*), schedule_status FROM igs_ps_sch_int GROUP BY schedule_status;

These support reconciliation summaries, pending-record reviews, and error triage. Because the module is obsolete, organizations should confirm the view's presence and status in their specific 12.1.1 or 12.2.2 instance before relying on it.