Search Results ieu_object_function




Overview
Explore in AI Chat

Overview

AST_FORECAST_UWQ_V is a read-only view owned by the APPS schema within the Oracle E-Business Suite TeleSales (AST) product family. It exposes sales forecast data in a flattened structure that also carries Universal Work Queue (UWQ) linkage attributes, allowing forecasts to be surfaced as resources within the UWQ framework and consumed by integrated applications. The view is registered as VALID in the ETRM metadata for both 12.1.1 and 12.2.2.

The view presents forecast measures at the period, status, resource group, and resource level, together with the metadata that the UWQ engine requires to render and route forecast work items. Because it joins forecast data to the JTF object definitions, it is particularly relevant for integrations and reports that need to identify the underlying object, its parameters, and the primary-key value that identifies each forecast record.

Underlying Base Objects

AST_FORECAST_UWQ_V is defined over two documented base objects:

The defining query joins these two sources on B.OBJECT_CODE = A.OBJECT_CODE, where B is JTF_OBJECTS_VL and A is AS_SALES_FORECAST_UWQ_V. The join enriches each forecast row with the object-level metadata needed by UWQ. For any integration or report that must not depend on the UWQ enrichment, AS_SALES_FORECAST_UWQ_V can be queried directly; AST_FORECAST_UWQ_V should be used when UWQ object context is required.

Key Columns

Together, FORECAST_AMOUNT, BEST_FORECAST_AMOUNT, and WORST_FORECAST_AMOUNT provide the three-point estimate commonly used in weighted forecast reporting.

Common Use Cases and Queries

Typical scenarios include UWQ-driven forecast worklists, resource-level forecast dashboards, and comparison of best-case against expected and worst-case forecasts. Because BEST_FORECAST_AMOUNT exists only at this level via AS_SALES_FORECAST_UWQ_V, queries should filter and aggregate appropriately.

Example — best-case forecast by resource group and period:

  • SELECT period_name, resource_group_id, resource_id, SUM(best_forecast_amount) best_total FROM apps.ast_forecast_uwq_v WHERE status_code = 'ACTIVE' GROUP BY period_name, resource_group_id, resource_id ORDER BY period_name;

Example — UWQ object context for a specific forecast:

  • SELECT ieu_object_function, ieu_param_pk_value, forecast_amount, best_forecast_amount FROM apps.ast_forecast_uwq_v WHERE ieu_param_pk_value = :forecast_id;

Reports joining to resource or period dimensions should reconcile against AS_SALES_FORECAST_UWQ_V to confirm that no rows are lost through the JTF object join. Standard AST responsibilities govern access to the view.