Results for “igs_da_out_stdt_spt”

AI-generated from documented ETRM metadata — verify critical details on the linked pages.

Overview

IGS_DA_OUT_STDT_SPT is a student-records table in the Oracle E-Business Suite IGS – Student System product family, now classified as Obsolete in the ETRM 12.1.1 / 12.2.2 documentation set. The table stores outgoing (persisted) information about every sport in which a student referenced by a Degree Audit request is involved. In practice it acts as an intersection entity within the Degree Audit extraction pipeline: the Degree Audit process selects a batch of students (IGS_DA_REQ_STDNTS), and this table denormalizes the sport affiliations of those students so they can be exported, printed, or fed to a downstream audit engine alongside the academic record.

The object occupies the analytical "satellite" layer of the Student System data model. Following the heuristic Data Vault classification supplied in the metadata, the table is satellite-leaning: it hangs off the Degree Audit request/student link and captures descriptive, non-key context (SPORT_NAME, SPORT_DESCRIPTION) plus standard audit/WHO columns, rather than representing an independent business concept. Note the documentation explicitly records "Not implemented in this database," meaning the physical table may not exist in every environment — a common situation for deprecated or optional IGS components.

Key Information Stored

The documented physical schema comprises 10 columns under the IGS schema owner. The most significant are:

• BATCH_ID — Identifier of the Degree Audit processing batch that the row belongs to; the leading column of the primary key and the FK back to the student request snapshot.
• PERSON_ID — The student (person) the sport record is attached to; second segment of the primary key and the join to the student request row.
• SPORT_SEQ_NUM — Sequence discriminator allowing a single student to carry multiple sport entries; the third key segment.
• SPORT_NAME — The short code/name of the sport activity associated with the student.
• SPORT_DESCRIPTION — The descriptive text for that sport, used for reporting and printed audit output.
• CREATION_DATE / CREATED_BY — Standard WHO creation audit columns.
• LAST_UPDATE_DATE / LAST_UPDATED_BY / LAST_UPDATE_LOGIN — Standard WHO update audit columns.

The surrogate-style composite primary key, IGS_DA_OUT_STDT_SPT_PK, is defined as (BATCH_ID, PERSON_ID, SPORT_SEQ_NUM). A unique index, IGS_DA_OUT_STDT_SPT_U1, is declared over the same three columns, confirming the business-key candidate. There is no separate meaningless surrogate column; instead, the natural/GUID key and the business key coincide. The only documented foreign key is BATCH_ID referencing IGS_DA_REQ_STDNTS.

Common Use Cases and Queries

Because the table is a snapshot-style staging area, queries typically run in one of three modes: extract for the audit file, reconciliation between request and output, and sport-participation reporting for batch populations.

To reconstruct a student's sports for a given batch:

SELECT s.batch_id, s.person_id, s.sport_seq_num,
       s.sport_name, s.sport_description
  FROM   igs_da_out_stdt_spt s
 WHERE   s.batch_id = :p_batch_id
   AND   s.person_id = :p_person_id
 ORDER BY s.sport_seq_num;

To validate that every extracted sport row corresponds to a requested student (orphan check):

SELECT s.batch_id, s.person_id
  FROM   igs_da_out_stdt_spt s
  LEFT JOIN igs_da_req_stdnts r
    ON r.batch_id = s.batch_id
   AND r.person_id = s.person_id
 WHERE  r.person_id IS NULL;

Aggregate reporting by sport name is also common when analyzing participation across a Degree Audit run:

SELECT sport_name, COUNT(*) student_count
  FROM   igs_da_out_stdt_spt
 WHERE  batch_id = :p_batch_id
 GROUP BY sport_name
 ORDER BY student_count DESC;

Typical consumers are Degree Audit output programs, registrar reporting extracts, and integration interfaces that pipe sport data into third-party student information systems.

Related Objects

• IGS_DA_REQ_STDNTS — Parent table for the Degree Audit request/student set; join on IGS_DA_REQ_STDNTS.BATCH_ID and PERSON_ID to IGS_DA_OUT_STDT_SPT.BATCH_ID and PERSON_ID. This is the sole documented FK relationship and the primary access path.
• IGS_DA_OUT_* sibling output tables (e.g., other outgoing Degree Audit entities keyed by BATCH_ID/PERSON_ID) — read together to assemble a complete audit extract.
• HZ_PARTIES / PERSON tables — The underlying person entity behind PERSON_ID, used to resolve student names for reports.
• IGS_DA_BATCHES (or equivalent batch definition object) — Provides header/batch context for the extracted rows.
• Degree Audit concurrent programs — The extract processes that populate and consume the table.

Given the obsolete status and the "Not implemented" note, DBAs should verify existence via DBA_TABLES before building dependent logic, and treat the table as legacy when planning upgrades to 12.2.2 or migration off the IGS Student System.