Search Results po_rcv_charges_u1

Overview

PO.PO_RCV_CHARGES is a transactional table in the Oracle E-Business Suite Receiving schema (owner PO) that stores charge records levied against receiving shipments. Each row represents a single charge — such as freight, insurance, duty, or handling — associated with a backing receipt shipment. The table is central to landed cost processing: charges recorded here can be allocated across receipt lines and, when the INCLUDE_IN_ACQUISITION_COST flag is set, rolled into the acquisition cost of the received items. The table resides in the APPS_TS_TX_DATA tablespace, with its indexes in APPS_TS_TX_IDX, and is marked VALID in the ETRM 12.2.2 catalog with 24 documented columns.

Structurally, the table distinguishes header-level from line-level charges: if SHIPMENT_LINE_ID is null, the charge applies to the entire shipment header; otherwise it applies to the specific shipment line. The metadata's heuristic Data Vault classification is satellite-leaning, which suggests modeling this object as a satellite attached to shipment header/line hubs rather than as an independent hub — a reasonable suggestion given that every row carries foreign keys to parent shipment entities and descriptive charge attributes.

Key Information Stored

• CHARGE_ID — the entity identifier and surrogate primary key (PK CHARGE_ID_PK). It is also the single-column unique index PO_RCV_CHARGES_U1, which serves as the documented business-key candidate.
• SHIPMENT_HEADER_ID — mandatory identifier of the item shipment header being charged; every charge must have a backing header.
• SHIPMENT_LINE_ID — identifier of the charged shipment line; null for header-level charges.
• INTERFACE_CHARGE_ID — links the charge back to its originating row in the charge interface table.
• COST_FACTOR_ID — identifies the cost factor (price element type) that classifies the charge.
• CURRENCY_CODE / CURRENCY_CONVERSION_TYPE / CURRENCY_CONVERSION_RATE / CURRENCY_CONVERSION_DATE — the charge currency and the conversion parameters used to translate it.
• ALLOCATION_METHOD — the basis for spreading the charge (WEIGHT, VALUE, QUANTITY, VOLUME).
• ESTIMATED_AMOUNT / ACTUAL_AMOUNT — the estimated and finalized charge amounts.
• INCLUDE_IN_ACQUISITION_COST — flag controlling whether the charge is capitalized into item cost.
• VENDOR_ID / VENDOR_SITE_ID — the supplier and site associated with the charge.
• ESTIMATED_TAX / ACTUAL_TAX — tax components of the charge.
• Standard WHO columns (CREATION_DATE, CREATED_BY, LAST_UPDATE_DATE, LAST_UPDATED_BY) — audit lineage.

Common Use Cases and Queries

Typical scenarios include landed cost analysis, freight reconciliation, and supplier charge reporting. A frequent pattern joins charges to their shipment header to summarize cost by receipt:

SELECT c.SHIPMENT_HEADER_ID, c.COST_FACTOR_ID,
       SUM(c.ACTUAL_AMOUNT) charge_total
FROM   PO.PO_RCV_CHARGES c
WHERE  c.INCLUDE_IN_ACQUISITION_COST = 'Y'
GROUP  BY c.SHIPMENT_HEADER_ID, c.COST_FACTOR_ID;

To isolate line-level versus header-level charges, filter on SHIPMENT_LINE_ID IS NULL. Allocation reporting joins PO_RCV_CHARGE_ALLOCATIONS on CHARGE_ID to trace how each charge was distributed. Currency exposure reporting uses the conversion columns.

Related Objects

• RCV_SHIPMENT_HEADERS — referenced via SHIPMENT_HEADER_ID; the mandatory parent receipt header.
• RCV_SHIPMENT_LINES — referenced via SHIPMENT_LINE_ID; the optional parent receipt line.
• PON_PRICE_ELEMENT_TYPES — referenced via COST_FACTOR_ID; classifies the charge.
• RCV_CHARGES_INTERFACE — referenced via INTERFACE_CHARGE_ID; the inbound interface source.
• PO_RCV_CHARGE_ALLOCATIONS — references this table via CHARGE_ID; holds the per-line allocation of each charge.