Results for “rcv_returns_v”

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

Overview

RCV_RETURNS_V is an APPS-owned database view in Oracle E-Business Suite Release 12.1.1 and 12.2.2, classified under the PO – Purchasing product family. Per the ETRM metadata, its status is VALID and it is described as "Retrofitted," indicating that the object was re-pointed against the R12 transactional data model, most likely from an earlier 11i definition. It exposes return-to-vendor, RMA, and related receiving return transactions for reporting and integration purposes.

The view presents return transaction records sourced from the receiving transaction table (RCV_TRANSACTIONS) rather than direct inserts, and is designed to be a reporting-friendly projection. Because it joins to purchasing, receiving, WIP, HR, and OE objects, it allows consumers to retrieve a return transaction together with pricing, vendor, routing, and destination context in a single query without writing the join logic themselves.

The user search term shelf_days does not appear in the documented view text or column list. There is no SHELF_DAYS column in the ETRM metadata for RCV_RETURNS_V; shelf-life calculation in EBS is normally handled through inventory lot attributes (for example MTL_LOT_NUMBERS.SHELF_LIFE_CODE and expiry date columns) rather than this view. Any shelf-life reporting requirement would therefore need to join RCV_RETURNS_V back to the relevant MTL lot/attribute tables on organization, item, and lot.

Underlying Base Objects

The documented referenced base objects for 12.2.2 span nine functional areas:

• Receiving: RCV_TRANSACTIONS, RCV_TRANSACTIONS_INTERFACE, RCV_SHIPMENT_HEADERS, RCV_SHIPMENT_LINES, RCV_SUPPLY, RCV_ROUTING_HEADERS (view).
• Purchasing: PO_HEADERS_TRX_V, PO_LINES_TRX_V, PO_LINE_LOCATIONS_TRX_V, PO_DISTRIBUTIONS_TRX_V (all views), PO_RELEASES_ALL, PO_REQUISITION_LINES, PO_VENDORS (view), PO_CLM_INTG_GRP (package).
• Inventory: MTL_SYSTEM_ITEMS.
• Order Management: OE_ORDER_HEADERS_ALL, OE_ORDER_LINES_ALL, OE_TRANSACTION_TYPES_ALL, OE_TRANSACTION_TYPES_TL.
• Work in Process: WIP_DISCRETE_JOBS, WIP_ENTITIES.
• Human Resources: HR_LOCATIONS_ALL_TL.
• Financials: FINANCIALS_SYSTEM_PARAMS_ALL.

Numerous base objects are synonyms rather than tables or views in the APPS schema. The distinction matters for debugging: a synonym resolves to the owning application schema, so invalid view compilation typically traces to a change in one of the underlying views such as PO_VENDORS, PO_LINES_TRX_V, or RCV_ROUTING_HEADERS.

Key Columns

The view exposes a broad transaction record plus join-derived attributes:

• Identity and audit: TRANSACTION_ID, TRANSACTION_TYPE, TRANSACTION_DATE, CREATION_DATE, LAST_UPDATE_DATE, CREATED_BY, LAST_UPDATED_BY, LAST_UPDATE_LOGIN.
• Quantity and UOM: QUANTITY, PRIMARY_QUANTITY, UNIT_OF_MEASURE, PRIMARY_UNIT_OF_MEASURE, UOM_CODE.
• Source and destination: SOURCE_DOCUMENT_CODE, DESTINATION_TYPE_CODE, INTERFACE_SOURCE_CODE, INTERFACE_SOURCE_LINE_ID, INV_TRANSACTION_ID.
• Purchase order context: PO_HEADER_ID, PO_LINE_ID, PO_LINE_LOCATION_ID, PO_DISTRIBUTION_ID, PO_RELEASE_ID, PO_REVISION_NUM, REQUISITION_LINE_ID.
• Pricing: PO_UNIT_PRICE, derived via NVL(PLL.PRICE_OVERRIDE, PL.UNIT_PRICE), plus CURRENCY_CODE, CURRENCY_CONVERSION_TYPE, CURRENCY_CONVERSION_RATE, CURRENCY_CONVERSION_DATE.
• Vendor: VENDOR_ID and VENDOR are suppressed for RMA-source returns via the DECODE on SOURCE_DOCUMENT_CODE; VENDOR_SITE_ID is retained.
• Location: LOCATION_ID is resolved with a DECODE that returns the receiving location for RECEIVING destinations, otherwise DELIVER_TO_LOCATION_ID; LOCATION_CODE comes from HR_LOCATIONS_ALL_TL.
• Workflow/status flags: RECEIPT_EXCEPTION_FLAG, INSPECTION_STATUS_CODE, ACCRUAL_STATUS_CODE, INSPECTION_QUALITY_CODE, USER_ENTERED_FLAG.
• WIP context: WIP_ENTITY_ID, WIP_LINE_ID, WIP_REPETITIVE_SCHEDULE_ID, WIP_OPERATION_SEQ_NUM, WIP_RESOURCE_SEQ_NUM, BOM_RESOURCE_ID, SUBSTITUTE_UNORDERED_CODE.
• Descriptive attributes: VENDOR_LOT_NUM, RMA_REFERENCE, COMMENTS, ATTRIBUTE_CATEGORY, and ATTRIBUTE1 through ATTRIBUTE15.

Common Use Cases and Queries

The view supports return analysis, vendor return reconciliation, and receiving exception reporting. A typical query retrieves returns against a purchase order with derived pricing and vendor context:

• Return transactions by date range, filtered on TRANSACTION_TYPE and TRANSACTION_DATE, joined to PO_HEADERS for segmentation.
• Price variance reporting using PO_UNIT_PRICE against CURRENCY_CONVERSION_RATE for foreign-currency POs.
• RMA versus vendor-return separation using SOURCE_DOCUMENT_CODE.
• Shelf-life analysis by joining to MTL_LOT_NUMBERS on ORGANIZATION_ID and item, since shelf-days logic is not exposed by this view.
• Exception reporting on RECEIPT_EXCEPTION_FLAG and INSPECTION_STATUS_CODE.

SELECT r.transaction_id, r.transaction_date, r.transaction_type,
       r.quantity, r.uom_code, r.po_unit_price, r.vendor,
       r.location_code, r.rma_reference
FROM   apps.rcv_returns_v r
WHERE  r.transaction_date >= :p_from_date
AND    r.transaction_date <  :p_to_date
AND    r.organization_id = :p_org_id;

Because the object is a view rather than a table, no direct DML is permitted; returns must be created through standard receiving processes or the interface tables referenced in the definition.