Search Results pn_buildings_v




Overview
Explore in AI Chat

Overview

PN_BUILDINGS_V is a form view owned by the APPS schema in Oracle E-Business Suite, belonging to the PN – Property Manager product. The ETRM documentation describes it as a "form view used to view company information," and its column list confirms that its primary purpose is to expose building and location level detail for property records. The view consolidates descriptive attributes of a property location — codes, aliases, building identifiers, lease or owned tenure, class, status, gross area, unit of measure, and full address information — together with the decoded meaning values from Oracle lookups and territory definitions. Because it joins transactional location data with reference lookups, it presents human readable property records without requiring the caller to resolve lookup codes manually.

In Oracle EBS 12.1.1 and 12.2.2, views of this type are typically bound to an Oracle Forms block and are also used by reports, concurrent programs, and integration extracts. The user search term "gross_area" maps directly to the GROSS_AREA column, which is one of the principal measures surfaced by the view and is relevant to space management and property valuation reporting.

Underlying Base Objects

The documented base objects for PN_BUILDINGS_V are:

The view is therefore a denormalized presentation layer over the PN location, property, and address tables, enriched with Oracle Applications lookup and territory reference data.

Key Columns

Identity and audit columns include ROW_ID, ORG_ID, LOCATION_ID, PROPERTY_ID, and the standard WHO columns LAST_UPDATE_DATE, LAST_UPDATED_BY, CREATION_DATE, CREATED_BY, and LAST_UPDATE_LOGIN.

Descriptive property columns include LOCATION_CODE, LOCATION_ALIAS, BUILDING, LOCATION_TYPE (decoded from LOCATION_TYPE_LOOKUP_CODE via FLV.MEANING), SPACE_TYPE_LOOKUP_CODE, FUNCTION_TYPE_LOOKUP_CODE, STANDARD_TYPE_LOOKUP_CODE, LEASE_OR_OWNED with its decoded LEASE_OR_OWNED_TENURE, CLASS with CLASS_NAME, and STATUS_TYPE with STATUS_TYPE_NAME.

Measurement columns are central to the "gross_area" search: GROSS_AREA holds the measured gross area value, UOM_CODE holds the stored unit of measure, and UNIT_OF_MEASURE holds its description from MTL_UNITS_OF_MEASURE. These pair together and should always be reported jointly.

Address columns include ADDRESS_LINE1 through ADDRESS_LINE4, COUNTY, CITY, STATE, PROVINCE, ZIP_CODE, COUNTRY, TERRITORY_ID, and ADDRESS_STYLE. The view also exposes INTERFACE_FLAG, ATTRIBUTE_CATEGORY, and ATTRIBUTE1 through ATTRIBUTE15 for extensibility.

Common Use Cases and Queries

Typical uses include property and space reporting, gross area aggregation by property, address mailing extracts, and integration feeds that require decoded lookup values.

  • Listing buildings with their gross area and unit of measure for a property.
  • Aggregating total gross area by property or by class and status.
  • Filtering leased versus owned locations using the decoded tenure.
  • Extracting address and territory detail for correspondence or interface staging.

Sample query:

SELECT property_name, building, location_code, gross_area, unit_of_measure, location_type, status_type_name FROM apps.pn_buildings_v WHERE org_id = :p_org_id AND gross_area IS NOT NULL ORDER BY property_name, building;

A further example aggregates area by class:

SELECT class_name, SUM(gross_area) total_gross_area FROM apps.pn_buildings_v WHERE org_id = :p_org_id GROUP BY class_name;

Because the view is a form view, direct DML is not supported; modifications should be performed through the Property Manager forms or the underlying PN_LOCATIONS interface rather than against the view itself.