Search Results igs_or_addr




Overview
Explore in AI Chat

Overview

IGS_OR_ADDR is an Oracle E-Business Suite (EBS) database view owned by the APPS schema and registered as a VALID object under the IGS – Student System product family. In release 12.1.1 and 12.2.2, its documented purpose is to capture the details of an address as maintained within the Student System model. Functionally, the view consolidates party, party-site, site-use, and location data into a single flattened address record that exposes legacy-style column names (ADDR_LINE_1 through ADDR_LINE_4, CORRESPONDENCE_IND, OTHER_DETAILS_1 through OTHER_DETAILS_3) expected by Student System forms, concurrent programs, reports, and inbound/outbound interfaces.

The view is a compatibility and reporting layer over the Trading Community Architecture (TCA) model. Because TCA normalizes addresses across HZ_PARTY_SITES, HZ_LOCATIONS, and HZ_PARTY_SITE_USES, the view re-presents that normalized data using the naming conventions historically required by IGS components. It is read-oriented; it is not a table and therefore carries no indexes of its own. Consumers that filter on high-volume columns should expect the optimizer to push predicates to the underlying TCA tables, and performance tuning is generally performed there rather than on the view.

The user search term "other_details_1" maps directly to a column exposed by this view. In IGS_OR_ADDR, OTHER_DETAILS_1, OTHER_DETAILS_2, and OTHER_DETAILS_3 are projected as NULL literals rather than being sourced from a physical column. Consequently, these attributes are placeholders in the documented view definition and return no data.

Underlying Base Objects

The documented view text defines IGS_OR_ADDR over five referenced base objects. The ETRM metadata records that no base objects are separately documented, but the view SQL itself establishes the following relationships:

Joins between HPS/HL, HPS/IGSPS, and HPS/PSU are performed on PARTY_ID, LOCATION_ID, and PARTY_SITE_ID respectively, with the IGSPS and PSU joins defined as outer joins. This means address rows may be returned without a matching IGS party-site extension or site-use record.

Key Columns

  • ROW_ID — the HZ_PARTY_SITES ROWID, useful for direct row addressing.
  • ORG_UNIT_CD / OU_START_DT — organizational context, derived from PARTY_NUMBER and the institution-org base view.
  • START_DT / END_DT — effective dating from the IGS party-site extension; may be null where no IGS extension exists.
  • ADDR_TYPE — the site-use type.
  • ADDR_LINE_1 … ADDR_LINE_4 — address lines sourced from HZ_LOCATIONS.ADDRESS1–ADDRESS4.
  • DATE_LAST_VERIFIED, CORRESPONDENCE_IND — verification date (projected as NULL) and the identifying-address flag.
  • CITY, STATE, PROVINCE, COUNTY, COUNTRY, POSTAL_CODE, DELIVERY_POINT_CODE — location geography attributes.
  • OTHER_DETAILS_1, OTHER_DETAILS_2, OTHER_DETAILS_3 — projected as NULL; retained for interface compatibility with legacy address structures. Queries filtering on other_details_1 will return no matching rows unless the predicate tests for NULL.
  • REQUEST_ID, PROGRAM_APPLICATION_ID, PROGRAM_ID, PROGRAM_UPDATE_DATE — concurrent-program audit context inherited from HZ_LOCATIONS.
  • STATUS — party-site status from HZ_PARTY_SITES.

Common Use Cases and Queries

Typical uses include extracting student or organization address data for reports, validating address completeness against TCA, and feeding downstream interfaces. A basic retrieval filtered by party number:

  • SELECT party_number, addr_type, addr_line_1, city, state, postal_code, status FROM apps.igs_or_addr WHERE party_number = :p_party_number;
  • SELECT * FROM apps.igs_or_addr WHERE other_details_1 IS NOT NULL; — note this returns no rows, since OTHER_DETAILS_1 is a NULL literal.
  • SELECT org_unit_cd, start_dt, end_dt, addr_line_1 FROM apps.igs_or_addr WHERE site_use_type = 'HOME' AND status = 'A';