Results for “pn_pland_v”

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

Overview

PN_PLAND_V is a reporting view owned by the APPS schema within the Oracle E-Business Suite Property Manager (PN) module. In EBS 12.1.1 and 12.2.2, it exposes property location records together with their associated postal address and territory information in a single, denormalized result set. The view is a read-only construct: it defines no storage of its own and instead projects data from the PN location, address, and property tables, supplemented by a PL/SQL-based formatting function for concatenated addresses. Its role is to provide report writers, inquiry screens, and integration developers with a stable presentation layer over the location and address model without requiring them to reassemble the joins themselves.

The view text confirms a flat structure in which each row corresponds to a single PN location record, enriched with address lines, territory attributes, and descriptive flexfield segments. Because the view is designated VALID and owned by APPS, it is directly accessible to custom concurrent programs, BI Publisher data templates, and SQL-based extracts executed under standard EBS responsibilities.

Underlying Base Objects

ETRM metadata identifies the following referenced base objects for PN_PLAND_V:

• PN_LOCATIONS (synonym) — the primary driver, supplying location identity, type, building, status, and DFF columns.
• PN_ADDRESSES_ALL (synonym) — supplies address line, city, county, state, province, zip, country, and address DFF columns via the ADDRESS_ID join.
• PN_PROPERTIES_ALL (synonym) — the property header referenced by the PROPERTY_ID column.
• FND_TERRITORIES_VL (view) — provides territory short name and address style for formatting.
• FND_LOOKUPS (view) — used for descriptive lookup values such as location type and status.
• FND_GLOBAL (package) — supplies session context (for example, user and responsibility) used in the view's WHERE clause logic.
• PNP_UTIL_FUNC (package) — its GET_CONCATENATED_ADDRESS function assembles a formatted address string from the address style and address lines, returning the concatenated column in the SELECT list.

Key Columns

• LOCATION_ID / LOCATION_CODE — unique identifier and user-facing code for the location record.
• LOCATION_TYPE_LOOKUP_CODE / STATUS — coded location classification and record status.
• BUILDING — building designation within the property.
• PROPERTY_ID — foreign key to the owning PN property.
• ADDRESS_ID — FK to the address row supplying the address columns.
• ADDRESS_LINE1–4, CITY, COUNTY, STATE, PROVINCE, ZIP_CODE, COUNTRY — postal components.
• TERRITORY_SHORT_NAME, ADDRESS_STYLE — territory reference and formatting style.
• ATTRIBUTE_CATEGORY, ATTRIBUTE1–15 — location descriptive flexfield segments; equivalent ADDR_ATTRIBUTE1–15 carry address DFF segments.
• ROW_ID, CREATED_BY, CREATION_DATE, LAST_UPDATED_BY, LAST_UPDATE_DATE, LAST_UPDATE_LOGIN — WHO columns and the ROWID-based row identifier.

Common Use Cases and Queries

Typical scenarios include location address listings, property occupancy reports, and integration extracts requiring formatted addresses.

SELECT location_code, building, status, territory_short_name,
       address_line1, city, state, zip_code
FROM   apps.pn_pland_v
WHERE  property_id = :p_property_id;

SELECT p.location_code,
       apps.pnp_util_func.get_concatenated_address(
         TERR.ADDRESS_STYLE, ... ) formatted_address
FROM   apps.pn_pland_v p
WHERE  p.status = 'ACTIVE';

Because PN_PLAND_V already joins territory and address data, custom reports avoid redundant joins to PN_ADDRESSES_ALL and FND_TERRITORIES_VL. Queries should still filter by the relevant property or location keys to limit row counts on large installations.