Search Results location_park_type




Overview
Explore in AI Chat

Overview

APPS.PN_LOCATIONS_V is a reporting view in the Oracle E-Business Suite Property Manager (PN) module. It presents a unified, denormalized picture of the physical hierarchical locations managed within an organization: location parks, properties, buildings, floors and offices. In EBS 12.1.1 and 12.2.2 the view is the principal interface through which location data is read for operational reporting, integration extracts and downstream lookups, since it flattens the master location structures into a single consumable row per building-level record.

The view is owned by APPS and is commonly referenced by sub-ledger and cross-module queries that need building identification, capacity information, address detail and descriptive flexfield attributes without joining the underlying PN base tables directly. Because building-level rows are exposed alongside property-level attributes, the view supports both site-level and portfolio-level reporting.

Underlying Base Objects

The documented base objects underlying the view are PN_LOCATIONS_ALL (synonym), PN_LOCATIONS (synonym), PN_PROPERTIES_ALL (synonym), PN_LOCATION_PARKS (synonym), PN_ADDRESSES_ALL (synonym), MTL_UNITS_OF_MEASURE (synonym), FND_LOOKUPS (view), FND_TERRITORIES_VL (view) and FND_GLOBAL (package), with supporting calls to the PNP_UTIL_FUNC package.

  • PN_LOCATIONS_ALL / PN_LOCATIONS — the primary source for building and location records; supplies location_id, location_code, location_alias, capacity, area, status, attributes and the location_park_id/location_type_lookup_code columns.
  • PN_PROPERTIES_ALL — provides property_id and property_name for the property to which the building belongs.
  • PN_LOCATION_PARKS — the parent grouping above property, referenced via location_park_id.
  • PN_ADDRESSES_ALL — supplies the address_id and address lines for the location.
  • MTL_UNITS_OF_MEASURE — resolves uom_code to the descriptive unit_of_measure.
  • FND_LOOKUPS — resolves lookup codes, including lease_or_owned_tenure from the lease/owned lookup meaning.
  • FND_GLOBAL — provides the session context (org_id and related values) used to filter the view to the operating unit.

Key Columns

  • row_id, org_id, location_id — unique row identifier, operating unit and the building-level location key.
  • location_code, location_alias, location_name (building), building, building_id, building_location_code — building identification values used to reference a specific building.
  • property_id, property_name — the owning property record.
  • location_park_id — the location park to which the building belongs; the related concept users search for as location_park_type is driven by this parent grouping rather than a distinct column in the view.
  • location_type_lookup_code, lease_or_owned, lease_or_owned_tenure — classify the building by type and tenure; lease_or_owned_tenure is the decoded meaning from FND_LOOKUPS.
  • max_capacity, optimum_capacity, rentable_area, usable_area — building capacity and area metrics; duplicate building_max_capacity, building_optimum_capacity, building_rentable_area and building_usable_area aliases are exposed for consistency across hierarchy levels.
  • floor_id, floor, office_id, office — placeholders returned as NULL, indicating the view surfaces building-level data only.
  • address_id, address_line1..3 — postal address of the location.
  • attribute1..attribute15, attribute_category — descriptive flexfield context and segments.
  • status, uom_code, unit_of_measure, last_update_date, last_updated_by, creation_date, created_by, last_update_login — audit and unit-of-measure columns.

Common Use Cases and Queries

Typical uses include building master reports, space and capacity analysis, lease-versus-owned tracking, and integration extracts feeding external facility systems. The following query lists buildings with their property, park and tenure:

  • SELECT location_code, building, property_name, location_park_id, location_type_lookup_code, lease_or_owned_tenure, max_capacity, rentable_area FROM apps.pn_locations_v WHERE org_id = :p_org_id;
  • SELECT building, address_line1, max_capacity FROM apps.pn_locations_v WHERE location_park_id = :p_park AND status = 'ACTIVE';
  • SELECT location_id, building, attribute1 FROM apps.pn_locations_v WHERE attribute_category = :p_cat ORDER BY building;

Because the view already resolves lookup meanings and joins the property, park, address and unit-of-measure structures, it reduces the join complexity otherwise required against PN_LOCATIONS_ALL and PN_PROPERTIES_ALL, and is preferred for read-only reporting in both 12.1.1 and 12.2.2.