Search Results pn_locations_all




Overview
Explore in AI Chat

Overview

The PN_LOCATIONS_ALL table is a core data object within the Oracle E-Business Suite Property Manager (PN) module. It serves as the master table for defining and storing all physical and logical spaces, or locations, managed by the application. A location represents a distinct, identifiable area within a property portfolio, such as an entire building, a specific floor, a suite, an office, or even a parking stall. This table enables the hierarchical structuring of space (e.g., Building A -> Floor 3 -> Suite 310), which is fundamental for space planning, allocation, and lease administration. Its role is to provide the definitive source for all space definitions against which tenancies, transactions, and features are tracked.

Key Information Stored

The table's primary key is a composite of LOCATION_ID, ACTIVE_START_DATE, and ACTIVE_END_DATE, supporting the maintenance of location history over time. Critical columns include LOCATION_ID (the unique identifier), LOCATION_CODE and NAME for business identification, and DESCRIPTION for detailed notes. The hierarchical relationship is established via PARENT_LOCATION_ID, which references another record in the same table to create a tree structure. Key foreign keys link a location to its overarching PROPERTY_ID (in PN_PROPERTIES_ALL) and its physical ADDRESS_ID (in PN_ADDRESSES_ALL). Additional columns track status, type, area measurements, and the standard currency for the location.

Common Use Cases and Queries

This table is central to reporting and operational processes in Property Manager. Common use cases include generating a roll-up of total leasable area for a property, analyzing vacancy by location hierarchy, and assigning costs or features to specific spaces. A frequent query retrieves the complete hierarchical tree for a property. For example, to find all child locations under a specific parent (like all suites on a floor), one might use a hierarchical SQL query: SELECT LEVEL, location_code, name FROM pn_locations_all START WITH parent_location_id = :parent_id CONNECT BY PRIOR location_id = parent_location_id. Another common pattern joins PN_LOCATIONS_ALL to PN_TENANCIES_ALL to report on leased versus vacant locations, filtering on ACTIVE_END_DATE to find currently active spaces.

Related Objects

As the central hub for space data, PN_LOCATIONS_ALL has extensive relationships with other Property Manager tables. It is directly referenced by transactional and assignment tables, including PN_TENANCIES_ALL (for lease agreements), PN_SPACE_ALLOCATIONS_ALL (for assigning space to tenants), and PN_LEASE_TRANSACTIONS_ALL (for billing transactions). It is linked to PN_LOCATION_FEATURES_ALL for storing attributes of a space and to PN_CONTACT_ASSIGNMENTS_ALL for associating contacts. The self-referential foreign key on PARENT_LOCATION_ID establishes the internal hierarchy. The table's "ALL" suffix indicates it is a multi-org table, storing data for all operating units, with security typically enforced via views like PN_LOCATIONS.