Results for “rcv_vrc_txs_int_v”

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

Overview

RCV_VRC_TXS_INT_V is an Oracle E-Business Suite (EBS) view owned by the APPS schema and categorized under the PO – Purchasing product module. The object metadata carries the description "10SC ONLY - Retrofitted," indicating it was originally introduced to support a specific 10SC (ten-supply-chain or a comparable release-specific) context and later retrofitted into the standard RCV receiving data model. Its status is VALID in both the 12.1.1 and 12.2.2 releases.

The view presents a consolidated, reporting-oriented projection of receiving transaction data drawn principally from RCV_TRANSACTIONS and its related shipment tables. Rather than exposing raw transaction columns alone, it denormalizes the data by joining shipment header and line information, item details, vendor and supplier site attributes, receiving location and receiver person names, and purchase order references. This makes it suitable for reconciliation, audit, and integration reporting where a single row representing a receiving event with descriptive context is more useful than the normalized base tables.

The view exposes a merged quantity column (RT.QUANTITY aliased as TRANSACT_QTY) and merged unit-of-measure columns, while also carrying both SHIP_TO_LOCATION_ID and DELIVER_TO_LOCATION_ID families of attributes, reflecting the dual location semantics central to receiving flows. Because it is a view rather than a table, it inherits the security and performance characteristics of its underlying objects, including any organization-level access restrictions enforced by HR security functions.

Underlying Base Objects

The documented metadata lists a broad set of referenced base objects. The core transactional sources are RCV_TRANSACTIONS (synonym), RCV_SHIPMENT_HEADERS (synonym), and RCV_SHIPMENT_LINES (synonym), which supply the transaction record, header-level receipt source code, and item/line attributes respectively. Receiving routing information is supplied by RCV_ROUTING_HEADERS (view).

Supplier and vendor context comes from PO_VENDORS and PO_VENDOR_SITES (both views), while purchase order linkage is supported through PO_REQUISITION_HEADERS_ALL and PO_REQUISITION_LINES (synonyms). Organizational and person data are resolved via HR_ALL_ORGANIZATION_UNITS_TL, HR_LOCATIONS_ALL_TL, PER_PEOPLE_F (view), and the packages HR_GENERAL, HR_PERSON_NAME, and HR_SECURITY. Currency and territory references use GL_DAILY_CONVERSION_TYPES and FND_TERRITORIES_TL, and FND_GLOBAL (package) provides session context such as the current user and responsibility. This combination of synonyms, views, and packages indicates the view is intended for read-only query and reporting rather than DML.

Key Columns

• TRANSACT_QTY / TRANSACT_UOM: The received or transacted quantity and its unit of measure, derived from RT.QUANTITY and RT.UNIT_OF_MEASURE.
• ITEM_ID, ITEM_REV, ITEM_DESC, VENDOR_ITEM_NUM: Item identity and descriptive attributes sourced from RCV_SHIPMENT_LINES.
• SOURCE_DOC_CODE / SOURCE_DOC_UOM / SOURCE_TYPE: The originating document code (for example PO), its UOM, and the receipt source category (INTERNAL ORDER, INVENTORY, VENDOR).
• SUPPLIER_ID / SUPPLIER / VENDOR_NAME / SUPPLIER_SITE: Supplier resolution that decodes by source document code to select either the vendor or the from-organization.
• SHIP_TO_LOCATION / DELIVER_TO_LOCATION: Location descriptions resolved from HR_LOCATIONS_ALL_TL.
• RECEIVER / DELIVER_TO_PERSON: Person full names obtained via HR_PERSON_NAME, with the receiver resolved using NVL of shipment-line and transaction employee IDs.
• PO_HEADER_ID, PO_LINE_ID, PO_LINE_LOCATION_ID, PO_DISTRIBUTION_ID: Purchase order reference identifiers for drill-through.
• INSPECTION_STATUS_CODE, REASON_ID, COMMENTS, VENDOR_LOT_NUM: Quality, reason, and lot tracking attributes.

Common Use Cases and Queries

Typical scenarios include receiving reconciliation, supplier performance analysis, and integration extracts feeding downstream inventory or WIP processes. Because the view presents descriptive supplier and location names alongside identifiers, it is well suited to ad-hoc reporting without additional joins.

• Listing receipts for a supplier within a date range:

SELECT transaction_id, transaction_date, transaction_type, transact_qty, item_desc, supplier, supplier_site FROM apps.rcv_vrc_txs_int_v WHERE transaction_date BETWEEN :from_date AND :to_date AND supplier = :supplier ORDER BY transaction_date DESC;

• Retrieving receiving activity by item and destination subinventory:

SELECT item_id, item_desc, transact_qty, transact_uom, subinventory, deliver_to_location FROM apps.rcv_vrc_txs_int_v WHERE item_id = :item_id AND subinventory = :subinventory;

• Reconciling purchase order receipts for audit:

SELECT po_header_id, po_line_id, po_line_location_id, transaction_type, transact_qty, receiver, ship_to_location FROM apps.rcv_vrc_txs_int_v WHERE po_header_id = :po_header_id ORDER BY transaction_date;

Queries should always be issued through the APPS schema (or a synonym) and constrained by organization and date to limit the volume returned from the underlying receiving tables.