Results for “ddf_context”

AI-generated from documented ETRM metadata — verify critical details on the linked pages.

Overview

The view APPS.MTL_FORECAST_DATES_COST_V is an Inventory (INV) module database object in Oracle E-Business Suite, documented with status VALID and marked as "Retrofitted" within the ETRM 12.2.2 repository. It presents forecast demand records held in the MRP_FORECAST_DATES table, enriched with standard costing information derived from the cost group item costs view. In effect, it joins forecast date information to item cost, allowing forecast quantities recorded at the item and organization level to be evaluated alongside their associated cost values.

Its role in reporting and integration is to provide a consolidated, read-only projection that combines demand-side scheduling data with costing attributes. Because forecast designators—including the SOURCE_FORECAST_DESIGNATOR column commonly referenced by users—reside on this view, it is frequently used to reconcile demand forecasts, source forecast references, and the resulting item cost impact within a single query surface. It exists to spare developers and report authors from re-implementing the underlying joins each time forecast and cost data must be combined.

Underlying Base Objects

Per the documented view text and metadata, MTL_FORECAST_DATES_COST_V is defined over the following base objects:

• MRP_FORECAST_DATES (SYNONYM) — the primary demand source supplying forecast transaction, designator, date, quantity, and demand-classification columns.
• CST_CG_ITEM_COSTS_VIEW (VIEW) — provides the item cost, aliased as ITEM_COST in the select list.
• MTL_PARAMETERS (SYNONYM) — supplies the organization's primary cost method and default cost group used to resolve the correct cost group.
• MRP_PROJECT_PARAMETERS (SYNONYM) — referenced in the documented base-object metadata, reflecting the view's union branch that handles project-related forecast records.

The structure is a UNION ALL of two branches. The first branch, per the view text, filters on FRCT.PROJECT_ID IS NULL and joins costs through CCICV.ORGANIZATION_ID = FRCT.ORGANIZATION_ID and CCICV.INVENTORY_ITEM_ID = FRCT.INVENTORY_ITEM_ID, linking MTL_PARAMETERS and resolving the cost group via DECODE(MP.PRIMARY_COST_METHOD, 1, 1, NVL(MP.DEFAULT_COST_GROUP_ID, 1)). The second branch handles the remaining (project-associated) forecast records, unifying the same column list.

Key Columns

• TRANSACTION_ID — identifier for the forecast transaction record.
• INVENTORY_ITEM_ID / ORGANIZATION_ID — the item and inventory organization context of the forecast.
• FORECAST_DESIGNATOR — the forecast designator under which the demand was entered.
• SOURCE_FORECAST_DESIGNATOR — the originating forecast designator, used to trace demand back to its source forecast.
• SOURCE_CODE / SOURCE_LINE_ID / SOURCE_ORGANIZATION_ID — provenance of the forecast demand.
• FORECAST_DATE, ORIGINAL_FORECAST_QUANTITY, CURRENT_FORECAST_QUANTITY — the date bucket and original versus current forecast quantities.
• CONFIDENCE_PERCENTAGE, BUCKET_TYPE, RATE_END_DATE — forecast confidence and bucket characteristics.
• ORIGINATION_TYPE, CUSTOMER_ID, SHIP_ID, BILL_ID — demand origination and party references.
• DEMAND_CLASS, FOCUS_TYPE, FORECAST_RULE_ID, END_ITEM_ID, END_PLANNING_BOM_PERCENT — demand-classification and planning attributes.
• PROJECT_ID / TASK_ID — project and task association (null in the first union branch).
• ITEM_COST — the item cost value obtained from CST_CG_ITEM_COSTS_VIEW.
• ATTRIBUTE_CATEGORY and ATTRIBUTE1–15, DDF_CONTEXT — descriptive flexfield context and segment columns.

Common Use Cases and Queries

Typical scenarios include reviewing forecast demand together with current item cost, tracing demand to its source forecast designator, and reconciling project versus non-project forecast records.

The following query retrieves forecasts by source designator with associated item cost:

• SELECT forecast_designator, source_forecast_designator, inventory_item_id, organization_id, forecast_date, current_forecast_quantity, item_cost FROM apps.mtl_forecast_dates_cost_v WHERE source_forecast_designator = :p_source_designator;

A second common pattern aggregates extended forecast value by organization and designator:

• SELECT organization_id, forecast_designator, SUM(current_forecast_quantity * item_cost) forecast_value FROM apps.mtl_forecast_dates_cost_v GROUP BY organization_id, forecast_designator;

Because the view exposes project and task columns, it also supports filtering non-project forecasts via WHERE project_id IS NULL, and because of the union-based construction, cost values should be interpreted in the context of the organization's primary cost method and default cost group resolved through MTL_PARAMETERS.