Search Results igs_ps_sch_hdr_int_all




Overview
Explore in AI Chat

Overview

IGS_PS_SCH_HDR_INT_ALL is a transactional interface table within the Oracle E-Business Suite Student System (IGS) product, owned by the IGS schema. It functions as the master header store for the Scheduling Interface, capturing the top-level control record for each scheduling interface transaction processed through the institution's student information system. In Oracle EBS 12.1.1 and 12.2.2, this table serves as the staging and audit anchor for bulk scheduling operations, including pattern and use-case assignments that are subsequently exploded into detail records.

From a heuristic Data Vault modeling perspective, the metadata classifies this object as hub-leaning, since the TRANSACTION_ID primary key acts as a durable business key representing a single scheduling interface event, and the table is referenced by multiple dependent child tables through that same identifier. Administrators and developers should treat it as the central reference point for all child rows belonging to a scheduling interface run.

Key Information Stored

The table contains 13 documented columns in ETRM 12.1.1. The most operationally significant are:

  • TRANSACTION_ID — the primary key (IGS_PS_SCH_HDR_INT_PK) and unique-index candidate (IGS_PS_SCH_HDR_INT_ALL_U1); it uniquely identifies each scheduling interface transaction and is propagated to all child interface tables.
  • ORIGINATOR — identifies the source system or user that submitted the scheduling interface request.
  • REQUEST_DATE — the date the interface request was raised, used for audit trails and aging analysis.
  • REQUEST_ID — the concurrent request identifier, linking the header to the Oracle EBS concurrent manager job that processed it.
  • PROGRAM_APPLICATION_ID — the application owning the concurrent program that generated the record.
  • PROGRAM_ID — the concurrent program definition identifier.
  • PROGRAM_UPDATE_DATE — the timestamp of the last concurrent program update associated with the request.
  • ORG_ID — the operating unit or organization context, enforcing multi-org data segregation.
  • CREATED_BY, CREATION_DATE — standard who-columns capturing the creating user and timestamp.
  • LAST_UPDATED_BY, LAST_UPDATE_DATE, LAST_UPDATE_LOGIN — standard audit columns tracking the most recent modification.

TRANSACTION_ID is the surrogate primary key, while the unique index IGS_PS_SCH_HDR_INT_ALL_U1 reinforces it as the business-key candidate for the interface hub.

Common Use Cases and Queries

Typical use cases involve monitoring the status of scheduling interface submissions, reconciling child pattern and use-case interface rows back to a header, and troubleshooting failed concurrent requests. A representative query joining the header to its request metadata is:

  • SELECT h.transaction_id, h.originator, h.request_date, h.request_id FROM igs.igs_ps_sch_hdr_int_all h WHERE h.org_id = :org_id ORDER BY h.request_date DESC;
  • Identify interface rows processed by a specific concurrent request: SELECT * FROM igs.igs_ps_sch_hdr_int_all WHERE request_id = :request_id;
  • Audit recalculation: SELECT transaction_id, created_by, creation_date, last_updated_by, last_update_date FROM igs.igs_ps_sch_hdr_int_all WHERE last_update_date >= :from_date;

Reporting scenarios include scheduling throughput metrics by originator, error diagnosis by correlating REQUEST_ID with FND_CONCURRENT_REQUESTS, and multi-org filtering using ORG_ID.

Related Objects

The table is referenced by dependent interface entities through TRANSACTION_ID foreign keys:

  • IGS_PS_SCH_PAT_INT — pattern interface detail; joins on TRANSACTION_ID = IGS_PS_SCH_HDR_INT_ALL.TRANSACTION_ID.
  • IGS_PS_SCH_USEC_INT_ALL — use-case assignment interface detail; joins on TRANSACTION_ID = IGS_PS_SCH_HDR_INT_ALL.TRANSACTION_ID.

Additional related objects commonly used in reconciliation and diagnostics include the FND_CONCURRENT_REQUESTS and FND_CONCURRENT_PROGRAMS views (via REQUEST_ID, PROGRAM_APPLICATION_ID, and PROGRAM_ID), and the base scheduling tables in the IGS scheduling family that receive the exploded data after interface validation.