Search Results igs_sv_ev_uadd_soa_blk_v

Overview

IGS_SV_EV_UADD_SOA_BLK_V is a reporting view that belongs to the IGS (Student System) product family in Oracle E-Business Suite. Its documented purpose is to fetch the new site of activities added to Exchange Visitor students. In the Exchange Visitor (J-1 visa) context, Student and Exchange Visitor Information System (SEVIS) reporting requires institutions to capture and transmit the physical locations where an exchange visitor performs his or her program activities. This view isolates a specific slice of address data — newly added activity site records — and presents them in a flattened, reporting-friendly form suitable for downstream extraction, batch processing, or integration with external regulatory filing processes.

The view is classified under IGS as an obsolete component. It is also documented as not implemented in the current database and carries no documented owner or referenced base objects in the ETRM 12.2.2 metadata. Its primary relevance today is historical and forensic: it explains how activity site data was assembled for Exchange Visitor reporting in earlier EBS 12.1.1/12.2.2 deployments, and it remains useful as a reference model when reconstructing comparable queries against the underlying address table.

Underlying Base Objects

The view text reveals a single underlying base object: IGS_SV_ADDRESSES, aliased UADD. No joins to other tables are present. All filtering and column derivation are performed directly against this table. The WHERE clause imposes three predicates that define the view's scope: ADDRESS_TYPE must equal 'A', ACTION_TYPE must equal 'A', and ACTIVITY_SITE_CD must not be null. The ACTION_TYPE='A' predicate is what gives the view its "UADD" (update/add) character, restricting the result set to records representing newly added addresses rather than modifications or deletions. The ACTIVITY_SITE_CD IS NOT NULL predicate ensures that only rows associated with an actual activity site are returned, excluding generic address rows.

Key Columns

• BATCH_ID — Identifier grouping the address records into a processing batch.
• PERSON_ID — The Exchange Visitor's person identifier.
• US_ADDRESS_LINE1 / US_ADDRESS_LINE2 — Street address lines for the U.S. activity site.
• US_CITY, US_STATE — City and state of the activity site.
• US_POSTAL_CODE, US_POSTAL_ROUTING_CODE — Postal code and routing code, supporting SEVIS address formatting.
• PARTY_SITE_ID — The TCA party site identifier, providing a stable key to the underlying site record.
• PARTY_SITE_NAME — This is a derived column, not a physical attribute. It is concatenated as ADDRESS_LINE1 || '-' || CITY || '-' || PARTY_SITE_ID. This concatenated string is the object commonly surfaced when users search for "party_site_name" in IGS reporting contexts.
• PRIMARY_FLAG — Indicates whether the address is the primary one for the person/site.

Common Use Cases and Queries

Typical use cases include auditing new activity sites for Exchange Visitor students, reconciling batch submissions, and providing a site label for user-facing reports. A representative query is:

SELECT batch_id, person_id, party_site_id, party_site_name, primary_flag
FROM igs_sv_ev_uadd_soa_blk_v
WHERE person_id = :p_person_id;

Because PARTY_SITE_NAME is a concatenation rather than a stored column, it should not be relied upon as a join key; PARTY_SITE_ID should be used for that purpose. Consumers should also note that the view returns only address_type 'A' and action_type 'A' rows, and only where activity_site_cd is populated, so it is intentionally narrow in scope.