Search Results pobv_scheduled_shipments




Overview
Explore in AI Chat

Overview

APPS.POBV_SCHEDULED_SHIPMENTS is a Purchasing (PO) module view that exposes scheduled shipment records for purchase orders and releases. Scheduled shipments are the lowest-level commitment in the purchasing document hierarchy: they extend a purchase order line to a specific ship-to location, need-by or promised date, and quantity. The _BV suffix indicates a business view, retrofitted for Oracle EBS 12.1.1 and 12.2.2 to support the Oracle Forms-based, multi-org architecture of E-Business Suite. The view carries a status of VALID in the APPS schema.

The view is used to present the shipment-level attributes required for order follow-up, receiving, invoicing, and matching rules. A significant portion of its projected columns are rendered as descriptive-flexfield-style display strings (for example _LA:PS.CLOSED_CODE:PO_LOOKUP_CODES:DOCUMENTSTATE:DISPLAYED_FIELD), which instruct the Forms client to translate stored lookup codes into user-facing values. This design is characteristic of EBS business views that serve Forms windows and related inquiry pages rather than pure interface tables.

The search term final_match_flag commonly appears when users reconcile this view against matching-level attributes. In the documented projection, matching type is derived dynamically from the receipt-required and inspection-required flags via a DECODE that yields 2-WAY, 3-WAY, or 4-WAY. No literal FINAL_MATCH_FLAG column is documented in this view's text, so users seeking final-match semantics should generally reference the derived matching type or the underlying shipment columns.

Underlying Base Objects

The view is defined over five documented base objects, all referenced through synonyms in the APPS schema:

  • PO_LINE_LOCATIONS_ALL — the primary source (aliased PS), supplying shipment-level columns including location, dates, quantities, tolerances, and control flags.
  • PO_LINES_ALL — aliased PL, providing the line number and line identity for the parent order line.
  • PO_HEADERS_ALL — aliased PH, supplying header context such as SEGMENT1 (the PO number).
  • PO_RELEASES_ALL — aliased PR, supplying the release number when the shipment belongs to a release.
  • HR_ALL_ORGANIZATION_UNITS — aliased OP, providing the operating unit (organization) name for the ORG_ID.

The joins key on PO_LINE_ID, PO_HEADER_ID, PO_RELEASE_ID, and operating unit, so the view naturally flattens the standard purchasing header–line–shipment hierarchy into a single readable row per shipment. It is therefore a reporting convenience layer, not an interface table; direct DML is not appropriate.

Key Columns

Common Use Cases and Queries

Typical scenarios include shipment-level outstanding-quantity reporting, receipt and matching analysis, need-by-date monitoring, and open-commitment inquiries. The derived matching type is frequently used in place of a final-match indicator.

  • List open shipments with outstanding quantity for a given operating unit.
  • Report shipments by promised or need-by date for expediting.
  • Identify three-way and four-way match shipments before invoicing.

Sample query:

SELECT segment1, line_num, shipment_num, need_by_date, promised_date,
  quantity, quantity_received, quantity_billed,
  DECODE(NVL(receipt_required_flag,'N') || NVL(inspection_required_flag,'N'),
    'NN','2-WAY','YN','3-WAY','YY','4-WAY', NULL) matching_type
FROM apps.pobv_scheduled_shipments
WHERE org_id = :p_org_id
  AND NVL(cancel_flag,'N') = 'N'
  AND quantity > NVL(quantity_received,0) + NVL(quantity_cancelled,0)
ORDER BY promised_date, segment1, line_num, shipment_num;

Because the view exposes the shipping, receipt, and invoice quantities side by side, it is well suited to reconciliation queries that compare ordered, received, and billed amounts at shipment granularity.