Search Results po_rcv_charge_allocations




Overview
Explore in AI Chat

Overview

The PO.PO_RCV_CHARGE_ALLOCATIONS table is a Purchasing (PO) module data object that records how charges captured against receipts are allocated, or apportioned, across individual receipt shipment lines. In Oracle EBS procurement, landed costs and other receipt-level charges (freight, duty, insurance, handling) are typically defined at a broader level through the PO_RCV_CHARGES table, but accurate accounting and inventory valuation requires that each such charge be spread across the shipment lines it relates to. PO_RCV_CHARGE_ALLOCATIONS is the table that stores this distribution, holding the estimated, actual, and tax-related amounts attributed to each shipment line.

In Data Vault modeling terms, the metadata's heuristic classification identifies this object as a link. That classification is suggested by its foreign-key structure: the table's role is fundamentally to associate a charge record with a shipment line record, which is characteristic of a link table connecting two business entities. This is a heuristic modeling suggestion rather than a formally declared Data Vault construct.

Key Information Stored

The documented physical schema contains 15 columns, with the surrogate primary key being CHARGE_ALLOCATION_ID, enforced by the PO_RCV_CHARGE_ALLOCATION_PK constraint. This surrogate key is system-generated and carries no business meaning; it exists to uniquely identify each allocation row.

Two columns function as the principal foreign keys and, jointly, serve as the strongest business-key candidates for the allocation record:

  • CHARGE_ID — references PO_RCV_CHARGES, identifying the parent charge being allocated.
  • SHIPMENT_LINE_ID — references RCV_SHIPMENT_LINES, identifying the receipt shipment line that receives the allocated portion.

The financial and tax columns carry the quantitative substance of the allocation:

The standard audit columns — CREATION_DATE, CREATED_BY, LAST_UPDATE_DATE, and LAST_UPDATED_BY — track the who-and-when lifecycle of each allocation row.

Common Use Cases and Queries

Typical uses center on landed-cost reporting, inventory valuation reconciliation, and tax recoverability analysis. A common query pattern joins the allocation to its parent charge and shipment line to present the full costing picture:

  • Landed-cost detail: join PO_RCV_CHARGE_ALLOCATIONS to PO_RCV_CHARGES on CHARGE_ID to obtain the charge type, then to RCV_SHIPMENT_LINES on SHIPMENT_LINE_ID to obtain the item and quantity, exposing the per-line allocated freight or duty.
  • Estimated versus actual reconciliation: compare ESTIMATED_AMOUNT against ACTUAL_AMOUNT to quantify variances in allocated charges.
  • Tax recoverability reporting: aggregate EST_RECOVERABLE_TAX and ACT_RECOVERABLE_TAX to determine recoverable versus non-recoverable tax absorbed into inventory cost.
  • Charge distribution audit: group by CHARGE_ID and sum allocated amounts to verify the sum of allocations equals the original charge.

A representative pattern is:

  • SELECT a.CHARGE_ID, a.SHIPMENT_LINE_ID, a.ESTIMATED_AMOUNT, a.ACTUAL_AMOUNT FROM PO.PO_RCV_CHARGE_ALLOCATIONS a WHERE a.CHARGE_ID = :charge_id;

Related Objects

The following objects are the most significant dependents or references, based on documented foreign-key relationships and PO module context:

  • PO_RCV_CHARGES — parent charge master; joined via PO_RCV_CHARGE_ALLOCATIONS.CHARGE_ID = PO_RCV_CHARGES.CHARGE_ID.
  • RCV_SHIPMENT_LINES — the receipt shipment line receiving the allocation; joined via PO_RCV_CHARGE_ALLOCATIONS.SHIPMENT_LINE_ID = RCV_SHIPMENT_LINES.SHIPMENT_LINE_ID.
  • PO_RCV_CHARGE_ALLOCATION_PK — the primary-key constraint enforcing unique CHARGE_ALLOCATION_ID values.
  • Receiving and receiving-transaction tables that feed shipment lines into the allocation process.
  • Purchasing and inventory valuation reporting views that consume allocated charge amounts.

Together these relationships position PO_RCV_CHARGE_ALLOCATIONS as the connective link between charge definitions and receipt lines, enabling accurate landed-cost and tax accounting in Oracle EBS 12.1.1 and 12.2.2.