Search Results estimated_amt




Overview
Explore in AI Chat

Overview

APPS.INL_ALLOCATIONS_V is a reporting view in the Oracle EBS Logistics (INL) schema that exposes allocation records associated with landed cost processing. The view is defined over the INL_ALLOCATIONS table and enriches each allocation row with a derived column, ESTIMATED_AMT, computed through a correlated subquery that aggregates allocation amounts across related shipment lines and adjustment records. In Oracle EBS 12.1.1 and 12.2.2, this view serves as the primary read interface for parties that need to reconcile the actual landed cost allocation amount (ALLOCATION_AMT) against its estimated counterpart (ESTIMATED_AMT). Because the view restricts output to rows where LANDED_COST_FLAG = 'Y', it is effectively a landed-cost-only projection of the underlying allocations table.

Underlying Base Objects

The documented base objects are INL_ALLOCATIONS and INL_SHIP_LINES_ALL, both referenced through APPS synonyms. INL_ALLOCATIONS is the driving table (aliased A), supplying allocation identifiers, parent relationships, shipment context, and the raw ALLOCATION_AMT. INL_SHIP_LINES_ALL is joined within an inline view (aliased B and CC) to resolve the parent shipment line identifier via NVL(CC.PARENT_SHIP_LINE_ID, CC.SHIP_LINE_ID). The ESTIMATED_AMT column is produced by a scalar subquery that re-reads INL_ALLOCATIONS (aliased IA) joined to INL_SHIP_LINES_ALL (aliased IC), aggregating NVL(IA.ALLOCATION_AMT, 0) for adjustment records with ADJUSTMENT_NUM = 0 that match either the current allocation or its parent allocation under a differing adjustment number. The outer join condition B.ALLOCATION_ID = A.ALLOCATION_ID ties the inline view back to the driving allocation row.

Key Columns

  • ALLOCATION_ID — Primary identifier of the allocation record.
  • ESTIMATED_AMT — Derived sum of NVL(ALLOCATION_AMT, 0) across base (ADJUSTMENT_NUM = 0) allocations on the parent shipment line, allowing comparison of the estimated landed cost against the actual allocated amount. This is the column most frequently targeted by users searching on "estimated_amt".
  • ALLOCATION_AMT — The actual allocation amount recorded on the row.
  • SHIP_HEADER_ID / SHIP_LINE_ID — Shipment header and line context for the allocation.
  • PARENT_ALLOCATION_ID — Reference to the parent allocation, supporting hierarchical allocation and adjustment structures.
  • ADJUSTMENT_NUM — Identifies adjustment records; zero denotes the base allocation.
  • LANDED_COST_FLAG — Filter column; the view only returns rows where this equals 'Y'.
  • ASSOCIATION_ID, FROM_PARENT_TABLE_NAME, FROM_PARENT_TABLE_ID, TO_PARENT_TABLE_NAME, TO_PARENT_TABLE_ID — Polymorphic linkage columns describing the source and target parent entities of the allocation.
  • CREATED_BY, CREATION_DATE, LAST_UPDATED_BY, LAST_UPDATE_DATE, LAST_UPDATE_LOGIN — Standard EBS audit columns.

Common Use Cases and Queries

Typical use cases include landed cost estimation versus actual reporting, reconciliation of shipment-level allocations, and integration extracts feeding cost accounting or data warehouse loads. A representative query retrieving estimated versus actual amounts for a shipment follows:

SELECT allocation_id, ship_header_id, ship_line_id, adjustment_num, estimated_amt, allocation_amt FROM apps.inl_allocations_v WHERE ship_header_id = :p_ship_header_id ORDER BY ship_line_id, adjustment_num;

To isolate variances between estimated and actual landed cost, users commonly filter on the derived column directly:

SELECT allocation_id, ship_line_id, estimated_amt, allocation_amt, (allocation_amt - estimated_amt) AS variance FROM apps.inl_allocations_v WHERE estimated_amt <> allocation_amt;

Because ESTIMATED_AMT is computed by a correlated subquery referencing INL_ALLOCATIONS and INL_SHIP_LINES_ALL, queries that filter or aggregate on this column can incur additional execution cost; restricting results by SHIP_HEADER_ID, SHIP_LINE_ID, or ALLOCATION_ID first is recommended for performance in both 12.1.1 and 12.2.2 environments.