Results for “tenure_code”

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

Overview

PN_LOCATIONS_PUB_V is a public (PUB) view owned by the APPS schema in Oracle E-Business Suite, delivered as part of the PN – Property Manager product. As its description states, it is a "public view used to view location information." In EBS 12.1.1 and 12.2.2, public views such as this one function as the supported, API-stable interface through which external modules, reports, and integrations read property and space data without querying the underlying base tables directly. The view consolidates hierarchical location details—buildings, floors, offices, sections, parcels, and land—into a single denormalised result set, and it resolves lookup codes into their human-readable meanings via joins to FND_LOOKUPS.

The view is significant in the context of the searched term "class_meaning" because it is one of the principal objects where lookup-code meanings (the class/meaning pattern used throughout EBS lookup architecture) are surfaced for property locations. Column pairs such as SPACE_TYPE_LOOKUP_CODE / SPACE_TYPE, FUNCTION_TYPE_LOOKUP_CODE / FUNCTION_TYPE, and STANDARD_TYPE_LOOKUP_CODE / STANDARD_TYPE follow the standard lookup resolution convention, where the *_LOOKUP_CODE column stores the internal code and the paired column exposes the FND_LOOKUPS MEANING.

Underlying Base Objects

The documented view metadata lists the following referenced objects: FND_GLOBAL (package), FND_LOOKUPS (view), FND_TERRITORIES_VL (view), PNP_UTIL_FUNC (package), PN_ADDRESSES_ALL (synonym), PN_LOCATIONS_ALL (synonym), PN_LOCATION_PARKS (synonym), and PN_PROPERTIES_ALL (synonym).

• PN_LOCATIONS_ALL is the primary driver (aliased PLO in the view text), supplying location identity, type, dates, areas, and capacities.
• PN_PROPERTIES_ALL (aliased PLB) supplies parent building information used to derive GPARENT_LOCATION_CODE and the hierarchical LOCATION_NAME values.
• PN_LOCATION_PARKS (aliased PLF) supplies floor/parcel-level parent data.
• FND_LOOKUPS resolves lookup codes (SPC, FUN, STD, STYP) into their MEANING values.
• PNP_UTIL_FUNC is a PL/SQL utility package invoked inside the view to compute VACANT_AREA and floor counts. It uses GET_AS_OF_DATE_4_LOC_PUBVIEW (or LEAST(SYSDATE, ACTIVE_END_DATE)) as the effective date, enabling point-in-time reporting.
• FND_GLOBAL and FND_TERRITORIES_VL support session context and territory/address resolution.

Key Columns

• LOCATION_ID / LOCATION_CODE / LOCATION_ALIAS – primary identifier and user-facing codes for the location.
• LOCATION_TYPE_LOOKUP_CODE – drives the DECODE logic that determines whether a row is a BUILDING, LAND, FLOOR, OFFICE, SECTION, or PARCEL.
• LOCATION_NAME, PARENT_LOCATION_NAME, GPARENT_LOCATION_NAME – name resolution derived per location type, giving the location, its parent, and grandparent.
• PARENT_LOCATION_CODE / GPARENT_LOCATION_CODE – hierarchical codes, NULL for top-level BUILDING and LAND rows.
• SPACE_TYPE / FUNCTION_TYPE / STANDARD_TYPE – the FND_LOOKUPS MEANING values (the "class_meaning" values) for each respective lookup code.
• STATUS_TYPE / STATUS_TYPE_NAME – status code and its resolved meaning.
• MAX_CAPACITY, OPTIMUM_CAPACITY – occupancy thresholds.
• RENTABLE_AREA, USABLE_AREA, GROSS_AREA, ASSIGNABLE_AREA, COMMON_AREA – space measurement attributes.
• VACANT_AREA, VACANT_AREA_PERCENT – computed as-of-date vacancy metrics via PNP_UTIL_FUNC.

Common Use Cases and Queries

Typical uses include property hierarchy reports, space utilisation and vacancy analysis, lease/occupancy reporting, and integration extracts feeding external facility systems. A representative query to retrieve locations with their resolved lookup meanings is:

• SELECT location_id, location_code, location_name, location_type_lookup_code, space_type, function_type, standard_type, vacant_area FROM apps.pn_locations_pub_v WHERE active_end_date IS NULL OR active_end_date > SYSDATE;
• SELECT location_code, location_name, parent_location_name, gparent_location_name FROM apps.pn_locations_pub_v WHERE location_type_lookup_code = 'OFFICE' ORDER BY location_code;

Because the view performs dynamic lookups and invokes PNP_UTIL_FUNC for each row, queries should be filtered by LOCATION_TYPE_LOOKUP_CODE or location identifiers where possible to limit execution cost.