Search Results fv_receipt_master_v




Overview
Explore in AI Chat

Overview

The view APPS.FV_RECEIPT_MASTER_V is a Federal Financials (FV) reporting entity owned by the APPS schema and documented as VALID in Oracle E-Business Suite 12.1.1 and 12.2.2. Its stated purpose is to retrieve receipt details for the form Document Cross-Reference, a federal accounting inquiry that allows users to trace supplier shipment and receipt activity against the associated purchasing document. Because the federal accounting model demands a verifiable audit trail between goods received and the obligations they liquidate, this view consolidates shipment header, shipment line, purchase order header, and purchase order line location attributes into a single denormalized projection suitable for both form-driven inquiry and ad hoc reporting.

The view is read-only and exposes no maintenance capability; it functions purely as a query surface for reporting, form LOV population, and integration extracts. Because it joins several high-volume RCV and PO tables, it should be treated as an inquiry object rather than a transactional interface.

Underlying Base Objects

Per the ETRM 12.2.2 metadata, the view is defined over five referenced base objects, all presented through APPS synonyms: RCV_SHIPMENT_HEADERS, RCV_SHIPMENT_LINES, RCV_TRANSACTIONS, PO_LINE_LOCATIONS_ALL, and PO_HEADERS. The join topology is a classic receiving chain: RCV_SHIPMENT_HEADERS joins to RCV_SHIPMENT_LINES on SHIPMENT_HEADER_ID; RCV_SHIPMENT_LINES joins to PO_LINE_LOCATIONS_ALL on PO_LINE_LOCATION_ID; PO_LINE_LOCATIONS_ALL joins to PO_HEADERS on PO_HEADER_ID; and RCV_TRANSACTIONS joins to RCV_SHIPMENT_LINES on SHIPMENT_LINE_ID. The SELECT DISTINCT clause suppresses duplication introduced by the RCV_TRANSACTIONS join, since a shipment line may carry multiple transaction rows.

Key Columns

  • ORG_ID — operating unit identifier sourced from PO_HEADERS, the primary Multi-Org security discriminator.
  • SHIPMENT_HEADER_ID / SHIPMENT_LINE_ID / LINE_LOCATION_ID — surrogate keys linking back to the receiving and purchasing entities.
  • VENDOR_ID / VENDOR_SITE_ID — supplier and supplier site identifiers.
  • RECEIPT_NUM / RECEIPT_DATE — receipt number and the shipment header creation date, aliased as the receipt date.
  • QUANTITY_RECEIVED / UNIT_OF_MEASURE / ITEM_DESCRIPTION — line-level receipt quantity, UOM, and item description.
  • SHIPMENT_LINE_STATUS_CODE — current disposition of the receipt line.
  • PACKING_SLIP — derived via DECODE(NVL(RSL.PACKING_SLIP,'1'),'1',RSH.PACKING_SLIP,RSL.PACKING_SLIP), meaning the line-level packing slip value is used when present, otherwise the header-level value is substituted.
  • SHIPMENT_NUM / SHIP_DATE — shipment number and the shipped date from the shipment header, alias of SHIPPED_DATE.

Common Use Cases and Queries

A frequent request is locating receipts by packing slip, which explains the "packing_slip" search term. Because the view already resolves the header/line packing slip precedence, a direct predicate is sufficient:

  • SELECT receipt_num, receipt_date, packing_slip, shipment_num, quantity_received FROM apps.fv_receipt_master_v WHERE packing_slip = 'PS-10045';
  • SELECT receipt_num, item_description, quantity_received, unit_of_measure FROM apps.fv_receipt_master_v WHERE org_id = :p_org_id AND receipt_date BETWEEN :p_from AND :p_to;
  • Document cross-reference inquiry filtering by shipment line status to isolate fully received versus partially received lines for federal reconciliation.

Reporting joins typically link SHIPMENT_LINE_ID back to RCV_TRANSACTIONS for transaction-level drill-down, or to PO_LINE_LOCATIONS_ALL to recover accounting distributions. Because the view returns only received shipments already matched to a purchase order, receipts against inventory-only or inter-org transfers are excluded.