Search Results po_line_locations_s




Overview
Explore in AI Chat

Overview

PO_SHIPMENTS_SV8 is a server-side PL/SQL package body owned by the APPS schema in Oracle E-Business Suite, classified under the ETRM metadata as an "OTHER" API. Its name follows the Oracle Purchasing "SV" (server validation / server view) naming convention applied to shipment-level processing, and it operates on the same data domain as the PO_LINE_LOCATIONS_S and PO_LINE_LOCATIONS_ALL base tables and views. The package encapsulates validation and derivation logic for purchase order shipment (line location) records, providing centralized processing that enforces business rules before shipment data is written or returned to the calling context. Because it depends on purchasing setup, financials setup, and master item definitions, it serves as a reusable validation layer rather than a standalone user-facing feature. In Oracle EBS 12.1.1 and 12.2.2 the object is reported as VALID and is referenced by two other packages, indicating it functions as a shared dependency in the purchasing module rather than an entry-point API.

Key Procedures and Functions

The ETRM metadata documents five procedures or functions associated with this package. The documented metadata lists only the generic name placeholder for these units, so no parameter lists, return types, or signatures are reproduced here. In aggregate the documented units provide the shipment-processing routines invoked against PO_LINE_LOCATIONS records. Based on the dependency footprint—which includes FND_MESSAGE, PO_MESSAGE_S, and PO_SHARED_PROC_PVT—the procedures perform validation and, where a rule fails, raise or populate messages through the standard Oracle Purchasing message infrastructure. The reliance on PO_SYSTEM_PARAMETERS and FINANCIALS_SYSTEM_PARAMETERS indicates that the units also consult system-level purchasing and financials options to determine valid processing behavior. One or more of the five units acts as the primary entry point for shipment validation, with the remaining units supporting helper logic such as value derivation or cross-entity checks. No procedures or functions beyond the five documented units should be assumed.

Tables Accessed

The package reads from a defined set of purchasing and reference tables through APPS synonyms. PO_LINE_LOCATIONS, PO_LINE_LOCATIONS_ALL, and PO_LINE_LOCATIONS_S supply the shipment/line-location data central to the package's purpose, with the _ALL variant used where organization-level attributes are required and the _S view used for the single-organization perspective. PO_HEADERS, PO_LINES, and PO_LINE_TYPES provide the parent document context and line-type rules needed to validate a shipment against its owning order. MTL_SYSTEM_ITEMS and PO_VENDORS / PO_VENDOR_SITES supply item and supplier qualification data. AP_PRODUCT_SETUP and FINANCIALS_SYSTEM_PARAMETERS supply financials and product-level setup controlling allowable processing, while PO_SYSTEM_PARAMETERS supplies purchasing options such as defaulting and control rules. The remaining dependencies—FND_MESSAGE, PO_MESSAGE_S, PO_SHARED_PROC_PVT, PO_COO_S, and DUAL—are supporting infrastructure for messaging, shared purchasing logic, and constant evaluation rather than business data tables.

Usage Notes

PO_SHIPMENTS_SV8 is an internal server package rather than a documented public API, so it is typically invoked indirectly. Oracle Purchasing forms and concurrent programs that maintain shipment records—notably the line-location and shipment detail blocks of the purchase order entry form—call this logic during validation and processing. The two packages that reference PO_SHIPMENTS_SV8 depend on it as a shared validation service, and custom extensions should follow the same pattern by calling the documented entry points instead of duplicating rules. Because the package touches setup and control tables, any customization must ensure PO_SYSTEM_PARAMETERS, AP_PRODUCT_SETUP, and FINANCIALS_SYSTEM_PARAMETERS are correctly configured for the operating unit. Direct modification of this package body is not supported; it is a standard Oracle-owned object and should be treated as read-only in both 12.1.1 and 12.2.2.