Search Results igs_ss_inq_contact




Overview
Explore in AI Chat

Overview

The IGS_SS_INQ_CONTACT table is a core data structure within the Oracle E-Business Suite (EBS) Student System (IGS) module. Its primary function is to store contact information for prospective students or inquiries that is captured through the self-service application interface. This table acts as a staging or transactional repository for contact details before they may be formally processed or integrated into the institution's master person and contact records. Critically, the official ETRM documentation explicitly marks this table as "Obsolete." This status indicates that while the table may exist in schemas for versions 12.1.1 and 12.2.2 to support historical data or legacy processes, it is no longer the active or recommended object for new development or data storage. Its use has likely been superseded by other, more current tables or architectural patterns within the Student System.

Key Information Stored

As a contact staging table, IGS_SS_INQ_CONTACT would typically hold attributes related to an individual's communication details. The primary key, INQ_CONTACT_ID, uniquely identifies each contact record. The most significant foreign key column is INQ_PERSON_ID, which links the contact information to a specific prospective student record in the IGS_SS_INQ_PERSON_ALL table. While the full column list is not detailed in the provided metadata, such a table would be expected to contain fields for contact types (e.g., home phone, mobile, email), the actual contact data (phone numbers, email addresses), and possibly flags indicating a preferred contact method. Status and date columns to manage the staging lifecycle are also common.

Common Use Cases and Queries

Given its obsolete status, direct operational use cases for this table in active processes are discouraged. Its primary contemporary use would be for historical reporting, data auditing, or migration support. Common queries would involve joining to the related inquiry person table to analyze captured contact information for legacy inquiry records. A typical reporting pattern would be:

  • Retrieving all contact records for a specific inquiry person to understand historical communication data capture.
  • Auditing data quality by checking for missing or invalid contact entries in legacy staging data.
  • Extracting data for archival purposes prior to a system decommissioning or major upgrade where the obsolete table may be removed.

Sample SQL: SELECT c.* FROM igs.igs_ss_inq_contact c, igs.igs_ss_inq_person_all p WHERE c.inq_person_id = p.inq_person_id AND p.last_name = '<Surname>';

Related Objects

The table maintains a direct and documented foreign key relationship, which is fundamental to its data integrity and purpose. The relationship is defined as follows:

  • Foreign Key Reference to IGS_SS_INQ_PERSON_ALL: The column IGS_SS_INQ_CONTACT.INQ_PERSON_ID is a foreign key that references the IGS_SS_INQ_PERSON_ALL table. This enforces that every contact staging record must be associated with a valid prospective student record in the inquiry person staging table. This relationship is essential for contextualizing the contact data within the broader self-service inquiry process.

No other foreign key relationships are documented in the provided metadata. As a staging table marked obsolete, it is unlikely to be widely referenced by other core application objects such as public APIs or key views.