Search Results igs_pe_person_addr_v




Overview
Explore in AI Chat

Overview

IGS_PE_PERSON_ADDR_V is a reporting and integration view in the Oracle E-Business Suite IGS (Student System) product family. It exposes person address detail, joining party-site records from the Oracle Trading Community Architecture (TCA) model against the IGS person-site extension table. The IGS product line is flagged as obsolete in the ETRM metadata, meaning the view is supplied for backward compatibility and historical reporting rather than for new development. Where the object is not implemented in a given database, the view text remains available in the data model documentation but the underlying objects are absent, so runtime queries against it fail.

The view is highly relevant to searches for "sales_tax_geocode". Sales tax determination in EBS relies on geographic identifiers attached to a party site or location. This view surfaces the location-level address attributes, including validated address flags and structured address components, which are the inputs from which jurisdiction and geocode logic derive tax treatment. Because the view projects both TCA location fields and IGS person-site attributes, it provides a single row per person address usable in tax, registration, and student record reporting.

Underlying Base Objects

The documented view text references three principal sources: the party-site table (aliased PS, supplying PARTY_ID, PARTY_SITE_ID, LOCATION_ID, the WHO columns, and the ATTRIBUTE1 through ATTRIBUTE20 descriptive flexfield columns), the person/party table (aliased P, supplying PARTY_NUMBER), the IGS person-site extension table (aliased IGSPS, supplying START_DATE and END_DATE), and the TCA location table (aliased L, supplying the address-level attributes). No base objects are separately documented in the ETRM metadata, so the definition must be derived from the view text itself. The join is driven from the party site to its location record, with the IGS extension adding effective dating to the party-site relationship.

Key Columns

Common Use Cases and Queries

Typical uses include reporting a person's current address against effective dates, verifying whether an address has been validated before tax calculation, and extracting structured address components for geocode or jurisdiction resolution.

SELECT PERSON_ID,
       PERSON_NUMBER,
       PARTY_SITE_ID,
       LOCATION_ID,
       ADDRESS_KEY,
       VALIDATED_FLAG,
       POSTAL_PLUS4_CODE,
       IDENTIFYING_ADDRESS_FLAG,
       START_DT,
       END_DT
  FROM IGS_PE_PERSON_ADDR_V
 WHERE STATUS = 'A'
   AND TRUNC(SYSDATE) BETWEEN START_DT AND NVL(END_DT, TRUNC(SYSDATE));

A second pattern targets geocode and tax-sensitive addresses by requiring a positive validation flag and a populated postal code before passing the address to third-party tax services. Where the view is not implemented in the database, queries return an invalid-identifier error and the equivalent TCA party-site and location tables must be used directly.