Search Results g_wf_notification_event




Overview
Explore in AI Chat

Overview

UMX_REGISTRATION_PVT is a private PL/SQL package in the Oracle E-Business Suite Applications (APPS) schema that supports the User Management (UMX) registration infrastructure. Its role is to orchestrate the processing of user registration requests, invoking Oracle Workflow processes after a registration flow has been submitted and assembling the attribute data that downstream workflow and approval logic requires. The package is declared with AUTHID CURRENT_USER and exposes a public record and collection type, UMX_REGISTRATION_DATA and UMX_REGISTRATION_DATA_TBL, which are used to pass name/value registration attributes between registration flow components and the workflow engine.

The package defines a substantial set of named constants (for example, G_REG_SERVICE_CODE, G_REG_FUNCTION_NAME, G_REQUESTED_FOR_USER_ID, G_WF_NOTIFICATION_EVENT, G_AME_APPLICATION_ID, and G_WF_BUS_LOGIC_EVENT) that provide the canonical attribute keys used when building registration data and workflow parameter lists. These constants allow registration services, request records, approver configuration, and Workflow/AME integration attributes to be referenced consistently across UMX components.

Key Procedures and Functions

  • UMX_PROCESS_REG_REQUEST — Documented as a private procedure that invokes an Oracle Workflow process after the registration flow completes. It is the central entry point for post-registration workflow activation.
  • FORMAT_ADDRESS_LOV — A procedure/function used to format address values for presentation as a List of Values, supporting registration and user-profile style address entry. This is the routine associated with the search term “format_address_lov”.
  • POPULATE_REG_DATA — Populates the registration data collection, mapping source attributes into the UMX_REGISTRATION_DATA structure used by the workflow process.
  • ASSIGN_ROLE — Assigns an Oracle Workflow/UMX role in the context of a registration request.
  • GET_PHONE_NUMBER — Retrieves a phone number for a person, used to enrich registration data.
  • GET_PERSON_ID — Resolves the party or person identifier associated with a registration request.
  • GET_MANAGER_NAME — Returns the manager name for a person, typically for approver or notification resolution.
  • GET_JOB_TITLE — Returns the job title for a person, used in registration and approval payloads.

Tables Accessed

The package reads and writes a defined set of UMX, HR, and Workflow tables. Registration request state is persisted in UMX_REG_REQUESTS and UMX_REG_REQUESTS_S, while registration service definitions reside in UMX_REG_SERVICES_B. Events are recorded in UMX_EVENTS_S. Person and party data are drawn from PER_ALL_PEOPLE_F and HZ_PARTIES; assignments, phone numbers, and user accounts come from PER_ALL_ASSIGNMENTS_F, PER_PHONES, and FND_USER. Function metadata is read from FND_FORM_FUNCTIONS. Workflow integration uses WF_EVENTS and WF_PARAMETER_LIST_T. Dynamic SQL through DBMS_SQL and lookups against DUAL and PLITBLM are also referenced.

Usage Notes

As a private (PVT) API, UMX_REGISTRATION_PVT is not intended to be called directly by custom code; it is invoked by the UMX registration framework, the User Management responsibility, and related profile-management flows when a registration request must be pushed into Oracle Workflow. It is referenced by five other packages, confirming its role as an internal collaborator rather than a public interface. Customizations should target supported public UMX APIs and the Workflow process definitions, treating this package as an implementation detail that may change between EBS 12.1.1 and 12.2.2.