Results for “pn_feature_condition”

12 results




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

Overview

The APPS.PN_LOCATION_FEATURES_V view is a reporting and integration object within the Oracle E-Business Suite Property Manager (PN) module. It presents a denormalized, human-readable projection of the PN_LOCATION_FEATURES base table, resolving internal lookup codes into their descriptive meanings and joining unit-of-measure codes to their formal names. The view exposes one row per location feature record, combining transactional attribute data with descriptive decode values drawn from the FND_LOOKUPS view. Its principal role is to simplify querying and external integration by delivering the location of a feature, its type, its condition, its quantity, size, and unit of measure in a single self-contained result set, without requiring the caller to independently join to the lookup and UOM reference data. The object is owned by APPS and is available in both Oracle EBS 12.1.1 and 12.2.2, with the ETRM metadata catalogued at the 12.2.2 level.

Underlying Base Objects

The view is defined over four documented base references:

  • PN_LOCATION_FEATURES (SYNONYM) — the driving table, aliased locf, which holds the location feature records including their lookup codes, quantities, and descriptive flexfield attributes.
  • FND_LOOKUPS (VIEW) — referenced twice, as aliases flv1 and flv2, to translate stored lookup codes into their meanings.
  • MTL_UNITS_OF_MEASURE (SYNONYM) — aliased uom, providing the formal unit-of-measure description for the stored uom_code.
  • FND_GLOBAL (PACKAGE) — referenced in the broader view definition (typically for org context via org_id), supporting multi-organization security and context resolution.

The joins are governed by specific lookup types. The flv1 join is an inner join constrained by lookup_type = 'PN_LOCATION_FEATURE_TYPE', matching lookup_code to location_feature_lookup_code. The flv2 join is an outer join ((+)) constrained by lookup_type = 'PN_FEATURE_CONDITION', matching lookup_code to condition_lookup_code. The UOM join is likewise an outer join on uom_code. These outer joins allow records with unset condition or UOM values to remain visible in the result set.

Key Columns

Common Use Cases and Queries

Typical uses include location feature inventory reporting, condition-based analysis, and integration extracts.

  • List all features at a location with decoded types, conditions, and UOM.
  • Filter by feature condition using the decoded meaning.
  • Report features lacking a defined condition or unit of measure.

Sample queries:

SELECT location_feature_id, location_id, location_feature, feature_condition, quantity, unit_of_measure
FROM   apps.pn_location_features_v
WHERE  location_id = :p_location_id;
SELECT location_id, location_feature, feature_condition
FROM   apps.pn_location_features_v
WHERE  feature_condition = 'Good';
SELECT location_feature_id, condition_lookup_code
FROM   apps.pn_location_features_v
WHERE  feature_condition IS NULL;