Search Results pobv_inbound_shipments




Overview
Explore in AI Chat

Overview

POBV_INBOUND_SHIPMENTS is a read-only view owned by the APPS schema in Oracle E-Business Suite, documented as VALID in both release 12.1.1 and 12.2.2 under the Purchasing (PO) product family. The "POBV" prefix follows the Oracle convention for Purchasing business views, and the metadata explicitly labels the object as "Retrofitted," indicating it was introduced or reclassified after the original module design, most likely to support inbound shipment visibility in the Receiving and Purchasing reporting layer. The view exposes shipment-header level attributes drawn from the Receiving execution model, providing a consolidated presentation of inbound shipment information: shipment identity, receipt references, expected versus actual shipping dates, freight and invoice details, weights, carrier data, supplier and organization context, and currency conversion attributes. Its primary role is to serve as a reporting and integration interface rather than a transactional entry point; because it is defined with READ ONLY, consumers can query the data safely without risk of DML affecting the underlying receiving tables.

Underlying Base Objects

The view is defined exclusively over RCV_SHIPMENT_HEADERS (referenced as a synonym in the documented 12.2.2 metadata). The SELECT statement projects columns from that table, applying column aliases to produce business-friendly names such as SHIPMENT_ID, SHIPMENT_NUMBER, RECEIPT_NUMBER, SUPPLIER_ID, and CARRIER. One column, "_LA:SH.RECEIPT_SOURCE_CODE:PO_LOOKUP_CODES:SHIPMENT SOURCE TYPE:DISPLAYED_FIELD", is a Lookup Attribute descriptor projected as the SHIPMENT_SOURCE column. This is the mechanism by which Oracle Forms and OAF-based pages resolve the receipt source code against PO_LOOKUP_CODES and render the value as "Shipment Source Type" on the inbound shipment user interface. RCV_SHIPMENT_HEADERS itself is the header-level table of the RCV schema (Receiving), which stores ASN and shipment header information for inbound deliveries. POBV_INBOUND_SHIPMENTS therefore provides a controlled, aliased, read-only projection of that table rather than aggregating multiple base objects.

Key Columns

Common Use Cases and Queries

Typical consumers include inbound logistics reports, ASN-based dashboards, and third-party integrations that need a stable, read-only projection of shipment headers without querying the RCV base table directly. A representative query for outstanding inbound shipments is:

  • SELECT SHIPMENT_NUMBER, RECEIPT_NUMBER, EXPECTED_RECEIPT_DATE, SHIPPING_DATE, SHIPMENT_SOURCE, CARRIER, WAYBILL_AIRBILL_NUMBER FROM APPS.POBV_INBOUND_SHIPMENTS WHERE EXPECTED_RECEIPT_DATE >= SYSDATE ORDER BY EXPECTED_RECEIPT_DATE;
  • SELECT SUPPLIER_ID, CURRENCY_CODE, INVOICE_AMOUNT, TAX_AMOUNT, FREIGHT_AMOUNT FROM APPS.POBV_INBOUND_SHIPMENTS WHERE INVOICE_STATUS IS NOT NULL;
  • SELECT SHIPMENT_ID, SHIPMENT_GROSS_WEIGHT, SHIPMENT_NET_WEIGHT FROM APPS.POBV_INBOUND_SHIPMENTS WHERE GROSS_WEIGHT_UNIT_OF_MEASURE = 'LB';

Because the view is read-only and narrowly scoped to RCV_SHIPMENT_HEADERS, any join to receipt lines, purchase order distributions, or item details must be made explicitly against the RCV and PO base tables in the query.