Results for “location_feature_lookup_code”

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

Overview

PN_LOCATION_FEATURES_ALL is a Property Manager (PN) transactional and descriptive table in Oracle E-Business Suite Releases 12.1.1 and 12.2.2. It stores information about the physical features available within a building or other property location managed through the PN module. Records in this table associate a specific feature definition (for example, a conference facility, loading dock, HVAC unit, or parking structure) with the location where that feature exists, together with descriptive detail such as quantity, size, unit of measure, and condition.

The table is owned by the PN schema and resides in the APPS-enabled environment under the standard multi-org conventions signalled by the _ALL suffix and the presence of the ORG_ID column. The documented primary key is PN_LOCATION_FEATURES_PK on LOCATION_FEATURE_ID, and a unique index PN_LOCATION_FEATURES_U1 also exists on LOCATION_FEATURE_ID. A single foreign key is documented: LOCATION_ID references PN_LOCATIONS_ALL, anchoring each feature row to the property location that owns it.

Under the heuristic Data Vault classification derived from the foreign-key structure, this table is satellite-leaning. In modeling terms, this suggests treating PN_LOCATION_FEATURES_ALL primarily as a descriptive satellite attached to a location or location-feature hub, rather than as an independent hub or a pure link. Its descriptive columns (quantity, size, condition, and descriptive flexfield attributes) support this interpretation.

Key Information Stored

The table is documented with 30 columns. The most significant are:

• LOCATION_FEATURE_ID — Surrogate primary key (PN_LOCATION_FEATURES_PK) and also the unique-indexed business-key candidate (PN_LOCATION_FEATURES_U1). Uniquely identifies each feature instance.
• LOCATION_ID — Foreign key to PN_LOCATIONS_ALL; identifies the building or property location to which the feature belongs.
• LOCATION_FEATURE_LOOKUP_CODE — Code classifying the type of feature (validated against the appropriate Oracle lookup type).
• DESCRIPTION — Free-text description of the feature.
• QUANTITY — Number of units of the feature present at the location.
• FEATURE_SIZE — Size or physical measurement of the feature.
• UOM_CODE — Unit of measure associated with FEATURE_SIZE.
• CONDITION_LOOKUP_CODE — Code indicating the condition or status of the feature.
• ORG_ID — Operating unit identifier supporting multi-org data partitioning.
• ATTRIBUTE_CATEGORY and ATTRIBUTE1–ATTRIBUTE15 — Descriptive flexfield columns for capturing client-specific feature attributes.
• Audit columns: LAST_UPDATE_DATE, LAST_UPDATED_BY, CREATION_DATE, CREATED_BY, LAST_UPDATE_LOGIN.

Common Use Cases and Queries

The table is most often queried to report feature inventories per location, to support leasing or space-management analysis, and to drive maintenance or condition assessments. Because it is multi-org enabled, queries should filter by ORG_ID where operating-unit context applies.

A typical join retrieves all features for a location:

SELECT f.location_feature_id,
       f.location_feature_lookup_code,
       f.description,
       f.quantity,
       f.feature_size,
       f.uom_code,
       f.condition_lookup_code
FROM   pn_location_features_all f
WHERE  f.location_id = :p_location_id
AND    f.org_id = :p_org_id;

Reporting patterns frequently aggregate quantity and size by feature type to compare facilities across a portfolio, or join to PN_LOCATIONS_ALL to present address and building context. Extension queries may read the ATTRIBUTE flexfield columns, and condition-based queries use CONDITION_LOOKUP_CODE to identify features requiring attention.

Related Objects

• PN_LOCATIONS_ALL — Parent location table; joined on PN_LOCATION_FEATURES_ALL.LOCATION_ID = PN_LOCATIONS_ALL.LOCATION_ID (documented foreign key).
• PN_LOCATIONS_V — View over locations, commonly joined to present location detail alongside features.
• PN_LOCATION_FEATURES_PK / PN_LOCATION_FEATURES_U1 — Primary and unique constraints enforcing key integrity.
• PN lookup types — Backing the LOCATION_FEATURE_LOOKUP_CODE and CONDITION_LOOKUP_CODE columns.
• PN Property Manager concurrent programs and forms — UI and batch components that create and maintain feature records.

These relationships establish PN_LOCATION_FEATURES_ALL as the descriptive detail layer supporting location-level facility and feature management within Oracle Property Manager.