Results for “pn_location_features_v”

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

Overview

PN_LOCATION_FEATURES_V is an APPS-owned database view in the Oracle E-Business Suite Property Manager (PN) module. It presents a denormalized, reporting-friendly projection of the PN_LOCATION_FEATURES base table, joining descriptive lookup meanings and unit-of-measure descriptions so that feature records attached to a property location can be consumed without further joins. The view is central to any reporting or integration scenario that needs to describe the physical characteristics of a location — for example, the count or size of fixtures, amenities, or equipment recorded against a leased or owned property.

The object is documented as VALID in both EBS 12.1.1 and 12.2.2. Because it is a view rather than a table, it holds no data of its own; it is a read-only window onto the underlying transactional table and the supporting lookups. The user search term "feature_size" maps directly to the FEATURE_SIZE column exposed by this view, which stores the measured magnitude of the feature (for example, 250) qualified by the UOM_CODE column (for example, SQFT or EA).

Underlying Base Objects

According to the ETRM 12.2.2 metadata, the view is defined over the following referenced objects:

• PN_LOCATION_FEATURES (SYNONYM) — the primary base table, aliased LOCF, supplying all feature attributes, WHO columns, and the LOCATION_ID foreign key.
• FND_LOOKUPS (VIEW) — referenced twice (FLV1 and FLV2) to resolve the LOCATION_FEATURE_LOOKUP_CODE (lookup type PN_LOCATION_FEATURE_TYPE) and the CONDITION_LOOKUP_CODE (lookup type PN_FEATURE_CONDITION) into human-readable MEANING values.
• MTL_UNITS_OF_MEASURE (SYNONYM) — aliased UOM, resolving the UOM_CODE into its descriptive UNIT_OF_MEASURE text.
• FND_GLOBAL (PACKAGE) — used to derive the ORG_ID (operating unit) context for multi-org filtering.

The joins to FND_LOOKUPS (FLV2) and MTL_UNITS_OF_MEASURE are outer joins, meaning a feature row is still returned even when no condition or unit of measure is recorded. The joins to FLV1 (the feature type lookup) and to the base table are inner joins.

Key Columns

• LOCATION_FEATURE_ID — primary key of the underlying feature record; uniquely identifies the row.
• LOCATION_ID — foreign key to the property location (PN_LOCATIONS) to which the feature belongs.
• FEATURE_SIZE — the quantitative size or measurement of the feature; the focus of the "feature_size" search.
• UOM_CODE / UNIT_OF_MEASURE — the unit qualifying FEATURE_SIZE; UNIT_OF_MEASURE is the resolved descriptive name.
• QUANTITY — the number of units of the feature present.
• LOCATION_FEATURE_LOOKUP_CODE / LOCATION_FEATURE — the coded feature type and its resolved MEANING.
• CONDITION_LOOKUP_CODE / FEATURE_CONDITION — the coded condition and its resolved meaning.
• DESCRIPTION — free-text description of the feature.
• ORG_ID — operating unit identifier used for multi-org security.
• ATTRIBUTE_CATEGORY and ATTRIBUTE1–ATTRIBUTE15 — the standard EBS DFF columns for extensible attribute storage.
• WHO columns (CREATION_DATE, CREATED_BY, LAST_UPDATE_DATE, LAST_UPDATED_BY, LAST_UPDATE_LOGIN) and ROW_ID.

Common Use Cases and Queries

The view is typically used in property inspection reports, lease abstracts, and integration extracts that must publish location characteristics in descriptive form. A representative query returns all features for a given location:

SELECT location_feature_id,
       location_feature,
       feature_size,
       unit_of_measure,
       quantity,
       feature_condition
FROM   apps.pn_location_features_v
WHERE  location_id = :p_location_id
ORDER  BY location_feature;

To summarize total measured size by feature type and unit:

SELECT location_feature,
       unit_of_measure,
       SUM(feature_size) total_size,
       SUM(quantity)     total_qty
FROM   apps.pn_location_features_v
GROUP  BY location_feature, unit_of_measure;

For multi-org integrations, constrain by ORG_ID or filter against the current operating unit context. Because the view performs the lookup and UOM resolution internally, downstream consumers avoid the joins to FND_LOOKUPS and MTL_UNITS_OF_MEASURE, simplifying extracts while preserving the EBS lookup semantics.