Search Results rcv_charges_interface_pk

Overview

RCV_CHARGES_INTERFACE is a PO (Purchasing) schema interface table that serves as the staging area for charge lines associated with receiving transactions in Oracle E-Business Suite 12.1.1 and 12.2.2. It temporarily holds landed cost or ancillary charge information—such as freight, duty, or handling—before the Receiving Open Interface processes those rows and transfers them into the permanent receiving charge tables. The table is heavily used in procure-to-pay and landed cost workflows, where charges must be applied to receipts and ultimately interfaced to Payables or Inventory valuation.

Based on the foreign key structure provided in the ETRM metadata, the heuristic Data Vault classification of this table is a link. This reflects its role as an associative table that joins a parent receiving transaction interface row to a specific price element type (cost factor), rather than acting as a standalone hub of unique business entities or a pure descriptive satellite.

Key Information Stored

The table contains nineteen documented columns. The most significant are outlined below.

• INTERFACE_CHARGE_ID — The surrogate primary key, defined by constraint RCV_CHARGES_INTERFACE_PK. It uniquely identifies each staged charge row.
• PARENT_INTERFACE_ID — Foreign key to RCV_TRANSACTIONS_INTERFACE, linking the charge to its parent receiving transaction interface row.
• PARENT_HEADER_INTERFACE_ID — Identifier associating the charge with the parent receipt header.
• COST_FACTOR_ID — Foreign key to PON_PRICE_ELEMENT_TYPES, identifying the specific price element (freight, insurance, duty, etc.) that defines the charge.
• COST_FACTOR_CODE — The descriptive code of the price element, allowing validation without a join.
• AMOUNT — The monetary value of the charge to be applied.
• CURRENCY_CODE, CURRENCY_CONVERSION_TYPE, CURRENCY_CONVERSION_RATE, CURRENCY_CONVERSION_DATE — Currency and conversion attributes needed to translate the charge into ledger currency.
• VENDOR_ID, VENDOR_SITE_ID — Supplier and supplier site attribution for the charge.
• GROUP_ID — Grouping identifier used by concurrent interface programs to batch-process related rows.
• PROCESSING_STATUS_CODE, TRANSACTION_STATUS_CODE — Control columns indicating whether the row is pending, processed, or errored.

While the primary key is the surrogate INTERFACE_CHARGE_ID, business-key candidates include the combination of PARENT_INTERFACE_ID and COST_FACTOR_ID, which logically identifies a distinct charge per parent transaction.

Common Use Cases and Queries

Typical usage involves diagnosing why a landed cost charge failed to import, reconciling amounts before and after processing, and verifying that charges map to valid price element types.

• Identifying unprocessed charge rows: SELECT interface_charge_id, amount, processing_status_code FROM rcv_charges_interface WHERE processing_status_code IS NULL;
• Joining to resolve the price element description: SELECT rci.interface_charge_id, rci.amount, ppe.name FROM rcv_charges_interface rci, pon_price_element_types ppe WHERE rci.cost_factor_id = ppe.price_element_type_id;
• Grouping charges by parent transaction to total landed cost per receipt.
• Validating currency conversion attributes prior to submission to the Receiving Open Interface.

Because the user searched for "pon_price_element_types," the COST_FACTOR_ID relationship is especially relevant: every charge must reference a valid price element type, and reporting queries frequently join these two tables.

Related Objects

• RCV_TRANSACTIONS_INTERFACE — Parent interface table; joined via RCV_CHARGES_INTERFACE.PARENT_INTERFACE_ID.
• PON_PRICE_ELEMENT_TYPES — Defines valid charge types; joined via COST_FACTOR_ID.
• PO_RCV_CHARGES — The permanent receiving charges table that references RCV_CHARGES_INTERFACE.INTERFACE_CHARGE_ID.
• RCV_CHARGES_INTERFACE_PK — Primary key constraint enforcing uniqueness on INTERFACE_CHARGE_ID.
• Receiving Open Interface concurrent program — The process that consumes rows from this table.

Together these objects form the landed cost interface chain from staging through validation to permanent receiving charge records.