Search Results allocation_amt




Overview
Explore in AI Chat

Overview

APPS.INL_ALLOCATION_FLOW_V is a reporting view in the Oracle E-Business Suite logistics and trade management schema. It exposes the flow of allocation amounts between parent entities participating in an allocation relationship, as recorded in the INL_ASSOCIATIONS and INL_ALLOCATIONS tables. The view resolves each allocation into two directional rows: one representing the source ("from") parent and one representing the destination ("to") parent, with the allocation amount sign-flipped on the source side to reflect the outflow. This symmetry allows consumers to reconstruct the full bilateral movement of quantities or values across allocation groups without performing the union logic themselves.

The view is most relevant to users and integrators querying by the ALLOCATION_AMT column, since the aggregation of that column is the central computation in the view definition and the natural entry point for allocation reporting queries.

Underlying Base Objects

The view is defined over two documented base objects, both referenced through synonyms in the APPS schema:

The two objects are joined on ASSOCIATION_ID. The view is a UNION ALL of two SELECT statements: the first aggregates ALLOCATION_AMT by the "from" parent and multiplies the sum by -1; the second aggregates ALLOCATION_AMT by the "to" parent without sign inversion. Both branches carry the association's originating parent attributes for traceability. Aggregation is performed with GROUP BY on SHIP_HEADER_ID, ADJUSTMENT_NUM, ASSOCIATION_ID, the parent table name and ID, and the association parent attributes.

Key Columns

  • SHIP_HEADER_ID — identifies the shipment header with which the allocation is associated.
  • ADJUSTMENT_NUM — the adjustment sequence number distinguishing revisions within the shipment.
  • ASSOCIATION_ID — the allocation association identifier linking back to INL_ASSOCIATIONS.
  • PARENT_TABLE_NAME / PARENT_TABLE_ID — the generic polymorphic reference to the parent entity for the row (either the "from" or the "to" side, depending on the UNION branch).
  • ALLOCATION_AMT — the summed allocation amount for the parent. Negative for "from" rows (outflow) and positive for "to" rows (inflow).
  • ASSOC_FROM_PARENT_TABLE_NAME / ASSOC_FROM_PARENT_TABLE_ID — the originating parent recorded on the association, retained on both branches for grouping and linkage.

Because PARENT_TABLE_NAME is polymorphic, consumers must resolve the underlying entity type before joining to domain-specific tables. The ALLOCATION_AMT sign convention is the primary invariant of the view and should be respected by any downstream calculation.

Common Use Cases and Queries

Typical uses include reconciliation of allocation flows for a shipment, net-position reporting per parent entity, and integration extracts into downstream cost or inventory systems. Because ALLOCATION_AMT is sign-flipped on the source side, a simple SUM over a parent yields its net allocation position.

Retrieve all flow rows for a shipment:

SELECT ship_header_id, adjustment_num, association_id,
       parent_table_name, parent_table_id, allocation_amt
FROM   apps.inl_allocation_flow_v
WHERE  ship_header_id = :ship_header_id;

Compute the net allocation amount per parent entity:

SELECT parent_table_name, parent_table_id,
       SUM(allocation_amt) net_allocation_amt
FROM   apps.inl_allocation_flow_v
WHERE  association_id = :association_id
GROUP BY parent_table_name, parent_table_id;

List the negative (outflow) rows only:

SELECT * FROM apps.inl_allocation_flow_v
WHERE  allocation_amt < 0;

Queries joining on ALLOCATION_AMT should always account for the view's sign convention and its polymorphic parent columns, and should filter on SHIP_HEADER_ID or ASSOCIATION_ID to keep result sets bounded.