Search Results home_address1

Overview

The view APPS.IGS_UC_IVGSTARA_2007_V is a reporting and integration layer within the Oracle E-Business Suite (EBS) 12.1.1 and 12.2.2 environments, specifically belonging to the Oracle Student System (formerly Oracle Student Administration/UCAS interface) module. It is a pre-defined database view that exposes a specific, flattened snapshot of applicant address and contact data as captured by the UCAS (Universities and Colleges Admissions Service) IVGSTARA 2007 data set. In the context of the EBS integration architecture, this view functions as a read-only presentation object that simplifies access to the underlying staging table, providing a stable interface for concurrent programs, inbound/outbound APIs, and custom reports without requiring direct queries against the base table. The view's primary role is to present applicant-centric address records—including both term-time and home addresses—in a denormalized format that is amenable to reporting tools such as Oracle Reports, BI Publisher, and OBIEE, as well as to PL/SQL packages that need to validate or migrate externally sourced applicant data.

Underlying Base Objects

The ETRM documentation identifies a single underlying base object for this view: the table IGS_UC_G_IVGSTARA_2007. The view is defined as a straightforward projection, selecting all eighteen columns from that base table without any joins, filters, aggregations, or analytical functions. The naming convention reflects its provenance: IGS_UC indicates the Student System UCAS interface, G typically denotes a global or generic staging table, and IVGSTARA_2007 specifies the IVGSTARA extract for the 2007 admissions cycle. Because the view performs no transformation, its column structure and data types are inherited directly from IGS_UC_G_IVGSTARA_2007. This one-to-one mapping means the view is best understood as a controlled publication endpoint rather than a logical model with independent business rules. No other referenced base objects are documented, and the view does not appear to consume data from tables such as HZ_PARTIES, HZ_LOCATIONS, or PER_ADDRESSES, confirming it sits in the UCAS staging/integration tier rather than the core Trading Community Architecture (TCA) tier.

Key Columns

The view exposes eighteen columns that together describe an applicant's contact and address profile. The most significant columns for the user's search term are:

• HOME_ADDRESS1 through HOME_ADDRESS4: the four address lines of the applicant's home (permanent) address. HOMEPOSTCODE supplies the corresponding postal code, and HOMECOUNTRYCODE the associated country.
• ADDRESS1 through ADDRESS4, POSTCODE, COUNTRYCODE: the term-time or correspondence address lines and their postal/country codes.
• ADDRESSAREA: a regional or area classification for the primary address.
• MAILSORT: the mail sorting code used by postal systems.
• TELEPHONE and MOBILE: landline and mobile contact numbers.
• EMAIL: the applicant's electronic mail address.
• APPNO: the UCAS application number, the primary business key linking the record to an applicant.
• TIMESTAMP: the date/time the row was captured or last updated in the staging table.

The HOME_ADDRESS1 column is therefore the first line of the applicant's permanent home address, distinct from the term-time ADDRESS1.

Common Use Cases and Queries

Typical usage involves extracting applicant contact details for admissions processing, correspondence generation, or migration into TCA. A simple query to retrieve home address details for a given applicant is:

• SELECT appno, home_address1, home_address2, home_address3, home_address4, homepostcode, homecountrycode FROM apps.igs_uc_ivgstara_2007_v WHERE appno = :p_appno;
• SELECT appno, home_address1, homepostcode FROM apps.igs_uc_ivgstara_2007_v WHERE UPPER(home_address1) LIKE '%' || UPPER(:search_text) || '%';
• SELECT appno, address1, home_address1, email, mobile FROM apps.igs_uc_ivgstara_2007_v WHERE timestamp >= :last_run_date;

These queries support applicant verification, duplicate detection, mass mailing, and incremental synchronization into the Student System. Because the view is read-only and unfiltered, reporting logic must apply its own date, applicant, or address-area predicates.