Search Results addr_attribute7




Overview
Explore in AI Chat

Overview

PN_LOCATIONS_ITF is an interface (staging) table owned by the PN schema within the Oracle Property Manager module. It stores space definition data that is imported into or exported out of Oracle Property Manager. Rather than representing a permanent transactional entity, the table acts as a transient holding area where location, floor, office, area, and capacity attributes are staged before being validated and transferred into the core Property Manager location structures, or where existing location records are exported for external processing.

Because the table is populated and consumed by concurrent programs rather than maintained as a long-lived master, each row carries a BATCH_NAME to group related import records and an ENTRY_TYPE to distinguish import from export activity. The presence of TRANSFERRED_TO_PN, TRANSFERRED_TO_CAD, ERROR_MESSAGE, and REQUEST_ID columns confirms its role in an interface-driven integration cycle.

Mined from its foreign key structure, the heuristic Data Vault classification for this object is satellite-leaning. It references PN_PROPERTIES_ALL, and the modeling suggestion is therefore to treat PN_LOCATIONS_ITF as a satellite attached to the property hub, capturing descriptive location detail rather than defining independent business entities.

Key Information Stored

The table is physically wide, with 91 documented columns in the ETRM 12.2.2 schema. The most significant columns for integration and reporting purposes are:

Common Use Cases and Queries

The most frequent operational pattern is monitoring an import or export run by batch. A typical query retrieves all rows for a batch and surfaces any rows that failed validation:

  • Select rows for a batch: SELECT LOCATION_CODE, ENTRY_TYPE, TRANSFERRED_TO_PN, ERROR_MESSAGE FROM PN_LOCATIONS_ITF WHERE BATCH_NAME = :batch;
  • Identify failed imports: filter on ERROR_MESSAGE IS NOT NULL or TRANSFERRED_TO_PN = 'N'.
  • Join to the property master to enrich reporting: SELECT i.LOCATION_CODE, p.PROPERTY_NAME FROM PN_LOCATIONS_ITF i JOIN PN_PROPERTIES_ALL p ON i.PROPERTY_ID = p.PROPERTY_ID;
  • Reconcile area totals per property by summing RENTABLE_AREA and USABLE_AREA grouped by PROPERTY_ID.

Reporting use cases include space-utilization analysis, capacity planning, and validation of CAD-to-Property-Manager space synchronization.

Related Objects

The following objects are most closely associated with PN_LOCATIONS_ITF:

Together these objects complete the Property Manager space-definition integration path.