Search Results pn_properties_all




Overview
Explore in AI Chat

Overview

The PN_PROPERTIES_ALL table is the central master data repository for property definitions within Oracle E-Business Suite Property Manager (PN). It stores the fundamental information that defines a property, which is a physical asset such as a building, land parcel, or other real estate holding managed by the organization. As a multi-organization (multi-org) enabled table, denoted by the "_ALL" suffix, it contains data for all operating units, with access controlled by the MOAC (Multi-Org Access Control) security model. This table is the primary source for all property-related transactions and serves as the parent record for numerous subsidiary tables in the module, forming the cornerstone of the property hierarchy and lease management structures.

Key Information Stored

While the provided metadata does not list specific columns, based on its role as the core properties table, PN_PROPERTIES_ALL typically contains key identifiers and descriptive attributes for each property record. The primary key is the PROPERTY_ID, a unique system-generated identifier. Essential columns generally include the PROPERTY_NAME and PROPERTY_NUMBER for identification, along with status flags (e.g., ACTIVE), classification codes, and dates for tracking the property lifecycle. Crucially, it includes the ORG_ID column to segregate data by operating unit, enabling the multi-org architecture. Other common attributes may encompass address information, area measurements, ownership details, and links to general ledger assets.

Common Use Cases and Queries

This table is fundamental for reporting, data extraction, and integration. Common use cases include generating property master lists, validating property IDs during data imports, and creating custom reports on the property portfolio. A typical query involves joining with related tables to build a comprehensive property profile. For instance, to retrieve a basic list of active properties for a specific operating unit, one might use:

  • SELECT property_id, property_number, property_name FROM pn_properties_all WHERE org_id = :org_id AND active_flag = 'Y';

Another critical pattern is validating the existence of a property before inserting related records, such as locations or lease agreements, ensuring referential integrity in custom interfaces or extensions.

Related Objects

As indicated by the extensive foreign key relationships in the metadata, PN_PROPERTIES_ALL is referenced by nearly all major transactional and setup tables in Property Manager. The PROPERTY_ID column is the key join field. Documented child tables include:

This network of relationships underscores the table's role as the primary parent entity for property-centric data across the module.