Search Results coordinate_person_number




Overview
Explore in AI Chat

Overview

IGSFV_LOCATIONS is a read-only view in the Oracle E-Business Suite (EBS) Student System (IGS) product family. It presents a consolidated, denormalized picture of the physical locations that an institution maintains for academic, administrative, and operational purposes. In EBS 12.1.1 and 12.2.2, the IGS product is documented as obsolete, and the ETRM metadata explicitly notes that this object is "Not implemented in this database," meaning the view may not be deployed in every environment.

Its principal role is to support reporting and integration by resolving the many foreign keys embedded in the base location table (IGS_AD_LOCATION_ALL) into human-readable descriptions. Rather than joining multiple tables manually, consumers—such as Oracle Reports, BI Publisher data models, OBIEE repositories, or custom PL/SQL—can query a single object and obtain location data alongside the coordinate person's party number, the location type description, and the revenue account description. This makes the view particularly useful as a discovery surface for the coordinate person, exposing COORDINATE_PERSON_NUMBER and COORDINATE_PERSON_ID as first-class columns.

Underlying Base Objects

The view text, documented in the ETRM excerpt, is defined over four tables joined with outer-join semantics:

The ETRM metadata lists no referenced base objects under "Documented view metadata," and the owner is not recorded. Nevertheless, the embedded view text makes the dependency chain unambiguous. Because the header table pivots on COORD_PERSON_ID, the HZ_PARTIES join is the mechanism by which the sought "coordinate_person_number" value is surfaced.

Key Columns

Note that the view also carries two descriptor columns beginning with underscores ("_DF:" and "_LA:") that support EBS Flexfield and Lookup display semantics.

Common Use Cases and Queries

A typical use is retrieving active locations with their coordinate person and account description:

  • SELECT location_code, description, location_type_desc, coordinate_person_number FROM igsfv_locations WHERE closed_indicator = 'N';
  • SELECT location_code, description, revenue_account_desc FROM igsfv_locations WHERE revenue_account_code IS NOT NULL;
  • SELECT COUNT(*), location_type_desc FROM igsfv_locations GROUP BY location_type_desc;

Because it is a WITH READ ONLY view, it should be used strictly for querying, not DML. Always validate availability in the target instance, since ETRM states the object may not be implemented.