Search Results per_phones

Overview

The PER_PHONES table is a core data structure within the Oracle E-Business Suite (EBS) Human Resources (HR) module. It serves as the central repository for storing telephone contact information for individuals managed by the HR system. Its primary role is to maintain a comprehensive and historical record of phone numbers associated with various person types, including current and former employees, current and former applicants, and contacts linked to employees. This table is essential for enabling communication workflows, contact management, and integrated reporting across the HR and related EBS applications.

Key Information Stored

The table's structure is designed to capture detailed phone information with context. Its primary key is the PHONE_ID column, which uniquely identifies each phone record. While the full column list is proprietary, typical critical columns in such a table include:

• PERSON_ID: Foreign key linking to the person (employee, applicant, contact) in the PER_ALL_PEOPLE_F table.
• PHONE_NUMBER: The actual telephone number.
• PHONE_TYPE: A code classifying the number (e.g., Work, Home, Mobile, Fax).
• DATE_FROM / DATE_TO: Columns defining the period during which this phone number is or was valid, supporting historical tracking.
• PRIMARY_FLAG: An indicator specifying the primary phone number for a given contact type.
• Standard Who columns (CREATED_BY, CREATION_DATE, LAST_UPDATED_BY, LAST_UPDATE_DATE, LAST_UPDATE_LOGIN) for auditing.

Common Use Cases and Queries

This table is frequently accessed for operational reporting, data validation, and integration. Common scenarios include generating employee contact lists, validating applicant contact information during recruitment, and providing data for downstream systems. Sample SQL patterns often involve joining to person tables and filtering by date and type.

• Retrieve current primary work numbers for employees:
  SELECT ppf.employee_number, ppf.full_name, pph.phone_number
FROM per_all_people_f ppf, per_phones pph
WHERE ppf.person_id = pph.person_id
AND SYSDATE BETWEEN ppf.effective_start_date AND ppf.effective_end_date
AND SYSDATE BETWEEN pph.date_from AND NVL(pph.date_to, SYSDATE)
AND pph.phone_type = 'W1' -- Example code for Work
AND pph.primary_flag = 'Y';
• Audit phone updates: Using the Who columns to track changes made to phone records for compliance.

Related Objects

PER_PHONES is intrinsically linked to other key HRMS tables and is typically accessed via official APIs rather than direct DML. Key related objects include:

• PER_ALL_PEOPLE_F: The master person table, linked via PERSON_ID.
• PER_PHONES_API: The public Oracle API package that should be used for creating, updating, or deleting phone records to maintain data integrity and business rule validation.
• Various HRMS forms and functions, such as the Person GUI, which read from and write to this table through the underlying API layer.