Search Results source_document_code

Overview

The view AX_RCV_TRANSACTIONS_V1 belongs to the AX - Global Accounting Engine product within Oracle E-Business Suite. It exposes a duplicate representation of a defined subset of columns from the base receiving table RCV_TRANSACTIONS. Its purpose is to provide the Global Accounting Engine with a controlled projection of receipt and receiving transaction data, shielding downstream accounting and integration logic from the full, wide column set of the underlying transaction table. The view is documented in ETRM as not implemented in the reference database, meaning the metadata describes the intended definition rather than an object present in every environment.

Because the view is defined as a straight column list over RCV_TRANSACTIONS, it is read-only in practical terms: no independent storage, no aggregation, and no filtering logic. All selectivity, joins, and filtering are pushed to the underlying base table at runtime.

Underlying Base Objects

The sole documented base object is RCV_TRANSACTIONS. The view text is a direct SELECT of named columns from that table, with no joins, unions, or derived expressions. ETRM documentation lists no referenced base objects beyond this, and the view is described as a duplicate of a subset of RCV_TRANSACTIONS columns rather than a transformation of them.

Consequently, row counts, data types, and NULL behavior mirror RCV_TRANSACTIONS exactly. Any DML against the base table is immediately visible through the view, since no materialization exists. The view carries no triggers, constraints, or indexes of its own; performance therefore depends entirely on the indexes defined on RCV_TRANSACTIONS, principally those on TRANSACTION_ID and the foreign-key columns.

Key Columns

The view exposes the principal identity, auditing, and transactional columns of receiving activity. Notable columns include:

• TRANSACTION_ID - primary identifier of the receiving transaction; the principal join key to related receiving and inventory tables.
• INTERFACE_SOURCE_CODE and INTERFACE_SOURCE_LINE_ID - identify the source system and line that originated the transaction, central to inbound interface reconciliation.
• INTERFACE_TRANSACTION_ID and GROUP_ID - correlate the transaction back to interface control and grouping identifiers.
• TRANSACTION_TYPE and TRANSACTION_DATE - classify the event (for example receipt, delivery, return) and timestamp it.
• SHIPMENT_HEADER_ID and SHIPMENT_LINE_ID - tie the transaction to the shipment structure.
• INV_TRANSACTION_ID - links the receiving event to its inventory transaction counterpart.
• QUANTITY, PRIMARY_QUANTITY, UOM_CODE, and UNIT_OF_MEASURE - quantities and units of measure for the movement.
• SOURCE_DOCUMENT_CODE, SOURCE_DOC_QUANTITY, and SOURCE_DOC_UNIT_OF_MEASURE - originating document attribution.
• INSPECTION_STATUS_CODE, ACCRUAL_STATUS_CODE, and INVOICE_STATUS_CODE - status flags relevant to accounting and accrual processing.
• ORGANIZATION_ID, SUBINVENTORY, and LOCATOR_ID - inventory destination context.
• ATTRIBUTE1 through ATTRIBUTE15 and ATTRIBUTE_CATEGORY - the standard descriptive flexfield columns.
• Audit columns - CREATION_DATE, CREATED_BY, LAST_UPDATE_DATE, LAST_UPDATED_BY, LAST_UPDATE_LOGIN, REQUEST_ID, PROGRAM_ID, and PROGRAM_APPLICATION_ID.

Common Use Cases and Queries

The view is typically consumed for accounting reconciliation, interface troubleshooting, and receiving reporting where the full RCV_TRANSACTIONS column set is unnecessary. A representative query retrieving interface-sourced receipts is:

SELECT transaction_id, transaction_type, transaction_date, interface_source_code, interface_source_line_id, quantity, uom_code FROM ax_rcv_transactions_v1 WHERE interface_source_code IS NOT NULL AND organization_id = :org_id ORDER BY transaction_date DESC;

Because the view filters nothing, adding predicates on TRANSACTION_DATE, ORGANIZATION_ID, or INTERFACE_SOURCE_CODE allows the optimizer to use the base table indexes. Where ETRM records the object as not implemented, DBAs should confirm its existence before relying on it and otherwise query RCV_TRANSACTIONS directly using the identical column list.