Search Results ieu_object_parameters




Overview
Explore in AI Chat

Overview

The view IEU_UWQ_FORECAST_V is an Oracle E-Business Suite database object belonging to the IEU (Universal Work Queue) product family. It is documented in ETRM metadata for EBS 12.1.1 and 12.2.2 as a "View used for UWQ selector SpreadTable." Its purpose is to project sales forecast data into the column shape and convention expected by the Universal Work Queue's SpreadTable selector, which renders tabular work items to agents in a call center or telephony-oriented application. The view therefore functions as an integration layer between the underlying sales forecast schema and the generic UWQ presentation model, translating source columns into the IEU-prefixed attributes that the UWQ runtime requires (object function, parameters, primary key column and value, media type UUID, and so on).

The ETRM record notes that the view is "Not implemented in this database," meaning that in the reference environment from which the metadata was extracted the object did not physically exist. Its definition is nonetheless documented, and it is deployed wherever UWQ forecast selectors are configured.

Underlying Base Objects

The view is defined over two referenced sources: AS_SALES_FORECAST_UWQ_V (aliased A) and JTF_OBJECTS_VL (aliased B), joined on the condition B.OBJECT_CODE = A.OBJECT_CODE. AS_SALES_FORECAST_UWQ_V is a sales forecast view in the Advanced Planning/forecasting schema that supplies the measured forecast values and dimensional attributes. JTF_OBJECTS_VL is the translated, multi-language view of the JTF Objects repository, which maps object codes to their object functions and object parameters. The join enriches each forecast row with the metadata that UWQ uses to launch the appropriate object (for example, a forecast form or detail region) when an agent selects the row. No additional base tables are documented; the ETRM record lists referenced base objects as "none documented," so the two views above should be treated as the direct dependencies.

Key Columns

Common Use Cases and Queries

The primary use case is diagnosing why a UWQ forecast selector displays or opens incorrectly, or confirming which object parameters will be passed for a given forecast. A representative query inspecting the parameter metadata and forecast key is:

SELECT ieu_object_function, ieu_object_parameters, ieu_param_pk_value, period_name, status_code, forecast_amount FROM ieu_uwq_forecast_v WHERE ieu_object_parameters IS NOT NULL ORDER BY period_name, resource_group_id;

To compare forecast scenarios across resources, select resource_id, resource_type, forecast_amount, best_forecast_amount, and worst_forecast_amount, filtering by status_code. Because the object is documented as not implemented in the reference database, administrators should verify its existence with ALL_VIEWS and its definition with DBMS_METADATA.GET_DDL or ALL_VIEWS.TEXT before relying on it in a given environment.