Results for “order_line”

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

Overview

ICX_RCV_ACCEPTED_ITEMS_V is an Oracle Applications view owned by the APPS schema and associated with the ICX product family (Oracle iProcurement). Under the ETRM 12.2.2 metadata the object carries the status VALID but is explicitly described as Obsolete, meaning it is retained for backward compatibility only and should not serve as the basis for new development. Historically, the view exposed receiving transactions that had been accepted into inventory, WIP, or expense destinations, and was consumed by iProcurement and related self-service receiving pages to present the receiver, supplier, shipment, and item context of accepted receipts.

Because the view is obsolete, its practical role in a 12.1.1 or 12.2.2 reporting landscape is limited to supporting legacy customizations, historical extracts, and migration analysis. Oracle's supported alternative for inbound receiving data is RCV_TRANSACTIONS and its associated RCV_SHIPMENT_LINES and RCV_SHIPMENT_HEADERS objects, joined directly or through the receiving inquiry views. Any query against ICX_RCV_ACCEPTED_ITEMS_V should therefore be treated as a read-only legacy access pattern rather than a strategic integration point.

Underlying Base Objects

The view is defined over a broad set of documented base objects. The core transactional source is RCV_TRANSACTIONS, which supplies the transaction identifier, type, date, quantities, units of measure, destination type, and the PO and WIP references. This is enveloped by RCV_SHIPMENT_HEADERS and RCV_SHIPMENT_LINES, which provide the shipment header and line context together with item, revision, description, and vendor item number. RCV_ROUTING_HEADERS contributes routing information where present.

Purchasing attributes derive from PO_HEADERS, PO_LINES, PO_LINE_LOCATIONS, PO_DISTRIBUTIONS, PO_RELEASES, PO_REQUISITION_HEADERS, and PO_REQUISITION_LINES. Supplier and site data come from PO_VENDORS and PO_VENDOR_SITES, while hazard and UN classification data are sourced from PO_HAZARD_CLASSES and PO_UN_NUMBERS. Item and reason descriptions are resolved through MTL_SYSTEM_ITEMS_KFV and MTL_TRANSACTION_REASONS. Organization and location context are supplied by ORG_ORGANIZATION_DEFINITIONS, HR_LOCATIONS, and HR_EMPLOYEES, with the ICX_PO_RCV_QTY package providing the net-quantity derivation. Security and profile behavior are governed by FND_PROFILE, FND_GLOBAL, HR_GENERAL, HR_PERSON_NAME, HR_SECURITY, and FINANCIALS_SYSTEM_PARAMETERS.

Key Columns

• TRANSACTION_ID / PARENT_TRANSACTION_ID — primary and parent receiving transaction identifiers from RCV_TRANSACTIONS.
• TRANSACTION_TYPE / TRANSACTION_DATE / INSPECTION_STATUS_CODE — the nature, timing, and inspection state of the accepted transaction.
• TRANSACT_QTY, TRANSACT_UOM, PRIMARY_QUANTITY, PRIMARY_UOM, NET_PRIMARY_QUANTITY — transaction and primary quantities, the net value being derived by ICX_PO_RCV_QTY.GET_NET_QTY.
• ITEM_ID, ITEM_REV, ITEM_DESC, VENDOR_ITEM_NUM — item identification and supplier-facing description from RCV_SHIPMENT_LINES.
• DESTINATION_TYPE, SUBINVENTORY, LOCATOR_ID — where the accepted material was delivered (inventory, WIP, or expense).
• PO_HEADER_ID, PO_LINE_ID, PO_LINE_LOCATION_ID, PO_DISTRIBUTION_ID, PO_RELEASE_ID — purchasing document references, including the order_line lineage that ties the receipt to its originating purchase order line.
• SUPPLIER_ID, SUPPLIER, SUPPLIER_SITE_ID, SUPPLIER_SITE — decoded supplier identity that resolves to vendor name for PO-sourced receipts and organization name for internal or inventory sources.
• RECEIVER, SHIP_TO_LOCATION, DELIVER_TO_LOCATION, DELIVER_TO_PERSON — receiver and delivery context from HR_EMPLOYEES and HR_LOCATIONS.

Common Use Cases and Queries

Legacy reporting typically joins this view to purchasing documents to reconcile accepted quantities against ordered quantities at the order-line level. A representative query that mirrors the order_line search pattern is:

• SELECT transaction_id, po_header_id, po_line_id, po_line_location_id, item_id, item_desc, transact_qty, primary_quantity, transaction_date FROM apps.icx_rcv_accepted_items_v WHERE po_line_id IS NOT NULL AND transaction_date >= :from_date AND transaction_date < :to_date;

Additional scenarios include supplier scorecard extracts keyed on supplier_id and supplier_site, receiver productivity reporting grouped by receiver, and destination analysis by destination_type and subinventory. Because the view is obsolete, these queries should be re-pointed to RCV_TRANSACTIONS joined directly to RCV_SHIPMENT_LINES, RCV_SHIPMENT_HEADERS, and the PO tables, which yields identical transactional data with supported object lifetimes across 12.1.1 and 12.2.2.