Search Results po_submission_check

Overview

APPS.PO_DOCUMENT_CHECKS_GRP is a public specification package (classified as a GRP — group specification) in the Oracle E-Business Suite Procurement module. It defines a standardized interface for enforcing business rules and validations before a purchasing document is submitted, saved, or otherwise transitioned in its lifecycle. The package acts as a declaration layer that exposes constants and check routines implemented in PO_DOCUMENT_CHECKS_PVT, allowing Oracle Forms, concurrent programs, and dependent PL/SQL packages to validate requisitions, purchase orders, purchase agreements, and releases consistently.

Its header, POXGDCKS.pls version 120.5, dates to the 11.5.11 "Doc Manager Rewrite," and the object remains present in both 12.1.1 and 12.2.2. The public constants define action codes such as DOC_SUBMISSION_CHECK, UNRESERVE, and FINAL_CLOSE_CHECK, along with document type identifiers for requisitions, POs, agreements, and releases, and document levels for header, line, shipment, and distribution. These constants ensure that callers pass uniform values when invoking the validation routines.

Key Procedures and Functions

• PO_SUBMISSION_CHECK — The primary entry point for submission validation. It evaluates whether a document of a given type and level can be submitted based on the requested action, returning errors when conditions are not met. This is the routine most directly associated with the search term "po_submission_check."
• PO_SECURITY_CHECK — Verifies that the current user or application possesses the necessary authority to perform the requested action against the document.
• PO_STATUS_CHECK — Confirms that the document's current status permits the requested transition, preventing illegal state changes.
• CHECK_STD_PO_PRICE_UPDATEABLE — Determines whether a standard purchase order allows price updates in its present condition.
• CHECK_REL_PRICE_UPDATEABLE — Equivalent updateability assessment for release documents.
• CHECK_PAYITEM_PRICE_UPDATEABLE — Validates whether an invoice/payment item price may be changed.
• PO_COMBINED_SUBMISSION_CHECK — Aggregates the individual submission checks into a single invocation, typically used by forms to reduce round trips.

Together these procedures cover the pre-submission, security, status, and price-change validation concerns for the purchasing document lifecycle.

Tables Accessed

The package's routines read from a range of procurement and validation tables via APPS synonyms to perform their checks:

• PO_DOCUMENT_TYPES — Confirms valid document type codes.
• PO_HEADERS, PO_HEADERS_ALL, PO_LINES_ALL, PO_LINE_LOCATIONS_ALL — Retrieve the document header, line, and shipment records being validated.
• PO_RELEASES — Supplies release information for release-level checks.
• PO_REQUISITION_HEADERS — Provides requisition data for submission checks.
• PO_SYSTEM_PARAMETERS, PO_SYSTEM_PARAMETERS_ALL, FINANCIALS_SYSTEM_PARAMS_ALL — Supply configuration flags that govern which checks apply.
• FND_ID_FLEX_STRUCTURES — Supports validation of key flexfield structures.
• PO_ONLINE_REPORT_TEXT, PO_ONLINE_REPORT_TEXT_S — Hold error or warning messages surfaced to the user.
• RCV_TRANSACTIONS_INTERFACE — Referenced where receipt-related constraints affect document actions.

Usage Notes

PO_DOCUMENT_CHECKS_GRP is documented as being referenced by 17 other packages, indicating broad internal reliance across Procurement. It is typically invoked from the Oracle Purchasing forms during document submission and save events, from concurrent programs performing batch validations, and from custom PL/SQL code that needs to replicate standard submission behavior. Because the specification package relies on PO_DOCUMENT_CHECKS_PVT for implementations, customizations should prefer calling the public GRP interface rather than the private body, preserving compatibility across 12.1.1 and 12.2.2.