Search Results igs_ad_addr_int




Overview
Explore in AI Chat

Overview

The IGS_AD_ADDR_INT view belongs to the IGS (Student System) product family, which is documented as obsolete in Oracle EBS 12.1.1 and 12.2.2. In the ETRM reference for release 12.2.2, this object is explicitly listed as "Not implemented in this database," meaning it is a legacy metadata artifact retained for documentation and migration auditing rather than an active runtime object. The view presents address interface data — the staging records that were historically loaded into Oracle's party and location infrastructure through the customer or student data import process. Its role in reporting and integration was to expose inbound address rows, their validation status, and any error codes produced during import, before those rows were promoted into the base party/site tables.

Users searching for the column token other_details_2 encounter this view because that column appears in the documented SELECT text, but practitioners should note that the view is not instantiated in the current database, so any reference to it in custom code will fail at runtime.

Underlying Base Objects

The documented view text selects from a single underlying object: IGS_AD_ADDR_INT_ALL. The _ALL suffix indicates that the interface table was partitioned or filtered by ORG_ID to support multi-organization (operating unit) security. ETRM metadata lists no other dependent objects, which is consistent with a thin interface view whose purpose was to apply the organization security predicate on top of the staging table.

Because the base interface table carries the full set of address attributes plus TCA-style interface columns (MATCH_IND, STATUS, ERROR_CODE, REQUEST_ID, PROGRAM_ID), the view behaves as a pass-through projection. It does not denormalize, aggregate, or join to lookup tables; it simply restricts rows by operating unit and renames ROWID as ROW_ID for downstream identification.

Key Columns

Common Use Cases and Queries

The classic use case was monitoring an inbound address import batch, checking which rows failed validation, and inspecting the overflow columns such as OTHER_DETAILS_2 that carried non-standard attributes. A representative query would be:

  • SELECT INTERFACE_ADDR_ID, STATUS, ERROR_CODE, OTHER_DETAILS_2 FROM IGS_AD_ADDR_INT WHERE STATUS = 'ERROR';
  • SELECT ORG_ID, COUNT(*) FROM IGS_AD_ADDR_INT GROUP BY ORG_ID;
  • SELECT INTERFACE_ID, MATCH_IND, CONTACT_PERSON_ID FROM IGS_AD_ADDR_INT WHERE REQUEST_ID = :request_id;

Given the "Not implemented" designation, these queries are only meaningful against an environment where the underlying IGS_AD_ADDR_INT_ALL table still exists. In current 12.1.1 and 12.2.2 instances, equivalent functionality is provided by the TCA interface tables (for example HZ_IMP_ADDRESSES_TBL and related HZ_IMP_* objects). Consultants should reference this view only for historical or migration documentation, and should not build new dependencies on it.