Results for “pn_pbuilding_v”

AI-generated from documented ETRM metadata — verify critical details on the linked pages.

Overview

PN_PBUILDING_V is an Oracle E-Business Suite view owned by the APPS schema within the Property Manager (PN) product module. As its name indicates, it presents property building-level information by combining location records with their associated address and territory details. The view is registered as VALID in the ETRM object inventory for both 12.1.1 and 12.2.2 and serves as a denormalized read interface over the core Property Manager location and address entity model.

In the EBS reporting and integration layer, PN_PBUILDING_V provides a convenient single source for building records enriched with postal address data. Rather than requiring report authors and interface developers to join PN_LOCATIONS, PN_ADDRESSES_ALL and FND_TERRITORIES_VL manually, the view exposes these relationships directly, including a pre-computed concatenated address produced by the PNP_UTIL_FUNC package. This makes it particularly useful for operational reports, label and correspondence generation, and inbound/outbound integrations that need to publish building locations in a human-readable form.

Underlying Base Objects

The documented base objects referenced by PN_PBUILDING_V are:

• PN_LOCATIONS (SYNONYM) — the primary driver, supplying location/building attributes such as LOCATION_CODE, LOCATION_TYPE_LOOKUP_CODE, BUILDING, STATUS and the descriptive flexfield columns ATTRIBUTE1 through ATTRIBUTE15.
• PN_ADDRESSES_ALL (SYNONYM) — supplies the address lines, COUNTY, CITY, STATE, PROVINCE, ZIP_CODE, COUNTRY, TERRITORY_ID and the ADDR_ATTRIBUTE1–15 flexfield columns.
• PN_PROPERTIES_ALL (SYNONYM) — the property header referenced through the PROPERTY_ID column, linking buildings to their owning property.
• FND_TERRITORIES_VL (VIEW) — provides TERRITORY_SHORT_NAME and ADDRESS_STYLE for the address territory.
• FND_LOOKUPS (VIEW) — supports lookup-code validation for location types and related status values.
• PNP_UTIL_FUNC (PACKAGE) — its GET_CONCATENATED_ADDRESS function assembles the address components into a single formatted address string based on the territory address style.
• FND_GLOBAL (PACKAGE) — used for session context such as user and responsibility identifiers.

The view therefore sits at the intersection of the location, address and property sub-entities of Property Manager, and its definition follows the standard APPS view pattern of selecting ROWID as the pseudo-key alongside the primary LOCATION_ID identifier.

Key Columns

• ROW_ID — the ROWID of the underlying PN_LOCATIONS row, used for row identification.
• LOCATION_ID — primary reference to the location record; the principal join key for downstream queries.
• LOCATION_CODE, LOCATION_TYPE_LOOKUP_CODE, BUILDING, STATUS — the core descriptive attributes of the building location.
• PROPERTY_ID — identifier of the parent property in PN_PROPERTIES_ALL.
• ATTRIBUTE_CATEGORY and ATTRIBUTE1–15 — the location descriptive flexfield context and segments.
• ADDRESS_ID, ADDRESS_LINE1–4, COUNTY, CITY, STATE, PROVINCE, ZIP_CODE, COUNTRY — the postal address components sourced from PN_ADDRESSES_ALL.
• ADDR_ATTRIBUTE_CATEGORY and ADDR_ATTRIBUTE1–15 — the address descriptive flexfield columns, aliased to avoid collision with the location flexfield.
• TERRITORY_ID, TERRITORY_SHORT_NAME, ADDRESS_STYLE — territory context used to control address formatting and validation.
• The concatenated address expression — a formatted, display-ready address string returned by PNP_UTIL_FUNC.GET_CONCATENATED_ADDRESS.
• Standard WHO audit columns — LAST_UPDATE_DATE, LAST_UPDATED_BY, CREATION_DATE, CREATED_BY and LAST_UPDATE_LOGIN.

Common Use Cases and Queries

Typical use cases include building master listings for a property, address labels, lease and occupancy reports, and extracts feeding external facility systems. The following query lists valid buildings with their formatted addresses:

• SELECT location_id, location_code, building, city, state, zip_code, territory_short_name FROM pn_pbuilding_v WHERE status = 'A' ORDER BY building;
• SELECT b.location_id, b.building, b.property_id, b.city, b.zip_code FROM pn_pbuilding_v b WHERE b.property_id = :p_property_id;
• SELECT p.property_name, b.building, b.address_line1, b.city FROM pn_pbuilding_v b, pn_properties_vl p WHERE b.property_id = p.property_id ORDER BY p.property_name, b.building;

Flexfield-driven reporting is also common, filtering on ATTRIBUTE_CATEGORY and specific ATTRIBUTE segments, while integration programs typically select LOCATION_ID and the concatenated address for outbound payloads. Because the view is a read-only projection, joins to PN_PROPERTIES_ALL and FND_TERRITORIES_VL are already resolved, and consumers should apply their own status and territory filters to scope results.