Results for “adjustment_num”

AI-generated from documented ETRM metadata — verify critical details on the linked pages.

Overview

INL_ALLOCATION_FLOW_V is a reporting view owned by the APPS schema in Oracle E-Business Suite, belonging to the INL (Oracle Landed Cost Management) product. Its documented purpose is to show information on the flow of shipment amounts to derive the corresponding shipment lines. In practical terms, the view presents the allocation of landed cost charges as they cascade from a shipment header down to the underlying shipment lines, exposing both a "from" side and a "to" side of each allocation relationship. This makes it a natural reference point for reporting and reconciliation of how landed cost amounts are distributed.

The view remains VALID in both 12.1.1 and 12.2.2, and is exposed through the APPS schema. Its role in EBS reporting and integration is to provide a denormalized, aggregated picture of allocation amounts keyed to shipment headers, adjustment numbers, and associations, so that downstream reports or integrations do not need to reconstruct the allocation flow logic themselves. Note that ALLOCATION_AMT in one of the two UNION ALL branches is sign-inverted, reflecting the directional nature of the flow.

Underlying Base Objects

The view is defined over two synonyms: INL_ALLOCATIONS and INL_ASSOCIATIONS, which reference the base tables of the same names in the INL module.

• INL_ALLOCATIONS — stores the individual allocation records, including the allocation amount, the adjustment number, the association identifier, and the from/to parent table names and IDs that identify which parent object an allocation moves between.
• INL_ASSOCIATIONS — stores the association definitions linking source and target objects; the view joins on ASSOC.ASSOCIATION_ID = ALLOC.ASSOCIATION_ID.

Each row is produced by joining these two objects on ASSOCIATION_ID and grouping by ship header, adjustment number, association, and the relevant parent table/ID columns. The view is the UNION ALL of two grouped queries: the first selects the FROM_PARENT_TABLE_NAME and FROM_PARENT_TABLE_ID with SUM(ALLOCATION_AMT) * -1, and the second selects the TO_PARENT_TABLE_NAME and TO_PARENT_TABLE_ID with SUM(ALLOCATION_AMT). This structure yields a two-sided view of the same allocation data.

Key Columns

• SHIP_HEADER_ID — identifies the shipment header to which the allocation and association belong.
• ADJUSTMENT_NUM — the landed cost adjustment number associated with the allocation.
• ASSOCIATION_ID — the association linking the allocation source and target objects.
• PARENT_TABLE_NAME / PARENT_TABLE_ID — the parent object (from the FROM side or the TO side, depending on the UNION ALL branch) that the row pertains to.
• ALLOCATION_AMT — the summed allocation amount; negative for the FROM-side branch and positive for the TO-side branch, so the union describes the flow direction.
• ASSOC_FROM_PARENT_TABLE_NAME / ASSOC_FROM_PARENT_TABLE_ID — the from-parent identity taken from the association record, providing a stable reference point for grouping the flow.

Common Use Cases and Queries

Typical uses include reconcili'ing total allocated landed cost per shipment header, tracing which shipment lines receive allocations, and feeding integration extracts for cost accounting.

Example: allocation amounts grouped by shipment header and association.

• SELECT ship_header_id, adjustment_num, association_id, parent_table_name, parent_table_id, SUM(allocation_amt) allocation_amt FROM inl_allocation_flow_v GROUP BY ship_header_id, adjustment_num, association_id, parent_table_name, parent_table_id ORDER BY ship_header_id, association_id;

Example: isolating the FROM side versus the TO side of the flow for a given shipment, using the sign of ALLOCATION_AMT as the discriminator, allows reconciliation of the net flow to zero across the two union branches. Filtering by SHIP_HEADER_ID is the most selective and most common access path.

Legal Notices: Oracle Proprietary, Confidential Information.