Search Results icx_receipt_headers_v




Overview
Explore in AI Chat

Overview

ICX_RECEIPT_HEADERS_V is a reporting view owned by the APPS schema in Oracle E-Business Suite, delivered as part of the ICX (Oracle iProcurement) product. Its documented description is "Receipt Headers View," and it presents receipt header information originating from the receiving tables in Oracle Inventory and Purchasing, joined to supplier, organization, location, and employee attributes needed for presentation and downstream reporting. The view is defined over RCV_SHIPMENT_HEADERS as the driving source and enhances each receipt with human-readable supplier and location descriptions.

In EBS 12.1.1 and 12.2.2 the object carries a status of VALID and is exposed through the APPS schema for use by iProcurement pages, concurrent reports, and customer-defined queries. Because it flattens several foreign-key relationships into descriptive columns, it is commonly used as a convenience layer for reporting on goods receipts without writing the underlying join logic against RCV_SHIPMENT_HEADERS, PO_VENDORS, PO_VENDOR_SITES, ORG_ORGANIZATION_DEFINITIONS, HR_LOCATIONS, and HR_EMPLOYEES.

Underlying Base Objects

The ETRM metadata for 12.2.2 lists the following referenced base objects: FND_GLOBAL (package), FND_PROFILE (package), HR_EMPLOYEES (view), HR_GENERAL (package), HR_LOCATIONS (view), HR_PERSON_NAME (package), HR_SECURITY (package), ORG_ORGANIZATION_DEFINITIONS (view), PO_VENDORS (view), PO_VENDOR_SITES (view), and RCV_SHIPMENT_HEADERS (synonym). The documented view text shows explicit outer joins from RCV_SHIPMENT_HEADERS to PO_VENDORS, PO_VENDOR_SITES, HR_LOCATIONS, HR_EMPLOYEES, and ORG_ORGANIZATION_DEFINITIONS, with the receipt number predicate RSH.RECEIPT_NUM IS NOT NULL. The FND and HR packages are referenced indirectly through the HR security and profile mechanisms that govern rows visible to the querying user.

Key Columns

Common Use Cases and Queries

Typical uses include receipt registers by ship-to location, supplier receipt analysis, and integration extracts that require supplier and location descriptions rather than raw identifiers. A basic query filtering on ship-to location follows:

  • SELECT receipt_num, receipt_date, supplier, ship_to_location, source_org FROM apps.icx_receipt_headers_v WHERE ship_to_location = :p_location_code;
  • SELECT supplier, COUNT(*) FROM apps.icx_receipt_headers_v WHERE receipt_date >= :p_from_date GROUP BY supplier;
  • SELECT receipt_num, vendor, supplier_site, packing_slip, expected_receipt_date FROM apps.icx_receipt_headers_v WHERE source_type = 'VENDOR' AND expected_receipt_date IS NOT NULL;

Because the view depends on HR security and profile packages, results may be restricted by the responsibilities and security profiles of the querying user. Report authors should therefore test queries under the intended responsibility and account for the outer joins, which return null descriptive values when a ship-to location, employee, or vendor record is not resolvable.