RCV_TRANSACTIONS

ProcurementUsed in 31 subject areas25 reporting columns

Receiving (RCV).

Likely primary key: TRANSACTION_ID (inferred from Oracle naming conventions — verify against Tables & Views)

Columns

Column	Key	In reports	Description (inferred)
ACCRUAL_STATUS_CODE		●	Code identifying the accrual status.
BILLING_UOM_CODE		●	Code identifying the billing unit of measure.
CREATED_BY		●	User who created the row.
CREATION_DATE		●	Date and time the row was created.
DIRECT_TRANSFER_ORDER_FLAG		●	Indicator (Y/N) for the direct transfer order.
INSPECTION_QUALITY_CODE		●	Code identifying the inspection quality.
INSPECTION_STATUS_CODE		●	Code identifying the inspection status.
INVOICE_STATUS_CODE		●	Code identifying the invoice status.
LAST_UPDATE_DATE		●	Date and time the row was last updated (the incremental-extract key).
PARENT_TRANSACTION_ID		●	Identifier for the parent transaction.
PO_HEADER_ID		●	Identifier for the purchase order header.
PO_LINE_ID		●	Identifier for the purchase order line.
QUANTITY		●	Quantity.
RECEIPT_EXCEPTION_FLAG		●	Indicator (Y/N) for the receipt exception.
REQ_DISTRIBUTION_ID		●	Identifier for the req distribution.
RMA_REFERENCE		●	Rma reference.
ROUTING_HEADER_ID		●	Identifier for the routing header.
SECONDARY_QUANTITY		●	Secondary quantity.
SECONDARY_UOM_CODE		●	Code identifying the secondary unit of measure.
SHIPMENT_LINE_ID		●	Identifier for the shipment line.
TRANSACTION_DATE		●	Transaction date.
TRANSACTION_ID	PK?	●	Identifier for the transaction.
TRANSACTION_TYPE		●	Type of transaction.
UOM_CODE		●	Code identifying the unit of measure.
VENDOR_ID		●	Identifier for the vendor.

Change a column here and these are the reports that move with it — the blast radius for any change to RCV_TRANSACTIONS.

The OTBI subject areas that expose this table. You can't join across them in OTBI — the owned conformed model joins them on shared keys.

Need the extract + dbt staging for RCV_TRANSACTIONS?

We ship parameterized SQL, BICC config, and dbt models you own.