Search Results is_username_available

Overview

The APPS.UMX_REG_REQUESTS_PVT_W package is a private PL/SQL wrapper that belongs to the Oracle User Management (UMX) product family in Oracle E-Business Suite. Its central purpose is to service the user self-registration and access-request workflow, which allows external or internal users to request an EBS account, and for administrators to approve or reject those requests. The "_PVT_W" naming convention indicates that this is a private package, intended to be called only from other UMX code rather than from customer extensions directly. It is declared with AUTHID CURRENT_USER, meaning its SQL statements execute under the privileges of the invoking schema rather than the definer, which is typical of packages designed to be called from a framework session that has already established the correct context.

Because registration requests are handled through a workflow, a package such as this typically exposes thin procedural interfaces that translate a workflow activity's arguments into the underlying entity operations. The package itself holds little business logic; it marshals parameters, invokes the corresponding private entity methods, and returns results to the workflow engine.

Key Procedures and Functions

The ETRM metadata documents exactly two procedures:

• IS_USERNAME_AVAILABLE — Determines whether a candidate username supplied during registration can be used. It returns a boolean-style result (reported as a NUMBER), allowing the registration flow to reject duplicates or names that already exist before a request is committed. This is the validation hook used by the registration UI and workflow.
• UPDATE_REG_REQUEST — Persists changes to an existing registration request record. The procedure signature takes a large number of IN OUT NOCOPY parameters (fifteen or more) representing the working set of columns for a request row, such as identifiers and descriptive attributes. The NOCOPY hint avoids copying the parameter values, and the IN OUT mode allows the entity layer to return derived or defaulted values back to the caller. This is the procedure a user would invoke when the search term is "update_reg_request".

No other public procedures are documented for this package in the supplied metadata.

Tables Accessed

The ETRM metadata does not record any base tables accessed directly by this package. In practice the wrapper delegates DML to a private entity package that maintains the registration request table (commonly UMX_REG_REQUEST and its child tables for user details and role assignments). Because the package is a wrapper, direct SQL is minimal and table access is indirect. Where DML does occur, it is performed under the invoking user's privileges per the AUTHID CURRENT_USER declaration.

Usage Notes

• The package is private and is not intended to be called from custom forms, concurrent programs, or ad hoc SQL. External callers should use the supported UMX APIs instead.
• It is invoked from the user registration and access-request workflow, where an activity or function calls IS_USERNAME_AVAILABLE to validate a name and UPDATE_REG_REQUEST to write request changes.
• In EBS 12.1.1 and 12.2.2 the package is Oracle-owned and unsupported for direct modification. Organizations that need custom behavior should extend the workflow rather than the package.
• Because parameters are declared IN OUT NOCOPY, callers must supply addressable variables; literal values are not permitted, and changes made to the entity fields are reflected back to the caller.

The package header carries the RCS identifier UMXRGRWS.pls 115.4, dating the interface to the original UMX release, indicating that its signature has been stable across the 12.1.x and 12.2.x releases.