Search Results igf_sl_addr_v




Overview
Explore in AI Chat

Overview

IGF_SL_ADDR_V is a reporting view historically shipped within the Oracle E-Business Suite Financial Aid module (product code IGF, "Financial Aid"). In EBS 12.1.1 and 12.2.2 it is classified as obsolete, meaning Oracle no longer actively maintains or supports it as part of the current Financial Aid data model. Its documented purpose is narrow and specific: to expose a person's address details, flattened into a single row per active address usage. The view resolves a party to its associated addresses, filtering on active status and on the site-use types HOME and RESIDES_AT, which are the two usage classifications relevant to student and dependent residence data in a financial aid context.

Because the view is obsolete and, per the supplied ETRM metadata, is "not implemented in this database," it should be treated primarily as a legacy artifact. Where it does exist, it functions as a convenience layer over the Oracle Trading Community Architecture (TCA) address model, sparing developers from writing the multi-table join by hand. Any user query such as "coforge vitamin nagar address" is unrelated to this object's schema semantics; the view simply stores postal address line and geography columns and can hold any address value, including corporate or institutional addresses supplied by third parties.

Underlying Base Objects

The documented view text is defined over three TCA tables:

The joins are: PS.LOCATION_ID = L.LOCATION_ID, PS.PARTY_SITE_ID = PSU.PARTY_SITE_ID, with a filter PSU.STATUS = 'A' and PSU.SITE_USE_TYPE IN ('HOME','RESIDES_AT'). The date predicate SYSDATE BETWEEN NVL(PS.START_DATE_ACTIVE,SYSDATE) AND NVL(PS.END_DATE_ACTIVE,SYSDATE) restricts output to currently effective party-site assignments. Note that the ETRM 12.2.2 metadata records no owner and lists no documented referenced base objects, reflecting the object's obsolete status.

Key Columns

  • PERSON_ID — sourced from PS.PARTY_ID; identifies the party (person) owning the address.
  • SITE_USE_TYPE — the usage classification, limited to HOME or RESIDES_AT.
  • ADDR_LINE_1..ADDR_LINE_4 — free-form street address lines from HZ_LOCATIONS.
  • CITY, STATE, PROVINCE, COUNTY, COUNTRY, POSTAL_CODE — geographic components of the address.
  • LAST_UPDATE_DATE — the last modification timestamp of the location record, useful for incremental extracts.

Common Use Cases and Queries

Typical usage is address extraction for financial aid correspondence, dependent-address verification, or migration of legacy student address data. A representative query follows:

  • SELECT person_id, site_use_type, addr_line_1, city, state, postal_code FROM igf_sl_addr_v WHERE person_id = :p_person_id;
  • SELECT person_id, postal_code, country, last_update_date FROM igf_sl_addr_v WHERE last_update_date >= :p_since;

Considerations: the view is obsolete and may not be deployed in all environments; multiple rows per person are possible when several active HOME or RESIDES_AT usages exist, so de-duplication or prioritization logic is advisable. Because it depends on SYSDATE, results vary over time. Where available, direct TCA queries against HZ_PARTY_SITES, HZ_LOCATIONS, and HZ_PARTY_SITE_USES are preferable for new development.