Search Results auto_close_po




Overview
Explore in AI Chat

Overview

PO_DOCUMENT_ACTION_CLOSE is a PL/SQL package owned by the APPS schema in Oracle E-Business Suite, classified in the ETRM metadata as an "OTHER" API rather than a formal public interface. Its business purpose is to execute close actions against Oracle Purchasing documents — purchase orders, releases, and their associated lines, shipments, and distributions. It provides the procedural backend for transitioning a purchasing document from an open or approved state into a closed state, either through deliberate user-initiated action ("manual close") or through scheduled system-driven processing ("auto close"). In the standard purchasing lifecycle, closing a document signals that no further receiving, invoicing, or change activity is expected against its remaining open quantities, thereby allowing the document to be finalized for accrual, encumbrance, and period-close purposes. Because the package isolates this logic from the Purchasing forms layer, it can be invoked by Oracle's own application code as well as by extension code that must programmatically close purchasing documents.

Key Procedures and Functions

The documented package exposes two procedures:

  • MANUAL_CLOSE_PO — Performs the close operation for a purchase order or release when the action is initiated explicitly by a user or by an application calling on the user's behalf. It drives the state change on the document and its subordinate lines, shipments, and distributions, applying the closure rules that Purchasing enforces for interactive close requests.
  • AUTO_CLOSE_PO — Performs the equivalent close operation when the action originates from automated or batch processing, such as the concurrent programs that close purchasing documents whose open quantities have been fully received or invoiced. It encapsulates the same closure semantics as the manual path but is intended for unattended, system-driven invocation.

No parameter lists are documented in the ETRM metadata, and none should be assumed; integrators should inspect the package specification in the target instance before calling either procedure directly.

Tables Accessed

The package reads and writes the core Purchasing document tables through APPS synonyms:

  • PO_HEADERS / PO_HEADERS_ALL — the purchasing document header, where overall document status and closure indicators are maintained.
  • PO_LINES / PO_LINES_ALL — document lines, whose open quantities and statuses must be evaluated and updated when the parent document is closed.
  • PO_LINE_LOCATIONS / PO_LINE_LOCATIONS_ALL — shipment and schedule-level detail that carries the receipt and invoice tolerances governing closure.
  • PO_DISTRIBUTIONS — accounting distributions that inherit the closure outcome and must remain consistent with the document state.
  • PO_RELEASES / PO_RELEASES_ALL — releases against blanket agreements, which may be closed independently of the agreement header.
  • PO_SYSTEM_PARAMETERS — purchasing system options that control close behavior, notably whether automatic closure is enabled.
  • PLITBLM — the standard EBS PL/SQL table (index-by table of VARCHAR2) used as a generic in-memory collection type by the package's internal logic.

Usage Notes

PO_DOCUMENT_ACTION_CLOSE is referenced by, and itself references, the helper package PO_DOCUMENT_ACTION_PVT; the two are tightly coupled, and the private package carries much of the shared processing logic. It is therefore normally reached indirectly — through the Purchasing forms and through the concurrent programs that perform automatic document closure — rather than being the first point of entry for custom code. Custom integrators who need to close a purchasing document programmatically should prefer the documented Purchasing document APIs (such as the PO document action APIs exposed through PO_DOCUMENT_ACTION_PVT) and treat PO_DOCUMENT_ACTION_CLOSE as an internal implementation detail. When direct invocation is unavoidable, validate the package specification, confirm that the document is eligible for closure under the current PO_SYSTEM_PARAMETERS settings, and ensure that any caller respects the transaction and locking conventions of the Purchasing application to avoid corrupting document or distribution state.