Search Results PER_ALL_PEOPLE_F




Overview
Explore in AI Chat

Overview

The PER_ALL_PEOPLE_F table is a core data object within the Oracle E-Business Suite Human Resources (PER) module, present in both releases 12.1.1 and 12.2.2. As a DateTracked table, it serves as the central repository for personal information pertaining to all individuals managed by the system. This includes not only employees but also applicants, contingent workers, and other person types. The table's DateTrack structure, indicated by the '_F' suffix and the EFFECTIVE_START_DATE and EFFECTIVE_END_DATE columns, enables the maintenance of a complete historical record of changes to a person's information over time, supporting legal and audit requirements.

Key Information Stored

The table's primary key is a composite of PERSON_ID, EFFECTIVE_START_DATE, and EFFECTIVE_END_DATE, which uniquely identifies each historical row for an individual. Critical columns include PERSON_ID (the unique system identifier), BUSINESS_GROUP_ID (linking the person to a specific HR organization), and PERSON_TYPE_ID (classifying the person, e.g., as an Employee or Applicant). Other significant columns store comprehensive personal details such as full name (FIRST_NAME, LAST_NAME), date of birth, National Identifier, gender, marital status, and contact information. The EFFECTIVE_START_DATE and EFFECTIVE_END_DATE define the date range for which the row's data is valid, with an END_DATE of '31-DEC-4712' representing the current active record.

Common Use Cases and Queries

This table is fundamental for any process involving person data. Common use cases include generating employee directories, creating applicant tracking reports, and serving as the source for personal data in integrated modules like Payroll and Benefits. A typical query to retrieve current information for all employees would use effective date logic:

  • SELECT person_id, last_name, first_name, employee_number FROM hr.per_all_people_f WHERE sysdate BETWEEN effective_start_date AND effective_end_date AND person_type_id = [Employee_ID];

Another frequent pattern involves joining to assignment tables (PER_ALL_ASSIGNMENTS_F) to report on persons with specific job or position assignments. When writing custom extracts or reports, it is essential to always include the effective date condition to ensure the correct historical or current snapshot of data is retrieved.

Related Objects

PER_ALL_PEOPLE_F has extensive relationships with other HR and EBS objects. As per the provided metadata, it holds foreign keys to HR_ALL_ORGANIZATION_UNITS (via BUSINESS_GROUP_ID) and PER_PERSON_TYPES (via PERSON_TYPE_ID). Crucially, it is referenced by numerous other tables, including assignment (PER_ALL_ASSIGNMENTS_F), payroll, and benefits tables. The metadata also shows specific foreign key relationships with objects from other modules, such as PJI_RESOURCES_DENORM (Project Resources) and several WMS (Warehouse Management) tables (e.g., WMS_DISPATCHED_TASKS), demonstrating its integration beyond core HR. For programmatic access and data integrity, Oracle provides PL/SQL APIs in packages like HR_PERSON_API for maintaining records in this table.