Search Results per_people_f_pk

Overview

ICX_PO_SUPPLIER_ITEMS_V is an APPS-owned database view in Oracle E-Business Suite, defined within the Oracle iProcurement (ICX) product module. Its documented status is VALID, and it is described in the ETRM metadata simply as the "Supplier Items View." Functionally, the view exposes the relationship between inventory items and their approved suppliers as maintained through sourcing rules. It returns the item number, description, unit of measure, buyer information, supplier name, effective and expiration dates, sourcing rank, and allocation percentage, joined to the operating unit's inventory organization.

Because it consolidates sourcing, item master, supplier, and buyer data into a single queryable object, the view serves as a convenient reporting and integration layer for iProcurement. It eliminates the need for custom code to repeatedly join the sourcing-level view against the item key flexfield view, the supplier view, and the HR person view. This makes it useful for both ad hoc reporting and for embedded logic within iProcurement's requisition and catalog functionality.

Underlying Base Objects

The view is defined over five primary base objects, with an additional dependency on HR packages. The documented referenced base objects are FINANCIALS_SYSTEM_PARAMETERS (SYNONYM), MRP_ITEM_SOURCING_LEVELS_V (VIEW), MTL_SYSTEM_ITEMS_KFV (SYNONYM), PER_PEOPLE_F (VIEW), and PO_VENDORS (VIEW). The view also references HR_GENERAL, HR_PERSON_NAME, and HR_SECURITY packages, which are typically invoked through PER_PEOPLE_F for name formatting and security.

The view text reveals a deliberate join strategy. The ORDERED and USE_NL hints force nested-loops execution in the documented table order MISL, MSI, POV, HRV, FSP. A specific INDEX(HRV PER_PEOPLE_F_PK) hint directs the optimizer to use the primary key index on the PER_PEOPLE_F view when resolving the buyer. This is significant: the search term "per_people_f_pk" corresponds directly to this index hint, which is the mechanism linking each item's BUYER_ID to a formatted full name. The join to PER_PEOPLE_F is an outer join (HRV.PERSON_ID(+) = MSI.BUYER_ID), so items without an assigned buyer are still returned.

The join to FINANCIALS_SYSTEM_PARAMETERS restricts results to the inventory organization configured for the current operating unit. The date predicate SYSDATE BETWEEN MISL.EFFECTIVE_DATE AND NVL(MISL.DISABLE_DATE, SYSDATE+1) filters the sourcing rows to those currently active.

Key Columns

• ITEM_NUM — Concatenated item key flexfield segments (MSI.CONCATENATED_SEGMENTS).
• ITEM_DESCRIPTION / UNIT_OF_MEASURE — Item description and primary UOM from MTL_SYSTEM_ITEMS_KFV.
• ITEM_ID / INVENTORY_ORGANIZATION_ID — Inventory item identifier and its organization.
• BUYER_ID / BUYER_NAME — Buyer identifier and full name resolved from PER_PEOPLE_F (aliased HRV.FULL_NAME).
• VENDOR_ID / VENDOR_NAME — Supplier identity from PO_VENDORS.
• EFFECTIVE_DATE / EXPIRATION_DATE — Sourcing validity window.
• RANK / SPLIT — Sourcing rank and allocation percent.
• SUPPLIER_URL / ITEM_URL — Link columns exposed for iProcurement navigation.

Common Use Cases and Queries

Typical uses include listing approved suppliers per item, auditing buyer assignments, and validating sourcing coverage. For example, to retrieve active sourced items with their suppliers:

SELECT item_num, description, buyer_name, vendor_name, rank, split
FROM   apps.icx_po_supplier_items_v
WHERE  inventory_organization_id = :org_id;

To locate items lacking a buyer assignment (leveraging the outer join), filter on BUYER_NAME IS NULL. The PER_PEOPLE_F_PK hint should be preserved if the view text is copied, as it materially affects performance of the buyer-name resolution.