Search Results get_phone_number

Overview

UMX_PROXY_USER_PVT is a private PL/SQL package in the APPS schema that supports proxy user functionality within Oracle E-Business Suite. The package is part of the User Management (UMX) product family, which governs user accounts, responsibilities, and delegated access across the EBS application tier. Its primary business purpose is to resolve identity and contact attributes for a proxy user, bridging the gap between the party model maintained in Oracle Trading Community Architecture (HZ_PARTIES) and the HR person model maintained in Oracle Human Resources (PER_ALL_PEOPLE_F). Specifically, the package converts a party identifier into a person identifier and then derives telephony and employment attributes for that person so that proxy-related workflows and notifications can address the correct individual.

The package carries the API classification "PVT," signifying that it is a private, internal API not intended for direct invocation by external or customer-developed code. It is designed to be called only by other UMX packages and by UMX-driven user interfaces that require proxy user data. The header comment indicates a creation lineage dating to 2005 and an internal development designation, reflecting the package's long-standing role in the EBS user management stack.

Key Procedures and Functions

The package exposes three documented program units, all of which are resolution utilities rather than transactional APIs:

• GET_PERSON_ID — A private function that retrieves a person identifier from a supplied party identifier. It validates that the party identifier corresponds to a valid party record before returning the person identifier.
• GET_PHONE_NUMBER — A private function that retrieves the phone number associated with a given person identifier. The person identifier must be a valid entry in PER_ALL_PEOPLE_F; the function returns the phone number as a VARCHAR2 value.
• GET_EMP_DATA — A private procedure that returns multiple employee attributes for a person identifier in a single call. It supplies both the phone number and the job title through output parameters, thereby reducing the number of round trips required to assemble proxy user contact and employment data.

No parameters beyond those documented should be assumed; the package metadata confirms only the input and output elements identified above.

Tables Accessed

The package reads from four core EBS tables through APPS synonyms:

• HZ_PARTIES — The TCA party master, used by GET_PERSON_ID to validate the party identifier and derive the associated person identifier.
• PER_ALL_PEOPLE_F — The HR person datastore, used to validate the person identifier supplied to the phone number and employee data routines.
• PER_PHONES — The phone number repository, used to source the telephone attribute returned by GET_PHONE_NUMBER and GET_EMP_DATA.
• PER_ALL_ASSIGNMENTS_F — The assignment datastore, used to resolve the current employment context from which job title information is derived.

All access is read-only in nature; the package resolves and returns identity and contact data rather than maintaining it.

Usage Notes

Because UMX_PROXY_USER_PVT is a private API, it is not a supported integration point for customer extensions. The ETRM metadata records that the package is referenced by zero other packages, indicating that its callers reside in application forms, concurrent program logic, or other UMX components that are not tracked as package-level dependencies. Typical invocation scenarios include proxy user definition forms, approval and notification workflows that must determine whom to contact on behalf of a proxy, and internal UMX processing that needs to translate between the party and person identity models. Custom code should avoid direct calls to this package; where proxy user contact data is required, developers should use the public UMX APIs or supported views instead.