Search Results per_all_people_f




Overview
Explore in AI Chat

Overview

The POR_RCV_REQS_NAME_V view is a reporting object owned by the APPS schema within the Oracle iProcurement (ICX) product family. It exposes requisition-to-receipt information related to receiving activities in Oracle E-Business Suite, and it belongs to the same functional grouping as the POR_RCV_* family of views used by iProcurement and the receiving workflow. Its status is VALID in both Oracle EBS 12.1.1 and 12.2.2, and its structure and definition are effectively shared across these releases.

The view consolidates requisition header and line data with purchase order, purchase release, vendor, shipment, and person information, then presents a denormalized result set. The inclusion of PER_ALL_PEOPLE_F joins indicates that the view resolves human-resources person identifiers (both the requisition preparer and the requisition line "to person") to descriptive full names, which are useful for display and selection purposes. Combined with the POR_VIEW_REQS_PKG.GET_REQ_TOTAL function call, the view provides a single row per requisition/delivery context enriched with a computed total, making it suitable for iProcurement pages that display requisition demand awaiting receipt.

Underlying Base Objects

The documented referenced objects for this view include PO_REQUISITION_HEADERS, PO_REQUISITION_LINES, PO_REQ_DISTRIBUTIONS, PO_DISTRIBUTIONS, PO_HEADERS, PO_LINE_LOCATIONS, PO_RELEASES, PO_VENDORS (exposed as a view), PO_SYSTEM_PARAMETERS, OE_ORDER_HEADERS, RCV_SHIPMENT_LINES, HR_ALL_ORGANIZATION_UNITS_TL, and PER_ALL_PEOPLE_F. All are referenced through APPS synonyms.

These joins link requisition lines to their corresponding PO distributions, line locations, and PO headers so that only deliverable quantities remain visible. Filtering conditions limit results to open, approved shipments that are routed for receiving (RECEIVING_ROUTING_ID = 3) and whose shipment type is STANDARD, BLANKET, or SCHEDULED. The documented view text also includes a UNION ALL branch that sources internal sales order data from OE_ORDER_HEADERS and organization units, extending the view beyond pure purchasing to encompass internal requisitions fulfilled through order management.

Key Columns

  • REQUISITION_HEADER_ID / SEGMENT1 / DESCRIPTION — identify the requisition and its document number and description.
  • PREPARER_ID — the person who prepared the requisition.
  • TO_PERSON_ID — the person for whom the line was requested (the recipient or deliver-to person).
  • PAPF.FULL_NAME / PAPF2.FULL_NAME — resolved full names for the to-person and preparer, obtained through effective-dated lookups on PER_ALL_PEOPLE_F.
  • ORDER_NUM_REL_NUM — a concatenated display value combining the PO or order number with its release number.
  • PO_NUMBER / ORDER_NUMBER / PO_RELEASE_NUMBER — the purchase order, internal order, and release identifiers.
  • VENDOR — the supplier or organization name associated with the source document.
  • CREATION_DATE — the requisition creation timestamp.
  • GET_REQ_TOTAL(...) — the result of the POR_VIEW_REQS_PKG function, providing the aggregated requisition total.

Common Use Cases and Queries

Typical usage is on iProcurement pages and receiving-related reports where a user must review requisitions with outstanding quantities, display the preparer and recipient names in readable form, and identify the corresponding vendor or order. A representative query filtering to a specific preparer or recipient follows:

SELECT requisition_header_id,
       segment1,
       full_name,
       order_num_rel_num,
       vendor,
       creation_date
FROM   apps.por_rcv_reqs_name_v
WHERE  preparer_id = :preparer_id
ORDER  BY creation_date DESC;

Because the view relies on PER_ALL_PEOPLE_F effective-dated subqueries to return the latest name version, joins to additional HR data should also be filtered by EFFECTIVE_END_DATE to avoid duplicate person rows. For integration and diagnostics, the view serves as a ready-made join between purchasing and HR person references, reducing the need to reconstruct the multi-table relationship across requisitions, distributions, releases, and person records.