Search Results ratio_to_report




Overview
Explore in AI Chat

Overview

APPS.INL_DET_LANDED_COSTS_V is a reporting view in the Oracle E-Business Suite Logistics module (INL — Landed Cost Management, part of the Inventory/Receiving product family; internal name in earlier releases: eLCM). It exposes, at the ship-line level, the detailed itemised breakdown of landed costs applied to a shipment header adjustment, including the allocation amount and the percentage each cost component contributes to the total. Landed cost components can originate from charges (INL_CHARGE_LINES), taxes (INL_TAX_LINES), or the item price itself, and this view aggregates them so that the total landed cost of a shipment line can be reconstructed and reconciled.

Because the query joins allocation summary data to landed-cost headers and to the charge/tax definitions, the view is suited to reporting and integration: for example feeding landed-cost figures into costing, margin analysis, or external customs/duty reports. It is a VIEW (not a table) and is owned by APPS, so it is normally queried through a synonym or with the APPS schema prefix and is subject to the standard EBS read-only reporting conventions.

Underlying Base Objects

The documented base objects for the 12.2.2 metadata are:

  • INL_ALLOCATIONS (synonym) — the primary driver, supplying ship_header_id, adjustment_num, ship_line_id, ship_line_group_id, organization_id, inventory_item_id, primary_qty, allocation_amt and the associated parent table/id used to identify the cost component.
  • INL_ASSOCIATIONS (synonym) — links allocations back to their originating entities (charges, taxes, ship headers/lines).
  • INL_CHARGE_LINES (synonym) — charge definitions referenced to derive the component name and charge line type.
  • INL_TAX_LINES (synonym) — tax definitions referenced to derive the tax code used as the component name.
  • INL_SHIP_HEADERS_ALL and INL_SHIP_LINES_ALL (synonyms) — shipment header and line context for the landed cost.
  • MTL_SYSTEM_ITEMS_KFV (synonym) — supplies the concatenated item segment (inv_item / component_name fallback).
  • MTL_UNITS_OF_MEASURE (synonym) — supplies the unit of measure code shown alongside the primary quantity.
  • PON_PRICE_ELEMENT_TYPES_VL (view) — supporting price element / cost component reference.

The view text references the allocation and landed-cost summary views (INL_ALLOCATION_SUMMARY_V, INL_SHIP_LANDED_COSTS_V) and charge line type lookup (INL_CHARGE_LINE_TYPES_VL), which in turn resolve to the base objects listed above.

Key Columns

Common Use Cases and Queries

Typical scenarios include reconciling the landed cost of a shipment receipt, auditing how charges and taxes are distributed across items, and exporting landed-cost detail to external systems. A representative query filtered by shipment header (the likely object of the search "inl_ship_headers") is:

  • SELECT ship_header_id, adjustment_num, ship_line_id, inv_item, unit_of_measure, component_type, component_name, allocated_amt, allocation_percent FROM apps.inl_det_landed_costs_v WHERE ship_header_id = :p_ship_header_id ORDER BY ship_line_id, component_type;
  • Aggregating by component to view total charges versus taxes for a given adjustment: SELECT component_type, SUM(allocated_amt) FROM apps.inl_det_landed_costs_v WHERE ship_header_id = :p AND adjustment_num = :a GROUP BY component_type;
  • Joining to INL_SHIP_HEADERS_ALL on ship_header_id to report the shipment number alongside the landed-cost breakdown.