Search Results hr_phone_api




Overview
Explore in AI Chat

Overview

APPS.HR_PHONE_API is a public PL/SQL API package within the Oracle E-Business Suite Human Resources (HR) module, classified in the ETRM as an API and maintained by the APPS schema. Its business purpose is to provide a controlled, validated interface for the creation, modification, and removal of telephone records associated with a person in Oracle HRMS. Because telephone data is date-tracked and subject to business rules—such as primary phone designation, phone type validation, and contact-relationship constraints—direct DML against the underlying base tables is not supported. Instead, HR_PHONE_API applies the standard HRMS API pattern, delegating validation and row-level processing to the HR_API utility layer and to the corresponding business-rule packages, so that all inserts, updates, and deletes conform to the same semantics used by the delivered application forms. As a package body it contains the concrete implementation (the specification declares the callable entry points), and it is recorded as VALID in the ETRM extract.

Key Procedures and Functions

The documented interface exposes four procedures. Parameter lists are not reproduced here; only the documented purpose of each entry point is described.

  • CREATE_PHONE — Inserts a new phone record for a person, applying HRMS validation rules before the row is committed to the PER_PHONES table.
  • UPDATE_PHONE — Modifies attributes of an existing phone record, subject to the same validation and date-track handling applied on creation.
  • DELETE_PHONE — Removes an existing phone record through the supported delete path, preserving referential integrity and audit behavior.
  • CREATE_OR_UPDATE_PHONE — A convenience entry point that determines whether a matching phone record already exists and routes the operation to the appropriate create or update logic, avoiding duplicate rows.

Tables Accessed

Per the ETRM dependency data, the package operates against two tables exposed through APPS synonyms. PER_PHONES is the primary transactional table; it stores the individual phone records, including the phone number, phone type, and the associated person reference. The package reads and writes this table through the insert, update, and shadow table dependencies PER_PHN_INS, PER_PHN_UPD, and PER_PHN_SHD, which indicate that date-tracked (datetrack) processing is in effect, with PER_PHN_DEL handling removal. PER_ALL_PEOPLE_F supplies the person-level context—the effective-dated person record against which the phone is validated and to which it is linked—so the API can confirm that the person exists and is valid for the effective date of the operation. Together these dependencies show that the package performs fully validated, date-effective maintenance rather than raw table manipulation.

Usage Notes

HR_PHONE_API is the supported programmatic route for phone maintenance and is typically invoked from Oracle Forms personalizations and customizations, from concurrent programs that load or migrate telephone data, and from custom PL/SQL integration code in both Oracle EBS 12.1.1 and 12.2.2. The same API underpins delivered HRMS functionality, so callers inherit the standard validation, datetrack, and audit behavior without reimplementing business rules. Because the ETRM records 13 other database objects referencing this package, any change to its behavior carries downstream impact and should be regression-tested broadly. Note that dependency metadata lists HR_PHONE_API as not referenced by any database object, indicating it stands at the top of the public API hierarchy rather than being an internal helper. Standard practice is to call these procedures inside a defined transaction and to commit explicitly after the API returns successfully, since the package itself does not control transaction boundaries.