Search Results specialty_code




Overview
Explore in AI Chat

Overview

The IGS.IGS_EN_SPLACEMENTS table is a core data structure within the Oracle E-Business Suite (EBS) 12.1.1 and 12.2.2, specifically in the Student Systems (SS) module, often part of the Oracle Campus Solutions or EBS for Education footprint. Its primary function is to store detailed placement information for student unit attempts. A placement typically refers to a practical, work-based learning component such as an internship, clinical rotation, practicum, or field study that is associated with a student's academic coursework. The table serves as the central repository for tracking the logistical and administrative details of these experiential learning activities, linking a specific student, their program, and their unit attempt to an external institution and role.

Key Information Stored

The table's columns capture the full lifecycle and context of a student placement. The primary identifier is the system-generated SPLACEMENT_ID. Key relational columns are PERSON_ID, COURSE_CD, and UOO_ID, which link the placement to the specific student, their program (course), and unit attempt, respectively. The INSTITUTION_CODE and TITLE columns, together with START_DATE, form a unique key (IGS_EN_SPLACEMENTS_U2), defining the specific role at an external organization. Other critical attributes include the placement's END_DATE, CATEGORY_CODE, PLACEMENT_TYPE_CODE, SPECIALTY_CODE, and operational details like COMPENSATION_FLAG, ATTENDANCE_TYPE, and LOCATION. Descriptive fields such as DESCRIPTION and NOTES allow for additional context. Standard "Who" columns (CREATED_BY, CREATION_DATE, etc.) audit all changes.

Common Use Cases and Queries

This table is central to managing and reporting on work-integrated learning. Common use cases include generating rosters of students at specific placement sites for an institution, tracking placement hours and duration for compliance, and reporting on placement types by academic program. A frequent query pattern involves joining to person and course tables to list active placements. For example, to find all current placements for a specific institution code, a query might be:

  • SELECT p.person_id, s.title, s.start_date, s.end_date, s.location FROM igs_en_splacem ents s, igs_pe_person p WHERE s.person_id = p.person_id AND s.institution_code = :p_inst_code AND SYSDATE BETWEEN s.start_date AND NVL(s.end_date, SYSDATE);

Another common report aggregates placements by category or type for a given academic term, requiring joins to the unit attempt (UOO_ID) and term tables.

Related Objects

The IGS_EN_SPLACEMENTS table has defined relationships with several other key tables in the schema, as per the provided dependency information.

  • Primary Key Reference: The table's primary key, SPLACEMENT_ID (via index IGS_EN_SPLACEMENTS_PK), is referenced by foreign keys in child tables:
    • IGS_EN_SPLACE_FACS.SPLACEMENT_ID → Likely stores facilitating or assessing faculty for the placement.
    • IGS_EN_SPLACE_SUPS.SPLACEMENT_ID → Likely stores supervisor information for the placement.
  • Foreign Key References (Outgoing): This table references other tables to enforce data integrity:
    • PERSON_ID → References IGS_EN_SU_ATTEMPT_ALL, linking the placement to the student's specific unit attempt record.
    • ATTENDANCE_TYPE → References IGS_EN_ATD_TYPE_ALL, validating the attendance type code against a defined lookup.