Search Results po_document_control_grp




Overview
Explore in AI Chat

Overview

PO_DOCUMENT_CONTROL_GRP is an APPS-owned PL/SQL package in Oracle E-Business Suite Purchasing (PO), classified in the ETRM metadata as an API of type GRP (Group). It encapsulates the document control logic that governs which actions a user or program may legitimately perform against a purchasing document at a given point in its lifecycle. In practice, document control determines whether a Purchase Order, release, or related line structure can be entered, approved, cancelled, closed, frozen, or otherwise modified based on its current status, document type, and control rules. By centralizing this decision logic in a single group package, Oracle ensures consistent enforcement of Purchasing document rules across the many callers that need it. The package status is documented as VALID, and its owner/schema is APPS.

The package is heavily reused: ETRM lists eleven dependent packages that reference it, including PO_CHG_REQUEST_GRP, PO_CHANGEORDERWF_PVT, PO_CHG_REQUEST_PVT, PO_DOCUMENT_CONTROL_PUB, PO_RCO_VALIDATION_PVT, PO_REQCHANGEREQUESTWF_PVT, PO_OM_INTEGRATION_GRP, PO_WIP_INTEGRATION_GRP, and MRP_CANCEL_PO. This dependency footprint confirms its role as a foundational control-layer utility rather than an end-user-facing process.

Key Procedures and Functions

The ETRM metadata documents five procedures/functions in total, of which four are named:

  • CONTROL_DOCUMENT — the principal routine that applies document control validation to a purchasing document, evaluating whether the requested action is permissible against the document's current control state.
  • VAL_CONTROL_ACTION — validates that a specific control action is legal for the document context supplied, returning or raising a validation outcome rather than performing the action itself.
  • CHECK_CONTROL_ACTION — performs the check of a control action, typically used as a Boolean-style test that a caller can branch on before proceeding.
  • VAL_DOC_PARAMS — validates the document parameters passed in, ensuring the caller supplies a coherent document identifier set (for example a header, line, or location combination) before deeper control logic runs.

The fifth documented program unit is not individually named in the excerpt. The naming convention (CONTROL_*, VAL_*, CHECK_*) reflects a validation-first design: the package validates parameters, tests the requested action, and then drives the document control transaction.

Tables Accessed

The package reads and writes Purchasing base tables via APPS synonyms, which is expected for a control-layer package.

Usage Notes

PO_DOCUMENT_CONTROL_GRP is invoked indirectly rather than directly by end users. Oracle Forms (such as the Purchase Orders and Purchase Order Summary forms) and the change-order workflow packages (PO_CHG_REQUEST_GRP, PO_CHANGEORDERWF_PVT) call it to validate actions before writing. Integration packages for OM and WIP, and MRP_CANCEL_PO, call it when external modules request Purchasing document changes, ensuring the same rules apply to interfaced data. Custom code should prefer the public API layer, notably PO_DOCUMENT_CONTROL_PUB, which in turn calls this group. The package applies identically in EBS 12.1.1 and 12.2.2; the ETRM metadata is captured from 12.2.2 and shows no divergence in the documented interface.