Search Results inq_addr_id

Overview

The IGR_IS_ADDRESS table is a data object within the Oracle E-Business Suite (EBS) 12.1.1 and 12.2.2 releases, specifically belonging to the IGS (Student System) module, which is documented as obsolete. Its primary function is to serve as a staging table for address data captured through self-service inquiry processes. In this context, it temporarily holds address information submitted by prospective students or other inquirers via web-based forms before that data is potentially validated, processed, and transferred to core transactional tables. Its role is integral to the front-end data collection workflow, acting as an intermediary repository that decouples data entry from immediate system integration.

Key Information Stored

Based on the provided ETRM metadata, the table's structure centers on a unique address identifier and a link to the corresponding inquiry person record. The primary key column, INQ_ADDR_ID, uniquely identifies each staged address record. The foreign key column, INQ_PERSON_ID, is critical as it associates the address with a specific inquirer's primary record stored in the related IGR_IS_PER_ALL table. While the full column list is not detailed in the excerpt, typical columns for such a staging table would include address lines (e.g., address line 1-4), city, state, postal code, country, address type, and possibly contact information or validation status flags, all pertaining to the inquiry process.

Common Use Cases and Queries

The primary use case involves extracting and processing staged inquiry data for administrative review or system integration. A common operational report would list all pending addresses for recently submitted inquiries. A typical SQL query would join to the person staging table to provide context.

Sample Query Pattern:
SELECT per.INQUIRY_PERSON_NAME, addr.*
FROM IGR_IS_ADDRESS addr,
     IGR_IS_PER_ALL per
WHERE addr.INQ_PERSON_ID = per.INQ_PERSON_ID
AND per.CREATION_DATE > TRUNC(SYSDATE) - 7;

Data from this table is typically consumed by batch or online processes that validate and migrate clean records into the permanent student information system, such as the core Person (PER) or Student (IGS) tables. Reporting use cases focus on tracking inquiry sources, geographic demographics of prospects, and data quality metrics within the staging layer.

Related Objects

The table maintains a documented foreign key relationship, defining its dependency within the staging schema.

• IGR_IS_PER_ALL: This is the primary related table. The column IGR_IS_ADDRESS.INQ_PERSON_ID references a record in IGR_IS_PER_ALL. This relationship ensures that every staged address is linked to a valid staged person inquiry, maintaining referential integrity within the self-service staging area. The join condition for queries is IGR_IS_ADDRESS.INQ_PERSON_ID = IGR_IS_PER_ALL.INQ_PERSON_ID.

Given the obsolete status of the IGS module and the staging nature of this table, it is less likely to be directly referenced by core EBS APIs or standard reports, which would instead interact with the production data tables populated after staging processing is complete.