Results for “picking_line_id”

50+ results




Overview
Explore in AI Chat

AI-generated from documented ETRM metadata — verify critical details on the linked pages.

Overview

The JAI_OE_MATCH_LINES_V view is an Oracle E-Business Suite dictionary object owned by the APPS schema and delivered as part of the JA — Asia/Pacific Localizations product family. It is a reporting and integration view whose purpose is to expose order-to-shipment match lines that are eligible for localised (Asia/Pacific) matching, invoicing, and excise/trading processing. Rather than simply projecting shipping data, the view filters WSH_DELIVERY_DETAILS so that only order-sourced delivery lines (SOURCE_CODE = 'OE') belonging to deliveries that are still open, and whose subinventory and item setups are flagged for trading and excise, are returned.

The view is central to the reconciliation flow between order management, shipping, and the localised inventory/AP matching logic. It is commonly joined by custom reports, interfaces, and concurrent programs that need a consolidated picture of shippable order lines, including organisation, customer, item, delivery, and location context. Because the view already applies the trading and excise constraints, consumers avoid re-implementing complex filtering rules.

Underlying Base Objects

JAI_OE_MATCH_LINES_V is defined over shipping and localisation tables joined together. The documented base objects are:

  • WSH_DELIVERY_DETAILS (WDD) — the shipment line (delivery detail) driving the row.
  • WSH_NEW_DELIVERIES (WND) — the parent delivery header, providing delivery ID and status.
  • WSH_DELIVERY_ASSIGNMENTS (WDA) — links delivery details to deliveries.
  • JAI_INV_SUBINV_DTLS (JSUBINV) — subinventory level localisation setups, filtered to trading subinventories.
  • JAI_INV_ITM_SETUPS (JAMSI) — item-level localisation setups, filtered to trading and excise-flagged items.
  • JAI_CMN_MATCH_RECEIPTS — referenced through a NOT EXISTS subquery to exclude detail IDs already matched.
  • Supporting views/packages such as HR_LOCATIONS_V, HR_GENERAL, and HR_API are referenced in metadata for organisation/location resolution.

The join logic requires WDA.DELIVERY_ID = WND.DELIVERY_ID, WDA.DELIVERY_DETAIL_ID = WDD.DELIVERY_DETAIL_ID, and WND.ORGANIZATION_ID = WDD.ORGANIZATION_ID. Subinventory and location setups must match, and the delivery status must not be Closed, Cancelled, or In-Transit ('CO', 'CL', 'IT').

Key Columns

The column list exposed by the view differs slightly from the internal select-list aliases; the documented columns are:

  • ORGANIZATION_ID / ORG_ID — inventory organisation owning the shipment line.
  • CUSTOMER_ID — customer associated with the order shipment.
  • INVENTORY_ITEM_ID — the shipped item.
  • PICKING_LINE_ID / DELIVERY_DETAIL_ID — the delivery detail identifier.
  • SUBINVENTORY — source subinventory.
  • ORDER_NO / ORDER_HEADER_ID — source order number and header reference.
  • LINE_ID — source order line reference.
  • UOM — unit of measure for requested quantity.
  • RELEASE_QTY — picked quantity, defaulting to requested quantity via NVL.
  • DELIVERY_ID — parent delivery identifier.
  • ORDER_TYPE_ID — order type of the source order.
  • LOCATION_ID — ship-from location.

Common Use Cases and Queries

Typical scenarios include localisation matching reports, excise documentation, and pre-invoice reconciliation. The following query returns open order match lines for a given organisation:

  • SELECT order_no, line_id, inventory_item_id, subinventory, release_qty, uom, delivery_id FROM jai_oe_match_lines_v WHERE organization_id = :org_id;
  • Joining to JAI_CMN_MATCH_RECEIPTS to identify lines not yet matched for invoicing.
  • Filtering by ORDER_HEADER_ID to reconcile all shipment lines belonging to a specific sales order.
  • Aggregating RELEASE_QTY by inventory_item_id for excise stock movement reporting.

Because the view enforces trading, excise, and status filters, it should be treated as a read-only reporting source and not updated directly.