Search Results charge_allocation_id

Overview

The view APPS.INL_PO_CHARGE_ALLOCATIONS_V is a reporting view owned by the APPS schema and belonging to the Oracle Landed Cost Management (INL) product. Its documented status is VALID. As stated in the ETRM metadata, this view presents INL charge allocations as displayed on the View Acquisition Costs page. It therefore plays a dual role: it is the data source for that Oracle E-Business Suite page, and it is a convenient read-only interface for reporting and integration against landed cost charge allocation data.

A user searching for charge_id reaches this view because CHARGE_ID is one of its exposed columns and represents the association between each allocation row and its originating charge line. The view consolidates allocation detail with shipment line context, estimated and actual amounts, pricing, and tax components, allowing acquisition cost information to be reconstructed without joining the underlying transactional tables directly.

Underlying Base Objects

The documented referenced base objects are:

• INL_ALLOCATIONS (SYNONYM) — core allocation records, filtered to landed cost, non-adjustment rows.
• INL_CHARGE_LINES (SYNONYM) — charge line definitions providing CHARGE_LINE_ID and the charge line type.
• INL_SHIPMENT_PVT (PACKAGE) — packaged logic invoked to compute matched actual amounts.
• PO_LINE_LOCATIONS_ALL (SYNONYM) — purchasing line location, supplying the original unit price override.
• PO_RCV_CHARGE_ALLOCATIONS (SYNONYM) — a second allocation source unioned into the result set.
• RCV_SHIPMENT_LINES (SYNONYM) — receipt shipment lines linking allocations to the landed cost shipment line.

The view definition is a UNION ALL. The first branch joins INL_ALLOCATIONS, INL_CHARGE_LINES, PO_LINE_LOCATIONS_ALL, and RCV_SHIPMENT_LINES, restricted to rows where FROM_PARENT_TABLE_NAME = 'INL_CHARGE_LINES', the parent ID matches the charge line, the ship line matches the LCM shipment line, LANDED_COST_FLAG = 'Y', and ADJUSTMENT_NUM = 0. The second branch selects directly from PO_RCV_CHARGE_ALLOCATIONS.

Key Columns

• CHARGE_ALLOCATION_ID — the allocation identifier, mapped from INL_ALLOCATIONS.ALLOCATION_ID.
• CHARGE_ID — the charge line identifier, mapped from INL_CHARGE_LINES.CHARGE_LINE_ID; this is the column returned when users search for charge_id.
• SHIPMENT_LINE_ID — the landed cost shipment line, mapped from RCV_SHIPMENT_LINES.LCM_SHIPMENT_LINE_ID.
• ESTIMATED_AMOUNT — the allocated estimated charge amount (IAL.ALLOCATION_AMT).
• ACTUAL_AMOUNT — computed through INL_SHIPMENT_PVT.GET_MATCHEDAMT against INL_CHARGE_LINES.
• ORIGINAL_UNIT_PRICE — derived from PO_LINE_LOCATIONS_ALL.PRICE_OVERRIDE.
• Tax columns — ORIGINAL_UNIT_NR_TAX, EST_RECOVERABLE_TAX, EST_NON_RECOVERABLE_TAX, ACT_RECOVERABLE_TAX, and ACT_NON_RECOVERABLE_TAX; several are hard-coded to zero, while ACT_NON_RECOVERABLE_TAX is derived via GET_MATCHEDAMT against INL_TAX_LINES.
• Audit columns — CREATION_DATE, CREATED_BY, LAST_UPDATE_DATE, LAST_UPDATED_BY.

Common Use Cases and Queries

Typical uses include reconciling estimated versus actual landed cost charge allocations, extracting charge allocation detail for financial reporting, and validating that charge lines were distributed across shipment lines correctly. A representative query returning allocations for a specific charge is:

• SELECT charge_allocation_id, charge_id, shipment_line_id, estimated_amount, actual_amount, original_unit_price FROM apps.inl_po_charge_allocations_v WHERE charge_id = :p_charge_id;
• SELECT charge_id, SUM(estimated_amount) est, SUM(actual_amount) act FROM apps.inl_po_charge_allocations_v GROUP BY charge_id;
• SELECT charge_allocation_id, shipment_line_id, estimated_amount, actual_amount FROM apps.inl_po_charge_allocations_v WHERE estimated_amount <> actual_amount;

Because ACTUAL_AMOUNT relies on the INL_SHIPMENT_PVT.GET_MATCHEDAMT function, queries against this view may carry execution cost proportional to allocation volume; filtering by charge_id or shipment_line_id is recommended.