Results for “assignment_location”

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

Overview

The APPS.HR_HIER_ASG_PEOPLE_V view is a denormalized, single-row-per-primary-assignment reporting object shipped in the Oracle E-Business Suite Human Resources (PER) product. It presents a flattened projection of person, primary assignment, work telephone, location, and business-group attributes, allowing external consumers and third-party interfaces to retrieve key workforce data without joining the numerous underlying PER tables directly. Its name and column set indicate it was designed primarily to support third-party interface extraction — a role reinforced by the inclusion of HR_THIRD_PARTY_INTERFACE_PKG.GET_EXTRACT_DATE in the WHERE clause.

All lookups against this view are date-effective: the package function GET_EXTRACT_DATE is applied against the person and assignment effective date ranges and against the phone number's date range. The view therefore returns the row that is effective as of the extract date supplied to the package, not necessarily the current system date. This makes it deterministic for point-in-time extracts but requires callers to be aware of the extract date configuration.

Underlying Base Objects

The view is defined over five synonyms and one package, all referenced from the APPS schema:

• PER_ALL_PEOPLE_F – the person record; drives FULL_NAME, PERSON_ID and other person attributes.
• PER_ALL_ASSIGNMENTS_F – the primary assignment (PRIMARY_FLAG = 'Y'); supplies assignment number, supervisor, organization, position, job, location, grade and payroll.
• PER_PHONES – outer-joined source for the work telephone number, restricted to PHONE_TYPE 'W1' and PARENT_TABLE 'PER_ALL_PEOPLE_F'.
• HR_LOCATIONS_ALL – outer-joined location details for the assignment location.
• HR_ALL_ORGANIZATION_UNITS – the business group organization, joined on ORGANIZATION_ID = BUSINESS_GROUP_ID.
• HR_THIRD_PARTY_INTERFACE_PKG – provides GET_EXTRACT_DATE, used for effective-date filtering.

The join between people and assignments is an inner join, while phones and locations are outer-joined, so an assignment will appear even if no work phone or location exists.

Key Columns

• FULL_NAME, EMPLOYEE_NUMBER, KNOWN_AS, SEX, DATE_OF_BIRTH, NATIONAL_IDENTIFIER, TITLE – person identity attributes.
• WORK_PHONE_NUMBER – the work telephone (PHONE_TYPE 'W1') for the person; the column that matches the search term "work_phone_number".
• EMAIL_ADDRESS, MAILSTOP – contact details.
• ASSIGNMENT_NUMBER, PRIMARY_FLAG, ASSIGNMENT_ID, PERSON_ID, SUPERVISOR_ID – assignment identity and reporting relationship.
• ORGANIZATION_ID, POSITION_ID, JOB_ID, LOCATION_ID, GRADE_ID, PAYROLL_ID, PEOPLE_GROUP_ID – assignment attributes.
• ASSIGNMENT_LOCATION, BUSINESS_GROUP_NAME, BUSINESS_GROUP_ID – location and business group context.
• TIME_NORMAL_START, TIME_NORMAL_FINISH – standard working hours.
• DATE_EMPLOYEE_DATA_VERIFIED, EXTRACT_DATE – data verification date and the effective extract date used in the predicate.

Common Use Cases and Queries

Typical uses include third-party payroll feeds, HR data extracts, reconciliation of work phone numbers, and reporting on primary assignments. A basic query selecting the work phone for a person is shown below:

• SELECT person_id, full_name, employee_number, work_phone_number FROM apps.hr_hier_asg_people_v;
• SELECT a.full_name, a.assignment_number, a.work_phone_number FROM apps.hr_hier_asg_people_v a WHERE a.employee_number = :emp_num;
• SELECT a.full_name, a.business_group_name, a.assignment_location, a.work_phone_number FROM apps.hr_hier_asg_people_v a WHERE a.supervisor_id = :sup_id;

Because the view is date-driven by GET_EXTRACT_DATE, results reflect the effective dates configured in the third-party interface package. Confirm the extract date value before relying on the output, and treat the view as read-only reporting metadata rather than a transaction source.