Search Results ship_status_code




Overview
Explore in AI Chat

Overview

INL_SHIP_PO_OVERALL_V is a reporting view owned by the APPS schema within Oracle Landed Cost Management (INL). It consolidates shipment information for purchase orders into a single denormalized row set spanning shipment headers, shipment line groups, shipment lines, and the originating procurement and receiving documents. The view is documented as VALID and is intended for operational reporting, inquiry screens, and integration extracts that require a flattened view of landed cost shipments without navigating the normalized INL base tables. Because the view joins the INL shipment hierarchy to PO_HEADERS, PO_LINES, PO_LINE_LOCATIONS, PO_RELEASES, RCV_SHIPMENT_HEADERS, RCV_SHIPMENT_LINES, RCV_TRANSACTIONS, and item master data, it is the preferred source when a report must reconcile landed cost shipment detail against the upstream purchasing and receiving records. The element the user searched, SHIP_STATUS_CODE, is exposed directly on the view and originates from INL_SHIP_HEADERS.

Underlying Base Objects

The view is defined over synonyms and views rather than tables owned by INL directly; the documented referenced objects are FND_GLOBAL (PACKAGE), HZ_PARTIES, HZ_PARTY_SITES, INL_ADJ_SHIP_LINES_V, INL_SHIP_HEADERS, INL_SHIP_LINES, INL_SHIP_LINE_GROUPS, INL_SHIP_LINE_TYPES_VL, INL_SHIP_TYPES_VL, MTL_SYSTEM_ITEMS_VL, PO_HEADERS, PO_LINES, PO_LINE_LOCATIONS, PO_LOOKUP_CODES, PO_RELEASES, PO_VENDORS, PO_VENDOR_SITES, RCV_SHIPMENT_HEADERS, RCV_SHIPMENT_LINES, RCV_SUPPLY, and RCV_TRANSACTIONS. The INL objects supply the shipment hierarchy — header, line group, and line — while the PO and RCV objects supply upstream procurement context, acknowledgements, receipts, and supply records. FND_GLOBAL is referenced for session context such as ORG_ID. This composition means the view reflects the current integration state between landed cost shipments and their purchase order and receiving counterparts, so it should be queried with the same concurrency and performance considerations as other multi-join APPS views.

Key Columns

Common Use Cases and Queries

A frequent requirement is locating shipments by status, which is where SHIP_STATUS_CODE is most often used. The following sample filters by organization and status:

  • Shipment status listing: SELECT ship_num, ship_date, ship_status_code, ship_type_code FROM inl_ship_po_overall_v WHERE org_id = :p_org_id AND ship_status_code = :p_status;
  • Line-level detail for a shipment: SELECT ship_num, ship_line_num, item, txn_qty, txn_uom_code, txn_unit_price, currency_code FROM inl_ship_po_overall_v WHERE ship_header_id = :p_ship_header_id ORDER BY ship_line_num;
  • Pending processing review: SELECT ship_num, ship_status_code, pending_matching_flag, pending_update_flag FROM inl_ship_po_overall_v WHERE pending_matching_flag = 'Y' OR pending_update_flag = 'Y';
  • Item-based landed cost analysis: SELECT item, item_description, SUM(primary_qty) qty FROM inl_ship_po_overall_v WHERE ship_status_code = 'CLOSED' GROUP BY item, item_description;

Because the view spans INL, PO, and RCV objects, queries should always restrict by ORG_ID or SHIP_HEADER_ID to bound the result set. Reports requiring only header-level attributes should join to INL_SHIP_HEADERS directly to avoid the cost of the broader joins inherent in this view.