Search Results container_number




Overview
Explore in AI Chat

Overview

The POBV_INBOUND_SHIPMENT_LINES view is a Purchasing (PO) module database object owned by the APPS schema in Oracle E-Business Suite 12.1.1 and 12.2.2. It exposes inbound shipment line information for Advance Shipment Notices (ASNs) and related receiving transactions, presenting a denormalized, read-only projection of shipment line data together with descriptive lookup values and transaction reason names. The view is delivered as a "retrofitted" object, meaning it was originally introduced or maintained under an earlier Oracle Applications release (notably the 11i "POBV" inbound shipment reporting framework) and carried forward into the R12 schema.

Its primary role is to support inbound shipment reporting, integration, and dependent BI/ETRM metadata. The POBV prefix denotes a Purchasing base view used within the inbound shipment workflow. The presence of leading-underscore columns such as _LA:SL.ASN_LINE_FLAG, _LA:SL.DESTINATION_TYPE_CODE, and _LA:SL.SOURCE_DOCUMENT_CODE reflects Oracle's "Lookup Attribute" (LA) convention, where lookup code columns are resolved to their display meanings through PO_LOOKUP_CODES at runtime. The view is defined WITH READ ONLY, so all access is restricted to query (SELECT) operations.

Underlying Base Objects

Per ETRM metadata for 12.2.2, the view is defined over two referenced base objects, both accessed via synonyms owned by APPS:

  • RCV_SHIPMENT_LINES (SYNONYM) — the core shipment line table aliased as SL. This is the primary source for nearly all columns, including quantity shipped/received, unit prices, item attributes, and the foreign key identifiers linking to PO and requisition entities.
  • MTL_TRANSACTION_REASONS (SYNONYM) — aliased as RE, providing the transaction reason description.

The two are joined with an outer join (WHERE SL.REASON_ID = RE.REASON_ID(+)), so every shipment line is returned even when no matching reason is defined. The view's read-only nature is enforced by the trailing WITH READ ONLY clause in the view text.

Key Columns

The view exposes a wide set of columns. Notable ones include:

Common Use Cases and Queries

Because the view is read-only and joins shipment lines to their transaction reason, it is typically used for inbound shipment inquiries, ASN reporting, and reconciliation of shipped-versus-received quantities. Typical access patterns include filtering by shipment header, by PO line, or by receiving destination.

  • Shipment contents for an ASN:
    SELECT shipment_line_id, line_number, item_description, shipped_quantity, received_quantity, unit_of_measure
    FROM apps.pobv_inbound_shipment_lines
    WHERE shipment_header_id = :p_header_id
    ORDER BY line_number;
  • Variance between shipped and received quantities:
    SELECT shipment_line_id, item_description, shipped_quantity - received_quantity short_qty
    FROM apps.pobv_inbound_shipment_lines
    WHERE shipped_quantity <> received_quantity;
  • Lines linked to a purchase order line:
    SELECT shipment_line_id, line_number, po_line_id, po_line_location_id, transaction_reason_name
    FROM apps.pobv_inbound_shipment_lines
    WHERE po_line_id = :p_po_line_id;
  • Resolution of descriptive lookups: The _LA: columns return display meanings for the underlying codes, so downstream reports need not rejoin PO_LOOKUP_CODES to render destination type, source document type, or the ASN line flag.

Consumers should note that the view is a read-only projection; DML against it is not supported, and reporting logic that requires modification of shipment line data must operate against the base tables directly.