Search Results igs_ad_addrusage_int_all




Overview
Explore in AI Chat

Overview

IGS_AD_ADDRUSAGE_INT_ALL is an interface (staging) table in the IGS schema, part of the Oracle EBS Student System product family. It holds information about a person's address usages as they are staged for validation and transfer into the production address usage tables. The table follows the standard Oracle interface naming convention: the _INT_ALL suffix indicates that it is a multi-org interface table populated by inbound data loads, open interfaces, or third-party legacy conversion programs before the corresponding base tables are updated.

As documented in the ETRM metadata for 12.1.1, the table is owned by IGS and is marked VALID. Its primary key, IGS_AD_ADDRUSAGE_INT_U1, is defined on the INTERFACE_ADDRUSAGE_ID column. The table is validated as having 18 documented columns and participates in a foreign key relationship with IGS_AD_ADDR_INT_ALL through the INTERFACE_ADDR_ID column.

Under the heuristic Data Vault classification derived from its foreign key structure, IGS_AD_ADDRUSAGE_INT_ALL is characterized as satellite-leaning. In Data Vault modeling terms, this suggests the table behaves as a descriptive satellite in the interface layer: the primary key acts as a surrogate identifier, INTERFACE_ADDR_ID functions as a foreign key pointing to a parent interface address record, and the remaining columns carry descriptive attributes. This classification should be treated as a modeling suggestion rather than a prescriptive rule, given the limited metadata available.

Key Information Stored

The table's most significant columns fall into three functional groups:

  • INTERFACE_ADDRUSAGE_ID — the surrogate primary key defined by IGS_AD_ADDRUSAGE_INT_U1. Each row is uniquely identified by this system-generated identifier and it is the recommended join key for update and delete operations during interface processing.
  • INTERFACE_ADDR_ID — the foreign key to IGS_AD_ADDR_INT_ALL. This links each address usage record to a staged address record, forming the parent-child relationship that drives the interface hierarchy.
  • SITE_USE_CODE — the business attribute indicating the purpose of the address, such as a mailing, billing, or permanent address usage.
  • COMMENTS — a free-text field used to store notes about the usage.
  • STATUS and MATCH_IND — interface control columns used to track processing state and to indicate whether a record matched an existing target row.
  • ERROR_CODE — populated when a row fails validation; this is used by error-reconciliation reports.
  • ORG_ID — the multi-org operating unit identifier, confirming the _ALL designation and enabling multi-org access.
  • Audit and concurrent-program columns — CREATED_BY, CREATION_DATE, LAST_UPDATED_BY, LAST_UPDATE_DATE, LAST_UPDATE_LOGIN, REQUEST_ID, PROGRAM_APPLICATION_ID, PROGRAM_ID, PROGRAM_UPDATE_DATE, and INTERFACE_RUN_ID identify the source of the record and the concurrent request that created it.

The primary key is a surrogate; no separate unique business index is documented, so candidate business keys must be derived from combinations such as INTERFACE_ADDR_ID and SITE_USE_CODE.

Common Use Cases and Queries

Typical usage centers on monitoring inbound address data. Developers commonly query the table to confirm whether records were staged, to identify failed rows by ERROR_CODE, and to join usage data against the parent address record.

  • Count rows by interface run: SELECT INTERFACE_RUN_ID, COUNT(*) FROM IGS_AD_ADDRUSAGE_INT_ALL GROUP BY INTERFACE_RUN_ID;
  • List errors: SELECT INTERFACE_ADDRUSAGE_ID, INTERFACE_ADDR_ID, ERROR_CODE, STATUS FROM IGS_AD_ADDRUSAGE_INT_ALL WHERE ERROR_CODE IS NOT NULL;
  • Join to the parent address table: SELECT a.INTERFACE_ADDR_ID, a.SITE_USE_CODE FROM IGS_AD_ADDRUSAGE_INT_ALL a, IGS_AD_ADDR_INT_ALL b WHERE a.INTERFACE_ADDR_ID = b.INTERFACE_ADDR_ID;
  • Audit trail: query by REQUEST_ID or PROGRAM_APPLICATION_ID to trace the concurrent program that loaded a batch.

Reporting scenarios include reconciliation of inbound address loads, validation exception reports, and pre-transfer verification before the records are posted to the base address usage tables.

Related Objects

The following objects are most significant in relation to this table, based on the documented foreign key structure and the standard IGS interface pattern:

  • IGS_AD_ADDR_INT_ALL — the parent interface address table; joined via IGS_AD_ADDRUSAGE_INT_ALL.INTERFACE_ADDR_ID = IGS_AD_ADDR_INT_ALL.INTERFACE_ADDR_ID.
  • IGS_AD_ADDRUSAGE (or the corresponding base address usage table) — the production table that receives staged data upon successful processing.
  • IGS_AD_ADDRESSES and related IGS address table variants — reference tables for address types and usage codes.
  • The IGS open interface concurrent programs — the programs that read IGS_AD_ADDRUSAGE_INT_ALL, invoke validation, and transfer records to the base tables.
  • IGS_AD_ADDRUSAGE_INT_U1 — the primary key index that enforces uniqueness of INTERFACE_ADDRUSAGE_ID.

Because the table sits at the boundary between external data sources and the Student System base tables, its related objects are primarily interface tables, validation routines, and the concurrent requests tracked in REQUEST_ID.