Search Results get_job_title




Overview
Explore in AI Chat

Overview

UMX_PROXY_USER_PVT is a private PL/SQL package body in the APPS schema that supports Oracle E-Business Suite's proxy user functionality, part of the User Management (UMX) infrastructure. A proxy user is a person who is authorized to act on behalf of another user within the EBS environment, most commonly to approve or manage workflow transactions, notifications, and approval activities when the designated approver is unavailable. This package provides the underlying data retrieval logic that resolves proxy relationships to concrete identity, contact, and employment information for the underlying person records.

The package is classified as a PVT (private) API, meaning it is an internal implementation package rather than a public, supported interface. It is not referenced by any other database object according to the ETRM metadata, and it is invoked internally by related UMX packages — notably UMX_REGISTRATION_PVT, which appears as a dependency. This positions UMX_PROXY_USER_PVT as a supporting utility layer within the broader User Management and proxy authorization architecture.

Key Procedures and Functions

The documented package exposes three program units, all of which are read-oriented data resolution utilities:

  • GET_PERSON_ID — Resolves and returns the unique identifier for a person record. This is the primary key used across Oracle HRMS and User Management tables (PER_ALL_PEOPLE_F, HZ_PARTIES) to identify an individual, and it is typically the value passed into and out of proxy-related operations.
  • GET_PHONE_NUMBER — Retrieves the telephone number associated with a person, drawing from the PER_PHONES table. This supports proxy notification and contact-resolution scenarios, where a proxy or delegating user must be reachable via a documented contact point.
  • GET_EMP_DATA — Returns employment-related data for a person, resolving attributes across the HRMS person, assignment, and job entities. This supports the identification of the person's organizational context, such as their assignment and job, which may be relevant to determining valid proxy relationships.

No parameter lists are documented in the ETRM metadata; each routine should be treated as an internal accessor whose signature is defined only in the package body and is not part of a supported public contract.

Tables Accessed

The package reads from the following tables through APPS synonyms:

  • PER_ALL_PEOPLE_F — The core HRMS person table, providing person identifiers and person-level attributes. This is the starting point for the identity resolution performed by GET_PERSON_ID and GET_EMP_DATA.
  • PER_ALL_ASSIGNMENTS_F — The assignment table, supplying employment and organizational context used by GET_EMP_DATA to determine the person's role and position.
  • PER_PHONES — The contact telephone table, queried by GET_PHONE_NUMBER.
  • HZ_PARTIES — The Trading Community Architecture party registry, which links the person to their party record and supporting contact data.

The metadata identifies the package as read-only with respect to these objects; no insert, update, or delete dependencies are documented.

Usage Notes

UMX_PROXY_USER_PVT is not intended for direct invocation by customer code. Its callers are internal UMX components — chiefly UMX_REGISTRATION_PVT — and it should be treated as a private helper. Customers and integrators configuring proxy users in EBS 12.1.1 or 12.2.2 should work through the supported User Management forms and public UMX APIs rather than calling this package directly. Because it maintains no external references and is a private package, its internal routines may change between releases or patches without notice, so custom code should never depend on its signature or behavior. Its practical role is limited to resolving person, phone, and employment details needed to validate and operate proxy user definitions within the EBS security model.