Results for “hr_process_phone_numbers_ss”

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

Overview

APPS.HR_PROCESS_PHONE_NUMBERS_SS is a public PL/SQL wrapper package in the Oracle E-Business Suite Human Resources (HR) module that mediates between user-facing phone number maintenance operations and the underlying phone API, HR_PHONE_API. The package is defined with AUTHID CURRENT_USER and includes the standard EBS version header (hrphnwrs.pkh 120.0, dated 2005/05/31), confirming its provenance as a shipped Oracle application object. Its stated purpose is to accept the full set of parameters defined in the base API and then delegate the actual insert, update, or delete work to the corresponding HR_PHONE_API call. In addition to simple pass-through behaviour, the package captures transaction context — notably the login person who initiated the change — and creates the transaction steps and values required for the HR API transaction framework. This makes it the recommended entry point for programmatic phone number manipulation when full transactional auditing and hierarchy consistency are required. The package is classified as OTHER in the ETRM repository and is not referenced by any other documented package, indicating it is a terminal consumer of the HR phone API rather than a shared library.

Key Procedures and Functions

• CREATE_PHONE — Creates a new phone record by invoking HR_PHONE_API.CREATE_PHONE. Accepts date range, phone type, phone number, parent identifier and parent table, plus the login person identifier, business group, and the descriptive flexfield attribute columns. Documented as raising an exception on failure.
• UPDATE_PHONE — Applies changes to an existing phone record through the underlying API, preserving the same transaction-context and attribute parameter model used by CREATE_PHONE.
• DELETE_PHONE — Removes a phone record via the API, again within the transaction framework.
• CREATE_OR_UPDATE_PHONE — Convenience entry point that determines whether the supplied phone data represents a new or existing record and dispatches to the appropriate create or update path.
• GET_PHONE_DATA_FROM_TT — Extracts phone data from a transaction table (or table type) for downstream processing; used to read back the values staged during an API transaction.
• PROCESS_API — Central orchestration routine that drives the API invocation and manages the surrounding transaction step/value bookkeeping.
• GET_TRANSACTION_DETAILS — Retrieves the details of a previously recorded API transaction, supporting review and audit of phone number changes.

The package also declares the constant GV_WF_REVIEW_REGION_ITEM, mapped to the WF_ITEM_ATTRIBUTES column, which is used to locate the HR review region item within the workflow attribute model, and the date format constant G_DATE_FORMAT set to 'RRRR-MM-DD'.

Tables Accessed

• PER_PHONES — The primary HR table holding phone number records; read and written through the API calls.
• PER_ALL_PEOPLE_F — Supplies and validates the person or contact context against which phone numbers are maintained.
• HR_API_TRANSACTION_STEPS — Stores the ordered transaction steps created so the phone operation can be audited and, where enabled, reversed.
• HR_API_TRANSACTION_VALUES — Holds the parameter values captured for each transaction step.
• WF_ITEM_ATTRIBUTES — Provides the workflow item attribute used to resolve the HR review region item referenced by GV_WF_REVIEW_REGION_ITEM.

Usage Notes

The package is typically invoked from Oracle Forms personalisations or custom PL/SQL when phone numbers must be added, changed, or removed for an employee or contact while maintaining HR API transaction integrity. Because it accepts P_LOGIN_PERSON_ID, it is suitable for self-service style flows in which one person maintains phone details for a related contact, ensuring the transaction steps are attributed to the correct actor rather than the contact. ETRM records no other package referencing HR_PROCESS_PHONE_NUMBERS_SS, so it should be treated as a direct-call interface. Custom code should invoke CREATE_PHONE, UPDATE_PHONE, DELETE_PHONE, or CREATE_OR_UPDATE_PHONE rather than writing to PER_PHONES directly, and should use GET_TRANSACTION_DETAILS to surface or reconcile the resulting transaction. The package is unchanged between release 12.1.1 and 12.2.2 at the documented version level.