Search Results rcv_shipment_headers




The RCV_SHIPMENT_HEADERS table in Oracle E-Business Suite (EBS) versions 12.1.1 and 12.2.2 serves as a critical repository for recording and managing receipt-related transactions within the Purchasing and Inventory modules. This table stores high-level information about inbound shipments, acting as the parent entity for detailed receipt lines stored in RCV_SHIPMENT_LINES. Below is a detailed technical and functional analysis of this table's structure, purpose, and integration within Oracle EBS.

Table Overview

RCV_SHIPMENT_HEADERS is part of the Receiving (RCV) application tablespace in Oracle EBS. It captures metadata about shipments received from suppliers, including shipment dates, receipt methods, and associated purchase orders. The table is fundamental to the three-way matching process (PO, receipt, and invoice) in procurement workflows.

Key Columns and Descriptions

  • SHIPMENT_HEADER_ID: Primary key, uniquely identifying each shipment record.
  • RECEIPT_NUM: User-friendly identifier for the shipment, often displayed in Receiving screens.
  • VENDOR_ID: References PO_VENDORS, linking to the supplier.
  • SHIP_TO_ORG_ID: Indicates the inventory organization receiving the shipment (references HR_ORGANIZATION_UNITS).
  • SHIPMENT_TYPE: Classifies shipments (e.g., "STANDARD", "RETURN TO VENDOR").
  • RECEIVE_DATE: Timestamp of receipt creation.
  • EMPLOYEE_ID: Identifies the receiver (references PER_ALL_PEOPLE_F).
  • STATUS: Tracks workflow state (e.g., "PENDING", "RECEIVED", "DELIVERED").
  • WAYBILL_AIRBILL_NUM: Carrier tracking number for logistics.
  • ASN_TYPE: Indicates Advance Shipment Notice (ASN) integration status.

Functional Significance

The table supports core procurement processes:
  1. Receipt Creation: Acts as the header for receipt transactions, whether manual or via ASN.
  2. Three-Way Matching: Provides data for validating PO-receipt-invoice consistency.
  3. Inventory Integration: Shipments transition to inventory via MTL_TRANSACTIONS_INTERFACE upon delivery.
  4. Supplier Performance: Timestamps and statuses enable supplier lead time analysis.

Integration Points

  • Purchasing: Linked to PO_HEADERS_ALL via PO_HEADER_ID.
  • Inventory: SHIP_TO_ORG_ID ties to MTL_PARAMETERS.
  • Payables: Receipts referenced in AP_INVOICE_LINES for matching.
  • Costing: Receipt dates impact material cost calculations in CST_ITEM_COSTS.

Technical Considerations

  • Indexes: Key indexes include RCV_SHIPMENT_HEADERS_U1 (on SHIPMENT_HEADER_ID) and RCV_SHIPMENT_HEADERS_N1 (on RECEIPT_NUM).
  • Partitioning: In high-volume environments, partitioning by RECEIVE_DATE improves query performance.
  • API Interactions: The RCV_TRANSACTIONS_PUB API manipulates this table during receipt processing.

Version-Specific Notes

Differences between 12.1.1 and 12.2.2 are minimal for this table, but 12.2.2 may include:
  • Enhanced ASN columns for EDI integrations.
  • Additional status values for new workflow states.
  • Optimized foreign key constraints for performance.

Customization Impact

Extensions often include:
  • Custom statuses via lookup codes (FND_LOOKUP_VALUES).
  • DFFs (Descriptive Flexfields) for industry-specific attributes.
  • Triggers to enforce business rules during receipt approval.

Conclusion

The RCV_SHIPMENT_HEADERS table is a linchpin in Oracle EBS' procure-to-pay cycle, ensuring accurate receipt recording and downstream processing. Its design reflects Oracle's commitment to auditability (via timestamps and status tracking) and integration across financial and supply chain modules. Proper understanding of this table is essential for troubleshooting receipt issues, designing custom reports, or extending receiving functionality.