Search Results primary_qty




Overview
Explore in AI Chat

Overview

INL_SHIP_LANDED_COSTS_V is a reporting view owned by the APPS schema in Oracle Landed Cost Management (INL). It consolidates landed cost information at the shipment header level, aggregating item price, charges, and taxes for each combination of shipment, adjustment, organization, and inventory item. In Oracle EBS 12.1.1 and 12.2.2 environments where Landed Cost Management is licensed and implemented, this view serves as a convenient abstraction over the more granular shipment-line-level landed cost view, enabling reporting and integration consumers to retrieve summarized cost values without traversing line-level detail.

The view is particularly relevant to users searching on "unit_landed_cost," since it exposes the derived UNIT_LANDED_COST column — essentially the total landed cost (item price plus charges plus taxes) divided by the total primary quantity. This column provides the per-unit landed cost at the shipment/item level, which is fundamental for inventory valuation comparisons, margin analysis, and auditing of landed cost allocations.

Underlying Base Objects

According to the documented metadata, INL_SHIP_LANDED_COSTS_V is defined solely over the base view INL_SHIPLN_LANDED_COSTS_V. It does not directly reference base tables; instead, it aggregates the line-level records exposed by that underlying view. The base view INL_SHIPLN_LANDED_COSTS_V supplies the shipment header identifier, adjustment number, organization, inventory item, primary quantity, unit of measure, and the individual cost components (item price, charges, taxes) that the summary view then rolls up.

Because the definition is a GROUP BY aggregation over a view rather than a table, the status of INL_SHIP_LANDED_COSTS_V is wholly dependent on the validity of INL_SHIPLN_LANDED_COSTS_V and the INL tables beneath it. In a typical EBS installation these objects are created and maintained by the INL product installation scripts and remain VALID as long as the dependent objects compile successfully.

Key Columns

  • SHIP_HEADER_ID — Identifier of the shipment header to which the landed costs belong; the primary grouping key for shipment-level reporting.
  • ADJUSTMENT_NUM — Adjustment number associated with the landed cost allocation, allowing differentiation between successive cost adjustments applied to the same shipment.
  • ORGANIZATION_ID — Inventory organization identifier, supporting multi-organization reporting and restricting results to a specific warehouse or operating unit.
  • INVENTORY_ITEM_ID — Inventory item identifier for which the costs are aggregated.
  • ITEM_PRICE — Sum of item price components across the underlying shipment lines.
  • CHARGES — Sum of landed cost charges (for example freight, duty, insurance) allocated to the shipment/item.
  • TAXES — Sum of tax amounts associated with the landed costs.
  • PRIMARY_QTY — Total primary quantity across the grouped lines.
  • PRIMARY_UOM_CODE — Unit of measure for the primary quantity.
  • UNIT_LANDED_COST — Computed as (ITEM_PRICE + CHARGES + TAXES) / PRIMARY_QTY, representing the per-unit landed cost. This is the column most commonly targeted by users searching for "unit_landed_cost."

Common Use Cases and Queries

Typical scenarios include reconciling landed cost allocations against purchase order receipts, analyzing the per-unit landed cost by item and organization, and feeding downstream cost analysis or data warehouse extracts. A representative query to retrieve unit landed cost for a specific item and organization is:

SELECT ship_header_id,
       adjustment_num,
       inventory_item_id,
       primary_qty,
       primary_uom_code,
       unit_landed_cost
  FROM apps.inl_ship_landed_costs_v
 WHERE organization_id = :org_id
   AND inventory_item_id = :item_id
 ORDER BY ship_header_id, adjustment_num;

To compare total landed cost components by shipment, the aggregated columns ITEM_PRICE, CHARGES, and TAXES can be selected directly. Because the view is an aggregation, it is best suited for summary-level reporting; line-level auditing should query INL_SHIPLN_LANDED_COSTS_V directly. Users should also be mindful that UNIT_LANDED_COST divides by PRIMARY_QTY, so records with zero quantity may yield null or error results in reporting tools that do not guard against division by zero.