Search Results igs_sv_edt_usaddr_v

Overview

APPS.IGS_SV_EDT_USADDR_V is a reporting and integration view within the Oracle E-Business Suite IGS — Student System product (the Student Information Management/Student Records module). Its documented purpose is to fetch United States address information for persons staged in the student batch-extract processing tables. The view isolates records flagged as US address type and delivers a flat, pre-joined result set for extraction to external systems or downstream reporting.

The view exists in EBS 12.1.1 and 12.2.2 and is recorded as VALID in the APPS schema. Its role is tightly scoped: it supports the "SEND" admission-action batch extract for the SV_US_ADDR tag, which suggests it feeds address data to an external recommendation or admissions-processing interface. The reported search term "us_state" maps directly to the view's US_STATE column, indicating user interest in the state component of the US address record.

Underlying Base Objects

Documented view text references two base tables:

• IGS_SV_ADDRESSES — aliased USA, the primary address store, filtered by ADDRESS_TYPE = 'U' (US address type) and ACTIVITY_SITE_CD IS NULL.
• IGS_SV_BTCH_SUMMARY — aliased USADDRSUMM, the batch summary table, which restricts the result to TAG_CODE = 'SV_US_ADDR' and ADM_ACTION_CODE = 'SEND'.

The two tables join on BATCH_ID and PERSON_ID. The batch summary acts as a whitelist: only persons whose address row is associated with a qualifying batch summary record (correct tag and admission action) are exposed. No additional documented referenced base objects are listed in the ETRM metadata for 12.2.2, so the view is effectively a two-table join.

Key Columns

• BATCH_ID — Identifier of the processing batch; ties the record to a specific extract run.
• PERSON_ID — Unique person identifier, the natural key linking student records to addresses.
• US_ADDRESS_LINE1, US_ADDRESS_LINE2 — Primary and secondary street address lines (source columns ADDRESS_LINE1, ADDRESS_LINE2).
• US_CITY — City name (source CITY).
• US_STATE — The state component (source STATE); this is the column surfaced by the "us_state" search term. It carries the US state abbreviation or code as stored.
• US_POSTAL_CODE — US ZIP code (source POSTAL_CODE).
• US_POSTAL_ROUTING_CODE — Extended postal routing/ZIP+4 element (source POSTAL_ROUTING_CODE).

All address columns are prefixed with US_ to distinguish them from other address-type columns that may exist in the underlying address table.

Common Use Cases and Queries

Typical usage involves extracting the US address of each person in a pending "SEND" batch. A representative query targeting state information is:

• SELECT PERSON_ID, US_STATE, US_POSTAL_CODE FROM APPS.IGS_SV_EDT_USADDR_V;
• Filtering one batch: SELECT * FROM APPS.IGS_SV_EDT_USADDR_V WHERE BATCH_ID = :batch_id;
• Grouping by state for distribution reporting: SELECT US_STATE, COUNT(*) FROM APPS.IGS_SV_EDT_USADDR_V GROUP BY US_STATE;
• Joining to person tables on PERSON_ID to enrich with name or demographic data.

Because the view already applies the ADDRESS_TYPE = 'U', TAG_CODE = 'SV_US_ADDR', and ADM_ACTION_CODE = 'SEND' filters, consumers receive only addresses actively queued for the US address extract, eliminating the need to re-implement that logic. Access should be granted through the APPS schema, and querying is read-only and safe for concurrent reporting workloads.