Search Results location_park_id




Overview
Explore in AI Chat

Overview

APPS.PN_PROPERTIES_V is a reporting view in the Oracle E-Business Suite Property Manager (PN) module that consolidates property master data with decoded lookup values, territory information, and location park hierarchy attributes. In Oracle EBS 12.1.1 and 12.2.2, this view serves as the primary read-only interface for property records used by operational reports, Oracle Discoverer workbooks, custom concurrent programs, and integration extracts. Rather than joining raw base tables each time property data is required, developers and report authors query PN_PROPERTIES_V to obtain a denormalized result set that already resolves lookup codes into their descriptive meanings and derives office park, region, and territory attributes from related location park and territory records. The view is owned by the APPS schema and is typically granted to reporting and read-only roles.

Underlying Base Objects

The documented base objects referenced by the view are PN_PROPERTIES (SYNONYM), PN_LOCATION_PARKS (SYNONYM), FND_LOOKUPS (VIEW), FND_TERRITORIES_VL (VIEW), and the FND_GLOBAL package. The core driver is PN_PROPERTIES, aliased PROP, which supplies all transactional and descriptive property columns. PN_LOCATION_PARKS is joined twice via outer joins—aliased PLP1 for the property's direct location park and PLP2 for a parent hierarchy level—allowing the view to distinguish between office parks and regions based on the LOCATION_PARK_TYPE flag. FND_TERRITORIES_VL is outer-joined on TERR.territory_code = PROP.country to return country and territory_short_name. FND_LOOKUPS is referenced six times (FNDZ, FNDP, FNDT, FNDC, FNDS, FNDD) to translate zone, portfolio, tenure, class, property status, and condition codes into their localized meanings, each keyed on the corresponding lookup type and code.

Key Columns

The view exposes the standard WHO columns (ORG_ID, ROW_ID, LAST_UPDATE_DATE, LAST_UPDATED_BY, CREATION_DATE, CREATED_BY, LAST_UPDATE_LOGIN) alongside core property attributes. PROPERTY_ID is the primary key, with PROPERTY_NAME and PROPERTY_CODE providing identification. LOCATION_PARK_ID, ZONE/ZONE_NAME, DISTRICT, COUNTRY, PORTFOLIO/PORTFOLIO_NAME, TENURE/TENURE_NAME, CLASS/CLASS_NAME, PROPERTY_STATUS/PROPERTY_STATUS_NAME, and CONDITION/CONDITION_NAME describe the property's classification and hierarchy. ACTIVE_PROPERTY is a flag indicating whether the property remains in service. The descriptive flexfield columns ATTRIBUTE_CATEGORY and ATTRIBUTE1 through ATTRIBUTE15 are exposed verbatim for user-defined extensions. Derived columns include TERRITORY_SHORT_NAME, and the decode-based pairs OFFICE_PARK_ID/OFFICE_PARK_NAME and REGION_ID/REGION_NAME, which are populated conditionally based on the location park type (OFFPRK or REGION) associated with the property.

Common Use Cases and Queries

A frequent requirement is listing all active properties with their classification meanings, as shown below.

  • Property master extracts for interface tables or data warehousing loads.
  • Hierarchical reporting on office parks and regions, using OFFICE_PARK_ID and REGION_ID from the same location park structure.
  • Validation queries during conversions or integrations to confirm lookup meanings before mapping legacy data.

A representative query returning active properties with classification names:

SELECT property_id, property_name, property_code, location_park_id, zone_name, portfolio_name, tenure_name, class_name, property_status_name, condition_name, territory_short_name, office_park_name, region_name FROM apps.pn_properties_v WHERE active_property = 'Y' AND org_id = :p_org_id ORDER BY property_name;

To isolate properties assigned to a specific office park or region, the derived columns can be filtered directly, for example WHERE region_id = :p_region_id or WHERE office_park_id = :p_office_park_id. Because PN_LOCATION_PARKS is outer-joined, properties with no location park assignment return NULLs in those derived columns, which should be accounted for in report logic. All joins to FND_LOOKUPS and FND_TERRITORIES_VL are also outer joins, so missing or inactive lookup values yield NULL meanings rather than dropping property rows, preserving completeness of the property set.