Search Results po_changeorderwf_pvt




Overview
Explore in AI Chat

Overview

The APPS.PO_CHANGEORDERWF_PVT package is a private PL/SQL package within the Oracle E-Business Suite Purchasing module (Oracle Purchasing / iProcurement workflow infrastructure). Its role is to orchestrate the Oracle Workflow activities that govern change order approvals on purchase orders, purchase requisitions, and supplier change requests. Although the object is classified as PVT (private) and therefore not part of the published public API surface, it is a critical internal component that drives the notification, approval, rejection, and status-transition logic for the Purchasing change order workflow. It is documented as VALID in both Oracle EBS 12.1.1 and 12.2.2, with the same owner (APPS) and the same dependency footprint.

Key Procedures and Functions

The package exposes 38 documented procedures and functions. The most significant documented routines include:

  • ISPOHEADERREJECTED — a boolean-style check that determines whether a purchase order header has been rejected, used to gate subsequent workflow branches.
  • KICKOFFPOAPPROVAL — initiates the PO approval workflow process for a change order.
  • STARTSUPPLIERCHANGEWF — launches the supplier change workflow, generally triggered when a supplier-related attribute on the PO is modified.
  • PROCESSRESPONSE / PROCESS_RESPONSE — process approval or rejection responses returned by approvers, routing the change request to the appropriate next state.
  • PROCESSHDRCANCELRESPONSE — handles the header-level cancellation response, typically used when a change order is withdrawn or cancelled.
  • BUYER_ACCEPT_CHANGE and BUYER_REJECT_CHANGE — record the buyer's decision to accept or reject a supplier- or requisition-originated change.
  • CHG_STATUS_TO_APPROVED — transitions the change request status to Approved once the approval chain completes.
  • IS_PRORATE_NEEDED — determines whether price or quantity proration is required on a change order.
  • GEN_NTF_FOR_* family (SUP_BUY_RP, BUYER_SUP_CHG, BUYER_SUBJECT, SUP_SUBJECT, PLAN_SUBJECT, REQ_SUBJECT, PLAN_SUP_CHN, REQ_SUP_CHN) — notification generators that build and dispatch workflow notifications to buyers, suppliers, planners, and requisitioners for the various change scenarios.
  • NOTIFYSUPALLCHGRPDWF and NOTIFY_REQ_PLAN — specialized notification dispatchers for all-changes-reputed and requisition/planner notification scenarios.

Tables Accessed

The package reads and writes through APPS synonyms, including: PO_CHANGE_REQUESTS (the primary change request record), PO_ACTION_HISTORY (audit trail of workflow and approval actions), PO_DISTRIBUTIONS_ALL and PO_ACCEPTANCES/PO_ACCEPTANCES_S (distribution and acceptance data affected by changes). Supporting lookups include MTL_SYSTEM_ITEMS and MTL_SYSTEM_ITEMS_KFV (item validation), MTL_PLANNERS (planner notifications), HR_ALL_ORGANIZATION_UNITS_TL, HR_LOCATIONS_ALL, and HZ_LOCATIONS (organization and location context for notifications). FND_USER, FND_RESPONSIBILITY, FND_NEW_MESSAGES, and FINANCIALS_SYSTEM_PARAMS_ALL supply user, responsibility, notification, and system-parameter information. The package also depends on the POS_ERR_TYPE error type and the SYS.STANDARD package.

Usage Notes

This package is invoked primarily from Oracle Workflow activity function definitions that belong to the Purchasing change order and supplier change request workflows. It is referenced by PO_REQAPPROVAL_INIT1, PO_REQCHANGEREQUESTWF_PVT, PO_SUP_CHG_REQUEST_WF_GRP, and by itself recursively (typical of internal helper calls). It is not intended for direct invocation by custom code; developers needing change-order automation should use the public Purchasing APIs. Customizations that replace workflow activity functions referencing this package must preserve the documented signature and the POS_ERR_TYPE error contract to avoid breaking the approval chain.