Results for “manager_first_name”

AI-generated from documented ETRM metadata — verify critical details on the linked pages.

Overview

PA_MANAGERS_V is a Projects (PA) module view owned by the APPS schema and validated in Oracle E-Business Suite 12.1.1 and 12.2.2. Its documented purpose is to expose manager details for all primary, active assignments. In practice, the view returns one row per active supervisor, joining the supervisor's person record to the assignment and organization in which that supervisor holds a primary, active position. The column most frequently requested by users, MANAGER_FULL_NAME, corresponds to the PER.FULL_NAME attribute derived from the PER_PEOPLE_X view and the HR_PERSON_NAME package, which formats a person's name according to the current HR name-formatting rules. Because name formatting is resolved at query time through HR packages, the value returned reflects the effective-dated person record rather than a denormalized stored string. The view is read-only and intended for reporting, concurrent programs, and integration extracts where a manager name and organizational context are required without navigating the full HR assignment model.

Underlying Base Objects

The view is defined over the following documented objects: PER_ASSIGNMENTS_F (view), PER_PEOPLE_X (view), PER_ASSIGNMENT_STATUS_TYPES (synonym), HR_ORGANIZATION_UNITS (view), HR_GENERAL (package), HR_PERSON_NAME (package), HR_SECURITY (package), and FND_LOOKUP_VALUES (synonym). The core join is self-referential on PER_ASSIGNMENTS_F: the supervisor's primary active assignment (ASSIGN) is matched to the supervisor's person row in PER_PEOPLE_X, and to a second assignment row (ASSIGN2) that carries the supervisor's own organization and effective dates. Filtering is enforced by PER_ASSIGNMENT_STATUS_TYPES, restricted to system statuses ACTIVE_ASSIGN and ACTIVE_CWK, with assignment types limited to Employee (E) and Contingent Worker (C). Only rows flagged PRIMARY_FLAG = 'Y' with a non-null JOB_ID and an effective end date null or on or after the current truncation of SYSDATE are returned. The organization name is resolved from HR_ORGANIZATION_UNITS via ORGANIZATION_ID. HR_GENERAL, HR_PERSON_NAME, and HR_SECURITY supply name formatting and security context; FND_LOOKUP_VALUES supports lookup-derived attributes.

h4>Key Columns

• MANAGER_FIRST_NAME — Supervisor's given name (PER.FIRST_NAME).
• MANAGER_LAST_NAME — Supervisor's family name (PER.LAST_NAME).
• MANAGER_FULL_NAME — Formatted full name (PER.FULL_NAME), typically the value searched by users.
• MANAGER_ID — Supervisor's person identifier (ASSIGN.SUPERVISOR_ID).
• ORGANIZATION — Name of the organization unit (HRORG.NAME).
• ORGANIZATION_ID — Internal identifier of the organization unit (ASSIGN2.ORGANIZATION_ID).
• START_DATE — Effective start date of the supervisor's assignment (ASSIGN2.EFFECTIVE_START_DATE).
• END_DATE — Effective end date of the assignment (ASSIGN2.EFFECTIVE_END_DATE).

Common Use Cases and Queries

Typical uses include listing managers for a given organization, validating supervisor assignments in Projects staffing reports, and feeding manager names into extracts or interfaces. Because the view already filters to active primary assignments, callers need not reapply assignment status logic.

Example — find a manager by full name:

SELECT manager_full_name, manager_id, organization
FROM   apps.pa_managers_v
WHERE  manager_full_name LIKE :p_name || '%';

Example — list managers within an organization:

SELECT organization_id, organization, manager_full_name, start_date, end_date
FROM   apps.pa_managers_v
WHERE  organization_id = :p_org_id
ORDER  BY manager_last_name;

Standard APPS schema grants apply; query through the APPS account or a synonym with appropriate HR security access, since HR_SECURITY governs which person records are visible.