Results for “rcv_po_items_v”

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

Overview

RCV_PO_ITEMS_V is a view owned by the APPS schema in Oracle E-Business Suite, registered under the Purchasing (PO) product module. It is classified as a retrofit object, and its status is VALID in the documented ETRM metadata. The view presents a denormalized reporting structure that combines purchasing line information from PO_LINES with inventory item flexfield attributes from MTL_ITEM_FLEXFIELDS. The union of these two sources allows the view to return a complete list of PO lines regardless of whether the line references a defined master item.

The user query term "po_lines" reflects the most common access path for this object. Users searching for PO line data typically navigate to this view because it exposes item identifiers, descriptions, revisions, and unit prices directly from PO_LINES, while enriching records with item number and organization context from the inventory flexfield view. This makes RCV_PO_ITEMS_V useful in purchasing reports, receiving validations, and integration extracts where item-level detail is required alongside the base PO line structure.

Underlying Base Objects

The ETRM metadata documents two referenced base objects: PO_LINES, which is a synonym (normally resolving to the PO.PO_LINES table), and MTL_ITEM_FLEXFIELDS, which is a view that exposes the item flexfield structure used in inventory. The view definition performs a UNION of two SELECT statements. The first statement joins PO_LINES to MTL_ITEM_FLEXFIELDS on ITEM_ID, returning populated ITEM_ID, ITEM_NUMBER, and ORGANIZATION_ID values for lines that reference a real master item. The second statement selects from PO_LINES alone, filtered by ITEM_ID IS NULL, substituting TO_NUMBER(NULL) for ITEM_ID and ORGANIZATION_ID and NULL for ITEM_NUMBER.

This UNION construction ensures that lines of type outside the item master — for example, certain service, outside processing, or free-text lines — still appear in the view. Consumers therefore receive every PO line, with item attributes present only where an item reference exists.

Key Columns

• PO_LINE_ID — Primary identifier of the purchasing line, originating from PO_LINES.
• ITEM_ID — Inventory item identifier from PO_LINES, populated only when the line references a master item.
• ITEM_DESCRIPTION — Line-level description of the item or service being purchased.
• ITEM_REVISION — Revision value carried on the purchasing line, where applicable.
• CATEGORY_ID — Purchasing or inventory category associated with the line.
• ITEM_NUMBER — Item number obtained from MTL_ITEM_FLEXFIELDS; NULL for non-item lines.
• ORGANIZATION_ID — Inventory organization context from the flexfields view; NULL for non-item lines.
• UNIT_PRICE — Unit price recorded on the PO line.

Common Use Cases and Queries

Typical uses include purchasing on-hand reference reports, receiving screen validations, and data extracts feeding downstream systems that must reconcile PO lines to inventory items. A straightforward query retrieving all lines for a given purchase order might join this view back to PO_HEADERS via PO_LINE_ID and PO_HEADER_ID in PO_LINES, although that parent linkage is not exposed through this view directly.

• Listing item numbers and descriptions for all PO lines: SELECT PO_LINE_ID, ITEM_NUMBER, ITEM_DESCRIPTION, UNIT_PRICE FROM APPS.RCV_PO_ITEMS_V;
• Filtering only lines with a valid item reference: SELECT PO_LINE_ID, ITEM_ID, ITEM_NUMBER FROM APPS.RCV_PO_ITEMS_V WHERE ITEM_ID IS NOT NULL;
• Isolating non-item lines for exception review: SELECT PO_LINE_ID, ITEM_DESCRIPTION FROM APPS.RCV_PO_ITEMS_V WHERE ITEM_ID IS NULL;

Because the object is a view, no DML should be issued against it, and indexing or constraint modifications apply to the underlying PO_LINES table instead. For version 12.1.1 and 12.2.2, the column set and union logic remain consistent with the documented definition.