Results for “rcv_view_interface_v”

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

Overview

RCV_VIEW_INTERFACE_V is an APPS-owned database view within the Oracle E-Business Suite Receiving (RCV) module, catalogued under the Purchasing (PO) product family. It is documented in ETRM with a VALID status across both 12.1.1 and 12.2.2, and its description carries the annotation "Retrofitted," indicating it was introduced or regenerated to preserve backward-compatible behavior between release levels. The view exposes the structure and derived attributes of the receiving interface staging area, surfacing rows held in RCV_TRANSACTIONS_INTERFACE alongside descriptive context drawn from shipment, purchasing, inventory, and reference-data sources.

Functionally, the view serves reporting and integration diagnostics rather than transactional processing. It allows implementers to inspect pending, unprocessed, or errored receiving records in a human-readable form by resolving identifiers into meaningful values such as transaction type display names, receipt numbers, line numbers, and item attributes. Because it is a view rather than a table, it is non-updatable in the conventional sense and should be treated as read-only for inquiry purposes.

Underlying Base Objects

The view is defined primarily over RCV_TRANSACTIONS_INTERFACE (RTI), which supplies the core interface transaction columns including INTERFACE_TRANSACTION_ID, TRANSACTION_TYPE, TRANSACTION_DATE, QUANTITY, UNIT_OF_MEASURE, and the full PO and requisition reference set. It is joined to RCV_SHIPMENT_HEADERS and RCV_SHIPMENT_LINES to obtain RECEIPT_NUM, SHIPMENT_NUM, LINE_NUM, PACKING_SLIP, and government-context attributes such as GOVERNMENT_CONTEXT and USSGL_TRANSACTION_CODE.

Item-level detail is drawn from MTL_SYSTEM_ITEMS, yielding control flags including ALLOWED_UNITS_LOOKUP_CODE, SERIAL_NUMBER_CONTROL_CODE, LOT_CONTROL_CODE, and shelf-life attributes. Transaction type presentation comes through PO_LOOKUP_CODES (aliased PLC1). Purchasing context is resolved via PO_HEADERS_TRX_V, PO_LINES_TRX_V, PO_LINE_LOCATIONS_TRX_V, PO_RELEASES_ALL, and PO_REQUISITION_LINES. Organizational and party enrichment is provided by ORG_ORGANIZATION_DEFINITIONS, HR_LOCATIONS_ALL_TL, PER_ALL_PEOPLE_F, PER_JOBS, PO_VENDORS, RCV_ROUTING_HEADERS, and MTL_TRANSACTION_REASONS. Security and session context are applied through FND_GLOBAL, HR_GENERAL, HR_SECURITY, and PO_CLM_INTG_GRP.

Key Columns

• INTERFACE_TRANSACTION_ID / PARENT_TRANSACTION_ID — primary identifier and hierarchical linkage for interface rows.
• TRANSACTION_TYPE / TRANSACTION_TYPE_DSP — internal type code and translated display value from PO_LOOKUP_CODES.
• QUANTITY / UNIT_OF_MEASURE / PRIMARY_UNIT_OF_MEASURE — transaction quantity and associated UOM conversions.
• SHIPMENT_HEADER_ID / SHIPMENT_LINE_ID — links to the shipment records supplying RECEIPT_NUM, SHIPMENT_NUM, and LINE_NUM.
• PO_HEADER_ID, PO_LINE_ID, PO_LINE_LOCATION_ID, PO_DISTRIBUTION_ID, PO_RELEASE_ID, PO_REVISION_NUM — full purchasing document reference chain.
• REQUISITION_LINE_ID, REQ_DISTRIBUTION_ID, REQUISITION_HEADER_ID — requisition-originated sourcing references.
• ITEM_ID, ITEM_DESCRIPTION, CATEGORY_ID, ITEM_REVISION, SERIAL_NUMBER_CC, LOT_CONTROL_CODE — item identity and control attributes.
• TO_ORGANIZATION_ID, SUBINVENTORY, LOCATOR_ID — destination inventory context.
• VENDOR_ID, VENDOR_SITE_ID, DELIVER_TO_PERSON_ID, DELIVER_TO_LOCATION_ID — supplier and delivery routing data.
• PO_UNIT_PRICE, CURRENCY_CODE, CURRENCY_CONVERSION_RATE, CURRENCY_CONVERSION_DATE — valuation and currency conversion detail.
• ATTRIBUTE_CATEGORY, ATTRIBUTE1–15 — descriptive flexfield storage.

Common Use Cases and Queries

The view is most commonly used to audit receiving interface activity, investigate stuck or rejected records, and reconcile receipt transactions against their purchasing source.

• Identify pending interface rows and their transaction types.
• Trace a receipt number back to its PO and requisition references.
• Validate item control attributes before processing.

A representative query is:

SELECT interface_transaction_id, receipt_num, line_num, transaction_type_dsp, transaction_date, quantity, unit_of_measure, item_description, po_header_id, po_line_id FROM rcv_view_interface_v WHERE transaction_date >= SYSDATE - 7 ORDER BY transaction_date DESC;

Additional filtering by TO_ORGANIZATION_ID, VENDOR_ID, or SUBINVENTORY supports operational reporting by warehouse, supplier, or destination inventory. Because the view integrates security packages, returned rows reflect the responsibility-level organizational and location access of the querying user.