Search Results po_core_s




Overview
Explore in AI Chat

Overview

RCV_SHIPMENT_HEADER_SV is an APPS-owned PL/SQL package in the Oracle E-Business Suite Receiving (RCV) module. Its primary business function is to encapsulate server-side validation and processing logic for shipment header records — the top-level container that represents an inbound shipment of goods against a purchase order, an internal requisition, or an advanced shipment notice (ASN). In the ETRM classification this object is typed as a view-style/validation package (API classification OTHER), meaning it is not a public transactional API in the strict sense but rather a shared service layer invoked by other Receiving and Purchasing packages to create and cancel shipment headers consistently.

The package is validated and VALID in release 12.2.2, and it is a heavily depended-upon low-level component: the documentation records it as referenced by nineteen other packages. Among the callers is PO_CORE_S, which is the object the searching user encountered. This dependency reveals that the Receiving shipment header logic is reachable not only from the Receiving forms and ASN flows, but also from the Purchasing core service layer, reinforcing its role as a cross-module shared routine.

Key Procedures and Functions

The documented interface exposes two procedures:

  • CREATE_SHIPMENT_HEADER — Inserts and validates a new shipment header record. It assembles header attributes such as vendor, vendor site, currency, terms, freight, tax code, and organization context, performing the required validation and defaulting before the record is persisted. This is the primary entry point for programmatically establishing an inbound shipment.
  • CANCEL_SHIPMENT — Reverses or cancels an existing shipment header, applying the business rules that govern which shipment states may be cancelled and the downstream effects on associated shipment lines and transactions.

Both routines are documented by name and purpose only; the package does not expose a broader public API surface in the metadata. Callers invoke them to avoid duplicating shipment-header validation logic in their own code.

Tables Accessed

The package reads and writes the following documented tables and views:

  • RCV_SHIPMENT_HEADERS — The base shipment header table; the target of CREATE_SHIPMENT_HEADER and the record manipulated by CANCEL_SHIPMENT.
  • RCV_HEADERS_INTERFACE — The open interface staging table used when shipment headers are loaded through the Receiving Open Interface; the package participates in interface processing and validation.
  • PO_VENDORS and PO_VENDOR_SITES — Supply vendor and vendor-site validation and defaulting for the shipment.
  • AP_TERMS and AP_TAX_CODES — Provide payment terms and tax code validation/defaulting.
  • FND_CURRENCIES — Validates the shipment currency.
  • ORG_FREIGHT and ORG_ORGANIZATION_DEFINITIONS — Supply freight carrier defaults and inventory organization context.
  • PO_LOOKUP_CODES — Resolves Purchasing lookup values used during validation.

Usage Notes

Typical invocations originate from the Receiving transaction and ASN processing packages (RCV_CORE_S, RCV_ASN_TRX_INSERT, RCV_HEADERS_INTERFACE_SV, RCV_SHIPMENT_LINE_SV, and the RCV_ROI_* and RCV_824_SV routines), from the Receiving Open Interface concurrent programs, and from the Purchasing core service layer PO_CORE_S. The dependency list also captures PO_CURRENCY_SV, PO_LOCATIONS_S, PO_TERMS_SV, PO_VENDORS_SV, and PO_VENDOR_SITES_SV, indicating that shipment header validation is bound tightly to Purchasing master-data validation. Custom code should invoke these routines rather than inserting directly into RCV_SHIPMENT_HEADERS, since direct DML bypasses the defaulting, cross-module validation, and interface-consistency checks the package enforces. Because RCV_SHIPMENT_HEADER_SV is also referenced by itself, recursive or internal shared logic is present within its own package body.