Search Results inl_adj_ship_lines_v




Overview
Explore in AI Chat

Overview

INL_ADJ_SHIP_LINES_V is a PL/SQL view owned by the APPS schema in Oracle E-Business Suite 12.1.1 and 12.2.2. It is a component of Oracle Landed Cost Management (INL), the module responsible for estimating, accruing, and reconciling landed costs such as freight, duty, insurance, and brokerage against received goods. Within that module, the view exposes adjustment shipment line records — the transaction lines that represent landed cost adjustments applied to an original shipment line — and presents them in a flattened, query-ready form.

The view's practical role is reporting and integration rather than transactional data entry. Because the base table INL_SHIP_LINES_ALL stores every version of a shipment line, including superseded rows generated when adjustments are applied, consumers that simply query the base table risk retrieving multiple historical rows for the same logical line. INL_ADJ_SHIP_LINES_V resolves this ambiguity by returning only the most recent row per shipment header, line group, and line number, making it suitable for extracts, reconciliation reports, and downstream integrations.

Underlying Base Objects

The view is defined over a single documented base object, the synonym INL_SHIP_LINES_ALL, which resolves to the INL shipment lines table in the APPS schema. The view does not join to INL_SHIP_HEADERS_ALL or to any receipt, purchase order, or inventory table; header-level and receipt-level context must be obtained separately by joining on SHIP_HEADER_ID or MATCH_ID.

The defining predicate is a correlated subquery. For each candidate row OPL1, the view retains it only when its SHIP_LINE_ID equals the maximum SHIP_LINE_ID among all rows sharing the same SHIP_HEADER_ID, SHIP_LINE_GROUP_ID, and SHIP_LINE_NUM. Because SHIP_LINE_ID is system-generated in ascending order, the maximum value identifies the newest version of that line. The effect is a de-duplicating filter: one row per logical shipment line, representing its current adjustment state.

Key Columns

Common Use Cases and Queries

The view is typically used to report current adjustment line detail, to reconcile landed cost adjustments against receipts matched through MATCH_ID, and to drive extracts into tax determination or cost accounting processes. A basic query lists the current lines for a shipment:

  • SELECT ship_header_id, ship_line_num, adjustment_num, inventory_item_id, txn_qty, primary_unit_price, fc_primary_unit_price FROM inl_adj_ship_lines_v WHERE ship_header_id = :p_header_id ORDER BY ship_line_num;
  • SELECT ship_line_id, match_id, currency_code, assessable_value FROM inl_adj_ship_lines_v WHERE org_id = :p_org_id AND landed_cost_flag = 'Y' AND adjustment_num IS NOT NULL;
  • SELECT v.ship_line_num, v.txn_qty, v.primary_unit_price, v.fc_primary_unit_price FROM inl_adj_ship_lines_v v WHERE v.ship_header_id = :p_header_id AND v.parent_ship_line_id IS NOT NULL;

Because the view carries ORG_ID, queries should always filter by operating unit to respect multi-org access. When header attributes such as shipment number or vendor are required, join to the shipment header table on SHIP_HEADER_ID. Since INL_SHIP_LINES_ALL can be large, filtering on SHIP_HEADER_ID or MATCH_ID is strongly recommended to avoid full scans driven by the correlated subquery predicate.