Search Results rcv_enter_receipts_internal_v




Overview
Explore in AI Chat

Overview

APPS.RCV_ENTER_RECEIPTS_INTERNAL_V is a Purchasing (PO) module view within the Oracle E-Business Suite Receiving (RCV) schema. The ETRM metadata classifies it with the description "10SC ONLY - Retrofitted," indicating it is a customer-specific or localized retrofit object rather than a core, generally-shipped view. Its status is VALID, and it is owned by the APPS schema in both 12.1.1 and 12.2.2.

The view presents a wide, denormalized row set that mirrors the field layout of the Enter Receipts form, exposing purchase order, requisition, shipment, shipment-line, item, and receiving-control attributes in a single queryable surface. It is intended for internal consumption — typically by the Enter Receipts form logic, by concurrent programs, or by inbound Application Service Number (ASN) and receiving integrations that must resolve receipt entry data without navigating multiple base tables. Because the view name carries the _INTERNAL_ designator, it is not part of the documented public API contract and should be treated as subject to change across patches and upgrades.

Underlying Base Objects

Per the documented ETRM metadata for 12.2.2, the view is defined over four referenced objects:

  • RCV_ENTER_RECEIPTS_INT_REQ_V (VIEW) — supplies requisition-sourced receipt entry lines.
  • RCV_ENTER_RECEIPTS_INVENTORY_V (VIEW) — supplies inventory-sourced receipt entry lines.
  • HR_GENERAL (PACKAGE) — resolves personnel, business group, and security attributes (e.g., deliver-to person, operating unit context).
  • HR_SECURITY (PACKAGE) — applies HR organizational security to restrict rows to the user's authorized hierarchy.

In practice this view acts as a union/aggregation layer: the two RCV_ENTER_RECEIPTS_*_V views provide the PO- and inventory-sourced line populations, while the two HR packages supply security predicates and person/general lookups. The underlying transactional data ultimately traces to PO headers, lines, and shipments, RCV shipment headers and lines, and item master attributes, but the documented dependency set is limited to the objects listed above.

Key Columns

The column list is extensive. Significant columns include:

Common Use Cases and Queries

Typical uses include populating receipt entry forms, driving ASN-based receiving integrations, and building custom receiving reports. A representative query filtering on the searched column ASN_TYPE is shown below.

SELECT po_number,
       po_line_number,
       rcv_shipment_number,
       item_number,
       ordered_qty,
       asn_type,
       bill_of_lading,
       freight_carrier_code,
       shipped_date
  FROM apps.rcv_enter_receipts_internal_v
 WHERE asn_type IS NOT NULL
   AND source_type_code = 'VENDOR'
 ORDER BY shipped_date DESC;

To reconcile expected versus received quantities for a shipment, the view can be joined or filtered on RCV_SHIPMENT_HEADER_ID and RCV_SHIPMENT_LINE_ID. Because row-level security is inherited through HR_SECURITY, queries executed under a restricted responsibility return only rows for authorized organizations. Given the "10SC ONLY - Retrofitted" designation, direct dependencies on this view in custom code should be validated against the standard supported API (RCV_ENTER_RECEIPTS_API) before promotion between 12.1.1 and 12.2.2 environments.