Results for “vendor_lot_num”

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

Overview

The RCV_ENTER_RECEIPTS_V view is an Oracle E-Business Suite database object owned by the APPS schema and classified under the PO – Purchasing product family. Its documentation describes it as "10SC ONLY – Retrofitted," indicating that it was introduced in a specific legacy or specialized release context and subsequently retrofitted into the standard Receiving (RCV) data model. Functionally, the view presents a consolidated, entry-oriented picture of receipts awaiting or undergoing processing in the Receiving open interface and receipt-entry flows. It exposes purchase order, requisition, shipment, item, and destination attributes in a single flattened structure, allowing receipt clerks, integration programs, and reporting tools to query receipt candidates without joining numerous base tables manually.

In Oracle EBS 12.1.1 and 12.2.2, the view supports the Receiving module's user interface layers and interface processing, providing a denormalized row set that reflects valid receipt sources and destinations. Because it is a view rather than a table, it does not store data; it derives its rows dynamically from its underlying base objects at query time.

Underlying Base Objects

Per the documented ETRM 12.2.2 metadata, RCV_ENTER_RECEIPTS_V references the following base objects:

• RCV_ENTER_RECEIPTS_ASN_V (VIEW) — supplies advanced shipment notice receipt rows.
• RCV_ENTER_RECEIPTS_INT_REQ_V (VIEW) — supplies internal requisition receipt rows.
• RCV_ENTER_RECEIPTS_INVENTORY_V (VIEW) — supplies inventory-sourced receipt rows.
• RCV_ENTER_RECEIPTS_PO_V (VIEW) — supplies purchase order receipt rows.
• RCV_ENTER_RECEIPTS_RMA_V (VIEW) — supplies return material authorization receipt rows.
• HR_GENERAL, HR_SECURITY, OE_SYS_PARAMETERS, and PO_CLM_INTG_GRP (PACKAGEs) — support security, system parameter, and integration logic invoked during view resolution.

The view therefore behaves as a union-style aggregator, channeling multiple receipt source types through a common column projection. This design permits a single query surface to retrieve PO, ASN, inventory, RMA, and internal requisition receipts together.

Key Columns

The projection exposes a wide set of identifying and descriptive columns, including:

• SOURCE_TYPE_CODE / RECEIPT_SOURCE_CODE / ORDER_TYPE_CODE — classify the origin of the receipt.
• PO_HEADER_ID, PO_LINE_ID, PO_LINE_LOCATION_ID, PO_RELEASE_ID — purchase order lineage keys.
• REQ_HEADER_ID, REQ_LINE_ID, REQ_DISTRIBUTION_ID — requisition lineage keys.
• RCV_SHIPMENT_HEADER_ID, RCV_SHIPMENT_LINE_ID — receiving shipment identity.
• ITEM_ID, ITEM_NUMBER, ITEM_REVISION, PRIMARY_UOM — item identification and unit of measure.
• VENDOR_ID, VENDOR_SITE_ID, VENDOR_ITEM_NUMBER — supplier details.
• DESTINATION_TYPE_CODE — the searched column, indicating the destination classification for the receipt.
• DELIVER_TO_PERSON_ID, DELIVER_TO_LOCATION_ID, DESTINATION_SUBINVENTORY — delivery target details.
• ORDERED_QTY, UNIT_PRICE, CURRENCY_CODE — quantity and pricing.
• INSPECTION_REQUIRED_FLAG, RECEIPT_REQUIRED_FLAG, ENFORCE_SHIP_TO_LOCATION_CODE — control flags.
• ATTRIBUTE1 through ATTRIBUTE15 — descriptive flexfield columns.
• NEED_BY_DATE, EXPECTED_RECEIPT_DATE, SHIPPED_DATE — scheduling dates.

The DESTINATION_TYPE_CODE column is particularly relevant for determining whether a receipt is destined to inventory, to an expense destination, or to another consuming location.

Common Use Cases and Queries

Typical applications include receipt-entry validation, interface loading, and destination-driven reporting. A representative query filtering by destination type is:

• SELECT po_number, item_number, ordered_qty, destination_type_code, destination_subinventory FROM apps.rcv_enter_receipts_v WHERE destination_type_code = 'INVENTORY';
• Querying receipts by source: SELECT receipt_source_code, po_number, vendor_id FROM apps.rcv_enter_receipts_v WHERE receipt_source_code = 'VENDOR';
• Reporting pending inspections: SELECT po_number, item_number, inspection_required_flag FROM apps.rcv_enter_receipts_v WHERE inspection_required_flag = 'Y';

Because the view is not a base table, it should not be used for direct DML; it serves read-only reporting, interface extraction, and UI support within the Purchasing and Receiving modules.