Search Results igs_sv_ev_edt_us_addr_v

Overview

The view IGS_SV_EV_EDT_US_ADDR_V is a reporting and integration object owned by the APPS schema within the IGS — Student System product family of Oracle E-Business Suite (documented for releases 12.1.1 and 12.2.2). Its stated purpose is to fetch modified United States address information for Exchange Visitor students. In practice, the view isolates a specific, time-sensitive subset of student address data: U.S. addresses belonging to persons for whom a batch process has raised a change notification tagged SV_US_ADDR and flagged for dispatch (SEND). This makes the view a purpose-built feeder for downstream reporting, extracts, or integration interfaces that must transmit updated U.S. address details for Exchange Visitor (SEVIS-related) processing rather than exposing the entire address repository. By filtering at the database view layer, it shields consumers from having to replicate the multi-condition join logic across the batch summary and address tables.

Underlying Base Objects

The view is defined over two base tables in the IGS schema:

• IGS_SV_ADDRESSES (aliased UADD) — the address store holding the person's address lines, city, state, postal code, and batch linkage.
• IGS_SV_BTCH_SUMMARY (aliased ADDSUMM) — the batch summary table that records the batch, person, tag code, and administrative action code associated with a change event.

The two are joined on BATCH_ID and PERSON_ID, ensuring each returned row represents an address tied to a specific batch notification for the same person. Although the documented base-object metadata records "none documented," the view text explicitly references these two tables, which are the authoritative dependencies. Three predicates constrain the result set: the address type must be 'U' (U.S. address), the activity site code must be null, and the batch summary must carry a tag code of 'SV_US_ADDR' with an administrative action code of 'SEND'. Only rows satisfying all conditions are surfaced.

Key Columns

• BATCH_ID — Identifier of the batch process that captured the address change; used to correlate the notification with its run.
• PERSON_ID — The individual (Exchange Visitor student) to whom the address belongs; the primary linkage to the person record.
• US_ADDRESS_LINE1 / US_ADDRESS_LINE2 — The street address lines, qualified as U.S. address components by the view's column naming.
• US_CITY — City of the U.S. address.
• US_STATE — State component of the U.S. address.
• US_POSTAL_CODE — ZIP or postal code.
• US_POSTAL_ROUTING_CODE — Postal routing code, typically the ZIP+4 extension.

The view text selects UADD columns (ADDRESS_LINE1, ADDRESS_LINE2, CITY, STATE, POSTAL_CODE, POSTAL_ROUTING_CODE) and exposes them under US_-prefixed aliases, confirming the intended U.S.-address semantics.

Common Use Cases and Queries

Typical consumers use this view to extract pending U.S. address updates for Exchange Visitor students for outbound transmission or reconciliation. A representative query retrieves all flagged address changes for a given batch or person:

• Batch extract: SELECT BATCH_ID, PERSON_ID, US_ADDRESS_LINE1, US_ADDRESS_LINE2, US_CITY, US_STATE, US_POSTAL_CODE, US_POSTAL_ROUTING_CODE FROM APPS.IGS_SV_EV_EDT_US_ADDR_V WHERE BATCH_ID = :p_batch_id;
• Person lookup: SELECT * FROM APPS.IGS_SV_EV_EDT_US_ADDR_V WHERE PERSON_ID = :p_person_id;
• Full staging pull: SELECT * FROM APPS.IGS_SV_EV_EDT_US_ADDR_V ORDER BY BATCH_ID, PERSON_ID;

Because the view already enforces the U.S. address type, null activity site, and the SV_US_ADDR/SEND batch criteria, callers should not re-apply those filters; doing so is redundant. The absence of a documented primary key on the view means callers should expect potentially multiple rows per person across batches and should qualify by BATCH_ID where a single notification is required. No public API is associated with the view, so it is intended strictly for read-only querying and reporting.