Results for “rcv_vrc_txs_vendint_v”

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

Overview

RCV_VRC_TXS_VENDINT_V is an APPS-owned view in the Oracle E-Business Suite Receiving module, catalogued under the PO – Purchasing product family. The ETRM documentation describes the object with the terse annotation "10SC ONLY – Retrofitted," which identifies it as a backward-compatibility construct originally introduced for Release 10SC and subsequently retrofitted forward into the 11i and R12 code lines. In Oracle EBS 12.1.1 and 12.2.2 the view remains VALID and continues to expose receiving transaction data in a flattened, report-friendly shape.

Its functional role is to present vendor-originated and internal receiving transactions together with their shipment, item, supplier, destination and delivery context, so that downstream reports, interfaces and integrations need not navigate the normalized RCV and PO table families individually. Because the view joins transaction records to shipment lines, purchase order delivery schedules, vendors and sites, and HR location and person data, it functions as a single-row-per-receiving-transaction projection suitable for inquiry screens, reconciliation extracts and custom inbound/outbound interfaces. The "VENDINT" suffix reflects its focus on vendor and internal receipt sources, distinguishing it from purely inventory-to-inventory movement views.

Underlying Base Objects

The documented base objects confirm a composition anchored on the Receiving tables, extended by Purchasing, HR and FND reference data. The transactional core is RCV_TRANSACTIONS, joined to RCV_SHIPMENT_LINES and RCV_SHIPMENT_HEADERS for receipt-level attributes, and to RCV_ROUTING_HEADERS for routing context. Purchasing context is supplied through PO_HEADERS_TRX_V, PO_LINES_TRX_V, PO_LINE_LOCATIONS_TRX_V, PO_DISTRIBUTIONS_TRX_V, PO_RELEASES_ALL, PO_REQ_HEADERS_TRX_V, PO_REQ_LINES_TRX_V and PO_JOB_ASSOCIATIONS, with PO_VENDORS and PO_VENDOR_SITES providing supplier identity. Master reference data comes from HR_ALL_ORGANIZATION_UNITS_TL, HR_LOCATIONS_ALL_TL and PER_PEOPLE_F in combination with the HR_GENERAL, HR_PERSON_NAME and HR_SECURITY packages, which enforce organization and person-level security at query time. FND_CURRENCIES_VL, FND_TERRITORIES_TL and GL_DAILY_CONVERSION_TYPES supply currency and territory lookups, PER_JOBS identifies job associations, and FND_GLOBAL is referenced for session context. PO_CLM_INTG_GRP participates in the vendor integration logic. The view text shows RCV_TRANSACTIONS aliased RT joined to RCV_SHIPMENT_LINES aliased RSL, with further outer joins to HR_LOCATIONS_ALL_TL (HRL1, HRL2) and PER_PEOPLE_F (HRE1, HRE2) for ship-to and deliver-to resolution.

Key Columns

The projection exposes the full audit stamp (ROWID, CREATION_DATE, CREATED_BY, LAST_UPDATE_DATE, LAST_UPDATED_BY, LAST_UPDATE_LOGIN) plus ORGANIZATION_ID for multi-org filtering. Transactional keys include TRANSACTION_ID, PARENT_TRANSACTION_ID, INTERFACE_TRANSACTION_ID, SHIPMENT_HEADER_ID, SHIPMENT_LINE_ID, TRANSACTION_TYPE, TRANSACTION_DATE, and the quantity/unit-of-measure triplet TRANSACT_QTY, TRANSACT_UOM and PRIMARY_UOM. Item context is carried by ITEM_ID, ITEM_REV, ITEM_DESC and VENDOR_ITEM_NUM. Destination data is represented by DESTINATION_TYPE_CODE (INVENTORY, WIP or EXPENSE), SHIP_TO_LOCATION_ID with SHIP_TO_LOCATION and SHIP_TO_LOCATION_DESC, plus DELIVER_TO_LOCATION_ID, DELIVER_TO_PERSON_ID and their derived RECEIVER, DELIVER_TO_PERSON and DELIVER_TO_LOCATION columns. Supplier resolution is noteworthy: SUPPLIER_ID and SUPPLIER are derived via DECODE on SOURCE_DOC_CODE, returning the PO vendor for 'PO' rows and the from-organization for internal transfers, while VENDOR_ID and VENDOR_NAME preserve the raw PO vendor values. Other significant columns include PO_HEADER_ID, PO_LINE_ID, PO_LINE_LOCATION_ID, PO_DISTRIBUTION_ID, PO_RELEASE_ID, the WIP identifiers (WIP_ENTITY_ID, WIP_LINE_ID, WIP_OPERATION_SEQ_NUM), DEPARTMENT_CODE, INSPECTION_STATUS_CODE, SUBINVENTORY, LOCATOR_ID, SOURCE_DOC_CODE, SOURCE_DOC_UOM, SOURCE_DOC_QTY, SOURCE_TYPE, VENDOR_LOT_NUM and COMMENTS.

Common Use Cases and Queries

Typical applications include supplier performance and receipt-history reporting, reconciliation of received quantity against ordered quantity at the delivery-schedule level, drill-down inquiries from receipt numbers to PO distributions, and data extraction for warehouse or WMS interfaces. A simple listing of vendor receipts for an operating unit can be written as:

• SELECT transaction_id, transaction_date, transaction_type, transact_qty, transact_uom, item_desc, supplier, supplier_site_id FROM rcv_vrc_txs_vendint_v WHERE organization_id = :p_org_id AND source_type = 'VENDOR' AND transaction_date >= :p_from_date;
• SELECT po_header_id, po_line_id, po_line_location_id, SUM(transact_qty) received_qty FROM rcv_vrc_txs_vendint_v WHERE transaction_type = 'RECEIVE' GROUP BY po_header_id, po_line_id, po_line_location_id;
• SELECT transaction_id, item_id, subinventory, locator_id, deliver_to_person, inspection_status_code FROM rcv_vrc_txs_vendint_v WHERE source_doc_code = 'PO' AND receipt routing context applies;

Because the view relies on HR_SECURITY and FND_GLOBAL, query results are inherently filtered by the operator's organization and security profile; this behavior should be accounted for in concurrent programs and interfaces that execute under a different responsibility. Its retrofitted status also means it should be treated as a compatibility surface, and new development on 12.2.2 should verify whether a current-generation RCV view is preferred before building dependencies upon it.