Search Results dm_workflow_call

Overview

The APPS.RCV_DEBIT_MEMO_NOTIF package is a PL/SQL specification declared with AUTHID CURRENT_USER, meaning its procedures execute with the privileges of the invoking schema rather than the defining schema. Its stated purpose, per the package header, is to retrieve receipt information and subsequently invoke the Oracle Workflow engine. In the Oracle EBS 12.1.1 and 12.2.2 receiving modules, this package supports the debit memo notification business flow: when a receipt transaction requires a debit memo — typically because goods are rejected, returned to vendor, or received short — the package assembles the data needed to launch an associated workflow process that routes the notification to the appropriate approver or recipient. The package header carries the internal filename RCVWPA1S.pls and an original creation date of 3/30/2000, reflecting its long-standing role in the Receiving (RCV) product family. Version control metadata ($Header: RCVWFDMS.pls 120.1) indicates it has been relatively stable since 2005, with subsequent maintenance limited to compatibility and dependency updates.

Key Procedures and Functions

The ETRM metadata documents two procedures for this package:

• DM_WORKFLOW_CALL — Accepts a transaction identifier and serves as the entry point for the debit memo workflow. Its documented role is to retrieve receipt information and then call the workflow engine.
• START_WF_PROCESS — Sets up the workflow item. The package comment states it generates the item key, sets up the item attributes, and then starts the workflow process. The inclusion of "Start_WF_Process" in the user's search strongly suggests this is the procedure most commonly referenced when examining the package.

No parameter lists beyond those in the shipped source are described here; the documentation confirms START_WF_PROCESS accepts item type, item key, workflow process, receipt number, employee ID, quantity, and PO number inputs.

Tables Accessed

The package references the following base tables through APPS synonyms:

• PO_HEADERS_ALL — source of purchase order header information needed to populate workflow attributes such as the PO number.
• PO_WF_ITEMKEY_S — sequence used to generate unique workflow item keys for the notification process.
• RCV_SHIPMENT_HEADERS — receipt shipment details, linking the transaction to its receipt.
• RCV_TRANSACTIONS — the specific receipt transaction being processed for debit memo evaluation.
• WF_ITEMS — the Oracle Workflow item table, where the created workflow item is registered and tracked.

Usage Notes

This package is invoked programmatically rather than through a form or concurrent program. It is typically called by the Receiving transaction processing logic when a receipt or return event must trigger a debit memo notification, with DM_WORKFLOW_CALL serving as the wrapper that fetches receipt context and delegates to START_WF_PROCESS to create and launch the workflow item. Because the ETRM records zero packages referencing RCV_DEBIT_MEMO_NOTIF, its consumers are almost certainly core RCV forms and concurrent programs or custom extensions, rather than other documented PL/SQL packages. Developers extending debit memo behavior should invoke DM_WORKFLOW_CALL with a valid RCV_TRANSACTIONS transaction ID, ensuring the workflow item type is properly configured in the Workflow Administrator responsibility.