Search Results sv_us_addr




Overview
Explore in AI Chat

Overview

IGS_SV_EV_EDT_US_ADDR_V is a reporting view in the Oracle EBS Student System (IGS) schema, owned by APPS. It exposes United States mailing address records that have been staged for extraction and processing within the Student System batch summary framework. The view is part of the address event data extraction layer (indicated by the "EV" and "EDT" fragments in its name — event edit/extract), which consolidates individual address records against batch-level administrative actions so downstream processes, interfaces, or reports can retrieve only addresses flagged for a specific action.

The name fragment "SV_US_ADDR" corresponds directly to the TAG_CODE value used in its definition, and "SV" denotes the Student System view namespace. The view therefore acts as a filtered, join-resolved projection over the address staging table, returning only United States addresses whose associated batch summary row carries the tag code SV_US_ADDR and an admission action code of SEND. This makes the view a convenient data source for third-party US address validation or mailing interfaces without requiring the calling process to re-implement the join and filter logic.

Underlying Base Objects

The view is defined over two documented base tables:

  • IGS_SV_ADDRESSES (aliased UADD) — the address staging table holding person-level address lines, city, state, postal code, and postal routing code.
  • IGS_SV_BTCH_SUMMARY (aliased ADDSUMM) — the batch summary table that tracks administrative actions and tag codes applied to each person and batch.

The two tables are joined on BATCH_ID and PERSON_ID. The view applies three filters on the address table (ADDRESS_TYPE = 'U', ACTIVITY_SITE_CD IS NULL) and two on the batch summary table (TAG_CODE = 'SV_US_ADDR', ADM_ACTION_CODE = 'SEND'). No other documented base objects are referenced, and the join is an inner join, so rows appear only when a matching summary record exists with the required tag and action codes.

Key Columns

  • BATCH_ID — Identifier of the processing batch to which the address and summary record belong; links the two base tables.
  • PERSON_ID — The person (student or applicant) to whom the address belongs.
  • ADDRESS_LINE1 / ADDRESS_LINE2 — Free-form street address lines typical of US postal formats.
  • CITY — City or locality name.
  • STATE — US state code or name as stored.
  • POSTAL_CODE — ZIP code, including ZIP+4 where applicable.
  • POSTAL_ROUTING_CODE — Additional routing information used for delivery or barcode generation.

The view deliberately excludes address_type and activity_site_cd, since both are fixed by the WHERE clause, leaving only the descriptive address fields needed by consumers.

Common Use Cases and Queries

Typical scenarios include extracting US addresses for a mailing house, feeding an address-cleansing or validation service, or auditing which persons in a batch were queued for the SEND action. A basic query retrieving all staged US addresses for a given batch is:

  • SELECT BATCH_ID, PERSON_ID, ADDRESS_LINE1, ADDRESS_LINE2, CITY, STATE, POSTAL_CODE, POSTAL_ROUTING_CODE FROM APPS.IGS_SV_EV_EDT_US_ADDR_V WHERE BATCH_ID = :p_batch_id;
  • SELECT PERSON_ID, CITY, STATE, POSTAL_CODE FROM APPS.IGS_SV_EV_EDT_US_ADDR_V WHERE POSTAL_CODE LIKE '9%' ORDER BY STATE, CITY;
  • SELECT BATCH_ID, COUNT(*) FROM APPS.IGS_SV_EV_EDT_US_ADDR_V GROUP BY BATCH_ID;

Because the view joins two staging tables and applies rigid filter values, query performance depends on indexes on IGS_SV_ADDRESSES(BATCH_ID, PERSON_ID) and IGS_SV_BTCH_SUMMARY(BATCH_ID, PERSON_ID, TAG_CODE, ADM_ACTION_CODE). Consumers should supply BATCH_ID or PERSON_ID predicates wherever possible and avoid treating the view as a general-purpose address master, as it returns only records already tagged SV_US_ADDR with a SEND action and no activity site. In Oracle EBS 12.1.1 and 12.2.2 the object is read-only and intended for SELECT access only.