Search Results edi_unit_price




Overview
Explore in AI Chat

Overview

APPS.POBV_INBOUND_SHIPMENT_LINES is a Business Intelligence System (BIS) view in the Oracle E-Business Suite APPS schema, owned by the Procurement (PO) product family and registered in FND Design Data as PO.POBV_INBOUND_SHIPMENT_LINES. The view presents inbound receiving information for items that have been shipped and/or received against a specific receipt source, consolidating shipment-line detail into a denormalized, reporting-friendly structure. Because it is a BIS view, it is intended primarily for reporting, analytics, and integration consumption rather than transactional update. Status is documented as VALID in ETRM 12.2.2. The view exposes 44 columns spanning identifiers, quantities, pricing, supplier references, destination attributes, and standard WHO audit columns. For users searching on shipment_unit_price, the relevant attribute is the SHIPMENT_UNIT_PRICE column, which carries the unit price associated with the inbound shipment line (distinct from EDI_UNIT_PRICE, which reflects the price transmitted electronically).

Underlying Base Objects

The documented view metadata identifies two referenced base objects: RCV_SHIPMENT_LINES (SYNONYM) and MTL_TRANSACTION_REASONS (SYNONYM). RCV_SHIPMENT_LINES is the core receiving table holding shipment line records, and it supplies the bulk of the columns exposed here, including SHIPMENT_LINE_ID, SHIPMENT_UNIT_PRICE, quantities, and supplier descriptors. MTL_TRANSACTION_REASONS provides the reason-name lookup resolved into TRANSACTION_REASON_NAME. In practice, the view also indirectly references related procurement and inventory entities (purchase order, requisition, distribution, and location tables) through the foreign-key identifiers exposed as columns such as PURCHASE_ORDER_ID, PO_LINE_ID, REQUISITION_LINE_ID, and DELIVER_TO_LOCATION_ID. These identifiers allow the reporting layer to join back to the operational tables without duplicating their full attribute sets.

Key Columns

Common Use Cases and Queries

The view is commonly used in inbound receiving reports, supplier performance analysis, ASN reconciliation, and landed-cost verification. A typical analytical query aggregates shipped versus received quantities and unit price by item and supplier lot.

  • Comparing shipment unit price against EDI unit price to detect pricing discrepancies on electronically received lines.
  • Reconciling supplier-shipped quantity against received quantity to measure fulfillment accuracy.
  • Reporting open inbound shipments by destination organization or subinventory for warehouse planning.
  • Joining to purchase order and requisition identifiers for spend and procurement traceability.

Sample SQL:

SELECT shipment_line_id, item_description, supplier_item_number, shipped_quantity, received_quantity, shipment_unit_price, edi_unit_price, shipment_unit_of_measure, shipment_line_status FROM apps.pobv_inbound_shipment_lines WHERE received_quantity > 0 ORDER BY shipment_line_id;

Because the view is a BIS reporting object, queries against it are read-only. Consumers should apply appropriate organization and date filters to limit result sets on high-volume receiving data.