Search Results ieu_lov_col2




Overview
Explore in AI Chat

Overview

APPS.AST_CUSTOMER_UWQ_LOV_V is a database view owned by the APPS schema in Oracle E-Business Suite, valid in both 12.1.1 and 12.2.2. It is registered in FND Design Data under the identifier AST.AST_CUSTOMER_UWQ_LOV_V. The name indicates its purpose: a List of Values (LOV) view for a Universal Work Queue (UWQ) customer selection component, and the AST prefix associates it with the Oracle TeleService/Service module (Customer Care). The view exposes a denormalized, flattened set of customer attributes intended to populate a value-selection LOV rather than to serve as a general-purpose reporting entity.

The ETRM documentation carries an explicit Oracle Internal Use Only warning and a view type of "Internal." Oracle Corporation does not support direct access to application data through this object except from standard Oracle Applications programs. Consequently, it should be treated as an implementation detail of the UWQ and LOV infrastructure. Direct queries are technically possible but are unsupported and may be affected by changes in underlying logic across patch levels or releases.

When a user searches for ieu_lov_col2, they are encountering the generic column naming convention used by the Interaction/Universal Work Queue LOV framework. The view is populated with generic IEU_LOV_COL1 through IEU_LOV_COL4 columns whose content is determined by the view definition rather than by the column names themselves.

Underlying Base Objects

The documented dependency list for AST_CUSTOMER_UWQ_LOV_V includes four referenced objects:

  • AR_LOOKUPS (VIEW) — supplies lookup-based values, most visibly the certification level and its decoded meaning.
  • FND_PROFILE (PACKAGE) — used at runtime to resolve profile option values, such as territory or operating unit context affecting the displayed rows.
  • FND_TERRITORIES_TL (SYNONYM) — the translated territories table, providing country code and country name.
  • HZ_PARTIES (SYNONYM) — the Trading Community Architecture party entity, the primary source of customer identity and address-related attributes.

The view is not referenced by any other database object, confirming its role as a terminal, presentation-layer construct consumed by application forms and OAF pages rather than by other views.

Key Columns

  • IEU_LOV_COL1 (VARCHAR2, 360) — primary display value for the LOV, typically the customer or party name.
  • IEU_LOV_COL2 (VARCHAR2, 30) — secondary identifier, commonly the customer number or party identifier class.
  • IEU_LOV_COL3 (NUMBER, 15) — numeric surrogate, generally the internal party or customer identifier used for programmatic reference.
  • IEU_LOV_COL4 (VARCHAR2, 962) — a concatenated descriptive string, often an assembled location or full address line.
  • EMAIL_ADDRESS (VARCHAR2, 2000), CITY, STATE, POSTAL_CODE, COUNTY, PROVINCE — address and contact attributes sourced from the party/location records.
  • COUNTRY_CODE and COUNTRY_NAME (VARCHAR2, 80) — territory values derived from FND_TERRITORIES_TL.
  • LOCATION (VARCHAR2, 1289) — a fully formatted address string.
  • CERTIFICATION_LEVEL (VARCHAR2, 30) and CERTIFICATION_MEANING (VARCHAR2, 80) — the certification lookup code and its translated meaning, sourced through AR_LOOKUPS.

Common Use Cases and Queries

The primary use case is LOV population within Universal Work Queue and Customer Care flows, where an agent selects a customer and the framework reads the generic IEU_LOV_COL columns for display and identification. Practical diagnostics include verifying which customers are visible to the LOV and inspecting certification decoding.

To list the top customer entries with certification details:

  • SELECT ieu_lov_col1, ieu_lov_col2, ieu_lov_col3, certification_level, certification_meaning FROM apps.ast_customer_uwq_lov_v;

To search a specific entry by the generic secondary column:

  • SELECT ieu_lov_col1, ieu_lov_col2, ieu_lov_col3, country_name FROM apps.ast_customer_uwq_lov_v WHERE ieu_lov_col2 = :search_value;

To review address and location data for a given customer number:

  • SELECT ieu_lov_col1, city, state, postal_code, country_name, location FROM apps.ast_customer_uwq_lov_v WHERE ieu_lov_col2 = :customer_number;

Because the object is flagged Oracle Internal Use Only, any custom reliance should be minimized and validated against the supported UWQ LOV APIs wherever possible.