Search Results pn_space_assign_emp_v




Overview
Explore in AI Chat

Overview

PN_SPACE_ASSIGN_EMP_V is a seeded Oracle E-Business Suite view owned by the APPS schema within the Property Manager (PN) product. It presents employee-level space assignments by combining records from the PN_SPACE_ASSIGN_EMP transaction table with supporting location and person attributes. In release 12.1.1 and 12.2.2 the view is registered as VALID and is available to any reporting, integration, or extension component that has been granted access to the APPS synonym. Because it exposes the descriptive flexfield columns (ATTRIBUTE_CATEGORY through ATTRIBUTE15) and standard WHO audit columns, it functions as a denormalized read model for space utilization analysis, occupancy reporting, and third-party facility interfaces.

The object is particularly relevant to searches involving "location_suite_name," which corresponds to the view column LOCATION_SUITE_NAME. That column is populated from PN_LOCATIONS.SUITE, providing the suite designation of the assigned location alongside the employee assignment details.

Underlying Base Objects

The documented view definition joins three base objects through APPS synonyms:

  • PN_SPACE_ASSIGN_EMP (alias PSAE) — the driving table holding the employee space assignment rows, including assignment dates, allocated and utilized area, project and task references, cost center, and comments.
  • PN_LOCATIONS (alias PL) — the location master, supplying location code, suite name, location type, unit of measure, active dates, and organization identifier.
  • PER_ALL_PEOPLE_F (alias PPF) — the effective-dated person record, supplying last name, first name, full name, and employee number.

The join between the assignment table and PN_LOCATIONS is an outer join on LOCATION_ID, filtered to exclude common areas via NVL(PL.COMMON_AREA_FLAG,'N') = 'N'. The person join is likewise outer and is constrained by SYSDATE BETWEEN PPF.EFFECTIVE_START_DATE(+) AND PPF.EFFECTIVE_END_DATE(+), so only the currently effective person row is returned. The view text includes a UNION ALL branch, indicating that a second query block is combined with the first to produce the complete result set.

Key Columns

Common Use Cases and Queries

Typical uses include employee seat and suite occupancy reports, area allocation chargeback extracts, reconciliation of assignments against the PN_LOCATIONS master, and integration feeds into facilities management systems. A representative query listing current assignments with suite and employee details follows:

  • SELECT employee_number, full_name, location_code, location_suite_name, allocated_area, utilized_area, emp_assign_start_date, emp_assign_end_date FROM apps.pn_space_assign_emp_v WHERE org_id = :p_org_id ORDER BY location_suite_name, full_name;
  • SELECT location_suite_name, SUM(utilized_area) total_area FROM apps.pn_space_assign_emp_v WHERE org_id = :p_org_id GROUP BY location_suite_name ORDER BY total_area DESC;

Because LOCATION_SUITE_NAME originates in PN_LOCATIONS.SUITE and the personnel attributes are effective-dated, consumers should filter by ORG_ID and be aware that results reflect the person record effective as of the query execution date.