Search Results root_transaction

Overview

RCV_FTE_TRANSACTIONS_V is a seeded Oracle E-Business Suite view owned by the APPS schema and classified under the PO – Purchasing product family. Its documented purpose is to provide rolled up transactions for logistics, meaning it consolidates receiving activity into a form suitable for downstream logistics, transportation, and warehouse-facing reporting. The view is a union of two query branches: the first returns base receipt and match transactions, while the second resolves return-to-vendor activity back to its originating receipt so that logistics consumers see a normalized, parent-linked transaction stream.

Rather than exposing raw RCV_TRANSACTIONS rows verbatim, the view normalizes several attributes. For example, the TRANSACTION_TYPE column applies a DECODE that reclassifies 'MATCH' rows as 'RECEIPT', aligning matched transactions with the physical receipt event they correspond to. The first branch emits NULL values for parent columns, whereas the second branch populates PARENT_TRANSACTION_ID and PARENT_TRANSACTION_TYPE from the associated receipt. This makes the view an integration-friendly surface for systems that expect a single, hierarchically consistent view of receiving data.

Underlying Base Objects

Per the documented ETRM 12.2.2 metadata, RCV_FTE_TRANSACTIONS_V is defined over two referenced base objects:

• RCV_TRANSACTIONS (SYNONYM) – the core receiving transactions table supplying transaction identifiers, dates, quantities, UOMs, locators, subinventories, and audit columns.
• MTL_UNITS_OF_MEASURE (SYNONYM) – the units-of-measure lookup used to translate the numeric UOM identifiers on RCV_TRANSACTIONS into human-readable UOM_CODE values.

The view references MTL_UNITS_OF_MEASURE three times via aliases — MUOM, PRIMARY_MUOM, and SECONDARY_MUOM — each joined with an outer join ((+)) on the corresponding UOM column of RCV_TRANSACTIONS. The RCV_TRANSACTIONS synonym is also self-joined in the second union branch to link return-to-vendor rows to their parent receipt.

Key Columns

The view exposes the full set of logistics-relevant receiving attributes, including:

• TRANSACTION_ID – the unique key of the receiving transaction; also used as ROOT_TRANSACTION/PARENT_TRANSACTION_ID linkage.
• TRANSACTION_TYPE – normalized as 'RECEIPT' for both 'RECEIVE' and 'MATCH' rows; other types pass through unchanged.
• TRANSACTION_DATE, SHIPMENT_LINE_ID, PO_UNIT_PRICE, CURRENCY_CODE – commercial and timing context of the receipt.
• QUANTITY, PRIMARY_QUANTITY, SECONDARY_QUANTITY – transactional quantities at each UOM level.
• UOM_CODE, PRIMARY_UOM_CODE, and SECONDARY_UOM_CODE – resolved UOM codes. The SECONDARY_UOM_CODE column, mapped from RT.SECONDARY_UNIT_OF_MEASURE through the SECONDARY_MUOM alias, is the value commonly searched for when reconciling dual-UOM (primary/secondary) receipt capture in a logistics interface.
• QC_GRADE, COUNTRY_OF_ORIGIN_CODE, LPN_ID, LOCATOR_ID, SUBINVENTORY – receiving quality and physical placement attributes.
• Audit columns: LAST_UPDATE_DATE, LAST_UPDATED_BY, CREATION_DATE, CREATED_BY, LAST_UPDATE_LOGIN.

Common Use Cases and Queries

Typical uses include logistics dashboards, inbound shipment reconciliation, and dual-UOM audits. A common pattern is to isolate transactions where secondary UOM information is populated:

• Secondary UOM reporting – retrieve receipt lines with a resolved secondary UOM code.
• Parent/child audit – identify return-to-vendor transactions and their originating receipts via PARENT_TRANSACTION_ID.
• Shipment-line rollup – aggregate receipts by SHIPMENT_LINE_ID and currency for logistics tracking.

Sample query:

SELECT TRANSACTION_ID, TRANSACTION_TYPE, TRANSACTION_DATE, SHIPMENT_LINE_ID, QUANTITY, UOM_CODE, PRIMARY_QUANTITY, PRIMARY_UOM_CODE, SECONDARY_QUANTITY, SECONDARY_UOM_CODE
FROM APPS.RCV_FTE_TRANSACTIONS_V
WHERE SECONDARY_UOM_CODE IS NOT NULL
AND TRANSACTION_DATE >= SYSDATE - 30;

Because the view is a union with outer-joined UOM lookups, queries should account for NULL UOM codes when a given UOM identifier is not present in MTL_UNITS_OF_MEASURE. The view is read-only and should be treated as a reporting surface rather than an update target.