Search Results update_req_change_flag




Overview

PO_REQCHANGEREQUESTWF_PVT is a private PL/SQL package in the APPS schema that supports the Oracle Purchasing requisition change request workflow. Its central role is to manage the approval, acceptance, rejection, and cancellation lifecycle for changes submitted against existing requisitions. When a buyer or requester modifies a requisition, the resulting change request must pass through a workflow-driven process; this package encapsulates that logic so the workflow activities can call a stable, well-defined API rather than operating directly on base tables.

The package is classified as a PVT (private) API, meaning it is not part of Oracle's documented public interface. It is invoked internally by other Purchasing packages and by Oracle Workflow. The ETRM metadata lists 71 documented procedures and functions, indicating a broad responsibility set spanning requisition change submission, buyer response handling, approval determination, and cancellation processing. Its position in the dependency graph — referenced by PO_DOCUMENT_CANCEL_PVT and PO_RCO_VALIDATION_PVT, and referencing FND_API — confirms that it participates in both the document cancellation framework and the requisition change order validation path.

Key Procedures and Functions

The documented entry points fall into several functional clusters:

Collectively these procedures drive the state transitions of the change request through the workflow, persisting the outcomes to history and flagging the requisition accordingly.

Tables Accessed

The package reads and writes a wide set of core Purchasing, Order Management, and inventory tables, accessed through APPS synonyms:

Usage Notes

PO_REQCHANGEREQUESTWF_PVT is not intended for direct invocation by end users or custom applications. It is called internally by Oracle Workflow processes and by other Purchasing packages, notably PO_DOCUMENT_CANCEL_PVT and PO_RCO_VALIDATION_PVT. Custom code should use the corresponding public APIs rather than calling this package directly, as its signature and behavior are private and subject to change across releases. When troubleshooting requisition change request workflow issues in EBS 12.1.1 or 12.2.2, DBAs and developers can trace execution through this package to determine how approval, acceptance, or cancellation decisions were recorded.