Search Results src_party_id




Overview
Explore in AI Chat

Overview

INL_SHIP_OVERALL_V is a VALID APPS-schema view belonging to the Oracle Landed Cost Management (INL) product family. Per its ETRM documentation, the view "shows overall information on Shipments and their sources different from Purchase Orders, Internal Requisitions and RMA." In the Oracle EBS 12.1.1 and 12.2.2 environments, Landed Cost Management relies on shipment records to associate estimated and actual landed cost charges to inbound and outbound material movements. Because the primary integration paths for LCM are purchase orders, internal requisitions, and returns, this view exists to surface the broader, "catch-all" shipment universe — shipment headers and their type classification — regardless of whether an individual shipment line traces back to one of those standard source documents.

Functionally, INL_SHIP_OVERALL_V acts as a header-level projection. It presents shipment header attributes from the LCM shipment header entity, plus empty (NULL-typed) placeholders for the entire subordinate line-level model (ship line groups, ship lines, item details, quantities, pricing, currency, and full source resolution). This design makes it a stable, upwardly compatible interface: downstream reports and integrations can select a consistent column footprint while the line-level population is supplied by companion views such as INL_ADJ_SHIP_LINES_V.

Underlying Base Objects

The documented base objects for INL_SHIP_OVERALL_V are:

The view therefore depends on the LCM shipment header for its populated content and on the ORG and HR security infrastructure for row-level access control, while merely naming the line-level and party objects to preserve a consistent column list.

Key Columns

  • SHIP_HEADER_ID — primary key of the shipment header; the join key to line-level LCM views.
  • SHIP_NUM, SHIP_DATE, SHIP_STATUS_CODE — business identifier, shipment date, and lifecycle status of the shipment.
  • SHIP_TYPE_ID, SHIP_TYPE_CODE, SHIP_TYPE_NAME — shipment type classification, resolved through INL_SHIP_TYPES_VL.
  • ORGANIZATION_ID, ORG_ID, LOCATION_ID — inventory organization, operating unit, and location context of the shipment.
  • PENDING_MATCHING_FLAG, PENDING_UPDATE_FLAG — processing indicators signalling matching or update work outstanding for the shipment.
  • SIMULATION_ID — identifies a what-if LCM simulation run rather than a live shipment.
  • NULL placeholders — SHIP_LINE_GROUP_ID, SHIP_LINE_ID, SRC_TYPE_CODE, SRC_* party/vendor/customer/source attributes, ITEM_*, TXN_QTY, TXN_UNIT_PRICE, LINE_AMT, and currency conversion columns are all typed NULL, confirming this view exposes headers only.

Common Use Cases and Queries

Typical uses include header-level shipment reporting, identifying shipments with pending matching or update activity, and pulling the shipment population into LCM landed-cost analysis alongside the line-level views. A representative query is:

  • SELECT ship_num, ship_date, ship_status_code, ship_type_name, organization_id FROM apps.inl_ship_overall_v WHERE ship_status_code = 'NEW' ORDER BY ship_date DESC;
  • SELECT ship_num, pending_matching_flag, pending_update_flag FROM apps.inl_ship_overall_v WHERE pending_matching_flag = 'Y' OR pending_update_flag = 'Y';
  • Join to INL_ADJ_SHIP_LINES_V on SHIP_HEADER_ID when line-level landed-cost detail is required.

Because line and source columns are NULL, queries must not rely on this view for item or source-document detail; they should join to the appropriate line-level LCM view instead.