Search Results mileage_marker_begin

Overview

IGW.IGW_PROP_LOCATIONS is a transactional table within the Oracle E-Business Suite Grants/Proposal (IGW) schema that stores the performing sites and physical work locations associated with a proposal. The table records where the proposed activity will actually be conducted, supporting the requirement that a single proposal may be delivered across several performing organizations and geographic sites. Each row represents one location-to-proposal association, capturing the performing organization, party reference, and detailed site attributes such as coordinates, congressional district, and mileage markers.

Because the primary key is a composite of PROPOSAL_ID and PERFORMING_ORGANIZATION_ID (IGW_PROP_LOCATIONS_PK), the table functions as an associative entity resolving the many-to-many relationship between proposals and performing organizations. Its columns carry both business descriptors and audit stamps. From a Data Vault modeling perspective, the ETRM heuristic classifies this object as a link, since it connects two principal business entities (proposals and organizations) rather than standing alone as a durable hub or serving purely as a descriptive satellite. This classification is a modeling suggestion; the table also exhibits satellite-like attributes (location detail) that may argue for hybrid treatment depending on the target architecture.

Key Information Stored

The most significant columns fall into three groups: keys, location detail, and standard who/audit fields.

• PROPOSAL_ID — Proposal identifier; part of the composite primary key and foreign key to IGW_PROPOSALS_ALL.
• PERFORMING_ORGANIZATION_ID — The organization or site carrying out the proposed activity; part of the composite primary key and foreign key to HR_ALL_ORGANIZATION_UNITS. Together with PROPOSAL_ID it defines row uniqueness.
• PROP_LOCATION_ID — Surrogate proposal-location identifier, enforced as unique by the index IGW_PROP_LOCATIONS_U1 on APPS_TS_TX_IDX. This column is the strongest business-key candidate and is the value most commonly supplied in reported search terms such as "prop_location_id".
• PARTY_ID — Party identifier for the organization associated with the location.
• LOCATION_TYPE_CODE — Code classifying the nature of the location.
• CONGRESSIONAL_DISTRICT — Congressional district where work is performed, relevant for grant and proposal reporting.
• GEOGRAPHIC_LOCATION — Free-text geographic location description (up to 250 characters).
• LATITUDE and LONGITUDE — Coordinate strings describing the site position.
• RAILWAY_OWNER, MILEAGE_MARKER_BEGIN, and MILEAGE_MARKER_END — Rail-corridor attributes useful for infrastructure-oriented proposals.
• ADDITIONAL_INFORMATION — Free-text notes about the work site (up to 2000 characters).
• LAST_UPDATE_DATE, LAST_UPDATED_BY, CREATION_DATE, CREATED_BY, LAST_UPDATE_LOGIN — Standard who columns recording creation and modification audit trails.
• RECORD_VERSION_NUMBER — Locking sequence number used for optimistic concurrency control.

The table holds 19 documented columns and resides in the APPS_TS_TX_DATA tablespace with PCT Free 10; its unique index lives in APPS_TS_TX_IDX.

Common Use Cases and Queries

Typical scenarios include proposal reporting by performing site, geographic roll-ups for grant proposals, and reconciliation between a proposal and the organizations scheduled to execute it. A frequently used pattern joins the subject to its parent proposal and organization master to enrich reporting:

SELECT pl.PROP_LOCATION_ID, pl.PROPOSAL_ID, pl.PERFORMING_ORGANIZATION_ID,
       pl.CONGRESSIONAL_DISTRICT, pl.GEOGRAPHIC_LOCATION, pl.LOCATION_TYPE_CODE
FROM   IGW.IGW_PROP_LOCATIONS pl, IGW.IGW_PROPOSALS_ALL p
WHERE  pl.PROPOSAL_ID = p.PROPOSAL_ID
AND    pl.PERFORMING_ORGANIZATION_ID = :organization_id;

A retrieval by the surrogate key is also common: SELECT * FROM IGW.IGW_PROP_LOCATIONS WHERE PROP_LOCATION_ID = :prop_location_id;. Aggregations by district or organization support cost-distribution analyses, while joins to HR_ALL_ORGANIZATION_UNITS enable workforce reconciliation.

Related Objects

The following are the most significant dependencies, grounded in the documented foreign-key relationships:

• IGW.IGW_PROPOSALS_ALL — Parent proposal entity; joined on PROPOSAL_ID.
• HR_ALL_ORGANIZATION_UNITS — Organization master; joined on PERFORMING_ORGANIZATION_ID to resolve the performing site.
• IGW_PROP_LOCATIONS_U1 — Unique index on PROP_LOCATION_ID supporting surrogate-key lookups.
• IGW_PROP_LOCATIONS_PK — Composite primary key on PROPOSAL_ID and PERFORMING_ORGANIZATION_ID.
• IGW_PROPOSALS_ALL-dependent IGW grant/proposal child tables that inherit the proposal context, useful when assembling full proposal location reporting.

As a link classified object, IGW_PROP_LOCATIONS is best treated alongside its hub-like parents (proposals and organizations) when modeling proposal work-site data.