Search Results terms_name




Overview
Explore in AI Chat

Overview

ICX_SO_HEADERS_V is a reporting and integration view owned by the Oracle iProcurement (ICX) module in Oracle E-Business Suite 12.1.1 and 12.2.2. It exposes order entry header information drawn from the Oracle Order Management (OE) order header structure, and is used to present sales order header data within iProcurement and dependent reporting flows. The view is described in the ETRM metadata as the "Order Entry Header View," reflecting its function as a denormalized read layer over the sales order header entity.

The view is particularly relevant to requisition-to-order and punchout-style integration scenarios, where an externally originating order (for example, an iProcurement shopping cart converted to a sales order) must expose its header identity, sourcing metadata, customer, shipping, pricing, and payment attributes to downstream consumers. The metadata explicitly notes that in the ETRM reference environment the view is "Not implemented in this database," which indicates that ICX_SO_HEADERS_V is a defined object within the ICX product lineage but may be created conditionally depending on module installation and patch level. Its column set nevertheless documents a stable contract for the order header interface.

Underlying Base Objects

The ETRM metadata does not document specific referenced base objects for this view, listing none. The view text, however, shows that it is defined over the OE order header table (aliased H, corresponding to OE_ORDER_HEADERS_ALL) and augments that base data with joins or scalar functions against customer and address entities (CUST for customer name/number, SHIPADDR and SHIPLOC for ship-to location and GSA indicators). It also invokes ICX_CUSTOMER_PANEL.GET_AR_CODE for tax control flag translation, OE_QUERY.ORDER_TOTAL for the order total, and FND_CURRENCY.SAFE_GET_FORMAT_MASK for currency formatting. Because these referenced objects are not enumerated in the documentation, they should be verified against the deployed instance before relying on any relational assumption.

Key Columns

Common Use Cases and Queries

Typical uses include reconciling iProcurement-originated orders back to their source system, reporting on order header attributes, and exposing formatted order totals to non-OE consumers. A simple query filtering by the sourcing column is common:

  • SELECT HEADER_ID, ORDER_NUMBER, ORIGINAL_SYSTEM_SOURCE_CODE, ORIGINAL_SYSTEM_REFERENCE, CUSTOMER_NAME, ORDER_TOTAL FROM ICX_SO_HEADERS_V WHERE ORIGINAL_SYSTEM_SOURCE_CODE = :p_source;
  • SELECT ORDER_NUMBER, DATE_ORDERED, CURRENCY_CODE, ORDER_TOTAL, SHIP_TO_LOCATION FROM ICX_SO_HEADERS_V WHERE CUSTOMER_NUMBER = :p_cust AND OPEN_FLAG = 'Y';

Because referenced objects are undocumented and the view may not be implemented in every instance, validate its existence and column definitions in the target environment prior to production use.