Search Results oe_order_line_num




Overview
Explore in AI Chat

Overview

APPS.RCV_ENTER_RECEIPTS_SUP_INT_V is an Oracle E-Business Suite view residing in the Receiving (RCV) module. It is designed to support the Receiving Open Interface and the Enter Receipts user interface, exposing a consolidated projection of receipt-related data across multiple receiving entry paths. The view name suffix "SUP_INT_V" indicates its role as a Supplier/Internal-facing integration source, providing the flattened record structure that downstream processes and forms consume when creating or validating receipt records.

Its principal purpose is to unify data originating from three distinct receiving scenarios — Advance Shipment Notices (ASN), internal requisitions, and inventory transfers — with data from standard purchase order receipts. This enables the Enter Receipts form and the Receiving Open Interface to operate against a single query surface rather than querying each source independently. For the user searching on "rcv_shipment_number," this view is directly relevant because RCV_SHIPMENT_NUMBER is one of its exposed columns, derived from the shipment header associated with each receipt line.

The view carries a cost-based transformation hint using opt_param('_optimizer_cost_based_transformation','off'), indicating that the optimizer is intentionally steered away from certain cost-based transformations, likely to preserve predictable execution plans for this composite union-style structure.

Underlying Base Objects

The ETRM metadata documents the following referenced base objects:

The view consequently behaves as a consolidation layer over four entry views, with package calls supplying security filtering and purchasing integration context at runtime.

Key Columns

The view exposes over one hundred columns. The most significant groupings are:

Common Use Cases and Queries

Typical uses include reporting on receipts awaiting entry, validating shipment contents for the Receiving Open Interface, and linking purchasing and requisition data to shipment records.

To locate receipts by shipment number:

  • SELECT rcv_shipment_number, po_number, item_number, ordered_qty, receipt_source_code FROM apps.rcv_enter_receipts_sup_int_v WHERE rcv_shipment_number = :shipment_number;

To list all open receipts for a purchase order by source type:

  • SELECT receipt_source_code, po_number, po_line_number, item_number, expected_receipt_date FROM apps.rcv_enter_receipts_sup_int_v WHERE po_number = :po_number AND NVL(closed_code,'OPEN') <> 'CLOSED';

To identify ASN-originated shipments with logistics detail:

  • SELECT rcv_shipment_number, asn_type, bill_of_lading, freight_carrier_code, shipped_date FROM apps.rcv_enter_receipts_sup_int_v WHERE asn_type IS NOT NULL;

Because row-level security is applied via HR_SECURITY and HR_GENERAL, results are automatically restricted to organizations the user is authorized to access. Queries should therefore be executed in the context of the requesting responsibility. For integration extracts, the view is commonly filtered on SOURCE_TYPE_CODE or ORDER_TYPE_CODE to isolate purchase order versus internal requisition versus inventory transfer populations.