Skip to content
Fusion Reference

RCV_TRANSACTIONS

Product: RCVtransactionPer inventory org

The receiving event ledger — one immutable row per receiving action (receive, inspect, transfer, deliver, correct, return), chained to its prior step by parent transaction id; the event-grain truth behind every receipt quantity

Identity
Module: ReceivingInventory-org partitioned (ORGANIZATION_ID)
Grain note

One receipt writes multiple rows (RECEIVE then DELIVER at minimum, plus corrections as new rows) — filter TRANSACTION_TYPE or received quantities double-count

Notes

Insert-only: corrections never update the original row; net quantity means walking the PARENT_TRANSACTION_ID chain (or reading the maintained net in the supply table, not yet cataloged). No item column — the item lives on the shipment line. The dictionary itself names the decode lookups: RCV_TRANSACTION_TYPE and RCV_SOURCE_DOCUMENT_TYPE.

What the badges mean
Product: EGP
Product: the Oracle product family that owns the object — the short code Oracle's Tables and Views documentation lists as the object owner. Fusion is SaaS, so this isn't a database schema; there's no SQL path to the tables at all (see the quirks guide).
master
Data class: what the table holds — master data, transaction documents, control/configuration, interface/staging, or a documented view.

Structural facts — how the table is partitioned, not a trap by itself

BU-striped (ORG_ID)
Rows are scoped to a business unit. The column is still named ORG_ID, but in Fusion it means business unit, not the EBS operating unit — treat any migrated “operating unit” filter as suspect (see the quirks guide).
Per inventory org
Rows are scoped to an inventory organization via ORGANIZATION_ID — always pair it with INVENTORY_ITEM_ID on item-level joins (see the quirks guide).
Set / ledger / named-BU striped
Some tables stripe by a named column instead of ORG_ID: reference data set (SET_ID — see the quirks guide), ledger (LEDGER_ID on the GL journal tables), or a named business-unit column (PRC_BU_ID / REQ_BU_ID in procurement). The table page’s partition line names the column, and the generated SQL anchors on it — never treat these tables as unpartitioned.
Language-striped
The table carries a LANGUAGE column (a _TL translation table or FND_LOOKUP_VALUES) — one row per language. Filter to one LANGUAGE or a join multiplies rows.

Join & extract hazards — verify before you rely on this

Date-effective
This is an _F table — one row per entity per effectivity window, with EFFECTIVE_START_DATE and EFFECTIVE_END_DATE part of the key. Join without a window filter and every fact multiplies by history (see the quirks guide).
View
This is a documented convenience view, not a physical table. Extract through the BICC data store that fronts its base objects instead of assuming the view lands as-is.
In field listings, the Key chip marks a key field — a member of the documented primary key or of a documented unique index.

Extract access

The delivered surfaces that reach this table — the BICC extract data store (PVO) for bulk extraction and the OTBI subject areas for real-time queries. There is no SQL path to the SaaS database.

  • FscmTopModelAM.ScmExtractAM.RcvBiccExtractAM.ReceivingReceiptTransactionExtractPVO
    OTBI: Receiving - Transactions Real Time

    Receipt Transactions data store — keyed on a PEO-prefixed mirror of TRANSACTION_ID. Do not confuse with the Receipt Accounting copy (CmrRcvTransactionsExtractPVO), a different table.

    Oracle data-store documentation (opens in new tab)

Fields

18 fields · 1 key

18 fields.

Table fields: position, field name, description, data type, and flags. 18 fields.
#FieldDescriptionTypeFlags
1TRANSACTION_IDSurrogate key of the receiving eventNUMBER
Key
2PARENT_TRANSACTION_IDThe parent event in the chain — walk it to net a receipt lineNUMBER
3SHIPMENT_HEADER_IDShipment header the event belongs toNUMBER
4SHIPMENT_LINE_IDShipment line the event acts on — the item lives there, not hereNUMBER
5TRANSACTION_TYPEEvent type — receive, inspect, transfer, deliver, correct, returnVARCHAR2
RCV_TRANSACTION_TYPE
6TRANSACTION_DATEWhen the receiving event occurredDATE
Filter date
7QUANTITYEvent quantity in the transaction UOMNUMBER
8UOM_CODETransaction UOM codeVARCHAR2
9PRIMARY_QUANTITYEvent quantity in the item's primary UOMNUMBER
10ORGANIZATION_IDReceiving inventory org where the event was createdNUMBER
11SOURCE_DOCUMENT_CODESource document type behind the eventVARCHAR2
RCV_SOURCE_DOCUMENT_TYPE
12PO_HEADER_IDPO header pointerNUMBER
13PO_LINE_IDPO line pointerNUMBER
14PO_LINE_LOCATION_IDPO schedule pointer — the schedule's cumulative buckets roll up from these eventsNUMBER
15DESTINATION_TYPE_CODEDestination type at event timeVARCHAR2
16SUBINVENTORYDestination subinventory of the eventVARCHAR2
17INSPECTION_STATUS_CODENot inspected, accepted, or rejectedVARCHAR2
18VENDOR_IDSupplier on the eventNUMBER

Field provenance: hand-curated. 1 key field.

Boilerplate SQL

Starting point for reading the BICC-landed copy of RCV_TRANSACTIONS on Databricks — real DATE columns need no conversion, and the org anchor and the LAST_UPDATE_DATE watermark (the column incremental BICC extracts key on) are already in place. Set your Unity Catalog location, schema, and org values below; they’re substituted into the SQL and the copy button.

Query parameters

7 parameters not filled: <catalog>, <schema>, <inventory_org_id>, <TRANSACTION_ID>, <DATE_FROM>, <DATE_TO>, <watermark>

-- ============================================================
-- Table  : RCV_TRANSACTIONS — The receiving event ledger — one immutable row per receiving action (receive, inspect, transfer, deliver, correct, return), chained to its prior step by parent transaction id; the event-grain truth behind every receipt quantity
-- Purpose: Column-selected read of RCV_TRANSACTIONS — auto-generated from field metadata
-- Grain  : One row per inventory org (ORGANIZATION_ID) + TRANSACTION_ID
-- Caution: One receipt writes multiple rows (RECEIVE then DELIVER at minimum, plus corrections as new rows) — filter TRANSACTION_TYPE or received quantities double-count
-- Notes  : Auto-generated skeleton for Oracle Fusion Cloud data landed in your lakehouse by a BICC extract — there is no SQL path to the SaaS database. Column names follow Oracle's table documentation — if your landed data still carries PVO attribute headers, map names first; see quirks #pvo-drift. Dates are real DATE/TIMESTAMP columns — no conversion needed. WHO audit columns omitted (see the quirks guide); the optional LAST_UPDATE_DATE watermark filter supports incremental extracts.
-- ============================================================
SELECT
  t.TRANSACTION_ID AS "Surrogate key of the receiving event",
  t.PARENT_TRANSACTION_ID AS "The parent event in the chain — walk it to net a receipt line",
  t.SHIPMENT_HEADER_ID AS "Shipment header the event belongs to",
  t.SHIPMENT_LINE_ID AS "Shipment line the event acts on — the item lives there, not here",
  t.TRANSACTION_TYPE AS "Event type — receive, inspect, transfer, deliver, correct, return",  -- decode t.TRANSACTION_TYPE via FND_LOOKUP_VALUES (LOOKUP_TYPE = 'RCV_TRANSACTION_TYPE', LANGUAGE-filtered)
  t.TRANSACTION_DATE AS "When the receiving event occurred",
  t.QUANTITY AS "Event quantity in the transaction UOM",
  t.UOM_CODE AS "Transaction UOM code",
  t.PRIMARY_QUANTITY AS "Event quantity in the item's primary UOM",
  t.ORGANIZATION_ID AS "Receiving inventory org where the event was created",
  t.SOURCE_DOCUMENT_CODE AS "Source document type behind the event",  -- decode t.SOURCE_DOCUMENT_CODE via FND_LOOKUP_VALUES (LOOKUP_TYPE = 'RCV_SOURCE_DOCUMENT_TYPE', LANGUAGE-filtered)
  t.PO_HEADER_ID AS "PO header pointer",
  t.PO_LINE_ID AS "PO line pointer",
  t.PO_LINE_LOCATION_ID AS "PO schedule pointer — the schedule's cumulative buckets roll up from these events",
  t.DESTINATION_TYPE_CODE AS "Destination type at event time",
  t.SUBINVENTORY AS "Destination subinventory of the event",
  t.INSPECTION_STATUS_CODE AS "Not inspected, accepted, or rejected",
  t.VENDOR_ID AS "Supplier on the event"
FROM <catalog>.<schema>.RCV_TRANSACTIONS t
WHERE
  t.ORGANIZATION_ID = <inventory_org_id>  -- inventory org, NOT the business unit — see quirks guide #item-org-striping
  -- AND t.TRANSACTION_ID = <TRANSACTION_ID>
  -- AND t.TRANSACTION_DATE >= DATE '<DATE_FROM>'
  -- AND t.TRANSACTION_DATE <= DATE '<DATE_TO>'
  -- AND t.LAST_UPDATE_DATE >= TIMESTAMP '<watermark>'  -- the column incremental BICC extracts key on
ORDER BY t.TRANSACTION_ID;

Verified September 2026 · docs release 26C

Column names differ in BICC extracts — see PVO header drift.

Relationships

Diagram of 1-hop neighbors — join details below. FND lookup decode and translation edges are highlighted; they’re the joins newcomers most often get wrong.

Join details

  • RCV_TRANSACTIONSRCV_SHIPMENT_HEADERSforeign key · N:1
    ON RCV_TRANSACTIONS.SHIPMENT_HEADER_ID = RCV_SHIPMENT_HEADERS.SHIPMENT_HEADER_ID
  • RCV_TRANSACTIONSRCV_SHIPMENT_LINESforeign key · N:1
    ON RCV_TRANSACTIONS.SHIPMENT_LINE_ID = RCV_SHIPMENT_LINES.SHIPMENT_LINE_ID
  • RCV_TRANSACTIONSRCV_TRANSACTIONSforeign key · N:1
    ON RCV_TRANSACTIONS1.PARENT_TRANSACTION_ID = RCV_TRANSACTIONS2.TRANSACTION_ID AND RCV_TRANSACTIONS1.ORGANIZATION_ID = RCV_TRANSACTIONS2.ORGANIZATION_ID
  • RCV_TRANSACTIONSPO_LINE_LOCATIONS_ALLforeign key · N:1
    ON RCV_TRANSACTIONS.PO_LINE_LOCATION_ID = PO_LINE_LOCATIONS_ALL.LINE_LOCATION_ID
  • RCV_TRANSACTIONSINV_ORG_PARAMETERSforeign key · N:1
    ON RCV_TRANSACTIONS.ORGANIZATION_ID = INV_ORG_PARAMETERS.ORGANIZATION_ID
  • RCV_TRANSACTIONSFND_LOOKUP_VALUESFND lookup decode · N:1
    ON RCV_TRANSACTIONS.TRANSACTION_TYPE = FND_LOOKUP_VALUES.LOOKUP_CODE AND FND_LOOKUP_VALUES.LOOKUP_TYPE = 'RCV_TRANSACTION_TYPE' AND FND_LOOKUP_VALUES.LANGUAGE = '<language>'
  • RCV_TRANSACTIONSFND_LOOKUP_VALUESFND lookup decode · N:1
    ON RCV_TRANSACTIONS.SOURCE_DOCUMENT_CODE = FND_LOOKUP_VALUES.LOOKUP_CODE AND FND_LOOKUP_VALUES.LOOKUP_TYPE = 'RCV_SOURCE_DOCUMENT_TYPE' AND FND_LOOKUP_VALUES.LANGUAGE = '<language>'
  • AP_INVOICE_LINES_ALLRCV_TRANSACTIONSforeign key · N:1
    ON AP_INVOICE_LINES_ALL.RCV_TRANSACTION_ID = RCV_TRANSACTIONS.TRANSACTION_ID
  • AP_INVOICE_DISTRIBUTIONS_ALLRCV_TRANSACTIONSforeign key · N:1
    ON AP_INVOICE_DISTRIBUTIONS_ALL.RCV_TRANSACTION_ID = RCV_TRANSACTIONS.TRANSACTION_ID

Browse more Receiving tables

More Receiving tables

Maintained by Summit Analytics, a supply chain analytics practice. The tools and references are free — the consulting is selective.

Part of the Summit Analytics reference library.

Work with the practice

Not affiliated with or endorsed by Oracle. Oracle and Oracle Fusion Cloud Applications are registered trademarks of Oracle and/or its affiliates.