Search Results freight_term




Overview
Explore in AI Chat

Overview

ICX_PANEL_CUSTOMER_V is a reporting view within the Oracle iProcurement (ICX) module of Oracle E-Business Suite. It presents a consolidated customer profile surface that combines raw Receivables customer attributes with decoded, human-readable values produced by calls to the package function ICX_CUSTOMER_PANEL.GET_AR_CODE. The view is therefore best understood as a presentation layer over RA_CUSTOMERS rather than a purely relational projection: several columns are returned as translated display strings instead of their underlying lookup codes.

The view is significant to users who search on customer_prospect_code, because it exposes the CUSTOMER_PROSPECT_CODE attribute in both raw and decoded form. The raw CUSTOMER_CODE (prospect) column carries the stored lookup value, while the decoded column — produced by GET_AR_CODE('CUSTOMER_PROSPECT_CODE', CUSTOMER_PROSPECT_CODE) — yields the descriptive meaning used in iProcurement panel rendering and downstream reporting.

Per the documented ETRM metadata, this view is marked as "Not implemented in this database," meaning it may be absent from certain environments or superseded by alternate iProcurement panel definitions. This must be confirmed against the specific 12.1.1 or 12.2.2 instance before relying on it.

Underlying Base Objects

The documented source object is RA_CUSTOMERS, the master customer and prospect table in Oracle Receivables. All columns in the SELECT list derive from RA_CUSTOMERS, with the exception of the translated columns computed at runtime by ICX_CUSTOMER_PANEL.GET_AR_CODE.

The ETRM metadata records no additional referenced base objects, though in practice the GET_AR_CODE function may internally consult Receivables lookup views such as AR_LOOKUPS. This dependency is functional, not structural, and is not listed in the documented view metadata.

Because the view is a single-source projection from RA_CUSTOMERS, joins on CUSTOMER_ID remain valid against any Receivables object keyed on the same column.

Key Columns

Common Use Cases and Queries

The view is typically queried to present or export a customer or prospect profile, and to filter records by prospect designation. Because the decoded prospect indicator is embedded in a column rather than a lookup join, queries must reference the correct column name for the desired form.

Listing customer and prospect profiles with decoded values:

  • SELECT customer_id, customer_name, customer_prospect_code, status, customer_type FROM icx_panel_customer_v;

Isolating prospects using the raw code column:

  • SELECT customer_id, customer_name, customer_code FROM icx_panel_customer_v WHERE customer_code = 'P';

Case-insensitive name search using the uppercase column:

  • SELECT customer_id, customer_name FROM icx_panel_customer_v WHERE customer_name_upper LIKE 'ACME%';

Joining back to Receivables for site-level detail:

  • SELECT v.customer_name, v.customer_prospect_code, s.site_use_id FROM icx_panel_customer_v v, ra_site_uses_all s WHERE s.customer_id = v.customer_id;

Because GET_AR_CODE executes per row, large extracts may incur performance overhead; restricting the result set and avoiding unnecessary selection of decoded columns is advisable. Organizations should verify view availability in their specific 12.1.1 or 12.2.2 environment, given the documented "not implemented" status.