Search Results int_loc_id

Overview

IGS.IGS_PS_SCH_LOC_INT is an interface (staging) table in the Oracle EBS Student Systems / Student Records (IGS) product family. It holds location detail — building and room information — that has been set up against a Unit Offering Pattern and is staged for the scheduling process. Per the ETRM metadata, its display name is Export Scheduling Unit Offering Pattern Location Detail, and its documented business entity category is IGS_UNIT.

The table functions as an inbound/outbound scheduling interface layer. Data loaded here is cross-referenced back to IGS_PS_SCH_PAT_INT (the Unit Offering Pattern interface) and consumed by the scheduling routines that create unit section and unit section occurrence level records. Its production (non-interface) counterpart is IGS_PS_UNIT_LOCATION, which is the only table that should be treated as the system of record once scheduling has completed.

The heuristic Data Vault classification mined from the foreign key structure is satellite-leaning. In practical modeling terms, this is consistent: the row carries descriptive attributes (location, building, room codes and descriptions) that qualify a parent scheduling entity, rather than introducing a new independent business key of its own. The natural parent key is INT_PAT_ID, which ties each location detail row to its unit offering pattern.

Key Information Stored

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

• INT_LOC_ID — surrogate primary key of the interface table, enforced by unique index IGS_PS_SCH_LOC_INT_PK. It is the unique identifier for each Unit Offering Pattern location in the Scheduler Interface. No business meaning beyond row identity; it should not be used for business matching.
• INT_PAT_ID — the foreign key to IGS.IGS_PS_SCH_PAT_INT. This is the effective business-key candidate for grouping: every location row belongs to one unit offering pattern in the interface.
• LOCATION_CODE (VARCHAR2 10) and LOCATION_DESCRIPTION (VARCHAR2 60) — the location code and description corresponding to the unit version of the unit offering pattern.
• BUILDING_CODE (VARCHAR2 10) and BUILDING_DESCRIPTION (VARCHAR2 80) — building-level detail for the location.
• ROOM_CODE (VARCHAR2 10) and ROOM_DESCRIPTION (VARCHAR2 80) — room-level detail, the finest grain of physical placement recorded on the row.
• CREATED_BY, CREATION_DATE, LAST_UPDATED_BY, LAST_UPDATE_DATE, LAST_UPDATE_LOGIN — standard Oracle "Who" audit columns used for change tracking and reconciliation of the staging load.

All ten non-audit/audit attributes above are the operationally relevant ones; the table deliberately carries no scheduling outcome fields, which are written downstream.

Common Use Cases and Queries

Typical scenarios include validating a scheduling load before it is committed to production, reconciling interface rows against the pattern header, and diagnosing rows that failed to generate unit sections. Because the table is small and keyed on INT_LOC_ID, joins are inexpensive.

• Count location rows per pattern — group by INT_PAT_ID to detect patterns with missing location detail: SELECT INT_PAT_ID, COUNT(*) FROM IGS.IGS_PS_SCH_LOC_INT GROUP BY INT_PAT_ID HAVING COUNT(*) = 0;
• List location detail for a given pattern — SELECT INT_LOC_ID, LOCATION_CODE, BUILDING_CODE, ROOM_CODE FROM IGS.IGS_PS_SCH_LOC_INT WHERE INT_PAT_ID = :p_pattern_id;
• Join to the pattern interface to see the complete picture — SELECT p.INT_PAT_ID, l.LOCATION_CODE, l.BUILDING_CODE, l.ROOM_CODE FROM IGS.IGS_PS_SCH_PAT_INT p, IGS.IGS_PS_SCH_LOC_INT l WHERE p.INT_PAT_ID = l.INT_PAT_ID;
• Recent staging activity — filter on CREATION_DATE or LAST_UPDATE_DATE to audit what was loaded in a given scheduling run.
• Compare to production — diff LOCATION_CODE/BUILDING_CODE/ROOM_CODE against IGS_PS_UNIT_LOCATION to confirm the interface was fully propagated.

Related Objects

• IGS.IGS_PS_SCH_PAT_INT — parent Unit Offering Pattern interface table; joined via INT_PAT_ID → INT_PAT_ID. This is the primary dependency.
• IGS.IGS_PS_UNIT_LOCATION — production counterpart; the target of the scheduling load that consumes this interface data.
• Unit section and unit section occurrence tables (IGS_PS_UNIT_SECTION and related occurrence tables) — created from the location detail originating here.
• IGS.IGS_PS_SCH_LOC_INT_PK — the unique index on INT_LOC_ID that enforces primary key uniqueness.
• The scheduling/concurrent program that populates and processes IGS_PS_SCH_* interface tables, which consumes this row set during the export scheduling process.

The table is a public-scope, active-lifecycle object stored in APPS_TS_TX_DATA with its index in APPS_TS_TX_IDX. Because it is an interface table, direct DML should be performed only through the supported scheduling programs; ad hoc updates can desynchronize the interface from IGS_PS_UNIT_LOCATION.