Results for “rcv_enter_receipts_int_req_v”

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

Overview

RCV_ENTER_RECEIPTS_INT_REQ_V is an APPS-owned database view within the Oracle E-Business Suite Purchasing (PO) module. Its documented description, "10SC ONLY - Retrofitted," identifies it as a custom retrofit object rather than a standard Oracle-delivered Receiving view. The view is designed to present requisition-sourced shipment data in the flat, consolidated column layout expected by the Receiving user interface and integration layer, specifically for the Enter Receipts function. By surfacing internal requisition shipment lines alongside item, location, UOM, and receipt-attribute information in a single row structure, it allows the receiving forms and concurrent integration programs to treat requisition-driven internal shipments as receipt-eligible records. The view returns VALID status in the ETRM documentation for both 12.1.1 and 12.2.2 and is registered against the PO product.

Underlying Base Objects

The view is defined over a join of requisition, shipment, item, and reference entities. The documented referenced base objects are: HR_GENERAL (package), HR_LOCATIONS_ALL_TL (synonym), HR_SECURITY (package), MTL_SUPPLY (synonym), MTL_SYSTEM_ITEMS (synonym), MTL_UNITS_OF_MEASURE (synonym), ORG_ORGANIZATION_DEFINITIONS (view), PO_HAZARD_CLASSES_TL (synonym), PO_REQUISITION_HEADERS_ALL (synonym), PO_REQUISITION_LINES (synonym), PO_UN_NUMBERS_TL (synonym), RCV_ROUTING_HEADERS (view), RCV_SHIPMENT_HEADERS (synonym), and RCV_SHIPMENT_LINES (synonym).

Functionally, the driving rows come from RCV_SHIPMENT_LINES (aliased RSL) and RCV_SHIPMENT_HEADERS (RSH), which supply the shipment, source document, and receipt source context. These are joined to PO_REQUISITION_HEADERS_ALL (PORH) and PO_REQUISITION_LINES (PORL) to recover the originating requisition identifiers, segment values, and need-by dates. Item attributes are drawn from MTL_SYSTEM_ITEMS, unit-of-measure class information from MTL_UNITS_OF_MEASURE, and organization names from ORG_ORGANIZATION_DEFINITIONS. Location, hazard class, UN number, and routing information are supplemented from HR_LOCATIONS_ALL_TL, PO_HAZARD_CLASSES_TL, PO_UN_NUMBERS_TL, and RCV_ROUTING_HEADERS respectively. The DECODE on SOURCE_DOCUMENT_CODE sets the second literal column to 'INTERNAL' and derives a display value of 'INTERNAL ORDER' when the source code is 'REQ'.

Key Columns

• Source/Receipt context: SOURCE_DOCUMENT_CODE, RECEIPT_SOURCE_CODE, and the literal 'INTERNAL' indicator establish that the row represents an internal requisition transfer.
• Requisition identifiers: REQUISITION_HEADER_ID, PORH.SEGMENT1, REQUISITION_LINE_ID, LINE_NUM, REQ_DISTRIBUTION_ID.
• Shipment identifiers: SHIPMENT_HEADER_ID, SHIPMENT_NUM, SHIPMENT_LINE_ID, and the shipment line's LINE_NUM.
• Organizations and locations: FROM_ORGANIZATION_ID, TO_ORGANIZATION_ID, OOD.ORGANIZATION_NAME, SHIP_TO_LOCATION_ID, and HL.LOCATION_CODE.
• Item and control attributes: ITEM_ID, ITEM_REVISION, ITEM_DESCRIPTION, CATEGORY_ID, UNIT_OF_MEASURE, serial/lot/revision control codes, shelf-life indicators, and allowed-units and location/subinventory restriction flags.
• Quantity and dates: QUANTITY_SHIPPED, NEED_BY_DATE, EXPECTED_RECEIPT_DATE.
• Receiving defaults and references: DESTINATION_TYPE_CODE, DELIVER_TO_PERSON_ID, DELIVER_TO_LOCATION_ID, TO_SUBINVENTORY, NOTE_TO_RECEIVER, PACKING_SLIP, VENDOR_ITEM_NUM, HAZARD_CLASS, UN_NUMBER, and the ATTRIBUTE1 through ATTRIBUTE12 flex columns.

Common Use Cases and Queries

This view is typically consumed when building or troubleshooting internal requisition receipt flows, validating shipment-to-requisition linkage, or populating the Enter Receipts interface structure. A representative query retrieves pending internal shipment lines for a target organization:

SELECT shipment_num, segment1, line_num, item_id,
       quantity_shipped, unit_of_measure,
       need_by_date, ship_to_location_id, to_subinventory
FROM   apps.rcv_enter_receipts_int_req_v
WHERE  to_organization_id = :org_id
AND    source_document_code = 'REQ';

A second common pattern joins the view back to RCV_SHIPMENT_LINES to reconcile quantities, while a third uses it to extract item control attributes (serial, lot, and revision codes) so downstream validation matches inventory-item setup before receipt entry is permitted. Because the view is documented as a retrofit object, DBAs and developers should treat it as site-specific and verify its definition against the current 12.1.1 or 12.2.2 instance before relying on it in production integrations.