Search Results qa_eres_rcv_trans_interface_v




Overview
Explore in AI Chat

Overview

QA_ERES_RCV_TRANS_INTERFACE_V is an APPS-owned database view in the Oracle E-Business Suite Quality (QA) module. It is documented as the "electronic record view for receiving transaction integration," meaning it exists to expose receiving transaction data in a form suitable for electronic records and integration processing, particularly in support of ERES (Electronic Records and Electronic Signatures) requirements in regulated environments. The view operates on top of the receiving transaction interface, allowing receiving data — purchase order receipts, RMA returns, and related shipment details — to be presented in a denormalized, human-readable format for reporting, validation, and audit purposes. In Oracle EBS 12.1.1 and 12.2.2, this view resides in the APPS schema and is reported as VALID.

Underlying Base Objects

The view is defined over a broad set of base tables, synonyms, and supporting objects spanning multiple EBS modules. Receiving data is sourced principally from RCV_TRANSACTIONS_INTERFACE, RCV_SHIPMENT_HEADERS_V, RCV_SHIPMENT_LINES, and RCV_ROUTING_HEADERS. Purchase order context is drawn from PO_HEADERS_ALL, PO_LINES_ALL, PO_LINE_LOCATIONS_ALL, PO_RELEASES_ALL, PO_DISTRIBUTIONS_ALL, PO_REQUISITION_HEADERS_ALL, PO_REQUISITION_LINES_ALL, and PO_VENDORS. Return/order context comes from OE_ORDER_HEADERS and OE_ORDER_LINES_ALL. Inventory master and location data is supplied by MTL_SYSTEM_ITEMS, MTL_SYSTEM_ITEMS_KFV, MTL_ITEM_LOCATIONS_KFV, MTL_UNITS_OF_MEASURE, MTL_PARAMETERS, MTL_CUSTOMER_ITEMS, and MTL_KANBAN_CARDS. Organization and location descriptions are resolved through HR_ALL_ORGANIZATION_UNITS_TL and HR_LOCATIONS_ALL_TL, while WIP_ENTITIES and WIP_LINES provide work-in-process references. Two PL/SQL packages, QA_ERES_PKG and RCV_PROJECT_GRP, supply derived values, and QA_CUSTOMERS_LOV_V supplies customer names. The view therefore consolidates interface, transactional, and descriptive data into a single queryable surface.

Key Columns

Identity and routing columns include INTERFACE_TRANSACTION_ID and PARENT_TRANSACTION_ID, which anchor each interface record. Organization context is provided by TO_ORGANIZATION_ID, ORGANIZATION_CODE, and the organization NAME. Receipt and shipment references appear as SHIPMENT_HEADER_ID, RECEIPT_NUM, and SHIPMENT_NUM, with TRANSACTION_TYPE and SOURCE_DOCUMENT_CODE identifying the nature of the transaction. ORDER_NUMBER, LINE_NUMBER, ORDERED_QUANTITY, RELEASE_NUM, and PLL.SHIPMENT_NUM describe the originating PO, RMA, or internal order. Item data includes ITEM_ID, CONCATENATED_SEGMENTS, ITEM_REVISION, ITEM_DESCRIPTION, VENDOR_ITEM_NUM, VENDOR_LOT_NUM, and CUSTOMER_ITEM_NUM. Quantities and units are captured through QUANTITY, UNIT_OF_MEASURE, SECONDARY_QUANTITY, and SECONDARY_UNIT_OF_MEASURE. Location and stocking information includes LOCATION_ID, LOCATION_CODE, DESCRIPTION, SUBINVENTORY, LOCATOR_ID, and the concatenated locator segments. Compliance-related columns include HAZARD_CLASS_ID and UN_NUMBER_ID, each accompanied by a package-derived decoded value. Vendor, customer, and project data are exposed through VENDOR_ID, VENDOR_NAME, CUSTOMER_ID, CUSTOMER_NAME, and the project and task numbers returned by RCV_PROJECT_GRP. TRANSACTION_DATE supports chronological reporting and audit trails.

Common Use Cases and Queries

Typical scenarios include auditing receiving transactions for electronic records compliance, validating interface records before processing, and producing receipt traceability reports that link POs, RMAs, items, and locations. The following query retrieves pending interface transactions with receipt context:

  • SELECT interface_transaction_id, receipt_num, source_document_code, order_number, item_description, quantity, unit_of_measure, transaction_date FROM qa_eres_rcv_trans_interface_v WHERE transaction_date >= SYSDATE - 30 ORDER BY transaction_date DESC;
  • SELECT organization_code, transaction_type, COUNT(*) FROM qa_eres_rcv_trans_interface_v GROUP BY organization_code, transaction_type;
  • SELECT receipt_num, vendor_name, item_description, vendor_lot_num, hazard_class_id FROM qa_eres_rcv_trans_interface_v WHERE source_document_code = 'PO';

Because the view joins many transactional tables, queries should be filtered by organization, date range, or transaction type to control execution cost. It is well suited to ERES-driven reporting, receiving reconciliation, and compliance extracts in both 12.1.1 and 12.2.2 environments.