Search Results pa_tasks_all




Overview
Explore in AI Chat

Overview

The APPS.PN_SPACE_ASSIGN_EMP_PUB_V view is a public Oracle E-Business Suite view owned by the APPS schema and registered under FND Design Data identifier PN.PN_SPACE_ASSIGN_EMP_PUB_V. Its status is VALID in both 12.1.1 and 12.2.2. As a public view, it is intended to support custom reporting and data extraction requirements without exposing consumers to the underlying normalized table structure of the Property Manager (PN) module. The view identifies an employee space assignment and its associated attributes, joining space allocation records to person, assignment, location, and organization data. It therefore serves as a denormalized read-only interface for facilities, real estate, and HR-integrated reporting, allowing space occupancy to be analyzed in the context of the employee assigned to a given location or suite.

Underlying Base Objects

The view is defined over the following documented base objects: PN_SPACE_ASSIGN_EMP_ALL, PN_LOCATIONS_ALL, PER_ALL_PEOPLE_F, PER_ALL_ASSIGNMENTS_F, PER_JOBS, PER_PERSON_TYPES_TL, PER_PHONES, HR_ORGANIZATION_UNITS, and FND_LOOKUP_VALUES, supplemented by the packages HR_GENERAL, HR_SECURITY, and PNP_UTIL_FUNC. PN_SPACE_ASSIGN_EMP_ALL is the primary transactional table holding employee space assignment rows, with EMP_SPACE_ASSIGN_ID populated from the PN_SPACE_ASSIGN_EMP_S sequence. PN_LOCATIONS_ALL supplies location attributes such as location code, suite name, and location type. PER_ALL_PEOPLE_F and PER_ALL_ASSIGNMENTS_F contribute employee identity, effective-dated employment, and assignment context; HR_SECURITY applies row-level person security so that only authorized employees are visible. FND_LOOKUP_VALUES resolves lookup-coded values, and PER_PERSON_TYPES_TL, PER_JOBS, and PER_PHONES enrich person type, job, and contact information. The user search term "pa_tasks_all" does not appear in the dependency list for this view; PA_TASKS_ALL belongs to Oracle Projects and is unrelated to the PN space assignment object model.

Key Columns

Identification columns include ROW_ID (ROWID), EMP_SPACE_ASSIGN_ID (the sequence-generated primary key of the assignment), and PERSON_ID, which links to PER_ALL_PEOPLE_F. LOCATION_ID and LOCATION_LOCATION_ID associate the record with PN_LOCATIONS_ALL, complemented by LOCATION_TYPE_LOOKUP_CODE, LOCATION_SUITE_NAME, and LOCATION_CODE. Date-effecting columns include ACTIVE_START_DATE and ACTIVE_END_DATE for the location, and EMP_EFFECTIVE_START_DATE and EMP_EFFECTIVE_END_DATE for the employee. Employee attributes consist of ASSIGNMENT_ID, LAST_NAME, FIRST_NAME, FULL_NAME, EMPLOYEE_NUMBER, EMAIL_ADDRESS, and PERSON_TYPE_ID. Together these columns provide a single-row view of who occupies which space, when the occupation is valid, and the organizational and personal context of that occupant.

Common Use Cases and Queries

Typical uses include facilities occupancy reports, space utilization dashboards, and HR-integrated headcount-versus-seat analyses. Because HR_SECURITY is applied, result sets are automatically restricted to the security profile of the querying user.

  • Listing active space assignments for a suite or building.
  • Reconciling employee locations against HR assignment data.
  • Extracting occupancy data for a data warehouse or third-party facilities system.

Example query by location:

SELECT emp_space_assign_id, full_name, employee_number, location_code, location_suite_name, active_start_date, active_end_date FROM apps.pn_space_assign_emp_pub_v WHERE location_code = :p_location_code AND TRUNC(SYSDATE) BETWEEN active_start_date AND NVL(active_end_date, TRUNC(SYSDATE));

Example query by person:

SELECT full_name, email_address, location_code, assignment_id FROM apps.pn_space_assign_emp_pub_v WHERE person_id = :p_person_id AND TRUNC(SYSDATE) BETWEEN emp_effective_start_date AND NVL(emp_effective_end_date, TRUNC(SYSDATE));