Search Results address_effective_date




Overview

IGS_GR_VENUE_ADDR_V is a database view owned by the APPS schema in Oracle E-Business Suite, delivered as part of the IGS (Student System) product family. In EBS 12.1.1 and 12.2.2 it carries a VALID status and is documented in the ETRM as an object used to maintain venue addresses — the physical locations at which the institution schedules graduations, examinations, ceremonies, and other events that must be tied to a validated address record. The view does not itself store data; it projects a joined, denormalized read model over Oracle's Trading Community Architecture (HZ) location tables and the IGS venue-specific extension tables. Because venue records must conform to the same address model used by Receivables, Order Management, and other HZ-consuming modules, this view exists to present a consistent address picture to graduation and venue-facing screens, concurrent programs, and reports. For the user searching on "contact_person," this view is the relevant object: CONTACT_PERSON is exposed directly as a column, sourced from the IGS_PE_HZ_LOCATIONS extension table, allowing venue address records to carry a named point of contact alongside the standard street address.

Underlying Base Objects

The view text joins four sources documented in the ETRM:

Join predicates are HL.LOCATION_ID = LA.LOCATION_ID and HL.LOCATION_ID = IHL.LOCATION_ID, with SOURCE_TYPE = 'V' restricting rows to venue source types. The PLU join is an outer join (+), so venue addresses without a site-use definition still appear, with ADDR_TYPE null.

Key Columns

  • LOCATION_ID — primary key linking back to HZ_LOCATIONS; the anchor for joins to parties and site uses.
  • VENUE_CD — the venue code from IGS_AD_LOCVENUE_ADDR, identifying the physical venue.
  • CONTACT_PERSON — the named individual associated with the venue address, sourced from IGS_PE_HZ_LOCATIONS. This is the column of interest for the "contact_person" search.
  • ADDR_TYPE — the site-use code from IGS_PE_LOCVENUE_USE, indicating the address purpose.
  • ADDRESS1–ADDRESS4, CITY, STATE, PROVINCE, COUNTY, COUNTRY, POSTAL_CODE, DELIVERY_POINT_CODE — the formatted address components.
  • ADDRESS_EFFECTIVE_DATE / ADDRESS_EXPIRATION_DATE — validity window for the address.
  • CORRESPONDENCE_IND — the identifying-address flag, marking the venue's primary correspondence address.
  • DATE_LAST_VERIFIED — date the venue address was last confirmed.

Common Use Cases and Queries

Typical uses include venue rosters for graduation ceremonies, address validation reports, and integration extracts feeding event management. To retrieve all venues with their contact person and city:

SELECT venue_cd, contact_person, city, state, country
FROM apps.igs_gr_venue_addr_v
WHERE correspondence_ind = 'Y';

To filter by contact person:

SELECT location_id, venue_cd, contact_person, addr_type
FROM apps.igs_gr_venue_addr_v
WHERE UPPER(contact_person) LIKE 'SMITH%'
ORDER BY venue_cd;

Because the view joins four base tables with an outer join to the site-use table, queries should be written with the understanding that ADDR_TYPE may be null. When deploying custom reports, always qualify the view with the APPS schema prefix.