Search Results pn_location_parks




Overview
Explore in AI Chat

Overview

PN_LOCATION_PARKS is a Property Manager (PN) module table in Oracle E-Business Suite 12.1.1 and 12.2.2 that stores master reference data describing geographic regions and office parks. Within the PN schema, this table functions as a foundational location hierarchy used by downstream property, lease, and facility management records. Each row represents a single location park or region, enabling organizations to organize physical sites into a parent-child structure for reporting, charge allocation, and lease administration.

From a Data Vault modeling perspective, the metadata classifies PN_LOCATION_PARKS as standalone, meaning it has no inbound or outbound foreign key relationships documented within the ETRM schema definition. This heuristic classification suggests the table can be modeled as an independent hub or reference satellite, since its business keys are not tied to other entity hubs through explicit FK constraints. The 28 documented columns include a multi-language component, indicating this is a translated (TL-style) reference entity.

Key Information Stored

The table's structure is organized around a composite primary key and a set of descriptive and audit columns. The most significant columns are:

  • LOCATION_PARK_ID — The surrogate primary key identifier for each region or office park record.
  • LANGUAGE — Language code, forming the second component of the composite primary key and enabling multilingual translation rows.
  • PARENT_LOCATION_PARK_ID — Self-referencing pointer establishing hierarchical relationships between parks (a park's parent region).
  • NAME — The display name of the region or office park.
  • DESCRIPTION — A longer free-text description of the location park.
  • LOCATION_PARK_TYPE — Classifies the record (for example, region versus office park), driving how the row is treated in downstream logic.
  • CREATED_BY, CREATION_DATE, LAST_UPDATED_BY, LAST_UPDATE_DATE, LAST_UPDATE_LOGIN — Standard Oracle who-columns supporting audit and concurrency tracking.
  • SOURCE_LANG — Indicates the source language for translation purposes.
  • ATTRIBUTE_CATEGORY and ATTRIBUTE1 through ATTRIBUTE15 — The Oracle Flexfield descriptive columns available for customer-specific extensions.

The surrogate primary key is PN_LOCATION_PARKS_PK (LOCATION_PARK_ID, LANGUAGE). The unique index PN_LOCATION_PARKS_U1 (LOCATION_PARK_ID, LANGUAGE) serves as the documented business-key candidate, mirroring the primary key structure. Note that the PK and unique index are functionally identical here, which is typical for translated reference tables where the surrogate key alone is not unique without the language component.

Common Use Cases and Queries

Typical scenarios include hierarchical location reporting, filtering active parks by type, and joining park identifiers to lease or property records. A common query pattern retrieves the current-language park hierarchy:

  • Listing all office parks with their parent region: SELECT child.NAME, parent.NAME FROM PN_LOCATION_PARKS child, PN_LOCATION_PARKS parent WHERE child.PARENT_LOCATION_PARK_ID = parent.LOCATION_PARK_ID AND child.LANGUAGE = 'US';
  • Filtering by type: SELECT LOCATION_PARK_ID, NAME FROM PN_LOCATION_PARKS WHERE LOCATION_PARK_TYPE = :type AND LANGUAGE = USERENV('LANG');
  • Reporting on maintenance and audit: querying by LAST_UPDATE_DATE to identify recently changed reference data.
  • Extracting flexfield values via ATTRIBUTE_CATEGORY and ATTRIBUTE1–15 for custom reporting or integration extracts.

Related Objects

Because the ETRM metadata classifies this table as standalone, there are no documented foreign key dependencies. The most significant related objects are therefore drawn from the Property Manager module and the technical framework surrounding the table:

  • PN_LOCATION_PARKS_PK — The primary key constraint on (LOCATION_PARK_ID, LANGUAGE).
  • PN_LOCATION_PARKS_U1 — The unique index on the same columns, serving as the business-key candidate.
  • PN_LOCATION_PARKS_TL — The typical translation table companion holding language-specific NAME and DESCRIPTION values.
  • PN_PROPERTIES / PN_LEASES_ALL — Property and lease entities that commonly reference LOCATION_PARK_ID for site grouping.
  • FND_LANGUAGES — Validates the LANGUAGE column and supports translation queries.
  • FND_FLEX_VALUES — Relevant where flexfield attributes or LOCATION_PARK_TYPE draw from value sets.

Given the self-referencing PARENT_LOCATION_PARK_ID column, recursive SQL using CONNECT BY or recursive CTEs is the recommended approach for traversing the regional hierarchy.