Search Results po_val_shipments




Overview
Explore in AI Chat

Overview

PO_VAL_SHIPMENTS is a validation package in the Oracle E-Business Suite (EBS) Purchasing module, owned by the APPS schema. It provides the server-side business rule engine that verifies shipment-level attributes on purchase order lines and line locations before a document can be saved or approved. In Oracle releases 12.1.1 and 12.2.2, the Purchasing forms and the underlying validation framework route shipment data through this package to ensure that receipt tolerances, invoice matching rules, dates, quantities, and organizational assignments conform to configured system parameters.

The package is registered in ETRM with an API classification of OTHER and exposes twenty-five documented procedures and functions. Its design follows the standard EBS validation pattern: callers pass a table of line-location identifiers together with the corresponding attribute values, and the procedures return results through PO_VALIDATION_RESULTS_TYPE collections and a result type indicator. This bulk, set-based approach allows the form to validate many shipments in a single round trip.

Key Procedures and Functions

The documented procedures cover several distinct validation domains.

Tables Accessed

The package reads and writes the following objects through APPS synonyms:

Usage Notes

PO_VAL_SHIPMENTS is typically invoked from the Purchasing forms during shipment entry and from the PO validation framework when a document is saved, submitted for approval, or processed by concurrent programs. It is referenced by one other package, indicating it participates in a layered validation call chain rather than being called directly by end users. Customizations and extensions that manipulate shipment tolerances, dates, or quantities should invoke these procedures in the same manner as the standard form to preserve consistency with seeded validation behavior. Because the package operates on collections, callers must populate the corresponding PO_TBL_NUMBER and PO_TBL_DATE structures before invocation. The presence of the "Complex Work R12" annotations on MATCH_4WAY_CHECK parameters indicates that the package was updated to support R12 procurement functionality, making it relevant to both 12.1.1 and 12.2.2 environments.