Results for “rcv_enter_receipts_asn_v”

AI-generated from documented ETRM metadata — verify critical details on the linked pages.

Overview

The RCV_ENTER_RECEIPTS_ASN_V view is an APPS-owned database object within the Oracle E-Business Suite Receiving (RCV) module, which falls under the Purchasing (PO) product family. Its documented description in the ETRM metadata is terse — "10SC ONLY - Retrofitted" — indicating that the object was introduced or carried forward to support a specific compliance or industry-vertical configuration rather than as part of the standard, universally deployed Receiving schema. The name itself (Receive Receipts ASN) signals its purpose: it presents outstanding shipment lines associated with Advance Shipment Notices (ASNs) in a shape suitable for the "Enter Receipts" form and for downstream inquiry or integration logic.

Functionally, the view conforms to the same projected column layout used by the corollary manual-receipt views (for example RCV_ENTER_RECEIPTS_PO_V and its siblings), so that receiving LOVs, folder forms, and custom receipt-entry clients can query a single, uniform interface regardless of whether the source is a purchase order, an internal requisition, or an ASN. In this respect it acts as a presentation and integration layer, joining purchasing, shipment, item, and vendor master data into a single flattened record set that a receiving screen or external process can consume directly.

Underlying Base Objects

The view is defined over a substantial set of base objects. The purchasing side draws from PO_HEADERS_TRX_V, PO_LINES_TRX_V, and PO_LINE_LOCATIONS_TRX_V (the transaction-mode purchasing views), together with synonyms such as PO_RELEASES_ALL, PO_LINE_TYPES_B, and the PO_VENDORS view for supplier identification. The shipment (ASN) side is built from RCV_SHIPMENT_HEADERS and RCV_SHIPMENT_LINES, which hold the advance shipment notice header and line records transmitted by the supplier.

Supporting master and reference data include MTL_SYSTEM_ITEMS and MTL_SYSTEM_ITEMS_TL (item attributes and descriptions), MTL_UNITS_OF_MEASURE (UOM class), HR_LOCATIONS_ALL_TL (ship-to location code), GL_DAILY_CONVERSION_TYPES (currency rate type), and PO_HAZARD_CLASSES_TL together with PO_UN_NUMBERS_TL for hazardous-material classification. RCV_ROUTING_HEADERS supplies routing names, RCV_PARAMETERS informs receiving-parameter behavior, and RCV_TRANSACTIONS_INTERFACE provides the interface target used when receiving from ASN lines. The package PO_CLM_INTG_GRP is referenced, further tying the view to the retrofitted configuration noted in the description.

Key Columns

The SELECT list follows the standard receiving-view column order. Leading literal columns establish the transaction context: a mode flag ('N'), a source type of 'ASN', a receipt source of 'VENDOR', a document type of 'PO', and the purchasing document type lookup code. Identifying keys then follow, including PO_HEADER_ID, SEGMENT1 (PO number), PO_LINE_ID, LINE_NUM, LINE_LOCATION_ID, SHIPMENT_NUM, PO_RELEASE_ID, and RELEASE_NUM.

The ASN-specific keys are SHIPMENT_HEADER_ID, SHIPMENT_NUM, SHIPMENT_LINE_ID, and the shipment line LINE_NUM. Vendor and location data are exposed through VENDOR_ID, VENDOR_NAME, VENDOR_SITE_ID, FROM_ORGANIZATION_ID, TO_ORGANIZATION_ID, SHIP_TO_LOCATION_ID, and LOCATION_CODE. Item columns include ITEM_ID, ITEM_NUMBER, ITEM_REVISION, ITEM_DESCRIPTION, CATEGORY_ID, VENDOR_ITEM_NUM, and UNIT_OF_MEASURE with its UOM_CLASS.

Control attributes — LOCATION_CONTROL_CODE, LOT_CONTROL_CODE, SERIAL_NUMBER_CONTROL_CODE, SHELF_LIFE_CODE, RESTRICT_LOCATORS_CODE, and RESTRICT_SUBINVENTORIES_CODE — drive form validation. Quantities, dates, and commercial fields (QUANTITY, EXPECTED_RECEIPT_DATE, NEED_BY_DATE, PACKING_SLIP, price, currency, rate, and DFF ATTRIBUTE1–ATTRIBUTE7) complete the projected record.

Common Use Cases and Queries

Typical uses include powering receipt-entry LOVs for ASN lines, reconciling expected versus received ASN quantities, and feeding RCV_TRANSACTIONS_INTERFACE for programmatic receipt creation.

• Retrieve open ASN lines for a specific supplier shipment header.
• List expected receipt quantities and dates by item for planning or discrepancy reporting.
• Drive folder-form or custom receiving UIs that require a consistent column layout across receipt sources.

Sample query:

SELECT shipment_header_id, shipment_line_id, segment1, item_number,
quantity, expected_receipt_date, vendor_name
FROM apps.rcv_enter_receipts_asn_v
WHERE shipment_num = :shipment_num;

Because the description notes "10SC ONLY - Retrofitted," availability and behavior should be validated against the target instance before relying on the view in custom code.