Results for “lease_or_owned”

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

Overview

The view APPS.PN_LOCATIONS_ITF_V is a reporting and integration interface object within the Oracle E-Business Suite Property Manager (PN) module. It presents a denormalized, consolidated picture of property locations by joining the core location entity in PN_LOCATIONS to its associated address, primary contact, and primary telephone records. The suffix _ITF_V denotes an interface view, indicating that its principal design intent is to serve as a stable, read-only projection of Property Manager data for downstream consumers — external systems, custom reporting, and interface programs — without requiring those consumers to understand the underlying normalized relationships between the location, address, contact, and phone tables.

Because Property Manager locations carry physical, financial, and operational attributes, this view is frequently leveraged by real estate, facilities, and space-planning reports. It exposes location classification and geospatial detail alongside capacity and area measurements, making it suitable for occupancy analysis and integration with third-party space management tools.

Underlying Base Objects

Per the documented ETRM metadata (12.2.2), PN_LOCATIONS_ITF_V is defined over the following base objects, all referenced as APPS synonyms:

• PN_LOCATIONS — the primary location entity, aliased as LOCN, supplying location identity, type, capacity, area, cost allocation, and descriptive attributes.
• PN_ADDRESSES_ALL — aliased as ADDR, supplying the structured address lines, county, city, state, province, ZIP code, country, address style, and address-level descriptive flexfields.
• PN_CONTACTS_ALL — supplying the contact's first and last name and email address.
• PN_CONTACT_ASSIGNMENTS_ALL — linking contacts to locations so that the appropriate contact can be resolved.
• PN_PHONES_ALL — aliased as PHON, supplying the contact telephone number.

The join effectively flattens the location-to-address and location-to-contact-to-phone chains into a single row per location, which is why the view is convenient for reporting but also carries the usual caution associated with multi-table joins: confirm cardinality assumptions (for example, one primary contact per location) before relying on row counts.

Key Columns

The view exposes a broad column set. Notable groupings include:

• Identity and classification: LOCATION_ID, LOCATION_CODE, LOCATION_TYPE_LOOKUP_CODE, PARENT_LOCATION_ID, which together model the location hierarchy and type.
• Physical structure: BUILDING, FLOOR, OFFICE, LEASE_OR_OWNED.
• Address: ADDRESS_LINE1 through ADDRESS_LINE4, COUNTY, CITY, STATE, PROVINCE, ZIP_CODE, COUNTRY, and ADDRESS_STYLE.
• Capacity and area: MAX_CAPACITY, OPTIMUM_CAPACITY, RENTABLE_AREA, USABLE_AREA, and UOM_CODE. This is the cluster most relevant to the search term max_capacity.
• Costing: ALLOCATE_COST_CENTER_CODE.
• Contact: CONTACT_NAME, CONTACT_PHONE, EMAIL_ADDRESS.
• Audit and DFFs: CREATED_BY, CREATION_DATE, LAST_UPDATED_BY, LAST_UPDATE_DATE, plus ATTRIBUTE_CATEGORY, ATTRIBUTE1–ATTRIBUTE15 for the location DFFs, and ADDR_ATTRIBUTE_CATEGORY, ADDR_ATTRIBUTE1–ADDR_ATTRIBUTE7 for the address DFFs.

Common Use Cases and Queries

Typical uses include space-utilization reporting, capacity planning, and data feeds for external facilities systems. To retrieve locations together with their capacity and area measurements:

• Capacity comparison: SELECT location_code, building, floor, max_capacity, optimum_capacity FROM pn_locations_itf_v WHERE max_capacity IS NOT NULL ORDER BY max_capacity DESC;
• Area utilization: SELECT location_code, rentable_area, usable_area, uom_code FROM pn_locations_itf_v WHERE rentable_area > 0;
• Location with primary contact and address: SELECT location_code, city, state, country, contact_name, contact_phone FROM pn_locations_itf_v WHERE country = 'US';
• Hierarchy inspection: SELECT location_code, parent_location_id, location_type_lookup_code FROM pn_locations_itf_v;

Because the view is read-only and interface-oriented, it should be used for retrieval only; inserts and updates must target the underlying base tables. Where the join can multiply rows, aggregate or filter by LOCATION_ID to preserve reporting accuracy.