Search Results shipment_line_status_code




Overview
Explore in AI Chat

Overview

APPS.FV_RECEIPT_MASTER_V is a reporting view in the Oracle E-Business Suite Applications (APPS) schema, identified by the FND Design Data object FV.FV_RECEIPT_MASTER_V. In the context of Oracle EBS 12.1.1 and 12.2.2, it exposes a consolidated, denormalized projection of receipt and shipment information originating from the Purchasing and Receiving modules. The view joins shipment header, shipment line, purchasing document, and transaction data to present a single row per shipment line, enriched with supplier, item, receipt, and packing information.

Because it is a view rather than a base table, it is intended for query and reporting access rather than direct transactional manipulation. Oracle designates the object as for internal use, meaning supported access is expected through standard Oracle Applications programs, and customers should treat the view as a read-oriented reporting surface. The view is notably referenced by APPS.FV_CROSS_DOC_REF, which confirms its role within the federal financials cross-document reference processing used by the FV product family.

Underlying Base Objects

Per the documented dependency information, APPS.FV_RECEIPT_MASTER_V is defined over five referenced base objects, each presented to the view through synonyms:

  • PO_HEADERS — purchasing document headers supplying supplier and document context.
  • PO_LINE_LOCATIONS_ALL — purchase order line and shipment schedules, providing line location identifiers and ship-to context.
  • RCV_SHIPMENT_HEADERS — receiving shipment headers, furnishing receipt header attributes such as receipt number and receipt date.
  • RCV_SHIPMENT_LINES — receiving shipment lines, the principal source of line-level quantity, status, and item detail.
  • RCV_TRANSACTIONS — receiving transactions, contributing receipt transaction information that drives quantity received and receipt status.

The joins across these objects allow the view to combine the procurement document chain (PO_HEADERS, PO_LINE_LOCATIONS_ALL) with the receiving chain (RCV_SHIPMENT_HEADERS, RCV_SHIPMENT_LINES, RCV_TRANSACTIONS), producing a receipt-centric master record keyed by shipment header and shipment line identifiers.

Key Columns

The view exposes fifteen columns. The primary identifiers are ORG_ID (operating unit), SHIPMENT_HEADER_ID, SHIPMENT_LINE_ID, and LINE_LOCATION_ID, which together support joins back to receiving and purchasing tables. VENDOR_ID and VENDOR_SITE_ID identify the source supplier and supplier site.

Receipt attributes include RECEIPT_NUM, RECEIPT_DATE, and PACKING_SLIP. Item and quantity information is provided through ITEM_DESCRIPTION, QUANTITY_RECEIVED, and UNIT_OF_MEASURE. Shipment tracking columns include SHIPMENT_NUM, SHIP_DATE, and the central status column SHIPMENT_LINE_STATUS_CODE, a VARCHAR2(25) field described in the metadata as the receipt status of the shipment line. For users searching on shipment_line_status_code, this is the authoritative column for determining whether a receipt line is, for example, expected, partially received, fully received, or cancelled, as maintained by the receiving transaction logic.

Common Use Cases and Queries

Typical uses include receipt status reporting, supplier receipt reconciliation, and cross-document reference processing. A representative query returns all receipt lines for an operating unit:

  • SELECT shipment_line_id, receipt_num, receipt_date, vendor_id, item_description, shipment_line_status_code, quantity_received FROM apps.fv_receipt_master_v WHERE org_id = :org_id;
  • Filtering by status: SELECT receipt_num, shipment_line_status_code FROM apps.fv_receipt_master_v WHERE shipment_line_status_code = 'EXPECTED';
  • Joining to purchasing: SELECT v.receipt_num, v.item_description, v.quantity_received FROM apps.fv_receipt_master_v v WHERE v.shipment_line_id = :line_id;

Because status values are derived from receiving transaction processing, queries should account for the standard RCV status code set. As the object is Oracle internal use only, custom code should limit itself to read access.