Search Results ieu_object_parameters




Overview
Explore in AI Chat

Overview

APPS.AST_FORECAST_UWQ_V is a reporting and integration view in Oracle E-Business Suite (12.1.1 and 12.2.2) that exposes sales forecast data through the Universal Work Queue (UWQ) framework. It is defined in the APPS schema and constructed as a join between the sales forecast base view AS_SALES_FORECAST_UWQ_V and the generic object metadata view JTF_OBJECTS_VL. The view performs a dual role: it surfaces forecast metrics (period, status, resource, and amount information) while simultaneously embedding the IEU (Interaction and Entity Utility) attributes required by the UWQ and object-entity-layer infrastructure.

The presence of the IEU_* columns (IEU_OBJECT_FUNCTION, IEU_OBJECT_PARAMETERS, IEU_MEDIA_TYPE_UUID, IEU_PARAM_PK_COL, and IEU_PARAM_PK_VALUE) indicates that this view is intended to register forecast records as navigable objects within the UWQ, allowing a forecast row to be passed as an entity into downstream applications via the object's function and parameter metadata. The IEU_MEDIA_TYPE_UUID column is supplied as an empty string literal rather than being sourced from a column, which is significant for consumers searching that term: the view does not derive a media type UUID from underlying data; it hard-codes a null placeholder.

Underlying Base Objects

The view is documented as being defined over exactly two referenced base objects:

  • AS_SALES_FORECAST_UWQ_V (VIEW) — the source of all forecast business attributes. Aliased as A in the view text, it provides forecast_id, period_name, status_code, resource_group_id, forecast_amount, best_forecast_amount, worst_forecast_amount, resource_id, resource_type, and object_code.
  • JTF_OBJECTS_VL (VIEW) — the source of object-level metadata. Aliased as B, it supplies OBJECT_FUNCTION and OBJECT_PARAMETERS, which describe how the object is invoked or navigated.

The two objects are joined by the predicate B.OBJECT_CODE = A.OBJECT_CODE, meaning that only forecast records whose object_code has a matching entry in the JTF object registry are returned. This effectively filters the forecast set to only those records participating in the UWQ/object framework, and enriches each row with the object's function and parameter definitions.

Key Columns

  • IEU_OBJECT_FUNCTION (from B.OBJECT_FUNCTION) — the function used to open or navigate to the forecast object.
  • IEU_OBJECT_PARAMETERS (from B.OBJECT_PARAMETERS) — parameter definitions associated with that function.
  • IEU_MEDIA_TYPE_UUID — returned as a literal ''; no media type is sourced.
  • IEU_PARAM_PK_COL — literal 'forecast_id', identifying the primary key column of the object.
  • IEU_PARAM_PK_VALUE — TO_CHAR(a.forecast_id), the character representation of the forecast primary key.
  • FORECAST_ID, PERIOD_NAME, STATUS_CODE — forecast identity, period, and lifecycle status.
  • RESOURCE_GROUP_ID, RESOURCE_ID, RESOURCE_TYPE — the resource grouping and resource to which the forecast applies.
  • FORECAST_AMOUNT, BEST_FORECAST_AMOUNT, WORST_FORECAST_AMOUNT — the expected, optimistic, and pessimistic forecast values.

Common Use Cases and Queries

Typical usage includes UWQ worklist integration, forecast reporting by period and resource, and building navigable entity links. A representative query:

SELECT ieu_object_function, ieu_param_pk_value, period_name, status_code, resource_id, forecast_amount, best_forecast_amount, worst_forecast_amount FROM apps.ast_forecast_uwq_v WHERE period_name = :period;

Because IEU_MEDIA_TYPE_UUID is always empty, queries filtering by media type will not retrieve meaningful values and should be adjusted accordingly.