Search Results igr_is_per_all




Overview
Explore in AI Chat

Overview

The IGR_IS_PER_ALL table is a core data object within the now-obsolete Oracle E-Business Suite Student System (IGS). Its primary function was to serve as a staging table for person-related data captured through the Self Service Inquiry functionality. This table acted as a temporary repository, holding prospective student or inquirer information submitted via web-based forms before that data was validated and potentially migrated into the main transactional person tables of the application. Given its designation as "Obsolete," this table and its related objects are part of a legacy module no longer under active development or enhancement by Oracle. The metadata explicitly states it is "Not implemented in this database," indicating it may not be present in all deployment instances or its use has been formally discontinued.

Key Information Stored

While the provided ETRM excerpt does not list specific column details beyond the primary key, the table's description and relationships define its core data structure. The central column is INQ_PERSON_ID, which serves as the unique identifier (primary key) for each staged person record. This ID is the critical link to all related staging data. Based on its role as a person staging table, it would typically hold foundational demographic information for an inquirer, such as name, date of birth, contact details, and possibly a system-generated identifier. The "_ALL" suffix in the table name is a common Oracle EBS convention indicating the table can store data for multiple business groups, with a corresponding ORG_ID column likely present to partition the data.

Common Use Cases and Queries

The primary historical use case involved processes supporting the prospective student inquiry lifecycle. Data would flow from self-service entry forms into this staging table, where it could be reviewed, cleansed, or processed by batch programs before formal creation of a person record in the live system. Common operational queries would involve joining this table to its related staging tables to get a complete view of an inquirer's submitted information. A typical reporting query pattern would be:

  • Retrieving a list of all staged inquirers along with their submitted inquiry details and test scores for review.
  • Identifying incomplete person records by checking for missing related data in child tables.
  • Extracting all staged data for a specific business group (ORG_ID) for data validation purposes.

Given the module's obsolete status, current use is almost exclusively limited to historical data reference, custom data extraction for archival, or support for legacy interfaces that were never migrated.

Related Objects

The IGR_IS_PER_ALL table sits at the center of a set of related staging tables, as defined by its foreign key relationships. The INQ_PERSON_ID column is referenced by four key child tables, each holding a specific category of supplemental inquirer data:

  • IGR_IS_ADDRESS: Links via IGR_IS_ADDRESS.INQ_PERSON_ID to store staged address information for the person.
  • IGR_IS_INQUIRY: Links via IGR_IS_INQUIRY.INQ_PERSON_ID to store the core details of the academic or program inquiry itself.
  • IGR_IS_RACE: Links via IGR_IS_RACE.PERSON_ID to store staged ethnic or race information for the person.
  • IGR_IS_TEST: Links via IGR_IS_TEST.INQ_PERSON_ID to store staged standardized test scores (e.g., SAT, ACT) for the person.

These relationships form a classic master-detail structure, where IGR_IS_PER_ALL is the master record for the person, and the other tables contain the detailed, associated information. Any complete data retrieval from this obsolete subsystem requires joining these tables on the INQ_PERSON_ID key.