Search Results pn_space_assign_emp_u1




Overview

The PN.PN_SPACE_ASSIGN_EMP_ALL table is a transactional data object within the Oracle EBS Project Manufacturing (PN) schema that stores employee space assignment information. Each row represents the allocation of physical space at a defined location to a specific employee over a bounded date range, and the assignment is fully date tracked to preserve historical occupancy records. In Oracle EBS 12.1.1 and 12.2.2, the table supports facilities, real estate, and project-driven space management business flows, where organizations must attribute occupied area to people, projects, tasks, and cost centers for reporting and chargeback purposes.

From a Data Vault modeling perspective, the mined metadata classifies this object heuristically as a link. This is a modeling suggestion rather than a physical designation: the table carries foreign keys to PA_PROJECTS_ALL and PA_TASKS, and holds surrogate references to locations, persons, and tasks, functioning as a relationship table between multiple business entities rather than as a standalone hub or a pure descriptive satellite. The physical schema is documented as containing 36 columns, with the primary key defined as PN_SPACE_ASSIGN_EMP_PK on EMP_SPACE_ASSIGN_ID.

Key Information Stored

The most business-significant columns include the following:

Common Use Cases and Queries

Typical usage includes space utilization reporting, occupancy reconciliation against locations, and project chargeback calculations. A frequent pattern joins the table to person and location masters while filtering on the active date window:

  • Active assignments by location: query rows where SYSDATE BETWEEN EMP_ASSIGN_START_DATE AND NVL(EMP_ASSIGN_END_DATE, SYSDATE), joining LOCATION_ID to PN_LOCATIONS_ALL.
  • Headcount-to-area analysis: aggregate ALLOCATED_AREA, UTILIZED_AREA, and ALLOCATED_AREA_PCT by COST_CENTER_CODE or ORG_ID.
  • Project space costing: join PROJECT_ID to PA_PROJECTS_ALL and TASK_ID to PA_TASKS to attribute occupied space to project budgets.
  • Employee occupancy history: query by PERSON_ID ordered by EMP_ASSIGN_START_DATE to reconstruct date-tracked space history.

Indexes PN_SPACE_ASSIGN_EMP_N1 through N7 on start date, end date, location, person, project, task, and cost center support these access paths efficiently.

Related Objects

  • PN_LOCATIONS_ALL — Joined via LOCATION_ID; provides location master details.
  • PER_ALL_PEOPLE_F — Joined via PERSON_ID; supplies employee information.
  • PA_PROJECTS_ALL — Foreign key relationship on PROJECT_ID.
  • PA_TASKS — Foreign key relationship on TASK_ID (references PA_TASKS_ALL).
  • PN_EMP_SPACE_ASSIGN_ITF — Interface table referencing EMP_SPACE_ASSIGN_ID, used to import space assignment data into this table.
  • PN_SPACE_ASSIGN_EMP_S — Sequence supplying the primary key values.