Search Results asn_type




Overview
Explore in AI Chat

Overview

APPS.RCV_ENTER_RECEIPTS_INTERNAL_V is a consolidated Oracle E-Business Suite view that exposes the data set used by the Enter Receipts form within Oracle Receiving (RCV). It presents one row per eligible receiving line — combining purchase order, requisition, shipment, vendor, item, and receipt header information — so that receiving personnel and downstream processes can identify what is available to receive, inspect, or match. In practice, the view functions as a union-style reporting and integration surface that merges internally sourced receipts (PO and requisition-based) with inventory-sourced receipts, while delegating some categorization logic to helper views.

The view is particulary relevant to users searching on asn_type, since ASN_TYPE is one of its exposed columns. ASN_TYPE identifies whether an advance shipping notice exists for the shipment (advanced versus standard shipment notification), which is essential for suppliers operating with ASN/ASBN workflows and for receiving organizations that must distinguish ASN-driven receipts from manual ones. Because the view is a read-only construct, it supports querying, form rendering, and integration extraction, but not direct DML.

Underlying Base Objects

The documented dependencies are:

  • RCV_ENTER_RECEIPTS_INTP_REQ_V — the requisition/internal requisition branch of the Enter Receipts data set.
  • RCV_ENTER_RECEIPTS_INVENTORY_V — the inventory-sourced branch of the Enter Receipts data set.
  • HR_GENERAL (package) — used for session and operating-unit context, including user and responsibility-specific security evaluation.
  • HR_SECURITY (package) — enforces organizational (HR) security so that only rows the current user is authorized to see are returned.

This structure means RCV_ENTER_RECEIPTS_INTERNAL_V is a union-style wrapper: internal and inventory receipt rows are supplied by the two subordinate views, while HR_GENERAL and HR_SECURITY supply the runtime security and context predicates. Any functional change to the two child views propagates directly to this parent view, so incremental patches to RCV can alter its column list and behavior.

Key Columns

The view projects a very wide column list. Notable groups include:

Common Use Cases and Queries

Typical situations include investigating outstanding receipts, validating ASN versus manual shipments, and building supplier performance extracts. A focused query on ASN type might return only ASN-flavored shipment lines:

SELECT PO_NUMBER, RCV_SHIPMENT_NUMBER, ASN_TYPE, VENDOR_ID, ITEM_NUMBER, ORDERED_QTY, SHIPPED_DATE, FREIGHT_CARRIER_CODE FROM APPS.RCV_ENTER_RECEIPTS_INTERNAL_V WHERE ASN_TYPE IS NOT NULL;

To review pending receipts by organization and date:

SELECT TO_ORGANIZATION_ID, PO_NUMBER, ITEM_NUMBER, EXPECTED_RECEIPT_DATE, NEED_BY_DATE, RECEIPT_REQUIRED_FLAG FROM APPS.RCV_ENTER_RECEIPTS_INTERNAL_V WHERE TO_ORGANIZATION_ID = :org_id AND EXPECTED_RECEIPT_DATE BETWEEN :start_date AND :end_date;

To inspect inspection-required PO lines for a given supplier:

SELECT PO_NUMBER, PO_LINE_NUMBER, PO_SHIPMENT_NUMBER, ITEM_NUMBER, INSPECTION_REQUIRED_FLAG, UNIT_PRICE, CURRENCY_CODE FROM APPS.RCV_ENTER_RECEIPTS_INTERNAL_V WHERE VENDOR_ID = :vendor_id AND INSPECTION_REQUIRED_FLAG = 'Y';

Because HR_SECURITY is invoked by the view, results are automatically filtered to the operating units and organizations the querying responsibility is permitted to access, which makes the view suitable for multi-org reporting without additional security predicates.