Search Results pn_space_assign_cust_pub_v




Overview
Explore in AI Chat

Overview

The PN_SPACE_ASSIGN_CUST_PUB_V view is a public, API-facing database object owned by the APPS schema within the Oracle E-Business Suite Property Manager (PN) module. Its documented purpose is to expose customer space assignment information for reporting and integration purposes. In EBS 12.1.1 and 12.2.2, the PN product manages the leasing, allocation, and utilization of physical space, and this view serves as the sanctioned, denormalized read interface over the underlying transactional table that stores customer assignments to locations. Rather than requiring external consumers to join the base assignment table to several Oracle Customers (HZ) and Property Manager (PN) master tables themselves, the view presents a single, business-friendly result set. It is referenced by the documented search term cust_space_assign_id, which is the primary key of the underlying record and the natural join and filter key for any query against this view.

Underlying Base Objects

Per the ETRM 12.2.2 metadata, the view is defined over the following objects:

The view therefore functions as a convenience join layer connecting the space assignment transaction to the Trading Community Architecture (TCA) customer model and Property Manager location master data.

Key Columns

The view exposes a wide set of columns. The principal identifier is CUST_SPACE_ASSIGN_ID, the unique key for a customer assignment. LOCATION_ID and the aliased location columns (LOCATION_CODE, LOCATION_SUITE_NAME, LOCATION_TYPE_LOOKUP_CODE) describe the physical space. Customer identity is carried by CUST_ACCOUNT_ID, CUSTOMER_NAME, SITE_USE_ID, and CUSTOMER_SITE. Classification and status appear through CUSTOMER_CATEGORY, CUSTOMER_CLASS, PROFILE_CLASS, SIC_CODE, and CUSTOMER_STATUS. Lease and financial linkage is provided by PROJECT_ID, TASK_ID, LEASE_ID, and EXPENSE_ACCOUNT_ID. Area and occupancy metrics include ALLOCATED_AREA_PCT, ALLOCATED_AREA, UTILIZED_AREA, and UOM_CODE. Date ranges are captured by CUST_ASSIGN_START_DATE and CUST_ASSIGN_END_DATE. Standard audit and descriptive flexfield columns (ATTRIBUTE1 through ATTRIBUTE15, ATTRIBUTE_CATEGORY) are also exposed, along with ORG_ID for multi-org security.

Common Use Cases and Queries

Typical scenarios include reporting on which customers occupy which locations, calculating allocated versus utilized area, and integrating customer assignments into external systems. The following query retrieves active assignments for a given organization:

  • SELECT cust_space_assign_id, customer_name, location_code, cust_assign_start_date, cust_assign_end_date, allocated_area FROM pn_space_assign_cust_pub_v WHERE org_id = :p_org_id AND (cust_assign_end_date IS NULL OR cust_assign_end_date > SYSDATE);

To resolve a specific record by the documented search term, the assignment ID is used directly:

  • SELECT * FROM pn_space_assign_cust_pub_v WHERE cust_space_assign_id = :p_id;

Because the view joins TCA and Property Manager masters, it is well suited to discoverer reports, BI Publisher data templates, and interface extracts that require customer, location, and area data in one retrieval pass.