Results for “position_location”

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

Overview

HR_HIER_POS_PEOPLE_V is a reporting view owned by the APPS schema in Oracle E-Business Suite, delivered as part of the PER (Human Resources) product family. As its ETRM description states, it presents "People with position details and place in position hierarchy." The view is a denormalized reporting construct that joins assignment and person attributes to position, job, location and organization attributes, and — critically — to the recursive position hierarchy structures stored in PER_POS_STRUCTURE_ELEMENTS and PER_POS_STRUCTURE_VERSIONS. Each row therefore represents a person occupying a position, together with that position's parent placement within a named position hierarchy.

Because it is a view rather than a table, it stores no data of its own; it is a read-only projection intended for extraction, reporting and third-party integration. Its name and the presence of the HR_THIRD_PARTY_INTERFACE_PKG package in its definition indicate that it was designed for outbound HR data feeds, where position-hierarchy context is required alongside employee details. The view is documented as VALID in the ETRM 12.2.2 catalog and is compatible with both 12.1.1 and 12.2.2 application releases.

Underlying Base Objects

The view is defined over a mixture of base tables, synonyms and other views. The principal driver is HR_HIER_ASG_PEOPLE_V, itself a view that supplies assignment and person attributes. This is joined one-to-many to PER_POS_STRUCTURE_ELEMENTS (PSE) and PER_POS_STRUCTURE_VERSIONS (PSV), which together model the versioned position hierarchy: PSV links a position structure version to its parent PER_POSITION_STRUCTURES row, and PSE supplies the parent/subordinate position pairs.

Position and job descriptive data come from HR_ALL_POSITIONS_F, HR_ALL_POSITIONS_F_TL, PER_ALL_POSITIONS, PER_JOBS and PER_JOBS_TL. Organizational context is provided by HR_ALL_ORGANIZATION_UNITS, joined twice — once for the business group (BG) and once for the position's owning organization (ORG). Location data is sourced from HR_LOCATIONS (a view) and the assignment-level location is carried on the assignment row. Two language joins restrict job and position translations to USERENV('LANG'). Date validation is performed through HR_THIRD_PARTY_INTERFACE_PKG.GET_EXTRACT_DATE and HR_GENERAL, which bound effective-dated rows (structure versions, organizations and jobs) to a single extract date, ensuring a point-in-time snapshot.

Key Columns

• PFT.NAME / JBT.NAME / ORG.NAME / BG.NAME / PS.NAME — position name, job name, position organization, business group and position structure name.
• PASG.FULL_NAME, EMPLOYEE_NUMBER, KNOWN_AS, EMAIL_ADDRESS, WORK_PHONE_NUMBER, MAILSTOP — person and assignment-level contact attributes.
• PASG.ASSIGNMENT_LOCATION, LOC.LOCATION_CODE — the assignment's location and the position's location code.
• PSV.DATE_FROM, DATE_TO, VERSION_NUMBER — effective dates and version of the position structure in force at extract time.
• PSE.SUBORDINATE_POSITION_ID, PSE.PARENT_POSITION_ID — the position and its immediate parent within the hierarchy, enabling recursive traversal.
• POS.TIME_NORMAL_START / FINISH, PASG.TIME_NORMAL_START / FINISH — standard working hours at position and assignment level.

Common Use Cases and Queries

Typical uses include producing organization charts, headcount-by-hierarchy reports, and extract files for third-party HR or payroll systems.

• Count employees reporting through a given structure at the current extract date.
• Reconstruct a reporting line by walking PARENT_POSITION_ID to SUBORDINATE_POSITION_ID.
• Feed position and incumbent data into an external HR portal.

Sample query:

SELECT full_name, employee_number, name, parent_position_id, subordinate_position_id, version_number FROM apps.hr_hier_pos_people_v WHERE version_number IS NOT NULL ORDER BY name, full_name;