Search Results pv_lead_workflows_s




Overview
Explore in AI Chat

Overview

PV_USER_REGISTRATION_PKG is an Oracle E-Business Suite PL/SQL package owned by the APPS schema, documented at application version 12.2.2 and applicable to 12.1.1 and 12.2.2 installations. The package body is registered as VALID and is classified under the generic API classification "OTHER" rather than as an Open Interface or Public API. Functionally it belongs to the Process Manufacturing / Product Development (PV) product family, where the PV schema and its APPS synonyms support recipe, specification, and lead-management workflows. The package's principal responsibility is the user-registration and notification layer of that lead-management flow: it identifies participants associated with a lead workflow and dispatches e-mail notifications to them, delegating the actual workflow state transitions to the Oracle Workflow engine rather than performing them directly.

The package is an internal implementation unit rather than an externally published API. ETRM records show that no other database object references APPS.PV_USER_REGISTRATION_PKG, which confirms that invocation originates from within the PV application layer itself, not from third-party or customer extensions.

Key Procedures and Functions

The documented package metadata lists a single callable program unit:

  • NOTIFY_USER_BY_EMAIL — Sends an e-mail notification to a user in the context of the PV lead workflow. The procedure encapsulates message construction and recipient resolution, reading lead-workflow data to determine the appropriate recipient(s), then submitting the notification. Because it depends on FND_MSG_PUB, it also participates in the standard EBS message-stack mechanism, allowing callers to retrieve posted messages through the usual FND_MSG_PUB APIs after the call returns.

No parameter lists are documented in ETRM; signatures should be confirmed by inspecting the deployed source in the target environment before direct invocation.

Tables Accessed

The only documented table reference is PV_LEAD_WORKFLOWS_S, reached through an APPS synonym. This is the base (non-_TL) table of the PV lead-workflows entity under the Multi-Org / MLS naming convention. The package uses it to determine which lead workflow instance and which participants the notification concerns — for example, resolving the owning user or role to be e-mailed. Reads dominate; the metadata does not document inserts, updates, or deletes against this table, nor any additional tables, PL/SQL tables, or DML targets.

Usage Notes

Four dependencies define the operational envelope. APPS.FND_API supplies the standard API return-status and error-handling conventions; FND_MSG_PUB provides message token and stack handling for those errors; WF_ENGINE is the Oracle Workflow engine, indicating that notifications are tied to workflow activity execution and are likely dispatched from a workflow function activity or a service component invoked by one; and PV_LEAD_WORKFLOWS_S supplies the recipient data. STANDARD and SYS.DUAL are normal PL/SQL dependencies.

Typical invocation paths are the PV lead-management forms and the Oracle Workflow background engine. Because the package is not referenced by any other database object and is not classified as a public API, it is intended for internal PV use. Customers extending lead notification behavior should invoke it only after confirming the current signature and error-handling expectations, and should prefer wrapping it in a custom API that observes the FND_API conventions. In 12.2.2 the package resides in the APPS schema with the same definition used in 12.1.1; the distinguishing factor between releases is the edition and patch level of the PV and FND dependencies, which should be verified during upgrades.