Results for “rcv_transactions_interface”

AI-generated from documented ETRM metadata — verify critical details on the linked pages.

Overview

RCV_TRANSACTIONS_INTERFACE is the receiving transactions interface table owned by the PO schema in Oracle E-Business Suite 12.1.1 and 12.2.2. It serves as the staging and validation surface through which receipt, delivery, return, transfer, and correction transactions are loaded into Oracle Receiving before they are processed into the permanent receiving tables. Rows are inserted by external systems, legacy conversions, EDI/ASN feeds, mobile receiving applications, or the Receiving Open Interface, and are subsequently validated and consumed by the receiving transaction processor.

Because the table is a high-volume staging structure that fans out to many transactional and master-data parents while carrying its own descriptive and monetary attributes, the heuristic Data Vault classification mined from its foreign key structure is satellite-leaning. In modeling terms, RCV_TRANSACTIONS_INTERFACE is best treated as a satellite-like staging entity keyed by its own surrogate identifier and surrounded by hub-like references to purchase orders, shipments, organizations, and items.

Key Information Stored

The primary key is RCV_TRX_INTERFACE_PK, defined on INTERFACE_TRANSACTION_ID, and the unique index RCV_TRANSACTIONS_INTERFACE_U1 on the same column is the documented business-key candidate. This surrogate identifier is the pivot that downstream child interface tables use to attach lot, serial, LPN, and error rows to a single staged transaction.

• INTERFACE_TRANSACTION_ID — surrogate primary key and the join anchor for all dependent child interface tables.
• TRANSACTION_TYPE, TRANSACTION_DATE, TRANSACTION_STATUS_CODE, PROCESSING_STATUS_CODE — define what the staged transaction is, when it occurred, and where it stands in the validation and processing lifecycle.
• GROUP_ID, INTERFACE_SOURCE_CODE, INTERFACE_SOURCE_LINE_ID — identify the batch, the originating feed, and the source line, enabling grouped processing and reconciliation.
• PO_HEADER_ID, PO_LINE_ID, PO_LINE_LOCATION_ID, PO_DISTRIBUTION_ID, PO_RELEASE_ID — link the staged receipt to its purchasing document, release, shipment line, and accounting distribution.
• ITEM_ID, QUANTITY, UOM_CODE, PRIMARY_QUANTITY, PRIMARY_UNIT_OF_MEASURE — carry the received item and the transactional and primary quantities.
• SHIPMENT_HEADER_ID, SHIPMENT_LINE_ID, RECEIPT_SOURCE_CODE, VENDOR_ID, VENDOR_SITE_ID — tie the transaction to the shipment and supplier context.
• SUBINVENTORY, LOCATOR_ID, DESTINATION_TYPE_CODE, TO_ORGANIZATION_ID, FROM_ORGANIZATION_ID — specify material movement and destination.
• LPN_ID, TRANSFER_LPN_ID, LICENSE_PLATE_NUMBER, LPN_GROUP_ID — support license plate number and warehouse execution handling.
• CURRENCY_CODE, PO_UNIT_PRICE, ACTUAL_COST, TRANSPORTATION_COST, CHARGE_ACCOUNT_ID, TRANSPORTATION_ACCOUNT_ID — hold valuation and accounting information for the receipt.
• INSPECTION_STATUS_CODE, INSPECTION_QUALITY_CODE — capture quality and inspection outcomes for the transaction.
• ATTRIBUTE1 through ATTRIBUTE15 — provide the standard EBS descriptive flexfield extension columns.

Common Use Cases and Queries

The principal operational use case is populating the interface, invoking the Receiving Open Interface, and monitoring PROCESSING_STATUS_CODE and TRANSACTION_STATUS_CODE until each row is consumed or rejected. A typical diagnostic query retrieves pending rows for a batch:

• SELECT interface_transaction_id, transaction_type, processing_status_code, transaction_status_code FROM rcv_transactions_interface WHERE group_id = :group_id;
• SELECT i.interface_transaction_id, i.item_id, i.quantity, i.po_line_location_id FROM rcv_transactions_interface i WHERE i.processing_status_code = 'PENDING' AND i.transaction_date >= :from_date;
• SELECT c.interface_transaction_id, c.lpn_id, c.license_plate_number FROM wms_lpn_contents_interface c WHERE c.interface_transaction_id = :id;

Reporting use cases include reconciling staged quantities against processed RCV_TRANSACTIONS rows, auditing feed accuracy by INTERFACE_SOURCE_CODE, calculating receipt accruals from PO_UNIT_PRICE and ACTUAL_COST, and tracing failed loads through PO_INTERFACE_ERRORS. Because the table retains large volumes, queries should filter on GROUP_ID, REQUEST_ID, or TRANSACTION_DATE to avoid full scans.

Related Objects

The most significant relationships connect the interface row to both its parent business documents and its dependent interface detail tables.

• RCV_TRANSACTIONS — joined on PARENT_TRANSACTION_ID; holds the processed transactions created from the interface.
• PO_LINE_LOCATIONS_ALL and PO_DISTRIBUTIONS_ALL — joined on PO_LINE_LOCATION_ID and PO_DISTRIBUTION_ID for shipment and distribution detail.
• PO_HEADERS_ALL, PO_LINES_ALL, PO_RELEASES_ALL — joined on PO_HEADER_ID, PO_LINE_ID, and PO_RELEASE_ID for purchasing context.
• RCV_SHIPMENT_HEADERS and RCV_SHIPMENT_LINES — joined on SHIPMENT_HEADER_ID and SHIPMENT_LINE_ID.
• MTL_MATERIAL_TRANSACTIONS — linked through INV_TRANSACTION_ID to the inventory transaction ultimately generated.
• WMS_LPN_CONTENTS_INTERFACE — references RCV_TRANSACTIONS_INTERFACE.INTERFACE_TRANSACTION_ID, the object the user searched for, carrying LPN content detail for warehouse execution.
• RCV_LOTS_INTERFACE and RCV_SERIALS_INTERFACE — child tables joined on INTERFACE_TRANSACTION_ID for lot and serial detail.
• PO_INTERFACE_ERRORS — joined on INTERFACE_TRANSACTION_ID, capturing validation and processing errors.
• MTL_ITEM_LOCATIONS, MTL_SECONDARY_INVENTORIES, PO_VENDORS, PO_VENDOR_SITES_ALL — reference data resolved through LOCATOR_ID, SUBINVENTORY, VENDOR_ID, and VENDOR_SITE_ID.