Search Results bucket_type_desc




Overview
Explore in AI Chat

Overview

The view APPS.ICX_MRP_FORECAST_DATES_V is a reporting and integration object owned by the APPS schema within Oracle E-Business Suite. It is delivered as part of the ICX (Oracle iProcurement) product family and is described in the ETRM repository simply as the "Forecast Dates View." Despite its association with iProcurement, the view surfaces planning data that originates in Oracle Manufacturing and Master Scheduling, specifically records held in the MRP forecast dates table.

The view's principal role is to expose forecast bucket and origination information in a user-readable form. Raw forecast data in MRP_FORECAST_DATES stores bucket and origination identifiers as lookup codes. The view resolves these codes into descriptive meanings through joins to MFG_LOOKUPS, adding columns such as BUCKET_TYPE_DESC and ORIGINATION_TYPE_DESC. This makes the view suitable for user-facing inquiry, reporting, and integration into planning or procurement dashboards where descriptive text is preferred over internal codes. The status of the object is VALID in the documented 12.2.2 environment, and the same definition is applicable to the 12.1.1 code line.

Underlying Base Objects

The view is defined over four documented objects:

The view therefore consolidates master data (items, organizations, lookups) around a single forecast fact record, providing descriptive context for each forecast row.

Key Columns

Because the user's search term was bucket_type_desc, primary attention should be given to that column.

  • BUCKET_TYPE_DESC — the translated meaning of BUCKET_TYPE, resolved from MFG_LOOKUPS under lookup type MRP_BUCKET_TYPE. This describes the forecast time bucket (for example, a weekly or period bucket designation).
  • BUCKET_TYPE — the underlying lookup code.
  • ORIGINATION_TYPE_DESC — the meaning of the origination type, resolved under lookup type MRP_FORECAST_ORIG, indicating the source of the forecast demand.
  • TRANSACTION_ID, INVENTORY_ITEM_ID, ORGANIZATION_ID — identifying keys for the forecast row.
  • FORECAST_DESIGNATOR, FORECAST_DATE, RATE_END_DATE — the forecast scenario name and its date range.
  • CURRENT_FORECAST_QUANTITY, ORIGINAL_FORECAST_QUANTITY, CONFIDENCE_PERCENTAGE — planning quantity and confidence measures.
  • ITEM_SEGMENTS, END_ITEM_SEGMENT — concatenated item identifiers from MTL_ITEM_FLEXFIELDS.
  • ORGANIZATION_CODE — the source organization identifier from MTL_PARAMETERS.
  • CUSTOMER_ID, SHIP_ID, BILL_ID — parties associated with customer-originated forecasts.
  • DEMAND_CLASS, SOURCE_CODE, SOURCE_LINE_ID — classification and source reference columns for the demand record.

Common Use Cases and Queries

The view is commonly used to produce descriptive forecasts by bucket and by organization. A typical query filters by bucket description to enumerate forecast rows for a planning horizon:

  • Retrieving forecasts by bucket description, item, and organization for a planning report.
  • Grouping current forecast quantity by BUCKET_TYPE_DESC to summarize demand across time buckets.
  • Filtering by ORIGINATION_TYPE_DESC to separate customer-sourced forecasts from internally sourced ones.
  • Joining to item and organization views without re-deriving lookup meanings, since they are already decoded.
SELECT BUCKET_TYPE_DESC,
       ORIGINATION_TYPE_DESC,
       FORECAST_DATE,
       ITEM_SEGMENTS,
       ORGANIZATION_CODE,
       CURRENT_FORECAST_QUANTITY
FROM   APPS.ICX_MRP_FORECAST_DATES_V
WHERE  ORGANIZATION_ID = :org_id
AND    FORECAST_DESIGNATOR = :designator
ORDER  BY FORECAST_DATE;

It is important to note the outer joins. If an end item or source organization has no matching master record, the descriptive columns may return null while the forecast row is still reported. Any query relying on ITEM_SEGMENTS or ORGANIZATION_CODE should therefore account for potential nulls and, where necessary, use an explicit inner join predicate to exclude unmatched rows.