Search Results igs_ps_sch_loc_int




Overview
Explore in AI Chat

Overview

The IGS_PS_SCH_LOC_INT table is an interface (staging) table within the Oracle E-Business Suite Student System (IGS) product family. Its documented purpose is to capture scheduler interface unit location data — that is, the physical delivery location information associated with scheduling records before that data is validated and transferred into the core scheduling tables. The table resides in the IGS schema and is documented as VALID in both Oracle EBS 12.1.1 and 12.2.2 environments, where the IGS product remains a standard component of the Student System module.

Interface tables of this type follow a well-established EBS pattern: external systems or bulk-loading processes populate the staging table, and a concurrent program or PL/SQL API subsequently validates the rows and moves them into the production scheduling entities. The table is therefore a transient data container rather than a long-lived transaction store.

From a Data Vault modeling perspective, the mined foreign-key structure suggests a satellite-leaning classification. The table carries a single surrogate primary key and one foreign key to a parent interface table, which is characteristic of a descriptive satellite attached to a parent hub or link. This classification is a modeling heuristic only and does not describe how the table is physically implemented in EBS.

Key Information Stored

The table contains 13 documented columns. The most significant are:

The only business-key candidate documented is the primary key itself; no additional unique indexes are defined on the descriptive columns, which permits duplicate-location staging errors to be detected at validation time rather than at insert time.

Common Use Cases and Queries

Typical usage centers on pre-validation reporting and error reconciliation. A frequent pattern is joining the location interface rows to their parent pattern rows to confirm that every staged location has a valid scheduling pattern:

  • Orphan detection: SELECT l.INT_LOC_ID, l.INT_PAT_ID FROM IGS.IGS_PS_SCH_LOC_INT l WHERE NOT EXISTS (SELECT 1 FROM IGS.IGS_PS_SCH_PAT_INT p WHERE p.INT_PAT_ID = l.INT_PAT_ID);
  • Location inventory: SELECT LOCATION_CODE, BUILDING_CODE, ROOM_CODE, COUNT(*) FROM IGS.IGS_PS_SCH_LOC_INT GROUP BY LOCATION_CODE, BUILDING_CODE, ROOM_CODE;
  • Load audit: SELECT CREATED_BY, TRUNC(CREATION_DATE), COUNT(*) FROM IGS.IGS_PS_SCH_LOC_INT GROUP BY CREATED_BY, TRUNC(CREATION_DATE);

These queries support batch-load monitoring, rejection analysis, and reconciliation reporting before the scheduler import process runs. After successful import, rows are typically purged or archived.

Related Objects

  • IGS_PS_SCH_PAT_INT — the parent interface table, joined via INT_PAT_ID = INT_PAT_ID. This is the documented FK relationship and the primary integration dependency.
  • IGS_PS_SCH_LOC_INT_PK — the primary key index on INT_LOC_ID, essential for efficient row-level lookups during validation.
  • The core scheduling location table (commonly referenced as IGS_PS_SCH_LOC) — the production target that receives validated rows from this interface staging table.
  • The scheduler import concurrent program and its PL/SQL validation package, which read from IGS_PS_SCH_LOC_INT during processing.
  • Standard EBS audit and error-reporting objects that reference the who-columns for load tracing.