Search Results inl_allocations_v




Overview
Explore in AI Chat

Overview

INL_ALLOCATIONS_V is a read-only view owned by the APPS schema in Oracle E-Business Suite, defined within the Oracle Landed Cost Management (INL) product. Its documented purpose is to show all amounts of a shipment, prorated across that shipment's individual shipment lines. In practice, the view presents the allocation records stored in the INL_ALLOCATIONS base table and enriches each row with parent-line context and an estimated amount, so that landed cost charges can be reconciled and reported at both the shipment-line and parent-line level.

The view plays a supporting role in ETRM-style reporting and integration. Because Landed Cost Management distributes charge amounts across shipment lines using allocation logic, the raw base table is not directly convenient for reporting: amounts must be linked back to their originating parent line, and estimated versus actual amounts must be distinguished. INL_ALLOCATIONS_V encapsulates that logic, making it suitable for ad hoc SQL, custom reports, and downstream integrations that need prorated landed cost figures without reimplementing the parent/child resolution.

Underlying Base Objects

The view is documented as referencing two base objects through synonyms in the APPS schema:

  • INL_ALLOCATIONS — the primary allocation table, holding one row per allocation record with the allocated amount, the shipment header, the shipment line, the parent table identifiers, the adjustment number, and the landed cost flag.
  • INL_SHIP_LINES_ALL — the shipment lines table, used to resolve the shipment line to its shipment header and to join child allocations back to their parent shipment line.

The view's SQL joins INL_ALLOCATIONS to an inline subquery over the same tables, using correlated scalar subqueries to derive the parent allocation identifier and the estimated amount. The join conditions correlate on FROM_PARENT_TABLE_NAME, FROM_PARENT_TABLE_ID, TO_PARENT_TABLE_NAME, TO_PARENT_TABLE_ID, SHIP_HEADER_ID, ASSOCIATION_ID, and the parent shipment line, and are restricted to rows where ADJUSTMENT_NUM = 0 and the allocation is not the row itself. This self-referential structure is what allows a child line allocation to be traced back to its parent line.

Key Columns

  • ALLOCATION_ID — primary identifier for the allocation record.
  • SHIP_HEADER_ID — the shipment header to which the allocation belongs.
  • SHIP_LINE_ID — the shipment line onto which the amount is prorated.
  • ASSOCIATION_ID — associates the allocation with its originating transaction or document context.
  • FROM_PARENT_TABLE_NAME / FROM_PARENT_TABLE_ID — identify the source parent entity, for example an INL_CHARGE_LINES row.
  • TO_PARENT_TABLE_NAME / TO_PARENT_TABLE_ID — identify the destination parent entity to which the amount is allocated.
  • PARENT_ALLOCATION_ID — the allocation identifier of the parent line, derived through the correlated subquery.
  • ESTIMATED_AMT — the amount inherited from the parent line, providing an estimate against which the line's own allocation can be compared.
  • ALLOCATION_AMT — the actual amount allocated to the shipment line.
  • LANDED_COST_FLAG — indicates whether the allocation pertains to landed cost processing.
  • ADJUSTMENT_NUM — adjustment sequence; zero denotes the base (non-adjusted) allocation used in the parent trace.
  • CREATED_BY, CREATION_DATE, LAST_UPDATED_BY, LAST_UPDATE_DATE, LAST_UPDATE_LOGIN — standard audit columns.

Common Use Cases and Queries

Typical scenarios include reconciling prorated landed cost charges per shipment line, comparing allocated amounts against parent estimates, and feeding landed cost data into costing or financial reports. A representative query lists allocations for a shipment:

  • SELECT allocation_id, ship_header_id, ship_line_id, parent_allocation_id, estimated_amt, allocation_amt, landed_cost_flag FROM apps.inl_allocations_v WHERE ship_header_id = :p_ship_header_id ORDER BY ship_line_id, allocation_id;
  • SELECT ship_line_id, SUM(allocation_amt) total_allocated FROM apps.inl_allocations_v WHERE ship_header_id = :p_ship_header_id GROUP BY ship_line_id;
  • SELECT allocation_id, allocation_amt, estimated_amt, (allocation_amt - estimated_amt) variance FROM apps.inl_allocations_v WHERE landed_cost_flag = 'Y' AND adjustment_num = 0;

Because the view contains correlated subqueries over INL_ALLOCATIONS and INL_SHIP_LINES_ALL, queries should always filter by SHIP_HEADER_ID or SHIP_LINE_ID to avoid unnecessary full scans. The view is intended for reporting and read access only; allocation maintenance should be performed against the underlying base tables through standard Landed Cost Management functionality.