Results for “disability_id”

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

Overview

IGS_PE_SN_CONTACT is a table in the Oracle E-Business Suite IGS — Student System product family, which Oracle classifies as obsolete in Release 12.1.1 and 12.2.2. The table stores details of a person's special need contact information, associating a contact record with a specific recorded disability for an individual. In the higher-education data model, this object functions as a dependent detail table that captures the contact point — name and date — tied to a disability registration held in the person disability table. The ETRM documentation for the deployment notes that the table is not implemented in the reference database, meaning no physical rows or DDL are present there, though the documented schema persists for reference.

From a Data Vault modeling perspective, the heuristic classification mined from the foreign-key structure is satellite-leaning. The dependency on IGS_PE_PERS_DISABLTY via DISABILITY_ID indicates this table behaves as a descriptive satellite attached to a parent disability business key, rather than as an independent hub or a many-to-many link.

Key Information Stored

The table is documented as owning ten columns. Its surrogate primary key is SN_CONTACT_ID, enforced through the constraint IGS_PE_SN_CONTACT_PK and mirrored by the unique index IGS_PE_SN_CONTACT_U1. Because the unique index covers the same SN_CONTACT_ID column, no separate natural or business-key candidate is documented; the surrogate key also serves as the documented unique identifier.

• SN_CONTACT_ID — surrogate primary key; uniquely identifies each special need contact row.
• DISABILITY_ID — foreign key to IGS_PE_PERS_DISABLTY, linking the contact to a person's recorded disability.
• CONTACT_NAME — the name of the special need contact person.
• CONTACT_DATE — the date associated with the contact record.
• COMMENTS — free-text remarks or notes about the contact.
• CREATED_BY, CREATION_DATE — standard WHO audit columns recording row creation.
• LAST_UPDATED_BY, LAST_UPDATE_DATE, LAST_UPDATE_LOGIN — standard WHO audit columns recording the most recent change and the login session responsible.

Common Use Cases and Queries

The most common access pattern joins the contact rows to their parent disability record, for example:

SELECT c.sn_contact_id, c.contact_name, c.contact_date, c.comments
FROM   igs_pe_sn_contact c, igs_pe_pers_disablty d
WHERE  c.disability_id = d.disability_id
AND    d.person_id = :person_id;

Reporting use cases include retrieving all special need contacts for a given student or applicant, auditing which contacts were recorded for a disability over time, and producing contact-date trend reports across a cohort. Administrative maintenance queries use SN_CONTACT_ID for single-row retrieval and update, since it is the enforced primary key. Audit-driven queries filter on LAST_UPDATE_DATE or CREATED_BY to reconcile record provenance.

Related Objects

• IGS_PE_PERS_DISABLTY — the parent table referenced by IGS_PE_SN_CONTACT.DISABILITY_ID; the primary join target for all queries.
• IGS_PE_SN_CONTACT_PK — the primary key constraint over SN_CONTACT_ID.
• IGS_PE_SN_CONTACT_U1 — the unique index on SN_CONTACT_ID.
• Person/disability registration components in the Student System family that surface contact details for special needs.

Because the object is documented as not implemented in the reference database, integration and reporting designs should confirm the table's presence before relying on it in a given environment.