Search Results current_location

Overview

RCV_TRANSACTIONS_V is a reporting and integration view owned by the APPS schema within the PO – Purchasing product of Oracle E-Business Suite. It is documented as retrofitted, meaning it has been carried forward and reconciled across releases, and it is classified as VALID in the ETRM dictionary for both 12.1.1 and 12.2.2. The view consolidates receipt and receiving transaction data held in the RCV_TRANSACTIONS and RCV_SUPPLY tables with descriptive attributes drawn from purchasing, order management, inventory, and party master data. Its principal function is to present a denormalized, human-readable picture of inbound receiving activity so that reports, extracts, and inbound/outbound integrations do not need to reconstruct the many joins between receipt headers, shipment lines, purchase orders, and returns themselves.

Because it exposes transaction-level rows keyed by RCV_TRANSACTION_ID and enriched with order numbers, item attributes, locator and subinventory control flags, and unit-of-measure classes, RCV_TRANSACTIONS_V is widely used in receiving reconciliation, vendor performance reporting, and supply chain extracts. A user searching for "current_location" will typically be looking for the location-related columns that flow from the inventory item definition and receipt routing information rather than a single column literally named CURRENT_LOCATION.

Underlying Base Objects

The view text is defined over a long chain of base objects. The core receiving facts come from RCV_TRANSACTIONS (a synonym over the transaction table) and RCV_SUPPLY, which supplies FROM_ORGANIZATION_ID and TO_ORGANIZATION_ID, PO_HEADER_ID, PO_LINE_ID, PO_RELEASE_ID, SUPPLY_SOURCE_ID, and ITEM_ID. Header information is joined through RCV_SHIPMENT_HEADERS (receipt source, vendor, shipment number), while shipment lines supply line-level attributes. Purchase order context is drawn from PO_HEADERS_TRX_V, PO_LINES_TRX_V, PO_LINE_LOCATIONS_ALL, PO_LINES, PO_DISTRIBUTIONS_ALL, PO_RELEASES_ALL, and PO_VENDORS. Order management return data comes from OE_ORDER_HEADERS_ALL, OE_ORDER_LINES_ALL, OE_TRANSACTION_TYPES_ALL, and OE_TRANSACTION_TYPES_TL.

Inventory master data is retrieved from MTL_SYSTEM_ITEMS, MTL_UNITS_OF_MEASURE, MTL_CUSTOMER_ITEMS, and MTL_TRANSACTION_REASONS. Party and location descriptions are resolved through HZ_PARTIES, HZ_CUST_ACCOUNTS, HR_LOCATIONS_ALL_TL, and HR_ALL_ORGANIZATION_UNITS_TL. Lookup decoding uses PO_LOOKUP_CODES, GL_DAILY_CONVERSION_TYPES, RCV_ROUTING_HEADERS, FINANCIALS_SYSTEM_PARAMS_ALL, and the FND_GLOBAL package. DUAL anchors the SELECT list.

Key Columns

• RCV_TRANSACTION_ID / TRANSACTION_DATE / TRANSACTION_TYPE — primary transaction identity, date, and type, with TRANSACTION_TYPE_DSP providing the displayed value.
• SOURCE_DOCUMENT_CODE / RECEIPT_SOURCE_CODE / ORDER_NUMBER / LINE_NUMBER — decoded document origin (PO, RMA, or shipment) and the corresponding order and line references.
• QUANTITY, UNIT_OF_MEASURE, PRIMARY_QUANTITY, PRIMARY_UOM, PRIMARY_UOM_CLASS, UOM_CLASS — transaction and primary quantities with their unit-of-measure classifications.
• PO_HEADER_ID, PO_LINE_ID, PO_RELEASE_ID, PO_REVISION_NUM, PO_RELEASE_NUMBER, PO_UNIT_PRICE — purchasing document linkage and pricing.
• ITEM_ID, ITEM_LOCATOR_CONTROL, RESTRICT_LOCATORS_CODE, RESTRICT_SUBINVENTORIES_CODE, ITEM_ALLOWED_UNITS_LOOKUP_CODE — item master controls that govern where material may be received, effectively the location-control indicators most relevant to a "current_location" style query.
• SHELF_LIFE_CODE, SHELF_LIFE_DAYS — shelf-life handling for the received item.
• VENDOR_ID, VENDOR_SITE_ID, SOURCE — supplier and source descriptions, with SOURCE resolved differently for PO, RMA, and other receipt sources.
• CATEGORY_ID, SUPPLY_SOURCE_ID, FROM_ORGANIZATION_ID, TO_ORGANIZATION_ID — category and organizational routing context.

Common Use Cases and Queries

Typical scenarios include reconciling received quantities against purchase order lines, extracting receipt history by vendor, and validating item routing and locator restrictions before put-away. The following query returns recent receiving activity with item location controls:

SELECT rcv_transaction_id,
       transaction_date,
       transaction_type,
       order_number,
       line_number,
       item_id,
       quantity,
       unit_of_measure,
       item_locator_control,
       restrict_locators_code,
       restrict_subinventories_code,
       to_organization_id
FROM   apps.rcv_transactions_v
WHERE  transaction_date >= SYSDATE - 30
ORDER  BY transaction_date DESC;

A location-focused variant filters on the item's locator and subinventory control flags, since the view exposes control indicators rather than a single current location column:

SELECT rcv_transaction_id,
       item_id,
       to_organization_id,
       item_locator_control,
       restrict_locators_code,
       restrict_subinventories_code,
       supply_source_id
FROM   apps.rcv_transactions_v
WHERE  item_locator_control = 2
AND    restrict_locators_code = 'Y';

For vendor analysis, SOURCE, VENDOR_ID, and ORDER_NUMBER can be aggregated with QUANTITY to produce supplier receipt summaries. Because the view depends on PO_HEADERS_TRX_V, PO_LINES_TRX_V, and PO_LOOKUP_CODES, performance is best when queries are restricted by transaction date or organization so that the underlying joins are driven from the RCV_TRANSACTIONS and RCV_SUPPLY base tables.