Results for “pn_offices_v”

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

Overview

PN_OFFICES_V is a public view owned by the APPS schema in Oracle E-Business Suite, delivered as part of the PN – Property Manager product. Its documented purpose is to expose Location information for reporting and integration purposes, presenting office and space records in a denormalized, human-readable form. The view resolves the raw lookup codes stored on the underlying location records into their corresponding meanings by joining to FND_LOOKUPS, so consumers receive descriptive values such as Location Type, Space Type, Function Type, and Standard Type rather than internal codes.

Because it is a public view rather than an internal implementation object, PN_OFFICES_V is intended as a supported read interface for custom reports, extracts, and integrations. In addition to static location attributes, the view computes several dynamic measures through calls to the PNP_UTIL_FUNC package, including vacant area, utilized capacity, office vacancy, and secondary area. This makes it particularly relevant to real property and space management reporting. Users searching for the "assignable_area" attribute will find it exposed here as ASSIGNABLE_AREA, one of several area metrics available alongside rentable, usable, and common area.

Underlying Base Objects

The documented base objects referenced by PN_OFFICES_V are:

• PN_LOCATIONS / PN_LOCATIONS_ALL (synonyms) – the primary source of location records, supplying identifiers, descriptive attributes, area values, status, and descriptive flexfield columns.
• FND_LOOKUPS (view) – referenced multiple times to translate lookup codes into meanings for location type, space type, function type, and standard type.
• PNP_UTIL_FUNC (package) – supplies the computed functions GET_VACANT_AREA, GET_UTILIZED_CAPACITY, GET_OFFICE_VACANCY, and GET_OFFICE_SECONDARY_AREA.
• FND_GLOBAL (package) – the standard EBS context package, typically used to resolve environment and session context.

The view text confirms these dependencies: aliases LOC, FLV, LST, FUN, STD, and FLR indicate joins across the location table and lookup view, while the PNP_UTIL_FUNC calls appear inline in the select list. The FLR alias derives BUILDING_ID from the parent location, establishing the office-to-building hierarchy.

Key Columns

• LOCATION_ID / ROW_ID – primary identifiers for each location record.
• LOCATION_CODE, LOCATION_ALIAS, BUILDING, FLOOR, OFFICE, SUITE – descriptive location attributes.
• LOCATION_TYPE, SPACE_TYPE, FUNCTION_TYPE, STANDARD_TYPE – decoded meanings from FND_LOOKUPS.
• RENTABLE_AREA, USABLE_AREA, ASSIGNABLE_AREA, COMMON_AREA – the core space measurement metrics, with ASSIGNABLE_AREA being the column most commonly sought.
• MAX_CAPACITY, OPTIMUM_CAPACITY – occupancy thresholds.
• PARENT_LOCATION_ID, BUILDING_ID – hierarchical relationships.
• VACANT_AREA, UTILIZED_CAPACITY, VACANCY, SECONDARY_AREA – computed values returned by PNP_UTIL_FUNC.
• STATUS, INTERFACE_FLAG – record state and interface control.
• ATTRIBUTE_CATEGORY and ATTRIBUTE1–ATTRIBUTE15 – descriptive flexfield columns.

Common Use Cases and Queries

Typical scenarios include space utilization reporting, vacancy analysis, and extraction of assignable area by building or floor for downstream systems. A representative query retrieving assignable area alongside location detail is:

• SELECT location_code, building, floor, office, assignable_area, rentable_area, vacancy FROM apps.pn_offices_v WHERE building = :p_building;
• SELECT location_code, assignable_area FROM apps.pn_offices_v WHERE location_type = 'OFFICE' ORDER BY building, floor;
• SELECT building_id, SUM(assignable_area) total_assignable FROM apps.pn_offices_v GROUP BY building_id;

Because the computed columns invoke PNP_UTIL_FUNC, queries returning vacancy or capacity measures may execute additional logic per row; restricting the result set is advisable in high-volume reporting.