Search Results launch_workflow

Overview

UMX_PROXY_NTF_WF is an Oracle E-Business Suite PL/SQL package owned by the APPS schema that supports the proxy notification and proxy privilege infrastructure of the User Management (UMX) module. Its principal business function is to launch the Oracle Workflow process that generates and delivers proxy-related notifications to FND users. The package acts as a thin orchestration layer over the Workflow Engine: rather than containing notification logic itself, it creates and starts a workflow process whose attributes are seeded from the supplied proxy user and the effective date range of the proxy privilege. In effect, UMX_PROXY_NTF_WF bridges the UMX proxy configuration data model and the Oracle Workflow notification subsystem, ensuring that the designated recipient receives the expected proxy notification within the correct validity window. The package is classified under the ETRM API classification OTHER, indicating it is not part of the published, supported public API surface but rather an internal component used by the UMX application.

Key Procedures and Functions

The documented package specification exposes a single procedure, LAUNCH_WORKFLOW. Per the package header, it is declared as a Private procedure. Its documented purpose is to create and start the workflow process that carries the proxy notification. The parameter list is documented in the header comments and is summarized as follows, without reproducing the full signature:

• p_proxy_username — The FND user name of the notification recipient. This parameter is optional (required = N). When supplied, it must be a valid FND User; the default is null, which likely causes the process to derive or omit the recipient.
• p_start_date — The date on which the proxy privilege begins. This parameter is mandatory (required = Y).
• p_end_date — The date on which the proxy privilege ends. This parameter is optional (required = N) and defaults to null, which is consistent with an open-ended proxy grant.

The procedure's documented pre-requisites are calls into the Workflow Engine: WF_ENGINE.CREATEPROCESS, WF_ENGINE.SETITEMATTRTEXT, and WF_ENGINE.STARTPROCESS. This confirms the sequence of operations performed by LAUNCH_WORKFLOW: a process instance is created, its item attributes are populated from the proxy user and date parameters, and the process is then started so that notification delivery can proceed. The procedure raises errors returned by these underlying Workflow Engine calls; no additional error handling or output parameters are documented. LAUNCH_WORKFLOW is the only procedure or function in the documented package specification (1 total), and the package is not referenced by any other packaged objects, reinforcing its role as a leaf-level integration point rather than a reusable utility.

Tables Accessed

ETRM documents two tables referenced through APPS synonyms:

• FND_USER — The Oracle E-Business Suite user repository. It is referenced to validate or resolve the proxy username passed into LAUNCH_WORKFLOW and to associate the notification with a legitimate FND user account. The documented validation requirement that p_proxy_username must be a valid FND User implies a lookup against this table.
• UMX_PROXY_NOTIFICATIONS_S — The UMX proxy notifications sequence, used to generate unique identifiers for proxy notification records or for the workflow item keys that link the notification to its underlying proxy grant.

Additional data may be read indirectly through the Workflow Engine calls (for example, workflow definition and item type metadata), but the two objects above are the only tables surfaced in the ETRM metadata.

Usage Notes

UMX_PROXY_NTF_WF is an internal UMX component. It is typically invoked when a proxy privilege is created, modified, or scheduled within the Oracle E-Business Suite, so that the affected user is notified through the standard Workflow notification framework. Because LAUNCH_WORKFLOW is documented as Private, it should not be called directly from custom code; instead, customizations should rely on the supported UMX or Workflow notification APIs, or on the UMX forms and concurrent programs that invoke this package internally. When troubleshooting proxy notification failures, verify that the supplied start date is populated, that the end date is either null or greater than the start date, that the proxy username corresponds to an active FND user, and that the Workflow Engine calls (CREATEPROCESS, SETITEMATTRTEXT, STARTPROCESS) complete successfully. Because the package is not referenced by other packages, issues isolated to it will generally originate from its inputs or from the Workflow Engine rather than from upstream PL/SQL callers.