Results for “requestor_id”

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

Overview

POR_RCV_EXPRESS_ITEMS_V is a database view owned by the APPS schema within the Oracle iProcurement (ICX) product family. Its documented purpose is to present the set of items eligible for receipt during express receiving of requisitions, consolidating requisition and purchase order lines into a single standardized result set that the receiving user interface can consume. The view is delivered with a VALID status and forms part of the standard Oracle E-Business Suite 12.1.1 and 12.2.2 data model.

The view acts as a reporting and integration surface rather than a transactional object. It does not store data; instead it projects columns from multiple purchasing and receiving base objects and normalizes them through a UNION ALL, so that internal requisitions (source type INVENTORY) and supplier-facing purchase order lines are presented with a uniform column layout. This makes it suitable for direct SQL querying in reports, form personalizations, and concurrent programs that need a single, predictable source of receivables-ready item rows.

Underlying Base Objects

The documented base objects underlying POR_RCV_EXPRESS_ITEMS_V span purchasing, receiving, inventory, and human resources schemas. They include PO_REQUISITION_HEADERS and PO_REQUISITION_LINES for the internal requisition branch, PO_HEADERS_ALL, PO_LINES_TRX_V, PO_LINE_LOCATIONS_TRX_V, PO_DISTRIBUTIONS_TRX_V, PO_REQ_DISTRIBUTIONS, PO_VENDORS, and PO_SYSTEM_PARAMETERS for the purchasing branch, RCV_SHIPMENT_LINES for the receiving linkage, MTL_UNITS_OF_MEASURE for unit-of-measure translation, HR_ALL_ORGANIZATION_UNITS_TL for organization naming, and PO_CLM_INTG_GRP as a supporting package. Most of these are referenced through APPS synonyms.

The join logic is driven by source type code INVENTORY for the requisition branch and by purchase order distribution lines for the PO branch. The view relies on RCV_SHIPMENT_LINES with a routing header identifier of 3 to restrict rows to the receiving context, and it filters out fully delivered or cancelled quantities so that only outstanding receipt quantities survive. Because PO_LINES_TRX_V and PO_LINE_LOCATIONS_TRX_V are transactional (TRX) views, the object reflects current, multi-org secured purchasing data rather than a static snapshot.

Key Columns

• KEY_ID — the identifier used by express receiving to uniquely address the row. In the requisition branch it resolves to PORL.REQUISITION_LINE_ID; the search term "key_id" therefore targets the receiving row key, not a foreign key to a single fixed table.
• ORDER_TYPE_CODE — distinguishes the origin of the row; the requisition branch returns 'INT' for internal requisitions, while the PO branch returns supplier order types.
• EXPECTED_RECEIPT_QUANTITY — the open quantity derived as ordered quantity less cancelled quantity less delivered quantity, representing what remains to be received.
• EXPECTED_RECEIPT_DATE — need-by or promised date, projected as the anticipated receipt date.
• RECEIPT_DATE — populated with SYSDATE as the effective receipt date for the row.
• RECEIPT_UOM / RECEIPT_UOM_TL / RECEIPT_UOM_CLASS — unit of measure code, translated description, and UOM class for the received quantity.
• SOURCE — organization name for internal requisitions, vendor name for supplier orders.
• SUPPLIER_ID — vendor identifier where applicable; NULL for internal requisitions.
• ITEM_ID / ITEM_DESCRIPTION — inventory item identifier and description, truncated to 240 characters on the PO branch.
• REQUISITION_NUMBER, REQUISITION_LINE_ID, REQUISITION_HEADER_ID — requisition document and line identifiers.
• PO_HEADER_ID, PO_LINE_LOCATION_ID, PO_DISTRIBUTION_ID — purchasing identifiers, returned as NULL in the requisition branch.
• ORGANIZATION_ID, REQUESTOR_ID, USSGL_TRANSACTION_CODE — destination organization, requester, and accounting flexfield context.

Common Use Cases and Queries

Typical uses include building express receiving LOVs, validating receipt eligibility, and reconciling outstanding requisition and PO quantities. The following sample retrieves all open express receiving rows for a given organization, keyed on KEY_ID.

SELECT key_id,
       order_type_code,
       requisition_number,
       item_description,
       expected_receipt_quantity,
       receipt_uom_tl,
       source
  FROM apps.por_rcv_express_items_v
 WHERE organization_id = :p_org_id
   AND expected_receipt_quantity > 0
 ORDER BY expected_receipt_date, key_id;

Because express receiving drives updates through KEY_ID, a second common pattern resolves a specific row before submission:

SELECT key_id, order_type_code, requisition_line_id, po_distribution_id
  FROM apps.por_rcv_express_items_v
 WHERE key_id = :p_key_id;

Reports frequently aggregate by source or UOM to plan warehouse workload, and integration routines use the view as the authoritative list of items awaiting receipt across both internal and supplier channels. Queries should respect operating unit and organization security, as the underlying TRX views enforce multi-org access.