Search Results inl_shipln_landed_costs_v




Overview
Explore in AI Chat

Overview

APPS.INL_SHIPLN_LANDED_COSTS_V is a reporting view owned by the APPS schema within Oracle Landed Cost Management (INL). It is a VALID database object in Oracle E-Business Suite 12.1.1 and 12.2.2. The view presents landed cost information aggregated at the shipment line level, allowing cost components allocated to imported or received goods to be analyzed by shipment header, adjustment number, ship line, organization, and inventory item.

In the context of the user search term landed_cost_flag, the view is significant because its internal aggregation logic filters the underlying allocation summary on LANDED_COST_FLAG = 'Y'. This flag distinguishes genuine landed cost allocations from other allocation rows that may exist for the same shipment, adjustment, line, organization, and item combination. Consequently, INL_SHIPLN_LANDED_COSTS_V serves as the canonical read-only interface for retrieving landed cost amounts that have been successfully associated with a shipment line, rather than raw allocation data that may include non-landed-cost adjustments.

The view is principally used in reporting, reconciliation, and integration scenarios where shipment-level cost composition — item price, charges, and taxes — must be examined independently and in total.

Underlying Base Objects

Per the ETRM metadata, the view's documented base objects are:

The view text references an intermediate object, INL_ALLOCATION_SUMMARY_V, from which the cost components are derived through correlated subqueries. Each subquery constrains the summary rows by SHIP_HEADER_ID, ADJUSTMENT_NUM, SHIP_LINE_ID, ORGANIZATION_ID, and INVENTORY_ITEM_ID, and applies LANDED_COST_FLAG = 'Y'. The association source table is further inspected via ASSOC_FROM_PARENT_TABLE_NAME pattern matching to classify rows as item price, charges, or taxes.

Key Columns

  • SHIP_HEADER_ID — identifier of the parent shipment header.
  • ADJUSTMENT_NUM — the landed cost adjustment number under which costs were computed.
  • SHIP_LINE_ID, SHIP_LINE_NUM — the shipment line identifier and displayed line number.
  • ORGANIZATION_ID — the inventory organization context for the allocation.
  • INVENTORY_ITEM_ID — the item to which costs are allocated.
  • ITEM_PRICE — summed allocation amount where ASSOC_FROM_PARENT_TABLE_NAME is null or does not begin with INL_CHARGE or INL_TAX.
  • CHARGES — summed allocation amount where the association originates from a table beginning with INL_CHARGE%.
  • TAXES — summed allocation amount where the association originates from a table beginning with INL_TAX%.
  • PRIMARY_QTY, PRIMARY_UOM_CODE — aggregated primary quantity and its unit of measure for the shipment line.

Common Use Cases and Queries

Typical uses include verifying landed cost allocation for a shipment, reconciling charges and taxes by item, and feeding downstream cost analysis or integration extracts. The following query lists landed cost components for a specific shipment header:

SELECT ship_line_num,
       inventory_item_id,
       item_price,
       charges,
       taxes,
       primary_qty,
       primary_uom_code
  FROM apps.inl_shipln_landed_costs_v
 WHERE ship_header_id = :p_ship_header_id
 ORDER BY ship_line_num;

To isolate lines where landed cost charges were allocated:

SELECT ship_header_id, adjustment_num, ship_line_id, charges
  FROM apps.inl_shipln_landed_costs_v
 WHERE charges > 0
   AND organization_id = :p_org_id;

Because the view is built from allocation summary data filtered by LANDED_COST_FLAG = 'Y', results reflect only allocations flagged as landed cost, making it suitable for period-end valuation and landed cost audit reporting.