Search Results pn_space_assign_cust




Overview
Explore in AI Chat

Overview

APPS.PN_SPACE_ASSIGN_CUST_V is a reporting view in the Oracle E-Business Suite Property Manager (PN) module. It presents customer space assignments — the allocation of leasable or owned space within a location to a specific customer account, site use, and (optionally) project and task. The view is a denormalized, read-only projection that joins the transactional assignment table PN_SPACE_ASSIGN_CUST to location, lease, customer, and lookup reference data, so that business users, reports, and interfaces can retrieve fully described space-assignment records without manually joining the underlying ETRM tables.

In EBS 12.1.1 and 12.2.2 the view is owned by APPS and is typically consumed through Oracle Reports, BI Publisher data models, OA Framework pages, custom concurrent programs, and ad hoc SQL. It carries no editioning (no _ALL suffix) because its driving table is non-ML; all rows are visible to the querying operating unit according to the location's ORG_ID, which the view exposes as a column.

Underlying Base Objects

The view is built over one primary transactional object and several supporting objects:

  • PN_SPACE_ASSIGN_CUST — the driving table holding customer space-assignment records (aliased PSAC). Supplies the assignment identifiers, dates, allocated and utilized areas, lease and tenancy references, recovery attributes, and the DFF columns ATTRIBUTE1–15.
  • PN_LOCATIONS (PL) — the location master, providing location code, type lookup code, suite name, unit of measure, active dates, and ORG_ID.
  • PN_LEASES (PLE) — supplies the lease name.
  • HZ_PARTIES (HP) — the customer party, providing party_name and sic_code.
  • HZ_CUST_ACCOUNTS_ALL (HCA) — supplies the customer account status.
  • HZ_CUST_SITE_USES_ALL (HCSU) — supplies the customer site (location).
  • HZ_CUST_PROFILES and HZ_CUST_PROFILE_CLASSES — provide the profile class name.
  • FND_LOOKUPS and AR_LOOKUPS — decode the customer category and customer class meanings; FND_LOOKUPS also resolves the recovery space standard and recovery type codes via SPST and RCTY.

FND_GLOBAL appears in the referenced metadata, consistent with the use of FND_GLOBAL.ORG_ID or similar session context in the view's WHERE clause.

Key Columns

Common Use Cases and Queries

Typical scenarios include customer space-occupancy reporting, expense-allocation and recovery analysis, lease-to-customer reconciliation, and integration extracts feeding downstream cost systems.

Current customer space assignment by location:

  • SELECT location_code, suite_name, customer_name, customer_site, allocated_area, uom_code FROM apps.pn_space_assign_cust_v WHERE cust_account_id = :p_account AND SYSDATE BETWEEN cust_assign_start_date AND NVL(cust_assign_end_date, SYSDATE+1);

Total allocated area per lease for an operating unit:

  • SELECT lease_name, SUM(allocated_area) total_area FROM apps.pn_space_assign_cust_v WHERE org_id = :p_org GROUP BY lease_name;

Assignments approaching customer-assignment end date:

  • SELECT cust_space_assign_id, customer_name, location_code, cust_assign_end_date FROM apps.pn_space_assign_cust_v WHERE cust_assign_end_date BETWEEN SYSDATE AND SYSDATE+90 ORDER BY cust_assign_end_date;

Recovery analysis by recovery type and space standard:

  • SELECT recovery_type_desc, recovery_space_std_desc, customer_category, SUM(utilized_area) FROM apps.pn_space_assign_cust_v WHERE recovery_type_code IS NOT NULL GROUP BY recovery_type_desc, recovery_space_std_desc, customer_category;

Because the view resolves operational codes into descriptive meanings at query time, standard practice is to filter on ID or code columns for performance and to restrict by ORG_ID in multi-organization implementations.