Search Results dpp_request_status_pvt




Overview
Explore in AI Chat

Overview

APPS.DPP_REQUEST_STATUS_PVT is a private (PVT) PL/SQL package within Oracle E-Business Suite that supports the workflow-driven request status notification framework used by Oracle's procurement and sourcing approval flows. The package functions as a specialized subscriber to Oracle Workflow business events. It listens for events relating to requests — such as approval decisions, rejections, or status transitions — and translates them into outbound messages that are dispatched through the Workflow notification infrastructure.

Because the package is classified as private (PVT), it is not an extension API. It is an internal implementation component invoked by the DPP approval engine, and Oracle does not document it as a supported customization entry point. Its presence in the APPS schema with VALID status confirms it is a deployed, active object in both 12.1.1 and 12.2.2 environments. The primary business objective is to ensure that approvers, suppliers, and internal stakeholders receive timely, accurate status communications whenever a procurement request transitions through the DPP approval lifecycle.

Key Procedures and Functions

The ETRM metadata documents two procedures for this package:

  • EVENT_SUBSCRIPTION — This procedure registers the package as a subscriber to Oracle Workflow business events. It associates the package with an event definition and parameter list so that, when the subscribed event is raised, Workflow invokes the package's handler logic. It is the mechanism by which the package becomes active in the event-driven architecture rather than remaining a passive library.
  • SET_REQUEST_MESSAGE — This procedure constructs and sets the content of the request status message. It interprets incoming event data, resolves the relevant request and supplier context, and populates the message payload delivered to recipients. This is the core business logic of the package, converting a raw workflow event into a human-readable, recipient-appropriate notification.

No parameter lists are invented here, as the metadata does not document explicit signatures. Both procedures operate on the Workflow event and parameter-list data structures that are standard to Oracle Workflow subscriptions.

Tables Accessed

The package reads and writes data through APPS synonyms, consistent with standard EBS design practice. The documented tables include:

  • WF_EVENT_T, WF_PARAMETER_LIST_T, WF_PARAMETER_T — Oracle Workflow event and parameter structures used by EVENT_SUBSCRIPTION to register the subscription and by SET_REQUEST_MESSAGE to receive event payload data.
  • DPP_TRANSACTION_HEADERS_ALL — the core DPP transaction header table, providing request identity, status, and ownership context.
  • DPP_APPROVAL_ACCESS — approval routing and access data, used to determine appropriate recipients of status messages.
  • AP_SUPPLIERS, AP_SUPPLIER_SITES_ALL — supplier master and site data, enabling targeted communication to supplier contacts where applicable.
  • FND_FORM_FUNCTIONS — form function metadata, supporting the linkage between the notification and the relevant form or menu entry.
  • JTF_RS_RESOURCE_EXTNS — resource extension data (typically sales/procurement resources), used to resolve personnel recipients.
  • DBMS_LOB, PLITBLM — Oracle-supplied packages invoked for large object handling and PL/SQL table utilities, supporting message body construction and parameter manipulation.

These tables collectively supply the request context, recipient list, and message payload needed to generate accurate status notifications.

Usage Notes

DPP_REQUEST_STATUS_PVT is invoked indirectly through Oracle Workflow's event subscription mechanism. In practice, the DPP approval process raises a business event when a request is approved, rejected, or otherwise updated; Workflow evaluates its subscriptions, matches the event, and calls EVENT_SUBSCRIPTION to activate the handler associated with this package. SET_REQUEST_MESSAGE then builds the outbound message.

Administrators typically do not call this package directly. Instead, they manage it through the Workflow Business Events and Subscription setup, where the subscription details (event, rule function, and package) can be inspected. In both EBS 12.1.1 and 12.2.2, the object resides in APPS and is fully patched with the standard DPP suite. Because no other packages reference it, its exposure is limited to the DPP approval framework, and any modification would be a non-supported customization that could be overwritten by patching. It should be treated as internal infrastructure rather than a public API.