Search Results assignment_location




Overview
Explore in AI Chat

Overview

APPS.HR_HIER_POS_PEOPLE_V is a public Oracle E-Business Suite view owned by the APPS schema, registered under FND Design Data as PER.HR_HIER_POS_PEOPLE_V with a status of VALID. Its documented purpose is to present "people with position details and place in position hierarchy," making it a reporting-oriented object suitable for custom reporting and other data requirements without exposing callers to the underlying normalized HR tables directly.

The view is commonly reached by searches involving assignment_location, because it exposes both ASSIGNMENT_LOCATION (the location of an assignment) and POSITION_LOCATION (the location tied to a position). This lets a single query report a person's assignment location alongside the position's home location, the position's place in a hierarchy, and the hierarchy version effective dates. As a public view it is broadly accessible under the APPS schema in both 12.1.1 and 12.2.2, and is intended for read-only reporting or integration extraction rather than transactional update.

Underlying Base Objects

The documented base objects show the view is a join across HR position, organization, and hierarchy structures, layered on top of other views and packages. Position attributes are sourced from HR_ALL_POSITIONS_F, PER_ALL_POSITIONS, and their translated name table HR_ALL_POSITIONS_F_TL. Job and organization context come from PER_JOBS and PER_JOBS_TL, plus HR_ALL_ORGANIZATION_UNITS. Hierarchy data — hierarchy name, structure version, and parent position — is drawn from PER_POSITION_STRUCTURES, PER_POS_STRUCTURE_ELEMENTS, and PER_POS_STRUCTURE_VERSIONS. Location attributes are retrieved through the HR_LOCATIONS view, and person-level assignment data is layered through the HR_HIER_ASG_PEOPLE_V view. Two PL/SQL packages, HR_GENERAL and HR_THIRD_PARTY_INTERFACE_PKG, are referenced, typically for date/name resolution and interface logic. The view therefore composes positional hierarchy, assignment, and person columns on top of the core HR model rather than storing data itself.

Key Columns

Common Use Cases and Queries

Typical reporting scenarios include locating all assignments at a given location, comparing position location to assignment location, listing personnel by organization within a hierarchy, and reproducing an effective-dated hierarchy snapshot. Where multiple hierarchy versions exist, filter on HIERARCHY_VERSION_START_DATE and HIERARCHY_VERSION_END_DATE to select the correct effective version.

Sample query by assignment location:

  • SELECT full_name, employee_number, position_name, job_name, organization_name, assignment_location, position_location
  • FROM apps.hr_hier_pos_people_v
  • WHERE assignment_location = '&loc'
  • ORDER BY full_name;

To compare the two location columns, add a predicate such as WHERE assignment_location <> position_location. Because the view derives from effective-dated HR entities, callers should also expect version rows and apply date filters where a single current record is required.