Search Results rcv_shipment_headers_s




Overview
Explore in AI Chat

Overview

The APPS.RCV_SHIPMENT_HEADERS_PKG package body provides the foundational data manipulation layer for shipment header records within the Oracle E-Business Suite Receiving (RCV) module. Shipment headers represent the top-level receiving document created when goods are expected or received against a purchase order, an internal requisition, or an RMA. This package encapsulates the core DML operations — insert, update, delete, and lock — that maintain the integrity of the RCV_SHIPMENT_HEADERS table and its associated intersection table RCV_SHIPMENT_HEADERS_S. In Oracle EBS 12.1.1 and 12.2.2, this object is classified as an OTHER API, meaning it is an internal supporting package rather than a public, fully documented business API. Its status is VALID, and it resides in the APPS schema, consistent with standard EBS database object conventions.

Key Procedures and Functions

The package body exposes four documented procedures that constitute a standard low-level table maintenance interface:

  • INSERT_ROW — Creates a new shipment header record, populating the base table RCV_SHIPMENT_HEADERS and its _S (security/inventory) counterpart with the supplied attribute values.
  • UPDATE_ROW — Modifies an existing shipment header, applying changes to the corresponding rows in the base and intersection tables while preserving referential consistency.
  • DELETE_ROW — Removes a shipment header record, typically invoked only when the header has no dependent shipment lines or receipts.
  • LOCK_ROW — Acquires a row-level lock on a shipment header using SELECT ... FOR UPDATE semantics, ensuring that concurrent sessions do not modify the same header simultaneously. This supports the multi-user concurrency model required by Oracle Forms-based receiving screens.

The package also references FND_MESSAGE and APP_EXCEPTION for error handling and message retrieval, and RCV_PARAMETERS to retrieve receiving system setup values that govern validation behavior.

Tables Accessed

The package operates on three principal objects, all accessed through APPS synonyms:

  • RCV_SHIPMENT_HEADERS — The primary table holding shipment header attributes such as shipment number, vendor, receipt source, and organizational context. This is the main DML target for insert, update, and delete operations.
  • RCV_SHIPMENT_HEADERS_S — The corresponding intersection table, which stores additional or security-related columns linked to the header. DML operations on the header are mirrored here to keep the two tables synchronized. This is also the object most frequently implicated when the user query "rcv_shipment_headers_s" is entered, as it shares the header table's naming prefix.
  • RCV_PARAMETERS — A read-only reference used to fetch receiving configuration settings, ensuring that header operations comply with the organization's receiving parameters.

Usage Notes

This package is an internal, supporting API rather than a public interface intended for direct customer invocation. It is most commonly called by the Oracle Receiving forms (RCV_RECEIVING and related forms) during the creation and maintenance of shipment headers, and by higher-level receiving APIs such as RCV_SHIPMENT_HEADERS_SV or RCV_HEADERS_PUB that wrap these DML operations with additional business logic. ETRM metadata records that the package is not referenced by any database object itself but is referenced by one other package, confirming its role as a dependent utility. Customizations should avoid direct calls to INSERT_ROW, UPDATE_ROW, and DELETE_ROW unless they fully replicate the validation and message handling performed by the calling layers; direct DML risks bypassing the synchronization between RCV_SHIPMENT_HEADERS and RCV_SHIPMENT_HEADERS_S and may corrupt receiving transactions.