Search Results pv_workflow_pub




Overview
Explore in AI Chat

Overview

PV_WORKFLOW_PUB is a public PL/SQL package in the APPS schema that provides the workflow-facing service layer for Oracle Partner Management (also referred to as Oracle Channel Revenue Management / Partner Management) lead and opportunity assignment. It encapsulates the business logic required to drive the Oracle Workflow processes that govern how leads and opportunities are routed, offered, matched, accepted, and closed out between a vendor organization and its channel partners.

The package is classified as a PUB (public) API, meaning it is intended to be callable from outside its own PL/SQL unit, unlike the companion PV_ASSIGNMENT_PVT private package. It exposes utilities used by workflow activities and notification callbacks, including timeout handling, approval bypass checks, offer and match outcome processing, and a set of "get" functions that resolve descriptive values for display in workflow notifications. Because it is a workflow service layer, it is tightly coupled to PV_LEAD_WORKFLOWS and related assignment tables, and it is referenced by PV_ASSIGNMENT_PUB, PV_ASSIGNMENT_PVT, and PV_BG_PARTNER_MATCHING_PUB.

Key Procedures and Functions

The documented interface contains twenty procedures and functions, summarized below by purpose (parameter lists are intentionally not reproduced here):

  • BYPASS_CM_APPROVAL_CHK and BYPASS_PT_APPROVAL_CHK — Determine whether the channel manager (CM) or partner (PT) approval step should be bypassed for a given assignment, allowing workflow to skip unnecessary notification and approval activities.
  • NEED_PT_OK_CHK — Evaluates whether partner acknowledgement is required before the workflow can advance.
  • SET_TIMEOUT — Establishes the timeout for an offer or approval step, enabling escalation or auto-action when a responder does not act.
  • WAIT_ON_MATCH and WAIT_ON_OFFER — Return the workflow wait status for a pending partner match or a pending offer to a partner, driving the wait/block activities within the workflow definition.
  • PROCESS_MATCH_OUTCOME and PROCESS_OFFER_OUTCOME — Consume the result of a match or offer activity and record the resulting assignment state.
  • SERIAL_NEXT_PARTNER — Sequences the assignment to the next candidate partner in a serial (rather than broadcast) routing strategy.
  • WRAPUP_PROCESSING — Performs finalization for a completed assignment workflow.
  • ABANDON_FYI and WITHDRAW_FYI — Handle FYI (for-your-information) notifications when an assignment is abandoned or withdrawn.
  • GET_ASSIGNMENT_TYPE, GET_ASSIGN_TYPE_MEAN, and GET_OPPTY_CONTACTS — Resolve assignment type codes and their meanings, plus associated contacts, for use in notification content.
  • GET_PRODUCTS, GET_PUBLISH_NOTES — Retrieve the products and published notes tied to an assignment for display in the notification body.
  • GET_VENDOR_ORG_NAME, GET_ACCEPT_USER_NAME, and GET_ACCEPT_USER_ORG — Resolve the vendor organization name and the name and organization of the user who accepted the assignment, supporting the notification message text.

Tables Accessed

The package reads and writes through APPS synonyms. Core assignment objects are PV_LEAD_ASSIGNMENTS, PV_LEAD_WORKFLOWS, PV_OPPTY_ROUTING_LOGS, PV_PARTNER_PROFILES, and PV_PARTY_NOTIFICATIONS, which hold the assignment record, workflow state, routing audit log, partner definition, and notification history respectively. Lead and opportunity data comes from AS_LEADS_ALL and AS_LEAD_LINES_ALL. Party and relationship lookups use HZ_PARTIES and HZ_RELATIONSHIPS. User and resource resolution uses FND_USER, JTF_RS_RESOURCE_EXTNS, PER_ALL_PEOPLE_F, and HR_ALL_ORGANIZATION_UNITS with its _TL translation table. Descriptive attribute labels are sourced from AK_ATTRIBUTES_TL.

Usage Notes

PV_WORKFLOW_PUB is invoked primarily by the Oracle Workflow engine rather than directly by end users. Workflow activities defined for the lead and opportunity assignment processes call its wait, timeout, and outcome-processing procedures, and its GET_* functions supply notification attribute values when message bodies are rendered. It may also be called from the Partner Management forms layer and from custom PL/SQL that extends assignment routing. Because it is an APPS-owned public package, customizations should call it rather than modifying it, and developers should treat its signature as version-sensitive across EBS 12.1.1 and 12.2.2.