Search Results charge_id_pk

Overview

PO_RCV_CHARGES is a Purchasing (PO) module table that stores freight and special charge records associated with receiving transactions in Oracle E-Business Suite 12.1.1 and 12.2.2. Each row represents an individual charge applied against a shipment header or shipment line, capturing the estimated and actual amounts passed from the receiving process into purchasing and cost accounting. The table is owned by the PO schema and is populated primarily through receiving and inspection workflows, where freight, duty, insurance, and other landed-cost elements are recorded against received goods.

From a dimensional modeling perspective, the FK structure classifies this object as satellite-leaning: it carries descriptive, time-stamped attributes (amounts, currency, dates) keyed by a surrogate primary key, and it hangs off core transactional entities such as RCV_SHIPMENT_LINES and RCV_SHIPMENT_HEADERS. This heuristic classification suggests treating PO_RCV_CHARGES as an attribute satellite to the receiving shipment hub, rather than as an independent hub or a linking table.

Key Information Stored

The table contains 24 documented columns. The most significant are summarized below.

• CHARGE_ID — Surrogate primary key defined by unique index PO_RCV_CHARGES_U1, uniquely identifying each charge record.
• SHIPMENT_HEADER_ID — Foreign key to RCV_SHIPMENT_HEADERS, tying the charge to the parent receipt.
• SHIPMENT_LINE_ID — Foreign key to RCV_SHIPMENT_LINES, tying the charge to a specific received line when the charge applies at line level.
• INTERFACE_CHARGE_ID — Foreign key to RCV_CHARGES_INTERFACE, linking open-interface charge rows to their persisted counterparts.
• COST_FACTOR_ID — Foreign key to PON_PRICE_ELEMENT_TYPES, identifying the price element (freight, duty, etc.) that classifies the charge.
• ESTIMATED_AMOUNT / ACTUAL_AMOUNT — The accrual estimate and the final booked charge value.
• ESTIMATED_TAX / ACTUAL_TAX — Corresponding tax amounts for estimated versus actual charges.
• CURRENCY_CODE, CURRENCY_CONVERSION_TYPE, CURRENCY_CONVERSION_RATE, CURRENCY_CONVERSION_DATE — Currency and conversion attributes used to translate charges into functional currency.
• ALLOCATION_METHOD — Determines how the charge is prorated across lines.
• INCLUDE_IN_ACQUISITION_COST — Flag indicating whether the charge is capitalized into item cost.
• VENDOR_ID, VENDOR_SITE_ID — Supplier and supplier site responsible for the charge.
• COST_COMPONENT_CLASS_ID, COST_ANALYSIS_CODE — Costing classifications used downstream by inventory and Cost Management.

Common Use Cases and Queries

Typical reporting uses include landed-cost analysis, freight accrual reconciliation, and supplier charge variance reporting. A common query pattern joins charges to their shipment lines and price element types:

• Retrieve all charges for a receipt: SELECT c.charge_id, c.estimated_amount, c.actual_amount FROM po.po_rcv_charges c WHERE c.shipment_header_id = :header_id;
• Break down charges by price element: SELECT p.price_element_code, SUM(c.actual_amount) FROM po.po_rcv_charges c, pon_price_element_types p WHERE c.cost_factor_id = p.price_element_type_id GROUP BY p.price_element_code;
• Reconcile interface to persisted charges via INTERFACE_CHARGE_ID against RCV_CHARGES_INTERFACE.
• Analyze allocation detail by joining PO_RCV_CHARGE_ALLOCATIONS on CHARGE_ID to distribute charges across receipt lines.
• Filter currency conversion exceptions where CURRENCY_CONVERSION_RATE is null.

Related Objects

• RCV_SHIPMENT_LINES — parent line entity joined on SHIPMENT_LINE_ID.
• RCV_SHIPMENT_HEADERS — parent receipt header joined on SHIPMENT_HEADER_ID.
• PON_PRICE_ELEMENT_TYPES — charge classification reference joined on COST_FACTOR_ID.
• RCV_CHARGES_INTERFACE — inbound interface staging joined on INTERFACE_CHARGE_ID.
• PO_RCV_CHARGE_ALLOCATIONS — child allocation detail referencing CHARGE_ID for line-level charge distribution.