Results for “pos_rcv_rejected_items_v”

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

Overview

POS_RCV_REJECTED_ITEMS_V is an Oracle E-Business Suite (EBS) 12.1.1 / 12.2.2 reporting view owned by the APPS schema and delivered with the POS (iSupplier Portal) product family. As its name implies, the view exposes information about rejected receipt items — that is, shipment lines and receiving transactions where goods were received but subsequently rejected during the receiving or inspection process. Because rejection activity is normally only visible inside the receiving forms or through raw RCV_TRANSACTIONS queries, this view provides a flattened, denormalized projection that consolidates rejection details with purchasing, supplier, item, and location context in a single queryable structure. This makes it well suited for supplier-facing reporting in iSupplier Portal, for buyer dashboards that monitor rejection trends, and for ad-hoc SQL used by support and implementation teams. Although the view's documentation centers on the rejection scenario, the underlying join pattern exposes the full receipt transaction context, so many practitioners also use it as a generic view of receiving transactions from a specific perspective.

Underlying Base Objects

The view is defined over the RCV receiving tables and joined to purchasing, supplier, and HR reference objects. The documented referenced base objects include:

• Receiving tables: RCV_TRANSACTIONS, RCV_SHIPMENT_HEADERS, RCV_SHIPMENT_LINES, and RCV_ROUTING_HEADERS, which supply transaction ID, transaction type, transaction date, quantity, unit of measure, source document code, inspection status, and routing information.
• Purchasing tables: PO_HEADERS_ALL, PO_LINES_ALL, PO_LINE_LOCATIONS_ALL, PO_DISTRIBUTIONS_ALL, and PO_RELEASES_ALL, joined on the PO header, line, location, distribution, and release identifiers carried in the receiving transaction.
• Requisition tables: PO_REQUISITION_HEADERS_ALL and PO_REQUISITION_LINES_ALL — the linkage that allows the view to surface requisition context. Note, however, that the documented view text excerpt does not explicitly show a REQUISITION_NUM column; the requisition joins are part of the underlying object set, and requisition identifiers are typically reached through the PO distribution or line relationships.
• Supplier and item reference objects: PO_VENDORS, PO_VENDOR_SITES_ALL, MTL_SYSTEM_ITEMS_KFV, and MTL_TRANSACTION_REASONS.
• HR and security objects: PER_ALL_PEOPLE_F, HR_LOCATIONS_ALL, HR_GENERAL, HR_SECURITY, and FND_GLOBAL, used to resolve receiver names, deliver-to persons, and location codes within the current operating unit and security profile.
• Packages and views: POS_PO_RCV_QTY (a package supplying the GET_NET_QTY function), FINANCIALS_SYSTEM_PARAMS_ALL, ORG_ORGANIZATION_DEFINITIONS, PO_HAZARD_CLASSES, and PO_UN_NUMBERS.

Because HR_SECURITY and FND_GLOBAL are referenced, the view is effectively row-secured against the caller's organization and HR access, which is important when it is queried directly rather than through the iSupplier Portal application layer.

Key Columns

Selected columns include ORGANIZATION_ID, PARENT_TRANSACTION_ID, SHIPMENT_HEADER_ID, SHIPMENT_LINE_ID, TRANSACTION_ID, TRANSACTION_TYPE, and TRANSACTION_DATE. Quantity columns include TRANSACT_QTY and TRANSACT_UOM, PRIMARY_QUANTITY and PRIMARY_UOM, QUANTITY_RECEIVED, and NET_PRIMARY_QUANTITY (derived via POS_PO_RCV_QTY.GET_NET_QTY). Item information is exposed as ITEM_ID, ITEM_REV, ITEM_DESC, and VENDOR_ITEM_NUM. Supplier context is provided by SUPPLIER_ID, SUPPLIER, VENDOR_ID, VENDOR_NAME, SUPPLIER_SITE_ID, and SUPPLIER_SITE. Location and personnel columns include SHIP_TO_LOCATION, SHIP_TO_LOCATION_DESC, DELIVER_TO_LOCATION, DELIVER_TO_PERSON, RECEIVER, SUBINVENTORY, and LOCATOR_ID. Inspection and rejection detail is carried by INSPECTION_STATUS_CODE, INSPECTION_QUALITY_CODE, REASON_ID, and COMMENTS. Destination type is indicated by DESTINATION_TYPE, and source context by SOURCE_DOC_CODE, SOURCE_DOC_UOM, SOURCE_DOC_QTY, and SOURCE_TYPE.

Common Use Cases and Queries

Typical uses include supplier scorecards showing rejection rates by vendor, buyer reports listing rejected items pending resolution, and integration extracts feeding quality or warehouse systems. A representative query is shown below; users searching for "requisition_num" should validate whether the column is actually exposed in their instance version before relying on it.

SELECT supplier,
       vendor_item_num,
       item_desc,
       transaction_date,
       transact_qty,
       transact_uom,
       inspection_status_code,
       reason_id,
       comments
  FROM apps.pos_rcv_rejected_items_v
 WHERE organization_id = :org_id
   AND transaction_date >= :from_date
   AND transaction_date <  :to_date
 ORDER BY transaction_date DESC;

To aggregate rejections by supplier, wrap the view in a GROUP BY on SUPPLIER_ID or SUPPLIER and sum the quantity columns. Because requisition linkage is not guaranteed in the projection, joins to PO_REQUISITION_HEADERS_ALL and PO_REQUISITION_LINES_ALL via the PO header or distribution identifiers may be required to obtain REQUISITION_NUM.