Results for “icx_receipt_headers_v”
36 results
AI-generated from documented ETRM metadata — verify critical details on the linked pages.
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
- RECEIPT_NUM, RECEIPT_DATE, SHIPMENT_NUM, SHIPMENT_HEADER_ID — the receipt identity, its creation date, and the shipment line reference.
- SOURCE_TYPE — maps RSH.RECEIPT_SOURCE_CODE, with documented values for Internal Order, Inventory, and Vendor receipts.
- SUPPLIER_ID / SUPPLIER and VENDOR_ID / VENDOR — for vendor receipts the supplier is taken from the vendor; for internal and inventory receipts it resolves to the organization. SUPPLIER_URL exposes POV.ATTRIBUTE14.
- SUPPLIER_SITE_ID / SUPPLIER_SITE — from the vendor site foreign key.
- ORGANIZATION_ID and SOURCE_ORG — the source organization identifier and its name.
- SHIP_TO_LOCATION_ID and SHIP_TO_LOCATION — the ship-to location identifier and the corresponding LOCATION_CODE from HR_LOCATIONS. The search term "ship_to_location" maps directly to these two columns.
- BILL_OF_LADING, PACKING_SLIP, SHIPPED_DATE, FREIGHT_CARRIER_CODE, EXPECTED_RECEIPT_DATE — shipment and logistics attributes.
- EMPLOYEE_ID / RECEIVER — the receiving employee and full name.
- NUM_OF_CONTAINERS, WAYBILL_AIRBILL_NUM, COMMENTS, USSGL_TRANSACTION_CODE, GOVERNMENT_CONTEXT — supplementary receipt details.
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.
-
View: ICX_RECEIPT_HEADERS_V 12.1.1
Receipt Headers View
APPS.ICX_RECEIPT_HEADERS_V·↳ FND_PROFILE·↳ HR_EMPLOYEES·↳ HR_GENERAL·Explore ICX module →
-
View: ICX_RECEIPT_HEADERS_V 12.2.2
Receipt Headers View
APPS.ICX_RECEIPT_HEADERS_V·↳ FND_GLOBAL·↳ FND_PROFILE·↳ HR_EMPLOYEES·Explore ICX module →
-
12.1.1 DBA Data 12.1.1
-
12.2.2 DBA Data 12.2.2
-
12.2.2 FND Design Data 12.2.2
-
12.1.1 FND Design Data 12.1.1
-
VIEW: APPS.HR_EMPLOYEES 12.2.2
-
VIEW: APPS.HR_EMPLOYEES 12.1.1
-
VIEW: APPS.PO_VENDOR_SITES 12.1.1
-
VIEW: APPS.PO_VENDOR_SITES 12.2.2
-
VIEW: APPS.HR_LOCATIONS 12.1.1
-
VIEW: APPS.HR_LOCATIONS 12.2.2
-
VIEW: APPS.PO_VENDORS 12.1.1
-
VIEW: APPS.PO_VENDORS 12.2.2
-
Set Distribution Table.
-
Set Distribution Table.
-
eTRM - ICX Tables and Views 12.2.2
-
eTRM - PO Tables and Views 12.1.1
Temporary table for tracking a receiving upgrade from Release 9 to Release 10
-
eTRM - ICX Tables and Views 12.1.1
-
12.2.2 DBA Data 12.2.2
-
12.1.1 DBA Data 12.1.1
-
eTRM - INV Tables and Views 12.1.1
-
eTRM - PER Tables and Views 12.1.1
Table to store NQF Training info for a person
-
Set Distribution Table.
-
Set Distribution Table.
-
eTRM - ICX Tables and Views 12.2.2
-
eTRM - ICX Tables and Views 12.1.1
-
eTRM - PO Tables and Views 12.1.1
Temporary table for tracking a receiving upgrade from Release 9 to Release 10
-
eTRM - INV Tables and Views 12.1.1
-
eTRM - PER Tables and Views 12.1.1
Table to store NQF Training info for a person