Search Results current_cost_center_code

Overview

The PN_SPACE_ASSIGN_EMP_PUB_V view is a public, API-supported database object owned by the APPS schema within the Property Manager (PN) product of Oracle E-Business Suite. It is classified as a VIEW with VALID status and is documented for both the 12.1.1 and 12.2.2 releases. Its stated purpose is to expose employee-to-space assignment information in a denormalized, read-only form suitable for reporting, integration, and external consumption.

The "PUB" naming convention indicates that this is a public interface object. Oracle publishes such views as the sanctioned contract for customers and integrators to query assignment data without depending on internal, unsupported tables. This shields downstream code from structural changes to the underlying transactional tables, since Oracle is only obliged to preserve the published view's shape. In practice the view is the recommended entry point for anyone needing to reconcile which employee occupies which property location, along with the associated cost center, utilization, and assignment attributes.

Underlying Base Objects

The view is defined primarily over PN_SPACE_ASSIGN_EMP_ALL, the base table storing employee space assignment records, aliased as PSAE in the view text. It joins to several HRMS objects to enrich each assignment with person and assignment detail:

• PER_ALL_PEOPLE_F (PPF) — person name, employee number, email, and effective dating.
• PER_ALL_ASSIGNMENTS_F (PAF) — assignment ID, position, job, organization, and employment category.
• PER_JOBS, PER_PERSON_TYPES_TL, and PER_PHONES — job name, person type translation, and phone number.
• HR_ORGANIZATION_UNITS (HOU) — organization name resolution.
• PN_LOCATIONS_ALL (PL) — location code, suite, active dates, and unit of measure.
• FND_LOOKUP_VALUES (FLV) — decoding of the employment category lookup.
• Packages HR_GENERAL, HR_SECURITY, and PNP_UTIL_FUNC — used for position name decoding, security filtering, and cost center derivation respectively.

Where several tables are effective-dated, the join is constructed to return the current or relevant row, allowing a single flat result set per assignment.

Key Columns

The view exposes identity, location, and assignment attributes. Principal columns include:

• EMP_SPACE_ASSIGN_ID — primary key of the assignment record.
• LOCATION_ID, LOCATION_CODE, LOCATION_SUITE_NAME — the property space assigned.
• PERSON_ID, FULL_NAME, LAST_NAME, FIRST_NAME, EMPLOYEE_NUMBER, EMAIL_ADDRESS — the assigned employee.
• ASSIGNMENT_ID, POSITION, JOB, ORGANIZATION, EMPLOYMENT_CATEGORY_MEANING — HR assignment context.
• EMP_ASSIGN_START_DATE and EMP_ASSIGN_END_DATE — the occupancy period.
• COST_CENTER_CODE, CURRENT_COST_CENTER_CODE, ALLOCATED_AREA_PCT, ALLOCATED_AREA, UTILIZED_AREA, UOM_CODE — cost allocation and area metrics.
• Standard WHO columns (CREATION_DATE, LAST_UPDATE_DATE, etc.) and the DFF segment columns (ATTRIBUTE_CATEGORY, ATTRIBUTE1…).

Common Use Cases and Queries

Typical uses include space utilization reporting, occupancy audits, cost-center chargeback analysis, and feeds into corporate real estate systems. Because the view is a public object, it can be queried directly in reports and interfaces.

To list current occupants of a location:

• SELECT person_id, full_name, location_code, allocated_area FROM apps.pn_space_assign_emp_pub_v WHERE location_id = :p_location_id;

To summarize allocated versus utilized area by cost center:

• SELECT cost_center_code, SUM(allocated_area), SUM(utilized_area) FROM apps.pn_space_assign_emp_pub_v GROUP BY cost_center_code;

To find assignments active within a date range:

• SELECT employee_number, full_name, emp_assign_start_date, emp_assign_end_date FROM apps.pn_space_assign_emp_pub_v WHERE :p_date BETWEEN emp_assign_start_date AND NVL(emp_assign_end_date, :p_date);

Queries should account for the effective dating and HR security implicit in the underlying joins.