Results for “igr_is_address”

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

Overview

IGR_IS_ADDRESS is a staging table owned by the IGS schema (Student System) in Oracle E-Business Suite 12.1.1 and 12.2.2. Its documented description is "Holds Self Service Staging Inquiry Address," which identifies its role as a transient or intermediate store for address records captured through self-service inquiry flows before such data is validated, promoted, or reconciled into the operational person and address model. In ETRM terms the object carries a status of VALID and comprises 25 documented columns.

From a modeling perspective, the mined foreign-key structure classifies this table as satellite-leaning. This is a heuristic suggestion: the table's grain is driven by a single parent reference (INQ_PERSON_ID pointing to IGR_IS_PER_ALL), and the remaining descriptive address attributes behave as dependent context around that parent key rather than as independent hubs or many-to-many links. Analysts designing a Data Vault or dimensional layer over IGS should treat IGR_IS_ADDRESS as a candidate satellite on the person hub, subject to confirmation against actual load semantics.

Key Information Stored

The primary key is defined by the unique index IGR_IS_ADDRESS_PK on the single column INQ_ADDR_ID. This surrogate identifier is the documented unique index and therefore the only business-key candidate recorded in the metadata; no composite natural key is documented for the staging record.

The most significant columns are:

• INQ_ADDR_ID — surrogate primary key for each staged address row.
• INQ_PERSON_ID — foreign key to IGR_IS_PER_ALL, linking each staged address to its person.
• ADDR_USAGE — the address type or usage classification (for example, mailing or permanent).
• ADDR_LINE_1 through ADDR_LINE_4 — the free-form address lines.
• CITY, STATE, COUNTY, PROVINCE, COUNTRY, POSTCODE — the geographic components of the address.
• START_DATE and END_DATE — the effective date range during which the address applies.
• STATUS — the processing or validity state of the staged record.

The remaining documented columns are standard Oracle EBS audit and concurrent-program attributes: CREATED_BY, CREATION_DATE, LAST_UPDATED_BY, LAST_UPDATE_DATE, LAST_UPDATE_LOGIN, REQUEST_ID, PROGRAM_APPLICATION_ID, PROGRAM_ID, and PROGRAM_UPDATE_DATE. These support traceability but carry no business meaning for address content.

Common Use Cases and Queries

The table is typically queried when reconciling self-service address entries against the person record, when validating staging loads before promotion, and when producing exception reports on incomplete or stale addresses.

Retrieving all staged addresses for a person:

• SELECT a.inq_addr_id, a.addr_usage, a.addr_line_1, a.city, a.state, a.postcode, a.status FROM igs.igr_is_address a WHERE a.inq_person_id = :person_id;

Joining to the person parent to enrich the result with person context:

• SELECT p.person_id, a.inq_addr_id, a.city, a.country, a.start_date, a.end_date FROM igs.igr_is_address a JOIN igs.igr_is_per_all p ON p.person_id = a.inq_person_id;

Identifying current active addresses uses STATUS together with the START_DATE and END_DATE range. Exception reporting commonly filters on missing POSTCODE or COUNTRY values, while audit reporting references REQUEST_ID and the PROGRAM_* columns to attribute staged rows to the concurrent request that created or updated them.

Related Objects

The following objects are the most significant in relation to IGR_IS_ADDRESS:

• IGR_IS_PER_ALL — the parent person table, joined on IGR_IS_ADDRESS.INQ_PERSON_ID = IGR_IS_PER_ALL.PERSON_ID. This is the only documented foreign-key relationship.
• IGR_IS_ADDRESS_PK — the unique index enforcing the INQ_ADDR_ID primary key.
• IGS person and address inquiry views and the Self Service inquiry pages that populate the staging table.
• Concurrent programs identified by PROGRAM_APPLICATION_ID and PROGRAM_ID, which write and refresh staged rows.
• Downstream IGS address validation and promotion routines that consume STATUS, START_DATE, and END_DATE.

The documented relationship model is deliberately narrow: one parent and one unique key. Any broader dependency map should be confirmed against the IGS data dictionary rather than inferred from this metadata alone.