Results for “qpr_wkfl_util”

AI-generated from documented ETRM metadata — verify critical details on the linked pages.

Overview

QPR_WKFL_UTIL is a utility package in the Oracle E-Business Suite Advanced Pricing / Oracle Price Protection (QPR) schema that centralizes the PL/SQL logic bridging the Pricing deal-approval data model with the Oracle Workflow (WF) engine. In 12.1.1 and 12.2.2, price protection and deal approval requests are driven through a Workflow item type whose activities must call back into the application to perform business validation and status transitions. QPR_WKFL_UTIL provides those callback entry points, together with helper routines that present deal details to the end user and attach the same details as a document to a notification. It is classified as a UTIL (utility) API rather than a public business API, meaning it is intended for internal invocation by Workflow activity function definitions, OAF/Forms pages, and other QPR packages rather than direct customer calls. The package is declared AUTHID CURRENT_USER, so all unqualified references resolve through the APPS schema synonyms under the privileges of the calling session.

Key Procedures and Functions

The package exposes eleven documented routines, most of which follow the standard Oracle Workflow function signature (item_type, itemkey, actid, funcmode, resultout).

• APPROVE_DEAL — Workflow callback that records approval of a deal and returns the appropriate result code to the workflow engine.
• REJECT_DEAL — Counterpart callback that records rejection of a deal and returns the workflow result.
• SET_CALLBACK_NFN_DETAILS — Populates the detail attributes of a callback notification so the approver sees meaningful deal context before acting.
• SET_APP_STATUS_NFN_DETAILS — Populates attributes for the application-status notification that reports the outcome of an approval cycle.
• SHOW_DEAL_DETAILS — Produces the deal detail document (as text) for on-screen display, based on document identifier and display type.
• ATTACH_DEAL_DETAILS — Generates the same deal details as a CLOB document suitable for attachment to a Workflow notification.
• INVOKE_CB_NFN_PROCESS — Invokes the callback notification process for a given response, passing the user list and comments and returning a status code and error buffer.
• INVOKE_TOAPP_NFN_PROCESS — Invokes the “forward to approver” notification process for a response, forwarding the deal to a designated user.
• INVOKE_APPSTAT_NFN_PROCESS — Invokes the application-status notification process, carrying user list, comments, and the resulting status.
• COMPLETE_TOAPP_NFN_PROCESS — Completes the forward-to-approver process, supplying the current user and status.
• CANCEL_TOAPP_NFN_PROCESS — Cancels the forward-to-approver process for a response.

Tables Accessed

The package reads and writes against APPS synonyms covering both the QPR pricing model and the Workflow runtime. Pricing tables include QPR_PN_REQUEST_HDRS_B, QPR_PN_LINES, QPR_PN_PRICES, QPR_PN_PR_DETAILS, and QPR_PN_RESPONSE_HDRS, which together hold deal headers, pricing lines, price details, and approval responses. FND_USER supplies user identity information for notification recipients and approvers. Workflow tables WF_ITEMS, WF_ITEM_ACTIVITY_STATUSES, and WF_PROCESS_ACTIVITIES are consulted to resolve the current item, its activity status, and process activity definitions during callback processing. PLITBLM is used as the standard PL/SQL table-of-varchar2 buffer for message and detail text.

Usage Notes

QPR_WKFL_UTIL is invoked primarily as the PL/SQL entry point configured on Workflow activity function attributes; when a QPR approval workflow reaches an approve or reject node, the engine calls APPROVE_DEAL or REJECT_DEAL with the standard callback signature. Notification display functions call SHOW_DEAL_DETAILS or ATTACH_DEAL_DETAILS to render deal content to the approver. The INVOKE_*, COMPLETE_*, and CANCEL_* procedures are called from QPR pages and background logic to start, advance, or terminate notification sub-processes, returning retcode and errbuf in the standard concurrent-program convention. Because it is a UTIL-class package, it should not be treated as a supported extension boundary; customizations should call documented QPR business APIs instead, and any direct dependency on QPR_WKFL_UTIL risks breakage across patch levels due to its internal Workflow coupling.