Search Results adjustment_num




Overview
Explore in AI Chat

Overview

APPS.INL_DET_LANDED_COSTS_V is a reporting view in the Oracle Landed Cost Management (INL) module of Oracle E-Business Suite, available in releases 12.1.1 and 12.2.2 with status VALID. Its stated purpose is to present detailed landed cost information for a shipment. Landed Cost Management allows organizations to capture charges, taxes, and item prices associated with inbound shipments, allocate those costs across receipt lines, and correlate estimated charges with the actual supplier invoices received against each shipment.

The view consolidates allocation rows from INL_ALLOCATIONS with shipment header and line context, item master descriptions, unit of measure lookups, and charge or tax definitions. It explicitly exposes ADJUSTMENT_NUM, the column referenced in the user's search. In INL, ADJUSTMENT_NUM identifies a cost adjustment or estimate-versus-actual revision of a landed cost. A null value typically represents the original estimate, while a positive value denotes an adjustment cycle, and a negative value represents the reversal of a prior adjustment. This convention is visible in the view's internal DECODE and SIGN logic, which distinguishes estimated versus actual allocated amounts. The view therefore serves as a foundational data source for cost simulation, trade operations reporting, and custom OBIEE or BI Publisher extracts.

Underlying Base Objects

The view is defined in the APPS schema and, based on documented metadata, references the following base objects through synonyms:

The join fabric ties each allocation to its shipment header and line, then enriches it with descriptive attributes from the item, UOM, and pricing element sources.

Key Columns

Common Use Cases and Queries

Typical scenarios include reconciling estimated landed costs to actual invoices, analyzing allocation percentages per component, and reporting cost adjustments by shipment and organization.

Example: retrieve all landed cost components for a shipment header, including adjustment versions.

  • SELECT ship_header_id, adjustment_num, ship_line_id, inv_item, component_type, component_code, allocated_amt, allocation_percent, estimated_allocated_amt FROM apps.inl_det_landed_costs_v WHERE ship_header_id = :p_ship_header_id ORDER BY ship_line_id, adjustment_num;

Example: isolate adjustment activity where an estimate has been revised.

  • SELECT ship_header_id, adjustment_num, ship_line_id, component_name, allocated_amt, estimated_allocated_amt FROM apps.inl_det_landed_costs_v WHERE adjustment_num IS NOT NULL ORDER BY ship_header_id, adjustment_num;

Example: summarize allocated costs by component type for a shipment.

  • SELECT component_type, component_code, SUM(allocated_amt) allocated_total FROM apps.inl_det_landed_costs_v WHERE ship_header_id = :p_ship_header_id GROUP BY component_type, component_code;

Because the view already performs aggregation and percentage calculations, it is well suited to direct reporting queries; however, callers should filter on SHIP_HEADER_ID and ADJUSTMENT_NUM to control the volume of rows returned from large alloc transactions.