Search Results igs_ad_os_sec_edu




Overview
Explore in AI Chat

Overview

The table IGS_AD_OS_SEC_EDU is a data entity within the Oracle E-Business Suite, specifically the now-obsolete IGS (Student System) module. Its primary function is to store detailed records of an applicant's secondary education history, which is a critical component for the assessment and evaluation of admissions applications. The table acts as a central repository for pre-tertiary academic credentials, enabling admissions officers to verify qualifications and make informed decisions. The metadata explicitly notes that this object is "Not implemented in this database," indicating it may be a legacy definition or a placeholder structure in the documented version of the EBS instance, which is a crucial consideration for any development or reporting work.

Key Information Stored

The table's structure is designed to uniquely identify and describe an applicant's secondary education entries. The primary key is a composite of PERSON_ID and SEQUENCE_NUMBER, allowing for multiple education records per applicant. While the full column list is not detailed in the provided excerpt, the foreign key relationships imply the storage of several key data points. These include a foreign key to HZ_PARTIES (PERSON_ID) to link to the applicant's master person record, a reference to IGS_PE_COUNTRY_CD (COUNTRY_CD) to specify the country where the education was completed, and a link to IGS_AD_OS_SEC_EDU_QF (OS_SCNDRY_EDU_QUALIFICATION) to categorize the specific type of qualification earned.

Common Use Cases and Queries

The primary use case is generating reports and providing data for the admissions assessment process. A typical query would join this table with person and qualification code tables to produce a comprehensive view of an applicant's secondary education background. For instance, an admissions report might list all applicants and their highest secondary qualification from a specific country. Given the "obsolete" and "not implemented" status, direct operational use in a live EBS 12.1.1/12.2.2 environment is unlikely. However, understanding its structure remains valuable for analyzing legacy data migrations or custom extensions that may have replicated its logic. A sample query pattern would be: SELECT p.party_name, edu.sequence_number, qf.qualification_name, c.country_name FROM igs_ad_os_sec_edu edu JOIN hz_parties p ON edu.person_id = p.party_id JOIN igs_ad_os_sec_edu_qf qf ON edu.os_scndry_edu_qualification = qf.qualification_code JOIN igs_pe_country_cd c ON edu.country_cd = c.country_cd WHERE edu.person_id = :applicant_id;

Related Objects

The table exists within a defined relational schema, as evidenced by its foreign key constraints. The documented relationships are as follows:

  • Referenced By This Table (Outgoing Foreign Keys):
    • IGS_AD_OS_SEC_EDU.PERSON_ID references HZ_PARTIES (Master person/party table).
    • IGS_AD_OS_SEC_EDU.COUNTRY_CD references IGS_PE_COUNTRY_CD (Country code lookup).
    • IGS_AD_OS_SEC_EDU.OS_SCNDRY_EDU_QUALIFICATION references IGS_AD_OS_SEC_EDU_QF (Secondary education qualification lookup).
  • References This Table (Incoming Foreign Key):
    • IGS_AD_OS_SEC_ED_SUB table references IGS_AD_OS_SEC_EDU via its composite columns (PERSON_ID, OSE_SEQUENCE_NUMBER), suggesting a child table for storing subject-level details within a secondary education record.