Search Results create_shipment_header




Overview
Explore in AI Chat

Overview

APPS.RCV_SHIPMENT_HEADER_SV is a server-side PL/SQL package body in the Oracle E-Business Suite Receiving (RCV) module. It provides the core application programming interface for creating and cancelling shipment header records that flow into the receiving transaction tables. The package acts as the validation and insertion gateway between external or upstream data sources — such as Advanced Shipment Notices (ASN), purchase order receipts, and interface-based inbound feeds — and the base receiving tables. In Oracle EBS 12.1.1 and 12.2.2, this package is classified as an "OTHER" API in the ETRM repository, owned by the APPS schema. Its primary design objective is to ensure that shipment header data is derived, defaulted, and validated in a standard sequence before any physical row is written to the receiving tables, thereby protecting data integrity across downstream invoicing and matching processes.

Key Procedures and Functions

  • CREATE_SHIPMENT_HEADER — The principal entry point for constructing a shipment header. It accepts an in-out header record based on the package-level headerrectype structure and applies a fixed processing sequence: deriving the shipment header, applying defaults when the error status is 'S' (success) or 'W' (warning), and then validating the header. If validation still returns 'S' or 'W', the record is inserted through the interface layer — unless the header's test_flag is set to 'Y', in which case insertion is skipped so that test scenarios can be validated without committing data. The procedure also sets processing_status_code conditions relating to invoice processability, particularly where shipment type is not ASBN or where ASBN lines fail validation. A WHEN OTHERS exception handler traps unexpected SQL errors via rcv_error_pkg, logs a fatal debug message when ASN debug is enabled, and returns a controlled error status to the caller.
  • CANCEL_SHIPMENT — A companion procedure responsible for cancelling an existing shipment, reversing or flagging shipment header data so the record is no longer treated as an active receipt for receiving and invoice-matching purposes.

Tables Accessed

The package and its delegated interface routines operate against a documented set of APPS synonyms. RCV_HEADERS_INTERFACE is the staging table through which header rows are derived, defaulted, validated, and inserted via RCV_HEADERS_INTERFACE_SV before final persistence. RCV_SHIPMENT_HEADERS is the base receiving table into which validated header information is ultimately populated. AP_TERMS and AP_TAX_CODES supply payment terms and tax code defaults needed for correct invoice processing of the resulting receipt. FND_CURRENCIES provides currency validation and defaulting, while ORG_FREIGHT supports freight and carrier-related defaulting for the shipment.

Usage Notes

RCV_SHIPMENT_HEADER_SV is referenced by 19 other packages, making it a foundational dependency within the Receiving module. It is typically invoked indirectly from the Receiving Open Interface, ASN inbound processing, and receipt-creation flows, and can also be called from custom PL/SQL when building interface-based shipment loads. Because CREATE_SHIPMENT_HEADER performs derivation, defaulting, validation, and insertion in a single controlled pass, callers must supply a correctly populated headerrectype record and inspect the returned error_record for status and messages. The test_flag mechanism allows validation-only execution, which is useful during implementation and regression testing. Customizations should treat this package as a controlled API rather than modifying its logic directly.