Skip to content
EBS Reference

RCV_TRANSACTIONS

Schema: POtransactionPer 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

Module: ReceivingInventory-org partitioned (ORGANIZATION_ID)
Grain note

One receipt writes multiple rows (RECEIVE then DELIVER, plus corrections and returns as separate signed rows) — filter TRANSACTION_TYPE or received quantities double-count

Notes

Insert-only: corrections never update the original row; net quantity means summing the parent-transaction chain. No item column — the item lives on the shipment line. The transaction-type code list is not Tier-1 enumerable, so it ships undecoded.

What the badges mean
master
Data class: what the table holds — master data, transaction documents, control/configuration, interface/staging, or an APPS-schema view.
In field listings, K marks a primary-key field.

Fields

18 fields · 1 key

Table fields: position, field name, description, data type, and flags. 18 fields.
#FieldDescriptionTypeFlags
1TRANSACTION_IDSurrogate key of the receiving eventNUMBER
Key
2TRANSACTION_TYPEThe receiving action — receive, accept, reject, transfer, deliver, correct, return; the code list is not Tier-1 enumerable, so it ships undecodedVARCHAR2
3TRANSACTION_DATEWhen the event happened — the primary analysis dateDATE
Filter date
4ORGANIZATION_IDThe inventory org the event happened inNUMBER
5PARENT_TRANSACTION_IDThe prior step in the receive→inspect→deliver chain — the self-join that nets correctionsNUMBER
6SHIPMENT_HEADER_IDThe receipt/shipment headerNUMBER
7SHIPMENT_LINE_IDThe shipment line — where the item lives; this ledger has no item columnNUMBER
8QUANTITYEvent quantity in the transaction UOM — sign semantics come from the transaction typeNUMBER
9UNIT_OF_MEASURETransaction UOM, name formVARCHAR2
10PRIMARY_QUANTITYEvent quantity in the item's primary UOM — the column to aggregateNUMBER
11SOURCE_DOCUMENT_CODEThe document family being received againstVARCHAR2
12DESTINATION_TYPE_CODEWhere this step puts the goods — receiving, inventory, expense, shop floorVARCHAR2
13PO_HEADER_IDThe PO, for PO receiptsNUMBER
14PO_LINE_IDThe PO lineNUMBER
15PO_LINE_LOCATION_IDThe PO shipment schedule the event executes againstNUMBER
16PO_DISTRIBUTION_IDThe PO distribution, once delivery is distributedNUMBER
17SUBINVENTORYPutaway subinventory on deliver rowsVARCHAR2
18INSPECTION_STATUS_CODEInspection outcome — not inspected, accepted, or rejectedVARCHAR2

Field provenance: hand-curated. 1 key field.

Boilerplate SQL

Starting point for reading RCV_TRANSACTIONSon Databricks — real DATE columns need no conversion, and the org anchor and the LAST_UPDATE_DATE watermark 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
-- ============================================================
-- 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, plus corrections and returns as separate signed rows) — filter TRANSACTION_TYPE or received quantities double-count
-- Notes  : Auto-generated skeleton for Oracle EBS R12 data landed in your lakehouse. 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.TRANSACTION_TYPE AS "The receiving action — receive, accept, reject, transfer, deliver, correct, return; the code list is not Tier-1 enumerable, so it ships undecoded",
  t.TRANSACTION_DATE AS "When the event happened — the primary analysis date",
  t.ORGANIZATION_ID AS "The inventory org the event happened in",
  t.PARENT_TRANSACTION_ID AS "The prior step in the receive→inspect→deliver chain — the self-join that nets corrections",
  t.SHIPMENT_HEADER_ID AS "The receipt/shipment header",
  t.SHIPMENT_LINE_ID AS "The shipment line — where the item lives; this ledger has no item column",
  t.QUANTITY AS "Event quantity in the transaction UOM — sign semantics come from the transaction type",
  t.UNIT_OF_MEASURE AS "Transaction UOM, name form",
  t.PRIMARY_QUANTITY AS "Event quantity in the item's primary UOM — the column to aggregate",
  t.SOURCE_DOCUMENT_CODE AS "The document family being received against",
  t.DESTINATION_TYPE_CODE AS "Where this step puts the goods — receiving, inventory, expense, shop floor",
  t.PO_HEADER_ID AS "The PO, for PO receipts",
  t.PO_LINE_ID AS "The PO line",
  t.PO_LINE_LOCATION_ID AS "The PO shipment schedule the event executes against",
  t.PO_DISTRIBUTION_ID AS "The PO distribution, once delivery is distributed",
  t.SUBINVENTORY AS "Putaway subinventory on deliver rows",
  t.INSPECTION_STATUS_CODE AS "Inspection outcome — not inspected, accepted, or rejected"
FROM <catalog>.<schema>.RCV_TRANSACTIONS t
WHERE
  t.ORGANIZATION_ID = <inventory_org_id>  -- inventory org, NOT the operating unit — see quirks guide #two-orgs
  -- 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>'  -- WHO watermark, bulk-stamped by batch jobs; see quirks guide #who-columns
ORDER BY t.TRANSACTION_ID;

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

Relationships

1-hop neighbors — click a table to navigate there. FND lookup decode and translation edges are highlighted; they’re the joins newcomers most often get wrong.

Join details

  • RCV_TRANSACTIONSRCV_SHIPMENT_LINESforeign key · N:1
    ON RCV_TRANSACTIONS.SHIPMENT_LINE_ID = RCV_SHIPMENT_LINES.SHIPMENT_LINE_ID
  • RCV_TRANSACTIONSRCV_SHIPMENT_HEADERSforeign key · N:1
    ON RCV_TRANSACTIONS.SHIPMENT_HEADER_ID = RCV_SHIPMENT_HEADERS.SHIPMENT_HEADER_ID
  • RCV_TRANSACTIONSPO_LINE_LOCATIONS_ALLforeign key · N:1
    ON RCV_TRANSACTIONS.PO_LINE_LOCATION_ID = PO_LINE_LOCATIONS_ALL.LINE_LOCATION_ID
  • RCV_TRANSACTIONSPO_DISTRIBUTIONS_ALLforeign key · N:1
    ON RCV_TRANSACTIONS.PO_DISTRIBUTION_ID = PO_DISTRIBUTIONS_ALL.PO_DISTRIBUTION_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
  • MTL_MATERIAL_TRANSACTIONSRCV_TRANSACTIONSforeign key · N:1
    ON MTL_MATERIAL_TRANSACTIONS.RCV_TRANSACTION_ID = RCV_TRANSACTIONS.TRANSACTION_ID AND MTL_MATERIAL_TRANSACTIONS.ORGANIZATION_ID = RCV_TRANSACTIONS.ORGANIZATION_ID
  • WIP_TRANSACTIONSRCV_TRANSACTIONSforeign key · N:1
    ON WIP_TRANSACTIONS.RCV_TRANSACTION_ID = RCV_TRANSACTIONS.TRANSACTION_ID AND WIP_TRANSACTIONS.ORGANIZATION_ID = RCV_TRANSACTIONS.ORGANIZATION_ID

Browse more Receivingtables →

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 E-Business Suite are registered trademarks of Oracle and/or its affiliates.