Search Results igw_prop_locations




Overview
Explore in AI Chat

Overview

IGW_PROP_LOCATIONS is a table within the Oracle E-Business Suite Grants Proposal (IGW) module, a component historically associated with Oracle Grants Management and the pursuit of sponsored research funding. The table is documented as obsolete in Oracle EBS 12.1.1 and 12.2.2, and the ETRM metadata explicitly records "Not implemented in this database." Its documented business description is "Sites where proposal activity is conducted," meaning it was intended to record the physical or organizational locations tied to a given grant proposal — for example, the performing organization's facility, field site, or geographic point at which sponsored activity would take place.

From a data modeling perspective, the ETRM metadata supplies a heuristic Data Vault classification of link. This is a modeling suggestion rather than an Oracle-imposed designation: the table sits at the intersection of two parent entities, connecting proposals to organizations, and therefore behaves like a relationship (link) structure rather than a descriptive hub or satellite. The classification is mined from the foreign key topology, in which IGW_PROP_LOCATIONS.PROPOSAL_ID references IGW_PROPOSALS_ALL and IGW_PROP_LOCATIONS.PERFORMING_ORGANIZATION_ID references HR_ALL_ORGANIZATION_UNITS.

Key Information Stored

The documented physical schema (ETRM 12.1.1) lists the table owner as IGW with 19 columns. The composite primary key, IGW_PROP_LOCATIONS_PK, is defined on two columns:

  • PROPOSAL_ID — the proposal to which the location record belongs; foreign key to IGW_PROPOSALS_ALL.
  • PERFORMING_ORGANIZATION_ID — the organization performing the proposed work at that site; foreign key to HR_ALL_ORGANIZATION_UNITS.

In addition to the composite key, the table carries a surrogate attribute, PROP_LOCATION_ID, which is backed by the unique index IGW_PROP_LOCATIONS_U1 and is therefore a documented business-key candidate. Other attributes of interest include PARTY_ID and LOCATION_TYPE_CODE, which classify and identify the site; GEOGRAPHIC_LOCATION, LATITUDE, LONGITUDE, and CONGRESSIONAL_DISTRICT, which capture the geography of the site; and MILEAGE_MARKER_BEGIN, MILEAGE_MARKER_END, and RAILWAY_OWNER, which suggest a linear-referencing model typical of transportation or right-of-way project sites. ADDITIONAL_INFORMATION provides a free-text extension, while the standard WHO columns — CREATION_DATE, CREATED_BY, LAST_UPDATE_DATE, LAST_UPDATED_BY, LAST_UPDATE_LOGIN — supply audit lineage, and RECORD_VERSION_NUMBER supports optimistic locking.

Common Use Cases and Queries

Because the object is obsolete and not implemented in current databases, its practical relevance is mainly historical reporting, data migration, and schema archaeology during upgrades from earlier IGW releases. A typical query joins the table to its two parents to reconstruct the site list for a proposal:

  • Enumerating all sites for a proposal: SELECT l.PROP_LOCATION_ID, l.LOCATION_TYPE_CODE, l.LATITUDE, l.LONGITUDE FROM IGW_PROP_LOCATIONS l WHERE l.PROPOSAL_ID = :proposal_id;
  • Resolving the performing organization name: join PERFORMING_ORGANIZATION_ID to HR_ALL_ORGANIZATION_UNITS to obtain the organization name for reporting.
  • Geographic reporting: aggregate sites by CONGRESSIONAL_DISTRICT or plot LATITUDE/LONGITUDE for mapping.
  • Migration extraction: select by PROP_LOCATION_ID, the unique business-key candidate, to reconcile records against a replacement structure.

Reports should expect no rows in 12.1.1 or 12.2.2 production instances and should treat any data as legacy.

Related Objects

  • IGW_PROPOSALS_ALL — parent entity; joined on IGW_PROP_LOCATIONS.PROPOSAL_ID = IGW_PROPOSALS_ALL.PROPOSAL_ID.
  • HR_ALL_ORGANIZATION_UNITS — parent entity for the performing organization; joined on IGW_PROP_LOCATIONS.PERFORMING_ORGANIZATION_ID = HR_ALL_ORGANIZATION_UNITS.ORGANIZATION_ID.
  • IGW_PROP_LOCATIONS_PK — composite primary key constraint (PROPOSAL_ID, PERFORMING_ORGANIZATION_ID).
  • IGW_PROP_LOCATIONS_U1 — unique index on PROP_LOCATION_ID, the business-key candidate for record identification.
  • Other IGW proposal child tables (for example, proposal personnel and budget objects) share the PROPOSAL_ID lineage and are commonly queried alongside this table in legacy Grants Proposal extractions.