Search Results shipment_net_weight




Overview
Explore in AI Chat

Overview

APPS.POBV_INBOUND_SHIPMENTS is a Business Intelligence System (BIS) view in Oracle E-Business Suite, owned by the APPS schema and registered under FND Design Data as PO.POBV_INBOUND_SHIPMENTS. In both 12.1.1 and 12.2.2 the object carries a status of VALID. Its purpose is to present receiving information for the source of actual or expected receipts, allowing inbound shipment data to be grouped by source type — Internal or Supplier — and by the specific origin of the receipt. This makes it a convenient reporting and integration surface for procurement, receiving, and supply-chain analysis without requiring consumers to navigate the underlying normalized shipment tables directly.

The view is particularly relevant to searches such as net_weight_unit_of_measure, because it exposes NET_WEIGHT_UNIT_OF_MEASURE alongside its companion weight columns, SHIPMENT_NET_WEIGHT and SHIPMENT_GROSS_WEIGHT, and the matching GROSS_WEIGHT_UNIT_OF_MEASURE. These attributes support freight, logistics, and landed-cost reporting where shipment weights and their units of measure must be reconciled with carrier and ASN documentation.

Underlying Base Objects

The documented base object for this view is RCV_SHIPMENT_HEADERS, referenced through a synonym. RCV_SHIPMENT_HEADERS is the receiving foundation table that stores shipment header records, whether inbound from a supplier (ASN or expected receipt) or internal (inter-organization transfer). The BIS view projects selected header attributes into a flatter, more descriptive structure, adding derived or lookup-resolved columns such as _LA:SHIPMENT_SOURCE (a descriptive flexfield-style label attribute) and ASN_TYPE.

Because RCV_SHIPMENT_HEADERS holds one row per shipment header, the view does not typically multiply rows; it preserves the header grain. Related child information, such as shipment lines and containers, resides in separate objects and is not joined here. Consequently, the view is best treated as a shipment-level summary rather than a line-level detail source, and joins to lines or inventory organizations should be made explicitly by the consumer.

Key Columns

Common Use Cases and Queries

Typical scenarios include inbound logistics reporting, supplier performance and on-time receipt metrics, internal transfer visibility, and freight cost analysis. Analysts frequently filter by source to separate supplier ASNs from internal shipments, and use the weight unit columns to normalize measurements across suppliers using different systems of measure.

A representative query isolating shipments by source and weight unit:

SELECT shipment_number, receipt_number, asn_type,
  shipment_net_weight, net_weight_unit_of_measure,
  shipment_gross_weight, gross_weight_unit_of_measure,
  expected_receipt_date, carrier
FROM apps.pobv_inbound_shipments
WHERE net_weight_unit_of_measure = 'LB'
ORDER BY expected_receipt_date DESC;

For integration, the view supports inbound data extracts feeding warehouse or analytics platforms, where the descriptive shipment source and unit-of-measure columns reduce the need for additional lookup joins against base receiving tables.