Search Results inv_event_27f

Overview

AX_RCV_TRANSACTIONS_V2 is a reporting view belonging to the AX – Global Accounting Engine product family in Oracle E-Business Suite. It is a constrained, presentation-oriented view over receiving transaction data sourced from Oracle Purchasing's RCV_TRANSACTIONS table, cross-referenced against inventory activity in MTL_MATERIAL_TRANSACTIONS. Its principal role is to identify those receiving transactions that are candidates for subledger accounting generation in the Global Accounting Engine (AX), specifically expense-destination receipts and receipts associated with selected inventory transaction types, while excluding transactions already accounted for in the AX Subledger Accounting Engine header table.

The version suffix ("V2") indicates this is a successor definition to an earlier view, and its UNION/MINUS construction reflects an iterative refinement of the selection logic used to feed AX accounting event processing. Because it sits in the AX schema area rather than RCV, it is intended for internal consumption by the Global Accounting Engine rather than general reporting.

Underlying Base Objects

The view is defined over three documented base objects:

• RCV_TRANSACTIONS — the primary driver, aliased RCV. Provides TRANSACTION_ID, TRANSACTION_DATE, and DESTINATION_TYPE_CODE.
• MTL_MATERIAL_TRANSACTIONS — aliased MMT. Joined via RCV_TRANSACTION_ID = TRANSACTION_ID to correlate the receiving transaction to its inventory material movement.
• AX_SLE_HEADERS — aliased SLH. Used in the MINUS branch to subtract transactions that already have a corresponding AX subledger header, matching SLH.REFERENCE_3 to RCV.TRANSACTION_ID.

The transformation is composed of three set operations: a first SELECT for EXPENSE-destination transactions, a second SELECT for transactions tied to inventory transaction types 18, 36, and 71, and a MINUS that removes records already present in AX_SLE_HEADERS for the INV_EVENT_1F, INV_EVENT_27F, and INV_EVENT_29F event classes.

Key Columns

• RCV_TRANSACTION_ID — the RCV_TRANSACTIONS.TRANSACTION_ID value, exposed as a character string via TO_CHAR for use as a textual reference key. This is the linking value to AX_SLE_HEADERS.REFERENCE_3.
• TRANSACTION_DATE — the receipt transaction date from RCV_TRANSACTIONS; used to drive accounting period determination.
• DESTINATION_TYPE_CODE — indicates the destination of the receiving transaction (for example, EXPENSE or INVENTORY). In this view it is both a filter criterion (EXPENSE branch) and a returned attribute.

Common Use Cases and Queries

Typical usage involves auditing or diagnosing which receiving transactions the Global Accounting Engine will pick up for accounting, and confirming that already-processed transactions have been excluded. A representative query returning pending EXPENSE receipt transactions is:

• SELECT RCV_TRANSACTION_ID, TRANSACTION_DATE, DESTINATION_TYPE_CODE FROM AX_RCV_TRANSACTIONS_V2 WHERE DESTINATION_TYPE_CODE = 'EXPENSE' ORDER BY TRANSACTION_DATE;
• SELECT COUNT(*) FROM AX_RCV_TRANSACTIONS_V2 WHERE TRANSACTION_DATE >= :start_date AND TRANSACTION_DATE < :end_date; — to size the accounting population for a period.
• SELECT v.RCV_TRANSACTION_ID FROM AX_RCV_TRANSACTIONS_V2 v WHERE NOT EXISTS (SELECT 1 FROM AX_SLE_HEADERS h WHERE h.REFERENCE_3 = v.RCV_TRANSACTION_ID); — a diagnostic query confirming exclusion from existing AX headers.

In Oracle EBS 12.1.1 and 12.2.2, the view's output reconciles receiving activity in RCV_TRANSACTIONS with inventory movements in MTL_MATERIAL_TRANSACTIONS, making it useful when investigating discrepancies between receipt accounting and inventory accounting in the Global Accounting Engine.