Search Results sport_seq_num




Overview
Explore in AI Chat

Overview

The IGS_DA_OUT_STDT_SPT table is a data staging table within the Oracle E-Business Suite (EBS) 12.1.1 and 12.2.2, owned by the IGS (iGrants) product family. Its primary role is to temporarily store outgoing information pertaining to student sports and athletic involvement as part of a batch data extraction or reporting process. The table is explicitly marked as obsolete in the provided documentation, indicating its functionality may have been superseded in later implementations or patches. It resides in the APPS_TS_INTERFACE tablespace, which is typically designated for transient data used in interfaces and batch operations, further underscoring its role as a staging area rather than a permanent transactional repository.

Key Information Stored

The table's structure is designed to capture a list of sports activities for specific students within a given batch request. The primary key is a composite of BATCH_ID, PERSON_ID, and SPORT_SEQ_NUM, ensuring uniqueness for each sport entry per student per extraction batch. Key columns include:

  • BATCH_ID: Links the record to a specific data extraction request.
  • PERSON_ID: The unique identifier for the student.
  • SPORT_SEQ_NUM: A programmatically assigned sequence number that orders multiple sports for a single student within the batch, forming part of the primary key.
  • SPORT_NAME and SPORT_DESCRIPTION: Capture the name and a descriptive detail of the athletic activity.
  • Standard WHO Columns (CREATION_DATE, CREATED_BY, etc.): Provide audit trail information for the record's creation and last update.
The SPORT_SEQ_NUM is critical for correctly ordering and identifying individual sport records when a student participates in multiple activities.

Common Use Cases and Queries

This table facilitates the batch extraction of student co-curricular data, likely for reporting or integration with external systems. A common use case would be generating a comprehensive list of all students and their associated sports for a given data request batch. A typical query would join this table to the related batch control table using BATCH_ID to filter and extract data for a specific report run. For example, to retrieve all sport data for a specific batch ID (e.g., 1001), ordered by student and sport sequence:

SELECT spt.PERSON_ID, spt.SPORT_SEQ_NUM, spt.SPORT_NAME, spt.SPORT_DESCRIPTION
FROM IGS.IGS_DA_OUT_STDT_SPT spt
WHERE spt.BATCH_ID = 1001
ORDER BY spt.PERSON_ID, spt.SPORT_SEQ_NUM;

Given the table's obsolete status, such queries would primarily be used for supporting or migrating legacy data interfaces.

Related Objects

Based on the provided relationship data, IGS_DA_OUT_STDT_SPT has a defined dependency linking it to a parent table that manages the batch request context. The documented foreign key relationship is:

  • TABLE: IGS.IGS_DA_REQ_STDNTS: The BATCH_ID column in IGS_DA_OUT_STDT_SPT references this table. This relationship enforces that sport records can only exist for a valid, pre-defined batch extraction request for students. The join condition would be IGS_DA_OUT_STDT_SPT.BATCH_ID = IGS_DA_REQ_STDNTS.BATCH_ID.
This relationship is fundamental, as it ties the detailed sport data to the overarching extraction job or report request.