Search Results igs_pe_sn_service




Overview
Explore in AI Chat

Overview

The IGS_PE_SN_SERVICE table is a data object within the Oracle E-Business Suite (EBS) 12.1.1 and 12.2.2 releases, specifically architected for the now-obsolete IGS (Student System) module. Its core function is to serve as a repository for information pertaining to services provided to individuals with documented special needs or disabilities. The table operates as a child entity, storing detailed service records that are linked to a primary disability profile for a person. As indicated by its "Obsolete" status, this table and its parent module are no longer under active development, and its use in newer implementations is strongly discouraged in favor of more current Oracle Student Management or Campus Solutions products.

Key Information Stored

The table's structure is designed to capture the association between a specific disability and a corresponding service. The primary identifier is the SN_SERVICE_ID column, which serves as the system-generated unique key for each service record. The two most critical foreign key columns define the relationship: DISABILITY_ID links the service entry to a specific disability record in the IGS_PE_PERS_DISABLTY table, establishing the context of the individual's need. The SPECIAL_SERVICE_CODE column identifies the precise type of service or accommodation provided, such as note-taking assistance, extended exam time, or specialized equipment, and is validated against a code lookup table. Together, DISABILITY_ID and SPECIAL_SERVICE_CODE form a unique key constraint (IGS_PE_SN_SERVICE_UK), preventing duplicate service entries for the same disability.

Common Use Cases and Queries

This table supports administrative and compliance reporting related to disability services. A primary use case is generating a summary report of all approved accommodations for a student, which requires joining to the person and disability tables. For auditing purposes, queries might count the frequency of specific service codes across the institution. A typical SQL pattern to list services for a person would involve a multi-table join:

  • SELECT p.LAST_NAME, d.DISABILITY_TYPE, s.SPECIAL_SERVICE_CODE FROM IGS_PE_PERSON p JOIN IGS_PE_PERS_DISABLTY d ON p.PERSON_ID = d.PERSON_ID JOIN IGS_PE_SN_SERVICE s ON d.DISABILITY_ID = s.DISABILITY_ID WHERE p.PERSON_ID = :person_id;

Given the module's obsolete status, direct operational use in new integrations is rare; data is typically accessed for historical reporting or migration projects.

Related Objects

The IGS_PE_SN_SERVICE table is centrally connected to two primary entities via foreign key relationships, as documented in the ETRM metadata.

  • IGS_PE_PERS_DISABLTY: This is the parent table for disability information. The relationship is defined by the column IGS_PE_SN_SERVICE.DISABILITY_ID, which references a primary key in IGS_PE_PERS_DISABLTY. Every service record must be associated with a valid, pre-existing disability profile.
  • IGS_PE_CODE_CLASSES: This code lookup table validates the IGS_PE_SN_SERVICE.SPECIAL_SERVICE_CODE column. It ensures that the service type entered is from a controlled list of valid values, maintaining data integrity and consistency for reporting.