Search Results validate_cancel_action

Overview

The APPS.PO_CONTROL_ACTION_VALIDATIONS package is a server-side PL/SQL validation component within the Oracle E-Business Suite Purchasing module (PO). Its principal business function is to enforce the control rules that govern whether a purchasing document — a purchase order, release, or associated line and distribution — may be legitimately subjected to a control action such as cancellation. Rather than performing the physical update or delete against the purchasing document, this package evaluates the eligibility and security context of the requested action so that downstream control routines (for example, those in PO_DOCUMENT_CANCEL_PVT) can proceed or be rejected with a meaningful error.

The package is classified in the ETRM metadata as an OTHER API, meaning it is a supporting validation utility rather than a public, supported business API. It is owned by the APPS schema and is recorded as VALID in the ETRM 12.2.2 object registry. Its dependency footprint confirms its role as a gatekeeper: it draws on purchasing document tables, document type definitions, session context, and financials system parameters, and it exposes its logic to sibling packages responsible for document cancellation.

Key Procedures and Functions

The ETRM metadata documents three callable program units within the package:

• VALIDATE_CANCEL_ACTION — The primary validation entry point. It determines whether a cancel action requested against a purchasing document is permissible, checking document state, associated lines, distributions, and system control settings before the cancel logic is allowed to run.
• IS_COMPLEX_WORK_PO — A predicate function that classifies a purchase order as a "complex work" document. This distinction matters because complex work POs carry different cancellation and control rules than ordinary POs, and the caller must know the document class before applying action logic.
• VAL_DOC_SECURITY — Validates document-level security for the action being attempted, ensuring that the operating user has the authority to act on the specified purchasing document.

Parameter lists are not published in the ETRM extract and are intentionally omitted here; callers should rely on the package specification shipped with the corresponding EBS release.

Tables Accessed

The package reads and references the following documented objects, all via APPS synonyms:

• PO_HEADERS, PO_LINES, PO_LINE_LOCATIONS, PO_RELEASES — Core purchasing document structures consulted to establish document type, line composition, and scheduling detail.
• PO_DISTRIBUTIONS, PO_DISTRIBUTIONS_ALL, PO_DISTRIBUTIONS_ARCHIVE_ALL — Distribution-level data, including archived records, used to assess whether committed or accounted distributions block a control action.
• PO_LINES_ARCHIVE_ALL, PO_LINE_LOCATIONS_ARCHIVE_ALL — Archived line and shipment data, required because cancellation eligibility must account for historical document versions.
• PO_DOCUMENT_TYPES — Determines the document type and the control rules attached to it.
• GL_CODE_COMBINATIONS — Validates accounting flexfield references attached to distributions.
• FINANCIALS_SYSTEM_PARAMETERS — Supplies system-level control options that influence whether cancellation is permitted.
• PO_SESSION_GT, PO_ONLINE_REPORT_TEXT, PO_ONLINE_REPORT_TEXT_S — Session-scoped temporary context and online report messaging used to communicate validation outcomes back to the calling form.

Usage Notes

PO_CONTROL_ACTION_VALIDATIONS is an internal validation package, not an end-user-invocable API. It is exercised indirectly by the Purchasing forms and by other PL/SQL packages when a user initiates a control action such as cancellation of a purchase order or release. The ETRM metadata records that it is referenced by PO_DOCUMENT_CANCEL_PVT, which is the principal consumer; PO_DOCUMENT_CANCEL_PVT calls the validation routines before applying cancellation to a document. In this sense the package behaves as a pre-condition checker embedded in the cancellation flow.

Because the package is marked as an OTHER API and is not listed as a supported public interface, customizations should not call its procedures directly. Extensions needing equivalent validation should instead route requests through the supported document control APIs so that Oracle's internal validation sequence, security checks, and system-parameter handling remain intact across patch applications and upgrades. When troubleshooting "cannot cancel" conditions in Purchasing, this package and its dependency PO_DOCUMENT_CANCEL_PVT are the appropriate starting points for diagnosis.