Search Results pon_employees_current_v




Overview
Explore in AI Chat

Overview

PON_EMPLOYEES_CURRENT_V is an APPS-owned database view within the Oracle E-Business Suite Sourcing (PON) product module. Its purpose is to present a consolidated, point-in-time snapshot of currently active employees, exposing identifying, contact, and assignment-level attributes in a single row per employee. Each row includes the full name, first name, middle names, last name, employee number, person identifier, effective period, email address, work telephone number, position, organization, and job title of the current employee. Because it returns a flattened, human-readable employee picture, the view is well suited for Sourcing reports, supplier collaboration screens, and integration interfaces that must resolve a person identifier to a display name or contact detail without navigating the full HRMS effective-dating model. The view is documented as VALID and carries a dependency on the HR_SECURITY package, meaning row-level access is governed by the HR security profile of the querying user.

Underlying Base Objects

The view is defined over seven documented base objects, all referenced through APPS synonyms: PER_ALL_PEOPLE_F, PER_ALL_ASSIGNMENTS_F, PER_PERIODS_OF_SERVICE, PER_ALL_POSITIONS, PER_PHONES, PER_JOBS, and PER_PERIODS_OF_PLACEMENT, together with the HR_SECURITY package. The primary driver is PER_ALL_PEOPLE_F, which supplies name, employee number, person identifier, business group, effective dates, and email. PER_ALL_ASSIGNMENTS_F supplies the primary assignment, organization, position, and job references, and is joined on PERSON_ID with PRIMARY_FLAG set to the primary assignment. The join to PER_PERIODS_OF_SERVICE enforces that the employee has not been terminated as of the current date. PER_ALL_POSITIONS and PER_JOBS are outer-joined to resolve position name and job title, while PER_PHONES is outer-joined on PERSON_ID for the W1 (work) telephone type. A UNION ALL branch extends the result set to contingent workers sourced through PER_PERIODS_OF_PLACEMENT, using the NPW_NUMBER as the employee number.

Key Columns

Common Use Cases and Queries

Typical scenarios include populating employee pick lists in Sourcing negotiation and sourcing event pages, resolving buyer names on reports, and supplying employee contact data to supplier-facing interfaces. Because the view already filters for current employees and primary assignments, callers do not need to apply their own effective-date logic. Row-level security is applied automatically through HR_SECURITY, so results reflect only persons the querying user is permitted to see.

A simple lookup by person identifier:

SELECT person_id, employee_number, full_name, email_address, phone_number, position, job_title FROM apps.pon_employees_current_v WHERE person_id = :p_person_id;

A search by name or number for a pick list:

SELECT employee_number, full_name, position, organization_id FROM apps.pon_employees_current_v WHERE UPPER(full_name) LIKE UPPER(:p_name || '%') OR employee_number = :p_number ORDER BY full_name;

Joining to an assignment-driven table to enrich sourcing records:

SELECT s.negotiation_id, e.full_name, e.job_title, e.email_address FROM apps.pon_employees_current_v e, apps.pon_negotiations s WHERE s.buyer_id = e.person_id;