Search Results root_transaction

Overview

APPS.RCV_FTE_TRANSACTIONS_V is a reporting and integration view in Oracle E-Business Suite 12.1.1 and 12.2.2 that consolidates receiving transaction activity for downstream consumption by Oracle Flow Manufacturing (FTE) and related supply chain modules. The view flattens the transactional detail of RCV_TRANSACTIONS into a denormalized rowset suitable for direct query, interface table population, and analytics. It is defined as a UNION ALL of two distinct result sets: the first captures standard RECEIVE and MATCH transactions, and the second captures RETURN TO VENDOR transactions joined back to their originating parent receipt so that the reversal can be reported with correct parentage context.

The view is significant because it presents both the transaction-level quantity and the three distinct unit-of-measure representations an EBS receiving transaction can carry: the transaction UOM, the primary UOM, and the secondary UOM. This makes it a reliable source for cross-module UOM reconciliation, particularly given the user's search interest in MTL_UNITS_OF_MEASURE.

Underlying Base Objects

The documented base objects are two synonyms: RCV_TRANSACTIONS and MTL_UNITS_OF_MEASURE. RCV_TRANSACTIONS is the driving table and supplies nearly every exposed column, including transaction identifiers, dates, shipment line references, pricing, currency, quality grade, LPN, locator, subinventory, and quantity measures. MTL_UNITS_OF_MEASURE is joined three times—aliased as muom, primary_muom, and secondary_muom—to resolve the internal unit_of_measure identifiers into human-readable uom_code values. All three joins are outer joins (indicated by the (+) syntax), so transactions with a null or unresolved UOM identifier still appear, with the corresponding uom_code returning null rather than dropping the row.

The second UNION ALL branch further references RCV_TRANSACTIONS self-joined to establish the return-to-vendor parent chain, deriving parent_transaction_id, parent_transaction_type, and the reconstructed transaction_type.

Key Columns

• transaction_id — unique identifier of the receiving transaction.
• parent_transaction_id / parent_transaction_type — populated only for the RETURN TO VENDOR branch; null (via TO_NUMBER(NULL) and TO_CHAR(NULL)) for standard receipts and matches.
• transaction_type — normalized type; MATCH is reported as RECEIPT via DECODE.
• transaction_date — effective date of the transaction.
• shipment_line_id — link to the shipment line.
• po_unit_price / currency_code — purchase-order pricing context.
• qc_grade, country_of_origin_code, lpn_id, locator_id, subinventory — quality and physical inventory attributes.
• quantity, uom_code — transaction quantity with its resolved transaction UOM code.
• primary_quantity, primary_uom_code — quantity converted to the item's primary UOM.
• secondary_quantity, secondary_uom_code — quantity in secondary UOM.
• last_update_date, last_updated_by, creation_date, created_by, last_update_login — standard EBS audit columns.

Common Use Cases and Queries

Typical applications include feeding Flow Manufacturing transaction interfaces, reconciling UOM conversions, and auditing return-to-vendor activity against original receipts.

Sample query for UOM reconciliation:

SELECT t.transaction_id, t.transaction_type, t.uom_code, t.uom_code, muom.uom_code, t.quantity, t.primary_uom_code, t.primary_quantity FROM apps.rcv_fte_transactions_v t WHERE t.transaction_date >= :p_start_date AND t.uom_code = :p_uom;

A second scenario isolates return transactions with their parents:

SELECT transaction_id, parent_transaction_id, parent_transaction_type, transaction_date FROM apps.rcv_fte_transactions_v WHERE parent_transaction_id IS NOT NULL;

Because all UOM joins are outer joins, queries joining to MTL_UNITS_OF_MEASURE for descriptions should retain the (+) or ANSI equivalent to preserve transactions lacking a valid UOM reference. Filters should always constrain transaction_date to limit the volume returned from RCV_TRANSACTIONS.