Results for “pn_locations”

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

Overview

APPS.PN_PBUILDING_V is a reporting and integration view in the Oracle E-Business Suite Property Manager (PN) module, which underpins the leasing, space management, and property operations functionality shared by Oracle Lease Management and Oracle Property Manager. The view denormalizes location records into a building-centric presentation: each row represents a physical location (a building, floor, or office definition held in PN_LOCATIONS), enriched with its mailing address details resolved through PN_ADDRESSES_ALL and its territory information from FND_TERRITORIES_VL. It also exposes a fully formatted, concatenated address string generated on the fly by the PNP_UTIL_FUNC package.

Because the PN data model normalizes addresses and locations into separate entities, the base location table alone is not directly usable for most reporting or interface requirements. PN_PBUILDING_V bridges that gap, providing a single relational row per location with address lines, city, state, postal code, and territory data already joined. The view is commonly consumed by Oracle Reports, BI Publisher data templates, custom concurrent programs, and interface/outbound extracts. The name and column set make it particularly relevant to implementers who have searched for "pn_locations" and are seeking a location-level data source that also carries building and address context.

Underlying Base Objects

The view is defined over the following documented base objects:

• PN_LOCATIONS (synonym to the underlying location table) — supplies the core location attributes, including location_id, location_code, location_type_lookup_code, building, status, and the descriptive flexfield columns attribute1 through attribute15.
• PN_ADDRESSES_ALL (synonym) — supplies address_line1 through address_line4, county, city, state, province, zip_code, country, territory_id, and the address-level descriptive flexfield columns (addr_attribute1 through addr_attribute15).
• FND_TERRITORIES_VL — supplies territory_short_name and related territory definitions.
• PNP_UTIL_FUNC — a PL/SQL package whose get_concatenated_address function assembles the formatted address string from the address_style and address lines.
• FND_LOOKUPS — referenced for lookup-code meaning resolution.
• FND_GLOBAL — the standard EBS package used to derive session context such as user_id and login information for who-columns.
• PN_PROPERTIES_ALL (synonym) — the property header entity to which locations belong via property_id.

The view is a straightforward outer join pattern: PN_LOCATIONS is the driving row source, joined to PN_ADDRESSES_ALL via address_id, and to FND_TERRITORIES_VL via territory_id.

Key Columns

• location_id / row_id — the primary key of the location and its physical row identifier.
• location_code — the short, user-facing identifier of the location.
• location_type_lookup_code — classifies the location (for example, building, floor, or office), validated against FND_LOOKUPS.
• building — the building name or code associated with the location.
• status — the active/inactive state of the location record.
• property_id — foreign key to PN_PROPERTIES_ALL, linking the location to its owning property.
• address_id and the address columns (address_line1–4, county, city, state, province, zip_code, country) — the mailing address of the building.
• territory_id / territory_short_name — the territory (country or region) definition used for address formatting and validation.
• address_style — the style code that governs how PNP_UTIL_FUNC.get_concatenated_address renders the address.
• attribute1–attribute15 and addr_attribute1–addr_attribute15 — descriptive flexfield segments for the location and the address, respectively.
• Who columns (created_by, creation_date, last_updated_by, last_update_date, last_update_login) — standard EBS audit fields.

Common Use Cases and Queries

Typical scenarios include building/space reporting, address validation extracts, lease location listings, and integration payloads that require a preformatted address. A representative query listing active building locations with formatted addresses follows:

• SELECT location_code, building, city, state, zip_code, territory_short_name, get_concatenated_address FROM apps.pn_pbuilding_v WHERE location_type_lookup_code = 'BUILDING' AND status = 'ACTIVE';
• Filtering by property_id to report all locations tied to a single property.
• Joining to PN_PROPERTIES_ALL on property_id to enrich output with property name and legal description.
• Using territory_short_name or country predicates to build regional space-utilization reports.
• Selecting the concatenated address column directly for mail-merge interfaces, avoiding the need to replicate address-formatting logic in custom code.

Because the view performs the address and territory joins internally, it should be treated as the preferred read-only source whenever location data is required alongside address detail, rather than querying PN_LOCATIONS directly.